[jira] [Updated] (DISPATCH-1860) QPID connection failure for apache broker
[
https://issues.apache.org/jira/browse/DISPATCH-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mahendra anil sonawale updated DISPATCH-1860:
-
Affects Version/s: (was: 1.12.0)
> QPID connection failure for apache broker
> -
>
> Key: DISPATCH-1860
> URL: https://issues.apache.org/jira/browse/DISPATCH-1860
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Protocol Adaptors, Routing Engine
>Affects Versions: 1.14.0
>Reporter: mahendra anil sonawale
>Priority: Major
> Attachments: qd_config_chunk.config
>
>
> Hello Team,
>
> We have installed Apache qpid in cluster and have master-slave brokers as a
> connectors.
> All connecting via AMQP protocol.
> 2020-11-30 09:55:53.916195 -0500 SERVER (info) [C288454] Connection to
> activemq-preprod-master2a.abcd:61618 failed: amqp:connection:framing-error
> Expected AMQP protocol header: no protocol header found (connection aborted)
> We are seeing below exception: could you please help us with the resolution.
> PFA the qpid config chunk.
>
> And below one is configuration in broker.xml.
>
> name="artemis">tcp://activemq-preprod-master2a.abcd.com:61618?protocols=AMQP,CORE,OPENWIRE;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true;sslEnabled=true;keyStorePath=${SSL_KEYSTORE_PATH};keyStorePassword=${SSL_KEYSTORE_PASSWORD};enabledProtocols=${TLS_VERSION};amqpCredits=1000;amqpLowCredits=300
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241652#comment-17241652
]
Andrew Stitcher commented on PROTON-2231:
-
This piece of code is keeping track of the total number of proactor
connections/listeners etc. open so that the proactor can generate an idle event
when there are none left.
So I think it is likely that it should probably not be executing for a close of
a connection that is already closed.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-521) ExceptionListener fired due to async dispatch failure is unable to close the Session/Connection
[ https://issues.apache.org/jira/browse/QPIDJMS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-521. Resolution: Fixed > ExceptionListener fired due to async dispatch failure is unable to close the > Session/Connection > --- > > Key: QPIDJMS-521 > URL: https://issues.apache.org/jira/browse/QPIDJMS-521 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Affects Versions: 0.55.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 0.56.0 > > > **When an unexpected failure occurs during the process of dispatching a > message to an asynchronous consumer (i.e the work surrounding, but not > including, onMessage), the connection ExceptionListener is fired as a result. > If the ExceptionListener attempts to close the consumers containing Session > or Connection it will currently fail with an javax.jms.IllegalStateException > noting an "Illegal invocation from MessageListener callback". > This happens because the session async dispatch thread is ordinarily not > allowed to call these methods, is in keeping with the impl and their API > definitions. However, in this case it is not firing onMessage at the time but > is rather actually firing onException instead (and has relinquished the > session delivery lock). As such the "Illegal invocation" exception is > incorrect and the thread calling those operations should be permitted during > this scenario. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-521) ExceptionListener fired due to async dispatch failure is unable to close the Session/Connection
[ https://issues.apache.org/jira/browse/QPIDJMS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-521: --- Issue Type: Bug (was: Task) > ExceptionListener fired due to async dispatch failure is unable to close the > Session/Connection > --- > > Key: QPIDJMS-521 > URL: https://issues.apache.org/jira/browse/QPIDJMS-521 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.55.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 0.56.0 > > > **When an unexpected failure occurs during the process of dispatching a > message to an asynchronous consumer (i.e the work surrounding, but not > including, onMessage), the connection ExceptionListener is fired as a result. > If the ExceptionListener attempts to close the consumers containing Session > or Connection it will currently fail with an javax.jms.IllegalStateException > noting an "Illegal invocation from MessageListener callback". > This happens because the session async dispatch thread is ordinarily not > allowed to call these methods, is in keeping with the impl and their API > definitions. However, in this case it is not firing onMessage at the time but > is rather actually firing onException instead (and has relinquished the > session delivery lock). As such the "Illegal invocation" exception is > incorrect and the thread calling those operations should be permitted during > this scenario. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2305) Pypi module for version 0.33
[ https://issues.apache.org/jira/browse/PROTON-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241569#comment-17241569 ] Ken Giusti commented on PROTON-2305: Just FYI I've built and uploaded the 0.33.0 python package to Pypi just now. > Pypi module for version 0.33 > > > Key: PROTON-2305 > URL: https://issues.apache.org/jira/browse/PROTON-2305 > Project: Qpid Proton > Issue Type: Bug >Reporter: Lazar Slavkovic-Raco >Priority: Major > > When we can expect python-qpid-proton v0.33 on pypi.org? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2305) Pypi module for version 0.33
[ https://issues.apache.org/jira/browse/PROTON-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2305. Resolution: Information Provided > Pypi module for version 0.33 > > > Key: PROTON-2305 > URL: https://issues.apache.org/jira/browse/PROTON-2305 > Project: Qpid Proton > Issue Type: Bug >Reporter: Lazar Slavkovic-Raco >Priority: Major > > When we can expect python-qpid-proton v0.33 on pypi.org? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2305) Pypi module for version 0.33
[ https://issues.apache.org/jira/browse/PROTON-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241451#comment-17241451 ] Robbie Gemmell commented on PROTON-2305: Please use the users mailing list for asking questions like this. I'll prod the relevant folks this time. The pypi bits are published by community members at some point after release. Last week was US thanksgiving so they may have been a bit busy or otherwise occupied. > Pypi module for version 0.33 > > > Key: PROTON-2305 > URL: https://issues.apache.org/jira/browse/PROTON-2305 > Project: Qpid Proton > Issue Type: Bug >Reporter: Lazar Slavkovic-Raco >Priority: Major > > When we can expect python-qpid-proton v0.33 on pypi.org? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241412#comment-17241412
]
Roddie Kieley commented on PROTON-2231:
---
No, I don't think so. It sounds like what we are saying here is the fact that
the code executes an assert like:
{code:java}
static void remove_active_lh(pn_proactor_t *p) {
assert(p->active > 0);
if (--p->active == 0) {
p->need_inactive = true;
}
} {code}
when you attempt to close and remove more listeners than have been opened is
incorrect based on the above. Either that code shouldn't execute at that point
in time or the assert itself is invalid.
I will review the other implementations and the documentation and see about
next steps to address the issue.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
