[jira] [Updated] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Sharda updated DISPATCH-332: --- Environment: Debian 8.3, Qpid Proton 0.12.2 for drivers and dependency for Qpid Dispatch, Ha

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279321#comment-15279321 ] Steven commented on QPID-7256: -- According to our business scene,We need that every time CeatCo

[jira] [Comment Edited] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279316#comment-15279316 ] Steven edited comment on QPID-7256 at 5/11/16 12:48 AM: if I used t

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279316#comment-15279316 ] Steven commented on QPID-7256: -- if I used the following code to test,it can send 1000 message

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279312#comment-15279312 ] Steven commented on QPID-7256: -- I was trying to connect to Qpid Java Broker. As you can see t

[jira] [Updated] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Sharda updated DISPATCH-332: --- Description: We are running two Dispatch Routers each configured for interior mode and the

[jira] [Updated] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Sharda updated DISPATCH-332: --- Description: We are running two Dispatch Routers each configured for interior mode and the

[jira] [Created] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

Vishal Sharda created DISPATCH-332: -- Summary: Heavy message loss happening with 2 interconnected routers Key: DISPATCH-332 URL: https://issues.apache.org/jira/browse/DISPATCH-332 Project: Qpid Dispatc

[jira] [Commented] (QPIDJMS-173) Provide for finer grained control over automatic presettling of received messages

[ https://issues.apache.org/jira/browse/QPIDJMS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279135#comment-15279135 ] ASF subversion and git services commented on QPIDJMS-173: - Commit

[jira] [Reopened] (QPID-7215) [Java Broker, WMC] WMC should use query to retrieve connections

[ https://issues.apache.org/jira/browse/QPID-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reopened QPID-7215: -- > [Java Broker, WMC] WMC should use query to retrieve connections > -

[jira] [Commented] (QPID-7215) [Java Broker, WMC] WMC should use query to retrieve connections

[ https://issues.apache.org/jira/browse/QPID-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279114#comment-15279114 ] Keith Wall commented on QPID-7215: -- On trunk, if the last virtualhostnode is deleted, the

[jira] [Reopened] (QPIDJMS-173) Provide for finer grained control over automatic presettling of received messages

[ https://issues.apache.org/jira/browse/QPIDJMS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened QPIDJMS-173: -- Some additional cleanup todo here. > Provide for finer grained control over automatic presettling

[jira] [Commented] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279077#comment-15279077 ] Keith Wall commented on QPID-7196: -- Alex, can you review this commit please? > [Java Brok

[jira] [Assigned] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7196: Assignee: Keith Wall (was: Alan Conway) > [Java Broker] ConcurrentModificationException can occur o

[jira] [Updated] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7196: - Assignee: Alan Conway > [Java Broker] ConcurrentModificationException can occur on Broker startup > when v

[jira] [Updated] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7196: - Assignee: Alex Rudyy (was: Keith Wall) > [Java Broker] ConcurrentModificationException can occur on Broker

[jira] [Updated] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7196: - Status: Reviewable (was: In Progress) > [Java Broker] ConcurrentModificationException can occur on Broker

[jira] [Commented] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

[ https://issues.apache.org/jira/browse/QPID-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279070#comment-15279070 ] ASF subversion and git services commented on QPID-7196: --- Commit 17432

[jira] [Commented] (QPIDJMS-175) Add support for a timeout value for drain requests.

[ https://issues.apache.org/jira/browse/QPIDJMS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279017#comment-15279017 ] ASF subversion and git services commented on QPIDJMS-175: - Commit

[jira] [Commented] (QPIDJMS-175) Add support for a timeout value for drain requests.

[ https://issues.apache.org/jira/browse/QPIDJMS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279016#comment-15279016 ] ASF subversion and git services commented on QPIDJMS-175: - Commit

[jira] [Comment Edited] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279012#comment-15279012 ] Adel Boutros edited comment on DISPATCH-290 at 5/10/16 9:41 PM: --

[jira] [Commented] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279012#comment-15279012 ] Adel Boutros commented on DISPATCH-290: --- This is the problem when working late, yo

[jira] [Commented] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279005#comment-15279005 ] Ted Ross commented on DISPATCH-290: --- Sure. I interpreted your comment from the 25th a

[jira] [Updated] (QPID-6866) Paginate connections table on virtualhost tab

[ https://issues.apache.org/jira/browse/QPID-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6866: - Fix Version/s: qpid-java-6.1 > Paginate connections table on virtualhost tab >

[jira] [Resolved] (QPID-6866) Paginate connections table on virtualhost tab

[ https://issues.apache.org/jira/browse/QPID-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-6866. -- Resolution: Fixed > Paginate connections table on virtualhost tab > -

[jira] [Commented] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1527#comment-1527 ] Adel Boutros commented on DISPATCH-290: --- [~tedross] I noticed that in the code yo

[jira] [Assigned] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-290: - Assignee: Ted Ross > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Sol

[jira] [Commented] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278853#comment-15278853 ] ASF subversion and git services commented on DISPATCH-290: -- Com

[jira] [Resolved] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-290. --- Resolution: Fixed > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris >

[jira] [Resolved] (DISPATCH-310) Use router.id instead of container.containerName

[ https://issues.apache.org/jira/browse/DISPATCH-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-310. --- Resolution: Fixed > Use router.id instead of container.containerName > -

[jira] [Commented] (DISPATCH-310) Use router.id instead of container.containerName

[ https://issues.apache.org/jira/browse/DISPATCH-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278787#comment-15278787 ] ASF subversion and git services commented on DISPATCH-310: -- Com

[jira] [Resolved] (DISPATCH-307) misc fixups for console plugin build

[ https://issues.apache.org/jira/browse/DISPATCH-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-307. --- Resolution: Fixed > misc fixups for console plugin build > -

[jira] [Commented] (DISPATCH-307) misc fixups for console plugin build

[ https://issues.apache.org/jira/browse/DISPATCH-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278736#comment-15278736 ] ASF subversion and git services commented on DISPATCH-307: -- Com

Problems with setting up Qpid Java in Eclipse

Hi All, I have been trying to setup my dev environment for Qpid Java [1] using Eclipse and I have not been successful yet. Following are the approaches I tried so far: *1. Using Maven pom.xml to import projects* a) After getting the source, I do File -> Import -> Import Maven Project b) Select th

[jira] [Updated] (DISPATCH-330) Access control policy should return more suitable errors

[ https://issues.apache.org/jira/browse/DISPATCH-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-330: -- Assignee: Chuck Rolke > Access control policy should return more suitable errors > ---

[jira] [Updated] (DISPATCH-211) Expose connection properties in management response

[ https://issues.apache.org/jira/browse/DISPATCH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-211: -- Fix Version/s: 0.7.0 > Expose connection properties in management response > -

[jira] [Updated] (DISPATCH-103) Websocket Listeners

[ https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-103: -- Assignee: (was: Ted Ross) > Websocket Listeners > --- > > Key: DIS

[jira] [Created] (DISPATCH-331) Allow for a default policy to apply when open.hostname doesn't match an existing policy

Ted Ross created DISPATCH-331: - Summary: Allow for a default policy to apply when open.hostname doesn't match an existing policy Key: DISPATCH-331 URL: https://issues.apache.org/jira/browse/DISPATCH-331 P

[jira] [Commented] (DISPATCH-306) Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively

[ https://issues.apache.org/jira/browse/DISPATCH-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278647#comment-15278647 ] Ernest Allen commented on DISPATCH-306: --- What I was seeing was because the config

[jira] [Resolved] (DISPATCH-47) qdrouterd doesn't know where its libraries are

[ https://issues.apache.org/jira/browse/DISPATCH-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-47. -- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > qdrouterd doesn't know wher

[jira] [Resolved] (DISPATCH-53) waypoints are not robust if targets not set up in advance.

[ https://issues.apache.org/jira/browse/DISPATCH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-53. -- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > waypoints are not robust if

[jira] [Resolved] (DISPATCH-58) Router/Broker interaction - Unroutable/released messages are continually resent

[ https://issues.apache.org/jira/browse/DISPATCH-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-58. -- Resolution: Fixed Fix Version/s: 0.6.0 > Router/Broker interaction - Unroutable/released message

[jira] [Resolved] (DISPATCH-175) Router continues to forward messages to the broker even when the broker is not available

[ https://issues.apache.org/jira/browse/DISPATCH-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-175. --- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > Router continues to forw

[jira] [Resolved] (DISPATCH-176) Messages sent got lost when one of the brokers went down

[ https://issues.apache.org/jira/browse/DISPATCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-176. --- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > Messages sent got lost w

[jira] [Resolved] (DISPATCH-207) When a message body of [ ] is sent from rhea it is rejected as an invalid body

[ https://issues.apache.org/jira/browse/DISPATCH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-207. --- Resolution: Fixed Assignee: Ganesh Murthy Fix Version/s: 0.6.0 > When a message body

[jira] [Resolved] (DISPATCH-234) undeliverable-here set to true for messages from waypoints if there is no receiver

[ https://issues.apache.org/jira/browse/DISPATCH-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-234. --- Resolution: Fixed Fix Version/s: 0.6.0 The 0.6.0 architecture update removes this behavior.

[jira] [Updated] (DISPATCH-306) Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively

[ https://issues.apache.org/jira/browse/DISPATCH-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-306: -- Fix Version/s: 0.6.0 > Deprecate addr and routerId attributes in qdrouter schema and replace them > w

[jira] [Updated] (DISPATCH-310) Use router.id instead of container.containerName

[ https://issues.apache.org/jira/browse/DISPATCH-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-310: -- Fix Version/s: 0.6.0 > Use router.id instead of container.containerName >

[jira] [Updated] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-290: -- Fix Version/s: 0.6.0 > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[jira] [Updated] (DISPATCH-320) SSL enabled connector does not do hostname verification

[ https://issues.apache.org/jira/browse/DISPATCH-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-320: -- Fix Version/s: 0.6.0 > SSL enabled connector does not do hostname verification > -

[jira] [Closed] (PROTON-1181) [reactor] Use the host passed to pn_reactor_connection_to_host as default hostname for open frame

[ https://issues.apache.org/jira/browse/PROTON-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti closed PROTON-1181. -- Resolution: Won't Fix It is not proper to meld the TCP host address with the AMQP 1.0 Connection Open

[jira] [Commented] (PROTON-1172) Bump the priority of reactor 'connecting' log messages down to Debug

[ https://issues.apache.org/jira/browse/PROTON-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278441#comment-15278441 ] ASF subversion and git services commented on PROTON-1172: - Commit

[jira] [Resolved] (PROTON-1172) Bump the priority of reactor 'connecting' log messages down to Debug

[ https://issues.apache.org/jira/browse/PROTON-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1172. Resolution: Fixed > Bump the priority of reactor 'connecting' log messages down to Debug >

[jira] [Commented] (QPID-5816) [Java Client 0-10] If a resolved destination is used to create a consumer on a new connection created after destination was resolved, the client does not try to create t

[ https://issues.apache.org/jira/browse/QPID-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278418#comment-15278418 ] ASF subversion and git services commented on QPID-5816: --- Commit 17432

[jira] [Assigned] (PROTON-1172) Bump the priority of reactor 'connecting' log messages down to Debug

[ https://issues.apache.org/jira/browse/PROTON-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1172: -- Assignee: Ken Giusti > Bump the priority of reactor 'connecting' log messages down to Debug >

[jira] [Resolved] (PROTON-1193) Proton-c uses getaddrinfo/socket calls incorrectly

[ https://issues.apache.org/jira/browse/PROTON-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1193. - Resolution: Fixed Fix Version/s: 0.13.0 > Proton-c uses getaddrinfo/socket calls i

[jira] [Commented] (PROTON-1193) Proton-c uses getaddrinfo/socket calls incorrectly

[ https://issues.apache.org/jira/browse/PROTON-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278166#comment-15278166 ] ASF subversion and git services commented on PROTON-1193: - Commit

[jira] [Assigned] (PROTON-1193) Proton-c uses getaddrinfo/socket calls incorrectly

[ https://issues.apache.org/jira/browse/PROTON-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-1193: --- Assignee: Andrew Stitcher > Proton-c uses getaddrinfo/socket calls incorrectly > ---

[jira] [Created] (PROTON-1193) Proton-c uses getaddrinfo/socket calls incorrectly

Andrew Stitcher created PROTON-1193: --- Summary: Proton-c uses getaddrinfo/socket calls incorrectly Key: PROTON-1193 URL: https://issues.apache.org/jira/browse/PROTON-1193 Project: Qpid Proton

[jira] [Resolved] (DISPATCH-321) Dispatch does not send out SASL-OUTCOME frame on sasl failure

[ https://issues.apache.org/jira/browse/DISPATCH-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-321. Resolution: Fixed Fix Version/s: 0.6.0 > Dispatch does not send out SASL-OUTCOME fr

[jira] [Commented] (DISPATCH-321) Dispatch does not send out SASL-OUTCOME frame on sasl failure

[ https://issues.apache.org/jira/browse/DISPATCH-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278103#comment-15278103 ] ASF GitHub Bot commented on DISPATCH-321: - Github user asfgit closed the pull re

[jira] [Commented] (DISPATCH-321) Dispatch does not send out SASL-OUTCOME frame on sasl failure

[ https://issues.apache.org/jira/browse/DISPATCH-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278102#comment-15278102 ] ASF subversion and git services commented on DISPATCH-321: -- Com

[GitHub] qpid-dispatch pull request: DISPATCH-321 - Removed qdpn_connector_...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/71 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature i

[jira] [Commented] (QPID-7251) [Python Client for AMQP 0-8...0-91] Setting of SASL mechanism (other then PLAIN) explicitly does not work in python client for AMQP 0-8...0-91

[ https://issues.apache.org/jira/browse/QPID-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278043#comment-15278043 ] ASF subversion and git services commented on QPID-7251: --- Commit 17431

[jira] [Commented] (QPIDJMS-175) Add support for a timeout value for drain requests.

[ https://issues.apache.org/jira/browse/QPIDJMS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277994#comment-15277994 ] ASF subversion and git services commented on QPIDJMS-175: - Commit

[jira] [Commented] (QPID-7257) [Java Broker] Correct connection state logging

[ https://issues.apache.org/jira/browse/QPID-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277993#comment-15277993 ] ASF subversion and git services commented on QPID-7257: --- Commit 17431

[jira] [Created] (QPID-7257) [Java Broker] Correct connection state logging

Alex Rudyy created QPID-7257: Summary: [Java Broker] Correct connection state logging Key: QPID-7257 URL: https://issues.apache.org/jira/browse/QPID-7257 Project: Qpid Issue Type: Bug C

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277934#comment-15277934 ] Rob Godfrey commented on QPID-7256: --- Which broker/service are you trying to connect to (e

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277912#comment-15277912 ] Steven commented on QPID-7256: -- originally,I want to use the method "connection.setExceptionLi

[jira] [Comment Edited] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277897#comment-15277897 ] Steven edited comment on QPID-7256 at 5/10/16 10:11 AM: after it ha

[jira] [Comment Edited] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277897#comment-15277897 ] Steven edited comment on QPID-7256 at 5/10/16 10:11 AM: after it ha

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277897#comment-15277897 ] Steven commented on QPID-7256: -- after it had executed it for some time,It will report socket c

[jira] [Commented] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

[ https://issues.apache.org/jira/browse/QPID-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277891#comment-15277891 ] Steven commented on QPID-7256: -- as I cannot attach any attachment,the source_code of test code

[jira] [Created] (QPID-7256) When invoke the method "connection.start" in a loop,reporting socket closed

Steven created QPID-7256: Summary: When invoke the method "connection.start" in a loop,reporting socket closed Key: QPID-7256 URL: https://issues.apache.org/jira/browse/QPID-7256 Project: Qpid Issue

[jira] [Commented] (QPID-7253) [Java Client 0-10] Application allowed to create new JMS session whilst failover is in progress

[ https://issues.apache.org/jira/browse/QPID-7253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277856#comment-15277856 ] Alex Rudyy commented on QPID-7253: -- The changes look reasonable to me. We should port them

[jira] [Commented] (QPID-7255) Support delivery delay

[ https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277801#comment-15277801 ] Rob Godfrey commented on QPID-7255: --- I don't see why an operator wouldn't be able to dele

[jira] [Commented] (QPID-7255) Support delivery delay

[ https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277793#comment-15277793 ] Keith Wall commented on QPID-7255: -- What would an operator be able to do with a message th

[jira] [Created] (QPID-7255) Support delivery delay

Keith Wall created QPID-7255: Summary: Support delivery delay Key: QPID-7255 URL: https://issues.apache.org/jira/browse/QPID-7255 Project: Qpid Issue Type: New Feature Components: Java