My Oracle Support Banner

Standalone EJB Module That Deploys and Works on GF 2.x Does Not Work on GF 3.x (Doc ID 1389719.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version: 3.1 and later   [Release: 3.1 and later ]
Information in this document applies to any platform.


  A Standalone EJB module with contents that looks like as shown below fails to work in GF3.x.
  • ejb/Bean.class
  • utility.jar
This standalone EJB module that deploys and works on GlassFish Server 2.x fails to work when deployed on GlassFish 3.x.  From the server.log, some of the bundled classes in utility.jar are not found causing NoClassDefFoundError or ClassNotFound exceptions to be thrown on the GlassFish's server.log during deployment. 

The example of some of these errors may appear like this :
[#|2011-12-28T14:03:33.627+0800|WARNING|glassfish3.1.2|global|_ThreadID=22;_ThreadName=Thread-2;|Error in annotation processing: java.lang.NoClassDefFoundError: utility/BeanRemote|#]

[#|2011-12-28T14:03:33.631+0800|WARNING|glassfish3.1.2|global|_ThreadID=22;_ThreadName=Thread-2;|Error in annotation processing: java.lang.NoClassDefFoundError: utility/BeanRemote|#]

[#|2011-12-28T14:03:33.755+0800|INFO|glassfish3.1.2||_ThreadID=22;_ThreadName=Thread-2;|EJB5181:Portable JNDI names for EJB SubBean: [java:global/standaloneejb/Bean!ejb.Bean, java:global/standaloneejb/Bean]|#]


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.