Use of "mappedName" attribute with @MessageDriven EJB3.0

Hi there,

I am learning EJB3.0. I have written a MDB using @MessageDriven annotation and succeeded too. But, I am little bit confused about the attribute "mappedName". Is this same like jndi name we give with @ActivationConfigProperty in activationConfig attribute.

What exactly "mappedName" would do? Can you guys please explain this?

Thanks,
Guru

What exactly "mappedName" would do? Can you guys please explain this?

From here,

The mappedName attribute specifies the JNDI name for the bean instance.

Hi,

Does mappedName attribute work with @MessageDriven EJB3.0 annotation with jboss 5.0 AS ?

it seems to be not working because I have to add a property like this so that he knows what queue to use :

I found a Jira ticket that look like to my problem (@EJB in JSF ignores mappedName) https://jira.jboss.org/jira/browse/JBAS-4399

PS : Jaikiran Pai the link here is no more good

igor bolsovitch wrote:

Does mappedName attribute work with @MessageDriven EJB3.0 annotation with jboss 5.0 AS ?

No it doesn't. The mappedName in JBoss is considered to be the JNDI name of the bean. Since MDBs don't get bound to the JNDI for lookup, the mappedName isn't used for MDBs.

igor bolsovitch wrote:
it seems to be not working because I have to add a property like this so that he knows what queue to use :

@ActivationConfigProperty(propertyName = &quot;destination&quot;, propertyValue = &quot;queue/orderQueue&quot;),

That's the correct way.

igor bolsovitch wrote:
PS : Jaikiran Pai the link here is no more good

Unfortunately, the trailblazer is no longer available. The EJB3 tutorials for JBoss AS5 can now be found here

igor bolsovitch wrote:

Does mappedName attribute work with @MessageDriven EJB3.0 annotation with jboss 5.0 AS ?

No it doesn't. The mappedName in JBoss is considered to be the JNDI name of the bean. Since MDBs don't get bound to the JNDI for lookup, the mappedName isn't used for MDBs.

+1 Glassfish

igor bolsovitch wrote:

+1 Glassfish

Sorry, i don't get what you mean here

Just because in glassfish it works

... as expected:

Annotation Type MessageDriven

Optional Element Summary
...

mappedName
A product specific name(e.g. global JNDI name of a queue) that this message-driven bean should be mapped to.

igor bolsovitch wrote:Just because in glassfish it works ... as expected:

Annotation Type MessageDriven

Optional Element Summary
...

mappedName
A product specific name(e.g. global JNDI name of a queue) that this message-driven bean should be mapped to.

You just posted only a part of the javadocs

The more important part of the javadocs reads as follows:

...Application servers are not required to support any particular form or type of mapped name, nor the ability to use mapped names. The mapped name is product-dependent and often installation-dependent. No use of a mapped name is portable.

Mea culpa,

It was a part I found in the top table (Summary)

I have serious problem with Jboss messaging.

I have 2 EJB

Stateless : OrderBean
and
MDB : EmailSenderBean

The first (OrderBean) has to send message to the queue orderQueue.
The second (EmailSenderBean) should realize that a new message has come (method onMessage) and should execute a buisiness method (Send an E-mail)

But it doesn't work : It seems that EmailSenderBean does not listen, because when I deploy my application I see this error in jboss:

16:38:01,090 INFO  [EJBContainer] STARTED EJB: com.newenergy.server.service.email.EmailSenderBean ejbName: EmailSenderB
16:38:01,128 WARN  [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1e8671c(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1e4926a destination=queue/orderQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.naming.NameNotFoundException: DLQ not bound
	at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
	at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
	at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
	at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
	at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at org.jboss.util.naming.Util.lookup(Util.java:222)
	at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106)
	at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82)
	at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
	at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)
	at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)
	at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)

Is that normal that he logs about the DLQ while in MDB I have :

Each queue has a Dead letter queue. By default it is queue/DLQ which is provided by default in JBoss. The WARN message indicates that the DLQ is not being found. Did you do any changes to the AS?