EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3 feature pack

[Chandrasekhar Elindram]

Hi,

I'm trying to migrate an EJB application from WAS 6.0 to WAS 6.1.0.15 with EJB3 feature pack. Interestingly, what I found was, I could deploy the application on WAS 6.1.0.15 as long as EJB3 feature pack is not installed on it. The moment I install EJB3 service pack on the server, application deployment is failing with one of the following exceptions com.ibm.websphere.naming.CannotInstantiateObjectException or DuplicateHomeNameException.

Did anyone come across this problem and found any resolution for the same?

Thanks in advance,
Chandra.
[ June 12, 2008: Message edited by: Chandrasekhar Elindram ]

[Cameron Wallace McKenzie]

Is it an EJB3 'service pack' or an EJB3 'feature pack.'

You are blazing new ground in this WebSphere forum by using EJB3. Not many posts on the subject at all yet. Please keep us appraised of your progress!

-Cameron McKenzie

[Jeanne Boyarsky]

Chandra,
I suggest asking IBM. Very few people have tried this yet so they are unlikely to run into this exact problem.

[Chandrasekhar Elindram]

Hi Cameron,

Sorry, It is EJB3 feature pack not Service pack. I did installation as per the steps explained in this link http://myjavaworld.wordpress.com/2008/06/06/applying-ejb3-service-pack-on-websphere-61/. Here they call it service pack, however, as per IBM site it is Feature pack only. I tried on both 6.1.0.17 and 6.1.0.15 and found no luck :-(
I'm using windows XP operating system.

I'm trying to get help from IBM, soon will update you all on that.

[Chandrasekhar Elindram]

I took really long to reply for this post....
Nevertheless, we are successful in resolving the deployment issue with the help of IBM support
Though, they took nearly a month to identify the issue, finally they come up saying that there was EJB spec violations in the code which resulted in deployment failure. One of our application modules with MDBs had few jndi lookups performed in its constructor, as per the spec we cannot do this in a constructor. Because of this violation application didn't get deployed on WAS 6.1.0.15, however the same works fine on WAS 6.0 and WAS 6.1 with no EJB 3 feature pack. Since its not as per the spec, IBM doesn't guarantee their server behavior in such cases.

After removing jndi lookups from MDB's constructor application got deployed successfully.

Best regards,
Chandra.
[ August 26, 2008: Message edited by: Chandrasekhar Elindram ]