Hi Binod, Sushmita
It seems you did not need to specify physical destination properties _on
SJSAS_ for the WMQ ?! In that case, how does the RA connect to WMQ QM ?
The problem now is not on WMQ QM but SJSAS is complaining on physical
destination properties for WMQ.
[#|2005-12-19T15:19:21.362+0800|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5090:
Exception in creating EJB container
[com.sun.enterprise.connectors.ConnectorRuntimeException: Could not find
physical destination : null]|#]
[#|2005-12-19T15:19:21.362+0800|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|appId=mdb-simple
moduleName=mdb-simpleEjb_jar ejbName=SimpleMessageEJB|#]
[#|2005-12-19T15:19:21.362+0800|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5004:
UnExpected error occured while creating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: Could not find
physical destination : null
at
com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:573)
at
com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
If you have been using LDAP for JNDI, can you list the entries
configured in the JNDI LDAP ? I think I may copy those and specify in
SJSAS directly.
Thanks
Max
Binod wrote:
> Hi Sushmita,
>
> Would you explain the JMSAdmin step, a bit more detail.
>
> thanks,
> Binod.
>
>> Hi Sushmita
>>
>> It seems you did not need to specify physical destination properties
>> for the WMQ ?! In that case, how does the RA connect to WMQ QM ?
>>
>> Can you send me your appserver's domain.xml as well?
>>
>> Thanks
>> Max
>>
>> Sushmita Sharma wrote:
>>
>>> Hi Max,
>>> I've attached a sample sun-ejb-jar.xml for mdb and a
>>> setup script which creates connector connection pool
>>> and resources and resource adapter config in jndi
>>> mode. Hope this will help.
>>>
>>> Summary of steps -
>>> 1. Create queue manager, start queue manager, create
>>> queue conn factory and queues in wmq
>>> 2. In appserver, create resource adapter config and
>>> deploy resource adapter
>>> 3. Update server classpath for wmq classes
>>> 4. Create connector-connection-pool, resource and
>>> admin object
>>> 5. Add resource adapter config in mdb deployment
>>> descriptor
>>>
>>> Please refer to the attached files.
>>>
>>> Regards,
>>> Sushmita.
>>