-
1. Re: JBoss Clustering is the Coolest Thing Ever
marc.fleury Dec 14, 2001 12:00 AM (in response to alanlewis):D
-
2. Re: JBoss Clustering is the Coolest Thing Ever
slaboure Dec 14, 2001 4:05 AM (in response to alanlewis):D :D :D :D
-
3. Re: JBoss Clustering is the Coolest Thing Ever
slaboure Dec 14, 2001 4:08 AM (in response to alanlewis)Hello Alan,
> I'm happy to answer any questions that aren't covered
> in the documentation. I used the default
> configuration thats in the docs for clustered
> stateless session beans and it worked fine. The only
> difficulty I had was in creating the client. My
> client code didn't need to be modified at all, but I
> did have to figure out how to run it under a security
> manager, which is something I've never done before.
Thank you for this very positive feedback, I do really appreciate! ;)
For the security manager thing, that is interesting. Have you added the jbossha-client.jar file to the classpath of your client? Do you remember for which class it was complaining if you didn't set a security manager?
Cheers,
Sacha -
4. Re: JBoss Clustering is the Coolest Thing Ever
bill.burke Dec 14, 2001 10:36 AM (in response to alanlewis)We need more people like you testing out this stuff. Thanks for trying it out and let us know directly any problems you have.
-
5. Re: JBoss Clustering is the Coolest Thing Ever
alanlewis Dec 14, 2001 12:39 PM (in response to alanlewis)> For the security manager thing, that is interesting.
> Have you added the jbossha-client.jar file to the
> classpath of your client? Do you remember for which
> class it was complaining if you didn't set a security
> manager?
>
I tried using the client code again this morning, and now it seems to be working without the security manager. So then it would seem that the only thing you need to do for clients is to make sure that the jbossha-client.jar file is in the CLASSPATH, right? -
6. Re: JBoss Clustering is the Coolest Thing Ever
slaboure Dec 15, 2001 10:10 AM (in response to alanlewis)Alan,
Yes, with jbossha-client.jar in the client classpath, everything should be fine.
Cheers,
Sacha -
7. Re: JBoss Clustering is the Coolest Thing Ever
nshashidhara Feb 25, 2004 11:53 AM (in response to alanlewis)Hi
I am new to jboss clustring , can you help me in configure.
i have created two jboss3.2.3 instances on linux machine.
all and all1 .
when i start both instances, nodes are identifing,
but when i shutdown any one one server, request is not going to another instance, please help urgent -
8. Re: JBoss Clustering is the Coolest Thing Ever
nshashidhara Feb 25, 2004 11:53 AM (in response to alanlewis)Hi
I am new to jboss clustring , can you help me in configure.
i have created two jboss3.2.3 instances on linux machine.
all and all1 .
when i start both instances, nodes are identifing,
but when i shutdown any one one server, request is not going to another instance, please help urgent
this is my mail id
nshashidhara@rediffmail.com -
9. Re: JBoss Clustering is the Coolest Thing Ever
glyn_walters Feb 26, 2004 7:13 AM (in response to alanlewis)The problem may be with the lookup code in your client. Are you using HA-JNDI when you create the IntialContext?
-
10. Re: JBoss Clustering is the Coolest Thing Ever
nshashidhara Mar 1, 2004 4:35 AM (in response to alanlewis)No , I am using common JNDI look up, can you assist me how we can do HA-JNDI lookup
-
11. Re: JBoss Clustering is the Coolest Thing Ever
gsureshbabu Mar 3, 2004 3:13 AM (in response to alanlewis)Dear all
I am g suresh babu
Sub:Problems Regarditing to clustering implementation
We have been trying to implement Jboss clustering on two machines.we got only progress those two nodes are appearing in clustering. Two nodes are in Default Partition. we did not change any in jboss cluster-service.xml file.
Changes made for configuration
1.farm-service.xml in server/all/deploy
2.For EJBs execution we made "clustered true" in ejb-jar.xml.
Errors Identified :
1. we tried to exceute from one node ,the client & jar files which are deployed in the
second(second node shutdown) but it was giving me error as JNDI name not bound.
We thought this one we r not getting HotDeployment.
2.we tried with
java.naming.url.provider=node1:1100,node2:1100
in all/sever/conf/jndi.properties file at this one we got Communication Exception
(SocketTimeoutException)
i.e node1:1100 is not connected & node2:1100 is not connected
3. In the client
p.put(Context.PROVIDER_URL, ""); at this point we got
javax.naming.CommunicationException: Receive timed out. Root exception is
java.net.SocketTimeoutException
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:629)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1223)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at ejb.HelloWorldClient.main(HelloWorldClient.java:31)
Exception: Receive timed out
We Supposed to put localhost:1100 or 1099 it is excuting in that particular node.
inform me what r the chnages required to configure two systems.
if you have any expmple code snipets forward to me.
which is the best documentation for Jboss clustering?.
Thanks &Regards
G.Suresh Babu
gsureshbabu9@rediffmail.com