[JBoss Cache Users] - InstanceAlreadyExistsException During hot deployment
by pavnesh
I am currently using JBOSS Cache v3.3.1GA with Websphere 6.1.0.21, JPA, Hibernate3.3, Spring 2.5.6. During development, we have hot deployed the application. So whever I make any change in the java code, code gets hot deployment on the server and I get the exception javax.management.InstanceAlreadyExistsException.
| javax.management.InstanceAlreadyExistsException: jboss.cache:service=TreeCache-Cluster,cell=TD2471Node01Cell,node=TD2471Node01,process=server1
| at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:470)
| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1428)
| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:954)
| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:355)
| at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:515)
| at com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:472)
| at org.jboss.cache.util.MBeanConfigurator.registerInterceptors(MBeanConfigurator.java:72)
| at org.jboss.cache.TreeCache._createService(TreeCache.java:1385)
| at org.jboss.cache.TreeCache.startService(TreeCache.java:1463)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:173)
| at org.hibernate.cache.TreeCacheProvider.start(TreeCacheProvider.java:75)
|
When I restart the server, it starts working fine. This process goes on whever we make any code change. Any help/clue with be highly appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257137#4257137
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257137
16 years, 7 months
[jBPM Users] - Hibernate, Sessions, and Sync - Oh my!
by michaelholtzman
Greetings -
We are plagued with StaleObjectStateExceptions that I have been unable to resolve. We are running jBPM (derived from version 3.1.2) in an application which launches and manages our workflows and also executes commands targetting specific workflow instances (for example, a signal from our main application, an external system wrt the jBPM app).
We have a number of custom nodes that call out to our system and enter a wait state. Our system processes the request and sends back a command to the jbpm application. The command will include the process instance and token that made the request, and possibly data that will be saved in jbpm instance variables.
Our custom nodes use the JbpmContext attached to the current ExecutionContext. The 'out of band' command processing creates a new JbpmContext from a singleton JbpmConfiguration, loads the specified token by id and modifies it, then saves and closes the JbpmContext.
In general this works great, but I have one case that consistently causes SOSE's:
A custom node (Wait) creates a timer with a 10 second due date. When the timer fires, it transitions to a custom node (Script) that messages our system and goes into a wait state. Our system responds with a 'Results' command that essentially does this:
| gProcessInstance = jbpmContext.loadProcessInstance(gProcessInstanceId);
| if (gProcessInstance == null)
| throw new Exception("Unable to load process instance id " + gProcessInstanceId);
|
| if (gTokenId > 0) {
| gToken = jbpmContext.loadToken(gTokenId);
| } else {
| gToken = gProcessInstance.getRootToken();
| }
|
| // Get new JbpmContext from static configuration
| jbpmContext = Manager.jbpmConfiguration.createJbpmContext();
| try {
| // Set some instance variables
| ...
|
| // Save and close the jbpmContext
| jbpmContext.save(gToken);
| } catch (Exception e) {
| ...
| } finally {
| jbpmContext.close();
| }
|
Usually this works correctly, advancing the token from the 'Script' node to the next node in the process. However, sometimes the signal advances the token from the 'Wait' node -- the token's previous node. The next execution of jbpmContext.close() throws the SOSE.
My theory du jour is that somehow the transition in the workflow from 'Wait' to 'Script' has not been committed at the time the 'Result' command arrives, so that the loadToken() call is getting the state of the token before it moved to the 'Script' node and the Token.getNode() is returning the wrong node as the source of the transition.
I have tried adding
| jbpmContext.save(token);
| jbpmContext.getSession().flush();
|
when the 'Wait' and 'Script' nodes go into their respective wait states, as well as inserting
| jbpmContext.getSession().refresh(gToken)'
|
after loading the token, but the problem persists.
Any ideas?
Thanx.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257134#4257134
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257134
16 years, 7 months
[JBoss Cache Users] - Re: 2 JBoss Cache questions
by userjboss99
Hi Manik,
Thanks for the reply...here is my info:
1) yes, the Java client is using the same JGroups stack as the appserver (essentially just the jbossall-client.jar, jbosscache-core.jar and jgroups.jar files found in the JBoss server distribution). This is all under JBoss 5.1.0.GA.
Also, if it helps, I'm running my client application with the following system properties to help it try to join the JGroups channel (though running with or without these properties doesn't seem to make any difference for me):
| -Djgroups.udp.mcast_addr=228.1.2.3 -Djgroups.mping.mcast_port=39472 -Djgroups.udp.mcast_port=34972 -Djgroups.bind_addr=10.1.0.22
|
2) here's the thread dump:
|
| Full thread dump Java HotSpot(TM) Server VM (11.2-b01 mixed mode):
|
| "DestroyJavaVM" prio=10 tid=0x7627b000 nid=0x1317 waiting on condition [0x00000000..0xb7f51070]
| java.lang.Thread.State: RUNNABLE
|
| "Timer-4,10.1.0.22:34975" daemon prio=10 tid=0x762ff400 nid=0x1334 waiting on condition [0x75cba000..0x75cbae30]
| java.lang.Thread.State: TIMED_WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0xaed041a0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
| at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
| at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
| at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "Timer-3,10.1.0.22:34975" daemon prio=10 tid=0x75e1c800 nid=0x1333 waiting on condition [0x75d0b000..0x75d0c0b0]
| java.lang.Thread.State: TIMED_WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0xaed041a0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
| at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
| at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
| at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "OOB-1,10.1.0.22:34975" prio=10 tid=0x09fcc400 nid=0x1332 waiting on condition [0x75d5c000..0x75d5d130]
| java.lang.Thread.State: WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0xaed07f78> (a java.util.concurrent.SynchronousQueue$TransferStack)
| at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
| at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:422)
| at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:323)
| at java.util.concurrent.SynchronousQueue.take(SynchronousQueue.java:857)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "Timer-2,10.1.0.22:34975" daemon prio=10 tid=0x762b7c00 nid=0x1331 waiting on condition [0x75dad000..0x75dadfb0]
| java.lang.Thread.State: TIMED_WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0xaed041a0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
| at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
| at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
| at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "UDP mcast,10.1.0.22:34975" prio=10 tid=0x762ea800 nid=0x1330 runnable [0x75dfe000..0x75dff030]
| java.lang.Thread.State: RUNNABLE
| at java.net.PlainDatagramSocketImpl.receive0(Native Method)
| - locked <0xaed40628> (a java.net.PlainDatagramSocketImpl)
| at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
| - locked <0xaed40628> (a java.net.PlainDatagramSocketImpl)
| at java.net.DatagramSocket.receive(DatagramSocket.java:712)
| - locked <0xaedec960> (a java.net.DatagramPacket)
| - locked <0xaed405f0> (a java.net.MulticastSocket)
| at org.jgroups.protocols.UDP.run(UDP.java:262)
| at java.lang.Thread.run(Thread.java:619)
|
| "UDP ucast,10.1.0.22:34975" prio=10 tid=0x75e0a400 nid=0x132f runnable [0x75f5c000..0x75f5ceb0]
| java.lang.Thread.State: RUNNABLE
| at java.net.PlainDatagramSocketImpl.receive0(Native Method)
| - locked <0xaed3ff40> (a java.net.PlainDatagramSocketImpl)
| at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
| - locked <0xaed3ff40> (a java.net.PlainDatagramSocketImpl)
| at java.net.DatagramSocket.receive(DatagramSocket.java:712)
| - locked <0xaedc39f0> (a java.net.DatagramPacket)
| - locked <0xaed3f938> (a java.net.DatagramSocket)
| at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:946)
| at java.lang.Thread.run(Thread.java:619)
|
| "DiagnosticsHandler,10.1.0.22:34975" daemon prio=10 tid=0x762a8400 nid=0x132e runnable [0x75fad000..0x75fadf30]
| java.lang.Thread.State: RUNNABLE
| at java.net.PlainDatagramSocketImpl.receive0(Native Method)
| - locked <0xaed4be90> (a java.net.PlainDatagramSocketImpl)
| at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
| - locked <0xaed4be90> (a java.net.PlainDatagramSocketImpl)
| at java.net.DatagramSocket.receive(DatagramSocket.java:712)
| - locked <0xaed9b2f8> (a java.net.DatagramPacket)
| - locked <0xaed4be40> (a java.net.MulticastSocket)
| at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2199)
| at java.lang.Thread.run(Thread.java:619)
|
| "FD_SOCK server socket acceptor,null" daemon prio=10 tid=0x762fd400 nid=0x132d runnable [0x75ffe000..0x75ffedb0]
| java.lang.Thread.State: RUNNABLE
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| - locked <0xaed3f0d8> (a java.net.SocksSocketImpl)
| at java.net.ServerSocket.implAccept(ServerSocket.java:453)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.jgroups.protocols.FD_SOCK$ServerSocketHandler.run(FD_SOCK.java:1022)
| at java.lang.Thread.run(Thread.java:619)
|
| "Timer-1,10.1.0.22:34975" daemon prio=10 tid=0x762b8400 nid=0x132c waiting on condition [0x7615c000..0x7615ce30]
| java.lang.Thread.State: TIMED_WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0xaed041a0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
| at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
| at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
| at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "RMI Scheduler(0)" daemon prio=10 tid=0x76237400 nid=0x1327 waiting on condition [0x761ad000..0x761ae130]
| java.lang.Thread.State: TIMED_WAITING (parking)
| at sun.misc.Unsafe.park(Native Method)
| - parking to wait for <0x7b662188> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
| at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
| at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
| at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
| at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
| at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
| "GC Daemon" daemon prio=10 tid=0x76231400 nid=0x1326 in Object.wait() [0x761fe000..0x761fefb0]
| java.lang.Thread.State: TIMED_WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| - waiting on <0x7b61d6f8> (a sun.misc.GC$LatencyLock)
| at sun.misc.GC$Daemon.run(GC.java:100)
| - locked <0x7b61d6f8> (a sun.misc.GC$LatencyLock)
|
| "RMI RenewClean-[10.1.0.22:1098]" daemon prio=10 tid=0x76278800 nid=0x1325 in Object.wait() [0x76665000..0x76666030]
| java.lang.Thread.State: TIMED_WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| - waiting on <0x7b61d000> (a java.lang.ref.ReferenceQueue$Lock)
| at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
| - locked <0x7b61d000> (a java.lang.ref.ReferenceQueue$Lock)
| at sun.rmi.transport.DGCClient$EndpointEntry$RenewCleanThread.run(DGCClient.java:516)
| at java.lang.Thread.run(Thread.java:619)
|
| "Low Memory Detector" daemon prio=10 tid=0x09dacc00 nid=0x1322 runnable [0x00000000..0x00000000]
| java.lang.Thread.State: RUNNABLE
|
| "CompilerThread1" daemon prio=10 tid=0x09daac00 nid=0x1321 waiting on condition [0x00000000..0x76a5a268]
| java.lang.Thread.State: RUNNABLE
|
| "CompilerThread0" daemon prio=10 tid=0x09da8000 nid=0x1320 waiting on condition [0x00000000..0x76adb2e8]
| java.lang.Thread.State: RUNNABLE
|
| "Signal Dispatcher" daemon prio=10 tid=0x09da6800 nid=0x131f waiting on condition [0x00000000..0x00000000]
| java.lang.Thread.State: RUNNABLE
|
| "Finalizer" daemon prio=10 tid=0x09d93000 nid=0x131e in Object.wait() [0x76d7d000..0x76d7e130]
| java.lang.Thread.State: WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| - waiting on <0x7b61d930> (a java.lang.ref.ReferenceQueue$Lock)
| at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
| - locked <0x7b61d930> (a java.lang.ref.ReferenceQueue$Lock)
| at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
| at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
|
| "Reference Handler" daemon prio=10 tid=0x09d91800 nid=0x131d in Object.wait() [0x76dce000..0x76dcefb0]
| java.lang.Thread.State: WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| - waiting on <0x7b61d6f0> (a java.lang.ref.Reference$Lock)
| at java.lang.Object.wait(Object.java:485)
| at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
| - locked <0x7b61d6f0> (a java.lang.ref.Reference$Lock)
|
| "VM Thread" prio=10 tid=0x09d8e400 nid=0x131c runnable
|
| "GC task thread#0 (ParallelGC)" prio=10 tid=0x09cf1400 nid=0x1318 runnable
|
| "GC task thread#1 (ParallelGC)" prio=10 tid=0x09cf2c00 nid=0x1319 runnable
|
| "GC task thread#2 (ParallelGC)" prio=10 tid=0x09cf4000 nid=0x131a runnable
|
| "GC task thread#3 (ParallelGC)" prio=10 tid=0x09cf5800 nid=0x131b runnable
|
| "VM Periodic Task Thread" prio=10 tid=0x09dae800 nid=0x1323 waiting on condition
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257126#4257126
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257126
16 years, 7 months
[JBoss Remoting Users] - JNDI Lookup Fails, Causes Failed EJB2 MDB
by mmichalek
I'm not exactly sure where to post this one, but since most of the relevant log shows jboss remoting code, I'll start here.
I'm trying to deploy an EJB 2 MDB to JBoss 4.2.3.
Here are the points of interest:
JBoss Messaging 1.4.4
JBoss Remoting 2.2.3
ear deployment Isolated=true
Here's some of my initial findings:
1) If I turn off ear deployment isolation, this problem goes away (and apparently remoting is not used for the lookup in that scenerio.)
2) From this log and looking at the source, it looks like a JNDI lookup for java:/StdJMSPool is failing (returning null) - but I don't understanding why that's happening.
Let me know if you have any ideas. It's important to me to get make the ear deployment isolation work.
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.ejb.plugins.jms.JMSContainerInvoker] looking up session pool factory: java:/StdJMSPool
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] unregistered connection ConnectionEndpoint[l3-c3gw510g-1-cy6v510g-ys6ooo-7375o4c5] with remoting session ID ...-g015wfyk-3f
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@4b2199 from registry
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[12933527:5c4o5737-ooo6sy-g015v6yc-1-g015wg3c-3k] is disconnected
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.jms.server.remoting.JMSServerInvocationHandler] removing callback handler ServerInvokerCallbackHandler[5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f+5c4o5737-ooo6sy-g015v6yc-1-g015wg3c-3i]
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[9099123:5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f].connect(null)
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[9099123:5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f] connected to InvokerLocator [bisocket://192.168.187.115:2088433572/callback?callbackServerHost=192.168.187.115&callbackServerPort=2088433572&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3h&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) removing client callback handler with session id of 5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f+5c4o5737-ooo6sy-g015v6yc-1-g015wg3c-3i.
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] unrecognized listener ID: 5c4o5737-ooo6sy-g015v6yc-1-g015wg3c-3i
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@146c67a from registry
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[9099123:5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f] is disconnected
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] stopped
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.InvokerRegistry] decremented org.jboss.remoting.transport.local.LocalClientInvoker@da85fe's count, current count 5
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[8486630:5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3f] is disconnected
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.InvokerRegistry] decremented org.jboss.remoting.transport.local.LocalClientInvoker@93133e's count, current count 5
| 12:43:23,640 DEBUG [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.remoting.Client] Client[28468394:5c4o5737-ooo6sy-g015v6yc-1-g015wfyk-3g] is disconnected
| 12:43:23,640 ERROR [JMSContainerInvoker(OfflineEventLogConsumerMDB) Reconnect] [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for OfflineEventLogConsumerMDB
| org.jboss.deployment.DeploymentException: Error during topic setup; - nested throwable: (java.lang.NullPointerException)
| at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:825)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1533)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.NullPointerException
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.createSessionPool(JMSContainerInvoker.java:1276)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:770)
| ... 2 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257120#4257120
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257120
16 years, 7 months