Tomcat reboot runtime PS...

[Adam Buglass]

I'm leaving work now so I'm gonna have to leave this thread for a while
but I'll definitely check up on it again when I get in tomorrow morning.

If I get a chance soon I'll have a go at whipping something up.

I may be barking up completely the wrong tree and if I write something
of course it may well just crash  burn, but I'm intrigued and anyway it
would keep me out of mischief!!

Regards,
Adam.

-- 

Adam Buglass,  
The Golden Freeway,
Department of Child Health,
University of Newcastle-upon-Tyne.
Royal Victoria Infirmary.

(0191) 2023062

Democracy is two wolves and a lamb voting on what to have for lunch.
Liberty is a well-armed lamb contesting the vote. 
~Benjamin Franklin, 1759


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: reclaiming memory problem PS

[Christopher Schultz]

Jerald (or is it Gerald -- your email address and 'name' don't match),

Now sessionStatus is getting caught  fine, but when I try and
redirect to a JSP after that, nothing happens. I originally tried
mapping.findForward (Struts), response.sendRedirect and forwarding
using RequestDispatcher. I have tried getSession(true) and false.
What implications (if any) does session timeout have in terms of
forwarding after the session is invalidated?
Session state should have nothing to do with your ability to forward, etc.

Can you post thesnippet of code where you try to redirect the user?

-chris



signature.asc
Description: OpenPGP digital signature

Re: reclaiming memory problem PS

[Jerald Powel]

Hi, 

 It’s Gerald (long dull story), but you can call me anything you like.

 

I can now say with some surety, that the forward is not the problem. In a Struts 
action, the null session is being picked up and the mapping.findForward(“a_file.jsp”); 
(a Struts forward method) is forwarding on to the specified resource. 

Great you’d think. But no. It seems to forward to the specified resource 
(execution is being logged, System.out.println(“some text”); is written to the console 
etc), but in the client, nothing happens, regardless of which method is used to 
forward. Just the broken original app remains. I have forwarded to a simple JSP, which 
again logs that it’s being executed. But again nothing is loaded in to the browser. 

Do you have any ideas, as I am fast running out of them.

I will consult the Struts list, but am yet unsure it is a Struts 
issue/question.

 

Many thanks

 

Gerald. 
Jerald (or is it Gerald -- your email address and 'name' don't match),

 Now sessionStatus is getting caught – fine, but when I try and
 redirect to a JSP after that, nothing happens. I originally tried
 mapping.findForward (Struts), response.sendRedirect and forwarding
 using RequestDispatcher. I have tried getSession(true) and false.
 What implications (if any) does session timeout have in terms of
 forwarding after the session is invalidated?

Session state should have nothing to do with your ability to forward, etc.

Can you post thesnippet of code where you try to redirect the user?

-chris



 ATTACHMENT part 2 application/pgp-signature name=signature.asc



-
  Yahoo! Messenger - Communicate instantly...Ping your friends today! Download 
Messenger Now

Re: reclaiming memory problem PS

[Christopher Schultz]

Jerald,

 session.setMaxInactiveTimeout(-1);

Yeah, this is a bad idea. The session will never go away by itself. This 
*requires* the user to press a logout button, and for you to explicitly 
call session.invalidate(). Users frequently do not log themselves out, 
and their sessions will never die. You will eventually run out of memory.

If you need a long timeout, just make it really long (like a couple of 
hours). There's usually no good reason to make it -1.

PS is the session time out linked wirth inactivity? My session
attribute only persists as long as I am using the app.
That's exactly how the 'inactive' timeout works.

-chris



signature.asc
Description: OpenPGP digital signature

Re: reclaiming memory problem PS

[Jerald Powel]

Hello, and thank you for that,

Yes, I am timing the session out and trying to handle the result. I have: 

 

HttpSession objSession = request.getSession(true);

String sessionStatus = (String) objSession.getAttribute(sessionStatus);



if (sessionStatus == null) {

 

forward off to JSP

 

}

 

Now sessionStatus is getting caught – fine, but when I try and redirect to a JSP after 
that, nothing happens. I originally tried mapping.findForward (Struts), 
response.sendRedirect and forwarding using RequestDispatcher. I have tried 
getSession(true) and false. What implications (if any) does session timeout have in 
terms of forwarding after the session is invalidated? 

 

Many thanks

 

G.


   

 

Jerald,

 session.setMaxInactiveTimeout(-1);

Yeah, this is a bad idea. The session will never go away by itself. This 
*requires* the user to press a logout button, and for you to explicitly 
call session.invalidate(). Users frequently do not log themselves out, 
and their sessions will never die. You will eventually run out of memory.

If you need a long timeout, just make it really long (like a couple of 
hours). There's usually no good reason to make it -1.

 PS is the session time out linked wirth inactivity? My session
 attribute only persists as long as I am using the app.

That's exactly how the 'inactive' timeout works.

-chris



 ATTACHMENT part 2 application/pgp-signature name=signature.asc





-
  Yahoo! Messenger - Communicate instantly...Ping your friends today! Download 
Messenger Now

Re: reclaiming memory problem PS

[Jerald Powel]

PS is the session time out linked wirth inactivity? My session attribute only persists 
as long as I am using the app.

G.


-
  Yahoo! Messenger - Communicate instantly...Ping your friends today! Download 
Messenger Now

Questions about tomcat as ps -ef

[Randy Paries]

Hello,

I am running tomcat jakarta-tomcat-4.0.4 and apache apache-1.3.27-2

My question is about all the tomcat processes/threads. It seems they
never seem to go a way.

I had to increase my maxProcessors=150 , because I was running out of
connections between apache and tomcat.

It seems that when I do a ps -ef | grep java | wc -l , that after a
restart then number starts at my minProcessors count. But during the day
the count continues to increase. 

My question is that the count never decreases. IS this normal? 

Thanks
Randy



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Re: XML parser PS

[Paul_Wallace]

I have downloaded the Xerces.ZIP (which incidentally is 4.8 MB - expanded 
to 22!), extracted it to webapps/ROOT/WEB-INF/lib/

I extrcated the xerxesImp1.jar to that location.

Paul.

ps!

[Marcella MacDougall]

And I forgot to mention that I keep getting a warning that the HTTP server
could not start.  I'm still using port 8080...

thanks,
Marcy


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Is something wrong with the Catalina 4.0.1 distribution? (PS)

[raj]

  Looking at jasper-compiler.jar I notice that the class 
TldLocationsCache is in the package
  org.apache.jasper.compiler
  and not
  org.apache.jasper.compiler.TldLocationsCache.processJars
  as it seems to be looking for from the above exceptions.

Sorry the above should have said:

There seems to be no file TldLocationsCache.processJars (or 
TldLocationsCache$processJars .class)
in the jasper-compiler.jar file


Cheers
-raj

Re: Tomcat process management using ps

[Craig R. McClanahan]

Mark Koscak wrote:

Hello everyone,I
am running Jakarta-Tomcat 3.2When I have a look
at my system processes (ps -aux) after starting tomcat, there are eighteen
(18) separate process id's the associated command being /usr/locak/jdk1.3
Each process apparently consuming 15.4% of memory. 18 * 15.4% = 277.2%How
can this be?Also (ok I'm being lazy on this
one) when starting tomcat can I prune the instances of the command /usr/local/jdk1.3
to say 8-10 instead of having 18.Thanks for
any input.RegardsMark
The Linux "ps" command lies to you. It makes individual threads look
like they are separate processes. There is only one process (assuming
you started only one), all sharing the same memory.
Craig McClanahan

Re: Tomcat process management using ps (Thanks)

[Mark Koscak]

Hi Craig,

Thanks for the info.

I had a hunch something like this was happening, it's nice to 
get some feedback that I can take to my boss supporting my 
argument.

Cheers
Mark Koscak

  - Original Message - 
  From: 
  Craig R. McClanahan 
  To: [EMAIL PROTECTED] 
  Sent: Tuesday, January 09, 2001 10:58 
  AM
  Subject: Re: Tomcat process management 
  using ps
  Mark Koscak wrote: 
  

Hello everyone,I am running 
Jakarta-Tomcat 3.2When I have a look at my system 
processes (ps -aux) after starting tomcat, there are eighteen (18) separate 
process id's the associated command being /usr/locak/jdk1.3 Each 
process apparently consuming 15.4% of memory. 18 * 15.4% = 
277.2%How can this be?Also (ok I'm being lazy on this one) when starting tomcat can I 
prune the instances of the command /usr/local/jdk1.3 to say 8-10 instead of 
having 18.Thanks for any input.RegardsMarkThe Linux "ps" 
  command lies to you. It makes individual threads look like they are 
  separate processes. There is only one process (assuming you started only 
  one), all sharing the same memory. 
  Craig McClanahan