Hi.
That's weird, any idea why this may be happening, and how to fix this?
I assume it's not really failing because the resource already exists, but
rather because some connection pool(?) fails to create...
asadmin> list-jms-resources
Command list-jms-resources executed successfully.
asadmin> list-jms-resources miServer
Command list-jms-resources executed successfully.
asadmin> create-jms-resource --target miServer --restype
javax.jms.QueueConnectionFactory jms/QueueConnectionFactory
remote failure: Unable to create connection pool.
A resource named jms/QueueConnectionFactory already exists.
Command create-jms-resource failed.
asadmin>