It may be taking a while for the broker.stop() to complete. If you try and
restart the broker before the transport connector from the previous broker
instance has been fully shutdown, that might explain the bind exception (as
the socket is already in use).
HTH
/Dave
On Tue, Jun 17, 2008 at 1:23 P
the meaning of a BindException is clear to me.
What baffles me is that the consumers were able to receive messages after
the broker was restarted, and then all of a sudden I get this BindException.
So WHO (or should I say "WHAT") could have taken those ports from the
broker?
Moreover this, from
On Sat, Jun 14, 2008 at 3:18 PM, drjava <[EMAIL PROTECTED]> wrote:
>
> I'm sorry...Trying again.
> http://www.nabble.com/file/p17843946/spring-config.xml spring-config.xml
> http://www.nabble.com/file/p17843946/BindException.txt BindException.txt
> http://www.nabble.com/file/p17843946/JmsLogMesseng
I'm sorry...Trying again.
http://www.nabble.com/file/p17843946/spring-config.xml spring-config.xml
http://www.nabble.com/file/p17843946/BindException.txt BindException.txt
http://www.nabble.com/file/p17843946/JmsLogMessengerTest.java
JmsLogMessengerTest.java
rajdavies wrote:
>
> I couldn't ac
I couldn't actually read the attached file - can you attach again
without the formatting ?
On 13 Jun 2008, at 22:30, drjava wrote:
I am (still) in the process of testing a JmsMessenger class called
JmsLogMessenger. One of my test cases scenario is as follows:
* start the JMS broker (Active
