[Clustering/JBoss] - Re: Clustering and load balancing EJB 2.x
by konkimalla
I am also doing the similar test but unable to make HAJNDI cluster work. I configured two nodes in the cluster and made sure the EJB has been deployed on two nodes using DistributedReplicantManager -> listContent(). I used the same configuration you have used; for ejb's I have not modified any deployment descriptor as I used @Clustered annotation as per the documentation. I am trying EJB3.0 in 4.2.0.GA
I configured the standalone client application, separately running away from A/S but with in one of the nodes in cluster, using the following properties:
props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
props.put("java.naming.provider.url", "localhost:1100");
props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
As part of the test, when I shutdown the server, one servicing the client, the client also dead. So, as per the document I changed url at client to
props.put("java.naming.provider.url", "<currentnodeip1>:1100,<another nodeip2>:1100"); Even then the same problem is appearing.
The client could not even connect to the A/S when I changed the url to
props.put("java.naming.provider.url", "<currentnodeip1>:1100");
Can you please let me know where I am doing wrong? I can't really go further with out this one.
Following is the exception when I shutdown the A/S in node1
---------------------------------------------------------------------------------
java.lang.RuntimeException: cluster invocation failed, last exception was:
at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterCh
ooserInterceptor.java:166)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPr
opagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityC
lientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.ejb3.remoting.ClusteredIsLocalInterceptor.invoke(ClusteredI
sLocalInterceptor.java:55)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.ejb3.stateful.StatefulClusteredProxy.invoke(StatefulCluster
edProxy.java:108)
at $Proxy2.add(Unknown Source)
at com.clique.cmg.client.Main.main(Main.java:93)
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid: jboss.j
2ee:ear=TestJmxBean.ear,jar=TestJmxBean.jar,name=SfAddBean,service=EJB3 was not
found in the Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRem
otingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(Se
rverThread.java:560)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.j
ava:369)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.jav
a:165)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientI
nvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemot
eInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterCh
ooserInterceptor.java:77)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPr
opagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityC
lientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.ejb3.remoting.ClusteredIsLocalInterceptor.invoke(ClusteredI
sLocalInterceptor.java:55)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.ejb3.stateful.StatefulClusteredProxy.invoke(StatefulCluster
edProxy.java:108)
at $Proxy2.add(Unknown Source)
at com.clique.cmg.client.Main.main(Main.java:93)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemot
eInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
java:101)
at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterCh
ooserInterceptor.java:77)
... 10 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068907#4068907
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068907
18Â years, 8Â months
[JBossWS] - Re: setHeader and setServerURL, using javax.xml.ws.Service?
by ericï¼ attask.com
Yeah I too could do the simple "Hello World", but i don't know how to include a complex type, such as
| <soapenv:Header>
| <urn:SessionHeader>
| <urn:sessionId>QwWsHJyTPW.1pd0_jXlNKOSU</urn:sessionId>
| </urn:SessionHeader>
| </soapenv:Header>
as a header. Notice it wraps sessionId inside SessionHeader.
I've tried a number of things including
StubExt soapStub = (StubExt)soapBinding;
| QName headerQ = new QName(service.getServiceName().getNamespaceURI(), "SessionHeader");
| QName sessionId = new QName(service.getServiceName().getNamespaceURI(), "SessionHeader", "sessionId");
| soapStub.addUnboundHeader(headerQ, Constants.TYPE_LITERAL_STRING, String.class, ParameterMode.IN);
| soapStub.setUnboundHeaderValue(sessionId, "QwWsHJyTPW.1pd0_jXlNKOSU");
but that only managed to produce:
| <ns1:SessionHeader xmlns:ns1='urn:partner.soap.sforce.com'>QwWsHJyTPW.1pd0_jXlNKOSU</ns1:SessionHeader>
I've tried several other things bug I haven't had much luck.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068906#4068906
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068906
18Â years, 8Â months
[JBoss Seam] - EntityQuery Ajax update
by jlane
Could someone please explain the steps necessary to have ajax update the input fields and rerun the query.
I have the entityquery running correctly when you enter text in a field and press the submit button - refreshing the datatable.
What I am trying to do is change the behavior to where as the user is entering keystrokes into the input fields the parameters are updated and the query is then rerun - updateing the datatable and re-rendered.
I have been successful in creating an ajax method call per keystroke but don't know how to update the query parameters and re-run the query.
<h:inputText id="classTitle" value="#{staffCourseList.staffCourse.classTitle}" style="width: 165px;">
<a:support event="onkeyup" actionListener="#{staffCourseList.find}" />
</h:inputText>
<a:commandButton id="submit" value="Find Course" action="#{staffCourseList.find}" reRender="dataTableStaffCourseList"/>
Thanks for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068900#4068900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068900
18Â years, 8Â months