Sorry, my mistake. I meant not com.ibm.mq.jms but com.ibm.mq.
On 18.03.2015 20:39, Krzysztof Sobkowiak wrote:
> Hi
>
> Could you please check first if you have installed any bundle exporting the
> com.ibm.mq.jms package?
>
> exports | grep com.ibm.mq.jms
>
> Probably one of the bundles you have installed provides this package.
>
> Please check next if your bundle (which fails) imports the missing package
> com.ibm.mq.jms
>
> headers id-of-your-bundle
>
> If not, enable the dynamic imports and check again the imports of your bundle
>
> dynamic-import id-of-your-bundle
> headers id-of-your-bundle
>
> If it helps, and you can probably see some more imports including the missing
> package, add the additional packages to
> your bundle's imports
>
> I have no experiences with MQ, but hope it helps you to go further
>
> Regards
> Krzysztof
>
>
> On 13.03.2015 19:19, pchakinala wrote:
>> Hi,
>> We are using SMX 4.4 and planning to communicate Websphere Message Queue. We
>> deployed below jar files into OSGI Container and able to communicate
>> Websphere Message Queue. However we noticed Deployment errors when security
>> exit has enabled
>>
>> <bean id="connectionFactory" class="com.ibm.mq.jms.MQConnectionFactory">
>> <property name="transportType" value="1"/>
>> <property name="channel" value="${QUEUE-CHANNEL}"/>
>> <property name="hostName" value="${MQSERVER-ADDRESS}"/>
>> <property name="port" value="${MQSERVER-PORT}"/>
>> <property name="queueManager" value="${MQ-MANAGER}"/>
>>
>> <property name="securityExit"
>> value="biz.capitalware.mqausx.MQAUSXJ2EE"
>> />
>> <property name="securityExitInit"
>> value="hvk003:nnn"></property>
>> </bean>
>>
>> Exception:
>> java.lang.NoClassDefFoundError: com/ibm/mq/MQExitChain
>> at java.lang.Class.getDeclaredMethods0(Native Method)[:1.6.0_31]
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)[:1.6.0_31]
>> at java.lang.Class.getDeclaredMethod(Class.java:1935)[:1.6.0_31]
>> at
>> com.ibm.mq.jmqi.remote.exit.RemoteExitChain.<clinit>(RemoteExitChain.java:157)
>> at
>> com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSecurityExits(RemoteConnection.java:1573)
>> at
>> com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:348)
>> at
>> com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:264)
>> at
>> com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:144)
>> at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1690)
>> at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1343)
>> at
>> com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:342)
>> at
>> com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6772)
>> at
>> com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6151)
>> at
>> com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:280)
>>
>> Here enclosed exception details as an attachement. Please suggest me how to
>> resolve this issue.
>>
>> Configured Websphere Message Queue OSGI jar files:
>>
>> <bundle>wrap:file:system/bundles/com.ibm.mq.osgi.directip_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.commonservices.j2se_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.jms.prereq_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.jms_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.nls_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.wmq.nls_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.wmq.prereq_7.1.0.3.jar</bundle>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.msg.client.osgi.wmq_7.1.0.3.jar</bundle>
>>
>>
>> <bundle>wrap:file:system/bundles/com.ibm.mq.osgi.java_7.1.0.3.jar</bundle>
>>
>> Regards,
>> pchakinala
>> exception_details.txt
>> <http://servicemix.396122.n5.nabble.com/file/n5722358/exception_details.txt>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://servicemix.396122.n5.nabble.com/Websphere-MQ-Security-Exit-tp5722358.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Krzysztof Sobkowiak
JEE & OSS Architect
Senior Solution Architect @ Capgemini SSC <http://www.pl.capgemini-sdm.com/en>
Apache ServiceMix <http://servicemix.apache.org/> Committer & PMC
