[PR] Python/pkg build [qpid-proton]
astitcher opened a new pull request, #424: URL: https://github.com/apache/qpid-proton/pull/424 This change moves the python package build away from the deprecated setup.py to the supported build.py builder with a setuptools backend. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-599) JmsTransactionInDoubtException: error
[
https://issues.apache.org/jira/browse/QPIDJMS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837833#comment-17837833
]
Timothy A. Bish commented on QPIDJMS-599:
-
>From the details provided the client sent a request to rollback a transaction
>due to a call to {code:java}session.rollback(){code} by the application. The
>server responds with an error indicating that it doesn't have any record of
>the specified transaction which is acceptable as the JMS API does indicate
>that the rollback method can throw due to internal errors. The application
>should be catching and maybe logging this or otherwise handling it. There is
>likely a connection drop and reconnect happening which leads to this but it is
>a bit hard to say for sure. There isn't much the client can do but throw as
>the remote has told it what it attempted failed.
> JmsTransactionInDoubtException: error
> -
>
> Key: QPIDJMS-599
> URL: https://issues.apache.org/jira/browse/QPIDJMS-599
> Project: Qpid JMS
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Rajesh Kumar
>Priority: Major
> Attachments: JMS_Exception_Details.txt
>
>
> Hi Team,
> we are receiving the following error intermittently
>
> Exception Details related JmsTransactionInDoubtException:
>
> Call Stack: org.apache.qpid.jms.JmsTransactionInDoubtException: Transaction
> is not declared Reference:9a13135d-348c-4a78-b53c-097a11ac103f,
> TrackingId:8ee88669-b631-4261-93eb-09b9beded92f_G8S3, SystemTracker:gtm,
> Timestamp:2024-03-05T01:40:45 [condition = amqp:transaction:unknown-id]
> at
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:39)
> at
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:25)
>
> Kindly help in fixing this error in priority
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
