[jboss-user] [EJB 3.0 Users] - Re: How do I define attributes in a service bean?
Jakiran, sorry for waiting your time. I am an eejit! I never put get/set in front of the attribute method calls. All working now. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4265749#4265749 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4265749 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0 Users] - How do I define attributes in a service bean?
Any methods I define in my Management Interface are displayed as operations. However I don't know how to define attributes. I have tried annotating the methods in question with @ManagementAttribute but they do not appear as attributes in the JMX console. Furthermore, how do I supply a description to the arguments of an operation or attribute? Thanks for your help. Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4265684#4265684 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4265684 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Howard, Got it sorted finally, you will be glad to hear that I have traced this problem down to faulty hardware. After two months of IT telling me the hardware was good I decided to rule it out and ran my own test across some desktops. Works perfectly, no faults. You should be able to close the JIRA you created. Later, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4255048#4255048 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4255048 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Microcontainer Users] - Declare a dependency on an MC bean
I'm trying to declare a dependency on the HornetQServer MC bean.
I took the name of the bean from the JMX Console to create the depends clause
but it does not work:
| @Depends(value={jboss.deployment:id=HornetQServer,type=Component})
|
This is the only reference I can find to HornetQServer in the JMX Console.
The HornetQ forum led me here, this was my original post
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254388#4254388
Could someone shed some light on this for me please?
Cheers,
Ross
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254394#4254394
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4254394
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Microcontainer Users] - Re: Declare a dependency on an MC bean
Apologies,
I was using a EJB3 Service Bean.
The solution by Jakiran works correctly and is as follows:
| @Service
| @Local(InputServiceBeanLocal.class)
| @Remote(InputServiceBeanRemote.class)
| @Management(InputServiceBeanManagement.class)
| @Depends(value={HornetQServer})
| public class InputServiceBean implements InputServiceBeanLocal,
InputServiceBeanRemote, InputServiceBeanManagement
| {
| ...
| }
|
How would you normally figure out what the correct name is for the MC Bean? Is
it simply the id values of the component from the JMX console?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254417#4254417
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4254417
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Microcontainer Users] - Re: Declare a dependency on an MC bean
Ok, so I looked in the -jboss-beans.xml file but every bean defined has a name. It's not easy to figure out which is the one I'm looking for. The new admin-console (which I'd never seen before), has absolutely no mention of HornetQServer, nor can I see any mention of micro-containers in the tree listing. Should it be there? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4254467#4254467 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4254467 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Microcontainer Users] - Re: Declare a dependency on an MC bean
I love it! I'll let them know the solution and they can add it to their WIKI, it'll save others the hassle of the search. Thanks a million, R. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4254477#4254477 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4254477 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: Bridge - Once and only once, connections failing after i
Howard, I'd like to raise another point on this issue. Every time this happens we simply restart each JBoss instance and it all starts working again. The main problem being that when the issue arises we cannot send messages to the local queue, so we essentially have lost these messages before we restart JBoss. Example: Box1: Just has a locally deployed queue Box2: Contains the remote queue we wish to send to and the bridge from the local queue on box1 to the remote queue here. When the bridge dies, we cannot send any messages to the local queue on box1. Surely we should always be able to send messages to the local queue on box1? The bridge should not be able to effect this action. If this happened then repairing the bridge would let messages be delivered to the remote queue once more with no loss of messages. I know you can't reproduce the error I'm getting but at least if all messages always made onto onto the local queue recovery would be possible. I think that a good rule of thumb would be: If the local queue is deployed correctly, it should always be possible to put messages on this queue. What do you think? Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4251036#4251036 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4251036 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.4 in AS5
Ok, you'll be glad to hear the memory leak was external to JMS. So I'm back to the problem where the bridges die after several hours idle time. I know I'm pushing on this, but I'd feel a lot better if I could see an 'Update JMessaging to 1.4.5.GA' task in the AS5 roadmap. Where would be an appropriate place to post on this? Cheers, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4250649#4250649 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4250649 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Messaging 1.4.4 in AS5
I've been keeping an eye on the AS5 roadmap and I still have not seen a task for incorporating Messaging 1.4.4 into AS5. Any idea when this might happen? I'm waiting on some fixes addressed in this release of messaging specifically to do with JMS Bridges. We cannot move to production until we have these fixes. I've tried building messaging 1.4.4 for AS5 but it does not work. Cheers, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249898#4249898 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249898 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.4 in AS5
Howard, that great news, I'd be interested to see how the remoting update effects the bridges. I'm having a strange issue where I'm running out of heap space that seems to be related to Bridges (If there not running there's no leak). Our dev environment is undergoing a rebuild at the moment but once it's back up I'll provide more info on memory leak if I can prove for sure that it's the bridges that are causing it. Cheers, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249988#4249988 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249988 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Howard, Here's another error for you. This ones a little different to the others but happens occasionally. | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.ServerInvoker] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) ServerInvoker (SocketServerInvoker[172.16.113.22:1241677967]) added client callback handler CallbackManager[15d09a2] with session id of 4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow and callback handle object of null. | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.InvokerRegistry] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) removed org.jboss.remoting.transport.local.localclientinvo...@bccf2c from registry | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) Session id for callback handler is 4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] using callbackTimeout value 1 | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[jbdevapp2:4457] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) DefaultCallbackErrorHandler[SocketServerInvoker[jbdevapp2:4457]] setting callback handler to ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) adding callback handler ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) found calllback handler for remoting session ...-fxcvn6ar-20ot UID=4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) registered connection ConnectionEndpoint[zo02-5b6nvcxf-1-1e2sbcxf-der9sr-m53gs4] as ...-fxcvn6ar-20ot | 2009-07-20 08:30:22,002 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) No SecurityMetadadata was available for phaseQueueToHandler, using default security config | 2009-07-20 08:30:22,013 DEBUG [org.jboss.remoting.Client] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) starting callback Connector: InvokerLocator [bisocket://172.16.113.22:640465832/callback?callbackServerHost=172.16.113.22callbackServerPort=640465832callbackServerProtocol=bisocketclientMaxPoolSize=1clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapperdatatype=jmsguid=4sg35m-rs9red-fxcbs2e1-1-fxcvn6bh-20p3isCallbackServer=trueonewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPoolserverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] | 2009-07-20 08:30:22,017 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-301) ServerInvoker (SocketServerInvoker[172.16.113.22:1340483958]) removing client callback handler with session id of 4sg35m-rs9red-fxcbs2e1-1-fxcvklqp-20gk+4sg35m-rs9red-fxcbs2e1-1-fxcvkq01-20gn. | 2009-07-20 08:30:22,020 DEBUG [org.jboss.remoting.ServerInvoker] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) SocketServerInvoker[172.16.113.22:640465832] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory. | 2009-07-20
[jboss-user] [EJB 3.0] - Re: ServiceBean and depends clause - Help Please
I added the following dependency using the jboss.xml file (which is in the META-INF directory in the EAR file): | ?xml version='1.0' encoding='UTF-8' ? | jboss | enterprise-beans | session | ejb-nameInputServiceBean/ejb-name | dependsjboss.j2ee:ear=phase-test.ear,jar=phase-input.jar,name=SourceBridgeCheckTimerBean,service=EJB3/depends | /session | /enterprise-beans | /jboss | And with the fully qualified class name for the service bean: | ?xml version='1.0' encoding='UTF-8' ? | jboss | enterprise-beans | session | ejb-namecom.paddypower.phase.input.bean.service.InputServiceBean/ejb-name | dependsjboss.j2ee:ear=phase-test.ear,jar=phase-input.jar,name=SourceBridgeCheckTimerBean,service=EJB3/depends | /session | /enterprise-beans | /jboss | But neither of these seems to work. The SourceBridgeCheckTimerBean always loads after the ServiceBean which would indicate that the depends clause has no effect. Am I specifying the ejb-name correctly? The depends clause is specified in the same way I used in the ServiceBean previously. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4243788#4243788 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243788 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: ServiceBean and depends clause - Help Please
Ok, the jboss.xml is definitely being picked up, so it must be the way I'm referencing the service bean is incorrect... | 2009-07-15 15:35:24,600 DEBUG [org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper] (HDScanner) Parsing file: zipentryhand...@12863780[path=phase-test.ear/META-INF/jboss.xml context=file:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/ real=file:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/phase-test.ear/META-INF/jboss.xml] for type: class org.jboss.metadata.ejb.jboss.JBossMetaData | | 2009-07-15 15:35:24,635 DEBUG [org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper] (HDScanner) Parsed file: zipentryhand...@12863780[path=phase-test.ear/META-INF/jboss.xmlcontext=file:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/ real=file:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/phase-test.ear/META-INF/jboss.xml] to: org.jboss.metadata.ejb.jboss.jboss50metad...@1f | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4243812#4243812 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243812 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hey Howard, Got a little further on figuring this out. What I did is write a keep alive generator for the bridges so I could monitor them. Each bridge has a timer bean which send a message across the bridge at 10 second interval. Unfortunately this did not stop the bridges from failing but did let me highlight the point where the bridge went down. | 2009-06-30 06:40:15,015 ERROR [org.jboss.remoting.transport.socket.ServerThread](WorkerThread#2[172.16.113.11:65011]) WorkerThread#2[172.16.113.11:65011] exception occurred during first invocation | | 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) Exception in thread Timer-3 | 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at java.util.TimerThread.run(Unknown Source) | 2009-06-30 06:44:43,967 ERROR [STDERR] (Timer-12) Exception in thread Timer-12 | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.run(Unknown Source) | 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) Exception in thread Timer-15 | 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 07:03:06,227 ERROR [STDERR] (Timer-15) at java.util.TimerThread.run(Unknown Source) | 2009-06-30 07:04:33,427 ERROR [org.jboss.jms.server.bridge.Bridge] (Thread-281) Failed to start source connection | Hopefully this will give you enough info to help pinpoint where the error occurs. If you have any ideas for further tests let me know. Cheers, R. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241122#4241122 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241122 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - ServiceBean and depends clause - Help Please
Ok,
I have a Service Bean in a jar file called: phase-input.jar
This jar also contains a stateless timer bean (SourceBridgeCheckTimerBean). The
service bean is dependent on the timer bean.
So when deploying this jar in it's own EAR file the @ depends clause in the
Service Bean looks like this:
| @Service
| @Local(InputServiceBeanLocal.class)
| @Remote(InputServiceBeanRemote.class)
| @Management(InputServiceBeanManagement.class)
|
@Depends(value={jboss.messaging.destination:service=Queue,name=phaseQueueToEngine,
|
jboss.j2ee:ear=phase-input.ear,jar=phase-input.jar,name=SourceBridgeCheckTimerBean,service=EJB3})
|
But this jar is supposed to be a service deployed on many different servers in
different applications.
When I create a new EAR called phase-test.ear the depends fails because the
clause should now look like this:
|
@Depends(value={jboss.messaging.destination:service=Queue,name=phaseQueueToEngine,
|
jboss.j2ee:ear=phase-test.ear,jar=phase-input.jar,name=SourceBridgeCheckTimerBean,service=EJB3})
|
I would need to recompile phase-input.jar to change this. In fact, I would need
to recompile it for every different EAR I want to add it to.
Furthermore, the JNDI name of the local interface to SourceBridgeCheckTimerBean
changes from this:
| phase-input/SourceBridgeCheckTimerBean/local
|
to
| phase-test/SourceBridgeCheckTimerBean/local
|
Two questions:
1) How do I put SourceBridgeCheckTimerBean into JNDI with a common name so no
matter what EAR it resides in I can call it in a common way (not another EJB,
I'm calling it in a POJO so have to do a JNDI lookup)?
2) Similarly, how do I depend on my timer bean in the Service bean no matter
what EAR file it's part of?
Note: there will only ever be one Input Service Bean on any JBoss instance.
Or is the solution to deploy my Input service bean in it's own jar directly
into the deploy directory. In this case can I access the service bean on the
local interface as it's not deployed in the same ear as the application?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240565#4240565
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240565
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Sorry about the delay in getting back to you. Here's the log from the box1, after the idle time. It seems that the remoting session etc. is found. Spot anything interesting? The second log extract is from box2 when I try to redeploy one of the bridges. | 2009-06-19 09:43:40,373 DEBUG [org.jboss.remoting.Client] (http-0.0.0.0-8080-1) starting callback Connector: InvokerLocator [bisocket://172.16.113.11:871825415/callback?callbackServerHost=172.16.113.11callbackServerPort=871825415callbackServerProtocol=bisocketclientMaxPoolSize=1clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapperdatatype=jmsguid=4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jqisCallbackServer=trueonewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPoolserverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory. | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] created server socket factory javax.net.defaultserversocketfact...@87bf5 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] setting pingFrequency to 214748364 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] setting pingWindowFactor to 10 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.Connector] (http-0.0.0.0-8080-1) org.jboss.remoting.transport.connec...@1117568 started | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) ServerInvoker (SocketServerInvoker[172.16.113.11:871825415]) added client callback handler CallbackManager[12d3d44] with session id of 4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr and callback handle object of null. | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.InvokerRegistry] (http-0.0.0.0-8080-1) removed org.jboss.remoting.transport.local.localclientinvo...@1e3ba17 from registry | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-1) Session id for callback handler is 4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-1) ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr] using callbackTimeout value 1 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-1) DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[jbdevapp1:4457] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-1) DefaultCallbackErrorHandler[SocketServerInvoker[jbdevapp1:4457]] setting callback handler to ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (http-0.0.0.0-8080-1) adding callback handler ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr]
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
I have tested all cases and the only way to recover from these errors is to restart both boxes. I will write a keep alive packet running from a timer and see does it fix the issue. I have added the following to jboss-log4j.xml. Howard, should this be sufficient to see further into the User null is NOT authenticated error? Or do I need to trace other packages as well? Maybe security too? | !-- ENABLE TRACE LEVEL LOGGING FOR JMS -- |category name=org.jboss.jms | priority value=TRACE/ |/category | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237670#4237670 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237670 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Ok so if I have this to trace: |category name=org.jboss.jms | priority value=TRACE/ |/category | |category name=org.jboss.remoting | priority value=TRACE/ |/category | I havn't added security as I think it's under the jms package. If it's something else just post the package name for me and I'll add it in. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237705#4237705 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237705 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Howard, Are you running the bridge across two physically different boxes? I have the default JMS Provider (localhost) and a remote JMS Provider to a separate box with a different IP Address. If your remote provider is also localhost you might not see the issue. Here are my JMS providers (jms-ds.xml): | ?xml version=1.0 encoding=UTF-8? | | connection-factories | | !-- -- | !-- JMS Stuff -- | !-- -- | |!-- |The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to |be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available. |See http://jira.jboss.org/jira/browse/JBMESSAGING-843. |-- |mbean code=org.jboss.jms.jndi.JMSProviderLoader | name=jboss.messaging:service=JMSProviderLoader,name=JMSProvider | attribute name=ProviderNameDefaultJMSProvider/attribute | attribute name=ProviderAdapterClassorg.jboss.jms.jndi.JNDIProviderAdapter/attribute | attribute name=FactoryRefjava:/XAConnectionFactory/attribute | attribute name=QueueFactoryRefjava:/XAConnectionFactory/attribute | attribute name=TopicFactoryRefjava:/XAConnectionFactory/attribute |/mbean | |mbean code=org.jboss.jms.jndi.JMSProviderLoader | name=jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider | attribute name=ProviderNameRemoteJMSProvider/attribute | attribute name=ProviderAdapterClass | org.jboss.jms.jndi.JNDIProviderAdapter | /attribute | attribute name=FactoryRef/XAConnectionFactory/attribute | attribute name=QueueFactoryRef/XAConnectionFactory/attribute | attribute name=TopicFactoryRef/XAConnectionFactory/attribute | attribute name=Properties | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://jbdevapp1:1099 | /attribute |/mbean | |!-- JMS XA Resource adapter, use this to get transacted JMS in beans -- |tx-connection-factory | jndi-nameJmsXA/jndi-name | xa-transaction/ | rar-namejms-ra.rar/rar-name | connection-definitionorg.jboss.resource.adapter.jms.JmsConnectionFactory/connection-definition | config-property name=SessionDefaultType type=java.lang.Stringjavax.jms.Topic/config-property | config-property name=JmsProviderAdapterJNDI type=java.lang.Stringjava:/DefaultJMSProvider/config-property | max-pool-size20/max-pool-size | security-domain-and-applicationJmsXARealm/security-domain-and-application | dependsjboss.messaging:service=ServerPeer/depends |/tx-connection-factory | | /connection-factories | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237486#4237486 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237486 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Another point, I ran the same test again. But this time I tried to re-deploy the bridges on box2 (before trying anything else). Strange thing is I get exactly the same errors as if I restarted box1. So now I restart box2, but still the same errors. The User null is NOT authenticated error seems to be a coverall for many different types of error. Is there anyway to see the logging at a finer grain to try and find out why this error is being thrown. Tomorrow I will try restarting box1 after idle before I try to send 100 messages. And the following day I will do the same but restart box 2. The only situation I've found so far that fixes the issue is to completely restart both jboss instances. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237488#4237488 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237488 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: 5.1.0.GA and Messaging 1.4.4 samples doesn't works
5.1.0.GA comes with Messaging 1.3. It's probably why the 1.4 examples fail to work. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4235826#4235826 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4235826 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Serious idle problem with Bridges on AS 5.1.0.Beta
I had previously reported a problem with idle timeouts on bridges: http://www.jboss.org/index.html?module=bbop=viewtopict=154559 In my previous post I had stated that this problem only occurred with QOS_ONCE_AND_ONLY_ONCE bridges. However it would appear that this is not the case. After extensive testing it also occurs with QOS_DUPLICATES_OK. This issue is a show stopper for us as we cannot move our application to production if this issue still exists. I have 3 questions related to this: | 1) Has anyone else encountered this problem | 2) Are there any planned fixes for this issue | 3) When possibly could we expect to see this issue fixed in an AS5 release (as we cannot build messaging ourseleves to work with AS5, we've tried but it just doesn't work!). | | | Using QOS_DUPLICATES_OK in our test scenario we have a box (box1) that sends messages and another that hosts the bridge file and receives them (box2). | | The bridge file on box2 looks like this: | | | | mbean code=org.jboss.jms.server.bridge.BridgeService name=jboss.messaging:service=Bridge,name=InputToEngineBridge xmbean-dd=xmdesc/Bridge-xmbean.xml | | | | depends optional-attribute-name=SourceProviderLoaderjboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider/depends | | depends optional-attribute-name=TargetProviderLoaderjboss.messaging:service=JMSProviderLoader,name=JMSProvider/depends | | | | attribute name=SourceDestinationLookup/queue/phaseQueueToEngine/attribute | | attribute name=TargetDestinationLookup/queue/phaseQueueFromInput/attribute | | | | !-- Optional: The Quality Of Service mode to use, one of: | |QOS_AT_MOST_ONCE = 0; | |QOS_DUPLICATES_OK = 1; | |QOS_ONCE_AND_ONLY_ONCE = 2;-- | | attribute name=QualityOfServiceMode1/attribute | | | | attribute name=MaxBatchSize1/attribute | | attribute name=MaxBatchTime-1/attribute | | attribute name=FailureRetryInterval5000/attribute | | attribute name=MaxRetries-1/attribute | | attribute name=AddMessageIDInHeaderfalse/attribute | | /mbean | | | | After an idle period of 16 hours (jboss running but no messages are sent), box1 attempts to send 100 messages. The following error occurs on box1: | | | | 2009-06-07 13:23:58,655 ERROR [org.jboss.messaging.util.ExceptionUtil] (http-0.0.0.0-8080-6) ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] createFailoverConnectionDelegate [8f41-nq47qnvf-1-yyggvmuf-g3h4ce-b53gs4] | | javax.jms.JMSSecurityException: User null is NOT authenticated | | at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) | | at sun.reflect.GeneratedMethodAccessor926.invoke(Unknown Source) | | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | | at java.lang.reflect.Method.invoke(Unknown Source) | | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | | at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) | | at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) | | at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) | | at javax.management.StandardMBean.invoke(Unknown Source) | | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | | at $Proxy108.authenticate(Unknown Source) | | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) | | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) | | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | | at
[jboss-user] [JBoss Messaging] - Re: JBoss 1.4.4.GA in AS5
bodrin, You have to wait for 1.4.4.GA to be released with AS 5. You cannot build it yourself. I have tried this on many occasions and it does not work. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4234623#4234623 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234623 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - JBoss 1.4.4.GA in AS5
Any idea when this release will make into JBoss AS5? We are waiting on some of the bugs fixed in this release. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4234079#4234079 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4234079 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge - Once and only once, connections failing after i
No problem, thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4229960#4229960 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4229960 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge - Once and only once, connections failing after i
Any info on this issue? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4229754#4229754 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4229754 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge - Once and only once, connections failing after i
From machine 1 to machine2: | mbean code=org.jboss.jms.server.bridge.BridgeService name=jboss.messaging:service=Bridge,name=InputToEngineBridge xmbean-dd=xmdesc/Bridge-xmbean.xml | | depends optional-attribute-name=SourceProviderLoaderjboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider/depends | depends optional-attribute-name=TargetProviderLoaderjboss.messaging:service=JMSProviderLoader,name=JMSProvider/depends | | attribute name=SourceDestinationLookup/queue/speQueueToEngine/attribute | !-- attribute name=SourceUsernameguest/attribute | attribute name=SourcePasswordguest/attribute -- | attribute name=TargetDestinationLookup/queue/speQueueFromInput/attribute | !-- attribute name=TargetUsernameguest/attribute | attribute name=TargetPasswordguest/attribute -- | | !-- Optional: The Quality Of Service mode to use, one of: |QOS_AT_MOST_ONCE = 0; |QOS_DUPLICATES_OK = 1; |QOS_ONCE_AND_ONLY_ONCE = 2;-- | attribute name=QualityOfServiceMode2/attribute | | attribute name=MaxBatchSize1/attribute | attribute name=MaxBatchTime-1/attribute | attribute name=FailureRetryInterval5000/attribute | attribute name=MaxRetries-1/attribute | attribute name=AddMessageIDInHeaderfalse/attribute | /mbean | | From machine2 to machine1: | mbean code=org.jboss.jms.server.bridge.BridgeService name=jboss.messaging:service=Bridge,name=EngineToHandlerBridge xmbean-dd=xmdesc/Bridge-xmbean.xml | | depends optional-attribute-name=SourceProviderLoaderjboss.messaging:service=JMSProviderLoader,name=JMSProvider/depends | depends optional-attribute-name=TargetProviderLoaderjboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider/depends | | attribute name=SourceDestinationLookup/queue/speQueueToHandler/attribute | !-- attribute name=SourceUsernameguest/attribute | attribute name=SourcePasswordguest/attribute -- | attribute name=TargetDestinationLookup/queue/speQueueFromEngine/attribute | !-- attribute name=TargetUsernameguest/attribute | attribute name=TargetPasswordguest/attribute -- | | !-- Optional: The Quality Of Service mode to use, one of: |QOS_AT_MOST_ONCE = 0; |QOS_DUPLICATES_OK = 1; |QOS_ONCE_AND_ONLY_ONCE = 2;-- | attribute name=QualityOfServiceMode2/attribute | | attribute name=MaxBatchSize1/attribute | attribute name=MaxBatchTime-1/attribute | attribute name=FailureRetryInterval5000/attribute | attribute name=MaxRetries-1/attribute | attribute name=AddMessageIDInHeaderfalse/attribute | /mbean | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4227825#4227825 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227825 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge - Once and only once, connections failing after i
Oh, and I'm using 1.4.3.GA of messaging. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4227563#4227563 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227563 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge - Once and only once, connections failing after idle
Since getting QOS_ONCE_AND_ONLY_ONCE bridges up and running I have run into an issue with the bridge failing after a period of idle time. I'm not sure exactly what amount of time is required to cause the fail but if I send no messages overnight the failure occurs the next time I send messages. I should point out that if I send messages consistently over the night the problem does not occur. Nor does it occur if I use QOS_DUPLICATES_OK or QOS_AT_MOST_ONCE even if there is idle time. Here the setup: Machine1: no bridge deployed here, Machine2: 2 Bridges deployed here. InputToEngineBridge takes messages from machine1 and transports them to a queue on machine2. EngineToHandlerBridge takes messages from machine2 and transports them to a queue on machine1. The User null is NOT authenticated error seems to pop up a lot but does not give much insight into what is going wrong. Any ideas on how I might debug this further and get to the root of the problem? Bear in mind I have to wait overnight each time I want to test it again. Error on machine1: | 2009-04-29 09:41:51,920 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-2) Session id for callback handler is 4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rb-4by+4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rk-4c1 | 2009-04-29 09:41:51,920 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-2) ServerInvokerCallbackHandler[4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rb-4by+4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rk-4c1] using callbackTimeout value 1 | 2009-04-29 09:41:51,920 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-2) DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[jbdevapp1:4457] | 2009-04-29 09:41:51,921 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-2) DefaultCallbackErrorHandler[SocketServerInvoker[jbdevapp1:4457]] setting callback handler to ServerInvokerCallbackHandler[4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rb-4by+4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rk-4c1] | 2009-04-29 09:41:51,921 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (http-0.0.0.0-8080-2) adding callback handler ServerInvokerCallbackHandler[4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rb-4by+4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rk-4c1] | 2009-04-29 09:41:51,921 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (http-0.0.0.0-8080-2) found calllback handler for remoting session ...-fu3s39rb-4by UID=4sg35b-lwxf6y-fu2oi7qk-1-fu3s39rb-4by | 2009-04-29 09:41:51,923 ERROR [org.jboss.messaging.util.ExceptionUtil] (http-0.0.0.0-8080-2) ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] createFailoverConnectionDelegate [4c4-nr93s3uf-1-kq7io2uf-y6fxwl-b53gs4] | javax.jms.JMSSecurityException: User null is NOT authenticated | at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) | at sun.reflect.GeneratedMethodAccessor301.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) | at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) | at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) | at javax.management.StandardMBean.invoke(Unknown Source) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy102.authenticate(Unknown Source) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at
[jboss-user] [EJB 3.0] - Re: Deployment error using Service beans
My jboss-app.xml is as follows:
| jboss-app
| loader-repository
| spe-test:archive=spe-test.ear
| /loader-repository
| /jboss-app
|
Here are the annotations used in the service bean:
| import javax.ejb.Local;
| import javax.ejb.Remote;
|
| import org.jboss.ejb3.annotation.Management;
| import org.jboss.ejb3.annotation.Service;
|
| @Service (objectName = spe-input:service=inputServiceBean)
| @Local(InputServiceBeanLocal.class)
| @Remote(InputServiceBeanRemote.class)
| @Management(InputServiceBeanManagement.class)
| public class InputServiceBean implements InputServiceBeanLocal,
InputServiceBeanRemote, InputServiceBeanManagement
|
InputServiceBeanLocal:
| public interface InputServiceBeanLocal
| {
|void start() throws Exception;
|void stop();
|
| }
|
InputServiceBeanRemote:
| public interface InputServiceBeanRemote
| {
|void start() throws Exception;
|void stop();
|
| }
|
InputServiceBeanManagement:
| public interface InputServiceBeanManagement
| {
|void create() throws Exception;
|void start() throws Exception;
|void stop();
|void destroy();
|String update(int val);
| }
|
|
So I removed the objectName attribute of the @Service annotation. But it did
not make much difference.
New service bean annotations:
| import javax.ejb.Local;
| import javax.ejb.Remote;
|
| import org.jboss.ejb3.annotation.Management;
| import org.jboss.ejb3.annotation.Service;
|
| @Service
| @Local(InputServiceBeanLocal.class)
| @Remote(InputServiceBeanRemote.class)
| @Management(InputServiceBeanManagement.class)
| public class InputServiceBean implements InputServiceBeanLocal,
InputServiceBeanRemote, InputServiceBeanManagement
|
My console log is now the following (first deploy):
| 12:31:44,010 INFO [SessionSpecContainer] Starting
jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
| 12:31:44,058 INFO [EJBContainer] STARTED EJB:
org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName:
SecureProfileService
| 12:31:44,080 INFO [JndiSessionRegistrarBase] Binding the following Entries
in Global JNDI:
|
| SecureProfileService/remote - EJB3.x Default Remote Business
Interface
|
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService -
EJB3.x Remote Business Interface
|
| 12:31:44,365 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
| 12:31:44,537 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
| 12:31:44,580 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build:
SVNTag=JBoss_5_1_0_Beta1 date=200903131506)] Started in 1m:2s:388ms
| 13:00:08,726 INFO [Ejb3DependenciesDeployer] Encountered deployment
abstractvfsdeploymentcont...@3695434{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 13:00:08,740 INFO [Ejb3DependenciesDeployer] Encountered deployment
abstractvfsdeploymentcont...@3695434{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 13:00:08,849 INFO [JBossASKernel] Created KernelDeployment for:
spe-input.jar
| 13:00:08,849 INFO [JBossASKernel] installing bean:
jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
| 13:00:08,850 INFO [JBossASKernel] with dependencies:
| 13:00:08,850 INFO [JBossASKernel] and demands:
| 13:00:08,850 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 13:00:08,850 INFO [JBossASKernel] and supplies:
| 13:00:08,850 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 13:00:08,850 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 13:00:08,850 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 13:00:08,850 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 13:00:08,850 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote
| 13:00:08,850 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
| 13:00:08,850 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
| 13:00:08,850 INFO [JBossASKernel] Added
bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3)
to KernelDeployment of: spe-input.jar
| 13:00:08,977 INFO [JBossASKernel] installing bean:
jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface
| 13:00:08,977 INFO [JBossASKernel] with dependencies:
| 13:00:08,977 INFO [JBossASKernel] and demands:
| 13:00:08,977 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
[jboss-user] [EJB 3.0] - Re: Deployment error using Service beans
Thanks for looking into this. Hopefully a fix will make it into the next release. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226948#4226948 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226948 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - JMS Bridge - MaxBatchTime not working
I'm using the 5.1.0 beta release of AS5 Previously I had been using the following in my bridge configuration: | attribute name=MaxBatchSize1/attribute | attribute name=MaxBatchTime-1/attribute | This worked but was very inefficient so I changed to this: | attribute name=MaxBatchSize20/attribute | attribute name=MaxBatchTime200/attribute | If I send 23 messages, only 20 get transported across the bridge. I must send another 17 before the left over 3 get sent. There is jira issue related to this: https://jira.jboss.org/jira/browse/JBMESSAGING-1186 A fix never seemed to be implemented for this. Note that unlike the above issue the remaining messages are never sent until the maxBatchSize is reached again. We will stick with a batch size of 1 as this is a suitable workaround in the short term on our production server. Any ideas greatly appreciated. Cheers, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226954#4226954 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226954 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge - MaxBatchTime not working
So I guess my next question is what are the chances of 1.4.4 being in the next AS5 release. The performance improvements of being able to send batches of messages are to much to ignore in our production environment. Should I be asking this question here or is there somewhere better to ask this? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226979#4226979 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226979 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge - MaxBatchTime not working
Only as far as 1.4.3.GA for messaging in the 5.1.0 Beta of AS5 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226980#4226980 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226980 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge - MaxBatchTime not working
Thanks Howard. I'll keep my eye on the roadmap and cross my fingers! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4227008#4227008 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227008 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge - Cannot get once and only once working
I am using the latest beta release 5.1.0.Beta of AS5. On the previous stable release there was a bug with bridges where a bridge would not correctly deploy on startup of JBoss. This issue no longer exists on the beta. I have a bridge setup between two different physical machines. Everything works fine once the QualityOfServiceMode in the bridge configuration is set to QOS_AT_MOST_ONCE or QOS_DUPLICATES_OK. If I set QualityOfServiceMode to QOS_ONCE_AND_ONLY_ONCE then I get the following error: | 2009-04-21 12:59:49,157 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.jmsactivations...@12324c2(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@a5061b destination=queue/speQueueDownstreamIn destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=6 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.jms.JMSSecurityException: User null is NOT authenticated | at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source) | at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) | at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) | at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) | at javax.management.StandardMBean.invoke(Unknown Source) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy109.authenticate(Unknown Source) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) | at org.jboss.remoting.Client.invoke(Client.java:1708) | at org.jboss.remoting.Client.invoke(Client.java:612) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_8584105.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_8584105.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) | at
[jboss-user] [JBoss Messaging] - Best way to pause delivery of messages on a queue
I have a situation whereby it would be helpful to be able to stop delivery of messages on a queue but still allows client to add messages to the queue in question. I see that there is a stopDelivery method in the JMSContainerInvokerMBean. Will calling this stop delivery and still allow clients to add messages to the queue? Is is this the same as the stop command in the JMX console? If it is then it would stop messages being added to the queue. In this case is there another way to do this? Thanks, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4227017#4227017 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227017 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Best way to pause delivery of messages on a queue
1.4.3.GA, comes with the 5.1.0 Beta of AS 5. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4227116#4227116 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227116 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Best way to pause delivery of messages on a queue
I'm using MDB's so I won't have direct access to the connection.
I simply want the MDB to stop firing onMessage until I tell the queue to start
delivering again (without stopping clients from sending messages to the queue).
I have the following code for JMSContainerInvokerMBean (it's in the package
(org.jboss.ejb.plugins.jms):
| MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
| JMSContainerInvokerMBean invoker;
| try
| {
| invoker = (JMSContainerInvokerMBean) MBeanProxy.get(
|JMSContainerInvokerMBean.class, objectName, mbeanServer);
| if (method == STOP)
| {
| invoker.stopDelivery();
| }
| else if (method == START)
| {
| invoker.startDelivery();
| }
| }
| catch( Exception e)
| {
| e.printStackTrace();
| }
|
Would the JMX forum be a better place to ask this question? Unfortunately the
documentation is not very informative concerning the method calls above.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227140#4227140
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227140
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Deployment error using Service beans
If I remove a service bean jar from an ears application.xml and redeploy, I get deployment errors for the missing jar file as if it should still exist. Here's the first ear I deploy: | ?xml version=1.0 encoding=UTF-8? | application xmlns=http://java.sun.com/xml/ns/javaee; | xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; version=5 | xsi:schemaLocation=http://java.sun.com/xml/ns/javaee | http://java.sun.com/xml/ns/javaee/application_5.xsd; | display-nameSPE Test/display-name | | module | web | web-urispe-test.war/web-uri | context-root/spe-test/context-root | /web | /module | | module | ejbspe-test.jar/ejb | /module | | module | ejbspe-input.jar/ejb | /module | | library-directorylib/library-directory | | /application | Then if I remove spe-input.jar from the ear file and change this file to reflect this change and redeploy: | ?xml version=1.0 encoding=UTF-8? | application xmlns=http://java.sun.com/xml/ns/javaee; | xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; version=5 | xsi:schemaLocation=http://java.sun.com/xml/ns/javaee | http://java.sun.com/xml/ns/javaee/application_5.xsd; | display-nameSPE Test/display-name | | module | web | web-urispe-test.war/web-uri | context-root/spe-test/context-root | /web | /module | | module | ejbspe-test.jar/ejb | /module | | library-directorylib/library-directory | | /application | I get this error: | DEPLOYMENTS MISSING DEPENDENCIES: | Deployment spe-input:service=inputServiceBean is missing the following dependencies: | Dependency UNKNOWN spe-input:service=inputServiceBean (should be in state Described, but is actually in state ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **) | | DEPLOYMENTS IN ERROR: | Deployment UNKNOWN spe-input:service=inputServiceBean is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' ** | Surely the jar I removed from the ear should be undeployed as it no longer exists as part of the ear? The only way to stop the error is to either restart JBoss or add the jar back into the ear and deploy it again. I'd be gratefult of any insight into this. Thanks, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226848#4226848 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226848 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Deployment error using Service beans
I'm using the latest beta release 5.1.0.Beta.
Here are the console logs:
First deploy including service bean jar:
| 10:59:37,526 INFO [SessionSpecContainer] Starting
jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
| 10:59:37,591 INFO [EJBContainer] STARTED EJB:
org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName:
SecureProfileService
| 10:59:37,633 INFO [JndiSessionRegistrarBase] Binding the following Entries
in Global JNDI:
|
| SecureProfileService/remote - EJB3.x Default Remote Business
Interface
|
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService -
EJB3.x Remote Business Interface
|
| 10:59:38,439 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
| 10:59:38,526 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
| 10:59:38,556 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build:
SVNTag=JBoss_5_1_0_Beta1 date=200903131506)] Started in 1m:7s:429ms
| 11:00:50,949 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
| 11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment
abstractvfsdeploymentcont...@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment
abstractvfsdeploymentcont...@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 11:00:51,726 INFO [JBossASKernel] Created KernelDeployment for:
spe-input.jar
| 11:00:51,726 INFO [JBossASKernel] installing bean:
jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
| 11:00:51,726 INFO [JBossASKernel] with dependencies:
| 11:00:51,726 INFO [JBossASKernel] and demands:
| 11:00:51,726 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 11:00:51,726 INFO [JBossASKernel] and supplies:
| 11:00:51,726 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,726 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,726 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,726 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,726 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote
| 11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
| 11:00:51,726 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
| 11:00:51,726 INFO [JBossASKernel] Added
bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3)
to KernelDeployment of: spe-input.jar
| 11:00:51,814 INFO [JBossASKernel] installing bean:
spe-input:service=inputServiceBean
| 11:00:51,814 INFO [JBossASKernel] with dependencies:
| 11:00:51,814 INFO [JBossASKernel] and demands:
| 11:00:51,814 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 11:00:51,814 INFO [JBossASKernel]
jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
| 11:00:51,814 INFO [JBossASKernel] and supplies:
| 11:00:51,814 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,814 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,814 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,814 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,814 INFO [JBossASKernel]
jndi:spe-test/InputServiceBean/remote
| 11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
| 11:00:51,814 INFO [JBossASKernel]
Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
| 11:00:51,814 INFO [JBossASKernel] Installing
bean(spe-input:service=inputServiceBean) into kernel
| 11:00:51,817 INFO [STDOUT] InputBeanService - Creating
| 11:00:51,818 INFO [EJBContainer] STARTED EJB:
com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
| 11:00:51,845 INFO [JndiSessionRegistrarBase] Binding the following Entries
in Global JNDI:
|
| spe-test/InputServiceBean/remote - EJB3.x Default Remote Business
Interface
|
spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
- EJB3.x Remote Business Interface
| spe-test/InputServiceBean/local - EJB3.x Default Local Business
Interface
|
spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
-
[jboss-user] [JBoss Messaging] - Re: Bridge - Cannot get once and only once working
I suppose it's always true that until you ask a question you never figure out the answer yourself! I had forgotten to change the ServerPeerID to a different value on one of the servers. Just a quick change to deploy/messaging-service.xml and it works! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226898#4226898 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226898 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Service Bean - Strange behaviour on redeploy
Because for the moment message order is critical, and allows us to design/test both source and destination systems knowing that message order is preserved. Eventually we will use MDB's (for performance reasons) but they will still need to be sorted/processed at a central location, which will most likely be a service bean in our case. Regardless of this fact, the issue clearly lies in that a service bean behaves differently depending on whether it is deployed for the first time or it is redeployed. This should not be the case, surely behaviour should be the same in either instance? I guess the question I really want to ask is, is this a bug? Has anyone seen this type of behaviour before? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4215154#4215154 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4215154 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Service Bean that depends on two queues
I have two queues A and B, and I want my service bean to be dependent on these two queues. So my depends clause looks like this but it's wrong: | @Depends(jboss.messaging.destination:service=Queue,name=A,jboss.messaging.destination:service=Queue,name=B) | My service bean is working fine and runs correctly once I deploy it after JBoss is started. What would be the correct argument to my depends clause. Thanks, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214807#4214807 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4214807 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Service Bean that depends on two queues
|mbean code=org.jboss.jms.server.destination.QueueService | name=jboss.messaging.destination:service=Queue,name=A | xmbean-dd=xmdesc/Queue-xmbean.xml | depends optional-attribute-name=ServerPeerjboss.messaging:service=ServerPeer/depends | dependsjboss.messaging:service=PostOffice/depends |/mbean | |mbean code=org.jboss.jms.server.destination.QueueService | name=jboss.messaging.destination:service=Queue,name=B | xmbean-dd=xmdesc/Queue-xmbean.xml | depends optional-attribute-name=ServerPeerjboss.messaging:service=ServerPeer/depends | dependsjboss.messaging:service=PostOffice/depends |/mbean | | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214834#4214834 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4214834 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Service Bean that depends on two queues
Perfect thanks! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214838#4214838 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4214838 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Service Bean - Strange behaviour on redeploy
I have a service bean, that spawns a thread, which reads messages from one queue and sends them out on another. The thread is correctly stopped in both the stop and destroy methods of the bean. Everything works as expected if it's a fresh startup of JBoss or the service bean is deployed for the first time. But when I re-deploy the service bean message receives are intermittent. I can see the messages that never get consumed in the MySQL DB. Restarting Jboss solves this problem. I'm running this on AS5.0.0.GA. Has anyone else had a similar problem or have any solution to this. For the moment the solution is to restart JBoss every time I redeploy the bean. P.S. I don't see any error messages in the log indicating there is a problem. However after a number of deploys I sometimes get a debug message Thread pool class supplied is not an object name. The following is the log when I send 10 messages to the queue. As you can see from the log only 4 messages are received (and there are only 7 responses (line delimited) in the log from the 10 sends I do). The other 6 are still in the DB. If I then restart JBoss the remaining 6 messages are read and the behaviour is once more normal. | 2009-03-04 12:21:52,544 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config | | 2009-03-04 12:22:07,998 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config | | 2009-03-04 12:22:08,011 DEBUG [org.jboss.remoting.ServerInvoker] (WorkerThread#0[172.16.66.231:59737]) Thread pool class supplied is not an object name. | 2009-03-04 12:22:08,014 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived | 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Received message | 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Routing to DS | 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Time to test: 1236169328058 | 2009-03-04 12:22:08,016 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (Thread-48) No SecurityMetadadata was available for speQueueDownstreamOut, using default security config | | 2009-03-04 12:22:34,902 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config | | 2009-03-04 12:22:39,365 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#0[172.16.66.231:59737]) No SecurityMetadadata was available for speQueueEngineIn, using default security config | 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived | 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) Received message | 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) Routing to DS | 2009-03-04 12:22:39,380 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:39,380 INFO [STDOUT] (Thread-48) Time to test: 1236169359426 | 2009-03-04 12:22:39,380 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (Thread-48) No SecurityMetadadata was available for speQueueDownstreamOut, using default security config | | 2009-03-04 12:22:47,535 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived | 2009-03-04 12:22:47,535 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Received message | 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Routing to DS | 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Time to test: 1236169367584 | | 2009-03-04 12:22:55,115 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived | 2009-03-04 12:22:55,115 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Received message | 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Routing to DS | 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) | 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Time to test: 1236169375163 | A similar thread runs fine from a servlet with no problems even after redeploy. Hence the reason I'm posting this in the EJB3.0 forum. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214872#4214872 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4214872 ___ jboss-user mailing list
[jboss-user] [JBoss Messaging] - User null is NOT authenticated
On AS5.0.0.GA we occasionally get an error when we startup jboss on two different boxes when there is a bridge between them. Here's the course of events: 1) Start both JBoss instances (on physically different boxes, no clustering) 2) Redeploy the bridge on one server (bug in this release) 3) and we get the ERROR below. The strange thing is that the only way to get this error to go away is to restart both servers and deploy the bridge again. If we remove the bridge file so it's not there on startup and deploy once startup is complete, we will never get the error below. Just making you guys aware of this. | 2009-03-03 12:11:18,423 WARN [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=TestBridge,service=Bridge Failed to set up connections | javax.jms.JMSSecurityException: User null is NOT authenticated | at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) | at sun.reflect.GeneratedMethodAccessor402.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(Unknown Source) | at javax.management.StandardMBean.invoke(Unknown Source) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy110.authenticate(Unknown Source) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206) | at org.jboss.remoting.Client.invoke(Client.java:1708) | at org.jboss.remoting.Client.invoke(Client.java:612) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_5452358.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_5452358.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:128) | at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:123) | at org.jboss.jms.server.bridge.Bridge.createConnection(Bridge.java:859) | at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:958) | at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1166) | at
[jboss-user] [EJB 3.0] - Can't inject resource when not using Servlet
I have several servlets and can inject properties easily like follows: @Resource(name=ConnectionFactory, mappedName=ConnectionFactory) private ConnectionFactory connectionFactory; @Resource(name=queue/out, mappedName=queue/out) private Destination out; But if I try to use a simple POJO and inject the resources it fails to work. I know the solution to this must be simple but for the life of me I can't find the answer. Thanks, Ross View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214197#4214197 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4214197 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Programatically create RemoteJMSProviders, Queues and Bridge
Is this even possible? We have a situation where a client wants to be able to dynamically create new destinations, bridges etc. If it is possible could someone point me in the right direction as to how to do this? Cheers View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4209473#4209473 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4209473 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Is it possible to inject a Remote bean in a client servlet?
I'm using a remote bean from a servlet to make a remote call. The code snippet
below works. But I'm wondering is it possible to inject this bean without
needing to do the remote JNDI lookup.
When using JMS I setup a RemoteJMSProvider and can inject both the connection
factory and destination queue from a servlet (I'm using the web 2.5 spec).
Is something similar possible with EJB's? Or am I stuck with the JNDI lookup
code. Maybe some kind of mbean provider where I can specify the remote machine
IP?
Cheers,
Ross
P.S. I've commented out the @EJB annotation as it does nothing.
| //@EJB
| private MyTestBeanRemote remoteBean;
|
| protected void doGet(HttpServletRequest request,
| HttpServletResponse response) throws ServletException,
IOException {
|
| try {
| Properties properties = new Properties();
| properties.put(Context.INITIAL_CONTEXT_FACTORY,
|
org.jnp.interfaces.NamingContextFactory);
| properties.put(Context.URL_PKG_PREFIXES,
| org.jboss.naming:org.jnp.interfaces);
| properties.put(Context.PROVIDER_URL, jnp://172.16.8.52:1099);
|
| Context ctx = new InitialContext(props);
| remoteBean = (MyTestBeanRemote)
ctx.lookup(TestEAR/MyTestBeanRemote/remote);
|
|
| } catch (Exception ex) {
| System.out.println(Could not create bean. +
| ex.getMessage());
| }
|
| if (remoteBean != null) remoteBean.doSomething();
| }
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208628#4208628
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208628
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
How should I supply the test program and configuration? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207996#4207996 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207996 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Nope, that's what I checked first. The point I'm at now, if I shutdown AS5 and replace the two libraries with the originals, the bridge will work (sending messages to a machine on a different subnet). If I then change to the libraries I built I get a host of errors which you can see in my previous posts. Here'e my JMS-ds.xml (The IP Address of the machine this is deployed on is 172.16.66.230): | ?xml version=1.0 encoding=UTF-8? | | connection-factories | | !-- -- | !-- JMS Stuff -- | !-- -- | |!-- |The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to |be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available. |See http://jira.jboss.org/jira/browse/JBMESSAGING-843. |-- |mbean code=org.jboss.jms.jndi.JMSProviderLoader | name=jboss.messaging:service=JMSProviderLoader,name=JMSProvider | attribute name=ProviderNameDefaultJMSProvider/attribute | attribute name=ProviderAdapterClassorg.jboss.jms.jndi.JNDIProviderAdapter/attribute | attribute name=FactoryRefjava:/XAConnectionFactory/attribute | attribute name=QueueFactoryRefjava:/XAConnectionFactory/attribute | attribute name=TopicFactoryRefjava:/XAConnectionFactory/attribute |/mbean | | mbean code=org.jboss.jms.jndi.JMSProviderLoader | name=jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider | attribute name=ProviderNameRemoteJMSProvider/attribute | attribute name=ProviderAdapterClass | org.jboss.jms.jndi.JNDIProviderAdapter | /attribute | attribute name=FactoryRef/XAConnectionFactory/attribute | attribute name=QueueFactoryRef/XAConnectionFactory/attribute | attribute name=TopicFactoryRef/XAConnectionFactory/attribute | attribute name=Properties | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://172.16.8.52:1099 | /attribute | /mbean | |!-- JMS XA Resource adapter, use this to get transacted JMS in beans -- |tx-connection-factory | jndi-nameJmsXA/jndi-name | xa-transaction/ | rar-namejms-ra.rar/rar-name | connection-definitionorg.jboss.resource.adapter.jms.JmsConnectionFactory/connection-definition | config-property name=SessionDefaultType type=java.lang.Stringjavax.jms.Topic/config-property | config-property name=JmsProviderAdapterJNDI type=java.lang.Stringjava:/DefaultJMSProvider/config-property | max-pool-size20/max-pool-size | security-domain-and-applicationJmsXARealm/security-domain-and-application | dependsjboss.messaging:service=ServerPeer/depends |/tx-connection-factory | | /connection-factories | The only thing I can be sure of at the moment is that the new libraries I built do not work. Although I should point out that I have left the remote instance using the new libraries. It would be fairer to say that the new libraries do not work with bridges to remote locations. Another question if I might, why is jboss-messaging not tested against AS5? I will investigate this further tomorrow and supply anything further I find out. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207965#4207965 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207965 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
If I startup AS5 with the new libraries the error is as follows: | 2009-02-08 00:25:26,836 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.jmsactivations...@1195c94(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@4eaead destination=queue/speQueueB destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=6 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.naming.NameNotFoundException: speQueueB not bound | at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) | at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) | at org.jnp.server.NamingServer.getObject(NamingServer.java:785) | at org.jnp.server.NamingServer.lookup(NamingServer.java:443) | at org.jnp.server.NamingServer.lookup(NamingServer.java:399) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673) | at javax.naming.InitialContext.lookup(Unknown Source) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) | at java.lang.Thread.run(Unknown Source) | As you can see from the error it is attempting to connect to the speQueueB using the DefaultJMSProvider, where it should be using the RemoteJMSProvider. If I then redeploy the bridge I don't get an error. But once I try to send a message I get the error from post above: | 2009-02-06 21:38:02,087 ERROR [org.jboss.messaging.util.ExceptionUtil] (Thread-47) ConnectionEndpoin | t[3g-zukpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] sendTransaction [ig-bvkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] | javax.jms.JMSException: Failed to route Reference[20217139725713415]:RELIABLE to speQueueB | So there is a startup bug where the wrong provider is used for the remote queue. And another where once redeployed message delivery fails. I can see that once the bridge is redeployed that a connection is made to the remote instance. There are still null references in the log as you can see from the post above. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207966#4207966 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207966 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
I've built the libraries for AS5, once more everything works locally and so does the bridge but only locally. If the bridge is connecting to a remote server then we once more have problems. If I kill the remote jboss instance that the bridge points too it behaves as you expect: | 2009-02-06 20:50:38,957 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections | javax.naming.CommunicationException: Could not obtain connection to any of these urls: 172.16.8.52:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server 172.16.8.52:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused]]] | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1727) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:680) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673) | at javax.naming.InitialContext.lookup(Unknown Source) | at org.jboss.jms.server.bridge.JNDIFactorySupport.createObject(JNDIFactorySupport.java:66) | at org.jboss.jms.server.bridge.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:45) | at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:939) | at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1206) | at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:68) | at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1552) | at java.lang.Thread.run(Unknown Source) | Caused by: javax.naming.CommunicationException: Failed to connect to server 172.16.8.52:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused]] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:311) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1698) | ... 10 more | Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:281) | ... 11 more | Caused by: java.net.ConnectException: Connection refused | at java.net.PlainSocketImpl.socketConnect(Native Method) | at java.net.PlainSocketImpl.doConnect(Unknown Source) | at java.net.PlainSocketImpl.connectToAddress(Unknown Source) | at java.net.PlainSocketImpl.connect(Unknown Source) | at java.net.SocksSocketImpl.connect(Unknown Source) | at java.net.Socket.connect(Unknown Source) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:277) | ... 11 more | 2009-02-06 20:50:38,958 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections, will retry after a pause of 5000 ms | But once this instance is available then neither of the queue's appear to be bound as far as the bridge is concerned (speQueue is local, speQueueB is remote): | 2009-02-06 20:49:03,329 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-33) null Failed to set up connections | javax.naming.NameNotFoundException: speQueueB not bound | at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) | at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) | at org.jnp.server.NamingServer.getObject(NamingServer.java:785) | at org.jnp.server.NamingServer.lookup(NamingServer.java:443) | at org.jnp.server.NamingServer.lookup(NamingServer.java:399) | at sun.reflect.GeneratedMethodAccessor266.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) | at sun.rmi.transport.Transport$1.run(Unknown Source) | at java.security.AccessController.doPrivileged(Native Method) | at sun.rmi.transport.Transport.serviceCall(Unknown Source) | at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) | at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) | at java.lang.Thread.run(Unknown Source) | at
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Hmm, this is strange. If I create a queue call speQueueB on the instance running the bridge, then the bridge will forward the messages to this queue instead of attempting to move it to the remote queue? Here's the bridge config: | mbean code=org.jboss.jms.server.bridge.BridgeService name=jboss.messaging:service=Bridge,name=TestBridge xmbean-dd=xmdesc/Bridge-xmbean.xml | | depends optional-attribute-name=SourceProviderLoaderjboss.messaging:service=JMSProviderLoader,name=JMSProvider/depends | depends optional-attribute-name=TargetProviderLoaderjboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider/depends | | attribute name=SourceDestinationLookup/queue/speQueue/attribute | attribute name=TargetDestinationLookup/queue/speQueueB/attribute | attribute name=QualityOfServiceMode2/attribute | attribute name=MaxBatchSize1/attribute | attribute name=MaxBatchTime-1/attribute | attribute name=FailureRetryInterval5000/attribute | attribute name=MaxRetries-1/attribute | attribute name=AddMessageIDInHeaderfalse/attribute | /mbean | Why would the bridge deliver locally? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207862#4207862 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207862 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
If I now delete speQueueB on the local bridge instance it will now attempt to deliver the message: | 2009-02-06 21:38:02,087 ERROR [org.jboss.messaging.util.ExceptionUtil] (Thread-47) ConnectionEndpoint[3g-zukpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] sendTransaction [ig-bvkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] | javax.jms.JMSException: Failed to route Reference[20217139725713415]:RELIABLE to speQueueB | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:757) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:815) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeTarget(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) | at org.jboss.remoting.Client.invoke(Client.java:1708) | at org.jboss.remoting.Client.invoke(Client.java:612) | at org.jboss.remoting.Client.invoke(Client.java:600) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeTarget(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java) | at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:662) | at org.jboss.jms.tx.ResourceManager.commit(ResourceManager.java:367) | at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:254) | at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:800) | at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2639) | at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1784) | at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88) | at com.arjuna.ats.arjuna.AtomicAction.end(AtomicAction.java:216) | at
[jboss-user] [JBoss Messaging] - Upgrading AS5 to use messaging 1.4.2.GA
What is the correct procedure for upgrading messaging on AS5? I've copied both jboss-messaging.jar and jboss-messaging-client.jar to there correct locations and copied the xml files to the deploy/messaging folder. I can produce and consume messages on the same instance but my bridge is not working. I repeatedly get the log message: | 2009-02-05 13:39:47,617 INFO [org.jboss.jms.server.bridge.Bridge] (Thread-314) null Succeeded in reconnecting to servers | 2009-02-05 13:39:47,618 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-44) Thread pool class supplied is not an object name. | 2009-02-05 13:39:47,619 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] (Thread-42) No SecurityMetadadata was available for speQueueEnd, using default security config | 2009-02-05 13:39:47,619 ERROR [org.jboss.messaging.util.ExceptionUtil] (Thread-42) ConnectionEndpoint[0d5-kep6htqf-1-9qtjgtqf-o95xms-e6u1gs4] sendTransaction [fd5-rep6htqf-1-9qtjgtqf-o95xms-e6u1gs4] | javax.jms.JMSException: Failed to route Reference[20215254017949969]:RELIABLE to speQueueEnd | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:757) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:815) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) | at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) | at org.jboss.remoting.Client.invoke(Client.java:1708) | at org.jboss.remoting.Client.invoke(Client.java:612) | at org.jboss.remoting.Client.invoke(Client.java:600) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java) | at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:662) |
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
I had working version of jboss messaging but need to upgrade for fixes to the following issues. https://jira.jboss.org/jira/browse/JBMESSAGING-999 I have tried just replacing the jars and the xml files from the download on the site. If these jars are not compiled for AS5 and they need to be that might explain why the bridge fails to work correctly. As I pointed out messaging works correctly within a local instance of JBoss. The problems begin once I try to use a bridge. How do you normally upgrade messaging in AS5? There must be some procedure for doing so, how else would you test it normally with AS5? Building the jars myself is not a problem, but if they cannot be built for AS5 I'm unsure as to how to continue... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207446#4207446 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207446 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Are YOURDB-persistence-service.xml and remoting-bisocket-service.xml the only config files I need to worry about? Previously I used the updated connections, destinations and messaging-service xml files from the release I downloaded. Should I revert to the copies of those files from the original AS5 download and only update the persistence and remoting-bisocket files? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207502#4207502 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207502 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge Deployment Failures: queue not bound on AS startup, r
If I start jboss AS 5, my bridge will not deploy as it would appear that the local queue is created after the attempt to start the bridge. If I then touch the bridge configuration once jboss has started, the bridge starts ok (In this case the remote node is up and running). Is there some way I can make the bridge deployment be dependent on the local queue being active? | 2009-02-04 13:50:20,790 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | *** CONTEXTS IN ERROR: Name - Error | | jboss.messaging:name=TestBridge,service=Bridge - javax.naming.NameNotFoundException: queue not bound | The other problem I have is that if the remote node is not running when I deploy the bridge after startup, deployment fails and so the bridge never starts. Surely the bridge should start regardless of the state of the other node, and connect when the node becomes available? My bridge configuration is as follows: | mbean code=org.jboss.jms.server.bridge.BridgeService name=jboss.messaging:service=Bridge,name=TestBridge xmbean-dd=xmdesc/Bridge-xmbean.xml | | depends optional-attribute-name=SourceProviderLoaderjboss.messaging:service=JMSProviderLoader,name=JMSProvider/depends | depends optional-attribute-name=TargetProviderLoaderjboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider/depends | | attribute name=SourceDestinationLookup/queue/speQueue/attribute | attribute name=TargetDestinationLookup/queue/speQueueEnd/attribute | attribute name=QualityOfServiceMode2/attribute | attribute name=MaxBatchSize1/attribute | attribute name=MaxBatchTime-1/attribute | attribute name=FailureRetryInterval5000/attribute | attribute name=MaxRetries-1/attribute | attribute name=AddMessageIDInHeaderfalse/attribute | /mbean | Once the bridge is up and running everything is fine. The remote node can appear/disappear all it wants and the bridge delivers messages everytime the remote node becomes available. Any help appreciated, thanks Ross View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4206984#4206984 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4206984 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge Deployment Failures: queue not bound on AS startu
So this is a solution to the second issue, does it also fix the first one? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4206993#4206993 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4206993 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Tomcat, HTTPD, Servlets JSP] - JBoss Transactions in AS5.0.0.GA
We recently moved from JBoss AS 4.0.5.GA to AS 5.0.0.GA and have begun testing
our applications. The first problem I'm having is to do with transactions. In
4.0.5.GA there are no issues, but in the new version I'm getting the following
exception:
java.lang.IllegalStateException: Can't lock a TransactionLocal after the
Transaction has ended
followed by the following:
2008-12-18 13:22:34,505 ERROR
[org.jboss.web.tomcat.service.jca.CachedConnectionValve] (http-0.0.0.0-8080-2)
Application error: action did not complete its transaction suspended
tx=TransactionImple ac, BasicAction: 7f01:e47f:49491afc:a32 status:
ActionStatus.COMMITTED
If I try to start another transaction after these errors I get a null pointer
exception. The transaction completes successfully on all DB's. Has something
changed drastically between the 2 AS releases? Any help would be greatly
appreciated.
Code is like this:
| TransactionManager transactionManager =
TransactionManagerLocator.getInstance().locate();
| Transaction transaction = null;
|
| try
| {
| //Begin the transaction and then get the transaction...
| transactionManager.begin();
| transaction = transactionManager.getTransaction();
|
| //Update on DB1
| //Update on DB2
| //Update on DB3
|
| transaction.commit();
| }
| catch(Exception e)
| {
| try
| {
| transaction.rollback();
| }
| catch (SystemException se)
| {
| log.debug(se);
| }
|
| }
| finally
| {
| try
| {
| //close all resources
| }
| catch(SQLException se)
| {
| log.error(SQLException: + se);
| }
| }
|
|
Stack trace as follows:
| 2008-12-18 13:22:32,437 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager]
(http-0.0.0.0-8080-2) Unable to synchronize with transaction
| java.lang.IllegalStateException: Can't lock a TransactionLocal after the
Transaction has ended
| at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:226)
| at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:109)
| at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:222)
| at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:545)
| at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:303)
| at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:720)
| at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:362)
| at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:155)
| at
com.paddypower.shopwallet.db.MultipleDatabaseDAO.performTransaction(MultipleDatabaseDAO.java:286)
| at
com.paddypower.shopwallet.action.WalletLDAction.performTransaction(WalletLDAction.java:589)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at
org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:266)
| at
org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:167)
| at
org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchAction.java:143)
| at
org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:53)
| at
org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:64)
| at
org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:48)
| at
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:190)
| at
org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:304)
| at
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:190)
| at
org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:280)
| at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1858)
| at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:459)
| at
[jboss-user] [Tomcat, HTTPD, Servlets JSP] - Re: JBoss Transactions in AS5.0.0.GA
That did the trick! Thanks! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4197591#4197591 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4197591 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
