[jira] [Updated] (QPID-4357) If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out.
[ https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4357: --- Fix Version/s: (was: 0.21) Future If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out. - Key: QPID-4357 URL: https://issues.apache.org/jira/browse/QPID-4357 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10, 0.12, 0.14, 0.16, 0.18, 0.20 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: Future Currently if the client receives an execution-exception while blocked on sync, it doesn't get notified. Instead the client times out with an exception as given bellow. This is less than ideal as it sometimes masks the real error and users need to go through the logs to figure out what really happens. This also adds a lot of time to our test suite when errors happen, prolonging the run time. org.apache.qpid.AMQException: timed out waiting for sync: complete = 37, point = 43 [error code 541: internal error] at org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1074) at org.apache.qpid.client.AMQSession_0_10.sync(AMQSession_0_10.java:1051) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4357) If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out.
[ https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4357: - Fix Version/s: (was: 0.19) 0.21 If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out. - Key: QPID-4357 URL: https://issues.apache.org/jira/browse/QPID-4357 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.21 Currently if the client receives an execution-exception while blocked on sync, it doesn't get notified. Instead the client times out with an exception as given bellow. This is less than ideal as it sometimes masks the real error and users need to go through the logs to figure out what really happens. This also adds a lot of time to our test suite when errors happen, prolonging the run time. org.apache.qpid.AMQException: timed out waiting for sync: complete = 37, point = 43 [error code 541: internal error] at org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1074) at org.apache.qpid.client.AMQSession_0_10.sync(AMQSession_0_10.java:1051) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4357) If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out.
[ https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4357: - Affects Version/s: 0.20 If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out. - Key: QPID-4357 URL: https://issues.apache.org/jira/browse/QPID-4357 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10, 0.12, 0.14, 0.16, 0.18, 0.20 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.21 Currently if the client receives an execution-exception while blocked on sync, it doesn't get notified. Instead the client times out with an exception as given bellow. This is less than ideal as it sometimes masks the real error and users need to go through the logs to figure out what really happens. This also adds a lot of time to our test suite when errors happen, prolonging the run time. org.apache.qpid.AMQException: timed out waiting for sync: complete = 37, point = 43 [error code 541: internal error] at org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1074) at org.apache.qpid.client.AMQSession_0_10.sync(AMQSession_0_10.java:1051) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
