Has anyone found a way to use something like the above,
with Tomcat, without complex registry editing?
The JavaService found at
http://www.alexandriasc.com/software/JavaService/index.html
does all this and it comes with a batch file to install it as a Tomcat 3.2 service...
works perfectly
Hi!
My connectionURL in server.xml now looks like this:
"jdbc:mysql://localhost/auth?user=rootpassword=somepassword"
and tomcat doesn't start up (although there is no error msg or anything) and
when i execute tomcat stop i get the following exception:
org.xml.sax.SAXParseException: Next
1. I know that linux will show me a lot of processes. I
know these processes are native threads and they share the
memory. (I have more then 40 processes, each one is
consuming 70456. This means that Tomcat isn't using 40 x
70456. But all these processes are sharing the same
40456.)
So I'm tryin with JavaService
(http://www.alexandriasc.com/software/JavaService/).
I configured the Tomcat Service and it starts but it
doesn't works. If I start Tomcat in the manual mode
(and the prompt window appears) it works
fine
I used the bat examples in JavaService that help
sigh -- and now I find it -- bug number 151
(http://znutar.cortexity.com/BugRatViewer/ShowReport/151)
...
there is no action listed for this... any comments?
I would guess that this is because it's fixed in Tomcat 3.2.1 - why don't you just
upgrade to the latest stable release? :)
quote
I would guess that this is because it's fixed in Tomcat
3.2.1 - why don't you just upgrade to the latest stable
release? :)
Eeep... just noticed you _are_ using Tomcat 3.2.1 - but still, that's what Tomcat
returns when queried on port 8080:
quote
GET /Teaching/Lectures/List/lectures.tsp
When the getSession line is reached in the code it freezes
for around 9-10 seconds before returning a session, leading
the user to think theyre not going to get anything back...
That's because of the secure random number generator that's used to create the session
ID - it takes quite some
Are you using JDK1.3 ? This is a know bug of JDK1.3. Change to 1.2.2. Check the
archives for details.
Or, if you _do_ want to use JDK1.3, use the JAVA Service Wrapper found at
http://www.alexandriasc.com/software/JavaService/
It's free, and it works perfectly with JDK 1.3, i.e. no unwanted
