Opened 12 years ago
Closed 12 years ago
#2186 closed defect (invalid)
Invalid stream header exception
| Reported by: | cmy | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | General | Version: | 2.0.2 |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
####<2012-11-15 上午09时43分30秒 CST> <Error> <HTTP> <jjgl> <qxx> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352943810996> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@182d86 - appName: 'mapguide', name: 'mapguide', context-path: '/mapguide'] Root cause of ServletException. org.osgeo.mapguide.MgInvalidStreamHeaderException: Invalid stream header exception.
at org.osgeo.mapguide.MapGuideJavaApiJNI.MgMap_CreateSWIG_0(Native Method) at org.osgeo.mapguide.MgMap.Create(MgMap.java:46) at jsp_servlet._mapviewerjava.mapframe._jspService(mapframe.java:329) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) 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:3272) 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:2019) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1925) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1394) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
This is not a bug report.
You didn't specify your environment.
You didn't specify your steps for reproduction and what type of data was involved.
And the error in question is known to be one of very little consequence. Stream header exceptions happen with dropped connections, but they are not dangerous in any way. And if this error did have a major impact, you didn't even mention how!
Not to mention 2.0.x series of MapGuide is way too old for any one of us to provide support.