[jira] [Commented] (DISPATCH-583) Random segmentation fault
[ https://issues.apache.org/jira/browse/DISPATCH-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712175#comment-15712175 ] Paolo Patierno commented on DISPATCH-583: - Ok ... I'm quite sure that the segmentation fault is related to connection suddenly closed. I have a systematic way for crashing, using my mqtt-frontend project and running this specific test : mvn -Dtest=PublishTest#publishQoS0toMqtt test I have to fix synchronization in my unit test to avoid this seddenly connection close but now we have more info to discover why the router crash. > Random segmentation fault > - > > Key: DISPATCH-583 > URL: https://issues.apache.org/jira/browse/DISPATCH-583 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.8.0 >Reporter: Paolo Patierno >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: qdrouterd.conf > > > Hello, > working with the following project : > https://github.com/EnMasseProject/mqtt-frontend > using the router, I have random "segmentation fault" errors when the > SubscribeTest is executed. It happens running the test 3-4 times ... or 20 > times ... totally random. > You can reproduce it, cloning the above repo and running : > mvn -Dtest=SubscribeTest test > I used the route built from the repo source code (about 2 weeks ago) but > applying the patch for message annotations on that. > I got the backtrace of one of the crash : > #0 0x000f00747369 in ?? () > #1 0x7f0eceddcf69 in pn_class_equals (clazz=, > a=, b=b@entry=0x7f0eb800bd90) at > /qpid-proton-0.15.0/proton-c/src/object/object.c:169 > #2 0x7f0eceddd466 in pn_list_index (list=list@entry=0x7f0eb802c0c0, > value=value@entry=0x7f0eb800bd90) at > /qpid-proton-0.15.0/proton-c/src/object/list.c:88 > #3 0x7f0eceddd559 in pn_list_remove (list=0x7f0eb802c0c0, > value=value@entry=0x7f0eb800bd90) at > /qpid-proton-0.15.0/proton-c/src/object/list.c:99 > #4 0x7f0ecede82ea in pn_link_finalize (object=0x7f0eb800bd90) at > /qpid-proton-0.15.0/proton-c/src/engine/engine.c:1129 > #5 0x7f0eceddce19 in pn_class_decref (clazz=0x7f0ecf013480 , > object=0x7f0eb800bd90) at /qpid-proton-0.15.0/proton-c/src/object/object.c:95 > #6 0x7f0ecedeadb0 in pn_event_finalize (event=0x7f0eb802a580) at > /qpid-proton-0.15.0/proton-c/src/events/event.c:212 > #7 pn_event_finalize_cast (object=0x7f0eb802a580) at > /qpid-proton-0.15.0/proton-c/src/events/event.c:257 > #8 0x7f0eceddce19 in pn_class_decref (clazz=0x7f0ecf013600 , > clazz@entry=0x7f0ecf012f00 , object=0x7f0eb802a580) at > /qpid-proton-0.15.0/proton-c/src/object/object.c:95 > #9 0x7f0eceddd02f in pn_decref (object=) at > /qpid-proton-0.15.0/proton-c/src/object/object.c:253 > #10 0x7f0ecedeb0a2 in pn_collector_pop > (collector=collector@entry=0x7f0eb8036450) at > /qpid-proton-0.15.0/proton-c/src/events/event.c:189 > #11 0x7f0ecf055d43 in process_connector (cxtr=0x7f0eb8002f90, > qd_server=0x2517e70) at /qpid-dispatch/src/server.c:851 > #12 thread_run (arg=) at /qpid-dispatch/src/server.c:1075 > #13 0x7f0ecebb45ba in start_thread () from /lib64/libpthread.so.0 > #14 0x7f0ece1037cd in clone () from /lib64/libc.so.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-586) Dispatch crash on running c sender and receiver
Ganesh Murthy created DISPATCH-586:
--
Summary: Dispatch crash on running c sender and receiver
Key: DISPATCH-586
URL: https://issues.apache.org/jira/browse/DISPATCH-586
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 0.7.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 0.8.0
Attachments: build.sh, receiver.c, sender.c
Sender and receiver c classes are attached.
Start the router (dispatch-master and proton-master)
Start the senders and receivers like this
./receiver -a 172.123.10.11:1 -c 36000 -q -s test6_1 &
./sender -a 172.123.10.11:1 -c 36000 -q -u -t test6_1
The router crashes with the following backtrace
{noformat}
(gdb) bt
#0 0x0070 in ?? ()
#1 0x7f31bba40de0 in pn_class_free (clazz=0x7f31a0058f80,
object=0x7f31a0025680) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/object/object.c:117
#2 0x7f31bba40fcf in pn_free (object=) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/object/object.c:263
#3 0x7f31bba4bcf2 in pni_free_children (children=0x7f31a0017180,
freed=0x7f31a0017040) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/engine/engine.c:456
#4 0x7f31bba4c509 in pn_session_finalize (object=0x7f31a0038fa0) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/engine/engine.c:926
#5 0x7f31bba40d98 in pn_class_decref (clazz=0x7f31bbc78500 ,
object=0x7f31a0038fa0) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/object/object.c:95
#6 0x7f31bba4f140 in pn_event_finalize (event=0x7f31a0016b40) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/events/event.c:212
#7 pn_event_finalize_cast (object=0x7f31a0016b40) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/events/event.c:257
#8 0x7f31bba40d98 in pn_class_decref (clazz=0x7f31bbc78600 ,
clazz@entry=0x7f31bbc77f00 , object=0x7f31a0016b40)
at /usr/src/debug/qpid-proton-0.14.0/proton-c/src/object/object.c:95
#9 0x7f31bba40faf in pn_decref (object=) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/object/object.c:253
#10 0x7f31bba4f402 in pn_collector_pop
(collector=collector@entry=0x7f31a0019340) at
/usr/src/debug/qpid-proton-0.14.0/proton-c/src/events/event.c:189
#11 0x7f31bbcbc82e in process_connector (cxtr=,
qd_server=0x15f7bb0) at /usr/src/debug/qpid-dispatch-0.7.0/src/server.c:856
#12 thread_run (arg=) at
/usr/src/debug/qpid-dispatch-0.7.0/src/server.c:1080
#13 0x7f31bb818dc5 in start_thread () from /lib64/libpthread.so.0
#14 0x7f31bad741cd in clone () from /lib64/libc.so.6
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7549) [Java Broker] Authentication using SimpleLDAP authentication provider fails with NPE when caching of authentication results is enabled(by default)
[
https://issues.apache.org/jira/browse/QPID-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7549:
-
Fix Version/s: qpid-java-6.2
> [Java Broker] Authentication using SimpleLDAP authentication provider fails
> with NPE when caching of authentication results is enabled(by default)
> --
>
> Key: QPID-7549
> URL: https://issues.apache.org/jira/browse/QPID-7549
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.2, qpid-java-6.1.1
>
>
> Authentication with SimpleLDAP authentication provider fails due to the
> following exception:
> {noformat}
> 2016-11-24 12:59:12,878 WARN [HttpManagement-testHTTP-158]
> (o.e.j.s.ServletHandler) - /service/sasl
> java.lang.NullPointerException: null
> at
> org.apache.qpid.server.security.auth.manager.AuthenticationResultCacher.digestCredentials(AuthenticationResultCacher.java:116)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.manager.AuthenticationResultCacher.getOrLoad(AuthenticationResultCacher.java:80)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.getOrLoadAuthenticationResult(SimpleLDAPAuthenticationManagerImpl.java:410)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.access$200(SimpleLDAPAuthenticationManagerImpl.java:83)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl$SimpleLDAPPlainCallbackHandler.handle(SimpleLDAPAuthenticationManagerImpl.java:669)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:87)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.authenticate(SimpleLDAPAuthenticationManagerImpl.java:312)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.security.SubjectCreator.authenticate(SubjectCreator.java:115)
> ~[qpid-broker-core-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.SaslServlet.evaluateSaslResponse(SaslServlet.java:213)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.SaslServlet.doPostWithSubjectAndActor(SaslServlet.java:135)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet$2.run(AbstractServlet.java:121)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet$2.run(AbstractServlet.java:117)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_74]
> at javax.security.auth.Subject.doAs(Subject.java:422) ~[na:1.8.0_74]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.doWithSubjectAndActor(AbstractServlet.java:218)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.doPost(AbstractServlet.java:115)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
> ~[geronimo-servlet_3.0_spec-1.0.jar:1.0]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> ~[geronimo-servlet_3.0_spec-1.0.jar:1.0]
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415]
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415]
> at
> org.apache.qpid.server.management.plugin.filter.ForbiddingAuthorisationFilter.doFilter(ForbiddingAuthorisationFilter.java:94)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
> ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415]
> at
> org.apache.qpid.server.management.plugin.filter.ForbiddingTraceFilter.doFilter(ForbiddingTraceFilter.java:65)
> ~[qpid-broker-plugins-management-http-6.1.0.jar:6.1.0]
> at
>
[jira] [Created] (QPID-7560) AbstractVirtualHost defines two state transitions from ERROR to ACTIVE
Keith Wall created QPID-7560: Summary: AbstractVirtualHost defines two state transitions from ERROR to ACTIVE Key: QPID-7560 URL: https://issues.apache.org/jira/browse/QPID-7560 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Fix For: qpid-java-6.2, qpid-java-6.1.1, qpid-java-6.0.6 The current implementation of AbstractVirtualHost defines two state transitions from ERROR=>ACTIVE. The state change mechanics could choose either which could lead to undesired -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7561) [Java Broker] Do not allow the creation of Derby Virtual Hosts if the Derby JDBC driver is not present
Rob Godfrey created QPID-7561: - Summary: [Java Broker] Do not allow the creation of Derby Virtual Hosts if the Derby JDBC driver is not present Key: QPID-7561 URL: https://issues.apache.org/jira/browse/QPID-7561 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey As per [this|http://mail-archives.apache.org/mod_mbox/qpid-users/201612.mbox/%3CVI1PR0901MB08935951C57678019161065DCD8F0%40VI1PR0901MB0893.eurprd09.prod.outlook.com%3E] mail on the users list, the broker should not offer to create a Derby backed virtual host / virtual host node if the Derby library is not on the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7562) Ensure that HTTP threads always carry a ManagementConnectionPrincipal
Keith Wall created QPID-7562: Summary: Ensure that HTTP threads always carry a ManagementConnectionPrincipal Key: QPID-7562 URL: https://issues.apache.org/jira/browse/QPID-7562 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Fix For: qpid-java-6.2 . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-229) allow supplying an SslContext instead of the configuration used to create one
[ https://issues.apache.org/jira/browse/QPIDJMS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-229: --- Summary: allow supplying an SslContext instead of the configuration used to create one (was: Please add back setSslContext() to the ConnectionFactory) Updated the title to better reflect the ask. Note that this wasn't 'removed' so much as it was simply never present, with the relevant parts of the newer client being implemented for Qpid JMS 0.1.0 before the change was ever made in the older/other client for Qpid 0.32. > allow supplying an SslContext instead of the configuration used to create one > - > > Key: QPIDJMS-229 > URL: https://issues.apache.org/jira/browse/QPIDJMS-229 > Project: Qpid JMS > Issue Type: New Feature >Affects Versions: 0.11.1 >Reporter: Jason Chan > > In reference to QPIDJMS-183, please add back the implementation of > setSslContext(). > The originating ticket which implemented this feature is: QPID-6400. The > main reason was to support the use of HSM > (https://en.wikipedia.org/wiki/Hardware_security_module) to hold the > keystores. This was implemented for 0.32. > In subsequent releases, this implementation was removed. > Here is an example of how to use HSM to access the keystore: > http://www.pixelstech.net/article/1420699130-Different-types-of-keystore-in-JavaPKCS11. > Once you have the keystore you you can initialize the SSLcontext and pass > that to the connection factory. As mentioned in QPID-6400, other vendors > provide this API as well. > If possible, please keep the API calls similar to the one in 0.32 as > discussed in QPID-6400. > Thank you! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
