axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen" <andreas.veit...@gmail.com>
Subject Re: Axis2 JMSListener on Websphere
Date Fri, 24 Oct 2008 23:01:30 GMT
Try to remove the geronimo-jms_1.1_spec-1.1.jar file from your WAR or
EAR. That should solve the problem.

Andreas

On Sat, Oct 25, 2008 at 00:22, djohnjimmy <djohnjimmy@gmail.com> wrote:
>
> I am facing the same problem although with JSF, Spring, MQ and WAS.
>
> JSF requires us to use change Class loader order to "Classes loaded with
> application class loader first" and with the configuration - the
> queueConnectionFactories wont initialze...
>
> And it WAS throws the following exception :
>
> Caused by: java.lang.IllegalArgumentException: Cannot convert value of type
> [com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle] to required type
> [javax.jms.ConnectionFactory] for property 'connectionFactory': no matching
> editors or conversion strategy found
>
> If we Change Class loader order to "Classes loaded with parent class loader
> first", then JSF will not work.
>
> Looks like its either JSF or MQ for us on WAS. Any ideas anyone?
>
>
>
>
>
>
> callagc4 wrote:
>>
>>
>> Hi,
>>
>> I have set up an MQQueueConnectionFactory in Websphere. I have configured
>> my axis2.xml to use this factory for my default JMSListener. On startup
>> the application is successfully finding the Factory reference in the
>> websphere jndi context however i am receiving the following exception
>>
>> "com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle incompatible with
>> javax.jms.ConnectionFactory"
>>
>> This appears to be a classpath issue on the server as i have configured
>> the client to use the same context and jndi reference and it has no
>> problem creating the MQQueueConnectionFactory and placing messages on the
>> queue. The client is a standalone java client, it is running on the ibm
>> websphere jre and i have placed the following classes on the classpath:
>> ibm-jaxrpc-client.jar
>> idl.jar
>> j2ee.jar
>> messagingClient.jar
>> naming.jar
>> namingclient.jar
>> sas.jar
>>
>> Another point to note is that this issue depends on the classloader
>> policy. When the ploicy is set to Application first - single loader i get
>> this issue. However when the ploicy is set to Application first - multiple
>> loaders the listener initializes. unfortunately our application contraints
>> require that our policy is Application fisrt - single loader.
>>
>> Has anybody seen this issue before or are there any ideas as to what may
>> be causing this incompatablility issue?
>>
>> Cheers,
>> Cathal
>>
>
> --
> View this message in context: http://www.nabble.com/Axis2-JMSListener-on-Websphere-tp15165852p20158727.html
> Sent from the Axis - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message