[JBoss Seam] - Deployment of exploded ear fails in 1.1.6
by novare
Hi,
When going from 1.1.1. to 1.1.6 we experienced that the jboss-seam.jar was started twice when we deployed our project exploded into JBossAS-4.0.5.GA. Resulting in an error saying:
23:45:04,630 ERROR [[/fm]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
| java.lang.IllegalStateException: duplicate factory for: actor
| at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:178)
| at org.jboss.seam.core.Init.addFactoryValueBinding(Init.java:196)
| at org.jboss.seam.init.Initialization.addComponents(Initialization.java:706)
| at org.jboss.seam.init.Initialization.init(Initialization.java:451)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
| 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:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
| 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:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
| at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
| at org.jboss.web.WebModule.startModule(WebModule.java:83)
| at org.jboss.web.WebModule.startService(WebModule.java:61)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| 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.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| 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 $Proxy41.start(Unknown Source)
| at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| 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 $Proxy42.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| 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 $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| 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:585)
| 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.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:585)
| 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 $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| 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 $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:490)
| at java.lang.Thread.run(Thread.java:595)
|
We do not have a component named actor, and I believe this error refer to the settings in components.xml within jboss-seam.jar.
The difference between deploying our project using 1.1.1.GA and 1.1.6.GA is the refernece in application.xml
<?xml version="1.0" encoding="UTF-8"?>
| <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
| <description>Logit Fleet Manager</description>
| <display-name>LogitFM-ear</display-name>
| <module>
| <java>jboss-seam-1.1.6.GA.jar</java>
| </module>
| <module>
| <java>jbpm-3.1.4.jar</java>
| </module>
| <module>
| <java>tomahawk-1.1.3.jar</java>
| </module>
| <module>
| <java>el-api-1.1.11.jar</java>
| </module>
| <module>
| <java>el-ri-1.1.11.jar</java>
| </module>
| <module>
| <java>tomahawk-1.1.3.jar</java>
| </module>
| <module>
| <ejb>LogitFM-ejb.jar</ejb>
| </module>
| <module>
| <ejb>LogitFM-Alert-ejb.jar</ejb>
| </module>
| <module>
| <ejb>LogitFM-MessageConfig-ejb.jar</ejb>
| </module>
| <module>
| <web>
| <web-uri>LogitFM-web.war</web-uri>
| <context-root>/fm</context-root>
| </web>
| </module>
| </application>
and the stack trace then tries to deploy a tmp-reference of jboss-seam
| 23:44:53,536 INFO [Scanner] scanning: /E:/usr/jboss-4.0.5.GA/server/logit/tmp/deploy/tmp34522jboss-seam-1.1.6.GA.jar
| 23:44:53,536 DEBUG [Scanner] archive: E:\usr\jboss-4.0.5.GA\server\logit\tmp\deploy\tmp34522jboss-seam-1.1.6.GA.jar
| 23:44:53,536 DEBUG [Scanner] found: META-INF/
| 23:44:53,536 DEBUG [Scanner] found: META-INF/MANIFEST.MF
| 23:44:53,536 DEBUG [Scanner] found: META-INF/components.xml
| 23:44:53,536 DEBUG [Scanner] found: META-INF/faces-config.xml
| 23:44:53,536 DEBUG [Scanner] found: org/
| 23:44:53,536 DEBUG [Scanner] found: org/jboss/
| 23:44:53,536 DEBUG [Scanner] found: org/jboss/seam/
| 23:44:53,536 DEBUG [Scanner] found: org/jboss/seam/Component$1.class
| 23:44:53,536 DEBUG [Scanner] found: org/jboss/seam/Component$ConstantInitialValue.class
| .
| .
| .
In addition to the exepcted one:
| 23:44:53,348 INFO [Scanner] scanning: /E:/usr/jboss-4.0.5.GA/server/logit/deploy/LogitFM-ear.ear/jboss-seam-1.1.6.GA.jar
| 23:44:53,348 DEBUG [Scanner] archive: E:\usr\jboss-4.0.5.GA\server\logit\deploy\LogitFM-ear.ear\jboss-seam-1.1.6.GA.jar
| 23:44:53,348 DEBUG [Scanner] found: META-INF/
| 23:44:53,348 DEBUG [Scanner] found: META-INF/MANIFEST.MF
| 23:44:53,348 DEBUG [Scanner] found: META-INF/components.xml
| 23:44:53,348 DEBUG [Scanner] found: META-INF/faces-config.xml
| 23:44:53,348 DEBUG [Scanner] found: org/
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/seam/
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/seam/Component$1.class
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/seam/Component$ConstantInitialValue.class
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/seam/Component$ELInitialValue.class
| 23:44:53,348 DEBUG [Scanner] found: org/jboss/seam/Component$InitialValue.class
| .
| .
| .
If deployed as a packed ear file it deployed successdully.
This might look like a JBossAS problem, but before posting the problem in that forum I woundered if someone knew what changes in seam might causes this behaviour?
Thanks a lot
Jarle
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013501#4013501
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013501
19Â years, 2Â months
[JBoss jBPM] - Re: NullPointerException executing timer
by smigniot
We have the same issue using the simplest workflow here :
<state name="validateIn20seconds">
| <transition name="" to="validated" />
| <transition name="missed" to="notvalidated" />
| <timer duedate="20 seconds" transition="missed">
| <action class="action.DoNothing" />
| </timer>
| </state>
| <state name="validated">
| <transition name="" to="end"></transition>
| </state>
| <state name="notvalidated">
| <transition name="" to="end"></transition>
| </state>
|
We're using the SchedulerServlet to execute timers
so the error is not due to your mechanism. We obtain
the same error :
INFO: runtime exception while executing timers
| java.lang.NullPointerException
| at org.jbpm.graph.def.GraphElement.getRuntimeActionsForEvent(GraphElement.java:259)
| at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:186)
| 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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:147)
| at org.jbpm.graph.node.State$$EnhancerByCGLIB$$d55a4606.fireAndPropagateEvent(<generated>)
| at org.jbpm.scheduler.exe.Timer.execute(Timer.java:77)
| at org.jbpm.scheduler.impl.SchedulerThread.executeTimers(SchedulerThread.java:118)
| at org.jbpm.scheduler.impl.SchedulerThread.run(SchedulerThread.java:70)
No idea what the solution is ...
We're using Jbpm as recommended by the docs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013496#4013496
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013496
19Â years, 2Â months
[Management, JMX/JBoss] - Parameter Changes through JBOSS JMX or Twiddle
by mahendra_kutare
Hi,
I am using JBoss version 4.0.4 GA for my test run with JDK 1.5.0.10.
I would like to understand the follownig -
1) If i change the MaxPoolSize (Count of Server threads) attribute value of pooled invoker configuration from JMX console or twiddle - then what will be the impact mechanism of this change ?
a) Say for example i have initial value of MaxPoolSize as 50. I then decrease it to 70 how and will JBoss behave internally ?
- Will it change the threads to 70 immediately, even if say the workload would not require more threads or it will wait till the workload requires more threads and then increase the count to 70 in this case ?
- Essentially what policy or algorithm does the JBoss application server uses if any parameter changes at container level or web server level in configuration files through JMX or twiddle ?
a) Say for example i have initial value of MaxPoolSize as 50. I then decrease it to 30 how and will JBoss behave internally ?
- Will it change the threads to 70 immediately, even if say the workload would not require more threads or it will wait till the workload requires more threads and then increase the count to 70 in this case ?
- Essentially what policy or algorithm does the JBoss application server uses if any parameter changes at container level or web server level in configuration files through JMX or twiddle ?
Please do respond to this as my tests are related to changing the parameters and their impact, hence its imperative to know what policy or algorithm does JBoss uses internally on any changes through JMX console or twiddle. If any more information on my environment is required, i would be glad to put that across.
Regards
Mahendra
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013486#4013486
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013486
19Â years, 2Â months