[EJB 3.0] - EJB3/Quartz problem
by jharby1
We have been using an EJB3 MDB with Quartz and everything was working fine but all of a sudden when I restarted JBoss, I received these errors below and Quartz no longer works. Does anyone know what is causing this?
12:45:21,846 WARN [ServiceController] Problem starting service jboss.j2ee:ear=scheduler.ear,jar=Letter.jar,name=AnnotatedQuartzMDBBean,service=EJB3
org.jboss.deployment.DeploymentException: Unable to create activation spec ra=jboss.jca:service=RARDeployment,name='quartz-ra.rar' messaging-type=org.quartz.Job properties={cronTrigger=ActivationConfigProperty(cronTrigger=0/40 * * * * ?)}; - nested throwable: (javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name='quartz-ra.rar' is not registered.)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:290)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:189)
at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:190)
at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:156)
at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy38.start(Unknown Source)
at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:301)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362)
at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173165#4173165
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173165
18 years
[Beginners Corner] - Tomcat welcome page
by daylejames
Hey all
I am pretty unfamiliar with jboss (although I'm getting there), but have a very annoying problem, which is holding me up on signing off on jboss in my test environment.
My manager wants to see a welcome page when I start up the jboss service, and for reasons I can't explain it's missing. Here is the process I have followed :
- Deploy jboss 4.2.2 with the minimal server in place - starts successfully (no errors in startup output).
- Copy the tomcat folder (jboss-web.deployer) into server/server_name/deploy)
- Make a couple of changes to the jboss-service.xml to facilitate the manual copying of tomcat... Can provide if necessary.
- Started up jboss.
Now to my mind, at this point, I should see the jboss startup screen when I navigate to http://:8080/ but I don't.
What I DO get is a blank web page with a done message in the browser. This tells me that the browser recognises that there is something on port 8080, but it has nothing to display.
Honestly, I've been trying to get this to work for a while now and I think it's driving me slightly strange.
Any help on how to proceed appreciated.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173159#4173159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173159
18 years
[Installation, Configuration & DEPLOYMENT] - JBoss slow after long uptime
by couzteau
Hi,
I need help analysing a problem with my JBoss deployment.
Generally the environment is stable. The problem has occurred 5 times since March and the web server handles about 250,000 - 500,000 requests per day.
Problem:
Sometimes the JVM suddenly gets incredibly slow. When that occurs I see that the CPU load never drops below 100% (1 CPU burning at top load). The memory consumption is higher than it should be according to the JVM setting (-Xmx2048m).
I'm guessing that a garbage collector thread crashed.
How can I analyse what is going wrong?
config:
* java version "1.6.0_04"
* Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
* Java HotSpot(TM) 64-Bit Server VM (build 10.0-b19, mixed mode)
* jboss-4.2.2.GA runs using 2GBRAM
* Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
* hardware: 16GB Ram, 4 dual core CPUs
* There is a mysql db running
Thank you very much.
jacques
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173158#4173158
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173158
18 years