> 2.Created 1 COM wrapper in VB to call the method of Win32 dll.
> when using the COM Wrapper with .NET application its working fine.
[quoted text clipped - 4 lines]
> To get the correct result everytime i need to restart the IIS server
> and inetinfo preocess.
>>2.Created 1 COM wrapper in VB to call the method of Win32 dll.
>>when using the COM Wrapper with .NET application its working fine.
[quoted text clipped - 11 lines]
> doesn't matter whether you close the first one cleanly, you are still not
> allowed to create a second one.
Chris,
That is a very interesting fact. Do you have any resources where I can
learn more?
Thanks,
Ray
> As to how to fix it, I'm afraid I have no idea. You can't do it by messing
> around with the JVM, you'll have to fix the way that the COM objects are
> handled somehow.
The most obvious (but hacky) way would be to invoke the JVM as a
separate process.

Signature
XML is the programmer's duct tape.
Chris Uppal - 04 Jan 2006 12:05 GMT
[me:]
> > a process has exactly one
> > chance to create a JVM instance, once it has created it, it cannot
[quoted text clipped - 3 lines]
> That is a very interesting fact. Do you have any resources where I can
> learn more?
I don't, I'm afraid. It's just one of those things that's well-known to anyone
who works much with JNI to call (as opposed to be called by) Java. There's a
bug-parade entry somewhere where Sun state that they have no intention of
ever making their JVM behave as implied by (their own!) API, but you should be
able to find that as easily as I (or rather, with no greater awkward
inconvenience than I).
I'm baffled on two counts. One is /how/ do they implement the restriction ?
The other is /why/ ? Bloody irritating...
-- chris