Hi Kevin, > Work's been crazed lately so I haven't had a lot of time to spend on qpid, > but I have a patch to implement listening on both styles of sockets. > java/broker/etc/config.xml contains the updated config needed to get this > working. In a nutshell you'll need to add a <sslOnly>(true | > false)</sslOnly> tag to the <ssl> config block. The value defaults to true > so as to get sane behavior in normal use but it can be overridden by > setting it false.
Many thanks for the patch. I was able to get the server to listen on both ports, but it does appear like the interpretation of the value for the <ssl><enabled/> element got reversed: SSL only appears to get enabled if a set it to false! That said, even when I got the broker to listen on both ports, non-ssl connections worked fine, but SSL connections didn't work: 2007-02-19 20:02:39,365 INFO [main] server.Main (Main.java:337) - Qpid.AMQP listening on non-SSL address 0.0.0.0/0.0.0.0:5672 2007-02-19 20:02:39,375 INFO [main] server.Main (Main.java:347) - Qpid.AMQP listening on SSL port 8672 2007-02-19 20:03:39,131 INFO [SocketAcceptor-0] pool.PoolingFilter (PoolingFilter.java:181) - Init called on PoolingFilter AsynchronousReadFilter 2007-02-19 20:03:39,131 INFO [SocketAcceptor-0] pool.PoolingFilter (PoolingFilter.java:181) - Init called on PoolingFilter AsynchronousWriteFilter 2007-02-19 20:03:39,491 INFO [SocketAcceptorIoProcessor-0.0] protocol.AMQPFastProtocolHandler (AMQPFastProtocolHandler.java:85) - Protocol session created 2007-02-19 20:03:39,501 INFO [SocketAcceptorIoProcessor-0.0] protocol.AMQPFastProtocolHandler (AMQPFastProtocolHandler.java:130) - Session opened 2007-02-19 20:03:39,922 ERROR [pool-2-thread-1] protocol.AMQPFastProtocolHandler (AMQPFastProtocolHandler.java:190) - Exception caught inAMQProtocolSession(/127.0.0.1:4007), closing session explictly: org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.qpid.framing.AMQProtocolHeaderException: Invalid protocol header - read ▬♥☺ (Hexdump: 3D 01 00 00 39 03 01 45 DA 48 EB 7E A2 46 8D C7 4A 4A B4 15 54 83 6A 6B 96 36 B1 CE 67 10 CC 37 5A BC 05 E7 1A BE A6 00 00 12 00 35 00 2F 00 05 00 04 00 0A 00 09 00 03 00 06 00 08 01 00) So it would appear like the server is indeed listening on the SSL port but with a without the SSL filter. Update: Actually scratch that; even when only listening on the SSL port it doesn't work, so it might be something else happening here. Might it be the inversed ssl/enabled flag? Thanks, Tomas Restrepo [EMAIL PROTECTED] http://www.winterdom.com/weblog/
