You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/19 13:33:30 UTC

[jira] [Resolved] (DOSGI-65) CRASH/FREEZE after a running for a while on production system

     [ https://issues.apache.org/jira/browse/DOSGI-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved DOSGI-65.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Sergey Beryozkin

Perhaps this was somehow related to the pax-web bug reported in DOSGI-64;
                
> CRASH/FREEZE after a running for a while on production system
> -------------------------------------------------------------
>
>                 Key: DOSGI-65
>                 URL: https://issues.apache.org/jira/browse/DOSGI-65
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>    Affects Versions: 1.1
>         Environment: Sun Netra 5120, Java 6, felix 2.0.1
>            Reporter: Michael Zehender
>            Assignee: Sergey Beryozkin
>            Priority: Blocker
>
> The system ran fine for a few weeks and then the web services froze - every single one of them.
> Other services like JMS and JBoss Remoting (which used the same business logic) still worked fine. Unfortunately the support team immediately restarted the system (as it is a production system it's very understandable) so I couldn't get a thread dump - if it happens again I will attach it to this bug.
> The bug was triggered on a Sun Netra 5120 with 64 cores.
> VERY VERY CRITICAL!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira