[jira] [Resolved] (PROTON-2822) Build fails without building the proactor library

[Andrew Stitcher (Jira)]

 [ 
https://issues.apache.org/jira/browse/PROTON-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-2822.
-
Fix Version/s: proton-c-0.40.0
   Resolution: Fixed

> Build fails without building the proactor library
> -
>
> Key: PROTON-2822
> URL: https://issues.apache.org/jira/browse/PROTON-2822
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
>Affects Versions: proton-c-0.39.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: proton-c-0.40.0
>
>
> The build should be able to build the core library and test it without 
> building the proactor or other libraries - this seems to have bit rotted.



--
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

[jira] [Commented] (PROTON-2822) Build fails without building the proactor library

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/PROTON-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845093#comment-17845093
 ] 

ASF subversion and git services commented on PROTON-2822:
-

Commit 2406d4361a7725afba2b06dd3da2761efeba06ee in qpid-proton's branch 
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=2406d4361 ]

PROTON-2822: [Build] Correctly build/test without proactor


> Build fails without building the proactor library
> -
>
> Key: PROTON-2822
> URL: https://issues.apache.org/jira/browse/PROTON-2822
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
>Affects Versions: proton-c-0.39.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
>
> The build should be able to build the core library and test it without 
> building the proactor or other libraries - this seems to have bit rotted.



--
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

[jira] [Created] (PROTON-2822) Build fails without building the proactor library

[Andrew Stitcher (Jira)]

Andrew Stitcher created PROTON-2822:
---

 Summary: Build fails without building the proactor library
 Key: PROTON-2822
 URL: https://issues.apache.org/jira/browse/PROTON-2822
 Project: Qpid Proton
  Issue Type: Bug
  Components: build
Affects Versions: proton-c-0.39.0
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher


The build should be able to build the core library and test it without building 
the proactor or other libraries - this seems to have bit rotted.



--
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

Client Abruptly Disconnects (python-qpid-proton 0.38.0)

[Uiseman Miranda Araujo]

We are experiencing issues maintaining communication with Solace using AMQP. 
The base code is an example from Solace's 
GitHub.
 Sometimes, we are encountering the following error:
  [A close up of a text  Description automatically generated]
Additionally, there are situations where even when the application pods are 
down, Solace continues to indicate that the client is connected. Another 
scenario is that at times the pods are connected to Solace, but no messages 
from the queue are being consumed. The only solution to fix this is to restart 
manually, which would be a critical problem in a production environment. After 
a lot of research, we found this similar issue on your Jira: 
https://issues.apache.org/jira/browse/PROTON-2098. The solution for it was 
commited as showed in the picture bellow:
[https://lh7-us.googleusercontent.com/YWu1utXdvCFdkDI9-3P9BC8xzRx7kijImJScggAYncgSl3kVaBPAcZ1RUL395yt5rWcYheKNz4ZQp5wttDBZ6fmza-b2c8p5DdTw2mIpBbYoilNrZaVa9ymDbLrQ6AwlSIPKHIPC5C5TG4XcTXwoiEI]
But looking in the code of 0.38.0 version, we noticed more changes in those 
lines:
[https://lh7-us.googleusercontent.com/hwGRkzNZCvRFqcbcHn0VZwGMjoAZrSxvhw-FW1lsigk-VkWLmc_4vULenDL0pco5t4XNqWnvtDXKfAjjnu-jSunzXFIyp6TqP7QAQW25qy0ymfOx42mUDOHzRjPhgjQO753aMixxziF3oxznX-Ckncs]

 As this issue was already solved before, maybe some changes on newer versions 
brought that bug again. So, we're counting with  you to assist us with 
diagnosing and resolving this matter.