[Clustering/JBoss] - FamilyClusterInfo loses all targets
by eric239
Hello:
I'm experiencing a problem where FamilyClusterInfo instance is losing all targets even though one of the nodes in the cluster is up. The scenario is described below; I'd like an advice from the forum community whether it does resemble a bug and should be filed as a JIRA issue.
The setup:
JBoss 4.2.2.GA installed on two linux servers, running on 1.6.0_04 JVM
A jboss config (aka server/instance) with several EJB3 SLSBs deployed and clustering enabled (HA JNDI and all). This will be referred to as "server instance"
A jboss config (aka server/instance) which looks up and makes use of those SLSBsThis will be referred to as "client instance"
Client uses a custom LoadBalance policy implementation which, for the sake of debugging the problem, has been stripped down to printing out error line if familiyClusterInfo.getTargets().isEmpty() is true
Both configs are running on both nodes by default; clusters appear to be setup properly, everything functions just fine
The problem scenario:
Leave a single client instance up. It connects to either of the server instances as expected. Bring a server instance (say, "node A") down. FamilyClusterInfo is properly updated, all calls are served by "node B".
Now bring "node A" up and bring "node B" down. At this point FamilyClusterInfo apparently loses all target (B is removed, but A is not added). This is proven by the error output from the custom LoadBalancePolicy impl as well as by the exception on the client side:
java.lang.RuntimeException: Unreachable?: Service unavailable.
| at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:176)
It seems that FamilyClusterInfo is only updated in terms of removal of dead targets but never in terms of addition of newly alive targets.
So... does it look like a solid candidate for posting as an issue? Or I'm missing something obvious? Or perhaps this should've been posted to developer forum instead?
--Ernest
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157416#4157416
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157416
17 years, 11 months
[JBoss jBPM] - Re: Multithreaded JobExecutor with ForEachForkActionHandler
by estaub
Pavel, look at hibernate config values for the following.
The ones with question-marks I can't help you with - I'm using local wrappers, and can't take time to look up generic solutions. Check the Hibernate docs, etc for these properties. I'm (obviously) on WebLogic - you'll need different values for other containers.
-Ed Staub
<!-- CMT transaction properties (begin) -->
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JDBCTransactionFactory</property>
| <!--property name="hibernate.transaction.manager_lookup_class">????????????????????????</property> -->
| <!-- CMT transaction properties (end) -->
|
| <!-- JTA transaction properties (begin) ===
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
| <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property>
| === JTA transaction properties (end) -->
|
| <!-- CMT transaction properties (begin) -->
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JDBCTransactionFactory</property>
| <!--property name="hibernate.transaction.manager_lookup_class">????????????????????</property> -->
| <!-- CMT transaction properties (end) -->
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157412#4157412
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157412
17 years, 11 months
[EJB/JBoss] - error when deploying day trader: Failed to parse descriptors
by openevol
Greetings,
i like to seek help and advice if any ppl out there has meddle with daytrader on jboss?
I'm using mysql database. My deployment codes can be found at http://www.openevol.com/share/peipei/daytrader-ear-2.0-SNAPSHOT.ear
The whole daytrader contents including the deployment file and instructions can be download at http://www.openevol.com/share/peipei/DayTrader_Jboss.zip
Anyone can contact me at vitalstrike82(a)hotmail.com if you have advise to guide me. Thanks.. :)
After editing and doing some changes to the daytrader, i manager to scales down the error to these:
22:50:34,628 INFO [EARDeployer] Init J2EE application: file:/home/chongming/jboss/server/default/deploy/daytrader-ear-2.0-SNAPSHOT.ear
22:50:34,770 WARN [MainDeployer] Found non-jar deployer for wsappclient.jar: org.jboss.deployment.ClientDeployer@2b2af3
22:50:34,996 WARN [NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.deployment.DeploymentException is assignable from: class org.jboss.deployment.DeploymentException
22:50:34,996 WARN [Tomcat5] Failed to parse descriptors for war(file:/home/chongming/jboss/server/default/tmp/deploy/tmp42092daytrader-ear-2.0-SNAPSHOT.ear-contents/web.war/)
org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: expected one home tag)
at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:683)
at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:334)
at sun.reflect.GeneratedMethodAccessor83.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:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy31.init(Unknown Source)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:843)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:863)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:780)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at sun.reflect.GeneratedMethodAccessor49.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:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182)
Caused by: org.jboss.deployment.DeploymentException: expected one home tag
at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:98)
at org.jboss.metadata.EjbRefMetaData.importEjbJarXml(EjbRefMetaData.java:70)
at org.jboss.metadata.WebMetaData.importWebXml(WebMetaData.java:859)
at org.jboss.metadata.WebMetaData.importXml(WebMetaData.java:677)
at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:678)
... 37 more
22:50:35,641 ERROR [MainDeployer] Could not start deployment: file:/home/chongming/jboss/server/default/tmp/deploy/tmp42092daytrader-ear-2.0-SNAPSHOT.ear-contents/dt-ejb.jar
org.jboss.deployment.DeploymentException: expected one display-name tag
at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:98)
at org.jboss.metadata.MetaData.getUniqueChildContent(MetaData.java:291)
at org.jboss.metadata.ClientMetaData.importClientXml(ClientMetaData.java:126)
at org.jboss.deployment.ClientDeployer.start(ClientDeployer.java:132)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:979)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at sun.reflect.GeneratedMethodAccessor49.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:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157411#4157411
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157411
17 years, 11 months
[EJB 3.0] - Re: EJB3 CallByValue=false, but acts like its true
by jaikiran
"fisherv(a)teoco.com" wrote :
| I thought that this JBoss EAR deployer CallByValue option was a feature implemented above and beyond the specification - it is, isn't it?
|
Not sure.
"fisherv(a)teoco.com" wrote :
| I considered switching to local, but that just leaves the potential problem for someone else to solve down the line if remote calls are ever needed later. I'm changing the code to work as call by ref - though this may involve changes in a number of places.
|
| I'm generally against using local for just this reason - your code may stop working if you ever change up your EJB allocation among JVMs/hosts!
|
As you rightly mention, using remote interfaces and then coding to expect that the parameters will be passed by reference was not the correct thing in the first place. I guess you will have to change the implementation to fix this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157404#4157404
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157404
17 years, 11 months