tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Tulley" <JTUL...@novell.com>
Subject RE: Tomcat on Netware
Date Tue, 30 Sep 2003 19:04:03 GMT
There are a few possibilities:
1) That JVM version has some weird bug that effects Tomcat uniquely
(But, did you say the version number incorrectly; is it really 1.3.1_08,
not 1.1.3.8??).  Officially we don't support Tomcat on NetWare 5.x, but
I've seen it work there before I think.
2) There are some peculiarities that you need to get right for a JVM on
NetWare; namely the current working directory needs to be set. (NetWare
itself has no notion of this).  For this, set -envCWD=sys:/tomcat/4 
(for instance) in the startup command line.

I've attached the startup scripts we used on NetWare 6.5, where we put
Tomcat in sys:/tomcat/4 by default.  I've been meaning to get these
submitted to jakarta, but have not done so yet.  If Tomcat is not in
sys:/tomcat/4 (and the scripts in sys:/tomcat/4/bin), then you will have
to edit each of these files and adjust the paths appropriately.

Also, I hope that the perl scripts work fine on NetWare 5.1, they have
not had much testing there.

(oh, rename the scripts from the .txt ending; I added that so that they
wouldn't be stripped from the mail list).

Let me know if you have further questions and/or concerns with getting
this working.

Jeff Tulley  (jtulley@novell.com)
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

>>> pguyatt@telesoft-technologies.com 9/30/03 8:19:06 AM >>>
Hi There,

	Sorry I don't, you may have to raise a bug report for this
problem.

I am positive that it will be an easy fix so it should be solved
relatively
quickly.

Hope this is ok

Thanks

Pete

-----Original Message-----
From: Aziz Yacoub [mailto:Aziz@decastar.com.au] 
Sent: 30 September 2003 15:08
To: tomcat-user@jakarta.apache.org 
Subject: RE: Tomcat on Netware


Thanks... do you know why tomcat would be doing this on startup??

>>> "Peter Guyatt" <pguyatt@telesoft-technologies.com> 30/09/2003
11:04:36 pm >>>
Yeah,

The fact that you need to have the call to the method synchronized its
the
same as using the wait() method implemented in the Object class

you need to own the lock before you can call this method eg.

some method {
synchronized (this) {
//this is ok
wait();
}
}

where as

some method {
wait();
}

would throw an IllegalMonitorStateException.

Hope this helps

Pete

-----Original Message-----
From: Aziz Yacoub [ mailto:Aziz@decastar.com.au] 
Sent: 30 September 2003 13:51
To: >
Subject: Tomcat on Netware


I've been successfully running Tomcat 4.0.4 on Novell Netware with the

Novell (ie Netscape) Enterprise Server (using nsapi_rd.nlm) for many
months, and now I want to upgrade to Tomcat 4.1.27.

I installed and configured 4.1.27 just like 4.0.4 (ajp13, workers
etc),

and now it's giving the following error when I try to start it:

Bootstrap: Class loader creation threw exception
java.lang.IllegalMonitorStateException: current thread not owner

The log file shows:

[Tue Sep 30 22:27:31 2003] [jk_worker.c (88)]: Into wc_open
[Tue Sep 30 22:27:31 2003] [jk_worker.c (222)]: Into build_worker_map,

creating 1 workers
[Tue Sep 30 22:27:31 2003] [jk_worker.c (228)]: build_worker_map,
creating worker worker1
[Tue Sep 30 22:27:31 2003] [jk_worker.c (148)]: Into wc_create_worker
[Tue Sep 30 22:27:31 2003] [jk_worker.c (162)]: wc_create_worker,
about to create instance worker1 of ajp13
[Tue Sep 30 22:27:31 2003] [jk_ajp13_worker.c (108)]: Into
ajp13_worker_factory
[Tue Sep 30 22:27:31 2003] [jk_worker.c (171)]: wc_create_worker,
about to validate and init worker1
[Tue Sep 30 22:27:31 2003] [jk_ajp_common.c (1219)]: Into
jk_worker_t::validate
[Tue Sep 30 22:27:31 2003] [jk_ajp_common.c (1239)]: In
jk_worker_t::validate for worker worker1 contact is localhost:8009
[Tue Sep 30 22:27:31 2003] [jk_ajp_common.c (1267)]: Into
jk_worker_t::init
[Tue Sep 30 22:27:31 2003] [jk_ajp_common.c (1287)]: In
jk_worker_t::init, setting socket timeout to 0
[Tue Sep 30 22:27:31 2003] [jk_worker.c (187)]: wc_create_worker,
done
[Tue Sep 30 22:27:31 2003] [jk_worker.c (238)]: build_worker_map,
removing old worker1 worker
[Tue Sep 30 22:27:31 2003] [jk_worker.c (250)]: build_worker_map,
done
[Tue Sep 30 22:27:31 2003] [jk_worker.c (111)]: wc_open, done 1
[Tue Sep 30 22:28:28 2003] [jk_nsapi_plugin.c (298)]: jk_init, a
second passed
[Tue Sep 30 22:29:22 2003] [jk_worker.c (118)]: Into wc_close
[Tue Sep 30 22:29:22 2003] [jk_worker.c (199)]: close_workers got 1
workers to destroy
[Tue Sep 30 22:29:22 2003] [jk_worker.c (206)]: close_workers will
destroy worker worker1
[Tue Sep 30 22:29:22 2003] [jk_ajp_common.c (1324)]: Into
jk_worker_t::destroy
[Tue Sep 30 22:29:22 2003] [jk_ajp_common.c (1331)]: Into
jk_worker_t::destroy up to 1 endpoint to close
[Tue Sep 30 22:29:22 2003] [jk_worker.c (120)]: wc_close, done

The server setup is Netware 5.1 sp6, JVM 1.1.3.8, NES 5.1.

Does anyone know what would cause an IllegalMonitorStateException ???

TIA




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org 
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org 


Mime
View raw message