[
https://issues.apache.org/jira/browse/CXF-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976581#comment-15976581
]
Christian Schneider commented on CXF-7197:
------------------------------------------
I pushed a possible solution to a branch:
https://github.com/apache/cxf/commit/1f7241ba6017f1496e9b8aadec5c807ed05e63b4
I would be happy if you could review and report if it works for your case.
> 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
> Assignee: Christian Schneider
> 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.15#6346)
