Bad Document File Error

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

 [ERROR] [qtp2132798551-40687] [Manager.EMWebServer.WebStartWebapp] Bad document file: 
java.io.IOException: Close org.eclipse.jetty.server.HttpConnection$SendCallback@9d9070c[PENDING][i=null,cb=org.eclipse.jetty.server.HttpChannel$SendCallback@66006f74] in state PENDING
 at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:428)
 at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:512)
 at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:366)
 at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:345)
 at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:1062)
 at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
 at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
 at java.lang.Thread.run(Thread.java:748)
[ERROR] [qtp2132798551-40627] [Manager.EMWebServer.WebStartWebapp] Bad document file: 
java.io.IOException: Close org.eclipse.jetty.server.HttpConnection$SendCallback@45684b51[PENDING][i=null,cb=org.eclipse.jetty.server.HttpChannel$SendCallback@ea9006c] in state PENDING
 at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:428)
 at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:512)
 at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:366)
 at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:345)
 at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:1062)
 at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
 at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
 at java.lang.Thread.run(Thread.java:748)

Environment

Release : 10.7.0

Component : Integration with APM

Resolution

Related to SSL . May be related to connection issues. Closed since error was having no impact.

Additional Information

The "Bad document file" error appeared to be related to closing a SSL connection in PENDING state according to its exception call stack.  Looking up the 10.7 EM code, the error could be raised from an IOException upon processing an request for Workstation web start jar resources.  There should be debug messages containing words like "WebStartResourceServlet" prior to this error message, but the uploaded EM log didn't capture any.