MQSeriesAdapter Exception: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed.

After changing the configuration of the MQSeriesAdapter I found below exceptions in the logs:

[2019-09-13T13:18:35.551+02:00] [MS_OSB1] [ERROR] [] [oracle.soa.adapter.mq.inbound] [tid: JCA-work-instance:MQSeries Adapter-44] [userId: <WLS Kernel>] [ecid: 8483ccd4-5c52-41e7-bec5-bf8eeb60f49b-002ba627,0] [partition-name: DOMAIN] [tenant-name: GLOBAL]  [endpoint_name: Service_v1/Proxy/ServiceMQAS] [QueueProcessor] Exception caught in inbound cycle[[ javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to perform another lookup of the Connection Factory eis/MQ/MQSeriesAdapter from JNDI and get a new Connection Handle.

        at weblogic.connector.outbound.ConnectionManagerImpl.checkIfPoolIsValid(ConnectionManagerImpl.java:479)

        at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)

        at oracle.tip.adapter.mq.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:120)

        at oracle.tip.adapter.mq.inbound.BaseQueueHandler.getNewConnection(BaseQueueHandler.java:76)

        at oracle.tip.adapter.mq.inbound.QueueProcessor.run(QueueProcessor.java:238)

        at oracle.tip.adapter.sa.impl.fw.jca.work.WorkerJob.go(WorkerJob.java:53)

        at oracle.tip.adapter.sa.impl.fw.common.ThreadPool.run(ThreadPool.java:281)

        at java.lang.Thread.run(Thread.java:748)

Apparently the changes has caused the connections to the queue manager to become stale. The solution was simple. I had to restart the WebLogic server in order to make it work again!