[Messaging, JMS & JBossMQ] - HAJNDIJMSProvider mbean not installed
by shaileshhp
HiI am using Jboss messaging bridge. I am getting following exception when server is started:
-jasre/jboss-4.0.5.GA/server/all/deploy/vertice-ear-0.0.5.30-SNAPSHOT.ear
11:26:11,962 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.messaging:service=Bridge,name=TestBridge
State: CONFIGURED
I Depend On:
jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider
jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider
State: NOTYETINSTALLED
Depends On Me:
jboss.messaging:service=Bridge,name=TestBridge
The source for the bridge is Tibco Topic and target is Queue. I have used JmsXA connetion factory for source Queue. Not sure why the above error is coming. Any suggestions will be really helpful.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165375#4165375
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165375
17 years, 9 months
[EJB 3.0] - Re: Using quartz from EJB 3.0
by henk53
"jaikiran" wrote : anonymous wrote : I would like to get the Quartz scheduler.
|
| How do you deploy the quartz scheduler? Does it get bound in the JNDI? If yes, then you can inject it using the @Resource annotation and the mappedName attribute:
|
Thanks for your suggestion. Currently I haven't set up anything yet. I've used Quartz a lot in plain web applications (Tomcat based) and I also made some simple EJB3 applications.
Recently the requirement came up to schedule jobs programmatically from within EJB3 beans. Since I've never combined the two before, I wondered what the best approach was.
What you basically mean is that I deploy Quartz within a separate web application, bind it to JNDI from there and pick it up through JNDI again from the EJB3 side?
If I did that, I probably can't give the scheduler a job class name of code that lives within the EJB3 container, since the scheduler then lives within another container (a web container). I could circumvent this perhaps by having a job class at the web container side that calls the EJB3 container again.
Is such a scheme what you're aiming at, or did you mean something else?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165372#4165372
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165372
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: Upgrading from 4.0.4 to 4.2.2
by PeterJ
As far as I know there is no migration guide. To migrate, do this:
1) If you changed any existing configuration files, then you need to make the corresponding changes to the new configuration files.
2) Rebuild and redeploy your application(s) (EARs, WARs, SARs) using the new libraries in 4.2.2.
3) Web services have changed dramatically. Either give up or redevelop (or search for other posts on moving axis-based web services forward).
4) Move over other files (*-ds.xml, *-service.xml). But first compare files of that kind to see if you have to make any changes. For example, the MBeans used to declare queues and topics are probably slightly different.
5) Post the errors you get when you deploy the app (start the app server first, then deploy one thing at a time, if the deployer throws an exception, post it)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165371#4165371
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165371
17 years, 9 months