[esb-issues] [JBoss JIRA] Closed: (JBESB-2433) Merge JBESB-2331 - JBrules deployment error when deploying to JBossAS

Tom Fennelly (JIRA) jira-events at lists.jboss.org
Fri Feb 20 12:51:54 EST 2009


     [ https://jira.jboss.org/jira/browse/JBESB-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Fennelly closed JBESB-2433.
-------------------------------

    Resolution: Done


JBESB_4_4_GA_FP: 25368

> Merge JBESB-2331 - JBrules deployment error when deploying to JBossAS
> ---------------------------------------------------------------------
>
>                 Key: JBESB-2433
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2433
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Content Based Routing
>            Reporter: Tom Fennelly
>            Assignee: Tom Fennelly
>             Fix For: 4.4 FP1
>
>
> TomF reported this error upon deploying to JBossAS:
> 08:36:18,799 INFO [JmxKernelAbstraction] installing MBean: persistence.units:unitName=org.drools.persistence.jpa with dependencies:
> 08:36:18,801 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=org.drools.persistence.jpa
> 08:36:18,813 WARN [ServiceController] Problem starting service persistence.units:unitName=org.drools.persistence.jpa
> java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.persistence.jpa
> at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:220)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> ...
> 08:36:18,930 INFO [EJB3Deployer] Deployed: file:/opt/jboss/as/4.2.3/jboss-4.2.3.GA/server/default/deploy/jbrules.esb/drools-process-enterprise-5.0.0.M4.jar
> 08:36:18,936 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment
> 08:36:18,937 INFO [JmxKernelAbstraction] installing MBean: persistence.units:unitName=org.drools.task with dependencies:
> 08:36:18,938 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=org.drools.task
> 08:36:18,944 WARN [ServiceController] Problem starting service persistence.units:unitName=org.drools.task
> java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.task
> at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:220)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> I'm also seeing this upon startup but it's not related to drools:
> 08:35:12,111 INFO [InventoryManager] Detected new Server [Resource[id=-4, type=Embedded Tomcat Server, key=jboss-web.deployer, name=danbev-laptop Embedded JBossWeb Server 2.0.1.GA (127.0.0.1), version=2.0.1.GA]] - adding to local inventory...
> 08:35:12,258 WARN [RuntimeDiscoveryExecutor] Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS]
> java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager
> at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107)
> at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72)
> at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44)
> at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246)
> at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218)
> at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136)
> at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97)
> at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list