[JBoss JIRA] (AS7-3016) Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
by Jiri Pechanec (Created) (JIRA)
Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Jonathan Halliday
Priority: Critical
This test case was identified in TCK6. There is a MDB with CMT configured - com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (AS7-1268) Can't update subhandler on async handler
by Stan Silvert (JIRA)
Can't update subhandler on async handler
----------------------------------------
Key: AS7-1268
URL: https://issues.jboss.org/browse/AS7-1268
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: David Lloyd
David, sorry if I'm assigning to the wrong person. I guess this could be a CLI bug.
[standalone@localhost:9999 /] cd subsystem=logging/async-handler=ASYNC
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
[standalone@localhost:9999 async-handler=ASYNC] :update-properties(subhandlers=["CONSOLE"])
{"outcome" => "success"}
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBRULES-3496) kbase.removeKnowledgePackage() aparent infinite loop
by Mariano De Maio (JIRA)
Mariano De Maio created JBRULES-3496:
----------------------------------------
Summary: kbase.removeKnowledgePackage() aparent infinite loop
Key: JBRULES-3496
URL: https://issues.jboss.org/browse/JBRULES-3496
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.4.0.CR1
Environment: Unix based (Ubuntu 10) Core i5 with 4GB RAM
Reporter: Mariano De Maio
Assignee: Mark Proctor
Attachments: Proj.tar.gz
I have attached a simple project containing just 1 rule and some declared classes.
The rule is compiled ok, but when after adding the generated package to a kbase, when trying to remove it, an infinite-loop (or what it seems like an infinite-loop) occurs.
If you remove some of the patterns in the rule, everything works fine.
I have debugged up to ReteooBuilder.resetMarks(). The execution never returns from that method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-5168) IllegalArgumentException when using tab-completion with a wildcard in the path
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-5168:
--------------------------------
Summary: IllegalArgumentException when using tab-completion with a wildcard in the path
Key: AS7-5168
URL: https://issues.jboss.org/browse/AS7-5168
Project: Application Server 7
Issue Type: Bug
Components: Console
Environment: AS7 master branch
Reporter: Jeff Mesnil
Assignee: Heiko Braun
I wanted to get all the values of jms-queues' attribute core-address from the CLI and it works as expected:
{noformat}
[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=*:read-attribute(name="queue-address")
{
"outcome" => "success",
"result" => [
{
"address" => [
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("jms-queue" => "myQueue")
],
"outcome" => "success",
"result" => "jms.queue.myQueue"
},
{
"address" => [
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("jms-queue" => "HELLOWORLDMDBQueue2")
],
"outcome" => "success",
"result" => "jms.queue.HELLOWORLDMDBQueue2"
}
]
}
{noformat}
However when I tried to tab-complete the name of the attribute, I got an IllegalArgumentException and the console exited.
{noformat}
[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=*:read-attribute(name=java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.getChild(ModelValue.java:108)
at org.jboss.dmr.ModelNode.get(ModelNode.java:798)
at org.jboss.as.cli.operation.impl.PropertyNameCompleter$1.getAllCandidates(PropertyNameCompleter.java:62)
at org.jboss.as.cli.impl.DefaultCompleter.complete(DefaultCompleter.java:64)
at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:222)
at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:93)
at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:96)
at org.jboss.jreadline.console.Console.complete(Console.java:809)
at org.jboss.jreadline.console.Console.read(Console.java:383)
at org.jboss.jreadline.console.Console.read(Console.java:221)
at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:166)
at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1140)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:270)
at org.jboss.modules.Main.main(Main.java:294)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-5375) jboss-cli undeploy -l output does not show details
by Cheng Fang (JIRA)
Cheng Fang created AS7-5375:
-------------------------------
Summary: jboss-cli undeploy -l output does not show details
Key: AS7-5375
URL: https://issues.jboss.org/browse/AS7-5375
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.2.0.Alpha1
Reporter: Cheng Fang
Assignee: Alexey Loubyansky
The help for undeploy says:
in case the deployment name isn't specified, the presence of the -l switch
will make the existing deployments printed one deployment per line, instead of
in columns (the default).
but its output just displays in short format:
$JBOSS_HOME/bin/jboss-cli.sh --connect --command="undeploy -l"
hello.war
This is not consistent with deploy -l, which does show the details one deployment per line.
$JBOSS_HOME/bin/jboss-cli.sh --connect --command="deploy -l"
NAME RUNTIME-NAME ENABLED STATUS
hello.war hello.war true OK
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-5420) Intermittent Testsuite: CMP Commerce Tests
by Eduardo Martins (JIRA)
Eduardo Martins created AS7-5420:
------------------------------------
Summary: Intermittent Testsuite: CMP Commerce Tests
Key: AS7-5420
URL: https://issues.jboss.org/browse/AS7-5420
Project: Application Server 7
Issue Type: Feature Request
Components: Test Suite
Affects Versions: 7.1.2.Final (EAP)
Reporter: Eduardo Martins
Assignee: Eduardo Martins
{code}
More CMP tests which fail sometimes, again this is due to an H2 behavior where dropping a table (done by a CMP module processor on undeploy) may be incomplete when a new deploy starts, and needs same tables.
In concrete, the deploy code will not find the table(s) on the DB metadata, tries to create and this fails.
Test:
org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderByQueryTestCase.org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderByQueryTestCase
Error Message:
Cannot deploy: cmp-commerce.jar
Stacktrace:
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: cmp-commerce.jar
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.jboss.as.test.integration.ejb.entity.cmp.CmpTestRunner.run(CmpTestRunner.java:71)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
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:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: java.lang.Exception: {
"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.START: JBAS010785: Failed start store manager
Caused by: java.lang.RuntimeException: JBAS010765: Error while creating table: CUSTOMER_ADDRESS
Caused by: org.h2.jdbc.JdbcSQLException: Table \"CUSTOMER_ADDRESS\" already exists; SQL statement:
CREATE TABLE CUSTOMER_ADDRESS (CUSTOMER BIGINT NOT NULL, ADDRESS BIGINT NOT NULL, CONSTRAINT PK_CUSTOMER_ADDRESS PRIMARY KEY (CUSTOMER, ADDRESS)) [42101-168]"},
"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.OrderEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.LineItemEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryBatchDeleteEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.UserEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeBatchDeleteEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryBatchDeleteEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".jdbc.store-manager.fk-barrier Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.UserEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.AddressEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.OrderEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.LineItemEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.AddressEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductEJB.START Missing[JBAS014861: <one or more transitive dependencies>]",
"jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeBatchDeleteEJB.START Missing[JBAS014861: <one or more transitive dependencies>]"
]
}
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:52)
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
... 89 more
Standard Output
[0m16:08:50,245 INFO [TableCleaner] (MSC service thread 1-5) NUKING!
[0m[0m16:08:50,247 INFO [TableCleaner] (MSC service thread 1-5) NUKE SUCCESS!
[0m[0m16:08:50,251 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment cmp-commerce.jar in 34ms
[0m[0m16:08:50,262 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/basic/target/jbossas/standalone/data/content/a0/a4448ba0597eeeaa09d5531bf5ced59cd03c30/content
[0m[0m16:08:50,262 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "cmp-commerce.jar"
[0m[0m16:08:50,675 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/basic/target/jbossas/standalone/data/content/6c/af1de7c5c33fd03ec78939a852af00ad256e2e/content
[0m[0m16:08:50,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "cmp-commerce.jar"
[0m[0m16:08:50,731 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named LineItemEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItemHome
java:app/cmp-commerce/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItemHome
java:module/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItemHome
java:global/cmp-commerce/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItem
java:app/cmp-commerce/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItem
java:module/LineItemEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.LineItem
[0m[0m16:08:50,732 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named TransactionWrappingSessionBean in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/TransactionWrappingSessionBean!org.jboss.as.test.integration.ejb.entity.cmp.TransactionWrappingSessionBean
java:app/cmp-commerce/TransactionWrappingSessionBean!org.jboss.as.test.integration.ejb.entity.cmp.TransactionWrappingSessionBean
java:module/TransactionWrappingSessionBean!org.jboss.as.test.integration.ejb.entity.cmp.TransactionWrappingSessionBean
java:global/cmp-commerce/TransactionWrappingSessionBean
java:app/cmp-commerce/TransactionWrappingSessionBean
java:module/TransactionWrappingSessionBean
[0m[0m16:08:50,733 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named TxTesterBean in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/TxTesterBean!org.jboss.as.test.integration.ejb.entity.cmp.commerce.TxTester
java:app/cmp-commerce/TxTesterBean!org.jboss.as.test.integration.ejb.entity.cmp.commerce.TxTester
java:module/TxTesterBean!org.jboss.as.test.integration.ejb.entity.cmp.commerce.TxTester
java:global/cmp-commerce/TxTesterBean
java:app/cmp-commerce/TxTesterBean
java:module/TxTesterBean
[0m[0m16:08:50,734 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named CustomerEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Customer
java:app/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Customer
java:module/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Customer
java:jboss/exported/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Customer
java:global/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocal
java:app/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocal
java:module/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocal
java:global/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerHome
java:app/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerHome
java:module/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerHome
java:jboss/exported/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerHome
java:global/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocalHome
java:app/cmp-commerce/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocalHome
java:module/CustomerEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.CustomerLocalHome
[0m[0m16:08:50,736 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named AddressEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.AddressHome
java:app/cmp-commerce/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.AddressHome
java:module/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.AddressHome
java:global/cmp-commerce/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Address
java:app/cmp-commerce/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Address
java:module/AddressEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Address
[0m[0m16:08:50,736 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ProductCategoryTypeEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
java:app/cmp-commerce/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
java:module/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
java:global/cmp-commerce/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
java:app/cmp-commerce/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
java:module/ProductCategoryTypeEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
[0m[0m16:08:50,737 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ProductCategoryBatchDeleteEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:app/cmp-commerce/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:module/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:global/cmp-commerce/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
java:app/cmp-commerce/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
java:module/ProductCategoryBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
[0m[0m16:08:50,738 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ProductCategoryEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:app/cmp-commerce/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:module/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategory
java:global/cmp-commerce/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
java:app/cmp-commerce/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
java:module/ProductCategoryEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryHome
[0m[0m16:08:50,739 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ProductCategoryTypeBatchDeleteEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
java:app/cmp-commerce/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
java:module/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryType
java:global/cmp-commerce/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
java:app/cmp-commerce/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
java:module/ProductCategoryTypeBatchDeleteEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductCategoryTypeHome
[0m[0m16:08:50,740 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named UserEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocalHome
java:app/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocalHome
java:module/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocalHome
java:global/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserHome
java:app/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserHome
java:module/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserHome
java:jboss/exported/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserHome
java:global/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocal
java:app/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocal
java:module/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocal
java:global/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.User
java:app/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.User
java:module/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.User
java:jboss/exported/cmp-commerce/UserEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.User
[0m[0m16:08:50,742 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named OrderEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Order
java:app/cmp-commerce/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Order
java:module/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Order
java:global/cmp-commerce/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderHome
java:app/cmp-commerce/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderHome
java:module/OrderEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderHome
[0m[0m16:08:50,743 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ProductEJB in deployment unit deployment "cmp-commerce.jar" are as follows:
java:global/cmp-commerce/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Product
java:app/cmp-commerce/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Product
java:module/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.Product
java:global/cmp-commerce/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductHome
java:app/cmp-commerce/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductHome
java:module/ProductEJB!org.jboss.as.test.integration.ejb.entity.cmp.commerce.ProductHome
[0m[0m16:08:50,769 INFO [TableCleaner] (MSC service thread 1-5) Activating cleaner for deployment: cmp-commerce.jar
[0m[0m16:08:50,888 INFO [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."cmp-commerce.jar",unit=cmp-commerce.jar,tests=[org.jboss.as.test.integration.ejb.entity.cmp.commerce.OneToManyBiTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.OrderByQueryTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.TxTesterTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.CommerceCascadeDeleteTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.LazyResultSetLoadingTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.ManyToOneUniTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.UserLocalTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.ManyToManyBiTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.CommerceTestCase, org.jboss.as.test.integration.ejb.entity.cmp.commerce.OneToOneUnitTestCase]]
[0m[0m16:08:50,916 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.0.0.CR15
[0m[31m16:08:50,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."cmp-commerce.jar".component.CustomerEJB.jdbc.store-manager.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."cmp-commerce.jar".component.CustomerEJB.jdbc.store-manager.START: JBAS010785: Failed start store manager
at org.jboss.as.cmp.jdbc.JdbcStoreManagerStartService.start(JdbcStoreManagerStartService.java:46)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
Caused by: java.lang.RuntimeException: JBAS010765: Error while creating table: CUSTOMER_ADDRESS
at org.jboss.as.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.java:447)
at org.jboss.as.cmp.jdbc.JDBCStartCommand.execute(JDBCStartCommand.java:262)
at org.jboss.as.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:234)
at org.jboss.as.cmp.jdbc.JdbcStoreManagerStartService.start(JdbcStoreManagerStartService.java:44)
... 5 more
Caused by: org.h2.jdbc.JdbcSQLException: Table "CUSTOMER_ADDRESS" already exists; SQL statement:
CREATE TABLE CUSTOMER_ADDRESS (CUSTOMER BIGINT NOT NULL, ADDRESS BIGINT NOT NULL, CONSTRAINT PK_CUSTOMER_ADDRESS PRIMARY KEY (CUSTOMER, ADDRESS)) [42101-168]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
at org.h2.message.DbException.get(DbException.java:169)
at org.h2.message.DbException.get(DbException.java:146)
at org.h2.command.ddl.CreateTable.update(CreateTable.java:108)
at org.h2.command.CommandContainer.update(CommandContainer.java:75)
at org.h2.command.Command.executeUpdate(Command.java:230)
at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:125)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:110)
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:375)
at org.jboss.as.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.java:439)
... 8 more
[0m[0m16:08:51,198 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS015870: Deploy of deployment "cmp-commerce.jar" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.START: JBAS010785: Failed start store manager
Caused by: java.lang.RuntimeException: JBAS010765: Error while creating table: CUSTOMER_ADDRESS
Caused by: org.h2.jdbc.JdbcSQLException: Table \"CUSTOMER_ADDRESS\" already exists; SQL statement:
CREATE TABLE CUSTOMER_ADDRESS (CUSTOMER BIGINT NOT NULL, ADDRESS BIGINT NOT NULL, CONSTRAINT PK_CUSTOMER_ADDRESS PRIMARY KEY (CUSTOMER, ADDRESS)) [42101-168]"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.OrderEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.CustomerEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.LineItemEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryBatchDeleteEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.UserEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeBatchDeleteEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryBatchDeleteEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".jdbc.store-manager.fk-barrier Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.UserEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.AddressEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.OrderEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.LineItemEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.AddressEJB.jdbc.store-manager.FOREIGN_KEYS Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"cmp-commerce.jar\".component.ProductCategoryTypeBatchDeleteEJB.START Missing[JBAS014861: <one or more transitive dependencies>]"]}
[0m[0m16:08:51,284 INFO [TableCleaner] (MSC service thread 1-5) NUKING!
[0m[0m16:08:51,289 INFO [TableCleaner] (MSC service thread 1-5) NUKE SUCCESS!
[0m[0m16:08:51,303 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment cmp-commerce.jar in 133ms
[0m
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-4274) Remoting deadlock after deserialization exception of a large object graph returned from EJB.
by Daniel Bevenius (JIRA)
Daniel Bevenius created AS7-4274:
------------------------------------
Summary: Remoting deadlock after deserialization exception of a large object graph returned from EJB.
Key: AS7-4274
URL: https://issues.jboss.org/browse/AS7-4274
Project: Application Server 7
Issue Type: Bug
Components: EJB, Remoting
Affects Versions: 7.1.1.Final
Environment: JBoss AS 7.1.1.Final
Reporter: Daniel Bevenius
Assignee: jaikiran pai
The use case is a remote EJB client that calls an EJB which returns a large object graph. Due to a configuration error on our part a class that is part of this object graph is not available in the clients classpath. This causes a ClassNotFoundException to be thrown when deserializing, and after this exception is thrown the client "freezes" but can be interrupted by CTRL+C, but the server will deadlock and will not respond and has to be shutdown by killing the server process.
Below is part of the thread dump (the complete thread dump will be attached to this jira)
{noformat}
"Remoting "beve-7719" read-1" prio=5 tid=00000000028cc800 nid=0xb56ab000 waiting for monitor entry [00000000b56aa000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:156)
- waiting to lock <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.xnio.IoUtils.safeClose(IoUtils.java:137)
at org.jboss.remoting3.remote.OutboundMessage.closeAsync(OutboundMessage.java:158)
at org.jboss.remoting3.remote.RemoteConnectionChannel.handleAsyncClose(RemoteConnectionChannel.java:502)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:259)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
Locked ownable synchronizers:
- None
"EJB default - 4" prio=5 tid=0000000002a10c00 nid=0xb3971000 in Object.wait() [00000000b3970000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at java.lang.Object.wait(Object.java:485)
at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:91)
- locked <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:125)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:113)
at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:77)
at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:86)
- locked <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:168)
at java.io.DataOutputStream.write(DataOutputStream.java:71)
- locked <00000000056972b8> (a java.io.DataOutputStream)
at org.jboss.as.ejb3.remote.protocol.versionone.AbstractMessageHandler$1.write(AbstractMessageHandler.java:188)
at java.io.OutputStream.write(OutputStream.java:99)
at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
at org.jboss.marshalling.SimpleDataOutput.flush(SimpleDataOutput.java:311)
at org.jboss.marshalling.SimpleDataOutput.write(SimpleDataOutput.java:82)
at org.jboss.marshalling.river.BlockMarshaller.flush(BlockMarshaller.java:306)
at org.jboss.marshalling.river.RiverMarshaller.writeEndBlock(RiverMarshaller.java:961)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1008)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:825)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:338)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:226)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Locked ownable synchronizers:
- <0000000008350f48> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months