|
From: Leif M. <le...@ta...> - 2004-01-31 03:14:37
|
My reply never showed up on the list, so resending it: --- Lakshman, I am not aware of any such problems with the Wrapper. The Wrapper itself makes use of JNI calls and I have not seen any string related problems on my 2k system. What does the string contain? Are they standard characters or extended? How are you returning the string to the JVM? I always use byte arrays and then decode them into strings in the JVM. It makes it much easier to deal with various character sets. I can't think of any reason why the app would work standalone but fail under the wrapper however. What is the thread that you are referring to? Is the JNI library something that you developed? Would it be possible to add some debug output to it just before returning the string to the JVM? Rereading your post, you say that it works when running in a console. This is under the Wrapper correct. But it is failing when running as a service. When run as a service, the Wrapper is run using the SYSTEM user. Is it possible that there are some environment differences between the user running the console version vs the SYSTEM user? By the way, could we move this over to the wrapper-user mailing list? The posts are more visible and others may have some useful feedback. Cheers, Leif Lakshmanan Ramakrishnan wrote: >Hi, > > We have a strange problem with Windows 2000 . We are using wrapper >3.0.5. > > We call a JNI dll to get a string. We get the string properly when >we run it as a console application. But when we run it as a NT service, we >are getting back a junk string. > > The same application is working fine in a XP machine. > > In one of the threads, I found a similar problem and seems the fix >is in the next release. So can any one tell me when would be the next >release. > >Lakshmanan > > |