[jboss-as7-dev] Problem deploying an EJB3 MDB

[Jaikiran Pai]

On Wednesday 13 April 2011 12:02 PM, Howard Gao wrote:
> Thanks Jaikiran. I'm the one handling this Jira. :)
Ah ok! I didn't notice that it was you who asked the question :)
>
> I'm trying to figure out what need to be done about this. The first step
> is to get the hornetq RA activated in as7. So I added a 'dummy' resource
> adapter and then deploy a simple mdb,
> I'm expecting to see some error messages like 'HornetQ Adapter class not
> founded' so I can get some clue where to do next.
The service dependencies that are being reported as missing can be 
tracked via the jboss-mc MBeans exposed via JConsole.
>
> Do you have any idea where I should look into ?
If you have some git branch where you are trying to integrate this, then 
I can clone it and take a look at it locally to see what's going on. It 
might be some EJB3 integration too.

-Jaikiran
>
> Thanks
> Howard
>
>
> On 04/13/2011 02:23 PM, Jaikiran Pai wrote:
>> EJB3 MDB support isn't yet available in AS7 upstream. It's waiting on
>> https://issues.jboss.org/browse/JBAS-9122
>>
>> -Jaikiran
>> On Wednesday 13 April 2011 11:50 AM, Howard Gao wrote:
>>> Need help on this issue, thanks.
>>>
>>> Synopsis:
>>>
>>> A Fresh AS7 build, deploy a simple EJB3 MDB with following annotation
>>>
>>> @MessageDriven(messageListenerInterface = EJB3MDBExample.class)
>>> @ResourceAdapter("ejb3-rar.rar")
>>>
>>> Starting AS7 standalone, the depoly failed but no error messages from
>>> the console, only one line warning:
>>>
>>> 13:47:48,936 WARN  [org.jboss.vfs] (MSC service thread 1-11) VFS was
>>> unable to set the URLStreamHandlerFactory.  This will have unpredictable
>>> results
>>>
>>> I'm not sure this is relevant. Restarting AS7 again, it spits out
>>>
>>> 14:14:13,450 ERROR [org.jboss.as] (MSC service thread 1-2) JBoss AS
>>> 7.0.0.Beta3-SNAPSHOT "TBD" started (with errors) in 2113ms - Started 112
>>> of 148 services (10 services failed or missing dependencies, 26 services
>>> are passive or on-demand)
>>>         Services missing dependencies:
>>>             service
>>> jboss.deployment.unit."mdb-example.ejb3".component.EJB3MDBExample.CREATE
>>>             service
>>> jboss.deployment.unit."mdb-example.ejb3".component.EJB3MDBExample.NAMESPACE
>>>             service
>>> jboss.deployment.unit."mdb-example.ejb3".component.EJB3MDBExample.START
>>>             service
>>> jboss.deployment.unit."mdb-example.ejb3".component.EJB3MDBExample.VIEW."javax.jms.MessageListener"
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample.EJBContext
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample.TransactionSynchronizationRegistry
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample.UserTransaction
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample.Validator
>>>             service
>>> jboss.naming.context.java.comp."mdb-example.ejb3"."mdb-example.ejb3".EJB3MDBExample.ValidatorFactory
>>>
>>> I don't understand what that mean. Was it that I need to add some services?
>>>
>>> Howard
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev