This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
When IBM ELM first starts, it only tries to connect to the database server once. If IBM ELM cannot connect, then IBM ELM enters a fault state and does not try again to reconnect - even if the Database Server comes online again. This is an issue as if the database and ELM application servers are both rebooted at the same time, then the IBM ELM server may never come up due to this race condition.
IBM ELM should retry the database connection at regular intervals (say every 1 minute).
See Case TS016681623 for an example case where this was investigated and confirmed as the way that IBM ELM currently works is to abort and enter a failed state.
The current workaround is either to:
1. Reboot the IBM ELM server, or
2. Restart the IBM ELM service, or
3. Log in as an administrator and reconnect to the Database Server from JTS setup.
All of these workarounds are manual, and cause additional downtime instead of being handled automatically.
Idea priority | Low |
Needed By | Quarter |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.