yuuvis® RAD Q&A

0 votes
by (2.9k points)
edited by

Dear OS-Team,

after upgrading to yuuvis7 our core-service.log prints following error:

2021-07-07 16:31:28,362 ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (WorkerQueueProcessorThread-1) Could not refresh JMS Connection for destination 'BPMWORKERQUEUE' - retrying using FixedBackOff{interval=5000, currentAttempts=104, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp:// Reason: java.net.ConnectException: Connection refused: connect

We were updating the applicaton-mq.yml based on our understanding of https://help.optimal-systems.com/yuuvis_develop/display/onpremise/How to upgrade to yuuvis RAD 7.0

There are some misunderstanding about the messaging-service. Based on the documentation, we assume the messaging-service is the microservice "Messaging" in spring boot admin and therefore installed on the service-manager (not on core-service).

Following setup do we have:

core-service (separate machine)
service-manager (separate machine; Ports 61616 and 61777 are open)


spring.activemq.broker-url: 'tcp://'
spring.activemq.broker-url-stomp: 'stomp://'
spring.activemq.in-memory: false
spring.activemq.pooled: true
spring.jms.pubSubDomain: true

Result: All microservices using the "Messaging" microservice are happy. But core-service is trying to connect to Do we have to set a configuration on the core-service in order to solve this Connection error?

If we change the application-mq.yml to set the ip of the core-server, than the service-manager.log will throw errors because the custom-microservices cannot connect to the messaging-server.

if we change the application-mq.yml to set the IP or hostname of the service-manager, the service-manager.log will throw Connection Refused errors, even though its his own IP.

Thank you for your help,


1 Answer

0 votes
by (15.7k points)
selected by
Best answer

Hello Dennis,

you need to put the public IP address of the service-manager server in the application-mq.yml.

Best regards

by (2.9k points)
Thanks Nicolai, your info helped. Now it's working.
It would be good if it could be written like that in the documentation :)