Skip to main content

RunnableBase removed from appserv-rt.jar in V2 b42+

2 replies [Last post]
Joined: 2006-07-27

Builds 42 & 43 of glassfish are causing my application client to fail on startup with the following error:

ERROR - Unspecified exception: com/sun/appserv/management/util/misc/RunnableBase$HowToRun
java.lang.NoClassDefFoundError: com/sun/appserv/management/util/misc/RunnableBase$HowToRun
at com.sun.enterprise.server.ApplicationServer.(
at com.sun.enterprise.util.ORBManager.initProperties(
at com.sun.enterprise.util.ORBManager.getORB(
at com.sun.enterprise.naming.SerialInitContextFactory.getInitialContext(
at javax.naming.spi.NamingManager.getInitialContext(
at javax.naming.InitialContext.getDefaultInitCtx(
at javax.naming.InitialContext.init(
at javax.naming.InitialContext.(

I tracked this down to the fact that RunnableBase.class was removed from appserv-rt.jar. The only way to solve the problem was to include appserv-ext.jar in my client classpath.

The wiki pages state that EJB application clients only need appserv-rt.jar at runtime, so this seems like a regression to me. Should this be raised as an issue?


Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2005-10-28


The com.sun.appserv package and its sub-packages belong to appserv-ext.jar. So, I think it is right to have this class in appserv-ext.jar.

The question of what an application client should have in its classpath is up for discussion, but frankly, with standalone clients, you are on your own. You should consider using appclient script in /bin.


Joined: 2006-07-27

Hi Kedar,

I am not saying it is wrong to have the classes in appserv-ext. However, this change invalidates the developer guide in the wiki as the instructions they give are no longer correct.


I looked into creating the appclient.jar using /bin/package-appclient.bat but it creates a 50MB jar file! Seems a little over the top.

I am not sure why you say that I am "on my own" with standalone clients - the instructions are clearly documented in the Developer Guide and as far as I am aware it is not an unusual thing to do! Rich clients even feature in the Glassfish V2 architecture diagram

So, either the Developer Guide needs updating, or the change needs to be reversed. Either way it is quite inconvenient when you have to spend a few hours tracking down what changed from one version of glassfish to the next. On top of that all the application library dependencies need to be changed for things to work again.