cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3494) Out Of Memory Exception
Date Tue, 30 Aug 2011 18:08:38 GMT

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

Daniel Kulp resolved CXF-3494.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid


Definitely more of a "container integration and configuration" issue and not really something
that can be fixed in CXF.

> Out Of Memory Exception
> -----------------------
>
>                 Key: CXF-3494
>                 URL: https://issues.apache.org/jira/browse/CXF-3494
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3.4
>         Environment: Windows 64Bit Jboss5.1 cxf 2.3.4
>            Reporter: jacques hefer
>             Fix For: Invalid
>
>
> We have multiple war files exposing different endpoints. We use Wss4J Interceptor which
in turn calls SAAJInInterceptor.
> When only one War is running everything works fine. When both are running and you call
a service on the first war it works. when you call it on the second War it hangs on MessageFactory.newInstance(....);
in the SAAJ interceptor
> Which eventually leads to a out of memory exception.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message