Hi Jason,
how nice that finally someone is really using the JMS ra and in a
distributed fashion. I have to admit that it has not been tested in such
a setup yet.

I will try to comment your mail, but first: there are two things that I
know have caused problem of the type you describe:

1. If you get a XAxxxConnectionFactory and you do not have any process
   that actuallt starts the transaction, then you are in trouble.

2. I have gotten the same type of exception, and as far as I can
   remember the solution is to put jbossmq-client.jar in your classpath,
   ie for server to server communication, put it in lib/ext (but I have
   not tested this for a while).

On 20 Jun, Jason Dillon wrote:
> Hey, I have been trying to figure this out for a few days now and I keep
> running into walls.  I have a distributed system that uses JMS for
> communication, using a centralized router (all running on JBoss with
> JBossMQ).
> 
> I was able to get everything working using an ExternalContext, to map in the
> namespace of the remote router, but that is less than perfect.  I started to
> change over to the JmsXA adapter, but I am running into some odd problems.
> 
> An overly simplified view of the system looks like this, showing three
> seperate pyshical machines: web server, manager node and router.  The
> current architecture assumes a hub-spoke model for using JMS resources, so
> that all machines that actually make use of the JMS resources are remote,
> there are not MDB's running on the router.

You mean the MDB:s are running on the nodes (subscribing to destinations
in the router) and the session beans are also on the nodes, sending to
destinations in the router?

> 
>                       RMI
>   [ web server ] +-----------+ [ manager node ]
>                                    |       |
>                          (SessionBean)   (MDB)
>                            |               |
>                    JMS Queue Resource      |
>                                  \        /
>                                    \    /
>                                  [ router ]
>                                      ||
>                                 (real queues)
> 
> I installed the resource adapter, which seems to like to be deployed rather
> than having a mbean entry added in jboss.jcml, which I basically copied from
> the main branch conf/default files.


Hm, the ra must be both in jboss.jcml AND be deployed. It is confiured
in jboss.jcml and bound to the correct JNDI, and then the *.ra file must
be deployed (which is done be default in cvs version and 2.4).


> 
> The manager has a JMSProviderLoader installed which is using a remote
> <hostname>:<port> url to the router, and has the default session pool stuff.
> I think that the MDB bits work fine.  I do not *think* that I had to change
> anything to get that to work, the problem I am running into is with JMS
> resources.

Do you have a customized JMSProviderLoader, of type:

  <mbean code="org.jboss.jms.jndi.JMSProviderLoader" 
name=":service=JMSProviderLoader,name=MyRemoteLoader">
    <attribute name="ProviderName">MyRemoteProvider</attribute>
     <attribute name="ProviderUrl">router:1099</attribute>
    <attribute 
name="ProviderAdapterClass">org.jboss.jms.jndi.JBossMQProvider</attribute>
  </mbean>


If this is the way you have done it you must also configure the RA to
use this provider: (Observer the JmsProviderAdapterJNDI attribute - this
configuration should also be possible to do in ra.xml

  <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
  <mbean code="org.jboss.resource.ConnectionFactoryLoader"
         name="JCA:service=ConnectionFactoryLoader,name=JmsXA">
    <attribute name="FactoryName">JmsXA</attribute>
    <attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
    <attribute name="ResourceAdapterName">JMS Adapter</attribute>
    <attribute name="ConnectionManagerFactoryName">MinervaXACMFactory</attribute>
    <!-- See the documentation for the specific connection manager
         implementation you are using for the properties you can set -->
    <attribute name="ConnectionManagerProperties">
    <attribute name="Properties">
      JmsProviderAdapterJNDI=MyRemoteProvider
    </attribute>
      # Pool type - uncomment to force, otherwise it is the default
      #PoolConfiguration=per-factory

      # Connection pooling properties - see
      # org.opentools.minerva.pool.PoolParameters
      MinSize=0
      MaxSize=10
      Blocking=true
      GCEnabled=false
      IdleTimeoutEnabled=false
      InvalidateOnError=false
      TrackLastUsed=false
      GCIntervalMillis=120000
      GCMinIdleMillis=1200000
      IdleTimeoutMillis=1800000
      MaxIdleTimeoutPercent=1.0
    </attribute>

    <!-- Principal mapping configuration -->
    <attribute 
name="PrincipalMappingClass">org.jboss.resource.security.ManyToOnePrincipalMapping</attribute>
    <attribute name="PrincipalMappingProperties">
    </attribute>
  </mbean>
> 
> Per your change note, I changed the res-jndi-name to from the external
> context path to java:JmsXA.  But I also had to use url's to get the
> destinations to work.  So I ended up with something like this:
> 
>  <resource-managers>
>     <resource-manager>
>       <res-name>QueueConnectionFactory</res-name>
>       <res-jndi-name>java:/JmsXA</res-jndi-name>
>     </resource-manager>
> 
>     <resource-manager>
>       <res-name>WorkRequestQueue</res-name>
>        <res-url>jnp://router:5001/queue/WorkRequestQueue</res-url>
>     </resource-manager>
> 
>     <resource-manager>
>       <res-name>WorkResponseQueue</res-name>
>       <res-url>jnp://router:5001/queue/WorkResponseQueue</res-url>
>     </resource-manager>
>   </resource-managers>
> 
> I started up the application again, and got:
> 
> <snip>
> javax.jms.JMSException: Invalid transaction id.
>       at
> org.jbossmq.SpyXAResourceManager.addMessage(SpyXAResourceManager.java:80)
>       at org.jbossmq.SpySession.sendMessage(SpySession.java:381)
>       at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:103)
>       at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:62)
>       at
> 
>com.boldfish.does.job.workflow.internal.RequestSpoolerEJB.send(RequestSpoolerEJB.java:217)
>       at
> 
>com.boldfish.does.job.workflow.internal.RequestSpoolerEJB.sendNextRequest(RequestSpoolerEJB.java:249)
>       at
> 
>com.boldfish.does.job.workflow.internal.RequestSpoolerEJB.spool(RequestSpoolerEJB.java:273)
>       at java.lang.reflect.Method.invoke(Native Method)
>       at
> 
>org.jboss.ejb.StatefulSessionContainer$ContainerInterceptor.invoke(StatefulSessionContainer.java:650)
>       at
> org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127)
>       at
> 
>org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:209)
>       at
> org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:159)
>       at
> org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:280)
>       at
> org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:107)
>       at
> org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195)
>       at
> org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:341)
>       at
> 
>org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:480)
>       at
> 
>org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:339)
>       at
> 
>org.jboss.ejb.plugins.jrmp.interfaces.StatefulSessionProxy.invoke(StatefulSessionProxy.java:136)
>       at $Proxy25.spool(Unknown Source)
>       at
> com.boldfish.does.job.service.JobController$Runner.run(JobController.java:216)
>       at java.lang.Thread.run(Thread.java:484)
> </snip>
> 
> So I thought that I should try a distributed TX manager, since that is what
> i really want.  I changed over to Tyrex on all nodes and I still got the
> same results.  I then tried to use a jnp:// url for the res-jndi-name, which
> looks like it got a little further, but throw a different TX related
> excepetion laiter.
> 
> I have session beans that use JMS resources and I have MDB, all of which
> work off of a remote provider.  What is the supported deployment descriptor
> syntax for JMS resources (both factories and desitations) and what needs to
> be done to make the distributed TX work.
> 
> A while back someone (could be you) said that using res-url was a hack
> around the lack of support for JMS resources, is that still true? 

For jboss 2.2.2 that is still true. In the developmen version it is not,
if the ra is used.

I have to admit there is still a problem with destination. To get the
connection from the correct JNDI you configure a ProviderLoader, but the
way both JMS and J2EE connector specifation is done I have found no way
of abstracting access to the destinations out from the normal JNDI
access.

If jnp://router:5001/queue/WorkRequestQueue does not work, you will have
to use Scot Starks solution to integrate another JNDI space into the
local JNDI, but I do not think this is your problem.

> If not
> what is the correct way to reference a remote connection and destination
> inside of the descriptor?

As far as I can see it you have done perfectly right, but remote
subscriptions with TX support has not been that much tested.

Pleas try the jbossmq-client.jar trick and see if it works.


I am sorry to say this, but I am going on a pretty long vaication from
today. I will try to check my mail of and on, the there may be long
periods of silence.

I do hope you get it going.


(Have you checked the jmsra tests in jbosstest?

//Peter
> 
> If you need more detail I can provide that for you, or really anyone who
> might have a clue as to why this is not working correctly.
> 
> Thanks,
> 
> --jason
> 
> 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user

-- 
Jobba hos oss: http://www.tim.se/weblab
------------------------------------------------------------
Peter Antman             Technology in Media, Box 34105 100 26 Stockholm
Systems Architect        WWW: http://www.tim.se
Email: [EMAIL PROTECTED]        WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 
------------------------------------------------------------


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to