2012-08-28 7 views
1

Mon serveur de méthode documentum java sur le lieu de travail a récemment rencontré un problème de mémoire insuffisante. En regardant autour de l'Internet, certaines personnes ont suggéré que c'est un problème connu, voici la citation: "C'est un problème connu avec WLS 7.0 SP7 (CR300032 et CR196369) lié à CompleteHTTPMessageTimeout. WebLogic Server ferme par intermittence une connexion tout en répondant lentement . clients Si vous avez un contrat de support, vous pouvez ouvrir une demande de service et obtenir le patch et les détails de la CR »Erreur de mémoire insuffisante Documentum

J'ai joint un extrait des journaux ci-dessous:

Cela fait partie seulement de la journaux entiers en raison de la limite d'espace sur le débordement de la pile

####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:34 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767034921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:40 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '42' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767040921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:46 AM EST> <Info> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '123' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767046921> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.> 
####<24/08/2012 10:10:51 AM EST> <Critical> <WorkManager> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <weblogic.timers.TimerThread> <<WLS Kernel>> <> <> <1345767051421> <BEA-002911> <WorkManager weblogic.kernel.System failed to schedule a request due to java.lang.OutOfMemoryError: unable to create new native thread 
java.lang.OutOfMemoryError: unable to create new native thread 
    at java.lang.Thread.start0(Native Method) 
    at java.lang.Thread.start(Thread.java:574) 
    at weblogic.work.RequestManager.createThreadAndExecute(RequestManager.java:271) 
    at weblogic.work.RequestManager.executeIt(RequestManager.java:245) 
    at weblogic.work.ServerWorkManagerImpl.schedule(ServerWorkManagerImpl.java:142) 
    at weblogic.timers.internal.TimerManagerImpl.execute(TimerManagerImpl.java:631) 
    at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:270) 
> 
####<24/08/2012 10:15:33 AM EST> <Info> <Server> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[STANDBY] ExecuteThread: '125' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345767333437> <BEA-002634> <The server "adminServer" disconnected from this server.> 
####<24/08/2012 10:42:56 AM EST> <Error> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '108' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345768976609> <BEA-101017> <[[email protected] - appName: 'acs', name: '/ACS', context-path: '/ACS'] Root cause of ServletException. 
java.net.SocketException: Connection reset 
    at java.net.SocketInputStream.read(SocketInputStream.java:168) 
    at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:138) 
    at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:199) 
    at com.documentum.acs.sdi.ACS.getPostUrlQuery(ACS.java:246) 
    at com.documentum.acs.sdi.ACS.doPost(ACS.java:72) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) 
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) 
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) 
    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:3214) 
    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:1983) 
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890) 
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344) 
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) 
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) 
> 
####<24/08/2012 10:42:56 AM EST> <Error> <HTTP> <b1knoxp0028> <DctmServer_MethodServer_B1KNOXP0028> <[ACTIVE] ExecuteThread: '67' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345768976640> <BEA-101017> <[[email protected] - appName: 'acs', name: '/ACS', context-path: '/ACS'] Root cause of ServletException. 
java.net.SocketException: Connection reset 
    at java.net.SocketInputStream.read(SocketInputStream.java:168) 
    at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:138) 
    at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:199) 
    at com.documentum.acs.sdi.ACS.getPostUrlQuery(ACS.java:246) 
    at com.documentum.acs.sdi.ACS.doPost(ACS.java:72) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) 
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) 
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) 
    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:3214) 
    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:1983) 
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890) 
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344) 
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) 
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) 
+0

Bonjour, encore une fois, s'il vous plaît laissez-moi savoir si vous avez besoin de plus d'informations, merci pour votre temps sur mon problème – dale

Répondre

0

Si vous suspectez une fuite de mémoire dans votre application ou dans un code WLS, vous pouvez essayer Plumbr. Il a de bons antécédents.

0

Il semble que votre JVM prend trop de temps à répondre ou à accepter une requête et qu'elle cause des problèmes sur toute la ligne. Je pense que vous pourriez augmenter la valeur du délai d'attente (je ne sais pas où le faire dans BEA) pour laisser au processus plus de temps pour terminer et augmenter la quantité de mémoire utilisée par le service. Si cela ne fonctionne pas, votre service perd probablement de la mémoire.

Bien sûr, il s'agit d'une solution de contournement, si l'outil est buggé, vous devrez le patcher.