Resolution:
The WebLogic application server's logs may present errors such as the following when running GridServer.
These errors are cosmetic and will not affect GridServer or WebLogic.
An example of the errors are as follows:
&ltJul 30, 2004 3:39:23 PM EDT> &ltError> &ltHTTP> &ltBEA-101045>
<[ServletContext(id=21 447570,name=livecluster,context-path=/livecluster)]
Could not resolve taglib location WEB-INFlibrequest.jar: no such jar file was found. It should be in the WEB-INF/lib directory>
&ltJul 30, 2004 3:39:57 PM EDT> &ltWarning> &ltHTTP> &ltBEA-101248>
<[null]: Deployment descriptor "web.xml" is malformed. Check against the DTD: org.xml.sax.SAXParseException: Attribute "role-name" must be declared for element type "auth-constraint". (line 260, column 42).>
&ltApr 19, 2005 7:31:49 AM EDT> &ltError> &ltHTTP> &ltBEA-101083> &ltConnection failure.
java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '48864' bytes instead of stated: '55161' bytes.
        at weblogic.servlet.internal.ServletOutputStreamImpl.ensureContentLength(ServletOutputStreamImpl.java:470)
        at weblogic.servlet.internal.ServletResponseImpl.ensureContentLength(ServletResponseImpl.java:1176)
        at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1188)
        at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2590)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Errors in logs when using a WebLogic application server