[jira] [Commented] (PROTON-1296) IllegalStateException on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473872#comment-15473872 ] Mark Soderquist commented on PROTON-1296: - I don't disagree with this assessment. I'll try and

[jira] [Created] (PROTON-1296) IllegalStateException on reconnect

Mark Soderquist created PROTON-1296: --- Summary: IllegalStateException on reconnect Key: PROTON-1296 URL: https://issues.apache.org/jira/browse/PROTON-1296 Project: Qpid Proton Issue Type:

[jira] [Commented] (QPID-6944) High CPU use sending message using SSL

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093985#comment-15093985 ] Mark Soderquist commented on QPID-6944: --- I have applied the patch and it appears to have worked. The

[jira] [Updated] (QPID-6944) High CPU use sending message using SSL

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid.cpu.png > High CPU use sending message using SSL >

[jira] [Updated] (QPID-6944) High CPU use sending message using SSL

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid.log.zip I'm back from vacation. I applied the patch and captured a high CPU

[jira] [Commented] (QPID-6944) High CPU use sending message using SSL

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083844#comment-15083844 ] Mark Soderquist commented on QPID-6944: --- Our host hardware is VMWare virtual servers. > High CPU use

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: (was: config.json) > High CPU use sending message >

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: config.json > High CPU use sending message > > >

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: config.json This morning I think I was able to narrow down the issue. I started with

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Description: Qpid is experiencing high CPU use when a message is sent. While the application

[jira] [Updated] (QPID-6944) High CPU use sending message using SSL

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Summary: High CPU use sending message using SSL (was: High CPU use sending message) > High CPU

[jira] [Updated] (QPIDJMS-143) What Qpid AMQP 1.0 client to use?

[ https://issues.apache.org/jira/browse/QPIDJMS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPIDJMS-143: Description: Over the months I have found at least four Qpid client libraries that could

[jira] [Created] (QPID-6955) BufferOverflowException downloading message content

Mark Soderquist created QPID-6955: - Summary: BufferOverflowException downloading message content Key: QPID-6955 URL: https://issues.apache.org/jira/browse/QPID-6955 Project: Qpid Issue Type:

[jira] [Commented] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060394#comment-15060394 ] Mark Soderquist commented on QPID-6944: --- I changed the Oracle BDB JE library to 5.0.104 but I ended

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: virtualhosts.xml config.json broker.acl I've

[jira] [Commented] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058383#comment-15058383 ] Mark Soderquist commented on QPID-6944: --- I have attached a project that is duplicating the issue. 1.

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid6944.zip Simple project to duplicate broker high CPU problem. > High CPU use

[jira] [Updated] (QPID-6944) High CPU use sending message

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Summary: High CPU use sending message (was: SelectorThread causing livelock) > High CPU use

[jira] [Updated] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago) OpenJDK Runtime Environment

[jira] [Updated] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid.cpu.png > SelectorThread causing livelock > --- > >

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056218#comment-15056218 ] Mark Soderquist commented on QPID-6944: --- Sorry, I should have added the environment information. It

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056223#comment-15056223 ] Mark Soderquist commented on QPID-6944: --- The CPU spike appears to occur immediately after startup.

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056313#comment-15056313 ] Mark Soderquist commented on QPID-6944: --- I have attached a graph of the CPU use. Note at the

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056290#comment-15056290 ] Mark Soderquist commented on QPID-6944: --- I think the CPU spike immediately after startup is a bit

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056750#comment-15056750 ] Mark Soderquist commented on QPID-6944: --- I've done more research and found that the live lock was

[jira] [Commented] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056378#comment-15056378 ] Mark Soderquist commented on QPID-6944: --- Just attached another screen shot where it live locked. No

[jira] [Updated] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid.cpu.png > SelectorThread causing livelock > --- > >

[jira] [Updated] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: qpid.6.0.png qpid.0.32.png > SelectorThread causing livelock >

[jira] [Created] (QPID-6944) SelectorThread causing livelock

Mark Soderquist created QPID-6944: - Summary: SelectorThread causing livelock Key: QPID-6944 URL: https://issues.apache.org/jira/browse/QPID-6944 Project: Qpid Issue Type: Bug Affects

[jira] [Updated] (QPID-6944) SelectorThread causing livelock

[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6944: -- Attachment: threaddump-1449856663270.tdump > SelectorThread causing livelock >

[jira] [Commented] (QPID-6862) IoReceiver thread using CPU even when there are no messages moving

[ https://issues.apache.org/jira/browse/QPID-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011423#comment-15011423 ] Mark Soderquist commented on QPID-6862: --- The patch appears to have worked as expected. CPU use is

[jira] [Created] (QPID-6862) IoReceiver thread using CPU even when there are no messages moving

Mark Soderquist created QPID-6862: - Summary: IoReceiver thread using CPU even when there are no messages moving Key: QPID-6862 URL: https://issues.apache.org/jira/browse/QPID-6862 Project: Qpid

[jira] [Commented] (QPID-6535) java.lang.OutOfMemoryError: unable to create new native thread

[ https://issues.apache.org/jira/browse/QPID-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14602301#comment-14602301 ] Mark Soderquist commented on QPID-6535: --- Thank you Rob. I look forward to testing

[jira] [Updated] (QPID-6535) java.lang.OutOfMemoryError: unable to create new native thread

[ https://issues.apache.org/jira/browse/QPID-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6535: -- Attachment: threaddump-qpid-stage-1431091571116.zip java.lang.OutOfMemoryError: unable to

[jira] [Created] (QPID-6535) java.lang.OutOfMemoryError: unable to create new native thread

Mark Soderquist created QPID-6535: - Summary: java.lang.OutOfMemoryError: unable to create new native thread Key: QPID-6535 URL: https://issues.apache.org/jira/browse/QPID-6535 Project: Qpid

[jira] [Created] (QPID-6483) Messages in the acquired state with no consumers

Mark Soderquist created QPID-6483: - Summary: Messages in the acquired state with no consumers Key: QPID-6483 URL: https://issues.apache.org/jira/browse/QPID-6483 Project: Qpid Issue Type:

[jira] [Updated] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6483: -- Attachment: qpid.restart.png Messages in the acquired state with no consumers

[jira] [Updated] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6483: -- Attachment: qpid.queue.attributes.png Messages in the acquired state with no consumers

[jira] [Updated] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6483: -- Attachment: qpid.acquired.png Messages in the acquired state with no consumers

[jira] [Commented] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485269#comment-14485269 ] Mark Soderquist commented on QPID-6483: --- A server restart seems to clear the acquired

[jira] [Commented] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485276#comment-14485276 ] Mark Soderquist commented on QPID-6483: --- We are not intentionally doing durable

[jira] [Commented] (QPID-6483) Messages in the acquired state with no consumers

[ https://issues.apache.org/jira/browse/QPID-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485273#comment-14485273 ] Mark Soderquist commented on QPID-6483: --- I can reproduce this problem regularly. It

[jira] [Created] (QPID-6482) NPE in SessionEndpoint.receiveTransfer when receiving large message

Mark Soderquist created QPID-6482: - Summary: NPE in SessionEndpoint.receiveTransfer when receiving large message Key: QPID-6482 URL: https://issues.apache.org/jira/browse/QPID-6482 Project: Qpid

[jira] [Created] (QPID-6479) System property qpid.connection_read_timeout not respected when using SSL

Mark Soderquist created QPID-6479: - Summary: System property qpid.connection_read_timeout not respected when using SSL Key: QPID-6479 URL: https://issues.apache.org/jira/browse/QPID-6479 Project:

[jira] [Commented] (QPID-6462) A message larger than 32732 bytes cannot be received under various circumstances

[ https://issues.apache.org/jira/browse/QPID-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14382208#comment-14382208 ] Mark Soderquist commented on QPID-6462: --- We have implemented changes according to the

[jira] [Created] (QPID-6459) SocketException printing stack trace

Mark Soderquist created QPID-6459: - Summary: SocketException printing stack trace Key: QPID-6459 URL: https://issues.apache.org/jira/browse/QPID-6459 Project: Qpid Issue Type: Improvement

[jira] [Created] (QPID-6439) Mandatory attribute storeUrl not supplied for instance of org.apache.qpid.server.security.FileKeyStoreImpl

Mark Soderquist created QPID-6439: - Summary: Mandatory attribute storeUrl not supplied for instance of org.apache.qpid.server.security.FileKeyStoreImpl Key: QPID-6439 URL:

[jira] [Commented] (QPID-6441) ClassNotFoundException: com.sleepycat.je.LockConflictException

[ https://issues.apache.org/jira/browse/QPID-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358675#comment-14358675 ] Mark Soderquist commented on QPID-6441: --- I have included the required libraries and

[jira] [Closed] (QPID-6441) ClassNotFoundException: com.sleepycat.je.LockConflictException

[ https://issues.apache.org/jira/browse/QPID-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist closed QPID-6441. - Resolution: Not a Problem ClassNotFoundException: com.sleepycat.je.LockConflictException

[jira] [Commented] (QPID-6441) ClassNotFoundException: com.sleepycat.je.LockConflictException

[ https://issues.apache.org/jira/browse/QPID-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357831#comment-14357831 ] Mark Soderquist commented on QPID-6441: --- Now I feel sheepish. That is most likely the

[jira] [Created] (QPID-6441) ClassNotFoundException: com.sleepycat.je.LockConflictException

Mark Soderquist created QPID-6441: - Summary: ClassNotFoundException: com.sleepycat.je.LockConflictException Key: QPID-6441 URL: https://issues.apache.org/jira/browse/QPID-6441 Project: Qpid

[jira] [Created] (QPID-6431) Consider using Hazelcast for distributed clustering

Mark Soderquist created QPID-6431: - Summary: Consider using Hazelcast for distributed clustering Key: QPID-6431 URL: https://issues.apache.org/jira/browse/QPID-6431 Project: Qpid Issue Type:

[jira] [Created] (QPID-6422) Pre-release binary distributions not available

Mark Soderquist created QPID-6422: - Summary: Pre-release binary distributions not available Key: QPID-6422 URL: https://issues.apache.org/jira/browse/QPID-6422 Project: Qpid Issue Type: Bug

[jira] [Created] (QPID-6386) IoSender thread leak

Mark Soderquist created QPID-6386: - Summary: IoSender thread leak Key: QPID-6386 URL: https://issues.apache.org/jira/browse/QPID-6386 Project: Qpid Issue Type: Bug Components: Java

[jira] [Commented] (QPID-6386) IoSender thread leak

[ https://issues.apache.org/jira/browse/QPID-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316909#comment-14316909 ] Mark Soderquist commented on QPID-6386: --- We are using the Qpid AMQP 1.0 client 0.30.

[jira] [Updated] (QPID-6386) IoSender thread leak

[ https://issues.apache.org/jira/browse/QPID-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6386: -- Attachment: Qpid6386Bug.java IoSender thread leak Key:

[jira] [Updated] (QPID-6386) IoSender thread leak

[ https://issues.apache.org/jira/browse/QPID-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-6386: -- Attachment: screenshot-1.png IoSender thread leak Key:

[jira] [Commented] (QPID-6338) AMQP 1.0 message not readable with AMQP 1.0 JMS client

[ https://issues.apache.org/jira/browse/QPID-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297271#comment-14297271 ] Mark Soderquist commented on QPID-6338: --- We going to do some experimenting with this

[jira] [Commented] (QPID-6338) AMQP 1.0 message not readable with AMQP 1.0 JMS client

[ https://issues.apache.org/jira/browse/QPID-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297752#comment-14297752 ] Mark Soderquist commented on QPID-6338: --- Here is what we found: When a message is

[jira] [Commented] (QPID-6338) AMQP 1.0 message not readable with AMQP 1.0 JMS client

[ https://issues.apache.org/jira/browse/QPID-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297869#comment-14297869 ] Mark Soderquist commented on QPID-6338: --- Sounds like this is not a bug, but I would

[jira] [Created] (QPID-6338) AMQP 1.0 message not readable with AMQP 1.0 JMS client

Mark Soderquist created QPID-6338: - Summary: AMQP 1.0 message not readable with AMQP 1.0 JMS client Key: QPID-6338 URL: https://issues.apache.org/jira/browse/QPID-6338 Project: Qpid Issue

[jira] [Commented] (QPID-6331) OutOfMemoryError: Java heap space

[ https://issues.apache.org/jira/browse/QPID-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289562#comment-14289562 ] Mark Soderquist commented on QPID-6331: --- That makes sense. I misunderstood that even

[jira] [Created] (QPID-6331) OutOfMemoryError: Java heap space

Mark Soderquist created QPID-6331: - Summary: OutOfMemoryError: Java heap space Key: QPID-6331 URL: https://issues.apache.org/jira/browse/QPID-6331 Project: Qpid Issue Type: Bug

[jira] [Created] (QPID-6332) Broker start slow when there are a lot of messages

Mark Soderquist created QPID-6332: - Summary: Broker start slow when there are a lot of messages Key: QPID-6332 URL: https://issues.apache.org/jira/browse/QPID-6332 Project: Qpid Issue Type:

[jira] [Commented] (QPID-6332) Broker start slow when there are a lot of messages

[ https://issues.apache.org/jira/browse/QPID-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286461#comment-14286461 ] Mark Soderquist commented on QPID-6332: --- After some more testing I have come to

[jira] [Comment Edited] (QPID-6332) Broker start slow when there are a lot of messages

[ https://issues.apache.org/jira/browse/QPID-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286461#comment-14286461 ] Mark Soderquist edited comment on QPID-6332 at 1/21/15 10:48 PM:

[jira] [Created] (QPID-6317) Calling Session.close prevents new session from being created

Mark Soderquist created QPID-6317: - Summary: Calling Session.close prevents new session from being created Key: QPID-6317 URL: https://issues.apache.org/jira/browse/QPID-6317 Project: Qpid

[jira] [Commented] (QPID-6317) Calling Session.close prevents new session from being created

[ https://issues.apache.org/jira/browse/QPID-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279376#comment-14279376 ] Mark Soderquist commented on QPID-6317: --- We are connecting to a Qpid 0.30 Java Broker

[jira] [Commented] (QPID-6317) Calling Session.close prevents new session from being created

[ https://issues.apache.org/jira/browse/QPID-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279378#comment-14279378 ] Mark Soderquist commented on QPID-6317: --- Not sure how to turn on protocol debug

[jira] [Commented] (QPID-6317) Calling Session.close prevents new session from being created

[ https://issues.apache.org/jira/browse/QPID-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279458#comment-14279458 ] Mark Soderquist commented on QPID-6317: --- [Thu Jan 15 15:50:29 MST 2015] FINE:

[jira] [Created] (QPID-6281) Child of type SessionAdapter already exists with name of 0

Mark Soderquist created QPID-6281: - Summary: Child of type SessionAdapter already exists with name of 0 Key: QPID-6281 URL: https://issues.apache.org/jira/browse/QPID-6281 Project: Qpid

[jira] [Commented] (QPID-5768) Add bind before search capability to SimpleLDAP authentication provider

[ https://issues.apache.org/jira/browse/QPID-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068571#comment-14068571 ] Mark Soderquist commented on QPID-5768: --- Rob, do you think your solution will allow

[jira] [Commented] (QPID-5768) Add bind before search capability to SimpleLDAP authentication provider

[ https://issues.apache.org/jira/browse/QPID-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068621#comment-14068621 ] Mark Soderquist commented on QPID-5768: --- Yes, that sounds reasonable. Add bind

[jira] [Created] (QPID-5884) NullPointerException when using Base64MD5 file for AMQP 1.0 authentication

Mark Soderquist created QPID-5884: - Summary: NullPointerException when using Base64MD5 file for AMQP 1.0 authentication Key: QPID-5884 URL: https://issues.apache.org/jira/browse/QPID-5884 Project:

[jira] [Commented] (QPID-5776) Unhandled Exception java.lang.IllegalArgumentException causes broker to exit

[ https://issues.apache.org/jira/browse/QPID-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004661#comment-14004661 ] Mark Soderquist commented on QPID-5776: --- We are doing some testing with Qpid and the

[jira] [Updated] (QPID-5776) Unhandled Exception java.lang.IllegalArgumentException causes broker to exit

[ https://issues.apache.org/jira/browse/QPID-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Soderquist updated QPID-5776: -- Attachment: QpidBrokerCrashTest.java Run the attached program twice to see the error occur. I

[jira] [Created] (QPID-5776) Unhandled Exception java.lang.IllegalArgumentException causes broker to exit

Mark Soderquist created QPID-5776: - Summary: Unhandled Exception java.lang.IllegalArgumentException causes broker to exit Key: QPID-5776 URL: https://issues.apache.org/jira/browse/QPID-5776 Project:

[jira] [Created] (QPID-5768) Add bind before search capability to SimpleLDAP authentication provider

Mark Soderquist created QPID-5768: - Summary: Add bind before search capability to SimpleLDAP authentication provider Key: QPID-5768 URL: https://issues.apache.org/jira/browse/QPID-5768 Project: Qpid

[jira] [Created] (QPID-5576) javax.naming.NamingException in org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory.getInitialContext()

Mark Soderquist created QPID-5576: - Summary: javax.naming.NamingException in org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory.getInitialContext() Key: QPID-5576 URL: