[
https://issues.apache.org/jira/browse/QPIDJMS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-272:
-----------------------------------
Description:
The client (and underlying it, proton-j) doesnt currently handle this scenario
well, say for example attempting to connect to a server not using a SASL layer
when it expects SASL be used, or not using AMQP at all. It should notice the
issue and fail-fast, but can await the connection process to timeout instead.
Depends on PROTON-1426 + PROTON-1427, and in turn QPIDJMS-270 to get them.
was:
The client (and underlying it, proton-j) doesnt currently handle this scenario
well, say for example attempting to connect to a server not using a SASL layer
when it expects SASL be used, or not using AMQP at all. It should notice the
issue and fail-fast, but typically awaits the process to timeout instead.
Depends on PROTON-1426 + PROTON-1427, and in turn QPIDJMS-270 to get them.
> fail fast when attempting connection to a server using unexpected protocol
> type
> -------------------------------------------------------------------------------
>
> Key: QPIDJMS-272
> URL: https://issues.apache.org/jira/browse/QPIDJMS-272
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.20.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.21.0
>
>
> The client (and underlying it, proton-j) doesnt currently handle this
> scenario well, say for example attempting to connect to a server not using a
> SASL layer when it expects SASL be used, or not using AMQP at all. It should
> notice the issue and fail-fast, but can await the connection process to
> timeout instead.
> Depends on PROTON-1426 + PROTON-1427, and in turn QPIDJMS-270 to get them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
