Re: [Wrapper-user] Re: DCOM and wrapper

[Leif M. <le...@ta...>]

Philip,
Have you made any progress with your DCOM issue? There was a post today on a
related issue that may be at the root of your problems. He noticed that 
DCOM was
expecting the JVM to be the one specified by JAVA_HOME, but the JVM launched
by the Wrapper was not the same due to the value of the wrapper.java.command
property.

Go take a look at the issue and let me know the status of your problem.
http://sourceforge.net/tracker/index.php?func=detail&aid=820216&group_id=39428&atid=425187

Cheers,
Leif

Philip Kubat wrote:

> Ok, here is my guess on what is going on. DCOM/COM interfaces exists 
> in a MTA (multi thread apartment) and maintains is own reference 
> counter to threads using it, as stated my Microsoft. When I the java 
> app in ran within wrapper the jni calls are started in new threads. I 
> can view this via the Microsoft debugger. When the first call finishes 
> that thread ends, (prior to me next jni call) and it kills the last 
> and only reference in the MTA. Thus when the other JNI calls go to use 
> this interface it now longer exists.
>
> So the question is why do the jni calls get place in new threads. This 
> is not the results when the app is not ran within wrapper. IE “java 
> myAppClass”
>
> Thanks
>
> Phil
>