-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic recovery with stomp bridge enables fails with: java.lang.NoClassDefFoundError: Could not initialize class com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl #341
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented
Restart local instance
Observe error:
|
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented
|
@glassfishrobot Commented
|
@glassfishrobot Commented Your report reminded me of this question on the forum |
@glassfishrobot Commented (Updated) I see the version used was 3.1.2.2 (July 2012). |
@glassfishrobot Commented |
|
When we are killing our glassfish with kill -9 because of the following bug: https://java.net/jira/browse/MQ-340
We are not able anymore to directly restart the server. The following message appears in the server.log:
We are running JMS in embedded mode and it is doing recovery on restart.
The problem here is that the JMS system is started for automatic recovery and the stomp bridge is started too. Unfortunately the classloader for the recovery thread seams to have problems to load UnifiedConnectionImpl.
I also added some details in the following thread:
https://www.java.net/forum/topic/glassfish/glassfish/noclassdeffounderror-when-using-stomp-bridge-openmq-one-cluster-node
The following work around works:
Environment
Glassfish 3.1.2.2, Linux, Java 7
Affected Versions
[4.5.2]
The text was updated successfully, but these errors were encountered: