AW: Solaris JVM never seems to garbage collect, runs out eventually.
Answer to both questions: I don't know. Haven't looked much at jikes. In the past there was a big difference, sun's licence didn't allow to redistribute a jdk (just a jre which has no compiler). So people who wanted to distribute JSP's applications without precompiled pages used jikes. But several month ago sun changed the license, so it its possible to include tools.jar (which includes javac) in a distribution. Since then the volume of jikes related questions in this list went down. -Ursprüngliche Nachricht- Von: August Detlefsen [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 7. Juni 2002 22:19 An: Tomcat Users List Betreff: Re: Solaris JVM never seems to garbage collect, runs out eventually. snip/ Will jikes work with JDK 1.4? Are there any other benefits to using jikes besides the memory leak issue? snip/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Solaris JVM never seems to garbage collect, runs out eventually.
Rick Fincher wrote: The javac in J2SE 1.4 has the memory leak 1.1.1 works OK under Solaris. - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] - First make shure that you don't have memory leaks on your own. - Make shure that you store as few data in sessions as possible. Remember that the sessions stay around for 30 minutes after the last action in the action. (30 minutes is the default for the session timeout). This way the number of concurrent sessions can be much higher than the number of active sessions. If you get 1 user per minute and each stays for one minute you will have 30 concurrent session, but only 1 active session. - The only memory leak that I know in this environment is the java compiler of the JDK. It has been reported that in some versions of the JDK javac has a memory leak. So each time tomcat compiles a page you will lose some memory. There are two solutions to this problem: - Use only precompiled JSP's (jspc) - Use another compiler (jikes) (Don't know if it's available for solaris) - I have read that some VM versions have trouble to invoke the gc if there isn't any available memory. It was suggested to issue a System.gc() if your free memory is below a watermark. I didn't investigate this further. - Use OptimizeIT to find out where the leaks are. -Ursprüngliche Nachricht- Von: David Hladky [mailto:[EMAIL PROTECTED]] snip/ Could someone with experience tuning Solaris JVMs give me and my friends a hint or two on how to force the JVM to garbage collect/tune. Or is this just a memory leak in Tomcat and or JBOSS? snip/ Thanks for the hints, We've torn our code apart with OptimizeIt and found out that it really isn't the problem. I think you are on to something about the jsp precompiled thing though. Thanks again. I'll try a few of the other things you've mentioned. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Solaris JVM never seems to garbage collect, runs out eventually.
Rick Fincher wrote: The javac in J2SE 1.4 has the memory leak 1.1.1 works OK under Solaris. Sorry, that should have been JVM 1.3.1 works OK under Solaris. Rick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Solaris JVM never seems to garbage collect, runs out eventually.
Ralph, you mention using jikes as a possible alternative... Will jikes work with JDK 1.4? Are there any other benefits to using jikes besides the memory leak issue? -August --- Dave Hladky [EMAIL PROTECTED] wrote: Rick Fincher wrote: The javac in J2SE 1.4 has the memory leak 1.1.1 works OK under Solaris. - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] - First make shure that you don't have memory leaks on your own. - Make shure that you store as few data in sessions as possible. Remember that the sessions stay around for 30 minutes after the last action in the action. (30 minutes is the default for the session timeout). This way the number of concurrent sessions can be much higher than the number of active sessions. If you get 1 user per minute and each stays for one minute you will have 30 concurrent session, but only 1 active session. - The only memory leak that I know in this environment is the java compiler of the JDK. It has been reported that in some versions of the JDK javac has a memory leak. So each time tomcat compiles a page you will lose some memory. There are two solutions to this problem: - Use only precompiled JSP's (jspc) - Use another compiler (jikes) (Don't know if it's available for solaris) - I have read that some VM versions have trouble to invoke the gc if there isn't any available memory. It was suggested to issue a System.gc() if your free memory is below a watermark. I didn't investigate this further. - Use OptimizeIT to find out where the leaks are. -Ursprüngliche Nachricht- Von: David Hladky [mailto:[EMAIL PROTECTED]] snip/ Could someone with experience tuning Solaris JVMs give me and my friends a hint or two on how to force the JVM to garbage collect/tune. Or is this just a memory leak in Tomcat and or JBOSS? snip/ Thanks for the hints, We've torn our code apart with OptimizeIt and found out that it really isn't the problem. I think you are on to something about the jsp precompiled thing though. Thanks again. I'll try a few of the other things you've mentioned. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Solaris JVM never seems to garbage collect, runs out eventually.
This may be a bit beyond the scope here but, We are running a J2EE system with Jakarta/Tomcat 3.2.1 and JBOSS 2.2 on Solaris. It uses the AJP13 connection protocol to connect to an Apache webserver and is load balanced between two J2EE servers. What seems to happen is that after a period of time running it continually ramps up the amount of memory used and never seems to return it. We are giving Tomcat 256MB of memory to start out with and 128MB to JBOSS. The machine itself has 512MB. After about 3 days or so of heavy use the system will run out of memory and Solaris will orphan the offending process. We have very little experience tuning Solaris JVM's. I use SGI myself so I am a little preplexed by this one. Could someone with experience tuning Solaris JVMs give me and my friends a hint or two on how to force the JVM to garbage collect/tune. Or is this just a memory leak in Tomcat and or JBOSS? Thanks Dave Hladky -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: Solaris JVM never seems to garbage collect, runs out eventually.
- First make shure that you don't have memory leaks on your own. - Make shure that you store as few data in sessions as possible. Remember that the sessions stay around for 30 minutes after the last action in the action. (30 minutes is the default for the session timeout). This way the number of concurrent sessions can be much higher than the number of active sessions. If you get 1 user per minute and each stays for one minute you will have 30 concurrent session, but only 1 active session. - The only memory leak that I know in this environment is the java compiler of the JDK. It has been reported that in some versions of the JDK javac has a memory leak. So each time tomcat compiles a page you will lose some memory. There are two solutions to this problem: - Use only precompiled JSP's (jspc) - Use another compiler (jikes) (Don't know if it's available for solaris) - I have read that some VM versions have trouble to invoke the gc if there isn't any available memory. It was suggested to issue a System.gc() if your free memory is below a watermark. I didn't investigate this further. - Use OptimizeIT to find out where the leaks are. -Ursprüngliche Nachricht- Von: David Hladky [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 4. Juni 2002 17:56 An: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Solaris JVM never seems to garbage collect, runs out eventually. snip/ Could someone with experience tuning Solaris JVMs give me and my friends a hint or two on how to force the JVM to garbage collect/tune. Or is this just a memory leak in Tomcat and or JBOSS? snip/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Solaris JVM never seems to garbage collect, runs out eventually.
The javac in J2SE 1.4 has the memory leak 1.1.1 works OK under Solaris. - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] - First make shure that you don't have memory leaks on your own. - Make shure that you store as few data in sessions as possible. Remember that the sessions stay around for 30 minutes after the last action in the action. (30 minutes is the default for the session timeout). This way the number of concurrent sessions can be much higher than the number of active sessions. If you get 1 user per minute and each stays for one minute you will have 30 concurrent session, but only 1 active session. - The only memory leak that I know in this environment is the java compiler of the JDK. It has been reported that in some versions of the JDK javac has a memory leak. So each time tomcat compiles a page you will lose some memory. There are two solutions to this problem: - Use only precompiled JSP's (jspc) - Use another compiler (jikes) (Don't know if it's available for solaris) - I have read that some VM versions have trouble to invoke the gc if there isn't any available memory. It was suggested to issue a System.gc() if your free memory is below a watermark. I didn't investigate this further. - Use OptimizeIT to find out where the leaks are. -Ursprüngliche Nachricht- Von: David Hladky [mailto:[EMAIL PROTECTED]] snip/ Could someone with experience tuning Solaris JVMs give me and my friends a hint or two on how to force the JVM to garbage collect/tune. Or is this just a memory leak in Tomcat and or JBOSS? snip/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
