Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Wed, 19 Apr 2017 14:26:41 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12902377.1444033661000.318347.1492612001657@Atlassian.JIRA>
In-Reply-To: <JIRA.12902377.1444033661000@Atlassian.JIRA>
References: <JIRA.12902377.1444033661000@Atlassian.JIRA> <JIRA.12902377.1444033661531@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (CXF-6624) [SOAP][JMS]
 javax.jms.IllegalStateException when setting the exception listener
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 19 Apr 2017 14:26:46 -0000


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

Christian Schneider resolved CXF-6624.
--------------------------------------
    Resolution: Not A Problem

I don't think this is an issue in the CXF JMS transport. It looks like the =
resource adapter you use in jboss simply does not support this method.


> [SOAP][JMS] javax.jms.IllegalStateException when setting the exception li=
stener
> -------------------------------------------------------------------------=
------
>
>                 Key: CXF-6624
>                 URL: https://issues.apache.org/jira/browse/CXF-6624
>             Project: CXF
>          Issue Type: Bug
>          Components: JMS, Transports
>    Affects Versions: 3.1.1
>            Reporter: Fr=C3=A9d=C3=A9ric Pirson
>            Assignee: Christian Schneider
>
> Hello,
> I need to use soap over jms via tibco for some service.
> Spring config :=20
> {code:xml}
>     <jaxws:endpoint
>             xmlns:tns=3D"http://blabla.be/WSDL/BE/BE_RiskAcceptance_BUS/1=
/GetRiskAcceptanceStatus/1"
>             id=3D"GetRiskAcceptanceStatus"
>             serviceName=3D"tns:GetRiskAcceptanceStatus"
>             endpointName=3D"tns:GetRiskAcceptanceStatus_Binding_JMS"
>             implementor=3D"#GetRiskAcceptanceStatusService" transportId=
=3D"http://cxf.apache.org/transports/jms"
>             address=3D"jms:jndi:ESB.BE.BS.RiskAcceptance.BE_RiskAcceptanc=
e_BUS.1.GetRiskAcceptanceStatus.1.Request"
>             >
>         <jaxws:features>
>             <ref bean=3D"jmsConfigFeatureGetRiskAcceptanceStatus"/>
>         </jaxws:features>
>     </jaxws:endpoint>
> {code}
> When deployment occurs, I see every 5s some reconnection.
> I analyzed what occurs and it comes from org.apache.cxf.transport.jms.JMS=
Destination.=20
> {code:java}
>    private JMSListenerContainer createTargetDestinationListener() {
>         Session session =3D null;
>         try {
>             connection =3D JMSFactory.createConnection(jmsConfig);
>             connection.setExceptionListener(new ExceptionListener() {
>                 public void onException(JMSException exception) {
>                     if (!shutdown) {
>                         LOG.log(Level.WARNING, "Exception on JMS connecti=
on. Trying to reconnect", exception);
>                         restartConnection();
>                     }
>                 }
>             });
>             session =3D connection.createSession(false, Session.AUTO_ACKN=
OWLEDGE);
>             Destination destination =3D jmsConfig.getTargetDestination(se=
ssion);
>             PollingMessageListenerContainer container =3D new PollingMess=
ageListenerContainer(connection,=20
>                                                                          =
                   destination, this);
>             container.setConcurrentConsumers(jmsConfig.getConcurrentConsu=
mers());
>             container.setTransactionManager(jmsConfig.getTransactionManag=
er());
>             container.setMessageSelector(jmsConfig.getMessageSelector());
>             container.setTransacted(jmsConfig.isSessionTransacted());
>             container.setDurableSubscriptionName(jmsConfig.getDurableSubs=
criptionName());
>             Executor executor =3D JMSFactory.createExecutor(bus, "jms-des=
tination");
>             container.setExecutor(executor);
>             container.start();
>             suspendedContinuations.setListenerContainer(container);
>             connection.start();
>             return container;
>         } catch (JMSException e) {
>             throw JMSUtil.convertJmsException(e);
>         } finally {
>             ResourceCloser.close(session);
>         }
>     }
> {code}
> The setExceptionListener invoked on a org.jboss.resource.adapter.jms.JmsS=
essionFactory throw directly that exception with message : "This method is =
not applicable inside the application server. See the J2EE spec, e.g. J2EE1=
.4 Section 6.6";
> For the specs : http://java.cnam.fr/iagl/biblio/spec/j2ee-1_4-fr-spec.pdf=
 page 103 + 104=20
> Something I do wrong or issue in jms transport ?
> Regards


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)