Hi if you manage to identify which class represents the "connection pool" and which one the "session pool" then you can use the setters (or constructor) through tomee resource instantiation mecanism - http://tomee.apache.org/admin/configuration/resources.html - and potentially link them between them using a reference ($service - <Service> - or @resource - <Resource> - from memory)
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> 2018-02-14 20:50 GMT+01:00 curveman <[email protected]>: > Hi, > > We are currently connecting to some Websphere MQs. We have added the > connection information in tomee.xml and we are able to communicate with the > queues without any issues. However, we got sent some Websphere MQ > recommandations and I am currently trying to figure out if the parameters > will be the same as what we would normally set them on a WebSphere server > or > if there is something specific. I have tried looking for an answer but > found > nothing relevant. > > Here is how we defined the queues : > > <Resource id="wmqRA" type="com.ibm.mq.connector.ResourceAdapterImpl" > class-name="com.ibm.mq.connector.ResourceAdapterImpl"> > connectionConcurrency=5 > maxConnections=10 > logWriterEnabled=true > reconnectionRetryCount=5 > reconnectionRetryInterval=300000 > traceEnabled=false > traceLevel=3 > </Resource> > > <Resource id="jms/CF" type="javax.jms.ConnectionFactory" > class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl"> > TransactionSupport=xa > ResourceAdapter=wmqRA > HostName= host > Port=1414 > QueueManager= qm > Channel= channel > TransportType=Client > SSLCipherSuite=TLS_RSA_WITH_AES_128_CBC_SHA > SSLFipsRequired=false > </Resource> > > <Resource id="jms/queue" type="javax.jms.Queue" > class-name="com.ibm.mq.connector.outbound.MQQueueProxy"> > arbitraryProperties > baseQueueManagerName=qmName > baseQueueName=qName > CCSID=1208 > encoding=NATIVE > expiry=APP > failIfQuiesce=true > persistence=APP > priority=APP > readAheadClosePolicy=ALL > targetClient=JMS > </Resource> > > Here are some of the recommandations we received : > > In “Connections pools” these values are mandatory: > “Connection Timeout” Set to 30 seconds. > “Maximum Connections” Set to minimum 5. A greater value can be evaluated > by > developers. > “Minimum Connections” Set to 0 the minimum connections. To ensure > disconnection. > “Reap time” Set to 30 seconds > “Unused timeout” Set to 300 seconds (5 minutes) > “Aged timeout” Set to 600 seconds (10 minutes) > “Purge Policy” Set to “EntirePool” > > In “Session pool” these values are mandatory: > “Connection Timeout” Set to 30 seconds. > “Maximum Connections” Set to minimum 5. A greater value can be evaluated > by > developers. > “Minimum Connections” Set to 0 the minimum connections. To ensure > disconnection. > “Reap time” Set to 30 seconds > “Unused timeout” Set to 300 seconds (5 minutes) > “Aged timeout” Set to 600 seconds (10 minutes) > “Purge Policy” Set to “EntirePool > > In this situation, will these settings be set at the tomee.xml level or > this > must be set in our code? I know that these are settings that can be set > directly in the Websphere console. > > Thanks in advance for your help. > > Michael > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users- > f979441.html >
