|
From: Leif M. <lei...@ta...> - 2010-06-19 03:36:34
|
Juan, Sorry for the delay. I am looking at it now. Your first mail arrived at 12:46am on Friday night here in Japan. I am able to reproduce the shutdown and am looking into the cause. I will hopefully be able to get back to shortly. Cheers, Leif On Sat, Jun 19, 2010 at 12:17 PM, Juan Sanchez <jsa...@pu...> wrote: > Hi Leif, I have sent you a mail with a sendspace link 12 hours ago, I > don't know if you received this one ? . any news? all my project can > be frustrated because of that problem :( > > Thanks > > Juan > > > > > > Leif Mortenson escribió: >> Juan, >> The Wrapper is able to load the file as wrapper.dll OR >> wrapper-windows-x86-32.dll. It does this so that it can have the >> native library for multiple platforms in the same directly. Users who >> want to deploy this way make use of the "delta pack" release of the >> Wrapper. In your case it is working correctly. >> >> I am trying to figure out what could be causing this for you. If you >> could send me a simple class that reproduces this it would be a big >> help in getting this resolved for you promptly. >> >> Thanks in advance >> Leif >> >> On Fri, Jun 18, 2010 at 4:18 PM, Juan Sanchez <jsa...@pu...> wrote: >> >>> Leif, I noticed that the DLL was wrong positioned, I fixed it... but >>> I have noticed in the wrapper.log that it can not found the file >>> wrapper-windows-x86-32.dll , but I have never gotten it ... I only >>> have the wrapper.dll file. I did the process once again but everything >>> still with the same mistakes. If I close the GUI , the services stop. >>> When I downloaded the wrapper packet I didn´t have the >>> wrapper-windows-x86-32.dll file. >>> >>> thks >>> Juan >>> >>> Leif Mortenson escribió: >>> >>>> Juan, >>>> Thank you for the log. It shows that there are a few non-daemon >>>> threads still running so that is not why the JVM is exiting. Since >>>> you are also not calling System.exit, then the most likely cause is a >>>> an external source shutting down the JVM. Any Wrapper induced >>>> shutdown would result in a log entry being made, so it must be coming >>>> directly to the JVM. >>>> >>>> One of the jobs of the wrapper.dll is to protect the JVM against such >>>> signals and log them when they take place. The Wrapper is currently >>>> looking in the following directory for the wrapper.dll. The error >>>> messages are saying that it does not exist. If the file were found, >>>> but simply corrupted then the error message would be different: >>>> C:\Documents and Settings\cooljsh\Mis >>>> documentos\chamba\cachuelo2\DEPLOY\MonitorLanCenter\lib >>>> >>>> Is your application something that we could try out locally? Sent off >>>> list of course. If not, would it be easy to create a simple class to >>>> reproduce what you are seeing? >>>> >>>> Cheers, >>>> Leif |