Home > WAS > Invalid Implementation Key, com.ibm.ws.transaction.NonRecovWSTxManager

Invalid Implementation Key, com.ibm.ws.transaction.NonRecovWSTxManager

I was getting this com.ibm.websphere.naming.CannotInstantiateObjectException exception with this error a few days ago, with a long stack trace

WARNING: jndiNamingException
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NoClassDefFoundError: Invalid Implementation Key, com.ibm.ws.transaction.NonRecovWSTxManager]
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt( Helpers.java:1000)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup( Helpers.java:705)
... 33 more

when I tried to get a reference to a JNDI datasource in Websphere Application Server.

If you do a search on the file system for a file called “implfactory.jar”, and you unjar it, you will see that it contains a configuration XML file with (among the rest) the following line

<!-- JTA Non Recoverable TransactionManager implementation class -->
<factory interface="com.ibm.ws.transaction.NonRecovWSTxManager" impl="com.ibm.ws.Transaction.client.NonRecoverableTranManagerSet" />

This is where the implementation key com.ibm.ws.transaction.NonRecovWSTxManager is defined, and its corresponding class (com.ibm.ws.Transaction.client.NonRecoverableTranManagerSet). This class can be found in the “com.ibm.ws.runtime_6.1.0.jar” file. You would think that by putting these jars in the classpath the problem would be solved, but alas, these files are (probably) already in the classpath, so it makes no difference.

The solution provided by IBM, does not work either, or, I should better say it didn’t work with me.

An actual and far simpler solution is to add the “com.ibm.ws.webservices.thinclient_6.1.0.jar” in the classpath. This solves the problem and it will probably work for all the “Invalid Implementation Key” errors.

Categories: WAS Tags:
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: