You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2019. It is now read-only.
We noticed an OutOfMemory issue after several weeks, or days sometime. It depends on the number of messages in the queues when the plugin runs. Version of Weblogic is 12.2.1.
The code resposible for this is in the JMS.java file line 172.
curs = (String) connections.invoke(destRTT[x], "getMessages", new Object[]{null, new Integer(0)}, new String[]{"java.lang.String", "java.lang.Integer"});
If we have messages in the queues and we run the plugin to gather the JMSStats, the number of weblogic.messaging.kernel.internal.QueueMessageReference instances doubles. Every time the plugin is run, the amount of instances doubles. I believe is an Oracle bug and we already have ticket with them about this. This is just for your info and you can try it also.
Hopefully this is helpful.
Br,
Alex Damacus.
The text was updated successfully, but these errors were encountered:
Hi,
We noticed an OutOfMemory issue after several weeks, or days sometime. It depends on the number of messages in the queues when the plugin runs. Version of Weblogic is 12.2.1.
The code resposible for this is in the JMS.java file line 172.
curs = (String) connections.invoke(destRTT[x], "getMessages", new Object[]{null, new Integer(0)}, new String[]{"java.lang.String", "java.lang.Integer"});
If we have messages in the queues and we run the plugin to gather the JMSStats, the number of weblogic.messaging.kernel.internal.QueueMessageReference instances doubles. Every time the plugin is run, the amount of instances doubles. I believe is an Oracle bug and we already have ticket with them about this. This is just for your info and you can try it also.
Hopefully this is helpful.
Br,
Alex Damacus.
The text was updated successfully, but these errors were encountered: