• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

AbstractMethodError on websphere 5.0.2.3

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
I have an EAR which runs successfully on WSAD 5.1. However when I deploy the same EAR on WAS 5.0.2.3, I get an AbstractMethodError exception as follows inside a session bean where I am calling getSessionContext().getRollbackOnly().
[4/19/04 20:45:57:194 GMT] 54c72c SystemErr R java.lang.AbstractMethodError
[4/19/04 20:45:57:195 GMT] 54c72c SystemErr R at com.ibm.ejs.container.EJSContainer.getCurrentTx(EJSContainer.java:1
633)
[4/19/04 20:45:57:195 GMT] 54c72c SystemErr R at com.ibm.ejs.container.CMStatelessBeanO.getRollbackOnly(CMStatelessB
eanO.java:98)
Any pointers as to why this occurs would be very helpful.
Thanks.
 
author
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Try re-generating the deployed code. You can do this during the deploy process by selecting deploy EJB.
The deploy code generator in 5.1 probably changed.
 
Subashini Ramakrishnan
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I did that. I deleted all the old deployed code and the class files and generated deploy code afresh. The problem still persists.
 
Roland Barcia
author
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You re-generated the code using the EJBdeploy.bat of the 5.0.2.3 server?
 
Subashini Ramakrishnan
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
No. I am building the EAR on WSAD. I am re-generating deploy code by right clicking on the EJB project and going to Generate --> Deployment and RMIC Code.
 
Roland Barcia
author
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are you deploying to a WebSphere instance server somewhere or are you testing with 2 different test servers within WSAD?
 
Subashini Ramakrishnan
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am testing on a separate WAS instance on a unix box.
 
Roland Barcia
author
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When you install the EAR, explicitly select deploy EJB button in the install wizard. This will generate the deploy code using the EJBDeploy.Bat of the server.
 
Subashini Ramakrishnan
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Roland,
I did that while deploying the EAR and tried. It still gives the same AbstractMethodError exception :-(
 
Subashini Ramakrishnan
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is it something to do with the JDBC driver ? We are using DB2 Legacy CLI-based Type 2 JDBC Driver(XA) and COM.ibm.db2.jdbc.DB2XADataSource as the implementation class.
Any pointers ?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic