On 09/04/2013 09:50 PM, Jonathan Albrecht wrote:
I'm trying to run the new Java send/recv example in proton 0.5 with the qpid 
java broker 0.22.

I have the broker running on localhost and I've added a queue named test to the 
default virtualhost through the web config. When I try to run the Send or Recv 
class with a:

-a amqp://localhost/test

Argument to point them at the broker, I get a steady stream of the following 
exception:

Sep 04, 2013 4:21:06 PM org.apache.qpid.proton.messenger.impl.MessengerImpl 
processActive
SEVERE: Error processing connection
java.io.IOException: An established connection was aborted by the software in 
your host machine
                 at sun.nio.ch.SocketDispatcher.read0(Native Method)
                 at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                 at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                 at sun.nio.ch.IOUtil.read(Unknown Source)
                 at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                 at 
org.apache.qpid.proton.driver.impl.ConnectorImpl.read(ConnectorImpl.java:127)
                 at 
org.apache.qpid.proton.driver.impl.ConnectorImpl.process(ConnectorImpl.java:93)
                 at 
org.apache.qpid.proton.messenger.impl.MessengerImpl.processActive(MessengerImpl.java:502)
                 at 
org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:617)
                 at 
org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:585)
                 at 
org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:254)
                 at 
org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:259)
                 at org.apache.qpid.proton.example.Recv.run(Recv.java:108)
                 at org.apache.qpid.proton.example.Recv.main(Recv.java:127)

The brokerless configuration works fine. Nothing shows up in the broker logs as 
far as connections go.

I can't see what I'm doing wrong. Any ideas?

The proton messenger client only supports ANONYMOUS authentication at the moment and by default I believe that is turned off on the java broker.

http://qpid.apache.org/releases/qpid-0.22/java-broker/book/Java-Broker-Security.html#Java-Broker-Security-Authentication-Providers has some instructions for adding providers. Does that fix it?


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to