[JBossCache] - Re: Problems while using JBoss Cache Replication in Cluster
by nirajal
I tried using SP2 and I was facing the same problem. The error log while starting JBoss is given below:
15:15:35,494 WARN [ServiceController] Problem starting service jboss.cache:serv
ice=PojoCache
java.lang.RuntimeException: failure to marshal argument(s)
at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java
:188)
at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java
:163)
at org.jboss.cache.TreeCache.callRemoteMethodsViaReflection(TreeCache.ja
va:4404)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4358)
at org.jboss.cache.loader.ClusteredCacheLoader.callRemote(ClusteredCache
Loader.java:75)
at org.jboss.cache.loader.ClusteredCacheLoader.getChildrenNames(Clustere
dCacheLoader.java:66)
at org.jboss.cache.loader.CacheLoaderManager.preload(CacheLoaderManager.
java:271)
at org.jboss.cache.loader.CacheLoaderManager.preloadCache(CacheLoaderMan
ager.java:235)
at org.jboss.cache.TreeCache.startService(TreeCache.java:1563)
at org.jboss.cache.aop.PojoCache.startService(PojoCache.java:94)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.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(ServiceControl
ler.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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.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 sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.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 $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.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(ServiceControl
ler.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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.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)
Caused by: java.lang.IllegalArgumentException: Marshaller.extractFqn(): Unknown
method call id: 22
at org.jboss.cache.marshall.Marshaller.extractFqn(Marshaller.java:147)
at org.jboss.cache.marshall.TreeCacheMarshaller140.extractFqnAsString(Tr
eeCacheMarshaller140.java:196)
at org.jboss.cache.marshall.TreeCacheMarshaller140.objectToStream(TreeCa
cheMarshaller140.java:90)
at org.jboss.cache.marshall.VersionAwareMarshaller.objectToByteBuffer(Ve
rsionAwareMarshaller.java:133)
at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java
:181)
... 100 more
Any help in this regard would be really appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025022#4025022
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025022
19Â years, 1Â month
[JBoss Seam] - Re: @In(create = true) @Out works fine in 1.1.5.GA and not i
by msystems
Now it works :-)
Old pages.xml (OK for 1.1.5 and not OK for 1.2.0):
| <!DOCTYPE pages PUBLIC "-//JBoss/Seam Pages Configuration DTD 1.1//EN" "http://jboss.com/products/seam/pages-1.1.dtd">
|
| <pages>
| <page view-id="/xhtml/account/create/agreement.jspx" action="#{accountBean.begin}"/>
| <page view-id="/xhtml/account/create/create.jspx" action="#{accountBean.validatePageRequest}"/>
| <page view-id="/xhtml/account/create/welcome.jspx" action="#{accountBean.validatePageRequest}"/>
| </pages>
|
New pages.xml (OK for 1.2.0. Havn't tried it for 1.1.5):
| <!DOCTYPE pages PUBLIC "-//JBoss/Seam Pages Configuration DTD 1.1//EN" "http://jboss.com/products/seam/pages-1.1.dtd">
|
| <pages>
| <page view-id="/xhtml/account/create/create.jspx" action="#{accountBean.validatePageRequest}"/>
| <page view-id="/xhtml/account/create/welcome.jspx" action="#{accountBean.validatePageRequest}"/>
| </pages>
|
For 1.2.0
| <page view-id="/xhtml/account/create/agreement.jspx" action="#{accountBean.begin}"/>
|
triggers a new conversation id for each request in the same conversation.
As mentioned earlier maybe it's not the correct way I have used page actions, but it's difficult to know, because it works just fine for 1.1.5 and not for 1.2.0 - maybe it have been a bug for Seam versions <1.1.5 (1.1.6) and the bug have been fixed for 1.2.0 or this is a new bug in 1.2.0?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025019#4025019
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025019
19Â years, 1Â month
[EJB 3.0] - Deployment order of web and ejb modules in same ear file
by jochenb
Hello,
we are developing an enterprise application containing two web and 3 ejb modules on Jboss 5. Now we want to do some initialization work when the application starts.
Our idea was to develop a servlet which has set its <load-on-startup>0</load-on-startup> parameter in the web.xml set to 0.
In the init Method of the servlet we are executing our initialization code. The problem is that we want to access the database via entity beans from the ejb modules in the initialization code.
But jboss first deploys the web modules and then the ejb modules in the ear. So at execution time of the init Method of our servlet the ejbs are not visible yet and we are getting exceptions. Is there a possibility to force Jboss to first load the ejb modules and then the web modules inside the ear?
I have seen the depends tag in the jboss-web.xml but I don't know how to get the JMX name for the ejb module.
Any help would be greatly appreciated.
Best regards,
Jochen
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025017#4025017
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025017
19Â years, 1Â month