Atreya,
Thank you for your help! Good to know someone else had the same problem,
gives me hope that I'll get it running.
I start tomcat by opening a command prompt, cd to \tomcat\bin, and
issuing the startup command. Like so:
C:\tomact\bin>startup
Using CATALINA_BASE: c:\tomcat
Using CATALINA_HOME: c:\tomcat
Using CATALINA_TMPDIR: c:\tomcat\temp
Using JAVA_HOME: C:\java
Then it opens a new console window, which comes up with the messages I
stated in my last email. I then usually open up
http://localhost/examples to see if by chance it might be working!
Thanks again,
Tristan
(jk2.properties and workers2.properties files attached below)
--- start jk2.properties ---
#Shared memory directive
shm.file=c:/Apache2/logs/jk2.shm
size=10485760
# Set the desired handler list
handler.list=apr,request,channelJni
# added to resolve 1st issue in original email
apr.NativeSo=c:/Apache2/modules/jkjni.dll
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
apr.jniModeSo=inprocess
--- end jk2.properties ---
--- start workers2.properties ---
[shm]
file=c:/Apache2/logs/jk2.shm
size=10485760
# Define the comunication channel
[channel.jni:jni]
info=The jni channel, used if tomcat is started inprocess
[config:]
file=c:/Apache2/conf/workers2.properties
debug=0
debugEnv=0
# Define the parameters for the Java Virtual Machine
[vm:]
info=Parameters used to load a JVM in the server process
OPT=-Djava.class.path=c:/tomcat/lib
OPT=-Dtomcat.home=c:/tomcat
OPT=-Dcatalina.home=c:/tomcat
OPT=-Xmx128M
# JNI worker startup handler
[worker.jni:onStartup]
info=Command to be executed by the VM on startup. This one will start
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=start
stdout=c:/Apache2/logs/stdout.log
stderr=c:/Apache2/logs/stderr.log
# JNI worker shutdown handler
[worker.jni:onShutdown]
info=Command to be executed by the VM on shutdown. This one will stop
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=stop
# Uri mapping
[uri:/examples]
info=Example webapp in the default context.
context=/examples
[uri:/examples/*]
info=Map the whole webapp
[status:]
info=Status worker, displays runtime information
channel=channel.socket:localhost:8009
[uri:/status/*]
worker=status:localhost:8009
group=status:
--- end workers2.properties ---
-----Original Message-----
From: Atreya Basu [mailto:[EMAIL PROTECTED]
Sent: 18 July 2003 15:59
To: 'Tomcat Users List'
Subject: RE: Apache2 / Tomcat4-1 / mod_jk2.dll / XP setup issues
Tricky,
I got this problem a while ago. I think it has something to do with how
you are starting tomcat. How are you starting it? What are the
contents of your workers2.properties and jk2.properties files?
Atreya
_____________________________________
Atreya Basu
Developer,
Greenfield Research Inc.
e-mail: atreya (at) greenfieldresearch (dot) ca
-----Original Message-----
From: Tricky [mailto:[EMAIL PROTECTED]
Sent: July 18, 2003 11:36 AM
To: [EMAIL PROTECTED]
Subject: Apache2 / Tomcat4-1 / mod_jk2.dll / XP setup issues
Hi,
I emailed yesterday with my problems, I since followed the tutorial
provided very kindly by one of the respondents, but still no joy :(
So, what I'm trying to do is to get tomcat running as an apache process.
Tomcat appears to be sulking about this idea, and just won't have any of
it. Its perfectly happy running standalone if I uncomment the non-SSL
Coyote HTTP/1.1 Connector on port 8080 part of server.xml, but it seems
to take issue with the Coyote/JK2 AJP 1.3 Connector on port 8009.
If I run it as is from command prompt, without any of my further
attempts to fix it, I receive a 500 error in the browser. I noticed this
line in the Tomcat loading information:
INFO: APR not loaded, disabling jni components:
java.io.IOException: no jkjni in java.library.path
I found a jkjni.dll in the nightly jk2 builds folder, so thought I'd try
and see if a 'apr.NativeSo=c:/Apache2/modules/jkjni.dll' in the
jk2.properties line would smooth things over...
...it seemed to do something, as now when tomcat started it presented me
with a dialog box 'java.exe - Unable to Locate Component' with the
message 'This application has failed to start because libapr.dll was not
found. Re-installing the application might solve this problem' - I wish!
Anyway, I noticed this DLL was also in the jk2 nightly builds, so
dropped a copy in the tomcat/bin directory...
...but no. Tomcat now informs me of more problems :( such as:
[Fri Jul 18 15:24:25 2003] (error ) [jk_config_file.c (279)]
config.update(): Can't find config file
${serverRoot}/conf/workers2.properties
[Fri Jul 18 15:24:25 2003] (info ) [jk_config.c (246)]
config.setAttribute(): Error setting config: file
${serverRoot}/conf/workers2.properties
[Fri Jul 18 15:24:25 2003] (info ) [jk_logger_file.c (177)] Initializing
lof file stderr
[Fri Jul 18 15:24:25 2003] (error ) [jk_shm.c (333)] shm.init(): No file
[Fri Jul 18 15:24:25 2003] (info ) [jk_workerEnv.c (403)]
workerEnv.init() ok ${serverRoot}/conf/workers2.properties
and still throws the same 500 error in the browser (I wasn't entirely
surprised though, its been showing me that page for 3 long days now!!).
I even set a serverRoot in system properties (didn't work)...
So, can anyone shed some light? I'd really appreciate some guidance.
Thank you very much in advance.
Tristan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
