PROTECTED]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Thanks Andreas,
I tried removing jms.jar from the war and then deployed with
parent
last
on WAS.
WAS now fills the logs with huge exceptions now :
[10/25/08 20:57:34:171 EDT
@ws.apache.org
Subject: RE: Axis2 JMSListener on Websphere
Hi mgainty,
Actually that is my jmsContext.xml. I also trying my luck
on JSF forum
( http://forums.sun.com/thread.jspa?threadID=5342580)
and spring forum
( http://forum.springframework.org/showthread.php?p=209833#post209833
contained within this transmission.
Date: Sat, 25 Oct 2008 20:55:34 -0700
From: [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Subject: RE: Axis2 JMSListener on Websphere
Hi mgainty,
Actually that is my jmsContext.xml. I also trying my luck
on JSF forum
( http://forums.sun.com
endorse content contained within
this transmission.
Date: Sat, 25 Oct 2008 18:02:58 -0700
From: [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Thanks Andreas,
I tried removing jms.jar from the war and then deployed with parent
last
Subject: Re: Axis2 JMSListener on Websphere
Then the culprit is probably jms.jar.
Andreas
On Sat, Oct 25, 2008 at 01:07, djohnjimmy [EMAIL PROTECTED] wrote:
Hi Andreas,
Thanks for the quick response. But I dont have that jar on my WAR or
classpath.
Jars in my WAR file
]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Then the culprit is probably jms.jar.
Andreas
On Sat, Oct 25, 2008 at 01:07, djohnjimmy [EMAIL PROTECTED] wrote:
Hi Andreas,
Thanks for the quick response. But I dont have that jar on my WAR or
classpath.
Jars
2008 18:02:58 -0700
From: [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Thanks Andreas,
I tried removing jms.jar from the war and then deployed with parent last
on WAS.
WAS now fills the logs with huge exceptions now :
[10/25/08 20:57:34
.
Date: Sat, 25 Oct 2008 18:02:58 -0700
From: [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Thanks Andreas,
I tried removing jms.jar from the war and then deployed with parent
last
on WAS.
WAS now fills the logs with huge exceptions now
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 :
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 [EMAIL PROTECTED] wrote:
I am facing the same problem although with JSF, Spring, MQ and WAS.
JSF requires us to use change Class loader
Hi Andreas,
Thanks for the quick response. But I dont have that jar on my WAR or
classpath.
Jars in my WAR file :
avalon-framework-4.1.3.jar jboss-el-2.0.0.GA.jar
org.springframework.web.servlet-2.5.5.A.jar
commons-beanutils-1.7.0.jar
Then the culprit is probably jms.jar.
Andreas
On Sat, Oct 25, 2008 at 01:07, djohnjimmy [EMAIL PROTECTED] wrote:
Hi Andreas,
Thanks for the quick response. But I dont have that jar on my WAR or
classpath.
Jars in my WAR file :
avalon-framework-4.1.3.jar
other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
Date: Sat, 25 Oct 2008 01:11:54 +0200
From: [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Subject: Re: Axis2 JMSListener on Websphere
Then the culprit is probably jms.jar
Hi Tom,
Im running Websphere 6.1, but i do not have the Web Services Feature Pack
installed. is this something that i should install or is there simply
something missing from my applicaiton classpath on the server?
Thanks,
cathal
Tom Seelbach wrote:
What version of WebSphere? Is it
Hi
Just FYI, some improvements have been made to the JMS transport and is
now available with the Synapse 1.1.1 release at
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/synapse/synapse-transports/1.1.1/synapse-transports-1.1.1.jar
This is an enhanced version of the same
Cathal,
Web Services Feature Pack uses Axis2 internally, so it might help. I don't
know.
I'm not a JMS expert, but I agree with you that it looks like a classpath
problem.
Does section 12.3 in this WebSphere JMS problem determination red paper
help?
What version of WebSphere? Is it WebSphere 6.1 with Web Services Feature
Pack?
-Tom
On Jan 29, 2008 1:20 PM, callagc4 [EMAIL PROTECTED] 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
17 matches
Mail list logo