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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
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.