[Design of POJO Server] - Re: Getting the whole cause stack of the deployment exceptio
by scott.stark＠jboss.org
I did update the exception thrown to include the cause and that is now available on the client as this CNFE example shows. There is an extraneous RuntimeException wrapper that I don't know who is adding yet, but at least the cause is there. This is in the JBAS-7177 issue.
| junit.framework.AssertionFailedError: DeploymentStatus.isCompleted: DeploymentStatus(command=START,state=FAILED,message=null,isCompleted=false,isRunning=false,isFailed=true,failure:
| java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** DEPLOYMENTS IN ERROR: Name -> Error
|
| vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml -> org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.test:service=NoSuchBean
|
|
| DEPLOYMENTS IN ERROR:
| Deployment "vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml" is in error due to the following reason(s): java.lang.ClassNotFoundException: org.jboss.test.profileservice.sar.NoSuchBean from BaseClassLoader@ca245c{VFSClassLoaderPolicy@191c1d{name=vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml domain=ClassLoaderDomain@a05c93{name=DefaultDomain parentPolicy=BEFORE parent=java.net.URLClassLoader@52513a} roots=[MemoryContextHandler@8701025[path= context=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u real=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}}
|
| at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:312)
| at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:189)
| at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:232)
| at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:89)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:112)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testSarCNFEDeployment(DeployUnitTestCase.java:235)
| 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 junit.framework.TestCase.runTest(TestCase.java:164)
| at junit.framework.TestCase.runBare(TestCase.java:130)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:120)
| at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
| at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
| Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** DEPLOYMENTS IN ERROR: Name -> Error
|
| vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml -> org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.test:service=NoSuchBean
|
|
| DEPLOYMENTS IN ERROR:
| Deployment "vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml" is in error due to the following reason(s): java.lang.ClassNotFoundException: org.jboss.test.profileservice.sar.NoSuchBean from BaseClassLoader@ca245c{VFSClassLoaderPolicy@191c1d{name=vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml domain=ClassLoaderDomain@a05c93{name=DefaultDomain parentPolicy=BEFORE parent=java.net.URLClassLoader@52513a} roots=[MemoryContextHandler@8701025[path= context=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u real=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}}
|
| at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:310)
| at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:208)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
| at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
| Caused by: java.lang.ClassNotFoundException: org.jboss.test.profileservice.sar.NoSuchBean from BaseClassLoader@ca245c{VFSClassLoaderPolicy@191c1d{name=vfsfile:/Users/svn/JBossAS/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/testCNFE-service.xml domain=ClassLoaderDomain@a05c93{name=DefaultDomain parentPolicy=BEFORE parent=java.net.URLClassLoader@52513a} roots=[MemoryContextHandler@8701025[path= context=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u real=vfsmemory://5c4o12w-hibs2x-fydde3xq-1-fyddvly8-9u]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}}
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1213)
| at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
| at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:344)
| at org.jboss.system.ServiceCreator.installPlainMBean(ServiceCreator.java:211)
| at org.jboss.system.ServiceCreator.install(ServiceCreator.java:130)
| at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:45)
| at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1632)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.install(ServiceController.java:274)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1632)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
| at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
| at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:297)
| at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:208)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
| at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:211)
| at org.jboss.remoting.Client.invoke(Client.java:1724)
| at org.jboss.remoting.Client.invoke(Client.java:629)
| at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:304)
| at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:189)
| at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:232)
| at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:89)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:112)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testSarCNFEDeployment(DeployUnitTestCase.java:235)
| 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 junit.framework.TestCase.runTest(TestCase.java:164)
| at junit.framework.TestCase.runBare(TestCase.java:130)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:120)
| at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
| at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
| )
| at junit.framework.Assert.fail(Assert.java:47)
| at junit.framework.Assert.assertTrue(Assert.java:20)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:116)
| at org.jboss.test.profileservice.test.DeployUnitTestCase.testSarCNFEDeployment(DeployUnitTestCase.java:235)
| ...
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249721#4249721
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249721
16 years, 7 months
[Design of POJO Server] - profile service overview?
by jhalliday
I'm working on making JBossTS integrate more cleanly with JBossAS.
As a first step I'm shifting the configuration from a TS specific style of xml file to a set of beans which can be wired up by MC through deploy/transaction-jboss-beans.xml So far so good.
However, under the old system the properties file could be rewitten remotely - a 'save' exposed by JMX caused the internal values to be serialized out to xml.
What's the equivalent for persisting config updates in the JBossAS world? From what little I know of profile service it sounds like what I need. Does my code need to be written or wired up in a particular way to play nice with profile service, or do I just add a magic annotation in the -beans.xml? Pointers to any documentation on such things would be appreciated.
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249665#4249665
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249665
16 years, 7 months
[Design of JBoss Transaction Services] - Re: beanifying the config
by jhalliday
So next time I casually mention I'm thinking of changing the configuration system, please stop me. Turns out there are (drum roll please...) not less than 120 configuration properties in the codebase. Not counting XTS. Got to love IDEs with refactoring support.
In place of the old config properties (and yes Mark, they are still there for backward compatibility) we now have a set of configuration beans as described previously. In general it's one per module, which the exception of ArjunaCore/arjuna which has four.
Almost all the code now uses the beans rather than accessing the property manager directly. Indeed I'm tempted to ditch the property manager entirely, but first we need to figure out if/how we want to handle persistent configuration changes.
Meanwhile there is just the marathon task of documenting each and every property. Any volunteers? :-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249662#4249662
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249662
16 years, 7 months