Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
This enhancement for domino java agent to allow threads to persist which is required by JMS API is very critical to use features/functionalities of MQ above version 8 and other alternatives is having some impact or drawbacks. Please don't wait for more votes on this and understand the importance of this enhancement.
This enhancement is business critical for applications within IBM.
A work around is to set SHARECNV to 0. Then the channel is made compatible to version 6. See also https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001660_.htm
Has anyone tried this using an application scope bean?
Just curious, can you use DOTS instead of java agent in NSF ? In theory since DOTS is initialised when server is started then the threads should be persistent, right ?
This enhancement is business critical for IBM. Numerous applications using Domino Java agent designed to call IBM MQ client layer. There are chances of multiple other customers having the same issue. MQ V7.x is EOL product , So we have to go with MQ v.8 however MQ API won't work with MQ v8 neither JMS API works !! So Please consider this request as a severity-1 issue. DO NOT WAIT for voting count !!