Hi,
the problem was in changed StompConnection API, as now the connect() method
do all the checks. It's fixed on the trunk, and you can also fix it in your
distro by removing
StompFrame connect = connection.receive();
if (!connect.getAction().equals(Stomp.Responses.CONNECTED)) {
throw new Exception ("Not connected");
}
from the example/src/StompExample.java
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Apr 8, 2010 at 9:17 PM, jmarks <[email protected]> wrote:
>
> I tried running StompExample after starting ActiveMQ using the following
> command line from Windows:
>
> bin\activemq.bat xbean:conf/activemq-stomp.xml
>
> ActiveMQ then indicated that it had started the two stomp connectors. When
> I
> tried to run the example, I got the following stack trace:
>
> Exception in thread "main" java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.net.SocketInputStream.read(SocketInputStream.java:182)
> at java.io.DataInputStream.readByte(DataInputStream.java:248)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:186)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:94)
> at
>
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:68)
> at
>
> org.apache.activemq.transport.stomp.StompConnection.receive(StompConnection.java:60)
> at StompExample.main(StompExample.java:36)
>
> Line 36 is where the example attempts to receive a frame after calling
> StompFrame.connect().
> --
> View this message in context:
> http://old.nabble.com/StompExample-not-working--tp28183353p28183353.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
