Error loading velocity classess
by Harish Hirasave
I am working on upgrading from Jboss-3.2.3 to Jboss-4.0.5. I get a
NoClassDefFoundError when I start my server while deploying EJBs
which have velocity classes in them. The jar has the Velocity jars
and this works for Jboss-3.2.3 but does not work for Jboss-4.0.5.The
error I get is below. Do we need any extra configuration settings for
the velocity classes to load?
Thanks
Harish
java.lang.NoClassDefFoundError: org/apache/velocity/context/Context
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
at java.lang.Class.privateGetPublicMethods(Class.java:1778)
at java.lang.Class.getMethods(Class.java:832)
at
org.jboss.verifier.strategy.AbstractVerifier.hasEJBCreateMethod(Abstra
ct
Verifier.java:687)
at
org.jboss.verifier.strategy.EJBVerifier20.verifySessionBean(EJBVerifie
r2
0.java:848)
at
org.jboss.verifier.strategy.EJBVerifier20.checkSession(EJBVerifier20.j
av
a:78)
at
org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:181)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:594)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
av
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
or
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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(ModelMB
ea
nOperationInterceptor.java:142)
at
org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.
ja
va:97)
at
org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Interceptor
Se
rviceMBeanSupport.java:238)
at
org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInte
rc
eptor.java:74)
at
org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerI
nt
erceptorEJB.java:44)
at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.c
re
ate(SubDeployerInterceptorSupport.java:180)
at
org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerIntercep
to
r.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.j
av
a:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> at $Proxy26.create(Unknown Source)
> at
> org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown
Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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(ModelMB
> ea
> nOperationInterceptor.java:142)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.j
> av
> a:264)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> at $Proxy8.deploy(Unknown Source)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeployment
> Sc
> anner.java:421)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentSc
> an
> ner.java:634)
> at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.d
> oS
> can(AbstractDeploymentScanner.java:263)
> at
> org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Ab
> st
> ractDeploymentScanner.java:336)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSu
> pp
> ort.java:289)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBe
> an
> Support.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> av
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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.j
> av
> a:264)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControll
> er
> .java:978)
> at $Proxy0.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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.j
> av
> a: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.j
> av
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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(ModelMB
> ea
> nOperationInterceptor.java:142)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.j
> av
> a: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:534)
> 16:22:06,568 ERROR [MainDeployer] Could not create deployment:
> file:/C:/jboss-4.0.5.GA/server/rrt/deploy/rrt_common_ejb.jar
<file:///C:\jboss-4.0.5.GA\server\rrt\deploy\rrt_common_ejb.jar>
> org.jboss.deployment.DeploymentException: Verification of Enterprise
> Beans failed, see above for error messages.
> at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
19Â years, 1Â month
[JBoss Seam] - Re: LocaleSelector
by base7691
For my application I was able to narrow the problem a little further. It looks like it has somthing to do with ICEFaces I used.
I tried some tests with the new seam 1.2 version. After setting up a new project with seam-gen the locale selector function does very well. Even if I used it with the cookie-enabled selector in the components.xml
<core:locale-selector cookie-enabled="true"/>
After configuring ICEFaces like it is in the example application the following error occured:
ERROR [com.icesoft.faces.facelets.D2DFaceletViewHandler] Problem in renderResponse: /layout/template.xhtml @19,72 value="#{localeSelector.supportedLocales}": Cannot get value for expression '#{org.jboss.seam.core.localeSelector}'
| javax.faces.el.EvaluationException: /layout/template.xhtml @19,72 value="#{localeSelector.supportedLocales}": Cannot get value for expression '#{org.jboss.seam.core.localeSelector}'
| at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:60)
| at javax.faces.component.UISelectItems.getValue(UISelectItems.java:55)
| at com.icesoft.faces.renderkit.dom_html_basic.MenuRenderer.getSelectItems(MenuRenderer.java:576)
| ...
If I don't use the cookie-enabled selector the application seems to work well but the localeSelector functionality has no effect after clicking the button.
It seems there are incompatibilities between ICEFaces and the localeSelector.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024315#4024315
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024315
19Â years, 1Â month
[JBoss jBPM] - Re: Stateless Process Engine executor threading issues
by jorgemoralespou_2
Hi Ronald,
I still don't get the point. Our executions are in such a way, for now, that once a token is signaled, it must continue through the end, that's why we get hold on to the context. There is no state saving till the end of the execution, because there isn't any waiting state. I don't see any clue in the examples or in any other document you pointed me.
Any change we made so far, leaves us at the same point, double client load, double response time, and plenty of free cpu.
Is there any concurrency issue or synchronicity issue regarding JBPM's context?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024313#4024313
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024313
19Â years, 1Â month