Hi Chuck,
> -----Original Message-----
> From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2008 4:59 PM
> To: Tomcat Users List
> Subject: RE: SEVERE: Error listenerStart
>
>
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Subject: SEVERE: Error listenerStart
> >
> > As far as I understand the term "listener" seems to be a bit
> > of a misnomer as no listening socktet (which I guess is
termed
> > a "connector" in J2EE speech) is concerned but rather a
callback
> > method provided by some webapp derived class.
>
> Read the servlet spec. A Listener is this case has nothing to
do with
> sockets, but rather with lifecyle events of the webapp.
>
Come on, I have no inclination to become a J2EE hacker.
Yet, I still maintain that the term "listener" is very
misleading.
If I hear something about lifecyle events
then rather event handlers or callbacks come to my mind but
certainly not listeners.
Probably I am Perl-spoilt for Java's fancy nomenclature.
> > java.lang.UnsatisfiedLinkError: no aDISWeb in
java.library.path
>
> Read up on Java. The above refers to a *native* library (a
.so) file,
> not a class file, that needs to be present for this webapp to
> run. The
> java.library.path system property refers to the location of
native
> libraries, not class files, and is obviously not set
> correctly for this
> application.
Ok, this is a great help.
So despite the OO distracting system property we are referring to
shared libs
instead of app provided classes.
Didn't know this.
So it is pretty much the same like populating the env var
LD_LIBRARY_PATH on JVM startup then?
Btw, would a -Djava.library.path provided argument take
precedence over LD_LIBRARY_PATH settings,
or do they even mix?
I can see two shared libs that must have been deployed together
with the app.
# find /var/www/tomcat/current/webapps/aDISWeb -name \*so
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_sl
.so
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_lx
.so
But interestingly, they both are 32bit builds while my kernel is
a 64Bit one.
So could we have some kind of ABI mismatch here?
# find /var/www/tomcat/current/webapps/aDISWeb -name \*so|xargs
file
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_sl
.so: ELF 32-bit MSB shared object, SPARC, version 1 (SYSV), not
stripped
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_lx
.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV),
not stripped
# ldd
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_lx
.so
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf7faf000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xf7ef6000)
libm.so.6 => /lib/libm.so.6 (0xf7ecf000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7ec3000)
libc.so.6 => /lib/libc.so.6 (0xf7d82000)
/lib/ld-linux.so.2 (0x56555000)
Can you see if this lib provides the required method
implementation?
# nm
/var/www/tomcat/current/webapps/aDISWeb/WEB-INF/lib/libaDISWeb_lx
.so|grep aDISWeb
0000000000004ae0 T
Java_de_astec_aDISWeb_aDISEngine_aDISEndSession
0000000000004240 T Java_de_astec_aDISWeb_aDISVisit_aDISWeb
00000000000056c0 T
Java_de_astec_aDISWeb_util_aDISTracing_configProgTrace
00000000000055c0 T
_Z48Java_de_astec_aDISWeb_util_aDISTracing_ProgTraceP7JNIEnv_P7_j
classP8_jstringi
0000000000004bc0 T _Z7aDISWebR9t_REQUEST
Many thanks for your help!
Ralph
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
