Hi Binod
Pls see inline..
Binod wrote:
> Hi Max,
>
>> Hi Binod
>>
>> With genericjmsra deployed and "connector-connection-pool"
>> reconfigured in SJSAS8.1 as -
>>
>> asadmin create-connector-connection-pool --port 5050 --raname
>> genericra --connectiondefinition javax.jms.QueueConnectionFactory
>> --property
>> SupportsXA=true:ProviderIntegrationMode=javabean:ConnectionFactoryClassName=com.ibm.mq.jms.MQConnectionFactory:CommonSetterMethodName=setProperty:UserName=guest:Password=guest:QueueConnectionFactoryClassName=com.ibm.mq.jms.MQQueueConnectionFactory:TopicConnectionFactoryClassName=com.ibm.mq.jms.MQTopicConnectionFactory:QueueClassName=com.ibm.mq.jms.MQQueue:TopicClassName=com.ibm.mq.jms.MQTopic:LogLevel=info:XAQueueConnectionFactoryClassName=com.ibm.mq.jms.MQXAQueueConnectionFactory:XATopicConnectionFactoryClassName=com.ibm.mq.jms.MQXATopicConnectionFactory:XAConnectionFactoryClassName=com.ibm.mq.jms.MQXAConnectionFactory
>> jms/wmqQCFpool
>>
>> rem asadmin create-connector-resource --port 5050 --poolname
>> jms/wmqQCFpool jms/wmqQCF
>>
>> asadmin create-admin-object --port 5050 --raname genericra --restype
>> javax.jms.Queue --property DestinationProperties=Name\\=wmqQueue
>> jms/wmqQueue
>>
>> I tried to start up SJSAS8.1 but have the following error -
>>
>> [#|2005-12-19T11:04:11.365+0800|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;|MDB00017:
>> [SimpleMessageEJB]: Exception in creating message-driven bean
>> container: [com.sun.enterprise.connectors.ConnectorRuntimeException:
>> Could not find physical destination : null]|#]
>>
>> [#|2005-12-19T11:04:11.365+0800|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;|com.sun.enterprise.connectors.ConnectorRuntimeException
>>
>> 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)
>>
>
> It seems a MDB is deployed to use default SunMQ and the physical
> destination is absent. i.e, the MDB is not configured properly to use
> genericra.
According to SunMQ 3.6sp3 Admin Guide (p.328), there are two
ResourceAdapter JavaBean properties
* addressList / connectionURL - e.g. mq://host:port/jms
which I'm not sure
* it's SunMQ specific so does not work for WMQ ?
and
* put as connector-connection-pool properties directly ?
* or as DestinationProperties name-value pair ?
Any advise?
>> at
>> com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
>>
>> at
>> com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
>>
>> at
>> com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
>>
>> at
>> com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
>>
>> at
>> com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
>>
>> at
>> com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:95)
>>
>> at
>> com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:180)
>> at
>> com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:200)
>>
>> at
>> com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
>>
>> at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
>> at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
>> |#]
>
>> Do you have experience on how to configure the physical destination
>> properties ("DestinationProperties" type-value pairs for
>> connector-connection-pool in SJSAS8.1 domain.xml)?
>
> So far, we have been using jndi as the IntegrationMode for websphere
> MQ. Sushmita, do you have some time to send your configuration to Max?
>
> Also, I havent yet javap'd and seen what are the properties of MQ
> destination class. If you know, one of them should be physical
> destination name. Also, if you increase the log level, you will get
> some more debug information to figure out whats happening.
>
> tahanks,
> Binod.