Ah ejb3-rar.rar is the ejb3 demo rar I wrote.
Service
"jboss.deployment.unit."mdb-example.ejb3".component.EJB3MDBExample.CREATE"
(class org.jboss.as.ee.component.ComponentCreateService) mode ACTIVE state DOWN (parent:
jboss.deployment.unit."mdb-example.ejb3".INSTALL) (dependencies: hornetqadapter,
jboss.ejb.utilities) (has missing dependency)
Why would there be a dependency on 'hornetqadapter'?
Basically if there is no @ResourceAdapter specified, the jms subsystem
should put it its own ServiceName to its Service<ResourceAdapter> in the
MDBDescription.
Carlo
On 04/13/2011 09:36 AM, Howard Gao wrote:
Thanks Carlo. I've talked to Jaikiran and Stuart on #jboss-as7. I
got
some clue on the issue that I can continue with.
I don't know where is ejb3-rar.rar.
Howard
On 04/13/2011 03:25 PM, Carlo de Wolf wrote:
> Basic MDB support is in there. As you can see it deploys a MDB.
> The ejb3 demo also deploys a rar and a MDB (cd demos; mvn
> -Dexample=ejb3 package).
>
> Try running
https://github.com/wolfc/jboss-as-divine-spells after
> starting AS. It'll analyze the missing dependencies and give a more
> dense report. (If there is a START_FAILED, you might need MSC-84.)
>
> What Jaikiran means is, where is ejb3-rar.rar source code?
>
> Are you on IRC somewhere?
>
> Carlo
>
> On 04/13/2011 08:40 AM, Howard Gao wrote:
>> On 04/13/2011 02:36 PM, Jaikiran Pai wrote:
>>> 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.
>> Ok, I'll try JCconsole.
>>>> 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.
>> I don't much about git branch. I just follow the steps in the link
>>
>>
http://community.jboss.org/wiki/HackingonAS7
>>
>> And I haven't changed any code.
>>
>>> -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(a)lists.jboss.org
>>>>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>