[Design of POJO Server] - Cause overwrite problem
by scott.stark＠jboss.org
With the current trunk I'm not able to startup the default config due to issues like the following:
| 2007-07-16 22:50:12,265 ERROR [org.jboss.ejb3.deployers.EJBRegistrationDeployer] Error during deploy: vfsfile:/C:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/profileservice/deployers/jboss-aop-jboss5.deployer/jboss-standalone-aspect-library-jdk50.jar
| org.jboss.deployers.spi.DeploymentException: java.lang.IllegalStateException: Can't overwrite cause
| at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:172)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.deploy(AbstractVFSRealDeployer.java:45)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:164)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:661)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:624)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:588)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:304)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1257)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:685)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:813)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:735)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:573)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:374)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:427)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:340)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:372)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:247)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:523)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.IllegalStateException: Can't overwrite cause
| at java.lang.Throwable.initCause(Throwable.java:320)
| at org.jboss.security.jacc.JBossPolicyConfigurationFactory.<init>(JBossPolicyConfigurationFactory.java:64)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
| at java.lang.Class.newInstance0(Class.java:350)
| at java.lang.Class.newInstance(Class.java:303)
| at org.jboss.ejb3.security.Ejb3PolicyConfigurationFactory.getPolicyConfigurationFactory(Ejb3PolicyConfigurationFactory.java:87)
| at org.jboss.ejb3.security.JaccHelper.initialiseJacc(JaccHelper.java:72)
| at org.jboss.ejb3.deployers.Ejb3JBoss5Deployment.createPolicyConfiguration(Ejb3JBoss5Deployment.java:74)
| at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:346)
| at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:160)
| ... 22 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064828#4064828
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064828
18 years, 8 months
[Design of JBossCache] - Re: Consolidate delegating cache loader classes [JBCACHE-113
by galder.zamarreno＠jboss.com
I wanted to note one thing that I forgot in my initial explanation. The reason that lead me to look at all this was the fact that I need any SingletonStoreCacheLoader implementations to extend AbstractDelegatingCacheLoader. I would rather customer having to implement an interface rather than extend a class as it gives them more flexibility. They can always extend AbstractDelegatingCacheLoader and gain from the benefits of overriding just the methods they want, but if alternatively they can implement an interface with getCL/setCL (a name that implies a CL that delegates to another CL, with the possibility of getting/setting the underlying CL), much better :)
I totally agree with the naming being confusing, hence my attempt to make a separation between cache/CL delegating CLs.
I think TcpDelegatingCacheLoader is a bit different to the rest of cache delegating caches.
The rest, LDCL, CCL, and the possible outcome of http://jira.jboss.com/jira/browse/JBCACHE-789, do pretty much the same, delegate cache loading to other caches. First one to a local cache, second to another cache via MethodCalls (using the caches RPC manager) and the third one via proxies. All three just mentioned could just extend AbstractCacheLoader as you said and override what needs overriding.
I like this idea (which is what u're saying in your 1st paragraph) more than having CCL extend DCL.
anonymous wrote : AbstractDelegatingCacheLoader (which delegates to other cache loaders) - makes more sense in it's implementation
Of course it does!!, i created it myself! hehehehe :-p ;-). This is the cache loader that I want getCL/setCL factored out into an interface to make people who re implement SSCL easier as mentioned earlier.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064781#4064781
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064781
18 years, 8 months
[QA of JBoss Portal] - Re: SSO Unit Testing
by sohil.shah＠jboss.com
FYI-
The previous post details the setup/test framework environment needed by the SSO test cases.
The SSO test cases themselves need to simulate a browser based user that
1/ Navigates to one instance of the portal (call it Portal 1)
2/ Logs in to the Portal
3/ Supports any SSO orchestration at the browser level that is needed for the SSO Framework in question
4/ Establishes the SSO session on Portal 1
5/ Navigates to a second instance of the portal (call this Portal 2)
6/ And asserts that on Portal 2, authentication is not required and the Subject from Portal 1 is automatically authenticated.
These test cases run at the browser level and should use the http client library to access the Portal
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064739#4064739
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064739
18 years, 8 months
[Design of JBossCache] - Re: Consolidate delegating cache loader classes [JBCACHE-113
by manik.surtani＠jboss.com
If you look at the DelegatingCacheLoader, it doesn't really do anything at all except proxy calls to abstract methods that need implementing - e.g., put() -> delegatePut(), get() -> delegateGet(), etc etc. Why not just have the implementation (E.g., TcpDelegatingCacheLoader) just implement CacheLoader directly rather than extend DelegatingCacheLoader (the way CCL does)? You have to implement the same number of methods anyway.
The only thing DCL adds is tracking transactions in a map. This is also done in AbstractCacheLoader, which DCL ought to extend.
Now if DCL provided no-op impls of the delegateXYZ() methods, then this makes sense since the implementation class could only override calls it would like to delegate.
In this case I see a benefit for CCL extending DCL.
AbstractDelegatingCacheLoader (which delegates to other cache loaders) - makes more sense in it's implementation, although I don't quite see much to be consolidated between ADCL and DCL.
What does need refactoring though is the names! AbstractDelegatingCacheLoader (delegates to cache loaders) and DelegatingCacheLoader (delegates to caches)? Hugely confusing. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064737#4064737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064737
18 years, 8 months
[Design of JBoss Profiler] - JBOSS 3.2.7 supports jboss-profiler-noAOP.sar?????
by juanillo
Hi all there
I'm trying to profile a JBOSS over windows XP and after follow the install porcess it seems everything is OK.
but when I try to deploy the jboss-profiler-noAOP.sar Jboss raises this error:
==============================
2007-07-16 18:18:12,062 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/JBOSS3.2.7/server/default/deploy/jboss-profiler-noAOP.sar
org.jboss.deployment.DeploymentException: Unknown xmbean type null; - nested throwable: (javax.management.NotCompliantMBeanException: Unknown xmbean type null)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:142)
at org.jboss.system.ServiceController.install(ServiceController.java:199)
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.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
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.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
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.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:415)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
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.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:191)
at org.jboss.Main$1.run(Main.java:480)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.management.NotCompliantMBeanException: Unknown xmbean type null
at org.jboss.mx.metadata.XMLMetaData.build(XMLMetaData.java:284)
at org.jboss.mx.modelmbean.XMBean.(XMBean.java:220)
at org.jboss.mx.modelmbean.XMBean.(XMBean.java:249)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:871)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:290)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:317)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:179)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:152)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:117)
... 81 more
=========================
Maybe the bproblems is that this version of JBoos doesn't support the jboss-profiler-noAOP.sar....
Any idea???
Thanks mates
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064642#4064642
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064642
18 years, 8 months