Hi Ed,
I have been able to reproduce the error on 2.2-SNAPSHOT now. It seems to
happen when the ConnectionFactory is not wrapped in a
SingleConnectionFactory.
With the config style you use this should happen automatically.
Could you provide me with a complete maven sample project that shows the
error? This would help debugging into the problem.
As a workaround you can use the new config style as explained in :
http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html
When you wrap the ConnectionFactory like in the example the error should
not occur. Still I would like to fix this of course ;-)
Greetings
Christian
Ed Scriven schrieb:
Christian,
I have tested my configuration with Tibco 4.3.0 and CXF 2.2-SNAPSHOT.
Unfortunately problems persist.
Although javax.jms.InvalidDestinationException is no longer thrown,
the client times out. Inspecting the Tibco logs shows that the
temporary queue is created successfully but "created receiver failed:
invalid temporary queue" remains.
For your information, my CXF configuration is as follows (please note
that this has been manually typed over from a segregated network):
Server:
<bean id="systemParametersService"
class="system.parameters.SystemParametersServiceImpl" />
<jaxws:endpoint id="systemParameters"
implementor="#systemParametersService" address="jms://" />
<jms:destination
name="{http://system.parameters/SystemParametersServiceImpl}SystemParametersServiceImplPort.jms-destination";>
<jms:address destinationStyle="queue"
jndiConnectionFactoryName="system.parameters.JMSConnectionFactory"
jndiDestinationName="system.parameters.SOAP"
useJms11="true">
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="com.tibco.tibjms.naming.TibjmsInitialContextFactory" />
<jms:JMSNamingProperty name="java.naming.provider.url"
value="tibjmsnaming://localhost:7222" />
</jms:destination>
Client:
<jaxws:client id="systemParametersClient"
serviceClass="system.parameters.SystemParametersService"
address="jms://" />
<jms:conduit
name="{http://system.parameters/SystemParametersServiceImpl}SystemParametersServicePort.jms-conduit";>
<jms:address destinationStyle="queue"
jndiConnectionFactoryName="system.parameters.JMSConnectionFactory"
jndiDestinationName="system.parameters.SOAP"
useJms11="true">
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="com.tibco.tibjms.naming.TibjmsInitialContextFactory" />
<jms:JMSNamingProperty name="java.naming.provider.url"
value="tibjmsnaming://localhost:7222" />
</jms:conduit>
Regards,
Ed
2009/1/28 Christian Schneider <[email protected]>:
Could you try to checkout the CXF head from subversion, compile it and try
it with your project.
I was not yet able to identify the source of the problem but for me it seems
solved on the head.
If it works for you too we can be quite sure that CXF 2.1.4 will include the
fix for this issue.
If your have subversion and maven installed the following will work:
svn co http://svn.apache.org/repos/asf/cxf/trunk
cd trunk
set MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=128M
mvn -Pfastinstall
In your project you then include the just compiled version as:
2.2-SNAPSHOT
Greetings
Christian
Ed Scriven schrieb:
Hello Christian,
Did you get a chance to check your own samples with Tibco EMS?
Regards,
Ed
2009/1/21 Christian Schneider <[email protected]>
Hi Ed,
I will check my own sample with tibco ems.
Greetings
Christian
Ed Scriven schrieb:
Hello,
I am experiencing problems getting JAX-WS CXF with Tibco JMS to work.
My
configuration is derived from the
http://cwiki.apache.org/CXF20DOC/jax-ws-java-first-with-jms-transport.htmland
http://cwiki.apache.org/CXF20DOC/jms-transport.html. I am using Spring.
If I provide a jndiReplyDestinationName on the jms:conduit/jms:address
element all works fine. Unfortunately when I remove this attribute and
expect temporary queues instead Tibco throws a
javax.jms.InvalidDestinationException:
Invalid temporary destination exception. This exception is raised from
the
Spring DefaultMessageListenerContainer requesting Tibco libraries to
create
a consumer.
Having inspected the Tibco logs the temporary queue is created
successfully
named $TMP$.EMS-SERVER.9A049772E795.2. The logs do state that "created
receiver failed: invalid temporary queue".
I have spent a good day trawling Google for anything related to this
issue,
but with no success. Apologies not stack traces nor code, they are on a
segregated network with no Internet access. I can get them if required.
Has anyone experience CXF with Tibco JMS? Has anyone experienced
temporary
queue problems before?
Regards,
Ed
--
Christian Schneider
---
http://www.liquid-reality.de
--
Christian Schneider
---
http://www.liquid-reality.de
--
Christian Schneider
---
http://www.liquid-reality.de
