OC4J and Message Driven Bean

Hi I suppose OC4J doesn't create a MessageDrivenContext, that is
a 'com.evermind.server.ejb.MessageDrivenHome'(=message_driven_con
text.toString() ).
The code is :
message_driven_context.setRollbackOnly();
and the errors are:
1)java.lang.IllegalStateException: MessageDriven beans have no
EJBHome
2)java.lang.IllegalStateException: Not active or marked for
rollback
I don't know what to do, because I think these are OC4J level
errors.
I'd like to create a transactional Context, so that if the ejb
doesn't succeed to do its task, the message'll be put in the
queue again and so on....
Thanks a lot. Bye

I had the same problem and have been told it is a bug. It may have been fixed in the production version of OC4J, I havent tried it out yet.
-Isaac

Similar Messages

My problem in Weblogic and Message Driven Bean for Topic

Hello to all
I used this page (http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
for setup JMS Server, Queue, Connection Factory on Weblogic Server
and I created a Message Driven Bean ,I used those Queue , and all things was OK
But I wanted to setup a Topic and use it in this manner
I created a Topic like previous steps for setup Queue
(http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
Except in Step 3 ,I selected Topic instead of Queue
then I created a Message Driven Bean in JDeveloper , my Message Driven Bean is like this:
@MessageDriven(mappedName = "jndi.testTopic")
<p>
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
</p>
When I deploy the Application , Weblogic shows me this error:
+<Aug 30, 2011 11:32:28 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: aliJMS1_MessageDrivenEJBBean is unable to connect to th+
e JMS destination: jndi.testTopic. The Error was:
+[EJB:011011]The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: jndi.testTopic. However, the object with+
the JNDI name: jndi.testTopic is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).>
And when I send message to the topic The Message Dirven Bean dosen't work
But when I create an ordinary Java application like this (it uses that Tpoic) :
import java.io.*;
import java.util.*;
import javax.transaction.*;
import javax.naming.*;
import javax.jms.*;
public class TopicReceive implements MessageListener
    public final static String JNDI_FACTORY =
        "weblogic.jndi.WLInitialContextFactory";
    public final static String JMS_FACTORY =
        "jndi.testConnectionFactory";
    public final static String TOPIC = "jndi.testTopic";
    private TopicConnectionFactory tconFactory;
    private TopicConnection tcon;
    private TopicSession tsession;
    private TopicSubscriber tsubscriber;
    private Topic topic;
    private boolean quit = false;
    public void onMessage(Message msg) {
        try {
            String msgText;
            if (msg instanceof TextMessage) {
                msgText = ((TextMessage)msg).getText();
            } else {
                msgText = msg.toString();
            System.out.println("JMS Message Received: " + msgText);
            if (msgText.equalsIgnoreCase("quit")) {
                synchronized (this) {
                    quit = true;
                    this.notifyAll();
        } catch (JMSException jmse) {
            jmse.printStackTrace();
    public void init(Context ctx, String topicName) throws NamingException,
                                                           JMSException {
        tconFactory = (TopicConnectionFactory)ctx.lookup(JMS_FACTORY);
        tcon = tconFactory.createTopicConnection();
        tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        topic = (Topic)ctx.lookup(topicName);
        tsubscriber = tsession.createSubscriber(topic);
        tsubscriber.setMessageListener(this);
        tcon.start();
    public void close() throws JMSException {
        tsubscriber.close();
        tsession.close();
        tcon.close();
    public static void main(String[] args) throws Exception {
        InitialContext ic = getInitialContext("t3://127.0.0.1:7001");
        TopicReceive tr = new TopicReceive();
        tr.init(ic, TOPIC);
        System.out.println("JMS Ready To Receive Messages (To quit, send a \"quit\" message).");
        synchronized (tr) {
            while (!tr.quit) {
                try {
                    tr.wait();
                } catch (InterruptedException ie) {
        tr.close();
    private static InitialContext getInitialContext(String url) throws NamingException {
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
        env.put(Context.PROVIDER_URL, url);
        env.put("weblogic.jndi.createIntermediateContexts", "true");
        return new InitialContext(env);
It's OK and shows messages When I send message to the Topic
Now I want know why the Message Driven Bean doesn't work for those Topic
I want create a Message Driven Bean for Topic in the same way I created for Queue
I don't know what is problem , please advice me
Thanks

Could you try adding a activationconfig to the message-driven bean, for example,
@MessageDriven(mappedName = "jndi.testTopic", activationConfig = {
        @ActivationConfigProperty(propertyName = "destinationName", propertyValue = "jndi.testTopic"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic")
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
}

Getting an Error in Deploying JMS and Message Driven Beans

HI ,
When I m trying to deploy my application It is giving the following exception cn any one plz help ..
I think m not writing correct XML so can any one plz give me any help regarding How to write XML..
0,333 ERROR [JMSContainerInvoker] Could not set ExceptionListener to null
ms.IllegalStateException: The connection is closed
at org.jboss.mq.Connection.setExceptionListener(Connection.java:559)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStopDelivery(JMSContainerInvoker.java:973)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1447)
at java.lang.Thread.run(Thread.java:595)
0,333 ERROR [JMSContainerInvoker] Could not stop JMS connection
ms.IllegalStateException: The connection is closed
at org.jboss.mq.Connection.stop(Connection.java:694)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStopDelivery(JMSContainerInvoker.java:987)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1447)
at java.lang.Thread.run(Thread.java:595)

This issue is resolved now. All i have to do to turn off the Proxy Server Settings from my Jdeveloper. I turned off the settings and deployment went well.
Thanks to Prasen for the solution.

How to send message from Message Driven Bean to JMS client?

In my project I have JMS client, two QueueConnectionFactory and Message Driven Bean. Client send message to MDB through the first QueueConnectionFactory , in one's turn MDB send message to client through the second Queue Connection Factory . I already config my Sun AppServer for sending message in one way, and sending message from MDB to the second QueueConnectionFactory. But on my Client there is an error : �JNDI lookup failed: javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/MyQueue2� (jms/MyQueue2 � this is the name of my Queue). So it couldn't get this message.
P.S.
Thank you for help!!!

What is the name of the second queue?is the connection factory on the local?Yes the connection factory is on the local. The name of my first queue is jms/MYQueue and the name of another one is jms/MyQueue2.

Messenger service using message driven beans

I need to implement a implement a messenger service. (using Messaging server, Message Queue, Message Clients and Message Driven Beans)
using netbeans 5.5
it should develop using EJB 3.0 architeture.
Can pls tell...how should i start this.(Basic steps of doing this)
Where should we write the Messaging server.(in a EJB 3.0 application...Is it?)
Any tutorial regrading this....!

EJBs and Message Driven Part.
what should i develop first. Messaging server OR Message Queue
How can i develop the Messaging Server. Do i need to use Message driven beans there?
Message was edited by:
jugp

Message Driven Bean and transaction handling

We are using container managed transactions with MDB's running on OC4J version 10.1.2. We have two database serveres, both running Oracle 10g.
The MDB consume messages from the AQ-database through JMS (connected to a JDBC datasource registered as "jdbc/OracleAQDS").
The MDB onMessage() code update the second database, using a JDBC datasource registered as "jdbc/OracleDBDS".
We need atomic behaviour - if the MDB enforce a roll-back we want the updates aginst the second database to be rolled-back as well.
(1) Should we use XA-datasources since AQ and DB runs on two different servers or do the OC4J container "magically" provide two-phase-commit for us?
(2) If the MDB does a roll-back we would like to add an error record to a database table. Can we configure a third datasource and prevent if from beeing part of the container managed MDB roll-back?
(3) When the MDB force a roll-back, is there some way for us to override the retry-delay in our Java code? If we catch certain errors during processing in onMessage we know that it is not necessary to retry for at least one hour (while less severe errors should be retried in just seconds).

{color:#008000}Hi Friends,
Thought of updating the answers for my questions in case somebody else would find it helpful.
{color}
{color:#999999}{color:#00ccff}I'm trying to make message driven bean and use the OnListener method.
But since I'm doing this for the first time I have very limited knowledge.
The following are my doubts :
1. Should I have a main function while using the MDB?{color}
{color:#008000} There is no need for any main function.{color}
{color:#00ccff}2. Is it mandatory to have JNDI setup done?
{color} {color}{color:#008000} There is no need for any JNDI setup done. But you need to configure the details on the
Websphere by creating valid entries inside Resources namely -
Queue Connection Factory, Queues and Listener Ports under the server.
Thanks,
Arun Prithviraj{color}

WebLogic 10 and EJB 3.0 for Message Driven Bean

Hi,
I am trying to deploy Message Driven Bean using EJB3.0 on weblogic 10. I am using annotations and don't want to use deployment descriptors.
The Bean class:
CalculatorBean.java
import javax.ejb.*;
import javax.jms.*;
import java.sql.Timestamp;
import java.util.StringTokenizer;
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/mdb")
public class CalculatorBean implements MessageListener {
public void onMessage (Message msg) {
TextMessage tmsg=null;
try {
if (msg instanceof TextMessage) {
tmsg = (TextMessage) msg;
System.out.println
("MESSAGE BEAN1: Message received: "
+ tmsg.getText());
} else {
System.out.println
("Message of wrong type1: "
+ msg.getClass().getName());
catch (JMSException e) {
e.printStackTrace();
catch (Throwable te) {
te.printStackTrace();
My client:
import javax.naming.*;
import javax.naming.InitialContext;
import java.text.*;
import javax.jms.*;
public class MsgClient {
public static void main(String args[])
QueueConnection cnn=null;
QueueSender sender=null;
QueueSession sess=null;
Queue queue=null;
try {
java.util.Properties p = new java.util.Properties();
p.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
p.put("java.naming.provider.url","t3://10.6.74.79:7001");
Context ctx=new InitialContext(p);
//InitialContext ctx=new InitialContext(p);
queue = (Queue)ctx.lookup("queue/mdb");
QueueConnectionFactory factory = (QueueConnectionFactory)ctx.lookup("ConnectionFactory");
cnn = factory.createQueueConnection();
sess= cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
sender = sess.createSender(queue);
TextMessage message = sess.createTextMessage();
message.setText("This is message by Gurumurthy" );
System.out.println("Sending message: " +message.getText());
sender.send(message);
sess.close();
catch (Exception e)
e.printStackTrace();
I am compiling and creating jar file for this class. Then I am creating a .ear file for this.
The meta-inf/application.xml contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com /xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
<display-name>MDBWorking1</display-name>
<description>Application description</description>
<module>
<ejb>MDBWorking1.jar</ejb>
</module>
</application>
I don't want to use deployment descriptor (ejb-jar.xml or weblogic-ejb-jar-xml), because I want to utilize the annotation feature of EJB3.0
So, after creating the .ear file for this, and try to deploy on weblogic 10, I get the following error:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(MDBWorking1.jar) Unable to deploy EJB: CalculatorBean from MDBWorking1.jar: [EJB:011113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
Substituted for missing class [EJB - 11113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
How to solve this?
Note:
I don't want to use Deployment Descriptor and all I want to use is EJB3.0's annotation feature.
Thanks,
Guru

Dear gurubbc,
I don't know if it still matters to you but you can use the javax.ejb.MessageDriven annotation to point your bean on your queue. I had the same issue like you but i could not solve it properly by switchihg to weblogic.ejb.MessageDriven.
Use the following annotation and it should work out:
@MessageDriven
(mappedName = "queue/mdb",
name = "CalculatorBean",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
Here you can see that the mappedName is the JNDI name of the queue you are trying to connect to. The name is the name for your Bean, and the only property passed is the destination type.
Hope this helps.
Cheers,
Istvan

Message Driven Bean and Distributed transaction

Hi ALL
I am developing an asynchronous application using MDB. My application flow is as follows:
1. From MDB onMessage i am calling a method MethodA that
a. calls a simple pojo1 where I am getting a Connection on XA enable datasource1 and executing Stored Procedure1 of DatabaseSchema1.
b. In that pojo without committing m closing the connection and coming back in MethodA.
c. Again from MethodA m calling a different pojo2 where I am getting a new Connection on XA enable datasource2 and executing Stored Procedure2 of
DatabaseSchema1. In this pojo also without committing m closing the connection and coming back in MethodA.
d. Again from MethodA m calling pojo1 where I am getting a new Connection on XA enable datasource1 and executing a different function of Stored Procedure1 of DatabaseSchema1.
Public class MDB{
Public void onMessage(��.)
Try{
Method1();
Catch(Exception x)
mdbcontext.setRollbackOnly();
Private void MethodA()
Call pojo1;
Call pojo2
Pojo1
Public void CallSP1()
Get connection from Datasource1 (shema1,user1, pwd1);
Call sp1();
//return without commit;
Pojo2
Public void CallSP2()
Get connection from Datasource2 (shema1,user2, pwd2);
Call sp2();
//return without commit;
SP1:
Insert table1
Savepoint 1
Insert into Table1
Rollback to 1
Insert a row
End SP1 (without commit)
SP2:
Insert table2
Savepoint 2
Update table2
Rollback to 2
Insert table2
End SP2 (without commit)
In ejb-jar.xml
Transaction type is Container
Transaction attribute is Required for all
Now problem is:
Case 1: success case when no exception is there at Java layer
SP1 works fine I mean there is only 2 inserts in Table 1
But In SP2 there are 3 inserts
Case 2: if an exception comes at Java layer
SP1 is fine
Rollback is not happening in SP2
In ejb-jar.xml transaction attributes is Required for all methods and transaction type is Container.
Backend is Oracle 10g and init.xa has already been run on that.
Will be very obliged if can have a single hint of the problem.
Both datasource are XA enable
Backend is Oracle 10g
Application server is WAS 6.0
Queue is WAS MQ 6.0
Thanks

{color:#008000}Hi Friends,
Thought of updating the answers for my questions in case somebody else would find it helpful.
{color}
{color:#999999}{color:#00ccff}I'm trying to make message driven bean and use the OnListener method.
But since I'm doing this for the first time I have very limited knowledge.
The following are my doubts :
1. Should I have a main function while using the MDB?{color}
{color:#008000} There is no need for any main function.{color}
{color:#00ccff}2. Is it mandatory to have JNDI setup done?
{color} {color}{color:#008000} There is no need for any JNDI setup done. But you need to configure the details on the
Websphere by creating valid entries inside Resources namely -
Queue Connection Factory, Queues and Listener Ports under the server.
Thanks,
Arun Prithviraj{color}

Message driven bean and JDBC Pool

          I am working with weblogic 7.0
          I have created a message driven bean the receives messages and store them in the
          database.
          for performance issue I have put the (SQL)Connection and a preparedStatement in
          the ejbCreate() method ...and I close them in the ejbRemove() method...but I notice
          that the ejbRemove dose not called ... even when I restart the weblogic7.0
          I notice also that when I deploy the the Message driven bean ...it consume a number
          of connections equals the number of instances created by weblogic.
          if I redeploy the message driven bean ...the weblogic consume anthor connections
          without free up the previous connections.
          thank you for any help


          Hi,
          EjbRemove will never be called for a message driven bean as it follows the lifecycle
          of a StatlessSession.
          http://e-docs.bea.com/wls/docs61/ejb/EJB_environment.html#1039510
          The container will call EJBRemove only when it gets a RemoteRuntimeException and
          has to recycle the bean.
          -Vimala Ranganathan
          "eyad" <[email protected]> wrote:
          >
          >I am working with weblogic 7.0
          >
          >I have created a message driven bean the receives messages and store
          >them in the
          >database.
          >for performance issue I have put the (SQL)Connection and a preparedStatement
          >in
          >the ejbCreate() method ...and I close them in the ejbRemove() method...but
          >I notice
          >that the ejbRemove dose not called ... even when I restart the weblogic7.0
          >
          >I notice also that when I deploy the the Message driven bean ...it consume
          >a number
          >of connections equals the number of instances created by weblogic.
          >if I redeploy the message driven bean ...the weblogic consume anthor
          >connections
          >without free up the previous connections.
          >thank you for any help
          >

Message Driven Beans: how to receive and send in a single session?

Hello
How to receive and send JMS messages in a message driven bean using a single session?
Thanks.

Are you referring to writing code within the onMessage method itself to receive JMS messages?
If so, that is not a pattern that is recommended, especially not in the case of a blocking JMS
receieve. If you must write an explicit JMS receive within an EJB component it's best to use
a "check the queue" approach where you give a very small timeout for the receive. That way
if the message is there it will be returned but if not the call will not block.
You'll also need to take the transactional settings of the onMessage method into account.
If your are sending a message and then waiting for a response, those two actions can
not be done within the same global transaction. For that, you'll need to either use
BMT and perform each in its own transaction or just not use global transactions at all,
in which case each send and receive operation will be atomic.
--ken

WLS Cluster with Message Driven Beans and MQSeries on more than one Host

          With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
          a MDB can be
          configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
          is started at the same Host that runs the WLS Server too.
          And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
          In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
          Queuemanager.
          A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
          of this Queue.
          If one of the two WLS Servers fails the other WLS Server with the corresponding
          MDB should get the Messages of the
          MQSeries Queue.
          If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
          and the following Exception is thrown:
          <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
          mdb_deployed
          weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
          exception is:
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
          'btsun1a:TEST'
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
          I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
          the same Exception when the MDB is deployed.
          The configuration of JMSadmin on both Hosts is the following:
          dis qcf(myQCF2)
          HOSTNAME(btsun1a)
          CCSID(819)
          TRANSPORT(CLIENT)
          PORT(1414)
          TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
          QMANAGER(TEST)
          CHANNEL(JAVA.CHANNEL)
          VERSION(1)
          dis q(myQueue)
          CCSID(819)
          PERSISTENCE(APP)
          TARGCLIENT(JMS)
          QUEUE(MYQUEUE)
          EXPIRY(APP)
          QMANAGER(TEST)
          ENCODING(NATIVE)
          VERSION(1)
          PRIORITY(APP)
          I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
          and a QueueManager on each WLS Server.
          Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?


          With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
          a MDB can be
          configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
          is started at the same Host that runs the WLS Server too.
          And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
          In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
          Queuemanager.
          A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
          of this Queue.
          If one of the two WLS Servers fails the other WLS Server with the corresponding
          MDB should get the Messages of the
          MQSeries Queue.
          If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
          and the following Exception is thrown:
          <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
          mdb_deployed
          weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
          exception is:
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
          'btsun1a:TEST'
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
          I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
          the same Exception when the MDB is deployed.
          The configuration of JMSadmin on both Hosts is the following:
          dis qcf(myQCF2)
          HOSTNAME(btsun1a)
          CCSID(819)
          TRANSPORT(CLIENT)
          PORT(1414)
          TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
          QMANAGER(TEST)
          CHANNEL(JAVA.CHANNEL)
          VERSION(1)
          dis q(myQueue)
          CCSID(819)
          PERSISTENCE(APP)
          TARGCLIENT(JMS)
          QUEUE(MYQUEUE)
          EXPIRY(APP)
          QMANAGER(TEST)
          ENCODING(NATIVE)
          VERSION(1)
          PRIORITY(APP)
          I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
          and a QueueManager on each WLS Server.
          Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?

Message driven beans and object binding

          I want to write a message driven bean, and use javax.naming.Context's "bind(String,
          Object)" method to bind the data to a key and eventually do a unbind(String) to
          look up the data . Is binding/unbinding of object is allowed inside a message
          driven bean or this violates the EJB2.0 spec? Also, does this have any negative
          consequences if I use a Weblogic cluster as opposed to a single instance? Any
          suggestions


Hi Austin,
          - I don't know if it is "legal" in EJB 2.0
          to call bind/unbind within an MDB. I
          would assume so, but I'm not sure. You can try confirming with
          the jndi and ejb newsgroups. Of course, if you don't
          ask, then no one can tell you "no". ;-)
          - Bind/unbind is a relatively expensive call performance-wise. I
          suspect one might want to avoid doing too many of these per
          second (the jndi newsgroup may be able to give pointers here.)
          - Servers in a cluster do not instantly propagate bind/unbind info
          to other servers in cluster, and JNDI may have trouble
          efficiently supporting larger objects: both potential drawbacks
          to using JNDI for data caching purposes.
          Tom, BEA
          Austin P wrote:
          > I want to write a message driven bean, and use javax.naming.Context's "bind(String,
          > Object)" method to bind the data to a key and eventually do a unbind(String) to
          > look up the data . Is binding/unbinding of object is allowed inside a message
          > driven bean or this violates the EJB2.0 spec? Also, does this have any negative
          > consequences if I use a Weblogic cluster as opposed to a single instance? Any
          > suggestions

B2B using JMS and Processing Messages with Message Driven Beans

We want to be able to use B2B to send messages to a JMS queue and then process messages from B2B using a Message Driven Bean. Is this supported.
We are using B2B 10.2.0.2 with Patchset 4.

Hello,
In 10.1.2.0.2 B2B , as part of the internal Delivery channel B2B can only send and receive messages from JMS queues.
Rgds,Ramesh

Message driven bean and security

Hi there!
I need to apply security capability during analyzing incoming messages.
Details:
I have an Entity bean with one method restricted by security to access. But
one of requirements is to provide this method call also in asynchronous way.
So I add Message Driven Bean that will call method of entity. But it's a
security violation.
So, can anybody advise how to provide security in conjunction with MDB?
Thank you in advance.

Hi Max,
I think the problem is that you have no context with which to pass the security
credentials. You need someway to pass the credentials.
Kind Regards,
Richard Wallace
Senior Developer Relations Engineer
BEA Support.
"Max" <[email protected]> wrote:
Hi there!
I need to apply security capability during analyzing incoming messages.
Details:
I have an Entity bean with one method restricted by security to access.
But
one of requirements is to provide this method call also in asynchronous
way.
So I add Message Driven Bean that will call method of entity. But it's
a
security violation.
So, can anybody advise how to provide security in conjunction with MDB?
Thank you in advance.

Create EJB 3.0 Message Driven Bean on a Oracle JMS (AQ)

Hi, I need to develop a EJB 3.0 Message Driven Bean. The MDB has to work on a Oracle AQ using Oracle JMS. Is there any how-to document giving an example about this issue. Can you give an example how to create the JMS destination in OC4J (how to configure the Oracle JMS AQ in OC4j), issue the JMS destination via annotions (resource injection) in the MDB. Please give me a working example of the MDB and a test client to produce a message. Regards, Arjan Jorritsma

Check your ejb-jar.xml and see if it has the version of "2.1" there...
If the application was depending upon EJB 3.0 annotations but it had a ejb-jar.xml that had version set to "2.1" and there was no oracle specific descriptor (orion-ejb-jar.xml) to designate it use the resource adapter; It would expect JMS destination and connection factory that is required for a JMS-MDB set in the ejb-jar.xml. So try to change the ejb-jar.xml to update the version to "3.0", OC4J would have parsed the annotation and combined the metadata with ejb-jar.xml and it would work.
-Frances

OC4J and Message Driven Bean

Similar Messages

Maybe you are looking for