Wednesday, 18 November 2009

WSWS7007E and WSVR0501E Conflict between Lotus Connections 2.5 and Feature Pack for Web Services for WebSphere Application Server V6.1

This is the first of two posts documenting some fun n' games that I've recently seen with LC 2.5 on a WAS environment that also included this Feature Pack: -

Utility: Feature Pack for Web Services for WebSphere Application Server V6.1

I'll document the more pressing issue in the next day or so, but wanted to mention that, on my own environment ( aka Orac ), I hit the following exceptions when trying to start Connections: -

WSWS7007E: The peoplepages.war application module cannot be loaded correctly because of the following error: Annotation processing failed for class:  com/ibm/lconn/profiles/internal/service/AbstractCodesService.class

and: -

WSVR0501E: Error creating component null [class] Annotation processing failed for class:  com/ibm/lconn/profiles/internal/service/AbstractCodesService.class

In essence, I was installing the Feature Pack onto an existing node ( the first, and currently only, node within a WAS 6.1 cell/cluster ) that was running WebSphere Application Server Network Deployment

The Feature Pack ( downloaded as 6.1.0-WS-WAS-WSFEP-LinuxX32.tar.gz ) went in without problems, but I was then unable to start Connections.

The Annotation Exception problem is/was well known in earlier versions of WAS, as a Google search will show.

In the end, I had to do the following: -

a) Remove the Feature Pack
b) Remove the fixpack for WAS ND ( and its corresponding SDK fix pack 23 )
c) Install the Feature Pack ( which in turns upgrades WAS and the SDK to fix pack 9 )
d) Install and 6.1.0-WS-WASWebSvc-LinuxX32-FP0000023.pak for the Feature Pack
e) Install 6.1.0-WS-WASSDK-LinuxX32-FP0000023.pak and 6.1.0-WS-WAS-LinuxX32-FP0000023.pak

Having done all of the above, now returns: -

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.
WVER0012I: VersionInfo reporter version, dated 11/12/08

IBM WebSphere Application Server Product Installation Status Report

Report at date and time November 17, 2009 9:35:40 PM GMT

Product Directory        /opt/IBM/WebSphere/AppServer
Version Directory        /opt/IBM/WebSphere/AppServer/properties/version
DTD Directory            /opt/IBM/WebSphere/AppServer/properties/version/dtd
Log Directory            /opt/IBM/WebSphere/AppServer/logs
Backup Directory         /opt/IBM/WebSphere/AppServer/properties/version/nif/backup
TMP Directory            /tmp

Product List
ND                       installed
WEBSERVICES              installed

Installed Product
Name                     IBM WebSphere Application Server - ND
ID                       ND
Build Level              cf230910.10
Build Date               3/10/09

Installed Product
Name                     WebServices Feature Pack
ID                       WEBSERVICES
Build Level              cf230907.03
Build Date               2/21/09

End Installation Status Report

and, perhaps MORE importantly, Connections 2.5 now starts, and then I hit the next problem ...

CLFRO0002E: Failed to post the bookmark to Bookmarks. java.lang.ClassCastException: org.apache.abdera.parser.stax.FOMText incompatible with

This is definitely a conflict between the Web Services Feature Pack and Lotus Connections, but I'm not yet sure how to resolve it .....

WATCH THIS SPACE ->>>>        <<<<--


Anglo said...

Our LC2.5 is also running on WAS, but we have another project requiring WAS with Feature pack for Web Services. We had problem with at the second platform, so we moved to and it is stable ... so far. About class cast exception I suggest first to try to change CLASSLOADER option - especially if it is currently "PARENT FIRST" to "PARENT LAST". Probably in this case the required class will be found into Bookmarks App library, not the global one. Hope this help!

Anglo said...

One more thing... Initially when we started developing applications required Feature Pack for Web Services, we got similar Annotation exception originating from DB2 jdbc driver and the server didn't start at all. So we had to change DB2 JDBC library to version 9.5. It is not the same case, but good to know.

Dave Hay said...

@Anglo - thanks, will check it out