Re: Catalina error: out of memory

2008-07-12 Thread Kevan Miller
On Jul 12, 2008, at 9:42 AM, Peter L. Berghold wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim McConnell wrote: -Xms256m -Xmx256m Thanks for the pointer. I've implemented this suggestion thusly: JPDA_OPTS=-Xdebug -Xms256m -Xmx256m - -Xrunjdwp:transport=$JPDA_TRANSPORT,address=

Re: CGI and Geronimo/Tomcat

2008-07-12 Thread Kevan Miller
On Jul 11, 2008, at 5:14 PM, Peter L. Berghold wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey folks, I've been doing web searches looking for the answer to this and I can't find my Geronimo book wherever I put it last. I am trying enable the processing of CGI scripts on

Re: javax.jms.JMSException: Failed to build body from bytes

2008-07-12 Thread Kevan Miller
What's the structure of your app(s)? This exception indicates that you're using JMS ObjectMessages and there's a problem deserializing the message bytes into an Object. The class app.entity.QuartzJobIssued is not being found. Where is that class packaged? --kevan On Jul 11, 2008, at

Re: Stateful Session Bean Problem Geronimo 2.1.1: Passivation Failed

2008-07-12 Thread Mario Kofler
thanks for the answer, passivation is working fine now, with explicitely closing the entity manager. i got one more question, maybe you know what could be the problem.. at higher user rates i get some exception, what looks like the server cannot take more users. stateful bean pool is set to 800

Re: Multiple 'Service' in GMO 2.1 (like in Tomcat)

2008-07-12 Thread Kevan Miller
On Jul 9, 2008, at 5:59 AM, cvx22 wrote: Hi gurus, I plan to migrate my web-apps from Tomcat6 to Geronimo2.1. I have one configuration problem. In my tomcat's server.xml I have declared two Service, like that: --- part of server.xml - Service

Re: javax.jms.JMSException: Failed to build body from bytes

2008-07-12 Thread jklcom99
JMS is a separate module. app -myApp -1.0 -myApp-1.0.car -appJMS app.entity.QuartzJobIssued is packaged in myApp.jar and it is in ear/lib. Kevan Miller wrote: What's the structure of your app(s)? This exception indicates that you're using JMS ObjectMessages and