JMS Connection failes

[robleer]

Hi,

Since last Friday I suddenly got this message and my application does not work anymore. I can login the app, but when I want to do something a connection error occurs.

I restarted the services and the server, but it keeps occuring. To my opinion nothing changed on this server, so anyone a clue what causes this??



INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - closing JMS connection
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop()
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop: JMSException: [org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException [java.io.EOFException]]
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop: JMSException: [ - during cleanup after - JMSException: javax.jms.JMSException: java.io.EOFException [java.io.EOFException]]
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - consumer.close()
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - session.close()
INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.close()
INFO | jvm 1 | 2023/03/20 13:44:13 | ERROR: org.openadaptor.adaptor.jms.JMSSource PublishException org.openadaptor.adaptor.jms.PublishException: org.openadaptor.adaptor.jms.JMSListener - close() failed with JMSException: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException [java.io.EOFException]
INFO | jvm 1 | 2023/03/20 13:44:13 | - during cleanup after - JMSException: javax.jms.JMSException: java.io.EOFException [java.io.EOFException]
INFO | jvm 1 | 2023/03/20 13:44:24 | mrt. 20, 2023 1:44:24 P.M. org.apache.coyote.AbstractProtocol pause
INFO | jvm 1 | 2023/03/20 13:44:24 | INFO: Pausing ProtocolHandler ["http-nio-443"]
INFO | jvm 1 | 2023/03/20 13:44:25 | mrt. 20, 2023 1:44:24 P.M. org.apache.coyote.AbstractProtocol pause
INFO | jvm 1 | 2023/03/20 13:44:25 | INFO: Pausing ProtocolHandler ["https-jsse-nio-8443"]
INFO | jvm 1 | 2023/03/20 13:44:25 | mrt. 20, 2023 1:44:24 P.M. org.apache.catalina.core.StandardService stopInternal
INFO | jvm 1 | 2023/03/20 13:44:25 | INFO: Stopping service [Catalina]
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: An illegal reflective access operation has occurred
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/C:/AwareIM/Tomcat/lib/catalina.jar) to field java.io.ObjectStreamClass$Caches.localDescs
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: All illegal access operations will be denied in a future release
INFO | jvm 1 | 2023/03/20 13:44:25 | mrt. 20, 2023 1:44:25 P.M. org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: The web application [AwareIM] appears to have started a thread named [Thread-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
INFO | jvm 1 | 2023/03/20 13:44:25 | [email protected]/java.lang.Object.wait(Native Method)
INFO | jvm 1 | 2023/03/20 13:44:25 | [email protected]/java.lang.Thread.join(Thread.java:1308)
INFO | jvm 1 | 2023/03/20 13:44:25 | [email protected]/java.lang.Thread.join(Thread.java:1375)
INFO | jvm 1 | 2023/03/20 13:44:25 | org.openadaptor.adaptor.RunAdaptor.run(RunAdaptor.java:703)
INFO | jvm 1 | 2023/03/20 13:44:25 | [email protected]/java.lang.Thread.run(Thread.java:835)

[customaware]

I don't have a clue but compliments of Chat GPT4....FWIW....

Based on the provided log file, the primary issue appears to be related to the JMS (Java Message Service) connection failure. The relevant log lines are:

Code: Select all

INFO | jvm 1 | 2023/03/20 13:44:13 | TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop: JMSException: [org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException [java.io.EOFException]]

The log indicates that the JMS connection failed due to an EOFException, which generally means that the input source reached the end of the file or stream unexpectedly. This could be caused by a network issue or a problem with the JMS broker (in this case, Apache ActiveMQ).

Additionally, there are some warnings related to illegal reflective access:

Code: Select all

INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: An illegal reflective access operation has occurred
INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/C:/AwareIM/Tomcat/lib/catalina.jar) to field java.io.ObjectStreamClass$Caches.localDescs

This is likely due to the use of an older library or framework that's not fully compatible with the current Java version. While this warning might not be directly related to the JMS connection issue, it's worth addressing to prevent potential issues in the future.

Lastly, there is a warning about a potential memory leak caused by a thread that was not properly stopped:

Code: Select all

INFO | jvm 1 | 2023/03/20 13:44:25 | WARNING: The web application [AwareIM] appears to have started a thread named [Thread-7] but has failed to stop it. This is very likely to create a memory leak.

To resolve these issues, consider the following steps:

- Check the network connectivity between the application and the JMS broker (Apache ActiveMQ).
- Ensure that the JMS broker is running and properly configured.
- Investigate the source code of the application, specifically around the JMS connection handling, to ensure proper handling of connection failures and
resource clean-up.
- Update any outdated libraries or frameworks to be compatible with the current Java version to address the illegal reflective access warnings.
- Examine the application's thread management and ensure proper handling of thread lifecycles to avoid potential memory leaks.

[robleer]

Hi Mark,

Thanks for your answer, but this application is running for months without problems and we did not change anything on the server of installation. I really do not know how to follow your advices and this never occured to me in years.

It seems that our firewall has had an update in the night before we noticed this problem. Looks like it has something to do with that.