[JBoss Remoting] - JBoss EJB3 remote invocation from client app
by zecas zecas
zecas zecas [http://community.jboss.org/people/zecas] created the discussion
"JBoss EJB3 remote invocation from client app"
To view the discussion, visit: http://community.jboss.org/message/544548#544548
--------------------------------------------------------------
Hi,
I'm trying to workout an EJB example with JBoss, but I'm having some trouble understanding some things, and making other things to work.
My Environment:
- Windows XP;
- JBoss 5.1.0.GA;
- Eclipse.
The project is composed of an EAR with an EJB 3.0 and WAR module. Then I'll try to connect remotely in a client application to invoke the EJB.
So for a start, my EJB definition is:
package com.test;
import javax.ejb.Stateless;
/**
* Session Bean implementation class MyBean
*/
@Stateless(name = "my-name", mappedName = "my-map")
public class MyBean implements MyRemote, MyLocal {
/**
* Default constructor.
*/
public MyBean() {
}
public String getMyCommon() {
return "My-Common";
}
public String getMyRemote() {
return "My-Remote";
}
public String getMyLocal() {
return "My-Local";
}
}
package com.test;
import javax.ejb.Local;
@Local
public interface MyLocal {
public String getMyCommon();
public String getMyLocal();
}
package com.test;
import javax.ejb.Remote;
@Remote
public interface MyRemote {
public String getMyCommon();
public String getMyRemote();
}
My ejb-jar.xml in EJB module META-INF, has no definitions:
<?xml version="1.0" encoding="ASCII"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
<display-name>my-ejb</display-name>
</ejb-jar>
My web.xml in WAR module has no reference to EJB:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
<display-name>my-web</display-name>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
</web-app>
My application.xml describes the modules:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5">
<display-name>my-ear</display-name>
<module>
<web>
<web-uri>my-web-0.0.1-SNAPSHOT.war</web-uri>
<context-root>/my-web</context-root>
</web>
</module>
<module>
<ejb>my-ejb-0.0.1-SNAPSHOT.jar</ejb>
</module>
</application>
The WAR has a small test page, that injects the @EJB local interface, and successfully gets data, so I assume no other config should be necessary (for now, at least).
For deployment, I just copied the EAR to deploy directory. No errors, and checking JMX Console I can find the following info:
jboss.deployment
# id="jboss.j2ee:ear=my-ear-0.0.1-SNAPSHOT.ear,jar=my-ejb-0.0.1-SNAPSHOT.jar,name=my-name,service=EJB3",type=Component
# id="jboss.j2ee:ear=my-ear-0.0.1-SNAPSHOT.ear,jar=my-ejb-0.0.1-SNAPSHOT.jar,name=my-name,service=EJB3_endpoint",type=Component
I then created a small standalone project, with following code:
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
environment.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
environment.put(Context.PROVIDER_URL, "jnp://127.0.0.1:1099"); // remote machine IP
InitialContext context = null;
try {
context = new InitialContext(environment);
Object obj = context.lookup("my-name");
System.out.println("-->> lookup object successfully");
} catch(Throwable ex) {
ex.printStackTrace();
} finally {
if( context!=null ) {
context.close();
}
}
When executing, I get the exception:
javax.naming.NameNotFoundException: my-name not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
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:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
Changing the lookup to:
Object obj = context.lookup("my-map");
Or replacing with:
MyRemote myRemote = (MyRemote) context.lookup("my-map");
Will return:
java.lang.ClassCastException: javax.naming.Reference cannot be cast to com.test.MyRemote
My client application has dependency to the EJB client jar, which only has MyRemote and MyLocal classes, and a dependency to jbossall-client-3.2.3.jar.
If I narrow:
MyRemote myRemote = (MyRemote) PortableRemoteObject.narrow(
context.lookup("my-map"),
MyRemote.class
);
I'll get:
java.lang.ClassCastException
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:229)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
... 2 more
Caused by: java.lang.ClassCastException: javax.naming.Reference cannot be cast to org.omg.CORBA.Object
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:212)
... 3 more
What am I doing wrong?
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544548#544548]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
[JBoss Messaging] - PLEASE HELP ME JBOSS QUEUE NOT BOUND EXCEPTION
by deepak mk
deepak mk [http://community.jboss.org/people/deepak.mk] created the discussion
"PLEASE HELP ME JBOSS QUEUE NOT BOUND EXCEPTION"
To view the discussion, visit: http://community.jboss.org/message/544525#544525
--------------------------------------------------------------
Hi,
Please anyone here help me in resolving the exception coming below ,:-
07:05:23,970 ERROR [JmsActivation] Unable to reconnect mailto:org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@707b124c(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@cba816c org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@707b124c(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)cba816c destination=NewsProcessorQueue destinationType=javax.jms.Queue selector= tx=true durable=false reconnect=10 provider=DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=30000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=10)
javax.naming.NameNotFoundException: NewsProcessorQueue not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.util.naming.Util.lookup(Util.java:222)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
I migrated from jboss 4 to jboss 5.1 GA , i am getting the exeception above as queue not bound . I have the configured the queue name in destinations-service.xml as follows :-
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=NewsProcessorQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
I also tried including <create-destiantion>true</create-destination> tag in jboss.xml . Not able to resolve this exception. Can anyone please help me
in this regard.
Deepak
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544525#544525]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
Re: [jboss-user] [jBPM] - Query task with variables
by Thomas Victor
Thomas Victor [http://community.jboss.org/people/tvictor] replied to the discussion
"Query task with variables"
To view the discussion, visit: http://community.jboss.org/message/544511#544511
--------------------------------------------------------------
Hi http://community.jboss.org/people/rebody HuiSheng Xu,
Thank you very much for replying to my post.
The way in which it works is described below.
I added the jbpm mappings to my persistence.xml. Please see the configuration below. So that my persistence unit contains the jbpm tables also. So I can use jbpm objects along with my domain objects in JPA.
The query is given below
entityManager.createQuery("SELECT new com.imagitek.prodagioap.workflow.invoice.InvoiceTask(task, invoice) from org.jbpm.api.task.Task task, org.jbpm.pvm.internal.type.Variable var, com.imagitek.prodagioap.entity.ImInvoice invoice where var.execution=task.execution and invoice.id=var.l").getResultList();
This works because I know my variable will be a long data type.
? Right now I have a separate jbpm.hibernate.cfg.xml which is supplied by jbpm4. I am using this configuration also. Ultimately I want to use only the JPA configuration for everything. I want to get rid of the jbpm.hibernate.cfg.xml file. While creating the process engine I was able to supply hibernateSessionFactory which is provided by jpa/seam to the process engine. Then I was able to get rid of the jbpm.hibernate.cfg.xml. but the problem was that no data was persisted to the database. But all the rules, events etc were getting fired. I assume I am missing some transaction related stuff. Can please tell me what are the things I need to do to persist the data.
Thanks & Regards
Thomas Victor
<persistence-unit name="prodagioAP" transaction-type="JTA">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:/prodagioAPDatasource</jta-data-source>
<mapping-file>jbpm.repository.hbm.xml</mapping-file>
<mapping-file>jbpm.execution.hbm.xml</mapping-file>
<mapping-file>jbpm.history.hbm.xml</mapping-file>
<mapping-file>jbpm.task.hbm.xml</mapping-file>
<!-- <mapping-file>jbpm.identity.hbm.xml</mapping-file>-->
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/>
<property name="hibernate.hbm2ddl.auto" value="validate"/>
<property name="hibernate.show_sql" value="false"/>
<property name="hibernate.format_sql" value="true"/>
<property name="jboss.entity.manager.factory.jndi.name" value="java:/prodagioAPEntityManagerFactory"/>
<property name="hibernate.search.default.indexBase" value="/prodagio_indexs"/>
<property name="hibernate.ejb.event.post-insert" value="org.hibernate.search.event.FullTextIndexEventListener"/>
<property name="hibernate.ejb.event.post-update" value="org.hibernate.search.event.FullTextIndexEventListener"/>
<property name="hibernate.ejb.event.post-delete" value="org.hibernate.search.event.FullTextIndexEventListener"/>
</properties>
</persistence-unit>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544511#544511]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
[EJB 3.0] - error in deploying EJB3
by paresh bhavsar
paresh bhavsar [http://community.jboss.org/people/bhavsar.er] created the discussion
"error in deploying EJB3"
To view the discussion, visit: http://community.jboss.org/message/544500#544500
--------------------------------------------------------------
Hi,
I am having below mentioned persistence.xml.
<
persistence-unit name=+"eksOracle">
<jta-data-source>java:OracleDS</jta-data-source>
<properties>
<property name=+"hibernate.dialect" value=+"org.hibernate.dialect.OracleDialect" />
</properties>
</persistence-unit>
=============================================
i am using @PersistenceContext
(unitName="eksOracle")
*private* EntityManager entityManager;
in my DAO and getting following error.
2010-05-24 19:10:51,729 INFO [org.jboss.ejb3.session.SessionSpecContainer] (HDScanner) Stopping jboss.j2ee:jar=TestEJB.jar,name=MstConceptFacade,service=EJB3
2010-05-24 19:10:51,729 INFO [org.jboss.ejb3.EJBContainer] (HDScanner) STOPPED EJB: com.eks.ias.service.core.entity.MstConceptFacade ejbName: MstConceptFacade
2010-05-24 19:10:51,729 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Start: name=jboss.j2ee:jar=TestEJB.jar,name=MstConceptFacade,service=EJB3 state=Create
*java.lang.ClassCastException: $Proxy947 cannot be cast to javax.naming.Context*
at org.jboss.util.naming.Util.createSubcontext(Util.java:70)
please let me know where i am mistaking in injecting EntityManager...
++
+
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544500#544500]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
[JBoss Messaging] - Bridge qos_once_and_only_once - XA Recovery - Lost Messages
by Carlo Pacini
Carlo Pacini [http://community.jboss.org/people/jbosse] created the discussion
"Bridge qos_once_and_only_once - XA Recovery - Lost Messages"
To view the discussion, visit: http://community.jboss.org/message/544495#544495
--------------------------------------------------------------
Hi all,
i'm finding some trouble configuring XA Recovery and bridge with qos _once_and_only_once:
In this example i've deployed a queue (queuea) on jbm1 bridged with a queue (queueb) on jbm2 using qos once_and_only_once.
Following jbm 1.4.5 user guide, steps are :
1) Source and destination are on different server -> need to enlist sending and consuming session in JTA Transaction
2) Both supplied connection factories are XA
3) Enable XA recovery with JBoss Transaction
On jbm1 (ServerPeerID 49) , RemoteJMSProvider definition:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider">
<attribute name="ProviderName">RemoteJMSProvider</attribute>
<attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
<!-- The combined connection factory -->
<attribute name="FactoryRef">XAConnectionFactory</attribute>
<!-- The queue connection factory -->
<attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
<!-- The topic factory -->
<attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=ip.address.jbm.2:1099
</attribute>
</mbean>
queuea:
<mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=queuea" xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
Bridge:
<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=queueab" xmbean-dd="xmdesc/Bridge-xmbean.xml">
<depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
<depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
<attribute name="SourceDestinationLookup">/queue/queuea</attribute>
<attribute name="TargetDestinationLookup">/queue/queueb</attribute>
<attribute name="QualityOfServiceMode">2</attribute>
<attribute name="MaxBatchSize">1</attribute>
<attribute name="MaxBatchTime">1000</attribute>
<attribute name="FailureRetryInterval">5000</attribute>
<attribute name="MaxRetries">-1</attribute>
<attribute name="AddMessageIDInHeader">false</attribute>
</mbean>
On jbm2 (ServerPeerID 51) queueb:
<mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=queueb" xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
Enable XA recovery with JBoss Transactions, added in jbossjta-properties.xml of jbm1 and jbm2:
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
Seems that sending messages to queuea and simulating a crash ( kill -9 pidjbm ) cause that some message are lost and not arrive on queueb.
Step to reproduce:
- started instances jbm1 and jbm2 (JBoss 4.2.3 with messaging 1.4.5, persistence on oracle db 11.2 ) on different linux server with queue and bridge definition
- sending 1000 messaging on queuea with jmeter
- while message are in transit from jbm1 to jbm2 , kill -9 jbm1
- wait a couple of minutes
- kill -9 jbm2
- start jbm1
- start jbm2
- wait 10 minutes
- looking on queueb via jmx-console there're 999 messages.
On db seems there's a stuck transaction:
SQL> select count(*) from jbm1.jbm_msg;
COUNT(*)
----------
1
SQL> select count(*) from jbm1.jbm_msg_ref;
COUNT(*)
----------
0
SQL> select count(*) from jbm1.jbm_tx;
COUNT(*)
----------
0
SQL> select count(*) from jbm2.jbm_msg;
COUNT(*)
----------
1000
SQL> select count(*) from jbm2.jbm_msg_ref;
COUNT(*)
----------
1000
SQL> select count(*) from jbm2.jbm_tx;
COUNT(*)
----------
1
In jbm1 server.log see:
2010-05-24 13:46:03,483 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.interna
l.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 29, 27, 1--3f578bcf:b0e5:4
bfa6494:96a-3f578bcf:b0e5:4bfa6494:96b^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@ >
or in another case:
SQL> select count(*) from jbm1.jbm_msg;
COUNT(*)
----------
1
SQL> select count(*) from jbm1.jbm_msg_ref;
COUNT(*)
----------
1
SQL> select count(*) from jbm1.jbm_tx;
COUNT(*)
----------
1
SQL> select count(*) from jbm2.jbm_msg;
COUNT(*)
----------
1000
SQL> select count(*) from jbm2.jbm_msg_ref;
COUNT(*)
----------
1000
SQL> select count(*) from jbm2.jbm_tx;
COUNT(*)
----------
1
jbm1 server.log :
2010-05-24 14:20:46,882 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.notrollback] Told not to rollback < 131075,
1--3f578bcf:e8cc:4bfa6b9d:a2e, -3f578bcf:e8cc:4bfa6b9d:a2f >
Same behaviour, send 1000 message on queuea, crash, 999 arrive on queueb.
Seems that records remain forever on db (no tansaction replication nor cleanup), suspect a configuration issue.
Looking the steps on user guide and on the wiki http://community.jboss.org/wiki/JBMBridgeConfiguration http://community.jboss.org/wiki/JBMBridgeConfiguration i've not found the error.
There're other steps to follow to configure bridge, qos once_and_only_once and xa recovery that i miss?
Thanks in advance,
Carlo
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544495#544495]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month