Bug 822161
| Summary: | jbpm-console cannot initialize session because of java.lang.NoClassDefFoundError: org/jboss/netty/channel/socket/ClientSocketChannelFactory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | jBPM Console | Assignee: | Ryan Zhang <rzhang> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | CC: | jcoleman, tcunning | ||||
| Target Milestone: | ER8 | ||||||
| Target Release: | BRMS 5.3.0.GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-02-10 03:19:52 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jiri Locker
2012-05-16 14:07:40 UTC
After trying to start a task, I'm seeing this in business-central (SOA-P 5.3 ER2 / BRMS ER7 deployable) :
Does business-central need it as well?
java.lang.ClassNotFoundException: org.jboss.netty.channel.socket.ClientSocketChannelFactory from BaseClassLoader@5b784b{vfsfile:/home/tcunning/Downloads/soa-p/530er2/jboss-soa-p-5/jboss-as/server/default/deploy/gwt-console-server.war/}
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:477)
java.lang.ClassLoader.loadClass(ClassLoader.java:247)
org.hornetq.core.remoting.impl.netty.NettyConnectorFactory.createConnector(NettyConnectorFactory.java:40)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:1117)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:992)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:223)
org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:673)
org.jbpm.task.service.hornetq.HornetQTaskClientConnector.connect(HornetQTaskClientConnector.java:94)
org.jbpm.task.service.hornetq.HornetQTaskClientConnector.connect(HornetQTaskClientConnector.java:74)
org.jbpm.task.service.TaskClient.connect(TaskClient.java:769)
org.jbpm.integration.console.TaskClientFactory.newAsyncInstance(TaskClientFactory.java:104)
org.jbpm.integration.console.StatefulKnowledgeSessionUtil.registerWorkItemHandler(StatefulKnowledgeSessionUtil.java:329)
org.jbpm.integration.console.StatefulKnowledgeSessionUtil.initializeStatefulKnowledgeSession(StatefulKnowledgeSessionUtil.java:158)
org.jbpm.integration.console.StatefulKnowledgeSessionUtil$SessionHolder.<clinit>(StatefulKnowledgeSessionUtil.java:127)
org.jbpm.integration.console.StatefulKnowledgeSessionUtil.getStatefulKnowledgeSession(StatefulKnowledgeSessionUtil.java:131)
org.jbpm.integration.console.SessionInitializer.<init>(SessionInitializer.java:25)
org.jbpm.integration.console.TaskManagement.<init>(TaskManagement.java:49)
org.jbpm.integration.console.ManagementFactory.createTaskManagement(ManagementFactory.java:26)
org.jbpm.integration.console.ManagementFactory.createTaskManagement(ManagementFactory.java:19)
org.jboss.bpm.console.server.TaskListFacade.getTaskManagement(TaskListFacade.java:72)
org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:101)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
The idea was to remove netty by default and rely on the version that is provided by the application server: "Let's make it work with what's provided in the container. (Note that this may break Tomcat, but we'll handle that the standard way - by documenting it.)" What container are you deploying this on? SOA-P 5.3, with mina as human-task-server client. In EAP/SOA-P, netty.jar is only provided in the client directory. So, we need to decide if we want to add netty.jar to the two war deployments in the BRMS-P deployable, or to document this step too. Assigning to Ryan, as this seems to be an issue that needs to be tackled in the build (or documentation if decided this is the best option). For SOA-P and EAP installations, this will only be supported when HornetQ is already installed. Then, netty.jar will be present in the server common/lib/ directory. Please verify them on ER8. VERIFIED fixed in ER8. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |