.peter
Felipe Oliveira wrote:
hi peter,
i run jboss in the same exactly environment, but i don't seem to be running into these problems.
we found the ibm jvm to be the best for our scenario...maybe you should take a look at it.
felipe
Peter Luttrell wrote:
We're using JBoss3.2.1 with Jetty on RedHat 9 with Suns 1.4.2_01 vm. We have a pretty heavy load.
After roughly a week many of the boxes start to experience weird problems where JBoss is unable to get what looks to be socket connections. In some cases, we cannot contact our mailserver, in other cases we cannot contact our database; in the latest case we're unable to get a connection to the local jndi server (localhost:1099). Sometimes a simple restart of jboss will sometimes solves the problems, othertimes we have to restart linux. The times of the crashes are roughly 4am and sometimes 6am, so it's likely caused by a cron job running at those times, which we're currently looking into. Has anyone experienced similar problems?
.peter
----------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you.
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
---------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you.
