2:22 p.m.
Steve Kruse [http://community.jboss.org/people/hskruse] created the discussion
"Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607054#607054
--------------------------------------------------------------
Hi,
I am having problem creating a Queue that is used for my service and I'm not real sure
what the issue is. I have tried to recreate my jboss-service.xml file thinking it may be
corrupt but that doesn't seem to help. I don't understand either why the second
queue seems to be created fine but not the first(this can be seen in the log). Here is
the error I am getting, any help would be much appreciated.
jboss-service.xml that resides in the deployment directory:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.messaging.destination:service=Queue,name=com.ngc.fni.CommOutbound">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.messaging.destination:service=Queue,name=com.ngc.fni.CommInbound">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.messaging.destination:service=Queue,name=com.ngc.fni.QueueFeedback">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.messaging.destination:service=Queue,name=com.ngc.fni.QueueInbound">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
</server>
This is the exception I keep getting:
2011-05-25 08:48:46,158 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory]
(main) org.jboss.jms.server.connectionfactory.ConnectionFactory@4dab04cf started
2011-05-25 08:48:46,332 ERROR [org.jboss.messaging.util.ExceptionUtil] (main) Queue[null,
name=com.ngc.fni.CommOutbound] startService
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readUTF(DataInputStream.java:592)
at java.io.DataInputStream.readUTF(DataInputStream.java:547)
at org.jboss.messaging.util.StreamUtils.readMap(StreamUtils.java:313)
at
org.jboss.messaging.core.impl.JDBCPersistenceManager.bytesToMap(JDBCPersistenceManager.java:2317)
at
org.jboss.messaging.core.impl.JDBCPersistenceManager$1GetMessageListTX.doTransaction(JDBCPersistenceManager.java:577)
at
org.jboss.messaging.core.impl.JDBCPersistenceManager$1GetMessageListTX.doTransaction(JDBCPersistenceManager.java:497)
at
org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474)
at
org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512)
at
org.jboss.messaging.core.impl.JDBCPersistenceManager.getMessages(JDBCPersistenceManager.java:614)
at
org.jboss.messaging.core.impl.PagingChannelSupport.processReferences(PagingChannelSupport.java:565)
at
org.jboss.messaging.core.impl.PagingChannelSupport.doLoad(PagingChannelSupport.java:498)
at
org.jboss.messaging.core.impl.PagingChannelSupport.load(PagingChannelSupport.java:211)
at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:105)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
at $Proxy38.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at
org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at
org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
2011-05-25 08:48:46,348 INFO [org.jboss.jms.server.destination.QueueService] (main)
Queue[/queue/com.ngc.fni.QueueInbound] started, fullSize=200000, pageSize=2000,
downCacheSize=2000
2011-05-25 08:48:46,358 INFO
[org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound
ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI
name 'java:JmsXA'
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607054#607054]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:53 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Daniel Bevenius [http://community.jboss.org/people/beve] created the discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607101#607101
--------------------------------------------------------------
Hi Steve,
it looks like your server is running JBoss Messaging but you are configuring queues for
JBoss MQ.
If you take a look at the quickstart they have different configurations for JBoss
Messaging (jbm-queue-service.xml), JBoss MQ (jbmq-queue-service), and HornetQ
(hornetq-jms.xml). Take a look at the one for JBoss Messaging and modify it adding your
queues.
Regards,
/Daniel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607101#607101]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:14 p.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Steve Kruse [http://community.jboss.org/people/hskruse] created the discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607330#607330
--------------------------------------------------------------
Daniel,
Thanks for feedback, but my service file seems to work fine. I have three other queues
that get started without a problem, but the one, CommOutbound, always fails. If I rename
the queue to something else it will work as well. Is it possible that the old queue name
is got cached or stored somewhere that has become corrupt.
Thanks,
Steve
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607330#607330]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:11 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Hans Wolffenbuttel [http://community.jboss.org/people/h.wolffenbuttel] created the
discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607404#607404
--------------------------------------------------------------
did you check the contents of the queue that fails? It seems to me that the initialisation
crashes when the persistence manager is activated. So it could just be the contents of the
queue where your problem lies.
Hans
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607404#607404]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:02 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Steve Kruse [http://community.jboss.org/people/hskruse] created the discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607471#607471
--------------------------------------------------------------
Hans,
Thanks for the reply. I'm not sure what you mean by the contents of the queue. At
startup I don't believe there is anything in the queue. I actually renamed the queue
to CommOutbound1 and all is working fine. I'm not sure what the problem is, I guess I
could do a new install of Jboss and see if that clears up the issue.
Steve
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607471#607471]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:10 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Daniel Bevenius [http://community.jboss.org/people/beve] created the discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607475#607475
--------------------------------------------------------------
Hi Steve,
I have three other queues that get started without a problem, but the
one, CommOutbound, always fails.
Sorry about that, I should have read your post more
carefully.
So just by renaming your queue it worked?
I've not see this before but you could try clearing out your servers data, work, and
tmp directories just incase.
Regards,
/Daniel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607475#607475]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:17 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Steve Kruse [http://community.jboss.org/people/hskruse] created the discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607480#607480
--------------------------------------------------------------
Daniel,
I tried that as well but it didn't work...
Steve
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607480#607480]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:15 a.m.
New subject: [JBoss ESB Development] - Re: Problem creating Queue for use with ESB Service
Hans Wolffenbuttel [http://community.jboss.org/people/h.wolffenbuttel] created the
discussion
"Re: Problem creating Queue for use with ESB Service"
To view the discussion, visit: http://community.jboss.org/message/607702#607702
--------------------------------------------------------------
Hi Steve,
By contents of the queue I mean just that, otherwise the persistence manager wouldn't
have any problems with your queue. In short, if you are using Oracle for instance, you
could check your messaging tables. This can be found in
"jbossesb-server-4.9\server\default\deploy\jboss-messaging.sar" and checking the
xxx-persistence-service.xml. That's the only way to be sure that there's nothing
in your queue anymore.
You could also just drop your JBoss user (in Oracle at least) and set recreate tables in
your xxx-persistence-service.xml to true. This way your tables will be recreated from
scratch and you can find out if its a data problem or not.
Regards,
Hans
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607702#607702]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4959
days inactive
4964
days old
jboss-dev-forums@lists.jboss.org
7 comments
3 participants
participants (3)
-
Daniel Bevenius -
Hans Wolffenbuttel
-
Steve Kruse