You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jérôme Tamborini (JIRA)" <ji...@apache.org> on 2016/12/22 16:09:58 UTC

[jira] [Commented] (CXF-7197) Loop on exception during polling message on JMS queue

    [ https://issues.apache.org/jira/browse/CXF-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770402#comment-15770402 ] 

Jérôme Tamborini commented on CXF-7197:
---------------------------------------

Here a PR on github: https://github.com/jerometambo/cxf/pull/1/commits/3be31af0abeb1b8a6c223ac1e3ced0086d8b926f

> Loop on exception during polling message on JMS queue
> -----------------------------------------------------
>
>                 Key: CXF-7197
>                 URL: https://issues.apache.org/jira/browse/CXF-7197
>             Project: CXF
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 3.1.4
>         Environment: CXF 3.1.4, Weblogic 12c, Soap over JMS
>            Reporter: Jérôme Tamborini
>              Labels: exception, jms, security
>             Fix For: 3.2.0
>
>
> Hi, 
> when an exception occurs (in my case JMSSecurityException) during PollingMessageListenerContainer$Poller#run(), it loops at CPU speed and write exception stacktrace in log. This makes the logfile grows very fast and can make the hard drive full on server.
> I can propose a PR (If I got the rights on Fisheye) which is working with the commit related to CXF-6742.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)