Is your datasource connection pool in JBoss configured to attempt to establish more connections than what your mysql DB is willing to give?
(ie. IIRC for instance PostgreSQL default max number of connections was 30 and JBoss Datasource pools were configured by default to 50).
Although if you're the only one browsing the site you shouldn't be able to reach even a small limit (unless you've got a resource leakage somewhere).
Thanks for your reply.
Changing the default datasource to use the MySql datasource instead of the default HSQL datasource seems to have solved the socket exception problem.
But, I still have the problem of failed http connections. I have never experienced this under standalone Tomcat.
When I run JBoss, webpages coming through port 80 fail to load or load incompletely (almost like the port is being intermitently blocked)
Any ideas there?
i searched a lot but havenot found anything useful on this.
on starting jboss 4.2.0.CR2 i get warnings UDP failed to join ... on lo: java.net.SocketException: No buffer space available.
my hibernate with distributed ehcache used to work on jboss 4.0.5 but now on 4.2.0.CR2 i get this - Error doing removeAll to remote peer. Message was java.net.ConnectException: Connection refused to host: 127.0.01. i think this problem is probly related to above problem.