Quantcast

[mule-user] Mule and JBoss Integration

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[mule-user] Mule and JBoss Integration

Maël LAVIE-DERANDE-2

 

First, I have confused WEB-INF and META-INF…

 

Look at the schema of my environment.

 

I am using eclipse and ant to deploy my config file. The echo component comes with mule, so the .jar is in the RAR.

I use JBoss 4.0.2, mule 1.1 RC1. I want to use JMS for the transport (so you must have the JBossMQ service which is running).

 

Look at my config files. I have joined my JBoss traces; tell me if you have the same errors.

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:46
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Very Much,

so where do you deploy your echo component on JBoss ( in the deploy directory or in the MuleRA.rar)

Mule will be usinf the mule-config.xml to identify the components. But from where will Mule pick them up from ?.

Also, are you putting the echo component as jar/ear or as plain class files?

-Poonam

 

 

----- Original Message -----

Sent: Thursday, July 28, 2005 3:07 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Server

            Default

                        Deploy

                                   MuleRA.rar

                                               Xyz.jar

                                               Pouet.jar

                                               Web-INF

                                                           ra.xml

I have not used MDBs yet

 

My first aim is to deploy three mule instances on three workstations with a simple echo component in each mule model. I encounter problems on startup; I feel it is a problem of cycling.

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:33
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Mael,

but i still am not very clear ,

By unzipped RAR do u mean ......mule-ra-1.0.rar is to be unzipped into the XYZ.rar directiry inside the dploy directory .

Also, what about my Ejb's( MDB) , do i deploy them as normal Ear's or is there some other procedure.

-Poonam

 

----- Original Message -----

Sent: Thursday, July 28, 2005 2:46 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Hello

 

If you want to start Mule with JBOss, you have to put the unzipped RAR in the deploy folder of the configuration you have choosen (default, for example). IMPORTANT: the folder’s name must end by ‘.rar’. In the WEB-INF directory, edit the ra.xml file and uncomment those lines:

 

<config-property>

  <description>A comma separated list of configuration resources to configure a Mule Manager instance.--> These can be a list of files on the classpath or filesystem. And the type of file--> referenced depends on the configurationBuilder set on this Adapter.</description>

  <config-property-name>Configurations</config-property-name>

  <config-property-type>java.lang.String</config-property-type>

  <config-property-value>mule-config.xml</config-property-value>

  </config-property>

 

I put the file mule-config.xml at the root oh the RAR. You should have to put some extra libs at the root too.

 

I still encounter problems when it starts. Try first with Mule Agents and test if you manage to reach localhost:9092.

 

I hope it will help you.

 

Maël

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 09:54
À : [hidden email]
Objet : [mule-user] Mule and JBoss Integration

 

How do I integrate Mule and JBoss ,

It specifies to write an outbound/Inbound  bean configuration

Which file will contain this configuration?

 

But, how to implant the mule instance into JBoss? How to use the resource adapter provided?

-Poonam.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: [mule-user] Mule and JBoss Integration

Maël LAVIE-DERANDE

Sorry, the archive has not passed the server.

 

You can download it here: http://www.isty.uvsq.fr/~lavied/%5bMule%20user%5d%20JBoss%20+%20JCA%20problems.zip

 

++

 


De : Maël LAVIE-DERANDE [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 12:03
À : [hidden email]
Objet : [mule-user] Mule and JBoss Integration

 

 

First, I have confused WEB-INF and META-INF…

 

Look at the schema of my environment.

 

I am using eclipse and ant to deploy my config file. The echo component comes with mule, so the .jar is in the RAR.

I use JBoss 4.0.2, mule 1.1 RC1. I want to use JMS for the transport (so you must have the JBossMQ service which is running).

 

Look at my config files. I have joined my JBoss traces; tell me if you have the same errors.

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:46
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Very Much,

so where do you deploy your echo component on JBoss ( in the deploy directory or in the MuleRA.rar)

Mule will be usinf the mule-config.xml to identify the components. But from where will Mule pick them up from ?.

Also, are you putting the echo component as jar/ear or as plain class files?

-Poonam

 

 

----- Original Message -----

Sent: Thursday, July 28, 2005 3:07 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Server

            Default

                        Deploy

                                   MuleRA.rar

                                               Xyz.jar

                                               Pouet.jar

                                               Web-INF

                                                           ra.xml

I have not used MDBs yet

 

My first aim is to deploy three mule instances on three workstations with a simple echo component in each mule model. I encounter problems on startup; I feel it is a problem of cycling.

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:33
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Mael,

but i still am not very clear ,

By unzipped RAR do u mean ......mule-ra-1.0.rar is to be unzipped into the XYZ.rar directiry inside the dploy directory .

Also, what about my Ejb's( MDB) , do i deploy them as normal Ear's or is there some other procedure.

-Poonam

 

----- Original Message -----

Sent: Thursday, July 28, 2005 2:46 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Hello

 

If you want to start Mule with JBOss, you have to put the unzipped RAR in the deploy folder of the configuration you have choosen (default, for example). IMPORTANT: the folder’s name must end by ‘.rar’. In the WEB-INF directory, edit the ra.xml file and uncomment those lines:

 

<config-property>

  <description>A comma separated list of configuration resources to configure a Mule Manager instance.--> These can be a list of files on the classpath or filesystem. And the type of file--> referenced depends on the configurationBuilder set on this Adapter.</description>

  <config-property-name>Configurations</config-property-name>

  <config-property-type>java.lang.String</config-property-type>

  <config-property-value>mule-config.xml</config-property-value>

  </config-property>

 

I put the file mule-config.xml at the root oh the RAR. You should have to put some extra libs at the root too.

 

I still encounter problems when it starts. Try first with Mule Agents and test if you manage to reach localhost:9092.

 

I hope it will help you.

 

Maël

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 09:54
À : [hidden email]
Objet : [mule-user] Mule and JBoss Integration

 

How do I integrate Mule and JBoss ,

It specifies to write an outbound/Inbound  bean configuration

Which file will contain this configuration?

 

But, how to implant the mule instance into JBoss? How to use the resource adapter provided?

-Poonam.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Mule and JBoss Integration

Poonam-2
I deployed the mule echo component i.e unzip mule-ra-1.0.rar into mule.rar directory in Jboss/default/deploy.
Also, i modifed ra.xml and uncommented the Configurations  property.
When JBoss Server starts , it throws the following Exception:
 
Caused by: org.mule.umo.lifecycle.InitialisationException: Failed to create Jms Connector
        at org.mule.providers.jms.JmsConnector.doInitialise(JmsConnector.java:136)
        at org.mule.providers.AbstractConnector.initialise(AbstractConnector.java:202)
        at org.mule.MuleManager.initialiseConnectors(MuleManager.java:649)
        at org.mule.MuleManager.initialise(MuleManager.java:559)
        at org.mule.MuleManager.start(MuleManager.java:593)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:273)
        ... 135 more
Caused by: javax.naming.NameNotFoundException: ConnectionFactory not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 
JBoss JMX-Console displays 
    +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
under global jndi namespace.
Can you tell me why it is not getting the ConnectionFactory?
 
 
 <endpoint-identifier name="fromLocalAPSToArguyl" value="jms://queue/A?connector=localJMSProvider"/>
Which is this queue in "jms://queue/A" in the above endpoint?
 
-Poonam.
----- Original Message -----
Sent: Thursday, July 28, 2005 3:36 PM
Subject: RE: [mule-user] Mule and JBoss Integration

Sorry, the archive has not passed the server.

 

You can download it here: http://www.isty.uvsq.fr/~lavied/%5bMule%20user%5d%20JBoss%20+%20JCA%20problems.zip

 

++

 


De : Maël LAVIE-DERANDE [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 12:03
À : [hidden email]
Objet : [mule-user] Mule and JBoss Integration

 

 

First, I have confused WEB-INF and META-INF…

 

Look at the schema of my environment.

 

I am using eclipse and ant to deploy my config file. The echo component comes with mule, so the .jar is in the RAR.

I use JBoss 4.0.2, mule 1.1 RC1. I want to use JMS for the transport (so you must have the JBossMQ service which is running).

 

Look at my config files. I have joined my JBoss traces; tell me if you have the same errors.

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:46
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Very Much,

so where do you deploy your echo component on JBoss ( in the deploy directory or in the MuleRA.rar)

Mule will be usinf the mule-config.xml to identify the components. But from where will Mule pick them up from ?.

Also, are you putting the echo component as jar/ear or as plain class files?

-Poonam

 

 

----- Original Message -----

Sent: Thursday, July 28, 2005 3:07 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Server

            Default

                        Deploy

                                   MuleRA.rar

                                               Xyz.jar

                                               Pouet.jar

                                               Web-INF

                                                           ra.xml

I have not used MDBs yet

 

My first aim is to deploy three mule instances on three workstations with a simple echo component in each mule model. I encounter problems on startup; I feel it is a problem of cycling.

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 11:33
À : [hidden email]
Objet : Re: [mule-user] Mule and JBoss Integration

 

Thanks Mael,

but i still am not very clear ,

By unzipped RAR do u mean ......mule-ra-1.0.rar is to be unzipped into the XYZ.rar directiry inside the dploy directory .

Also, what about my Ejb's( MDB) , do i deploy them as normal Ear's or is there some other procedure.

-Poonam

 

----- Original Message -----

Sent: Thursday, July 28, 2005 2:46 PM

Subject: RE: [mule-user] Mule and JBoss Integration

 

Hello

 

If you want to start Mule with JBOss, you have to put the unzipped RAR in the deploy folder of the configuration you have choosen (default, for example). IMPORTANT: the folder’s name must end by ‘.rar’. In the WEB-INF directory, edit the ra.xml file and uncomment those lines:

 

<config-property>

  <description>A comma separated list of configuration resources to configure a Mule Manager instance.--> These can be a list of files on the classpath or filesystem. And the type of file--> referenced depends on the configurationBuilder set on this Adapter.</description>

  <config-property-name>Configurations</config-property-name>

  <config-property-type>java.lang.String</config-property-type>

  <config-property-value>mule-config.xml</config-property-value>

  </config-property>

 

I put the file mule-config.xml at the root oh the RAR. You should have to put some extra libs at the root too.

 

I still encounter problems when it starts. Try first with Mule Agents and test if you manage to reach localhost:9092.

 

I hope it will help you.

 

Maël

 

 

 


De : Poonam [mailto:[hidden email]]
Envoyé : jeudi 28 juillet 2005 09:54
À : [hidden email]
Objet : [mule-user] Mule and JBoss Integration

 

How do I integrate Mule and JBoss ,

It specifies to write an outbound/Inbound  bean configuration

Which file will contain this configuration?

 

But, how to implant the mule instance into JBoss? How to use the resource adapter provided?

-Poonam.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Mule and JBoss Integration

Andrew Perepelytsya
Poonam,

From what I see, the first item to check is the jndiDestinations
property. If it is set to false, there can be issues with JNDI and JMS
resource lookup.

Next, try the java:/ConnectionFactory version instead of the ConnectionFactory.

Cheers,
Andrew
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Mule and JBoss Integration

Poonam-2
yes i got the solution...
the problem was that mule server(manager) was started before jndi in Jboss,
so i first started Jboss Server without mule rar and later on deployed my
mule rar .
it starts successfully ...
now I trying to send a jms msg to this mule component.....

-Poonam

----- Original Message -----
From: "Andrew Perepelytsya" <[hidden email]>
To: <[hidden email]>
Sent: Thursday, August 04, 2005 7:07 PM
Subject: Re: [mule-user] Mule and JBoss Integration


Poonam,

>From what I see, the first item to check is the jndiDestinations
property. If it is set to false, there can be issues with JNDI and JMS
resource lookup.

Next, try the java:/ConnectionFactory version instead of the
ConnectionFactory.

Cheers,
Andrew

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Done Mule and JBoss Integration

Poonam-2
Hi All,

I have been succesful  in integrating Mule and Jboss.. and I would like to
share this information with all
Special thanks to Mael...

Deploy Mule Instance on JBoss , for this you need to deploy Mule Resource
Adapter in Jboss Server.
Steps:
1. Download the Mule Resource adapter mule-ra-1.0.rar  from
http://mule.codehaus.org/Resource+Adapter.
2. Unzip it to a directory e.g. mule.rar.
3. Edit the file mule.rar/META-INF/ra.xml and uncommment the following
           <config-property>
            <description>
            A comma separated list of configuration resources to configure a
Mule Manager instance.
            These can be a list of files on the classpath or filesystem.
And the type of file
            referenced depends on the configurationBuilder set on this
Adapter.
           </description>
     <config-property-name>Configurations</config-property-name>
            <config-property-type>java.lang.String</config-property-type>
           <config-property-value></config-property-value>
        </config-property>

Note : Here <config-property-value> specifies the name of the mule config
file that mule instance will read on startup. For the time being you can
keep it empty.
4. Start JBoss Server with default configuartion .
        Note : Jboss may first start your mule service before starting the
jndi service. So, it may fail to find the jndiDestinations. The solution to
this problem is deploy Mule Service after jndi service has started. (Hot
Deployment)
5. Copy mule.rar directory into JBoss/default/deploy directory after JBoss
Server starts. You should be able to see Mule Manager Start successfully.


Deploy a custom component as a Mule UMO Component in JBoss.
1. Edit the file mule.rar/META-INF/ra.xml and specify the mule-config file
in <config-property-value>.
See below:
           <config-property>
            <description>
            A comma separated list of configuration resources to configure a
Mule Manager instance.
            These can be a list of files on the classpath or filesystem.
And the type of file
            referenced depends on the configurationBuilder set on this
Adapter.
           </description>
     <config-property-name>Configurations</config-property-name>
            <config-property-type>java.lang.String</config-property-type>
           <config-property-value>mule-config.xml</config-property-value>
        </config-property>

2. Add the mule-config file in the mule.rar directory under JBoss.
3. In the mule-config file specify the UMO components and the connectors(e.g
jms).

<connector name="jmsConnector1"
className="org.mule.providers.jms.JmsConnector">
     <properties>
          <property name="jndiInitialFactory"
value="org.jnp.interfaces.NamingContextFactory"/>
          <property name="jndiProviderUrl" value="jnp://localhost:1099"/>
          <property name="connectionFactoryJndiName"
value="ConnectionFactory"/>
     </properties>
 </connector>

 <endpoint-identifiers>
        <endpoint-identifier name="fromLocalAPSToArguyl"
value="jms://queue/A?connector=jmsConnector1"/>
  </endpoint-identifiers>


4. Put all your UMO components and connectors (Class files) under the
mule.rar directory in a jar file.
    Mule Instance will read this mule-config file for UMO components.
5. For testing try sending messages to this UMO Component on the specified
connectors(endpoint). The UMO component handles theses messages and may
send another the endpoint.

Any problems in the above procedure you can contact me

-Poonam

----- Original Message -----
From: "Poonam" <[hidden email]>
To: <[hidden email]>; "Andrew Perepelytsya" <[hidden email]>
Sent: Thursday, August 04, 2005 7:45 PM
Subject: Re: [mule-user] Mule and JBoss Integration


> yes i got the solution...
> the problem was that mule server(manager) was started before jndi in
Jboss,

> so i first started Jboss Server without mule rar and later on deployed my
> mule rar .
> it starts successfully ...
> now I trying to send a jms msg to this mule component.....
>
> -Poonam
>
> ----- Original Message -----
> From: "Andrew Perepelytsya" <[hidden email]>
> To: <[hidden email]>
> Sent: Thursday, August 04, 2005 7:07 PM
> Subject: Re: [mule-user] Mule and JBoss Integration
>
>
> Poonam,
>
> >From what I see, the first item to check is the jndiDestinations
> property. If it is set to false, there can be issues with JNDI and JMS
> resource lookup.
>
> Next, try the java:/ConnectionFactory version instead of the
> ConnectionFactory.
>
> Cheers,
> Andrew
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Done Mule and JBoss Integration

Ross Mason-x
Great!

We'll update the site docs.  Thanks for your (and Mael's) efforts :)

Cheers,

Ross

Poonam wrote:

>Hi All,
>
>I have been succesful  in integrating Mule and Jboss.. and I would like to
>share this information with all
>Special thanks to Mael...
>
>Deploy Mule Instance on JBoss , for this you need to deploy Mule Resource
>Adapter in Jboss Server.
>Steps:
>1. Download the Mule Resource adapter mule-ra-1.0.rar  from
>http://mule.codehaus.org/Resource+Adapter.
>2. Unzip it to a directory e.g. mule.rar.
>3. Edit the file mule.rar/META-INF/ra.xml and uncommment the following
>           <config-property>
>            <description>
>            A comma separated list of configuration resources to configure a
>Mule Manager instance.
>            These can be a list of files on the classpath or filesystem.
>And the type of file
>            referenced depends on the configurationBuilder set on this
>Adapter.
>           </description>
>     <config-property-name>Configurations</config-property-name>
>            <config-property-type>java.lang.String</config-property-type>
>           <config-property-value></config-property-value>
>        </config-property>
>
>Note : Here <config-property-value> specifies the name of the mule config
>file that mule instance will read on startup. For the time being you can
>keep it empty.
>4. Start JBoss Server with default configuartion .
>        Note : Jboss may first start your mule service before starting the
>jndi service. So, it may fail to find the jndiDestinations. The solution to
>this problem is deploy Mule Service after jndi service has started. (Hot
>Deployment)
>5. Copy mule.rar directory into JBoss/default/deploy directory after JBoss
>Server starts. You should be able to see Mule Manager Start successfully.
>
>
>Deploy a custom component as a Mule UMO Component in JBoss.
>1. Edit the file mule.rar/META-INF/ra.xml and specify the mule-config file
>in <config-property-value>.
>See below:
>           <config-property>
>            <description>
>            A comma separated list of configuration resources to configure a
>Mule Manager instance.
>            These can be a list of files on the classpath or filesystem.
>And the type of file
>            referenced depends on the configurationBuilder set on this
>Adapter.
>           </description>
>     <config-property-name>Configurations</config-property-name>
>            <config-property-type>java.lang.String</config-property-type>
>           <config-property-value>mule-config.xml</config-property-value>
>        </config-property>
>
>2. Add the mule-config file in the mule.rar directory under JBoss.
>3. In the mule-config file specify the UMO components and the connectors(e.g
>jms).
>
><connector name="jmsConnector1"
>className="org.mule.providers.jms.JmsConnector">
>     <properties>
>          <property name="jndiInitialFactory"
>value="org.jnp.interfaces.NamingContextFactory"/>
>          <property name="jndiProviderUrl" value="jnp://localhost:1099"/>
>          <property name="connectionFactoryJndiName"
>value="ConnectionFactory"/>
>     </properties>
> </connector>
>
> <endpoint-identifiers>
>        <endpoint-identifier name="fromLocalAPSToArguyl"
>value="jms://queue/A?connector=jmsConnector1"/>
>  </endpoint-identifiers>
>
>
>4. Put all your UMO components and connectors (Class files) under the
>mule.rar directory in a jar file.
>    Mule Instance will read this mule-config file for UMO components.
>5. For testing try sending messages to this UMO Component on the specified
>connectors(endpoint). The UMO component handles theses messages and may
>send another the endpoint.
>
>Any problems in the above procedure you can contact me
>
>-Poonam
>
>----- Original Message -----
>From: "Poonam" <[hidden email]>
>To: <[hidden email]>; "Andrew Perepelytsya" <[hidden email]>
>Sent: Thursday, August 04, 2005 7:45 PM
>Subject: Re: [mule-user] Mule and JBoss Integration
>
>
>  
>
>>yes i got the solution...
>>the problem was that mule server(manager) was started before jndi in
>>    
>>
>Jboss,
>  
>
>>so i first started Jboss Server without mule rar and later on deployed my
>>mule rar .
>>it starts successfully ...
>>now I trying to send a jms msg to this mule component.....
>>
>>-Poonam
>>
>>----- Original Message -----
>>From: "Andrew Perepelytsya" <[hidden email]>
>>To: <[hidden email]>
>>Sent: Thursday, August 04, 2005 7:07 PM
>>Subject: Re: [mule-user] Mule and JBoss Integration
>>
>>
>>Poonam,
>>
>>>From what I see, the first item to check is the jndiDestinations
>>property. If it is set to false, there can be issues with JNDI and JMS
>>resource lookup.
>>
>>Next, try the java:/ConnectionFactory version instead of the
>>ConnectionFactory.
>>
>>Cheers,
>>Andrew
>>
>>    
>>
>
>
>
>  
>

--
Regards,

Ross Mason
SymphonySoft Ltd

tel: 07005-978-001
fax: 07005-978-003
www.symphonysoft.com

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Done Mule and JBoss Integration

George Chen
In reply to this post by Poonam-2
Hi, Poonam or others,

I am having problem the  moment I dropped the mule.rar in jboss ( in server\default\deploy folder) after this step:

5. Copy mule.rar directory into JBoss/default/deploy directory after JBoss
Server starts.

before even deploying any UMO components.  I am using mule 1.2, jboss 4.0.4 and mule-ra-1.2.rar.  The message is pasted at the end.  Do you have any idea I did wrong?
Thanks,
George



JBOSS console message:

22:50:53,781 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 10s:766ms
22:51:22,906 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mule.rar/
22:51:23,078 WARN  [ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='mule.rar'
javax.resource.spi.ResourceAdapterInternalException: Failed to instanciate configurationBuilder class:
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:88)
        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy23.start(Unknown Source)
        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:345)
        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
        at java.lang.String.charAt(String.java:558)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:197)
        at org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:277)
        at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:284)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
        at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.mule.util.ClassHelper$8.run(ClassHelper.java:178)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.mule.util.ClassHelper.loadClass(ClassHelper.java:175)
        at org.mule.util.ClassHelper.instanciateClass(ClassHelper.java:277)
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:84)
        ... 42 more
22:51:23,109 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: user:service=QuartzService,name=QuartzService
  State: CONFIGURED
  I Depend On:
    jboss.jca:service=LocalTxCM,name=QuartzDS

ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: javax.resource.spi.ResourceAdapterInternalException: Failed to instanciate configurationBuilder class:

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: javax.resource.spi.ResourceAdapterInternalException: Failed to instanciate configurationBuilder class:

ObjectName: jboss.jca:service=LocalTxCM,name=QuartzDS
  State: NOTYETINSTALLED
  Depends On Me:
    user:service=QuartzService,name=QuartzService



Poonam wrote
Hi All,

I have been succesful  in integrating Mule and Jboss.. and I would like to
share this information with all
Special thanks to Mael...

Deploy Mule Instance on JBoss , for this you need to deploy Mule Resource
Adapter in Jboss Server.
Steps:
1. Download the Mule Resource adapter mule-ra-1.0.rar  from
http://mule.codehaus.org/Resource+Adapter.
2. Unzip it to a directory e.g. mule.rar.
3. Edit the file mule.rar/META-INF/ra.xml and uncommment the following
           <config-property>
            <description>
            A comma separated list of configuration resources to configure a
Mule Manager instance.
            These can be a list of files on the classpath or filesystem.
And the type of file
            referenced depends on the configurationBuilder set on this
Adapter.
           </description>
     <config-property-name>Configurations</config-property-name>
            <config-property-type>java.lang.String</config-property-type>
           <config-property-value></config-property-value>
        </config-property>

Note : Here <config-property-value> specifies the name of the mule config
file that mule instance will read on startup. For the time being you can
keep it empty.
4. Start JBoss Server with default configuartion .
        Note : Jboss may first start your mule service before starting the
jndi service. So, it may fail to find the jndiDestinations. The solution to
this problem is deploy Mule Service after jndi service has started. (Hot
Deployment)
5. Copy mule.rar directory into JBoss/default/deploy directory after JBoss
Server starts. You should be able to see Mule Manager Start successfully.


Deploy a custom component as a Mule UMO Component in JBoss.
1. Edit the file mule.rar/META-INF/ra.xml and specify the mule-config file
in <config-property-value>.
See below:
           <config-property>
            <description>
            A comma separated list of configuration resources to configure a
Mule Manager instance.
            These can be a list of files on the classpath or filesystem.
And the type of file
            referenced depends on the configurationBuilder set on this
Adapter.
           </description>
     <config-property-name>Configurations</config-property-name>
            <config-property-type>java.lang.String</config-property-type>
           <config-property-value>mule-config.xml</config-property-value>
        </config-property>

2. Add the mule-config file in the mule.rar directory under JBoss.
3. In the mule-config file specify the UMO components and the connectors(e.g
jms).

<connector name="jmsConnector1"
className="org.mule.providers.jms.JmsConnector">
     <properties>
          <property name="jndiInitialFactory"
value="org.jnp.interfaces.NamingContextFactory"/>
          <property name="jndiProviderUrl" value="jnp://localhost:1099"/>
          <property name="connectionFactoryJndiName"
value="ConnectionFactory"/>
     </properties>
 </connector>

 <endpoint-identifiers>
        <endpoint-identifier name="fromLocalAPSToArguyl"
value="jms://queue/A?connector=jmsConnector1"/>
  </endpoint-identifiers>


4. Put all your UMO components and connectors (Class files) under the
mule.rar directory in a jar file.
    Mule Instance will read this mule-config file for UMO components.
5. For testing try sending messages to this UMO Component on the specified
connectors(endpoint). The UMO component handles theses messages and may
send another the endpoint.

Any problems in the above procedure you can contact me

-Poonam

----- Original Message -----
From: "Poonam" <poonam@kenati.com>
To: <user@mule.codehaus.org>; "Andrew Perepelytsya" <aperepel@gmail.com>
Sent: Thursday, August 04, 2005 7:45 PM
Subject: Re: [mule-user] Mule and JBoss Integration


> yes i got the solution...
> the problem was that mule server(manager) was started before jndi in
Jboss,
> so i first started Jboss Server without mule rar and later on deployed my
> mule rar .
> it starts successfully ...
> now I trying to send a jms msg to this mule component.....
>
> -Poonam
>
> ----- Original Message -----
> From: "Andrew Perepelytsya" <aperepel@gmail.com>
> To: <user@mule.codehaus.org>
> Sent: Thursday, August 04, 2005 7:07 PM
> Subject: Re: [mule-user] Mule and JBoss Integration
>
>
> Poonam,
>
> >From what I see, the first item to check is the jndiDestinations
> property. If it is set to false, there can be issues with JNDI and JMS
> resource lookup.
>
> Next, try the java:/ConnectionFactory version instead of the
> ConnectionFactory.
>
> Cheers,
> Andrew
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [mule-user] Mule and JBoss Integration

sateesh
In reply to this post by Maël LAVIE-DERANDE-2
Hi All,

  I tried deploying mule-ra-1.3-rc4.rar on JBoss4.0.4 and got the below Exception in the console..

  Has any one tried 1.3 rc4 on JBoss4.0.4 ..!!!


08:41:23,934 INFO  [JkMain] Jk running ID=0 time=0/62  config=null
08:41:23,950 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started i
n 34s:413ms
08:45:38,075 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mule-ra-1.3-rc4.rar/

08:45:38,965 WARN  [ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='mule-ra-1.3-rc4.ra
r'
java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;
        at org.mule.config.ExceptionHelper.initialise(ExceptionHelper.java:111)
        at org.mule.config.ExceptionHelper.<clinit>(ExceptionHelper.java:91)
        at org.mule.umo.UMOException.initialise(UMOException.java:133)
        at org.mule.umo.UMOException.setMessage(UMOException.java:78)
        at org.mule.umo.UMOException.<init>(UMOException.java:59)
        at org.mule.MuleException.<init>(MuleException.java:46)
        at org.mule.config.ConfigurationException.<init>(ConfigurationException.java:36)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:208)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:191)
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:99)
        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy23.start(Unknown Source)
        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:345)
        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
3)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
08:45:38,980 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.jca:service=RARDeployment,name='mule-ra-1.3-rc4.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;


--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name='mule-ra-1.3-rc4.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;

Thanks
Sateesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Mule and JBoss Integration

Andrew Perepelytsya
Sateesh,

You have a duplicate commons-collections.jar in your server classpath. Chech that you have only one instance of the library, preferrably the one bundled with Mule.

Andrew


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Mule and JBoss Integration

sateesh
Hi Andrew,

  I have removed the commons-collections and restarted the Jboss and getting the following Error..

  I had a commons-collections.jar in Jboss4.0.4\server\default\deploy\jbossweb-tomcat55.sar\jsf-libs
  which i have removed..

  And in ra.xml initially i had an empty config-property-value Element <config-property-value></config-property-value>
 
  and got the Same Exception

  Then i changed it to the original one <config-property-value>mule-config.xml</config-property-value>
  and restarted JBoss and got the below Exception..!!



10:10:05,775 INFO  [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp4224jbossws-exp.war/
10:10:06,150 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar

10:10:06,368 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
10:10:11,315 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mule-ra-1.3-rc4.rar/

10:10:12,361 WARN  [ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='mule-ra-1.3-rc4.ra
r'
javax.resource.spi.ResourceAdapterInternalException: Failed to load configurations:
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:101)
        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy23.start(Unknown Source)
        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:345)
        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
3)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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:464)
        at java.lang.Thread.run(Thread.java:595)
Caused by: org.mule.config.ConfigurationException: MuleManager Failed to initialise (org.mule.config.ConfigurationExcept
ion)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:193)
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:99)
        ... 90 more
Caused by: org.mule.config.ConfigurationException: MuleManager Failed to initialise
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:208)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:191)
        ... 91 more
Caused by: java.lang.NullPointerException
        at org.mule.config.builders.MuleXmlConfigurationBuilder.setContainerProperties(MuleXmlConfigurationBuilder.java:
226)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:201)
        ... 92 more
10:10:12,439 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
10:10:12,439 INFO  [QuartzResourceAdapter] start quartz!!!
10:10:12,533 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
10:10:12,548 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
10:10:12,548 INFO  [RAMJobStore] RAMJobStore initialized.
10:10:12,548 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource fil
e in Quartz package: 'quartz.properties'
10:10:12,564 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
10:10:12,564 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
10:10:13,453 INFO  [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultD
S' to JNDI name 'java:DefaultDS'
10:10:13,656 WARN  [JBossManagedConnectionPool] Throwable while trying to match ManagedConnection, destroying connection
: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@15dc721[state=NORMAL mc=org.jboss.r
esource.adapter.jdbc.local.LocalManagedConnection@377e2a handles=0 lastUse=1156169413641 permit=false trackByTx=false mc
p=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$PoolBySubject@13c1b69 context=org.jboss.resource.conne
ctionmanager.InternalManagedConnectionPool@12bbe6b xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$L
ocalXAResource@e28a61 txSync=null]
java.lang.NoSuchMethodError: org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getValidateOnMatch()Z
        at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConne
ctionFactory.java:198)
        at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPoo
l.java:206)
        at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnection
Pool.java:577)
        at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:
339)
        at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:301)
        at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:39
2)
        at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseCon
nectionManager2.java:836)
        at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
        at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.<init>(JDBCStateManager.java:498)
        at org.jboss.mq.sm.jdbc.JDBCStateManager.initDB(JDBCStateManager.java:415)
        at org.jboss.mq.sm.jdbc.JDBCStateManager.startService(JDBCStateManager.java:378)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy25.start(Unknown Source)
        at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
3)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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:464)
        at java.lang.Thread.run(Thread.java:595)

Thanks
Sateesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Mule and JBoss Integration

Andrew Perepelytsya
Well, it's not the same.

You have 2 errors in your stacktrace:
  1. NPE in MuleXmlConfig builder , it's related to null container reference. Post your Mule config to know more.
  2. NoSuchMethod error in JBoss's RA, have no idea what's going on there, but check if there are any duplicate resource adapter jars in your server.
Andrew


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Mule and JBoss Integration

George Chen
In reply to this post by Andrew Perepelytsya
Hi, Andrew,

I am wondering where I can find some detailed instructions on integrating mule with jboss, for example, for the simple echo example?
I tried 1.2 with jboss 4.0.4 with no luck.  I also tried 1.3-rc4 with jboss 4.0.4 with the echo example and ended up getting something quite like Sateesh's first post.  Here are the steps I used, please tell what I am missing.

1) donwload the mule-ra-1.3-rc4.rar.zip at: http://dist.codehaus.org/mule/rars/ 
2) unzip the rar in a folder with folder name ending with .rar, in my case, mule.rar
3) place a version of echo-mule-config.xml (see below) at the top level of mule.rar
4) I also put all  mule 1.3-rc4 jars  from the lib and lib/opt folders in mule.rar folder, in order to resolve the no class found exception. ( I am not sure about this step.  It seems the default mule-ra-1.3-rc4.rar has many classes missing.  I also remembered reading from somewhere that jboss uses a flat class loading model to avoid loading duplicated classes, not 100% sure though.)
5) edit the ra.xml under META-INF under the folder created in 2),
   to specify  echo-mule-config.xml to be loaded.
6) start jboss
7) drop the mule.rar in jboss at server\default\deploy folder.



This is my echo-mule-config.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mule-configuration PUBLIC "-//SymphonySoft //DTD mule-configuration XML V1.0//EN"
                                "http://www.symphonysoft.com/dtds/mule/mule-configuration.dtd">

<mule-configuration id="Mule_Echo_Sample" version="1.0">

    <description>
    This is a simple component example that demostrates how to expose a component over multiple transports.

    To invoke the EchoUMO component as a webservice hit the following URL -
    http://localhost:8081/services/EchoUMO?method=echo&param=Is there an echo?
    (remember to replace the '&' with an ampersand)

    To view the WSDL for the EchoUMO service go to -
    http://localhost:8081/services/EchoUMO?wsdl
    </description>

   
   
     <transformers>
        <transformer name="HttpRequestToSoapRequest" className="org.mule.providers.soap.transformers.HttpRequestToSoapRequest"/>
    </transformers>

   
    <model name="echoSample">
       
        <mule-descriptor name="EchoUMO" implementation="org.mule.components.simple.EchoComponent">
           
            <inbound-router>
           
                <endpoint address="axis:http://localhost:8081/services" transformers="HttpRequestToSoapRequest" />               
            </inbound-router>
           
           
           
        </mule-descriptor>
    </model>
</mule-configuration>


This is the message from jboss console:

22:12:17,803 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 10s:235ms
22:12:57,193 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mule.rar/
22:12:58,146 INFO  [MuleManager] Transformer HttpRequestToSoapRequest has been initialised successfully
22:12:58,224 INFO  [TransformerReference] Setting transformer: HttpRequestToSoapRequest on org.mule.impl.endpoint.MuleEndpoint.transformer
22:12:58,287 INFO  [MuleManager] Connectors have been initialised successfully
22:12:58,287 INFO  [MuleManager] Initialising agents...
22:12:58,287 INFO  [MuleManager] Agents Successfully Initialised
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,318 WARN  [ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='mule.rar'
java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;
        at org.mule.config.ExceptionHelper.initialise(ExceptionHelper.java:111)
        at org.mule.config.ExceptionHelper.<clinit>(ExceptionHelper.java:91)
        at org.mule.providers.soap.axis.AxisConnector.<clinit>(AxisConnector.java:69)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at org.mule.providers.service.ConnectorFactory.createConnector(ConnectorFactory.java:209)
        at org.mule.providers.service.ConnectorFactory.getOrCreateConnectorByProtocol(ConnectorFactory.java:296)
        at org.mule.providers.service.ConnectorFactory.getOrCreateConnectorByProtocol(ConnectorFactory.java:287)
        at org.mule.impl.ImmutableMuleEndpoint.initialise(ImmutableMuleEndpoint.java:611)
        at org.mule.impl.ImmutableMuleDescriptor.initialise(ImmutableMuleDescriptor.java:296)
        at org.mule.impl.model.AbstractComponent.initialise(AbstractComponent.java:112)
        at org.mule.impl.model.AbstractModel.initialise(AbstractModel.java:421)
        at org.mule.MuleManager.initialise(MuleManager.java:666)
        at org.mule.MuleManager.start(MuleManager.java:745)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:205)
        at org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:191)
        at org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java:99)
        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy23.start(Unknown Source)
        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:345)
        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
22:12:58,349 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError: org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;


This is really quite a long message.  Thank you in advance for your time.

George Chen




Andrew Perepelytsya wrote
Sateesh,

You have a duplicate commons-collections.jar in your server classpath. Chech
that you have only one instance of the library, preferrably the one bundled
with Mule.

Andrew
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Mule and JBoss Integration

Andrew Perepelytsya
org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map

The same problem with duplicate commons-collections.

JBoss is known for its problems with a Unified ClassLoader (UCL). Uncareful use may result in havoc :) The good news is it can be switched to a J2EE-style behavior. Don't remember the details (check their docs and forums), but I definitely remember this mode is ON by default in the 'all' server configuration.

This may reduce the number of classloading problems you are experiencing at the expense of extra server resources required.

Andrew

On 8/21/06, zgchen88 <[hidden email]> wrote:

Hi, Andrew,

I am wondering where I can find some detailed instructions on integrating
mule with jboss, for example, for the simple echo example?
I tried 1.2 with jboss 4.0.4 with no luck.  I also tried 1.3-rc4 with jboss
4.0.4 with the echo example and ended up getting something quite like
Sateesh's first post.  Here are the steps I used, please tell what I am
missing.

1) donwload the mule-ra-1.3-rc4.rar.zip at:
http://dist.codehaus.org/mule/rars/
2) unzip the rar in a folder with folder name ending with .rar, in my case,
mule.rar
3) place a version of echo-mule-config.xml (see below) at the top level of
mule.rar
4) I also put all  mule 1.3-rc4 jars  from the lib and lib/opt folders in
mule.rar folder, in order to resolve the no class found exception. ( I am
not sure about this step.  It seems the default mule-ra-1.3-rc4.rar has many
classes missing.  I also remembered reading from somewhere that jboss uses a
flat class loading model to avoid loading duplicated classes, not 100% sure
though.)
5) edit the ra.xml under META-INF under the folder created in 2),
   to specify  echo-mule-config.xml to be loaded.
6) start jboss
7) drop the mule.rar in jboss at server\default\deploy folder.



This is my echo-mule-config.xml :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mule-configuration PUBLIC "-//SymphonySoft //DTD
mule-configuration XML V1.0//EN"

" http://www.symphonysoft.com/dtds/mule/mule-configuration.dtd">

<mule-configuration id="Mule_Echo_Sample" version="1.0">

    <description>
    This is a simple component example that demostrates how to expose a
component over multiple transports.

    To invoke the EchoUMO component as a webservice hit the following URL -
    http://localhost:8081/services/EchoUMO?method=echo&param=Is there an
echo?
    (remember to replace the '&' with an ampersand)

    To view the WSDL for the EchoUMO service go to -
    http://localhost:8081/services/EchoUMO?wsdl
    </description>

    <!--
        The system stream connector is used to send and receive information
via the
        System.in and System.out. Note this connector is only really useful
for testing
        purposes.
        promptMessage - is what is written to the console
        messageDelayTime - is the time in milliseconds before the user is
prompted again.
        These properties are set as bean properties on the connector.
    -->
    <!--
    <connector name="SystemStreamConnector"
className="org.mule.providers.stream.SystemStreamConnector">
        <properties>
            <property name="promptMessage" value="Please enter something:
"/>
            <property name="messageDelayTime" value="1000"/>
        </properties>
    </connector>
-->
     <transformers>
        <transformer name="HttpRequestToSoapRequest"
className="org.mule.providers.soap.transformers.HttpRequestToSoapRequest"/>
    </transformers>

    <!--
        The Mule model initialises and manages your UMO components
    -->
    <model name="echoSample">
        <!--
            A Mule descriptor defines all the necessary information about
how your components will
            interact with the framework, other components in the system and
external sources.
            Please refer to the Configuration Guide for a full description
of all the parameters.
        -->
        <mule-descriptor name="EchoUMO"
implementation=" org.mule.components.simple.EchoComponent">
            <!-- any number of endpoints can be added to an inbound router
-->
            <inbound-router>
            <!--
                <endpoint address="stream://System.in"/>
                -->
                <endpoint address="axis:http://localhost:8081/services"
transformers="HttpRequestToSoapRequest" />
            </inbound-router>
            <!-- An outbound router can have one or more router
configurations
            that can be invoked depending on business rules, message
contents, headers
            or ant other criteria.
            The OutboundPassthroughRouter is a router that automically sends
every
            message it receives -->

            <!--
            <outbound-router>
                <router
className="org.mule.routing.outbound.OutboundPassThroughRouter">
                    <endpoint address="stream://System.out"/>
                </router>
            </outbound-router>
            -->
        </mule-descriptor>
    </model>
</mule-configuration>


This is the message from jboss console:

22:12:17,803 INFO  [Server] JBoss (MX MicroKernel) [ 4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 10s:235ms
22:12:57,193 INFO  [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/mule.rar/
22:12:58,146 INFO  [MuleManager] Transformer HttpRequestToSoapRequest has
been initialised successfully
22:12:58,224 INFO  [TransformerReference] Setting transformer:
HttpRequestToSoapRequest on org.mule.impl.endpoint.MuleEndpoint.transformer
22:12:58,287 INFO  [MuleManager] Connectors have been initialised
successfully
22:12:58,287 INFO  [MuleManager] Initialising agents...
22:12:58,287 INFO  [MuleManager] Agents Successfully Initialised
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising
exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising
exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,287 INFO  [DefaultComponentExceptionStrategy] Initialising
exception listener: org.mule.impl.DefaultComponentExceptionStrategy@1829c6b
22:12:58,318 WARN  [ServiceController] Problem starting service
jboss.jca:service=RARDeployment,name='mule.rar'
java.lang.NoSuchMethodError:
org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;
        at
org.mule.config.ExceptionHelper.initialise (ExceptionHelper.java:111)
        at org.mule.config.ExceptionHelper.<clinit>(ExceptionHelper.java:91)
        at
org.mule.providers.soap.axis.AxisConnector.<clinit>(AxisConnector.java:69)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
        at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance (DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance (Class.java:303)
        at
org.mule.providers.service.ConnectorFactory.createConnector(ConnectorFactory.java:209)
        at
org.mule.providers.service.ConnectorFactory.getOrCreateConnectorByProtocol(ConnectorFactory.java :296)
        at
org.mule.providers.service.ConnectorFactory.getOrCreateConnectorByProtocol(ConnectorFactory.java:287)
        at
org.mule.impl.ImmutableMuleEndpoint.initialise(ImmutableMuleEndpoint.java:611)
        at
org.mule.impl.ImmutableMuleDescriptor.initialise(ImmutableMuleDescriptor.java:296)
        at
org.mule.impl.model.AbstractComponent.initialise(AbstractComponent.java:112)
        at
org.mule.impl.model.AbstractModel.initialise (AbstractModel.java:421)
        at org.mule.MuleManager.initialise(MuleManager.java:666)
        at org.mule.MuleManager.start(MuleManager.java:745)
        at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure (MuleXmlConfigurationBuilder.java:205)
        at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:191)
        at
org.mule.ra.MuleResourceAdapter.start(MuleResourceAdapter.java :99)
        at
org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109)
        at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at
org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
        at
org.jboss.mx.server.RawDynamicInvoker.invoke (RawDynamicInvoker.java:164)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at
org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy23.start(Unknown Source)
        at
org.jboss.deployment.SimpleSubDeployerSupport.startService (SimpleSubDeployerSupport.java:345)
        at
org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
        at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke (ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke (Invocation.java:88)
        at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
        at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at
org.jboss.deployment.scanner.URLDeploymentScanner.scan (URLDeploymentScanner.java:634)
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop (AbstractDeploymentScanner.java:274)
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
22:12:58,349 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError:
org.apache.commons.collections.MapUtils.invertMap (Ljava/util/Map;)Ljava/util/Map;

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name='mule.rar'
  State: FAILED
  Reason: java.lang.NoSuchMethodError:
org.apache.commons.collections.MapUtils.invertMap(Ljava/util/Map;)Ljava/util/Map;


This is really quite a long message.  Thank you in advance for your time.

George Chen





Andrew Perepelytsya wrote:
>
> Sateesh,
>
> You have a duplicate commons-collections.jar in your server classpath.
> Chech
> that you have only one instance of the library, preferrably the one
> bundled
> with Mule.
>
> Andrew
>
>

--
View this message in context: http://www.nabble.com/-mule-user--Mule-and-JBoss-Integration-tf180681.html#a5918596
Sent from the Mule - User forum at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[ANN] VTD-XML 1.7

jimmy Zhang-2
In reply to this post by George Chen
XimpleWare released Version 1.7 of VTD-XML, the next generation XML
parser that goes beyond DOM and SAX, under GPL. VTD-XML is getting
faster, leaner, more stable and complete with this release. New features
included in this releases are:

* Additional XPath functions support
* Union Expression
* A rewritten VTDNav implementation
* Various bug fixes in VTDGen and XPath evaluation

Please visit http://vtd-xml.sf.net for the latest release.

 
For further reading, please refer to the following articles:
a.. Simplify XML Processing with VTD-XML
a.. Cut, Paste, Assemble and Split XML files with VTD-XML
a.. XML on a Chip
a.. Process Large XML Files with VTD-XML
a.. The performance Woe of Binary XML
a.. VTD-XML: The Next Generation XML Parser



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Loading...