[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p
by thomasra
This is from JBM to ActiveMQ. The "outbound" queue is mapped in the Properties section of my ProviderLoader (attached below the bridge xml).
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Example Message Bridge configurations
|
| $Id: destinations-service.xml 1930 2007-01-09 18:16:04Z timfox $
| -->
|
| <server>
|
| <mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="com.nordpool:service=Bridge,name=BridgeToOM"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
|
| <attribute name="SourceProviderLoader">jboss.mq:service=JMSProviderLoader,name=JMSProvider</attribute>
|
| <attribute name="TargetProviderLoader">jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider</attribute>
|
| <attribute name="SourceDestinationLookup">topic/out</attribute>
|
| <attribute name="TargetDestinationLookup">outbound</attribute>
|
| <attribute name="SourceUsername">test</attribute>
|
| <attribute name="SourcePassword">test</attribute>
|
| <attribute name="TargetUsername">test</attribute>
|
| <attribute name="TargetPassword">test</attribute>
|
| <attribute name="QualityOfServiceMode">0</attribute>
|
| <attribute name="Selector">SERVICE='om'</attribute>
|
| <attribute name="MaxBatchSize">1</attribute>
|
| <attribute name="MaxBatchTime">1</attribute>
|
| <attribute name="SubName">bridge</attribute>
|
| <attribute name="ClientID">bridge-id</attribute>
|
| <attribute name="FailureRetryInterval">1000</attribute>
|
| <attribute name="MaxRetries">2</attribute>
|
| </mbean>
|
|
| </server>
|
The provider ds.xml:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <connection-factories>
|
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider">
| <attribute name="ProviderName">ActiveMQJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">ConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">ConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">ConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
| java.naming.provider.url=tcp://externalhost:61616
| queue.inbound=OM.from
| queue.outbound=OM.to
| </attribute>
|
| </mbean>
|
| </connection-factories>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053822#4053822
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053822
18 years, 10 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p
by timfox
"thomasra" wrote : 08:50:08,328 WARN [Bridge] Failed to send + acknowledge batch, closing JMS objects
| javax.jms.InvalidDestinationException: Destination cannot be foreign
| at org.jboss.jms.message.JBossMessage.setJMSDestination(JBossMessage.java:469)
| at org.jboss.jms.message.MessageProxy.setJMSDestination(MessageProxy.java:198)
| at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1507)
| at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
| at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:356)
| at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1201)
| at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:64)
| at org.jboss.jms.server.bridge.Bridge$SourceListener.onMessage(Bridge.java:1422)
| at org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:153)
| at org.jboss.jms.client.remoting.MessageCallbackHandler$ListenerRunner.run(MessageCallbackHandler.java:884)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
Please can you post your bridge config.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053819#4053819
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053819
18 years, 10 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p
by thomasra
08:50:08,328 WARN [Bridge] Failed to send + acknowledge batch, closing JMS objects
javax.jms.InvalidDestinationException: Destination cannot be foreign
at org.jboss.jms.message.JBossMessage.setJMSDestination(JBossMessage.java:469)
at org.jboss.jms.message.MessageProxy.setJMSDestination(MessageProxy.java:198)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1507)
at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:356)
at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1201)
at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:64)
at org.jboss.jms.server.bridge.Bridge$SourceListener.onMessage(Bridge.java:1422)
at org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:153)
at org.jboss.jms.client.remoting.MessageCallbackHandler$ListenerRunner.run(MessageCallbackHandler.java:884)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053809#4053809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053809
18 years, 10 months
[Design of JBoss jBPM] - Re: Thinking about transition attrs
by tom.baeyens＠jboss.com
brittm, i think that method binding *is* supported in our current implementation. i remember i tweaked commons-el to check for property-getters, fields and methods.
but the downside is that this feature might be removed as we are probably going to standardize on the jboss-el implementation. that one supports even parameter binding in methods, but you have to choose wether you do a value binding or a method binding upfront. which means that you'll have to use different tags for method binding as for value binding in the language.
for adding the ui-stuff like confirm="true" to the process, i'm not that strict in separating process and UI things. i believe there can be some overlap for convenience. however we are very careful before we implement things that we don't consider crucial. as every piece of code that we include requires maintenance. and if this maintenance becomes too big for the benefits, combined with the load we can handle, it might be that your feature just gets removed. that is worse for you. so we are very reluctant to adopt new features, not in the core target of the project and if there is a chance that we might not be able to sustain the maintenance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053806#4053806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053806
18 years, 10 months
[Deployers on JBoss (Deployers/JBoss)] - Re: Error while deploying jar file
by Malert
Thanks peter,
I had a problem in the jar file and now it has been cleared, thanks a lot but now i have another error. hte error is given below,
ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.
0.5.GA/server/default/deploy/ServiceBean.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans faile
d, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
rServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInt
erceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(Deployer
InterceptorEJB.java:44)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy26.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
plese tell me if you have any idea on this.
Thanks,
Malert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053794#4053794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053794
18 years, 10 months