Chhotisiaasha's Blog

AXIS webservice deployment on Websphere

Posted on: February 2, 2010

Last week I was working on deploying  my axis webservice on WebSphere 6.1 server for the first time. Till now they were using websphere 5.1, but we needed to move the extended service to Websphere 6.1 . Some JDBC datasources Websphere V4 were existing on  the new server, may be for some other application, not sure.

When I installed my application, I got following exception.

Exception thrown [] Msg[Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object.] RootCauseExcp[javax.naming.NamingException] RootCauseMsg[Attempted to use a 4.0 DataSource from a 2.3 (or higher) servlet. Invalid configuration.] RootCauseToString[javax.naming.NamingException: Attempted to use a 4.0 DataSource from a 2.3 (or higher) servlet. Invalid configuration.]
faultActor: null
stackTrace: AxisFault

To resolve this I had to create WebSphere V5 datasources and had to delete the earlier V 4 datasources then only it could recognize the V5 datasources. It seems, but default it was looking for some V4 datasources. While creating V5 datasources, I read from IBM docs, that I will also need to create some J2C authentication alias, to supply for the dasources. I created it, and as per the documentation, it was preceded by some node name. This resolved the problem and I was able to successfully access the database, but still need to understand why it pick a different node name than one on which I installed application.


Leave a Reply

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

You are commenting using your 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


  • None
  • No comments yet
%d bloggers like this: