Suspending/Pausing a MDB's Consumption Programmatically

Question

Hey guys
I have come across a lot of forums saying that there are new methods available from Weblogic 9 that enable the suspension of a MDB's consumption but I can not find any examples of it. Does anyone by any chance have an example of this?
I am using Weblogic 10.3. Is it possible? I have been stuck on this for a while now and I really have no where to turn... Java code would be so awesome right now. All I am trying to do is emulate what happens when you click on Suspend MDB in the console of weblogic so that messages can be added to the queue and not get processed then once resumed (maybe from the console) the MDB would carry on processing the messages.
Thanks for any help

Answer 1

Thanks Albert, with your help I have come to a solution
Here is an example of the code I think is the best option:
import java.util.Hashtable;
import javax.management.MBeanServerConnection;
import javax.management.ObjectName;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
import javax.naming.Context;
public class StopTheBean implements Runnable{
     public void stopTheBean() {
          Thread runner = new Thread(this);
          runner.start();
     public void run() {
          try {
               String hostname = "127.0.0.1";
               String portString = "7001";
               String username = "weblogic";
               String password = "weblogic";
               String protocol = "t3";
               Integer portInteger = Integer.valueOf(portString);
               int port = portInteger.intValue();
               String jndiroot = "/jndi/";
               String mserver = "weblogic.management.mbeanservers.runtime";
               JMXServiceURL serviceURL = new JMXServiceURL(protocol, hostname, port, jndiroot + mserver);
               Hashtable<String, Object> h = new Hashtable<String, Object>();
               h.put(Context.SECURITY_PRINCIPAL, username);
               h.put(Context.SECURITY_CREDENTIALS, password);
               h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote");
               h.put("jmx.remote.x.request.waiting.timeout", new Long(10000));
               JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
               MBeanServerConnection connection = connector.getMBeanServerConnection();
               Hashtable<String, String> prop = new Hashtable<String, String>();
               prop.put("Name", "SuspendBean_SORBModule!SORBOrderRequest_Q");
               prop.put("Type", "MessageDrivenEJBRuntime");
               prop.put("ServerRuntime", "Local_Admin");
               prop.put("ApplicationRuntime", "SuspendMDBEAR");
               prop.put("EJBComponentRuntime", "SuspendMDB.jar");
               ObjectName beanName = new ObjectName("com.bea", prop);
               connection.invoke(beanName, "suspend", null, null);
               System.out.println("MDB Stopped");
               connector.close();
          } catch (Exception e) {
               System.out.println(e.toString());
}Here is another example using a web service instead of a new thread:
import java.util.Hashtable;
import javax.jws.*;
import javax.management.MBeanServerConnection;
import javax.management.ObjectName;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
import javax.naming.Context;
@WebService
public class StopTheBean {
     @WebMethod
     public void beginTheSuspend() {
          try {
               String hostname = "127.0.0.1";
               String portString = "7001";
               String username = "weblogic";
               String password = "weblogic";
               String protocol = "t3";
               Integer portInteger = Integer.valueOf(portString);
               int port = portInteger.intValue();
               String jndiroot = "/jndi/";
               String mserver = "weblogic.management.mbeanservers.runtime";
               JMXServiceURL serviceURL = new JMXServiceURL(protocol, hostname, port, jndiroot + mserver);
               Hashtable<String, Object> h = new Hashtable<String, Object>();
               h.put(Context.SECURITY_PRINCIPAL, username);
               h.put(Context.SECURITY_CREDENTIALS, password);
               h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote");
               h.put("jmx.remote.x.request.waiting.timeout", new Long(10000));
               JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
               MBeanServerConnection connection = connector.getMBeanServerConnection();
               Hashtable<String, String> prop = new Hashtable<String, String>();
               prop.put("Name", "SuspendBean_SORBModule!SORBOrderRequest_Q");
               prop.put("Type", "MessageDrivenEJBRuntime");
               prop.put("ServerRuntime", "Local_Admin");
               prop.put("ApplicationRuntime", "SuspendMDBEAR");
               prop.put("EJBComponentRuntime", "SuspendMDB.jar");
               ObjectName beanName = new ObjectName("com.bea", prop);
               connection.invoke(beanName, "suspend", null, null);
               System.out.println("MDB Suspended");
               connector.close();
          } catch (Exception e) {
               System.out.println(e.toString());
}First of all, it has to be on its own thread separate from the MDB otherwise the thread will just hang... Secondly I know the context can be used to get the MBeanServer but it gives errors on authorization. That's why it has to be done this way, so that you can set the username and password to be used. The alternative way looks like this for anyone that is interested:
InitialContext ctx = new InitialContext();
MBeanServer server = (MBeanServer) ctx.lookup("java:comp/env/jmx/runtime");And to further this post, these two sections of code return the exact same thing. So if you are struggling with getting the object name of the message bean you can find out what that is with the first of the next two sections of code:
               ObjectName[] bob = (ObjectName[]) server.getAttribute(new ObjectName("com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean"), "Services");
               for (ObjectName objectName : bob) {
                    ObjectName serverrt = (ObjectName) server.getAttribute(objectName, "ServerRuntime");
                    ObjectName[] apprt = (ObjectName[]) server.getAttribute(serverrt, "ApplicationRuntimes");
                    for (ObjectName appName : apprt) {
                         if (appName.toString().contains("SuspendMDBEAR")) {
                              ObjectName[] comprt = (ObjectName[]) server.getAttribute(appName, "ComponentRuntimes");
                              ObjectName[] ejbrt = (ObjectName[]) server.getAttribute(comprt[0], "EJBRuntimes");
                              for (ObjectName ejbName : ejbrt) {
                                   server.invoke(ejbName, "suspend", null, null);
               Hashtable<String, String> prop = new Hashtable<String, String>();
               prop.put("Name", "SuspendBean_SORBModule!SORBOrderRequest_Q");
               prop.put("Type", "MessageDrivenEJBRuntime");
               prop.put("ServerRuntime", "Local_Admin");
               prop.put("ApplicationRuntime", "SuspendMDBEAR");
               prop.put("EJBComponentRuntime", "SuspendMDB.jar");
               ObjectName beanName = new ObjectName("com.bea", prop);
               server.invoke(beanName, "suspend", null, null);I will REPEAT, the immediate above two sections do the exact same thing. Please note, the variable "server" in these two sections of code refers to the MBeanServer.
Here are some useful attributes that can be retrieved from the MDB:
               connection.getAttribute(beanName, "ConnectionStatus");
               connection.getAttribute(beanName, "Destination");
               connection.getAttribute(beanName, "EJBName");
               connection.getAttribute(beanName, "HealthState");
               connection.getAttribute(beanName, "JmsClientID");
               connection.getAttribute(beanName, "JMSConnectionAlive");
               connection.getAttribute(beanName, "LastException");
               connection.getAttribute(beanName, "LastExceptionAsString");
               connection.getAttribute(beanName, "MDBStatus");
               connection.getAttribute(beanName, "Name");
               connection.getAttribute(beanName, "Parent");
               connection.getAttribute(beanName, "ProcessedMessageCount");
               connection.getAttribute(beanName, "SuspendCount");
               connection.getAttribute(beanName, "Type");I think they all return as Strings. Just check it before you use it!
I hope this helps anyone that was in my position!
ENJOY