Continous HTTP access error logged when using Weblogic Cluster

Question

I am not sure if this is the right forum for this discussion, but here we go anyways.
We have created a Weblogic Cluster with one Administration Server and up to 12 Managed Servers. Our Weblogic version is 9.2.
SSL has been enabled for all Servers and the HTTP Listen Ports are all turned off. The cluster and all applications are working fine and communicating over HTTP as expected, however the logs grow 3MB+ per hour due to an error that repeatedly logged. This error appears to be an attempt by an internal Weblogic process to access some resource over HTTP.
Here are the various messages received in the logs. There are 3 messages logged per error occurred.
This first log message is from the domain log (I replaced the hostname/IP info with <PEER>):
####<Aug 11, 2008 12:08:46 PM GMT+00:00> <Warning> <Security> <PEER> <ManagedServer7> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1218456526962> <BEA-090475> <Plaintext data for protocol HTTP was received from peer <PEER> instead of an SSL handshake.>
This second log message is from the ".out" log from the Administration Server:
####<Aug 11, 2008 12:08:58 PM GMT+00:00> <Info> <ServletContext-/bea_wls_internal> <PEER> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1218456538658> <000000> <HTTPClntLogin: Login rejected with code: 'Failed', reason: java.net.ProtocolException: HTTP tunneling is disabled
at weblogic.rjvm.http.HTTPServerJVMConnection.acceptJVMConnection(HTTPServerJVMConnection.java:88)
at weblogic.rjvm.http.TunnelLoginServlet.service(TunnelLoginServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3231)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2002)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1908)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1362)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
This last message is from the access.log for the Admin Server:
<PEER> - - [11/Aug/2008:12:08:58 +0000] "GET /bea_wls_internal/HTTPClntLogin/a.tun?wl-login=https+dummy+WLREQS+9.2.2.0+dummy+%0A&rand=8038349418070109915&AS=2048&HL=19 HTTP/1.1" 200 1337
I have searched all over trying to find a solution but with no luck thus far. I have seen some posts about turning on HTTPTunneling and this does seem to prevent the error from occurring, but this is not a solution for us.
I could really use some help in understanding whats going on and trying to resolve this issue. Our client will make a big deal out of this and will want a solution. Any help would be greatly appreciated.
Message was edited by:
user651444

Answer 1

Hi,
We had this problem with WebLogic Platform 9.2 MP2, running on Solaris. The patch CR344429 worked fine. The corresponding patch for 9.2 MP3 is CR370091. You can get these patches through Oracle Support.
A couple of points:
1. We did not have to set StartScriptEnabled=true for the patch to work. We use the SSL Niode manager.
2. Using the t3: protocol (-Dweblogic.management.server=t3://<admin server listen address>:<admin server listen port) does stop these exceptions, but causes these warning messages to appear in the administration server log file:
<Warning> <[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <...> <BEA-002637> <Failed to register a disconnect listener because of weblogic.rmi.extensions.DisconnectMonitorUnavailableException: Could not register a DisconnectListener for [weblogic.rmi.internal.BasicRemoteRef ......>
<Warning>  <[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <...> <BEA-002637> <Failed to register a disconnect listener because of weblogic.rmi.extensions.DisconnectMonitorUnavailableException: Could not register a DisconnectListener for [weblogic.rmi.internal.BasicRemoteRef ......>
Hope these comments help.