-
sorry vikram, I pasted the console logs, here are the logs found under /tmp/j-Interop0.log:
I think it is trying to resolve a netbios name which it cannot do. I fixed the issue by placing the correct ip address in /etc/hosts but I cannot figure why the netbios name is being used instead of the IP address. No where in my application I am using the netbios name.
It could be that it was...
2009-06-26 13:18:03 UTC in j-Interop : Java - COM Interoperability
-
same exact operations performed on a windows box:
================================================================================
= Testing: string payload =
= (com.example.MsmqFunctional2TestCase) =
================================================================================
[06-26 13:49:22] WARN...
2009-06-26 11:56:01 UTC in j-Interop : Java - COM Interoperability
-
Hi Vikram, here are the logs set at Finest Level.
Sequence of events is the following:
//create queueInfo object
session = JISession.createSession(auth.getDomain(), auth.getUsername(), auth.getPassword());
progId = getProgId();
comServer = new JIComServer(progId , auth.getHost(), session);
comObject = comServer.createInstance();
dispatchInterface =...
2009-06-26 11:46:59 UTC in j-Interop : Java - COM Interoperability
-
I have built an application that interacts with MSMQ using JInterop 2.06, and for message notification, I have also managed to attach an event handler such that MSMQ calls my custom method whenever a new message makes it to the queue.
This works perfectly well on a Windows machine, even when the client has no MSMQ, but event handling is not working well when the client (which uses JInterop...
2009-06-26 10:14:10 UTC in j-Interop : Java - COM Interoperability
