Your jndi.properties for the client needs to specify
the host running JBoss, otherwise it will try to connect
to your local machine.
JBoss isn't on that machine => Connection Refused.
I sometimes used to receive messages as i/o error occured while trying to read from socked and socketexception.
What could be the reason for that.
Is it because of some db problem or some properties or parameter setting in jboss.
Which operating system are you using.
I've seen connection refused on Win2K and XP when
you try to make too many connections too quickly.
The windows ip stack thinks you are doing a denial
of service attack.
This is very annoying when trying to stress test an
I have an Win NT workstation, on which i have installed Jboss2.4.3 and tomcat3.2.3. Once in a while i get this problem. If i give a gap of sometime and start the server it works fine. There are times when it never gets connected, even after idle time.
Well, I have a doubt in this regard - is there any means of finding in the jboss 3.0.7 server side and not in the Oracle 8 database server side,
how many connections are there in the pool,
how many connections are in use and
how many connections are being returned at a given point of time?