[
https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2699:
-----------------------------------
business_ruleservice_ruleAgent, business_ruleservice_stateful, business_rules_service and
custom_action run with no problems on as4 and as5.
However, wrt business_service:
JBoss.org AS 4.2.3.GA
Sun JDK 1.5.0_19
Fedora 11
PROBLEM ON 'ant deploy' FROM 'product/install':
...
11:20:14,310 INFO [JmxKernelAbstraction] installing MBean:
persistence.units:unitName=org.drools.task with dependencies:
11:20:14,311 INFO [PersistenceUnitDeployment] Starting persistence unit
persistence.units:unitName=org.drools.task
11:20:14,319 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)
...
11:20:17,645 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:unitName=org.drools.persistence.jpa
State: NOTYETINSTALLED
I Depend On:
jboss.jca:name=jdbc/testDS1,service=DataSourceBinding
ObjectName: persistence.units:unitName=org.drools.task
State: FAILED
Reason: java.lang.RuntimeException: You have not defined a jta-data-source for a JTA
enabled persistence context named: org.drools.task
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: persistence.units:unitName=org.drools.task
State: FAILED
Reason: java.lang.RuntimeException: You have not defined a jta-data-source for a JTA
enabled persistence context named: org.drools.task
ObjectName: jboss.jca:name=jdbc/testDS1,service=DataSourceBinding
State: NOTYETINSTALLED
Depends On Me:
persistence.units:unitName=org.drools.persistence.jpa
...
QUICKSTART STILL RUNS WITHOUT ISSUES.
========================================
JBoss.org AS 5.1.0.GA
Sun JDK 1.5.0_19
Fedora 11
PROBLEM ON 'ant deploy' FROM
'product/samples/quickstarts/business_service':
...
11:38:01,095 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3_endpoint"
is missing the following dependencies:
Dependency
"jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3"
(should be in state "Configured", but is actually in state "** NOT FOUND
Depends on
'jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3'
**")
DEPLOYMENTS IN ERROR:
Deployment
"jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3"
is in error due to the following reason(s): ** NOT FOUND Depends on
'jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3'
**
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
...
QUICKSTART STILL RUNS WITHOUT ISSUES.
In summary, deploying the ESB itself into
JBoss.org AS 4.2.3.GA has a problem although the
quickstart itself still runs, whereas deploying the ESB into
JBoss.org AS 5.1.0.GA has no
problems, but deploying the quickstart itself has a problem, but again the quickstart
itself still runs.
Verify quickstarts business_ruleservice_ruleAgent ->
custom_action
------------------------------------------------------------------
Key: JBESB-2699
URL:
https://jira.jboss.org/jira/browse/JBESB-2699
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.5
Reporter: Kevin Conner
Assignee: David Ward
Fix For: 4.6
business_ruleservice_ruleAgent
business_ruleservice_stateful
business_rules_service
business_service
custom_action
--
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