WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

java.net.ConnectException: Connection refused errors after migrating WAS environment from AIX 6.1 to AIX 7.2

  • 1.  java.net.ConnectException: Connection refused errors after migrating WAS environment from AIX 6.1 to AIX 7.2

    Posted Mon December 21, 2020 09:06 PM

    We migrated our WAS environment from AIX 6.1 to AIX 7.2 using backupconfig and restoreconfig method and

    changed the hostname in serverindex.xml file and restarted the jvms. During the startup, the applications

    fail to connect to ActiveMQ and receive connection refused errors. We have the following generic jvm arguments

    set on the jvm conneting to ActiveMQ and have given 775 permissions to all files under /xxx/directory:

    -------------

    -Djava.rmi.server.hostname=xxxhost

    -Dcom.sun.management.jmxremote

    -Dcom.sun.management.jmxremote.port=1234

    -Dcom.sun.management.jmxremote.ssl=false

    -Dcom.sun.management.jmxremote.authenticate=true

    -Dcom.sun.management.jmxremote.access.file=/xxx/jmx.access

    -Dcom.sun.management.jmxremote.password.file=/xxx/jmx.password

    --------------

    We see the following errors:

    SystemOut.log:

    java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException

    [Root exception is java.rmi.ConnectException: Connection refused to host: xxxx.yournetwork.com; nested exception is:

    java.net.ConnectException: Connection refused]

    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:380)

    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:281)

    at org.springframework.jmx.support.MBeanServerConnectionFactoryBean.connect(MBeanServerConnectionFactoryBean.java:133)

    at org.springframework.jmx.support.MBeanServerConnectionFactoryBean.afterPropertiesSet(MBeanServerConnectionFactoryBean.java:121)

    ....

    Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: xxxx.yournetwork.com; nested exception is:

    java.net.ConnectException: Connection refused]

    at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:134)

    at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:217)

    at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)

    at javax.naming.InitialContext.lookup(InitialContext.java:428)

    at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1966)

    at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1933)

    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:298)

    Caused by: java.rmi.ConnectException: Connection refused to host: xxxx.yournetwork.com; nested exception is:

    java.net.ConnectException: Connection refused

    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)

    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)

    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:214)

    at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:354)

    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)

    at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:130)

    ... 55 more

    Caused by: java.net.ConnectException: Connection refused

    at java.net.Socket.connect(Socket.java:666)

    at java.net.Socket.connect(Socket.java:606)

    at java.net.Socket.<init>(Socket.java:469)

    at java.net.Socket.<init>(Socket.java:239)

    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:52)

    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:160)

    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:625)

    native_stderr.log:

    Error: Password file read access must be restricted: /xxx/jmx.password

    Exception in thread "jlmAgent" java.lang.Error: snmp agent failed to launch

    at com.ibm.misc.SystemIntialization$1.run(SystemIntialization.java:186)

    Caused by: java.lang.reflect.InvocationTargetException

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

    at java.lang.reflect.Method.invoke(Method.java:507)

    at com.ibm.misc.SystemIntialization$1.run(SystemIntialization.java:183)

    Caused by: java.lang.RuntimeException: Password file read access must be restricted

    at sun.management.Agent.error(Agent.java:539)

    at sun.management.Agent.error(Agent.java:531)

    at sun.management.Agent.startAgent(Agent.java:293)

    at sun.management.Agent.startAgent(Agent.java:476)



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)


  • 2.  RE: java.net.ConnectException: Connection refused errors after migrating WAS environment from AIX 6.1 to AIX 7.2
    Best Answer

    Posted Mon December 21, 2020 09:07 PM

    The RuntimeException means that the file specified in the "com.sun.management.jmxremote.password.file" property is readable by users other than the current user: /xxx/jmx.password.

    As per the JMX documentation, read/write access to the password file must be restricted to the current user only.

    https://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html

    The following command would achieve that:

    chmod 600 /xxx/jmx.password



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)