MsmqJava

Commented Issue: Makefile with 64 bit support

snakefoot — Thu, 27 Aug 2009 08:24:08 GMT

Unless having knowledge about JNI, C++ and Java, then it can be difficult to setup Microsoft SDK properly.

To setup an environment for compiling the DLL:

1) Install Microsoft Vista SDK and ensure that x64 compiler and library is selected (Unselect documentation and samples)
- Have tried using Win2008 SDK and Win7 SDK but the SetEnv.cmd is faulty (Fails to set LIB-path and PATH environment variables properly)
2) Install Sun JDK (I used Sun JDK 1.6 14)
3) Modify the makefile so it points to SDK and JDK
JAVADIR = "C:\Program Files\Java\jdk1.6.0_14"
VC = "C:\Program Files\Microsoft SDKs\Windows\v6.0\VC"
PSDKDIR = "C:\Program Files\Microsoft SDKs\Windows\v6.0"

To compile the 32 bit dll:
1) Open a command prompt
2) Setup the VC environment by running this command
"C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\SetEnv.Cmd" /Release /x86 /xp
3) Go to the Msmqjava source code (where the makefile resides), and run this command
nmake

To compile a 64 bit dll, then we need to modify the makefile, so it becomes aware of what environment we are targetting. I have attached a makefile, that checks the environment variable CPU and sets the compiler and library accordinly. Use this makefile instead of the one supplied with MsmqJava.

To compile the 64 bit dll (After having updated to the new makefile):
1) Open a command prompt
2) Setup the VC environment by running this command (Notice x64)
"C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\SetEnv.Cmd" /Release /x64 /xp
3) Go to the Msmqjava source code (where the makefile resides), and run this command
nmake
Comments: ** Comment from web user: snakefoot **

Seems the reason why SetEnv.cmd on Win2008/Win7 SDK is not working is because it should either be launched with some extra parameters to properly execute SetEnv.cmd:

cmd.exe /E:ON /V:ON

The same parameters are used when using the shortcuts in the Start Menu created by the SDKs

Commented Issue: Makefile with 64 bit support

snakefoot — Tue, 25 Aug 2009 15:49:00 GMT

Btw. I have modifed the compiler options in the attached makefile, so it compiles with static libraries, so one avoids the need to deploy extra Microsoft DLLs. http://blogs.msdn.com/aymans/archive/2006/04/04/568466.aspx

Created Issue: Makefile with 64 bit support

snakefoot — Tue, 25 Aug 2009 15:46:26 GMT

New Post: Transactional support

snakefoot — Tue, 25 Aug 2009 15:16:53 GMT

I guess it will be near impossible to attach the MSQM-operations to a java-transaction.

MSMQ has its own transaction manager. It can be started using MQBeginTransaction.

http://msdn.microsoft.com/en-us/library/ms699827(VS.85).aspx

I guess one should create a transaction manager-wrapper, that will handle commit/abort of the MQ-Transaction. This will ensure that if exceptions are thrown after having started a MSMQ transaction, then it will automatically abort the transaction when the transaction manager is destroyed (Unless explicit commit was performed). No idea if this is possible in java garbage collection world.

New Post: Transactional support

Cheeso — Tue, 11 Aug 2009 21:57:19 GMT

I am not familiar with how to do transactions in C code on Windows.

I'll need more than a little help implementing that feature.

New Post: Transactional support

miridk — Fri, 10 Jul 2009 16:25:55 GMT

Hi,

great project, I am very happy I found this project, it will save me alot of
time. One thing though, even though it partly supports transactional
queues, I really need an explicit commit and rollback method, instead
of an implicit one. I know it is possible in MSMQ. I hope you can find the
time to implement this. I can send you the C# code for it, if that helps.

Best regards,
Michael

New Post: Problem running native methods

csgordon — Wed, 18 Jun 2008 20:08:56 GMT

I figured out that it stops proceeding right when it trys to load the JNIMSMQ.dll file in the static initializer block in Queue.java.

It must not successfully load the dll file, but I do not receive any error or warning or anything. I've also tried placing the .dll file in all different locations, so I'm not sure why it isn't working.

Edit:

At first I could not get it to load the .dll file, at least it would not hit any code after this statement. However, using System.load and the absolute path, I was able to hit code that was after the load .dll statement. However, it would not go past the nativeInit() code even when running past the System.load( ) call.

It doesn't seem to be running these native calls properly, and I believe this is the source of the problem.. any suggestions? Am I not properly including any of the files (I only have Queue.java, Message.java, MessageQueueException.java, and JNIMSMQ.dll in the project)? I'm not sure where to put the C files or how to reference them.

Since I changed the code do I have to create a new .dll file to reference the changed class files? And if so, how can I do that? I've tried making a new .dll library based off of tutorials I've seen online but none of the commands seem to be working (I'm working in windows).

Thanks.

New Post: Problem running native methods

csgordon — Wed, 18 Jun 2008 19:30:50 GMT

Hi,
This is going to be pretty hard to explain but I figured I'd try anyway...

Basically, I'm running some code that implements a listener (this is in java), and upon triggering this listener, I want the program to automatically Open an exisiting queue in MSMQ, and send a given message to that queue.

I've commented out main in the TestClient.java MsmqJava code, and basically I run the Open and Send methods (changed slightly) when this listener is triggered to acheive what I want.

Right now, when the program runs and the listener is triggered, the code gets to the Open method in the MsmqJava code, but when it reaches the "Msmq = new Queue(name);" line (where it actually sets the instance of Queue to the one given to open it), it seems to stop. The program itself does not stop running, and there is no error given, and when the next listener is triggered it reapeats this process, but it seems to be having trouble actually accessing the Queue.java code (since nothing after this code in the MSMQ side is hit. No message is sent, the queue doesn't even seem to actually open). Since I am using a separate application to link to this one, I have several different directories and I have a feeling that this is why it's not working. Perhaps the Queue.java, etc., files are not being accessed properly or perhaps the JNIMSMQ.dll file is not being found. But I figured this would trigger its own error, and everything compiles and runs fine (up until this problem).

I know that I can't exactly describe the situation better than that but I was hoping maybe something would stand out and you'd be able to help.

Thanks very much, I appreciate it.

New Post: UnsatisfiedLinkError

intltechventures — Wed, 11 Jun 2008 02:59:39 GMT

The latest release of the Apache ActiveMQ 5.1 now includes a JMS-to-MSMQ bridge that may be worth looking at too.

https://issues.apache.org/activemq/browse/AMQ-438

http://activemq.apache.org/

New Post: UnsatisfiedLinkError

intltechventures — Wed, 11 Jun 2008 02:55:19 GMT

Try passing this parameter when you run the program (java -Djava.library.path=c:\yourpathtothedll

You might also try downloading the zip file I posted in the patches area - and look at the modified bat files I included to see how to invoke the program.

NEW POST: UnsatisfiedLinkError

csgordon — Mon, 09 Jun 2008 16:08:37 GMT

Hi, when running TestClient.java I'm getting an exception upon hitting ENTER to specify the location of the server as local (in other words, when opening a queue, i enter the name of the queue and then it prompts for the location and I hit enter and receive the following error)
The exception is:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no JNIMSMQ in java.library.path

at java.lang.ClassLoader.loadLibrary(Unknown Source)

at java.lang.Runtime.loadLibrary0(Unknown Source)

at java.lang.System.loadLibrary(Unknown Source)

at ionic.Msmq.Queue.<clinit>(

Queue.java:201)

at TestClient.Open(

TestClient.java:136)

at TestClient.Run(

TestClient.java:232)

at TestClient.main(

TestClient.java:22)

I'm sure this is a very simple error, but I'm fairly new to programming in general and so I'm not exactly sure how to fix it. I'm assuming I need to download JNIMSMQ.dll to a certain location. If so, where is that?
Any help would be greatly appreciated.
Thanks.

Patch Uploaded

intltechventures — Sat, 10 May 2008 00:57:08 GMT

intltechventures has uploaded a patch.

Description:
I reorganzied the source code into separate directories for the C#, C++, and Java code; created an Eclipse project (3.3. Europa); refactored the build process to use an Ant-1.7 build.xml; and added an Ant task to automatically generate javadocs.

I also modified TestClient.java so that you can now specify either a public queue - or a private queue name at the input prompt:

E.g.
// return "DIRECT=" + a1 + ":" + h1 + "\\private$\\" + queueShortName;
return "DIRECT=" + a1 + ":" + h1 + "\\" + queueShortName;

For a private queue named myTest, you would specify private$\\myTest at the input prompt for the queue name.
For a public queue, you would simply specify myTest.

CREATED ISSUE: need Unit Tests

Cheeso — Wed, 06 Feb 2008 19:09:01 GMT

There ought to be unit tests for MsmqJava.

Source code checked in

Cheeso — Wed, 06 Feb 2008 06:22:10 GMT

Added read & send methods for byte[] . Previously, there were only read + send for Strings.

UPDATED RELEASE: 1.0 (Feb 05, 2008)

Wed, 06 Feb 2008 01:44:28 GMT

Initial release of the JNI MSMQ library, which allows Java applications to connect to MSMQ, via a JNI library.

Source code checked in

Cheeso — Wed, 06 Feb 2008 01:42:43 GMT

added a license file, updated the makefile.

Source code checked in

Cheeso — Wed, 06 Feb 2008 01:37:17 GMT

Initial checkin of the MsmqJava code.

UPDATED WIKI: Home

Cheeso — Wed, 06 Feb 2008 01:21:12 GMT

Project Description
This is a JNI library for MSMQ. It allows Java applications to connect to MSMQ on Windows.

Summary
Many Java applications have the need to connect to MSMQ, for various reasons. For one, MSMQ can serve as a key interop conduit between Java and .NET applications. Outside of interop scenarios, Java applications can take advantage of MSMQ by themselves.

At least initially, this library is going to be pretty basic. Depending on interest, it may grow.