[
https://issues.apache.org/jira/browse/CXF-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032889#comment-13032889
]
Freeman Fang commented on CXF-3494:
-----------------------------------
Hi,
Could you configure your JBoss container to use self first way to avoid loading
container's saajapi and saajimpl.jar to see if it helps?
In any case I don't think this is something we can fix in CXF.
Freeman
> 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
>
> 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
