Varun,
You probably didn't even need to extends the class, because MQ is
installed on the same machine. We had to do this a while back because
MQ was running on System i and the credentials didn't match.
Can you retry with the default MQConnectionFactory and post the
exception stack trace you get?
Gert
unni_varun wrote:
Gert,
Yeah i remember the discussion we had on this. This is what i did.
1) Wrote a java class which extends MQQueueConnectionFactory class and
overrides the createQueueConnection() method. I gave my windows user
id/password in that. (IBM MQ was installed using the same.)
2) Created the jar file for this java class and kept in
Jboss-4.0.5.GA\server\default\lib folder.
3) Modified the xbean.xml of jms su. Please look at this.
<jms:endpoint service="iq:jms"
endpoint="endpoint"
role="provider"
destinationStyle="queue"
jmsProviderDestinationName="Q1.SQ"
connectionFactory="#connectionFactory" />
<bean id="connectionFactory" class="IQQueueConnectionFactory">
<property name="queueManager" value="SampleQM1" />
<property name="transportType" value="1" />
<property name="hostName" value="localhost" />
<property name="port" value="1417" />
</bean>
IQQueueConnectionFactory is the jar file holding my java class.
Now when i deploy my SA in jboss i'm getting exception in my
servicemix-shared component. It was mentioning "Unable to deploy
servicemix-shared component."
So this is where i'm stuck up. Right now jboss is throwing access violation
error. So cant get the actual stack trace.
