We have a production environment in which there are several remote servers which will go online next week (10 servers). We are using JMS queues to store messages to be sent to the servers when they go 'online' for updates. One server for example has over 34,000 messages in it's queue ready to be processed. In the meantime we have 3 servers with their own queues already in production. Everything was running fine for the past 2 months, until over the weekend when at 3am the JBOSS server was 'hung' and we had to restart it in the morning. At 3am we have nightly updates to be sent to the enterprise server. For some reason the nightly updates did not appear on the enterprise server. We had to resolve this issue manually. However, when we restarted the JBOSS server the message processing is again running smoothly as it has for the last 2 months. We do notice a performance degregation later in the day.
What should we look at to resolve this issue? Keep in mind that we will have 180+ servers and 180+ queues when we are fully 100% in production. The enterprise "JBOSS" server is a Pentium IV computer running Windows 2000 Server Edition with 2 gigs of memory. We changed the hsqldb-ds.xml setting for max pool size from 20 to 100 today to see if this improves the performance. Please Advise. Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843278#3843278 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843278 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
