January 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - DeployerInterceptorEJB3 depends on jboss.ejb3:service=EJB3De

by dimitris＠jboss.org

The latest refactoring on Branch_4_2 that replaced jbossws14.sar with jbossws.sar expects the EJB3Deployer to be present. EJB3 is still an optional component in JBossAS, so although we now require jdk5, we may not have EJB3 present. We need to include a jboss-service.xml descriptor that doesn't have this dependency, in the standard (no EJB3) jbossAS config. http://jira.jboss.com/jira/browse/JBAS-3964 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997327#3997327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997327

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Problem deploying a -beans.xml in a SAR

by scott.stark＠jboss.org

I see the error and will look at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997325#3997325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997325

17 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Code Coverage in JBoss AS Test Suite

by pavel.tsekov＠redhat.com

Posted to the wrong forum thread ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997323#3997323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997323

17 years, 4 months

1
0
0 / 0

[Design of JBoss ESB] - Re: JMS Provider(s) Design - JBossMQ/JBossMessaging/ActiveMQ

by jeffdelong

I built jbossesb from trunk and deployed sar to jboss-4.0.5.GA along with esb configuration files and war. I am getting an exception when I start the server org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] Cannot launch <org.jboss.soa.esb.listeners.message.MessageAwareListener> java.lang.NoSuchMethodException: org.jboss.soa.esb.listeners.message.MessageAwareListener.(org.jboss.soa.esb.listeners.message.EsbListenerController, org.jboss.soa.esb.helpers.ConfigTree) at java.lang.Class.getConstructor0(Class.java:2647) at java.lang.Class.getConstructor(Class.java:1629) at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.tryToLaunchChildListener(EsbListenerControllerFactory.java:394) at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.run(EsbListenerControllerFactory.java:346) at java.lang.Thread.run(Thread.java:595) 2007-01-02 11:04:25,640 ERROR [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] Cannot launch <org.jboss.soa.esb.listeners.message.MessageAwareListener> java.lang.NoSuchMethodException: org.jboss.soa.esb.listeners.message.MessageAwareListener.(org.jboss.soa.esb.listeners.message.EsbListenerController, org.jboss.soa.esb.helpers.ConfigTree) at java.lang.Class.getConstructor0(Class.java:2647) at java.lang.Class.getConstructor(Class.java:1629) at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.tryToLaunchChildListener(EsbListenerControllerFactory.java:394) at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.run(EsbListenerControllerFactory.java:346) at java.lang.Thread.run(Thread.java:595) 2007-01-02 11:04:25,656 DEBUG [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] About to sleep 49969 2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.State] Listener component [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] is now in a state of 'Ready'. 2007-01-02 11:04:25,734 DEBUG [org.jboss.soa.esb.listeners.message.EsbListenerControllerService] Started jboss.org:service=EsbListenerController 2007-01-02 11:04:25,734 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.org:service=EsbListenerController dependent components: [] 2007-01-02 11:04:25,734 DEBUG [org.jboss.system.ServiceController] starting service jboss.org:service=GatewayListenerController 2007-01-02 11:04:25,734 DEBUG [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] Starting jboss.org:service=GatewayListenerController 2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] starting message aware listener with config file jbossesb-gateway.xml 2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.gateway.GatewayListenerController] No value specified for: endTime - Listener will run until parent container/process terminates. 2007-01-02 11:04:25,750 DEBUG [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] Started jboss.org:service=GatewayListenerController 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.org:service=GatewayListenerController dependent components: [] 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting service jboss.jca:service=DataSourceBinding,name=JBossESBDS 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss.jca:service=DataSourceBinding,name=JBossESBDS 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting service jboss.jdbc:service=metadata,datasource=JBossESBDS 2007-01-02 11:04:25,750 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.DataSourceMetaData] Starting jboss.jdbc:service=metadata,datasource=JBossESBDS 2007-01-02 11:04:25,750 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.DataSourceMetaData] Started jboss.jdbc:service=metadata,datasource=JBossESBDS 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.jdbc:service=metadata,datasource=JBossESBDS dependent components: [] 2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting Also getting: 2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Loading jUDDI configuration. 2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Resources loaded from: /C:/jboss-ps-0.1/jboss-4.0.5.GA/server/ps/conf/juddi.properties 2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Initializing jUDDI components. 2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Service name: trailblazer-jmsbank:jmsbankreplies 2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Description: null 2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Key id: 8A386AE0-909D-11DB-AAE0-C8137B127B1B 2007-01-02 11:04:34,781 ERROR [STDERR] Exception in thread "Thread-36" 2007-01-02 11:04:34,781 ERROR [STDERR] java.lang.LinkageError: loader constraints violated when linking org/w3c/dom/Document class 2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.internal.soa.esb.addressing.helpers.EPRHelper.toXMLString(EPRHelper.java:151) 2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:185) 2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.register(GatewayListenerController.java:644) 2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.run(JmsGatewayListener.java:75) 2007-01-02 11:04:34,781 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997322#3997322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997322

17 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Code Coverage in JBoss AS Test Suite

by ryan.campbell＠jboss.com

Manik, Where should we document this test case? A readme in the src/etc folder? Somewhere else? Thanks, Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997316#3997316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997316

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Problem deploying a -beans.xml in a SAR

by bstansberry＠jboss.com

There are problems deploying the tc6 clustering cache on trunk. It's deployed via a -beans.xml nested in an expanded .sar. I get errors deploying some of the nested beans in the config as follows; which bean fails seems to vary. 2006-12-31 17:28:44,527 ERROR [org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer] Error during deployment: jboss:id=tc6-cluster.sar,service=jacc | org.jboss.deployers.spi.DeploymentException: Error deploying: TomcatClusteringBuddyLocatorConfig | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:71) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) | 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:508) | at java.lang.Thread.run()V(Unknown Source) | Caused by: java.lang.IllegalStateException: TomcatClusteringBuddyLocatorConfig is already installed. | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:249) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:67) | ... 16 more This may be an odd case due to funky packaging. The sar looks like this: tc6-cluster.sar -- META-INF -- -- tc6-cluster-beans.xml -- tc6-cluster.aop That packaging is a bit of a 4.x legacy and doesn't need to be that way; using a simple directory to logically group the two files is fine, even better: tc6-cluster -- tc6-cluster-beans.xml -- tc6-cluster.aop When I shift to this packaging, it seems to deploy without issue. But, the other packaging was working with the Beta1 release, so I want to mention it in case this is a sign of something more fundamental being broken. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997313#3997313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997313

17 years, 4 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JSR-160 support

by tom.elrod＠jboss.com

jmx-remoting.sar is already included in HEAD and would use the JDK 1.5 JSR-160 implementation by default. Could also include this for JBoss 4.2 if desired. At that point, is only a question of performance (assuming JDK 1.5 or higher is required for JBossAS 4.2+) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997280#3997280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997280

17 years, 4 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JSR-160 support

by tom.elrod＠jboss.com

Probably not. There were only two initial reasons for JSR-160 implementation: 1. JDK 1.4 did not have it built in, so would need to drop in an implementation. 2. Performance could potentially be better with custom implementation. Since are so far behind on JBoss implementation, don't know that 1 applies anymore (since JBoss 5 will be jdk 1.5, which has JSR-160 built in). As for 2, don't know how good/bad Sun's implementation is in regards to performance. Since remote jmx calls is not part of core JBoss infrastructure, may not really be an issue (where as jboss jmx microkernel was dependent upon jmx, rolling our own implementation made sense for performance reasons). I personally don't care either way, just don't have the time/resources to devote to it at the moment (and don't know when I would as has always been a low priority). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997278#3997278 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997278

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover refactoring

by clebert.suconic＠jboss.com

Why did you remove testSimpleFailover from FailoverTest? This test killed the server, and performed an invocation while the server is dead. Something would intercept an exception from the communication layer and activate failover from that exception. I reactivated the test on my local copy, and the test is fails. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997277#3997277 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997277

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: unable to resolve beanClass method from remote proxy cal

by ravishbhupesh

hey I also got the same problem. actually I tried on 3-4 systems. on some the application is working fine but on 2-3 systems it is giving same error... if anybody got some sol. plz do reply.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997276#3997276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997276

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007