-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse,
On 6/23/12 9:50 AM, Jesse Farinacci wrote: > Greetings, > > On Fri, Jun 22, 2012 at 2:53 AM, Rainer Jung > <rainer.j...@kippdata.de> wrote: >> What is strange is, that startup says you *did* successfully load >> version 1.1.24, so the symbol should be there. >> >> Can you check your tcnative.so file, whether the symbol >> Java_org_apache_tomcat_jni_Poll_addWithTimeout is defined in it >> (using nm or whatever alternative there is on S390). > > I'm sorry for the delay in response, thank you for your > suggestions. The shared object looked just fine, I discovered the > real issue after digging around. I had an old v1.1.17 > tomcat-native.jar file on the classpath, so even though the 1.1.24 > was available, it seems it took the 17 version first, as > alphabetically it did come first. Wow, where did you get a 1.1.17 JAR file? The JNI-related classes are currently located in tomcat-coyote.jar and should be fairly tightly-bound to a particular Tomcat version. > The message we saw: > > 22-Jun-2012 00:41:05.701 INFO [AsyncFileHandlerWriter-1149650054] > org.apache.catalina.core.AprLifecycleListener.init Loaded APR > based Apache Tomcat Native library 1.1.24 using APR version 1.3.3. Some kind soul recently added that message to the APRLifecycleListener to help clarify things. In this case, it seems to be lying. Tomcat should be nixing any existing CLASSPATH when you launch it. Have you modified the startup process? Or, did you do something silly like have that JAR file in an endorsed directory? Also, the log message above is coming from a recent version of the Java code, so I'm not sure how you had a new version of the Java, plus a new version of the native libraries and still experienced such weirdness. > must have been only referencing the shared object version and its > underlying APR linkage. Not the actual tomcat-native jar version > information. In retrospect, I find this a bit confusing, but maybe > some other more experienced people here can weigh in whether or not > it would be valuable to add additional information to that log > line. Specifically, the tomcat native jar version which is doing > the loading (perhaps even with a version mismatch warning). Hrm. > Removing the old 1.1.17 jar, and letting the 1.1.24 do its job, > solved the problem! Thanks again for your help, What was the name of that JAR file, and where was it? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/mYvwACgkQ9CaO5/Lv0PApZgCgslXwaU1Skv0J9+hIsYLNrcL4 CdUAn2xL9BqErC8FBFSp+at35KHCxiAG =p8YS -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
