[Clustering/JBoss] - Re: Two asterisks in JSESSIONID before jvmRoute
by jjfevs
Thank you for your answer. I'll explain more in detail the environment. We have two virtual machines. Each of them we have two instances of JBoss running (with different configurations of course). And one of the instances of one machine forms part of a cluster with other instance in the other machine. So, in the end, we have two clusters, lets call them Spain and Colombia (the real ones).
Here is an example of the JSESSIONID of the Colombian cluster, the ones without eh two asterisks (so, this is an indicative of clustered JSESSIONID? ). Also is an example of a JSESSIONIDSSO:
JSESSIONIDSSO=16D95E07D7FD37CC0D09BF5B726F3B20
JSESSIONID=2D52EA0E56A4330C145C44075E4316F9.Node2
We use the same pattern for defining the jvmRoute for both clusters: both have one called Node1 and other called Node2.
In the Spain cluster, when the JSESSIONID works correctly, it is like this:
JSESSIONIDSSO=EEEED918158A844B050B822E8835940F
JSESSIONID=qjL2rvE2+Ly5+oWp7q0bTA**.Node1;
And when it fails, it's like this
JSESSIONID=.Node2 -> the first time you access JBoss
JSESSIONID=.Node2.Node1 -> the second and subsequent times. 2 and 1 value varies depending of the server accessed.
We use Apache mod_proxy_ajp, sorry, I told you wrong. The problem is we use sticky sessions, and the balancer uses the jvmRoute string to distinguish between one instance and the other (we have two virtual host and two balancers, for redirecting to Spain and Colombia respectively ).
I read the TwoClustersInTheSameNetwork document in JBoss online docs, and yesterday we have applied a workaround explained there in another environment (that is a exact replica of this one). This was about setting emptySessionPath=false in the connector in jboss-web.deployer/server.xml file. The problem has not occurred since then... but I'm not very confident myself with this fix.
About the tag, yes I've confirmed that in this cluster is not set, AND this problem does not occur.
About JBoss, We use JBoss 4.3 EAP.
Thank you!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240255#4240255
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240255
17 years
[JBossWS] - Re: JBOSS-5.1.0.GA web service client doesn't work ( runtime
by rangalo
Thanks,
Now I have at least some other error !
If I use only lib I get this error, I think it is related to stax implementation.
Am I missing some jar?
| [hardik@antariksh: HelloWsClient]$ wsrunclient.sh -cp "dist/hello-client.jar:jboss-generated:lib" com.hardik.mejb.JAXWSClient
| http://localhost:8080/Greeter/HelloBean?WSDL
| Exception in thread "main" java.lang.ExceptionInInitializerError
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
| at java.lang.Class.newInstance0(Class.java:355)
| at java.lang.Class.newInstance(Class.java:308)
| at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:31)
| at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:128)
| at javax.xml.ws.spi.Provider.provider(Provider.java:83)
| at javax.xml.ws.Service.<init>(Service.java:56)
| at com.hardik.mejb.Greeter.<init>(Greeter.java:45)
| at com.hardik.mejb.JAXWSClient.main(Unknown Source)
| Caused by: javax.xml.ws.WebServiceException: Error creating JAXBContext for W3CEndpointReference.
| at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:201)
| at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:196)
| at java.security.AccessController.doPrivileged(Native Method)
| at com.sun.xml.internal.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:196)
| at com.sun.xml.internal.ws.spi.ProviderImpl.<clinit>(ProviderImpl.java:67)
| ... 12 more
| Caused by: javax.xml.bind.JAXBException: Provider com.sun.xml.bind.v2.ContextFactory not found
| - with linked exception:
| [java.security.PrivilegedActionException: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory]
| at javax.xml.bind.ContextFinder.loadClass(ContextFinder.java:192)
| at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:205)
| at javax.xml.bind.ContextFinder.find(ContextFinder.java:388)
| at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
| at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
| at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:199)
| ... 16 more
| Caused by: java.security.PrivilegedActionException: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.xml.bind.ContextFinder.loadClass(ContextFinder.java:175)
| ... 21 more
| Caused by: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory
| at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
| at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
| at javax.xml.bind.ContextFinder$1.run(ContextFinder.java:180)
| at javax.xml.bind.ContextFinder$1.run(ContextFinder.java:176)
| ... 23 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240248#4240248
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240248
17 years
[JBoss jBPM] - Re: Indentityservice - Jbpm4
by nilspreusker
Hi all,
I've tried to register a custom IdentitySessionImpl the way it is described in chapter 9 of the user guide (implementing org.jbpm.session.IdentitySession - which has been moved to org.jbpm.pvm.internal.identity.spi.IdentitySession - and configuring it in the trasnaction-context of the jBPM configuration as <object class="your.package.YourIdentitySession" />). However it looks as though the configuration is ignored and the internal implementation of the identity session (org.jbpm.pvm.internal.identity.impl.IdentitySessionImpl) is always used. A quick look at the source code suggests that the IdentitySessionBinding contains a hard-coded reference to org.jbpm.pvm.internal.identity.impl.IdentitySessionImpl, which explains this behavior. Now I've heard that some restructuring of the identity component is on its way, so my question is whether there is a way to get this to work at the moment. (I'm working with the jBPM4 trunk at revision 5066.)
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240237#4240237
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240237
17 years