RE: After installation: UnsatisfiedLinkError: libawt: libXp.so.6
I've had almost this exact same problem. What was the answer for you? -Original Message- From: Jonathan Crenner [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 5:44 AM To: [EMAIL PROTECTED] Subject: After installation: UnsatisfiedLinkError: libawt: libXp.so.6 Hi All, I'm trying to have Cocoon successfully running on the following config after having developed/tested my applications with Cocoon under Windows: * Linux Mandrake 8.1 kernel 2.4.8 * Tomcat 4.0.3 * Cocoon 2.0 * Sun's jdk 1.4.0 Cocoon initializes correctly, but after the first request (which fails: The sitemap handler's sitemap is not available.), here is what I get in the error.log file (full listing at the end): java.lang.UnsatisfiedLinkError: /usr/java/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) I thought I had a problem with AWT, but I coded a simple AWT application which worked perfectly... If I check the libraries with ldconfig -p | grep libXp, I get: libXp.so.6 (libc6) = /usr/X11R6/lib/libXp.so.6 libXp.so (libc6) = /usr/X11R6/lib/libXp.so So the libXp.so library that Cocoon claims to be missing is available on the system... This is not even a problem because my server is headless, otherwise I assume I would have got: java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable. Anyway, even if I have an X server running, the exception gets sent as well This is neither linked to jdk 1.4 as I upgraded from 1.3 to try to solve the problem and the exception was the exact same with this older version... So has anyone got this error or has clues on how to solve it? Thanks a lot in advance for your help, Jonathan Crenner Complete listing of error.log: FATAL_E (2002-03-18) 13:04.16:965 [core.datasources.personnel] (Unknown-URI) Unknown-thread/LogKitLogger: Excalibur could not create any connections. Examine your settings to make sure they are correct. Make sure you can connect with the same settings on your machine. ERROR (2002-03-18) 13:16.18:526 [sitemap.generator.velocity] (/cocoon/) HttpProcessor[8180][4]/VelocityGenerator: ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ERROR (2002-03-18) 13:16.18:724 [sitemap.generator.velocity] (/cocoon/) HttpProcessor[8180][4]/VelocityGenerator: ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ERROR (2002-03-18) 13:16.18:846 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:849 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:874 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:876 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:924 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:926 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:946 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:949 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.23:404 [sitemap] (/cocoon/) HttpProcessor[8180][4]/Handler: Error compiling sitemap java.lang.UnsatisfiedLinkError: /usr/java/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1480) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1396) at java.lang.Runtime.loadLibrary0(Runtime.java:772) at java.lang.System.loadLibrary(System.java:832) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1397) at java.awt.Toolkit.clinit(Toolkit.java:1418) at java.awt.Color.clinit(Color.java:250) at org.apache.batik.css.value.DefaultSystemColorResolver.activeBorder (Unknown Source) at
Re: After installation: UnsatisfiedLinkError: libawt: libXp.so.6
I believe I have a solution for your problem. It may become problematic in a production environment. My tomcat is set up to run under the tomcat user. the X display :0 is always logged in under corey. Basically X server does not allow the batik code (which is the AWT requirement) to connect to the server because it is the tomcat user. It should be pretty obvious I'm surrently using my workstation as my cocoon server, so this may not apply to you. Two solutions: 1. Install an AWT library which is not dependant on X libs (Apparently all Sun and IBM JDKs are. This is probably the better solution. There's a link somewhere in the cocoon docs to such an AWT implementation. 2. A quick X solution is to run 'xhost localhost' which adds localhost to the list of accepted network clients. I have tomcat set up to boot with the machine via an init.d script, but I've found I have to kill it and restart after enabling localhost to connect to X. Also you may have to nuke the contents of tomcat/work to clear the cache. HTH Corey On Mon, 2002-03-18 at 04:43, Jonathan Crenner wrote: Hi All, I'm trying to have Cocoon successfully running on the following config after having developed/tested my applications with Cocoon under Windows: * Linux Mandrake 8.1 kernel 2.4.8 * Tomcat 4.0.3 * Cocoon 2.0 * Sun's jdk 1.4.0 Cocoon initializes correctly, but after the first request (which fails: The sitemap handler's sitemap is not available.), here is what I get in the error.log file (full listing at the end): java.lang.UnsatisfiedLinkError: /usr/java/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) I thought I had a problem with AWT, but I coded a simple AWT application which worked perfectly... If I check the libraries with ldconfig -p | grep libXp, I get: libXp.so.6 (libc6) = /usr/X11R6/lib/libXp.so.6 libXp.so (libc6) = /usr/X11R6/lib/libXp.so So the libXp.so library that Cocoon claims to be missing is available on the system... This is not even a problem because my server is headless, otherwise I assume I would have got: java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable. Anyway, even if I have an X server running, the exception gets sent as well This is neither linked to jdk 1.4 as I upgraded from 1.3 to try to solve the problem and the exception was the exact same with this older version... So has anyone got this error or has clues on how to solve it? Thanks a lot in advance for your help, Jonathan Crenner Complete listing of error.log: FATAL_E (2002-03-18) 13:04.16:965 [core.datasources.personnel] (Unknown-URI) Unknown-thread/LogKitLogger: Excalibur could not create any connections. Examine your settings to make sure they are correct. Make sure you can connect with the same settings on your machine. ERROR (2002-03-18) 13:16.18:526 [sitemap.generator.velocity] (/cocoon/) HttpProcessor[8180][4]/VelocityGenerator: ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ERROR (2002-03-18) 13:16.18:724 [sitemap.generator.velocity] (/cocoon/) HttpProcessor[8180][4]/VelocityGenerator: ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ERROR (2002-03-18) 13:16.18:846 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:849 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:874 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:876 [sitemap.generator.xmldb] (/cocoon/) HttpProcessor[8180][4]/XMLDBGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:924 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:926 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.18:946 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: There was a problem setting up the connection ERROR (2002-03-18) 13:16.18:949 [sitemap.generator.xmldbcollection] (/cocoon/) HttpProcessor[8180][4]/XMLDBCollectionGenerator: Make sure that your driver is available ERROR (2002-03-18) 13:16.23:404 [sitemap] (/cocoon/) HttpProcessor[8180][4]/Handler: Error compiling sitemap java.lang.UnsatisfiedLinkError: /usr/java/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6:
