1-Sep-2004 1:46:26 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
These two lines say that the JK2 connector has started normally it
seems to me that the problem isn't on the java side
ld.so.1: /usr/java/bin/java: fatal: relocation error: file
Hi all...
I ran the ldd utility on the jni dynamic library libjkjni.so with
the following results:
ldd libjkjni.so
libcrypt_i.so.1 = /usr/lib/libcrypt_i.so.1
libapr-0.so.0 =
/usr/local/apache-httpd-2.0.50/lib/libapr-0.so.0
libc.so.1 = /usr/lib/libc.so.1
On Fri, Sep 03, 2004 at 10:44:13AM -0400, Jonathan Rengifo wrote:
: nm /usr/local/apache-httpd-2.0.50/lib/libapr-0.so.0 | grep div
: [337] | 0| 0|FUNC |GLOB |0|UNDEF |.div
: [640] | 0| 0|FUNC |GLOB |0|UNDEF |.udiv
: [909] | 0| 0|NOTY |GLOB
Hi, thanks for your very important help..
I ran the ldd utility on the libapr-0.so.0 lib, with the following results:
/usr/local/apache-httpd-2.0.50/lib ldd libapr-0.so.0
libsendfile.so.1 = /usr/lib/libsendfile.so.1
librt.so.1 =/usr/lib/librt.so.1
libm.so.1 =
Hi, all...
My problem is definitive related with the libjkjni.so lib, when I add
the path of the library to the LD_LIBRARY_PATH I get the error
message:
ld.so.1: /usr/java/bin/java: fatal: relocation error: file
/usr/local/apache-httpd-2.0.50/lib/libapr-0.so.0: symbol __divdi3:
referenced symbol
Try to make a small java test (without tomcat) that use the unix sockets
and see what happens maybe you can debug it and find what/where is
happenning
Jonathan Rengifo escribió:
Hi, all...
My problem is definitive related with the libjkjni.so lib, when I add
the path of the library to the
I made the test with succesful results, I guess it is a linking
problem, but don't know how to solve it..
On Fri, 03 Sep 2004 16:18:13 -0400, John Villar
[EMAIL PROTECTED] wrote:
Try to make a small java test (without tomcat) that use the unix sockets
and see what happens maybe you can
Maybe its because of the tomcat classpath, remember it doesn't use the
system wide classpath, but its own ;-)
Jonathan Rengifo escribió:
I made the test with succesful results, I guess it is a linking
problem, but don't know how to solve it..
On Fri, 03 Sep 2004 16:18:13 -0400, John Villar
I've already setup the CATALINA_HOME and TOMCAT_HOME path variables
Any other suggestion? :'(
Regards
Jonathan
On Fri, 03 Sep 2004 16:54:36 -0400, John Villar
[EMAIL PROTECTED] wrote:
Maybe its because of the tomcat classpath, remember it doesn't use the
system wide classpath, but its
I remember an issue i was having with JNI where the Hotspot compiler and
the JVM should have a proper directory structure, it was something like
having a client and server directory could be that
however... i think your main problem is that Solaris 9 has a broken lib
that tomcat relies
I guess you are right, maybe there is a problem I can't definitive
handle, but I am worry about having this connector working via TCP
socket on production, because I guess this is not the better
configuration. Do you have experience working like this on a
production scenario?
I am very thankful
Well, maybe using TCP sockets will solve the problem, and worrying about
using TCP on a production enviroment isn't a real issue, what do you
think the vast mayority off production enviroments are using nowadays?
;-) also, if your problem is security, IPSec does the trick.
just
I am really worry about speed, we have a very accessed news server and
speed was my really problem, but if you say its ok maybe I don't have
nothing to worry about.
Thanks for your time and attention
Regards
Jonathan
On Fri, 03 Sep 2004 17:28:43 -0400, John Villar
[EMAIL PROTECTED] wrote:
Jonathan Rengifo wrote:
I made the test with succesful results, I guess it is a linking
problem, but don't know how to solve it..
On Fri, 03 Sep 2004 16:18:13 -0400, John Villar
[EMAIL PROTECTED] wrote:
Try to make a small java test (without tomcat) that use the unix sockets
and see what
I built the connector and the Apache web server by my self on the
Solaris 9 64 bit box with the source downloaded from the Apache
Project site with succeeding results, when I built the connector I got
the following files mod_jk2.so and jkjni.so and when I built the
Apache release I got the apr
Hi ...
I've install Apache2 and Tomcat5 last versions from the Apache project
web page, and they are currently well running standalone in my 64 bits
Solaris 9 Box, but now I need to connect them, so I installed the new
mod_jk2 connector, with succeeding results at the configure and make
steps,
On Thu, Sep 02, 2004 at 06:25:53PM -0400, Jonathan Rengifo wrote:
: 1-Sep-2004 1:46:26 PM org.apache.jk.common.ChannelSocket init
: INFO: JK2: ajp13 listening on /0.0.0.0:8009
: ld.so.1: /usr/java/bin/java: fatal: relocation error: file
: /usr/local/apache-httpd-2.0.50/lib/libapr-0.so.0: symbol
I ran ldd utility on mod_jk.so (compiled by me) with the following results:
/usr/local/apache/modules ldd mod_jk2.so
libc.so.1 = /usr/lib/libc.so.1
libdl.so.1 =/usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
Then I ran ...
/usr/lib nm
18 matches
Mail list logo