[
https://issues.apache.org/jira/browse/QPID-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464931
]
Gordon Sim commented on QPID-245:
---------------------------------
The exception on the broker appears to be caused by the use of non-standard
field table value codes in the client properties sent by the java client as
part of the connection.start-ok method.
I will try and improve the error handling a little here (the code in question
will likely be out of date soon due to changes in io handling and also in the
move to 0.9 so I won't spend too long on that). We can of course also implement
the non-standard types in c++ as well. However as that has interoperability
implications it should be discussed further on the list.
It certainly seems wrong to use non-standard types for the client properties
(or anywhere by default) as that would make our clients incompatible with any
other implementation. Allowing applications to explicitly use non-standard
behaviour is different, particularly if they are informed that doing so will
cause their application to become dependent on qpid.
> Java client hangs with C++ broker
> ---------------------------------
>
> Key: QPID-245
> URL: https://issues.apache.org/jira/browse/QPID-245
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, Java Client
> Environment: svn revision 491076, RHEL 4 64 bit
> Reporter: Robert Greig
>
> Run a C++ broker, and any java client.
> During the connection phase the broker emits:
> ---------------0x545a80
> St9exception
> The client outputs:
> main 2007-01-03 21:26:29,477 INFO
> [qpid.client.transport.SocketTransportConnection] Attempting connection to
> localhost/127.0.0.1:5673
> AnonymousIoService-1 2007-01-03 21:26:29,738 INFO
> [qpid.client.security.CallbackHandlerRegistry] Available SASL mechanisms:
> CRAM-MD5 PLAIN
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
