[Messaging, JMS & JBossMQ] - jms messages table not deleting causing org.jboss.mq.SpyJMS
by renukhush
We have 2 instances of JBOSS 3.2.3 running on the same SUNmachine for an application. Both the server and client are running at all time. This problem happens randomaly and not very frequently. The oracle database is used for jms persistence store. Every 15 minutes around 100000 messages are being send. Its published to a topic. In the normal event the messages are publised and read by the subcriber very quickly.
But sometimes, for some reason, some of the messages are received by the topic subcriber but not all of them. The messages in the table keeps increasing and being cleared at a very slow rate. This makes the application literally inoperable and leads to loss of the data being collected.
Restarting the jboss, does not seems to solve the problem, as the error of duplicate key keeps happening again.
A workaround found by us, to remove the old jboss jms_message table and jms transaction table. Then the new tables are recreated and jboss restarted.
I have looked through all the forum and faq and getting find a suitable answer as why this is happening and what can be done for it.
There was one possible idea of using message exparition time, but this would cause us to loose data.
Any help is welcomed
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077123#4077123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077123
18Â years, 8Â months
[Messaging, JMS & JBossMQ] - jms messages table not deleting causing org.jboss.mq.SpyJMS
by renukhush
We have 2 instances of JBOSS 3.2.3 running on the same SUNmachine for an application. Both the server and client are running at all time. This problem happens randomaly and not very frequently. The oracle database is used for jms persistence store. Every 15 minutes around 100000 messages are being send. Its published to a topic. In the normal event the messages are publised and read by the subcriber very quickly.
But sometimes, for some reason, some of the messages are received by the topic subcriber but not all of them. The messages in the table keeps increasing and being cleared at a very slow rate. This makes the application literally inoperable and leads to loss of the data being collected.
Restarting the jboss, does not seems to solve the problem, as the error of duplicate key keeps happening again.
A workaround found by us, to remove the old jboss jms_message table and jms transaction table. Then the new tables are recreated and jboss restarted.
I have looked through all the forum and faq and getting find a suitable answer as why this is happening and what can be done for it.
There was one possible idea of using message exparition time, but this would cause us to loose data.
Any help is welcomed
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077122#4077122
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077122
18Â years, 8Â months
[JBoss AOP] - Re: dynamic cflow double call
by system.out
2 questions:
1 - As per section 10.4, by default the aop bindings are global to whole VM. What happens if aop is deployed after the deployments of ear? Would all aspectized ear be instrumented? If not, can it be enfoced to do so!
2 - Should section 10.4 (below) include 'deploy-hasingleton' folder beside 'deploy' folder?
anonymous wrote : 10.4. Scoping aop to the classloader
| By default all deployments in JBoss are global to the whole application server. That means that any ear, sar, jar etc. that is put in the deploy directory can see the classes from any other deployed archive. Similarly, aop bindings are global to the whole virtual machine. This "global" visibility can be turned off per top-level deployment.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077111#4077111
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077111
18Â years, 8Â months