This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
WAS traditional: Allow setting JMS sessions as unshareable from the application configuration
There's a known issue (limitation) when using connections to databases or messaging providers from for example servlets without using server-managed transactions. It's described here:
https://www.ibm.com/support/pages/common-reasons-why-connections-stay-open-long-period-time-websphere-application-server - Shared Connections with Local Transaction Containment https://www.ibm.com/support/pages/how-change-shareable-unshareable-connections https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/cdat_conshrnon.html
The workaround is to set connections as unshared. This can be done in 2 ways in general: 1. Unshareable in resource reference (= application level) 2. defaultConnectionTypeOverride, globalConnectionTypeOverride connection pool custom properties (= server level)
But exactly the same issue also affects JMS sessions in the case of the WebSphere MQ provider. In this case, it's only possible to set sessions as unshareable at the server level. - session.sharing.scope connection factory custom property (= server level) https://www-01.ibm.com/support/docview.wss?uid=swg1PK59605
There's no possibility to configure sessions as unshareable at the application level.
This RFE asks to make it possible to set sessions as unshareable at the application level. - Ideally, Unshareable in resource reference should also affect sessions since they're affected the same way as connections. - If that isn't acceptable for some reason, make it possible via WebSphere specific deployment descriptor such as ibm-web-ext.xml, ibm-web-bnd.xml or deployment.xml used in enhanced ears.
This would make things more consistent and allow developers that workaround the issue via setting res-sharing-scope in resource reference to cover all possible cases and not depend on server-level settings.
Do not place IBM confidential, company confidential, or personal information into any field.