[JBoss Messaging] - Re: programmatically deploy clustered topic
by fatbatman
Hi Tim,
Thanks for the suggestion I might have a play with the farm service in the future.
If anyone is interested, for now I use something like the following, it seems to do what I need;
public void addTopicMessageListener(String jndiName, MessageListener messageListener) throws NamingException, JMSException, Exception {
|
| String topicName = jndiName.substring(jndiName.lastIndexOf('/')+1);
|
| try{
| //CHECK IF THE TOPIC IS DEPLOYED LOCALLY
| Topic topic = (Topic)haInitialContext.lookup(jndiName);
| log("OK Topic " + jndiName+ " exists");
|
| //I think this will throw an exception if the Topic is on a remote machine
| MessageConsumer subscriber = localJMSSession.createConsumer(topic);
| subscriber.setMessageListener(messageListener);
| log("Lstener "+messageListener+" add to topic " + topicName);
| }catch(Exception e){
| log("NO TOPIC, OR TOPIC WAS ON A REMOTE ONLY WHEN ADDING MessageListener TO topic "+topicName+". "+e.getMessage());
|
| //DEPLOY THE TOPIC ON THIS MACHINE
| MBeanServerConnection mBeanServer = MBeanServerLocator.locateJBoss();
| ServerPeerMBean serverPeerMBean = (ServerPeerMBean) MBeanServerInvocationHandler.newProxyInstance(mBeanServer, new ObjectName("jboss.messaging:service=ServerPeer"), ServerPeerMBean.class, false);
| serverPeerMBean.deployTopic(topicName, jndiName);
|
| //MAKE IT CLUSTERED
| ObjectName on = new ObjectName("jboss.messaging.destination:service=Topic,name="+topicName);
| MBeanInfo mbeanInfo = MBeanServerLocator.locateJBoss().getMBeanInfo(on);
| MBeanServerLocator.locateJBoss().invoke(on, "stop", null, null);
| MBeanServerLocator.locateJBoss().setAttribute(on, new Attribute("Clustered", true));
| MBeanServerLocator.locateJBoss().invoke(on, "start", null, null);
|
| //TRY TO ADD THE messageListenerAgain
| Topic topic = localJMSSession.createTopic(topicName);
| MessageConsumer subscriber = localJMSSession.createConsumer(topic);
| subscriber.setMessageListener(messageListener);
| log("Successfully added listener "+messageListener+" to distributed topic " + topicName);
| }
|
| }
cheers
James
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094631#4094631
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094631
18Â years, 9Â months
[EJB 3.0] - CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required S
by rasisuku
Hi,
server: jboss-5.0.0.Beta2
os: winxp
I created one session bean which has entity manager injection in it like
@PersistenceContext (unitName="ejb3test")
EntityManager em;
and my persistence.xml is
<persistence-unit name="ejb3test">
<jta-data-source>jdbc/test</jta-data-source>
</persistence-unit>
when i create a jar file out of this and deploy, it gives the following error . please help to solve this issue.
10:03:26,343 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta2 (build: SVNT
ag=JBoss_5_0_0_Beta2 date=200704060017)] Started in 1m:21s:750ms
10:03:34,921 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:jar=sa.jar,
name=AnnotationClient,service=EJB3 with dependencies:
10:03:34,921 INFO [MCKernelAbstraction] persistence.units:unitName=ejb3t
est
10:03:34,984 WARN [HDScanner] Failed to process changes
org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete dep
loyments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual Stat
e}
jboss.j2ee:jar=sa.jar,name=AnnotationClient,service=EJB3
-> {Described:** UNRESOLVED AbstractDemandMetaData$DemandDependencyIte
m@16d383a{name=jboss.j2ee:jar=sa.jar,name=AnnotationClient,service=EJB3 dependsO
n=null whenRequired=Described resolved=false demand=persistence.units:unitName=e
jb3trail} **}
*** CONTEXTS IN ERROR: Name -> Error
-> ** UNRESOLVED AbstractDemandMetaData$DemandDependencyItem@16d383a{n
ame=jboss.j2ee:jar=sa.jar,name=AnnotationClient,service=EJB3 dependsOn=null when
Required=Described resolved=false demand=persistence.units:unitName=ejb3test} *
*
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.checkIncom
plete(HDScanner.java:346)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDSca
nner.java:303)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScan
ner.java:234)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:41
7)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java
:280)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$101(ScheduledThreadPoolExecutor.java:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
runPeriodic(ScheduledThreadPoolExecutor.java:142)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(ScheduledThreadPoolExecutor.java:166)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:675)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094606#4094606
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094606
18Â years, 9Â months