Description
Summary of Topic
JMS queue becomes too large, and incident, "Large Supervisor JMS Request Queue", is generated.
This is normally caused by either slow IO or too many notifications or "requests" being generated by AO. This can cause system performance issues but not always.
There are 2 Queues:
1) Email Queue:
- pending e-mail notifications go here:
- /opt/glassfish/domains/domain1/imq/instances/imqbroker/fs370/message/Qjms_EmailQueue/vrfile
2) Pending incidents, scheduled reports and scheduled queries:
- the entry point of all types of messages which include incident, scheduled query/report, etc...
- /opt/glassfish/domains/domain1/imq/instances/imqbroker/fs370/message/Qjms_RequestQueue/vrfile
Solution Steps
Here are the steps for deleting the JMS queue.
NOTE: you will lose any pending notifications, incidents, scheduled reports/queries.
-
Open a SSH session to AO Super
-
Run 'cd /opt/glassfish/domains/domain1/imq/instances/imqbroker/fs370/message/Qjms_RequestQueue
-
Run 'rm –f vrfile'
-
Run 'cd /opt/glassfish/domains/domain1/imq/instances/imqbroker/fs370/message/Qjms_EmailQueue
-
Run 'rm –f vrfile'
-
restart appsvr
a) killall -9 java
Additional Resources
n/a
Caveats/Limitations
You will lose any pending notifications, incidents, scheduled reports/queries.
Version Application
All Versions
