It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×10,958
×3,951
×64
×58

question asked: Nov 28 '13, 2:49 p.m.
question was seen: 7,929 times
last updated: Dec 12 '13, 6:05 a.m.

Related questions

Heads-up: iFixes IFPM98576 and IFPM98578 for WebSphere break RRC

4
Christian Glockner (166●1●3) | asked Nov 28 '13, 2:49 p.m.
edited Dec 04 '13, 5:25 a.m.
Hello,

Just to give everyone a heads-up, WebSphere released iFix IFPM98576 last week to address APAR PM98576. This iFix upgrades the version of the JDK used by WebSphere version 8 to SR7. Unfortunately RRC is incompatible with this version of the JDK and it will stop working.

Once the iFix has been applied, access to RRC will fail with 500 Server Error messages and the details (and the logs) will show an error such as this: 

com.ibm.rdm.fronting.server.services.storedqueries.internal.model.StoredQueryQueryModel incompatible with java.lang.Comparable

This issue affects all versions of WebSphere Application Server V8 when iFix IFPM98576 is installed. WebSphere Application Server V7 may be affected too because a similar iFix was released for that version as well, but this is currently not known.

It appears this issue will be resolved in version 4.0.6 of RRC. In the meantime you are advised not to install WebSphere iFix IFPM98576 in the first place or to uninstall it if you have already installed it.

Update (Nov 29, 11:30 CET): iFix IFPM98578 for WebSphere Application Server V7 also causes this problem.
Update (Nov 29, 15:10 CET): There is now a Flash Alert to alert clients of the situation.
Update (Dec 4, 11:20 CET): Clients who are using RRC version 4 and who wish to install one of the iFixes above can now contact IBM Rational Client Support to receive a Hotfix for the specific version of RRC they are using. The published Flash will be updated shortly to reflect this information.

-Christian
IBM Rational Global Response Team
Comments
Krzysztof Kaźmierczyk commented Nov 28 '13, 4:02 p.m.

Hi Christiam,
Tehcnote could be useful here

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
N Z (362●1●21●27) | answered Nov 28 '13, 4:44 p.m.
 Thanks for the info, I'm sure it was communicated as soon as it came to light, so much appreciated.

It highlights one of the weaknesses of the CLM tools, too many moving parts, too complex, too many things to go wrong.

If IBM can't even do regression when something changes, what hope has the customer got?

In the 2 organisations I've been in using CLM, both used WAS, and I'm constantly amazed when calling support (or even the devs for that matter), they have a Tomcat focus, in many cases, support did not even have an environment that matches our own, and we were using standard technologies!

I'd like to see IBM, the Jazz Team and support improve much more in the area, because from my point of view, it appears you've created a product that can't be supported as well as it could be.
1
permanent link
Paul Ellis (1.3k●6●13) | answered Dec 06 '13, 12:00 p.m.
JAZZ DEVELOPER
edited Dec 12 '13, 6:05 a.m.

Thanks Christian for your immediate announcement.  See: http://www-01.ibm.com/support/docview.wss?uid=swg21657605 for the official statement from IBM.

Especially for Tomcat users on 4.0.5: http://www-01.ibm.com/support/docview.wss?uid=swg21655852

Also see the security vulnerabilities post: http://www-01.ibm.com/support/docview.wss?uid=swg21656459

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.