Hi,
We have been experiencing this problem for sometime. We have this problem of jms messages getting stuck in the queue. When I restart the server the queues are cleared up and they are received. I'm not able to understand the reason why they periodically gets stuck in the queue and do not flow normally unless I have to restart the server.
Here is a error stacktrace from the log file that is thrown, but still I'm not able to identify if this is a code issue or something specific to the environment. Because first whenever I restart the server the queue is cleared up and also the app is running in other environments and the queue do not gets stuck. Can someone provide some light on this it will be highly appreciated.
<Oct 28, 2009 10:33:13 AM EST> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
javax.ejb.TransactionRolle
dbackLocal
Exception:
EJB Exception: ; nested exception is: java.lang.NullPointerExcep
tion.
javax.ejb.TransactionRolle
dbackLocal
Exception:
EJB Exception: ; nested exception is: java.lang.NullPointerExcep
tion
java.lang.NullPointerExcep
tion
javax.ejb.TransactionRolle
dbackLocal
Exception:
EJB Exception: ; nested exception is: java.lang.NullPointerExcep
tion
at weblogic.ejb20.internal.EJ
BRuntimeUt
ils.throwT
ransaction
Rolledback
Local(EJBR
untimeUtil
s.java:247
)
at weblogic.ejb20.internal.Ba
seEJBLocal
Home.handl
eSystemExc
eption(Bas
eEJBLocalH
ome.java:2
46)
at weblogic.ejb20.internal.Ba
seEJBLocal
Object.pos
tInvoke(Ba
seEJBLocal
Object.jav
a:326)
at com.cinr.otf.ejb20.RmProce
ssor_llw7x
m_ELOImpl.
execute(Rm
Processor_
llw7xm_ELO
Impl.java:
114)
at com.cinr.otf.ejb20.MPIPers
istenceMDB
.onMessage
(MPIPersis
tenceMDB.j
ava:75)
at weblogic.ejb20.internal.MD
Listener.e
xecute(MDL
istener.ja
va:370)
at weblogic.ejb20.internal.MD
Listener.o
nMessage(M
DListener.
java:262)
at weblogic.jms.client.JMSSes
sion.onMes
sage(JMSSe
ssion.java
:2678)
at weblogic.jms.client.JMSSes
sion.execu
te(JMSSess
ion.java:2
598)
at weblogic.kernel.ExecuteThr
ead.execut
e(ExecuteT
hread.java
:219)
at weblogic.kernel.ExecuteThr
ead.run(Ex
ecuteThrea
d.java:178
)
thank you