java.lang.NoClassDefFoundError: Lorg/apache/commons/logging/Log; The EAR file contained the commons-logging jar in the root. This is what the Glassfish log contains: Jun 29, 2010 9:37:17 PM com.sun.enterprise.glassfish.bootstrap.ASMain main INFO: Launching GlassFish on Felix platform Welcome to Felix ================ INFO: Perform lazy SSL initialization for the listener 'http-listener-2' INFO: Starting Grizzly Framework 1.9.18-o - Tue Jun 29 21:37:22 CEST 2010 INFO: Starting Grizzly Framework 1.9.18-o - Tue Jun 29 21:37:22 CEST 2010 INFO: Grizzly Framework 1.9.18-o started in: 68ms listening on port 8181 INFO: Grizzly Framework 1.9.18-o started in: 60ms listening on port 4848 INFO: Grizzly Framework 1.9.18-o started in: 18ms listening on port 7676 INFO: Grizzly Framework 1.9.18-o started in: 115ms listening on port 8080 INFO: Grizzly Framework 1.9.18-o started in: 42ms listening on port 3700 INFO: The Admin Console is already installed, but not yet loaded. INFO: GlassFish Server Open Source Edition 3.0.1 (22) startup time : Felix(4079ms) startup services(1277ms) total(5356ms) INFO: Hibernate Validator bean-validator-3.0-JBoss-4.0.2 INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver. INFO: Binding RMI port to *:8686 INFO: Grizzly Framework 1.9.18-o started in: 23ms listening on port 8080 INFO: JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://192.168.0.100:8686/jndi/rmi://192.168.0.100:8686/jmxrmi SEVERE: Class [ Lorg/apache/commons/logging/Log; ] not found. Error while loading [ class nl.kabisa.rsstank.ejb.ImportBean ] WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: Lorg/apache/commons/logging/Log; SEVERE: Exception while deploying the app java.lang.IllegalArgumentException: Invalid ejb jar [rsstank-ejb-2.0.0-SNAPSHOT.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. 3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by marceloverdijk, 1 year ago
Framework 1.9.18-o started in: 115ms listening on port 8080 INFO: Grizzly Framework 1.9.18-o started in: 42ms listening on port 3700 INFO: The Admin Console is already installed, but not yet loaded. INFO: GlassFish Server Open Source Edition 3.0.1 (22
via Oracle Community by glassfisher, 1 year ago
: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. 3. If the jar file contains valid EJBs which are annotated with EJB
java.lang.NoClassDefFoundError: Lorg/apache/commons/logging/Log; The EAR file contained the commons-logging jar in the root. This is what the Glassfish log contains: Jun 29, 2010 9:37:17 PM com.sun.enterprise.glassfish.bootstrap.ASMain main INFO: Launching GlassFish on Felix platform Welcome to Felix ================ INFO: Perform lazy SSL initialization for the listener 'http-listener-2' INFO: Starting Grizzly Framework 1.9.18-o - Tue Jun 29 21:37:22 CEST 2010 INFO: Starting Grizzly Framework 1.9.18-o - Tue Jun 29 21:37:22 CEST 2010 INFO: Grizzly Framework 1.9.18-o started in: 68ms listening on port 8181 INFO: Grizzly Framework 1.9.18-o started in: 60ms listening on port 4848 INFO: Grizzly Framework 1.9.18-o started in: 18ms listening on port 7676 INFO: Grizzly Framework 1.9.18-o started in: 115ms listening on port 8080 INFO: Grizzly Framework 1.9.18-o started in: 42ms listening on port 3700 INFO: The Admin Console is already installed, but not yet loaded. INFO: GlassFish Server Open Source Edition 3.0.1 (22) startup time : Felix(4079ms) startup services(1277ms) total(5356ms) INFO: Hibernate Validator bean-validator-3.0-JBoss-4.0.2 INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver. INFO: Binding RMI port to *:8686 INFO: Grizzly Framework 1.9.18-o started in: 23ms listening on port 8080 INFO: JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://192.168.0.100:8686/jndi/rmi://192.168.0.100:8686/jmxrmi SEVERE: Class [ Lorg/apache/commons/logging/Log; ] not found. Error while loading [ class nl.kabisa.rsstank.ejb.ImportBean ] WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: Lorg/apache/commons/logging/Log; SEVERE: Exception while deploying the app java.lang.IllegalArgumentException: Invalid ejb jar [rsstank-ejb-2.0.0-SNAPSHOT.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. 3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:72)
at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:124)
at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:722)
at com.sun.enterprise.deployment.Application.visit(Application.java:1744)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:774)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openWith(ApplicationArchivist.java:253)
at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:152)
at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:612)
at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:554)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:262)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
at java.lang.Thread.run(Thread.java:637)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.