Hi Conny,
Sorry for the delay in responding,
The description looks fine,
Could you set ConnectionValidationEnabled=true and
--failallconnections=true when creating the pool. As of now this is the
only reason we can think of for the the problem you are facing.
asadmin create-connector-connection-pool --raname genericra
--connectiondefinition javax.jms.QueueConnectionFactory
--transactionsupport NoTransaction --failallconnections=true --property
ConnectionFactoryJndiName=QCF:ConnectionValidationEnabled=true
MypoolQCF
And also verify in domain.xml if the properties have been set across the
pool.
Thanks
-Ramesh
conny.gyllendahl_at_crosskey.fi wrote On 09/27/06 12:27,:
>
>
>
> Here is a description of the setup on our side:
>
> adm01 - SunApp domain administration server
> app01 - application host 1
> app02 - application host 2
> clu01 - SunCluster host 1
> clu02 - SunCluster host 2
>
> app01 and app02 are in an appserver cluster. Nothing special there,
> just a standard Appserver 8.1 EE installation.
>
> WebSphere MQ 5.3 client+manpages installed on app01, app02
> WebSphere MQ 5.3 client+server+manpages installed on clu01, clu02
>
> The cluster (clu01, clu02) has a resource group critical_rg
> including the following:
> - a filesystem: /critical
> - a logical hostname/ip: critical/10.11.12.13
> (all of these are moved to the other node on a fail/switch over)
> - a start script that runs when the resource group is started
> - a stop script that runs when the resource group is stopped
>
> Queuemanager QMGR created on node that runs critical_rg.
> Updated /var/mqm/qms.ini on other node info for QMGR.
> Moved /var/mqm/qmgrs/QMGR to /critical/mqm/qmgrs/QMGR.
> Moved /var/mqm/log/QMGR to /critical/mqm/log/QMGR.
> Symlinked /var/mqm/qmgrs/QMGR to /critical/mqm/qmgrs/QMGR on both nodes.
> Symlinked /var/mqm/log/QMGR to /critical/mqm/log/QMGR on both nodes.
>
> Start script runs "strmqm QMGR"
> Stop script runs "endmqm -i QMGR"
>
> I used JMSAdmin on both machines (app01, app02) to store the information in
> /var/mqm/JNDI/.bindings:
>
> def qcf(QCF) hostname(10.11.12.13) port(1414) channel(SYSTEM.DEF.SVRCONN)
> transport(CLIENT) qmanager(QMGR)
> def q(TQueue) queue(LOCAL.QUEUE) qmanager(QMGR)
>
> I also ran "runmqsc QMGR < /opt/mqm/java/bin/MQJMS_PSC.mqsc".
>
> Here are the asadmin commands:
>
> asadmin create-resource-adapter-config --property
> SupportsXA=false:ProviderIntegrationMode=jndi:UserName=mqm:Password=*****:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:\\/\\/\\/var\\/mqm\\/JNDI:LogLevel=finest
> genericra
>
> asadmin deploy --target my-cluster /tmp/genericra.rar
>
> asadmin create-connector-connection-pool --raname genericra
> --connectiondefinition javax.jms.QueueConnectionFactory
> --transactionsupport NoTransaction --property ConnectionFactoryJndiName=QCF
> MypoolQCF
>
> asadmin create-connector-resource --poolname MypoolQCF --target my-cluster
> jms/MyQCF
>
> asadmin create-admin-object --raname genericra --restype javax.jms.Queue
> --property DestinationJndiName=TQueue --target my-cluster jms/RequestQ
>
> Add the following to
> /var/opt/SUNWappserver/domains/domain1/config/server.policy:
>
> // Generic Resource Adapter for JMS
> grant {
> permission java.util.logging.LoggingPermission "control";
> permission java.util.PropertyPermission "*", "read,write";
> };
>
> Added these to "Classpath Suffix" for the app cluster:
> /opt/mqm/java/lib/com.ibm.mq.jar
> /opt/mqm/java/lib/com.ibm.mqbind.jar
> /opt/mqm/java/lib/com.ibm.mqjms.jar
> /opt/mqm/java/lib/providerutil.jar
> /opt/mqm/java/lib/jndi.jar
> /opt/mqm/java/lib/fscontext.jar
>
> Added these to "Native Library Path Suffix" for the app cluster:
> /opt/mqm/java/lib
> /opt/mqm/lib
>
>
>
> Binod.Pg_at_Sun.COM skrev 27.09.2006 05:49:41 :
>
>
>>conny.gyllendahl_at_crosskey.fi wrote:
>>
>>
>>>
>>>I would probably have to get an ok from the security department for
>>>that, and probably have to remove/anonymize some data/settings from
>>>the config files. And knowing them that would either take a few weeks
>>>or result in an instant "No!". :-(
>>>
>>>Would it help if I instead send you the commands I typed into JMSAdmin
>>>and asadmin to set everything up? That I could do fairly quick by just
>>>changing some IP-adresses and names.
>>>
>>>
>>
>>Yes. That would be fine.
>>
>>- Binod
>>
>>
>>>regards,
>>>Conny
>>>
>>>
>>>Binod.Pg_at_Sun.COM skrev 26.09.2006 18:53:28 :
>>>
>>>
>>>
>>>
>>>>Can you please send us the domain.xml and the WMQ
>>>>ConnectionFactory configuration in the JNDI store
>>>>(using JMSAdmin)?
>>>>
>>>>thanks,
>>>>Binod.
>>>>
>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
>>>For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>>>
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
>>For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>