EJB 3.0 Cache Issue With OC4J Instance With Multiple JVM's

Question

I created an EJB 3.0 project in JDeveloper 10.1.3.3.0 and everything works fine in the embedded OC4J server. I am deploying the application to an OC4J instance consisting of 3 Java Virtual Machines in Oracle Application server 10.1.3 and seem to be getting a different persistence context for each virtual machine. i.e. I'll have 3 browsers that can view the same data even after updating, another 2 browsers that can't see the first 3's changes but can see changes by any browser in this group, etc.
I tried adding the below to the persistence-unit tag in the persistence.xml but it didn't seem to help.
<properties>
<property name="toplink.cache.shared.default" value="true"/>
</properties>
How do you get all connections to use the same cache?

Answer 1

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush