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

Biswa Ranjan Ray updated QPID-8595:
-----------------------------------
    Environment: 
System: Windows10 64bit

QPID-Broker-J: 8.0.6

Springboot: 2.2.4.RELEASE (Will be migrating to 2.6 or higher)

JAVA: JDK8/JDK11/JDK17

 

  was:
System: Windows10 64bit

QPID-Broker-J: 8.0.6

Springboot: 2.6.6 

JAVA: JDK8/JDK11/JDK17

 


> Unable to connect to QPID [Broker-J] due to authentication issue.
> -----------------------------------------------------------------
>
>                 Key: QPID-8595
>                 URL: https://issues.apache.org/jira/browse/QPID-8595
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-8.0.6
>         Environment: System: Windows10 64bit
> QPID-Broker-J: 8.0.6
> Springboot: 2.2.4.RELEASE (Will be migrating to 2.6 or higher)
> JAVA: JDK8/JDK11/JDK17
>  
>            Reporter: Biswa Ranjan Ray
>            Priority: Major
>         Attachments: Application_logs_1.jpg, Application_logs_2.jpg, 
> QPID_logs.jpg
>
>
> We've a springboot application and we use QPID as a message broker. When we 
> tried to start Qpid we found it throws a warning related to 
> {*}AuthenticationProvider{*}. And when we try to run our application it 
> crashes with a Socket closed exception. Application logs and Qpid warnings 
> are attached.
>  
> We also tried the following settings :
>  * Set QPID_HOME to its installation directory in Windows system variables 
>  * Set "modelVersion" : "8.0" in config.json file
>  * Add "secureOnlyMechanisms": [] under "authenticationproviders" in 
> config.json file. The config.json file is found under C:\<User 
> Dir>\AppData\Roaming\Qpid
>  * Set "version" : "8.0" in preference.json file.
> We tried to run QPID with different versions of JDK e.g 8/11/17, but it works 
> with none.
> Any suggestion please.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to