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

Fabien Bulourde commented on CXF-7197:
--------------------------------------

HI,

I work with Jerôme and I test the fix durring the migration to CXF 3.2.4.

Unfortunatly, we still have the problem on Weblogic.

When I try to connect to a secure queue on Weblogic using SOAP over JMS, with 
no security information in the endpoint, JMSSecurityException occur in loop at 
CPU speed (the initial case explained by Jerôme).

I try to reproduce the same test with Active MQ and the behavior is different : 
in JMSDestination#createTargetDestinationListener(), the exception is thrown by 
  
  session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
  
So, it's JMSDestination#restartConnection() how catch it and I use the 
"retryInterval" parameters to wait.

With Weblogic, the exception occur when the container start in 
JMSDestination#createTargetDestinationListener() so it's the 
PollingMessageListenerContainer who catch it and use the ExceptionListener to 
treat it (defined in JMSDestination#createTargetDestinationListener()) : it 
loop creating thread in order to restart at CPU speed.

> 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
>            Priority: Major
>              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
(v7.6.3#76005)

Reply via email to