[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-444) MODCLUSTER000043: Failed to send - Connection refused exception using JBoss EAP 6.3.2

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar closed MODCLUSTER-444.
-------------------------------------


> MODCLUSTER000043: Failed to send - Connection refused exception using JBoss EAP 6.3.2
> -------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-444
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-444
>             Project: mod_cluster
>          Issue Type: Feature Request
>            Reporter: Siddharth GARG
>            Assignee: Jean-Frederic Clere
>
> We are using JBOSS version 6.3.2 and getting below exception while trying to access the application deployed on it - 
> MODCLUSTER000043: Failed to send STATUS to server1: java.net.ConnectException: Connection refused
> 	at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.7.0_71]
> 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) [rt.jar:1.7.0_71]
> 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) [rt.jar:1.7.0_71]
> 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) [rt.jar:1.7.0_71]
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.7.0_71]
> 	at java.net.Socket.connect(Socket.java:579) [rt.jar:1.7.0_71]
> 	at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnection(DefaultMCMPHandler.java:835)
> 	at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.getConnectionWriter(DefaultMCMPHandler.java:858)
> 	at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:499)
> 	at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:600)
> 	at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:414)
> 	at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:468)
> 	at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> 	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1]
> 	at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1323) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1]
> 	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1588) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1]
> 	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1574) [jbossweb-7.4.9.Final-redhat-1.jar:7.4.9.Final-redhat-1]
> 	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
> Could you please let me know if this is known issue/bug with JBOSS 6.3.2 and if there is any fix pack available for this
> Thanks,



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)