We are having the exact problem described in these two JIRA cases: http://jira.jboss.com/jira/browse/JBPAPP-366 http://jira.jboss.org/jira/browse/JBWEB-82
These JIRA cases suggest that we should move to JBoss Native and JBoss Web. This is simply not an option for us at this time, and we have production machines experiencing this serious problem. Are there ANY other workarounds or suggestions that may help us to avoid this problem until we can start to implement JBoss Web on our QA / DEV servers and eventually roll it to production? I'm concerned that we haven't seen more of this problem given the installed base-- can anyone help? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117191#4117191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117191 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
