Already fixed in http://jira.jboss.com/jira/browse/JBAS-3107
It's due to running out of sockets, not CPU starvation as I thought.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4026259#4026259
Reply to the post :
I'm unsure where to post this, but as this issue manifested itself whilst
stress loading a Resource Adapter I though I'd post it here.
As anyone ever witnessed the spontaneous undeployment of farmed applications
(in a JBoss cluster) when an application is under stress?
We're managing this feat
I finally got access to the test server logs, and found these lines
particularly interesting:
| (ScannerThread) WARN [FileURLLister] Could not list directory
'/jboss/server/default/farm', reason unknown
| (ScannerThread) WARN [FileURLLister] Could not list directory
Having written the UDP RA, is it possible to get any loadbalancing out of
running it in a JBoss cluster?
After reading http://www.jboss.com/index.html?module=bbop=viewtopict=86104 it
looks like not, but I'd like to double check.
In my case the RAs don't need to share any data, they are 100%
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995534#3995534
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995534
___
jboss-user mailing list
jboss-user@lists.jboss.org
Hi all.
I'm about to implement a Resource Adaptor to act as a UDP interface between an
EIS and a J2EE application.
The EIS currently broadcasts UDP packets requesting a service and expects UDP
packets with the responses. It is an asynchronous system.
Outside a JBoss environment I would
