[jboss-jira] [JBoss JIRA] Commented: (JBAS-5305) Loadbalancing and clustering JBOSS using Apache Http server

[Yugant Shah (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-5305?page=comments#action_12402533 ] 
            
Yugant Shah commented on JBAS-5305:
-----------------------------------

Hello,
I have attached the code used for the above issue on the jboss clustering forum.
The link for the same is :
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129976 

Thanks,
Yugant Shah.


> Loadbalancing and clustering JBOSS using Apache Http server
> -----------------------------------------------------------
>
>                 Key: JBAS-5305
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5305
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.2.GA
>         Environment: Windows XP
>            Reporter: Yugant Shah
>         Assigned To: Brian Stansberry
>
> Hello, 
> I have clustered two instances of JBOSS and I have configured the jboss web deployer for load balancing using apache http server. 
> Consider I have 2 instances of Tomcat (embedded in JBOSS) say TOM1 and TOM2. 
> Loadbalancer1 is TOM1 and TOM2 is Loadbalancer2 are configured in Apache server. 
> A request is processed by TOm1 and it goes down(using Ctrl+C) the request is then load balanced to TOM2.In the mean I start TOM1 again. 
> And bring TOM2 down...The request state is transfered to TOM1 and TOm1 restarts the processing of same request. 
> The problem is that TOM1 throws an exception 
> 13:24:40,954 INFO [STDOUT] YUGANT Bean:5 
> 13:24:41,455 INFO [STDOUT] YUGANT Bean:6 
> 13:24:41,957 INFO [STDOUT] YUGANT Bean:7 
> 13:24:42,458 INFO [STDOUT] YUGANT Bean:8 
> 13:24:42,960 INFO [STDOUT] YUGANT Bean:9 
> 13:24:43,477 ERROR [ServerThread] Worker thread initialization failure 
> java.net.SocketException: Connection reset by peer: socket write error 
> at java.net.SocketOutputStream.socketWrite0(Native Method) 
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) 
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136) 
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65 
> ) 
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) 
> at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputSt 
> ream.java:1631) 
> at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:666) 
> at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.s 
> endObjectVersion2_2(JavaSerializationManager.java:121) 
> at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.s 
> endObject(JavaSerializationManager.java:95) 
> at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write( 
> SerializableMarshaller.java:120) 
> at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(Serve 
> rThread.java:806) 
> at org.jboss.remoting.transport.socket.ServerThread.processInvocation(Se 
> rverThread.java:606) 
> at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.j 
> ava:373) 
> at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.jav 
> a:166) 
> 15:06:03,431 INFO [TreeCache] viewAccepted(): [192.168.0.33:1652|17] [192.168.0 
> .33:1652, 192.168.0.50:2949] 
> 15:06:03,463 INFO [TreeCache] locking the subtree at / to transfer state 
> 15:06:03,479 INFO [StateTransferGenerator_140] returning the state for tree roo 
> ted in /(1024 bytes) 
> 15:06:07,702 INFO [final16] New cluster view for partition final16 (id: 17, del 
> ta: 1) : [192.168.0.33:1199, 192.168.0.50:1199] 
> 15:06:07,702 INFO [final16] I am (192.168.0.33:1199) received membershipChanged 
> event: 
> 15:06:07,702 INFO [final16] Dead members: 0 ([]) 
> 15:06:07,702 INFO [final16] New Members : 1 ([192.168.0.50:1199]) 
> 15:06:07,702 INFO [final16] All Members : 2 ([192.168.0.33:1199, 192.168.0.50:1 
> 199]) 
> And the request is left unprocessed. 
> I am not able to resolve this issue. 
> Thanks in advance. 
> Thanks, Yugant Shah. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira