RE: [Wrapper-user] socket creation failed and libwrapper.so

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi Leif,

Thanks for your very quick answer (can't imagine a quicker one!).

I have pasted the new "wrapper.log" (using the modified wrapper.jar) at the
end the text.

Regarding Problem 1: we have done a test after changing the permissions on
the file "libwrapper.so" to 777, but it produces exactly the same output as
with default permisions (644).

Question: how could we check if the "libwrapper.so" file is corrupted?
FYI, a checksum on the file gives:
26458 32 libwrapper.so

"DEBUG  | wrapper  | 2003/04/09 15:28:01 | Spawning intermediate process...
DEBUG  | wrapper  | 2003/04/09 15:28:02 | Spawning daemon process...
STATUS | wrapper  | 2003/04/09 15:28:02 | --> Wrapper Started as Console
INFO   | wrapperp | 2003/04/09 15:28:02 | port 1777 already in use, using
port 1781 instead.
DEBUG  | wrapperp | 2003/04/09 15:28:02 | server listening on port 1781.
DEBUG  | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[0] : /opt/java1.3/bin/java
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[1] : -Xms3m
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[2] : -Xmx64m
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[3] :
-Djava.library.path=/home/vccdev/VCCInt/deploy/lib
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[4] : -classpath
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[5] :
/home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[6] :
-Dwrapper.key=NZop9_KQY_q7viil
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[7] : -Dwrapper.port=1781
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[8] : -Dwrapper.debug=TRUE
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[9] :
-Dwrapper.cpu.timeout=10
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[10] : -Dwrapper.jvmid=1
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[11] :
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG  | wrapper  | 2003/04/09 15:28:03 | Command[12] :
com.spower.vcc.intf.client.VCCRxClient
STATUS | wrapper  | 2003/04/09 15:28:03 | Launching a JVM...
DEBUG  | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG  | wrapperp | 2003/04/09 15:28:04 | socket creation failed. (11)
INFO   | jvm 1    | 2003/04/09 15:28:04 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2003/04/09 15:28:04 | Wrapper Manager: Registering
shutdown hook
INFO   | jvm 1    | 2003/04/09 15:28:04 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2003/04/09 15:28:04 | java.lang.UnsatisfiedLinkError: no
wrapper in java.library.path
INFO   | jvm 1    | 2003/04/09 15:28:04 | 	at
java.lang.ClassLoader.loadLibrary(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 	at
java.lang.Runtime.loadLibrary0(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 	at
java.lang.System.loadLibrary(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 	at
org.tanukisoftware.wrapper.WrapperManager.<clinit>(WrapperManager.java:393)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 	at
org.tanukisoftware.wrapper.WrapperSimpleApp.main(WrapperSimpleApp.java:366)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 
INFO   | jvm 1    | 2003/04/09 15:28:04 | WARNING - Unable to load native
library 'libwrapper.so'.  The file
INFO   | jvm 1    | 2003/04/09 15:28:04 |           is located on the path
at the following location but could
INFO   | jvm 1    | 2003/04/09 15:28:04 |           be loaded:
INFO   | jvm 1    | 2003/04/09 15:28:04 |
/home/vccdev/VCCInt/deploy/lib/libwrapper.so
INFO   | jvm 1    | 2003/04/09 15:28:04 |           Please verify that the
file is readable by the current user
INFO   | jvm 1    | 2003/04/09 15:28:04 |           and that the file has
not been corrupted in any way.
INFO   | jvm 1    | 2003/04/09 15:28:04 |           System signals will not
be handled correctly.
INFO   | jvm 1    | 2003/04/09 15:28:04 | 
INFO   | jvm 1    | 2003/04/09 15:28:04 | Java Version   :
1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM
INFO   | jvm 1    | 2003/04/09 15:28:04 | Java VM Vendor : Hewlett-Packard
Company
INFO   | jvm 1    | 2003/04/09 15:28:04 | 
INFO   | jvm 1    | 2003/04/09 15:28:04 | Wrapper (Version 3.0.2a)
INFO   | jvm 1    | 2003/04/09 15:28:04 | 
INFO   | jvm 1    | 2003/04/09 15:28:04 | Open socket to wrapper...
INFO   | jvm 1    | 2003/04/09 15:28:04 | Opened Socket
INFO   | jvm 1    | 2003/04/09 15:28:04 | Send a packet 110 :
NZop9_KQY_q7viil
INFO   | jvm 1    | 2003/04/09 15:28:04 |
handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=60260])
DEBUG  | wrapperp | 2003/04/09 15:28:04 | accepted a socket from 127.0.0.1
on port 60260
DEBUG  | wrapperp | 2003/04/09 15:28:04 | read a packet 110 :
NZop9_KQY_q7viil
DEBUG  | wrapper  | 2003/04/09 15:28:04 | Got key from JVM: NZop9_KQY_q7viil
DEBUG  | wrapperp | 2003/04/09 15:28:04 | send a packet 112 : 1
DEBUG  | wrapperp | 2003/04/09 15:28:04 | socket read failed. (11)
DEBUG  | wrapper  | 2003/04/09 15:28:04 | Start Application.
DEBUG  | wrapperp | 2003/04/09 15:28:04 | socket creation failed. (11)
ERROR  | wrapper  | 2003/04/09 15:28:04 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2003/04/09 15:28:04 | JVM did not exit on request,
terminated
INFO   | jvm 1    | 2003/04/09 15:28:05 | Received a packet 112 : 1
INFO   | jvm 1    | 2003/04/09 15:28:05 | Wrapper Manager: LowLogLevel from
Wrapper is 1
INFO   | jvm 1    | 2003/04/09 15:28:05 | java.io.EOFException
INFO   | jvm 1    | 2003/04/09 15:28:05 | java.io.EOFException
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
java.io.DataInputStream.readByte(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.java:1
434)
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:1750)
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:05 | Dump the stack so I can see how we
got here.
INFO   | jvm 1    | 2003/04/09 15:28:05 | java.lang.Exception: Stack trace
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
java.lang.Thread.dumpStack(Unknown Source)
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
org.tanukisoftware.wrapper.WrapperManager.closeSocket(WrapperManager.java:13
30)
INFO   | jvm 1    | 2003/04/09 15:28:05 | 	at
org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:1767)
DEBUG  | wrapperp | 2003/04/09 15:28:05 | socket creation failed. (11)
DEBUG  | wrapper  | 2003/04/09 15:28:05 | JVM was only running for 2 seconds
leading to a failed restart count of 1."

Thanks again for the great support.

Best Regards,
Nicolas

-----Original Message-----
From: Leif Mortenson
To: wra...@li...
Sent: 4/9/2003 2:37 PM
Subject: Re: [Wrapper-user] socket creation failed and libwrapper.so

Nicolas,
    Thanks for the detailed report.  I do not have access to an HP-UX 
machine but others have been using  it on that platform without problems as
far as I know. If any HP-UX users out there could chime in, I would
appreciate it.

    Problem 1:  The library not being loaded.  Looking at the ls and 
wrapper.log output that you provided, the only ideas that I have here are
permission problems reading the file or maybe that the library file is
corrupted.  In the wrapper.jar file that I am sending you, I have added code
to test for this case.  This will be in the 3.0.2 release as well.

    Problem 2:  Socket disconnect problem. This one is puzzling. The
Java side successfully connects to the native code and sends back the 
authorization key. The Wrapper then responds by sending the Log Level to the
JVM.  The JVM is successfully reading this Log Level and displaying a
message.  The problem is that at this point, it appears that the JVM is
closing the socket for some reason.

   Looking at the code, the only thing that I can find that would cause
this is if an IOException was being thrown.  I am currently not displaying
this stack trace because up until now, it is only thrown in the event of the
socket being closed on shutdown.   This may not be correct.

   I have temporarily added some stack dumps to the code and have build you
a special wrapper.jar file to test this. (I will send it to you directly as
everyone else on the list does not need it.  Please respond to
the list though.)

   If you could send me the new wrapper.log just as you did this time, it
might give me the info I need to get this fixed for you.  I only need a
single run of the Wrapper output. You don't need to send all 5 attempts at
launching the JVM.

Cheers,
Leif

Moulin, Nicolas wrote:

>Hi All,
>
>We are having an issue when running the wrapper 3.0.1 on HP-UX11i.
>
>It seems that there is a socket problem and also the file
"libwrapper.so"
>can't be found, ALTHOUGH it is existing in the directory where the
wrapper
>is trying to find it (see log below)...
>
>Please find below the content of the "wrapper.log" file:
>  
>
<snip>

>Note:
>$ ls -lrt /home/vccdev/VCCInt/deploy/lib/libwrapper.so
>
>-rw-r--r--   1 vccdev     dev          16384 Apr  8 17:51
>/home/vccdev/VCCInt/deploy/lib/libwrapper.so
>

-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

____________________________________________________
This message contains information that may be privileged or confidential and
is the property of the Cap Gemini Ernst & Young Group. It is intended only
for the person to whom it is addressed. If you are not the intended
recipient, you are not authorised to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all copies
of this message.