java.io.IOException

[Ed]

I have multiple weblogic servers running on different IPs on the same server, when I try to grab data via the wlagent I get an IOException (below).

I am able to connect to the instance, tried with bad user/password:
./wlsagent.sh 'hostname=webp01a.site02.net&port=7001&username=fake&password=smell&jdbc=*;2;5'
java.lang.SecurityException: User: fake, failed to be authenticated.|

I am not a java person, so have no idea where the problem is.

2012-11-15 14:40:44.655:INFO:oejsh.ContextHandler:started o.e.j.s.ServletContextHandler{/wlsagent,null}
2012-11-15 14:40:44.704:INFO:oejs.AbstractConnector:Started SelectChann...@0.0.0.0:9090
java.io.IOException
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:195)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:83)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
        at net.wait4it.wlsagent.jmx.JmxConnectionFactory.getInstance(Unknown Source)
        at net.wait4it.wlsagent.jmx.JmxService.getConnection(Unknown Source)
        at net.wait4it.wlsagent.WlsModule.run(Unknown Source)
        at net.wait4it.wlsagent.WlsServlet.doGet(Unknown Source)
        at net.wait4it.wlsagent.WlsServlet.doPost(Unknown Source)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.eclipse.jetty.server.Server.handle(Server.java:349)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
        at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:857)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
        at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
        weblogic.utils.NestedException: java.lang.AssertionError: Exception creating response stream]
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
        at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
        ... 31 more
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
        weblogic.utils.NestedException: java.lang.AssertionError: Exception creating response stream
        at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
        at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
        ... 34 more

[Ed]

I am running wlsagent-r147

[Ed]

I fixed it by removing the wlfullclient.jar and crerating sym links to wlclient.jar and wljmxclient.jar in the weblogic install to the wlagent lib directory

[Yann Lambret]

Hi Ed,

Thanks for the feedback. I experienced troubles with the regular wlclient.jar and wljmxclient.jar with my WebLogic 12.1 setup, and I fixed it by using the wlfullclient.jar, which also works with the 10.3.4 version. I will amend the wiki to clear things up.

Thanks again,

Yann

2012/11/15 Ed <ed.do...@mavenwire.com>

[Hao Dang]

Hi, Yann

Thanks for your great work!

Actually I think the client jar issue really matters. Shall you add the tips about how to create a wlfullclient.jar into some readme stuff? 

在 2012年11月16日星期五UTC+8上午5时26分08秒，Yann写道：

[Yann]

Hi Hao,

The correct setup is to use sym links to wlclient.jar, wljmxclient.jar and weblogic.jar. If you want to copy the files, you will have to add some dependencies to avoid NoClassDefFoundError. It's really important that you load the wljmxclient.jar file before the weblogic.jar file, or the plugin won't use the right implementation to manage the T3 connection and you will encounter serious performance issues. That's also why it's not ultimately a good idea to use the wlfullclient.jar, because we can predict which implementation will be used. If you need extra information, the plugin wiki is up to date (see Wlsagent page).

Regards,

Yann