[JBoss Portal] - Re: Default Pages On Reboot
by PeterJ
Yes, if you are using the same database for development and production, you could just copy the database contents, provided that you have not, during development or testing, put a lot of things into the database that you don't want in production. As an example, I placed a lot of things into CMS to test out various directory structures, and some of those artifacts ended up with multiple revisions. But in production I wanted just the last directory structure and last version of only some of the artifacts. For this it was easier to start with a clean database with my desired CMS content as the default content. I spent a lot of time in development reinitializing everything, including the database, that I wrote an ant script to do it for me. Thus my latest portal layout was always in *-object.xml files. And it was easy to place the portal under version control as it was being developed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132325#4132325
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132325
18 years, 1 month
[JNDI/Naming/Network] - remote JNDI lookup fails
by lamprecht
Hi,
I've a problem reaching JDNI from a remote, standalone client. The lookup is done by the following code:
Properties props = new Properties();
| props.setProperty("java.naming.provider.url", "jnp://server:1099");
| props.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
| props.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| InitialContext ctx = new InitialContext(props);
| result = ctx.lookup(path);
It runs perfect on the host "server". But when I run it on a different host, I get an exception:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
| java.net.ConnectException: Connection refused]
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at mdb.test.client.Lookup.lookup(Lookup.java:49)
| at mdb.test.client.jms_client.main(jms_client.java:23)
| Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
| java.net.ConnectException: Connection refused
| at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
| at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
| at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
| at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
| ... 4 more
What surprises me is, that the client seems to try to connect to localhost, even though the provider URL points to a different host.
There are no firewalls between the two maschines. JBoss (4.2.2GA) is listening on the respective IP/port on the server, I can reach it with telnet.
If I shutdown JBoss, I get a different error message. Therefore I assume, that the client is connecting to the server.
Thanks in advance,
Heiner
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132314#4132314
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132314
18 years, 1 month
[JBoss Portal] - Re: Default Pages On Reboot
by dsulliva
I understand what you are saying.
Is this the only way to do this. For instance playing with the forums portlet.
If I make the parent-ref empty (ie. <parent-ref></parent-ref> )
then the forums tab/page does not show up and the forums portlet instance is not an available portlet when modifying page content
Is there a way to change *-object.xml to prevent it from being configured initially and still have the portlet instance show up as being available and then have the portlet management configure where to put the portlet instance?
Just seems to me like all portlet instances would be loaded in without being pre-defined by *-object.xml. I guess I may be missing something.
Please inform.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132313#4132313
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132313
18 years, 1 month
[EJB/JBoss] - Migrating from jBoss4.0.5GA to 4.2.2GA
by nsmith80
I'm trying to use 4.2.2GA for an EJB3 application that currently runs in 4.0.5GA without any major issues. I'm running into an issue where the app server is trying to use ejb-jar.xml file even though I don't use it. I get the following warnings when I start the server:
008-02-26 13:34:22,737 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminStatsLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminRegionLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrCoachLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrSchoolLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,768 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserPlayerLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserCoachLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserGroupLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserGameLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserStatsLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserVenueLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSchoolLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSportLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSeasonLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
2008-02-26 13:34:22,831 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
It finally throws up toward the end of the deployment with the following error:
2008-02-26 13:34:36,984 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminFactoryBean,service=EJB3
State: FAILED
Reason: java.lang.RuntimeException: could not resolve global JNDI name for @EJB for container BeloAdminFactoryBean: reference class: com.belo.leaderboard.ejb.session.function.ISessionDMAUserSeasonLocal ejbLink: duplicated in LeaderboardEJB.jar
I Depend On:
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminDMABean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminStatsBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminCoachBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserRegionBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrAthleticDirectorBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserPositionBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrDiv1AthleteBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminSeasonBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminGroupBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrAlumBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminUserBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrReportingGroupBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminSportBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserTeamBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=AuthenticationBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserMeetBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserTournamentBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminSchoolBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminVenueBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserRosterBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminPlayerBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminGameBean,service=EJB3
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminRegionBean,service=EJB3
Depends On Me:
jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminBean,service=EJB3
Does anyone have any ideas? Is there a way to keep jBoss from looking for the ejb-jar.xml file altogether?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132311#4132311
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132311
18 years, 1 month
[Remoting] - SLL Socketfactory: Keystore was tampered with, or password w
by skassa
I'm running into this problem intermittently. It only clears up if I shutdown JBoss server. Here code snippet that causes it:
HashMap metadata = new HashMap();
metadata.put(Bisocket.IS_CALLBACK_SERVER, "true");
boolean serverToClient = true;
remotingClient.addListener(callbackHandler, metadata, null,
serverToClient);
Caused by: java.io.IOException: Error initializing socket factory SSL context: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(Unknown Source)
at java.security.KeyStore.load(Unknown Source)
at org.jboss.remoting.security.SSLSocketBuilder.loadKeyStore(SSLSocketBuilder.java:1548)
at org.jboss.remoting.security.SSLSocketBuilder.loadTrustManagers(SSLSocketBuilder.java:1395)
at org.jboss.remoting.security.SSLSocketBuilder.initializeSocketFactorySSLContext(SSLSocketBuilder.java:1326)
at org.jboss.remoting.security.SSLSocketBuilder.createCustomSocketFactory(SSLSocketBuilder.java:451)
at org.jboss.remoting.security.SSLSocketBuilder.createSSLSocketFactory(SSLSocketBuilder.java:431)
at org.jboss.remoting.security.SSLSocketBuilder.createSSLSocketFactory(SSLSocketBuilder.java:381)
at org.jboss.remoting.AbstractInvoker.createSocketFactory(AbstractInvoker.java:307)
at org.jboss.remoting.transport.sslbisocket.SSLBisocketClientInvoker.createSocketFactory(SSLBisocketClientInvoker.java:80)
at org.jboss.remoting.RemoteClientInvoker.(RemoteClientInvoker.java:46)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.(MicroSocketClientInvoker.java:218)
at org.jboss.remoting.transport.socket.SocketClientInvoker.(SocketClientInvoker.java:72)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.(BisocketClientInvoker.java:157)
at org.jboss.remoting.transport.sslbisocket.SSLBisocketClientInvoker.(SSLBisocketClientInvoker.java:66)
at org.jboss.remoting.transport.sslbisocket.TransportClientFactory.createClientInvoker(TransportClientFactory.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.remoting.InvokerRegistry.loadClientInvoker(InvokerRegistry.java:419)
at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:320)
at org.jboss.remoting.Client.connect(Client.java:459)
at org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:153)
at org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1707)
at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1371)
at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:641)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:756)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132306#4132306
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132306
18 years, 1 month
[EJB 3.0] - MDB DeploymentException: Unable to create activation spec
by rledousa
Hi-
I've just created my first MDB in JBoss 5.0 Beta 4 using Java 1.5. When I start Jboss, I see the following error:
12:14:37,375 INFO [EJBContainer] STARTED EJB: cmpe275.ejb.SensorDataMDB ejbName: SensorDataMDB
12:14:37,406 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=cmpe275-prj3-ejb.jar,name=SensorDataMDB,service=EJB3 state=Create
org.jboss.deployment.DeploymentException: Unable to create activation spec ra=jboss.jca:service=RARDeployment,name='jms-ra.rar' messaging-type=javax.jms.MessageListener properties={destination=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@aac6440e{destination}, destinationType=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@96f19068{destinationType}, subscriptionDurability=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@2263d106{subscriptionDurability}}
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:299)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:192)
at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:187)
at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:151)
at org.jboss.ejb3.mdb.MDB.start(MDB.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46)
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:327)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at org.jboss.system.ServiceController.doChange(ServiceController.java:659)
at org.jboss.system.ServiceController.start(ServiceController.java:431)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:150)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:108)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
at org.jboss.Main.boot(Main.java:208)
at org.jboss.Main$1.run(Main.java:534)
at java.lang.Thread.run(Thread.java:803)
Caused by:
javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name='jms-ra.rar' is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662)
at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:294)
... 54 more
Here's the class definition:
import javax.jms.Message;
import javax.jms.MessageListener;
import org.jboss.logging.Logger;
import javax.ejb.MessageDriven;
import javax.ejb.ActivationConfigProperty;
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Topic"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="topic/SensorData")
})
// topic is under java:comp/env/
public class SensorDataMDB implements MessageListener {
private static Logger logger = Logger.getLogger(SensorDataMDB.class);
public SensorDataMDB() {
}
public void onMessage(Message arg0) {
// TODO Auto-generated method stub
}
}
Any help would be greatly appreciated!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132304#4132304
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132304
18 years, 1 month