JMS / MBean WL7 bug

          Hi,
          We have a message driven bean with a configured max pool size of 8 and min pool
          size of one. The message driven bean is heavily used. When viewing active JMS
          destinations, the JMS queue has 8 consumers which is correct However, when we
          pull the stats from the mbeans regarding the idle count and in_use count of the
          message driven bean it starts off correct as 8 in_use and 0 idle . After some
          time the figure changes and is now at 386 (idle) and -83 (in use).
          Kevin

I agree. I suggest reporting this to customer support.
          Tom
          Kevin Sharfman wrote:
          > Hi,
          >
          > We have a message driven bean with a configured max pool size of 8 and min pool
          > size of one. The message driven bean is heavily used. When viewing active JMS
          > destinations, the JMS queue has 8 consumers which is correct However, when we
          > pull the stats from the mbeans regarding the idle count and in_use count of the
          > message driven bean it starts off correct as 8 in_use and 0 idle . After some
          > time the figure changes and is now at 386 (idle) and -83 (in use).
          >
          > Kevin

Similar Messages

MBean Invoke Bug?

Im registering an Mbean with a method that starts up a process and writes to the
log file. If i invoke this mbean as Admin, all is well and it gets started fine.
If i invoke it using an Operator Role, i get an exception like
Access not Allowed for subject:principals=[operator, Operators], on ResourceType:
DomainLogHandlerRuntime Action: execute Target: registerToMe.
Im not sure why the domainloghandler is invoked in this case as i have log4j writing
to my log file. Is this a bug?
Thanks
Raj

"raj" <[email protected]> wrote:
>
Im registering an Mbean with a method that starts up a process and writes
to the
log file. If i invoke this mbean as Admin, all is well and it gets started
fine.
If i invoke it using an Operator Role, i get an exception like
Access not Allowed for subject:principals=[operator, Operators], on ResourceType:
DomainLogHandlerRuntime Action: execute Target: registerToMe.
Im not sure why the domainloghandler is invoked in this case as i have
log4j writing
to my log file. Is this a bug?You may want to ask this question in weblogic.developer.interest.management

Weblogic 10 Ant task, JMS Module & Foreign JMS Destinations

Any body knows how to configure JMS System Modules (which got introduced in WL ver. 9) and other JMS MBeans such as JMS Destinations and ConnectionFactories under the newly created JMS Module, using ant task for Weblogic 10.3 ?
Also, when I create the ForeignJMSServer and the child MBeans such as Foreign Destinations and ConnectionFactories using ant task, it just creates the ForeignJMSServer and not creating the child MBeans. The problem is with WL 10. In WL 8.1, it works fine.
In Weblogic 8.1, þe ant target for this job is as follows.
===========================================================================
     <target name="prepareForeignJMSServer">
<wlconfig url="t3://localhost:7001" username="weblogic"
password="weblogic" failonerror="false">
<create type="ForeignJMSServer" name="myForeignJMSServer" property="temp-jms-server">
<set attribute="InitialContextFactory" value="weblogic.jndi.WLInitialContextFactory"/>
<set attribute="ConnectionURL" value="t3://192.168.0.23:7001"/>
<set attribute="Targets" value="mydomain:Name=myserver,Type=Server"/>
<create type="ForeignJMSConnectionFactory" name="MyRemoteCF">
<set attribute="LocalJNDIName" value="MyLocalCFJNDI"/>
<set attribute="RemoteJNDIName" value="MyRemoteCFJNDI"/>
<set attribute="Username" value="weblogic-remote"/>
<set attribute="Password" value="weblogic-remote"/>
</create>
<create type="ForeignJMSDestination" Name="MyRemoteQueue1">
<set attribute="LocalJNDIName" value="MyLocalQueue1JNDI"/>
<set attribute="RemoteJNDIName" value="MyRemoteQueue1JNDI"/>
</create>
     </create>
          </wlconfig>
     </target>
=====================================================================
This target runs without error in WL 10, but does not create the ForeignJMSConnectionFactory and ForeignJMSDestination.
If some one knows the solution, please give me advice.
Thanks,

Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

Javax.naming.NameNotFoundException: jms/QueueConnectionFactory not found

Hi,
I wrote a Java JMS client that connect to Oracle9iAs 9.0.2.1
using OC4J 9.0.3.
I got the error javax.naming.NameNotFoundException: jms/QueueConnectionFactory not found?
first I'm a bit confused about which rmi port to use to connect
to Oracle9ias, I found there is 7 ports open from 3101 to 3107?
How could I I know which port my OC4J_Home is using??
thanks
Ahmed

thanks for your help, I know now that i'm connecting to the right port, however, i'm still getting the error message
error javax.naming.NameNotFoundException: jms/QueueConnectionFactory not found?
note that i'm not getting such message on OC4J standalone.
I know that Oracle donestn't recommend the use of ligth
JMS only AQ, becouse light oracle JMS have some bugs,
is this one of the bugs?
any body have a idea what could be the probelm?
Ahmed

Creating JMS Topic using JMX/MBeans Interface

Hello,
I'm trying to create a JMS Topic using MBeans. For this, I first
create a JMSTemplateMBean, then I create a JMSServerMBean (do
setTemporaryTemplate() and addTarget() on the latter) and finally
create JMSTopicMBean. On the JMSTopicMBean, I do setJNDIName() and
jmsServerMBean.addDestination(topicMBean).
Problem is that when I look in the console, I see only the JMS
Template and JMS Server (JMS Topic is NOT there). But if I try to
rerun my program, it gives 'InstanceAlreadyExistsException' on the
JMSTopic. Also, when I print out all the MBeans, the JMSTopic MBean is
there i.e. its been created. So why won't it show up in the Console ?
Any ideas are appreciated.
Thanks
-PG

I'm having exact same problem, except I'm trying to go through the weblogic.Admin command-line tool. (I'm working with version 6.1) First I create a JMSServer and set its Targets property. It shows up in console and I see the entry in config.xml. Then I create a new JMSTopic and set its JNDIName (I can't see this new topic from console, but an entry is made in config.xml and I can't create the topic again.) Then I invoke the addDestination method on the JMSServer MBean and pass in my new topic. The method returns "false", with no futher explanations or exceptions. If I try to go through the setDestinations property of the JMSServer MBean, the same thing happens: a silent failure.
I have no idea what to do! Is this a bug? Has anyone ever succeeded in doing this sort of thing?

[svn] 2692: Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out .

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

JMS Listener Bug??

I am implementing SIM 7.0 and have enabled a JMS Listener resource. The resource works well and we have no issues with it.
The problem is when you try to edit the Synchronization policy for the JMS Listener and then cancel it without saving i.e.
1. Select the JMS Listener
2. Edit Synchronization Policy
3. Cancel the dit, you need not change anything
This throws a Task may have been deleted error. Can someone help me with solving this issue?
I have been trying to raise this as a bug but have not been successful. Can someone help me with how to report a bug. I went to the Bugs Reporting page but could not determine the proper set of options to pick to report a bug with the JMS Listener resource on Sun IdM.

That's what I figured with that global interactive I was trying to access the instance variables before so it wasn't showing up under my user. Now instead of an error pop up the error message shows up at the bottom of the runtime UI.
Error at bottom of page: (Followed by a bunch of package names)
Unexpected Error
javax.faces.el.EvaluationException: /jsf/menu/menuActionNormal.xhtml @24,147 onActivate="#{componentBean.doExecuteAction}": fuego.papi.exception.InvalidTaskNumberException: Invalid task number '0' for activity '/Manager#Default-1.0/Global'.
Warning in the Log:
There was an error when trying to obtain the environement information: null
Application: Engine, Module: Main, Thread: <0> StartUpServerIt gives me the top error when I have the notification set up to receive an external notification and gives me the warning for both cases either external notification or internal event. Its an internal event but in the documentation it never covers internal event situations for NotificationWait so I tried both.
Another thing is when I have 2 or more instances waiting at the wait how does it know which one to go too? In the real example it will be receiving an object from the thread that will have an id number. But in this little test set up how does it know which instance the global activity is for?

Monitoring jms distributed queue on WebLogic 8.1 via MBeans

Good afternon,
please do you have someone java code (only basic enough !) for jmx monitoring jms distributed queue on weblogic 8.1 (Monitor all Active JMS Destinations and there Consumers, Consumers High, Consumers Total and so on..). Think should be used JMSDestinationRuntimeMBean interface but have no idea how write the code.
Thank you for any hint
Lada Dvorak

This is a simple jmx sample code based on WLS 8.x
import javax.naming.Context;
import java.util.Set;
import java.util.Iterator;
import java.io.PrintWriter;
import java.io.FileOutputStream;
import weblogic.jndi.Environment;
import weblogic.management.MBeanHome;
import weblogic.management.WebLogicMBean;
import weblogic.management.WebLogicObjectName;
public class ListAllMBeans{
     public static void main(String args[]) {
          String url = "t3://localhost:7001";
          String username = "weblogic";
          String password = "weblogic";
          PrintWriter pWriter = null; // print without buffering
try {            //Obtaining an MBeanHome Using JNDI
               Environment env = new Environment();
               env.setProviderUrl(url);
               env.setSecurityPrincipal(username);
               env.setSecurityCredentials(password);
               Context ctx = env.getInitialContext();
               MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
Set allMBeans = home.getAllMBeans();
               System.out.println("Size: " + allMBeans.size());
               for (Iterator itr = allMBeans.iterator(); itr.hasNext(); ) {
                    WebLogicMBean mbean = (WebLogicMBean)itr.next();
                    WebLogicObjectName objectName = mbean.getObjectName();
                    pWriter = new PrintWriter(new FileOutputStream("JMXType.txt", true), true);
                    pWriter.println(objectName.getName() + " is a(n) " + mbean.getType());
                    //System.out.println(objectName.getName() + " is a(n) " + mbean.getType());
          }catch(Exception e){
               System.out.println(e);
I hope this will be helpful to you.

Mbean that listen for jms queue messages

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Creating more then one JMS Destination using MBeans

Hi all,
I am trying to create 2(or more) JMS Destinations (Topics and Queues) in a JMS Server.
The code looks like:
MBeanHome home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
ServerMBean srvrMBean = (ServerMBean) home.getMBean("examplesServer", "Server",
"examples");
JMSServerMBean jmsServer = (JMSServerMBean)home.findOrCreateAdminMBean("examplesServer",
"JMSServer", "examples");
jmsServer.setStore(jmsStore);//jmsStore is JMSJDBCStoreMBean obj
jmsServer.setTargets(srvrMBean);
JMSDestinationMBean jmsTopic1 = (JMSTopicMBean)home.findOrCreateAdminMBean("tempTopic1",
"JMSTopic", "examples", jmsServer);
jmsTopic1.setJNDIName("com.temp.topic1");
jmsServer.addDestination(jmsTopic1);
and the second one is added as:
JMSDestinationMBean jmsTopic2 = (JMSTopicMBean)home.findOrCreateAdminMBean("tempTopic2",
"JMSTopic", "examples", jmsServer);
jmsTopic2.setJNDIName("com.temp.topic2");
jmsServer.addDestination(jmsTopic2);
(Actually, the Topics are added to the jmsServer in a method)
I can see in the console that the first topic is added to the JMS server and to the
JNDItree of the server instance,
But for some reason, the second topic is not added to the JNDI tree(but it is added
to the JMS Server).
and I can not look up the second object in JNDI.
Does anybody come across this problem??
what is the right way to add the destinations??
thanks for any help
-Vijay

Hi Mihir,
thanks....I tried the same program, but the only difference is i am setting the targets
to the jms server (i.e. jmsServer.setTarget(tm);) before adding second destination
to it(i tried both setDestinations and addDestination).
Because, (according to my requirements) after adding the first destination i have
to set the target for the jmsserver (which eventually starts the JMSserver).
So, is there any way to add the destinations to the jmsserver after setting the targets??
thanks for any help
-Vijay
"Mihir Kulkarni" <[email protected]> wrote:
The following code works for me.
Btw, I use setDestinations and pass it an array of JMSDestinationMBeans
instead of using addDestinations()
Hope this helps...
mihir
import java.util.Set;
import java.util.Iterator;
import java.rmi.RemoteException;
import javax.naming.*;
import weblogic.jndi.Environment;
import weblogic.management.MBeanHome;
import javax.management.ObjectName;
import weblogic.management.WebLogicMBean;
import weblogic.management.MBeanCreationException;
import weblogic.management.configuration.ServerMBean;
import weblogic.management.runtime.ServerRuntimeMBean;
import weblogic.management.WebLogicObjectName;
import weblogic.management.configuration.*;
import javax.management.InvalidAttributeValueException;
/* Running this program will create a JMS Server and a JMS Connection
* Factory targetted to the Admin server. It will also add a JMS Topic
* and a JMS Queue to the JMSServer.
* This will create the following entries in the config.xml:
* <JMSServer Name="myJMSServer" Targets="MyServer">
* <JMSQueue JNDIName="jmx.jms.myJMSQueue" Name="myJMSQueue"/>
* <JMSTopic JNDIName="jmx.jms.myJMSTopic" Name="myJMSTopic"/>
* </JMSServer>
* <JMSConnectionFactory JNDIName="jmx.jms.myJMSConnectionFactory"
* Name="myJMSConnectionFactory" Targets="MyServer"/>
public class createJMS {
public createJMS() {
public static void main(String[] args) {
JMSServerMBean jmsServer = null;
JMSDestinationMBean jmsQueue = null;
JMSDestinationMBean jmsTopic = null;
JMSConnectionFactoryMBean jmsConnectionFactory = null;
JMSSessionPoolMBean jmsSessionPool = null;
JMSConnectionConsumerMBean jmsConnectionConsumer = null;
ServerMBean srvrMBean = null;
MBeanHome home = null;
JMSServerMBean jmsServerConfig = null;
file://domain variables
String url = "t3://localhost:7001";
String username = "system";
String password = "mihirk00";
file://variable Names
String DOMAIN = "mihirDomain";
String ADMINSERVERNAME = "MyServer";
String JMSSERVER = "myJMSServer";
String JMSCONNECTIONFACTORY = "myJMSConnectionFactory";
String JMSQUEUE = "myJMSQueue";
String JMSTOPIC = "myJMSTopic";
log("Creating AdminMBeans for JMS queue and JMS connection
factory");
try
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
home = (MBeanHome)ctx.lookup("weblogic.management.adminhome");
log("Got AdminHome: " + home);
String name = DOMAIN + ":,Name=" + ADMINSERVERNAME + ",Type=Server"
WebLogicObjectName objName = new WebLogicObjectName(name);
srvrMBean = (ServerMBean)home.getMBean(objName);
file://srvrMBean =
(ServerMBean)home.getMBean(ADMINSERVERNAME,"Server",DOMAIN);
log("Got the serverMBean: " + srvrMBean);
} catch (Exception e) {
log("Exception in getting Admin home & srvrMBean: " + e);
/* the findOrCreateAdminMBean method of the MBeanHome is used to
create
* the Admin MBeans for all the JMS stuff needed for this utility
* the method takes 3 parameters - Name, Type, Domain
* the type Parameter is the name of the MBean you want to create
* minus the MBean prefix
* eg) JMSServer, JMSConnectionFactory, JMSQueue etc..
* It also takes an addition parameter which is the parent
AdminMbean
* if one needs to create a child node in the xml tree.
* Once the MBean is created you can set attributes on it using
the
* exposed API of that MBean
* Its always better to use the findOrCreateAdminMBean method compared
* to createAdminMBean method .
file://use findOrCreateAdminMBean to create JMSConnectionFactory
try {
jmsConnectionFactory =
(JMSConnectionFactoryMBean)home.findOrCreateAdminMBean(JMSCONNECTIONFACTORY,
"JMSConnectionFactory", DOMAIN);
if( jmsConnectionFactory.getJNDIName() == null) {
jmsConnectionFactory.setJNDIName("jmx.jms.myJMSConnectionFactory");
log("Created a JMSConnectionFactory");
else
log("looked up JMS ConnectionFactory: " +
jmsConnectionFactory.getJNDIName());
} catch (MBeanCreationException e) {
log("MBeanCreationException: " + e);
catch(InvalidAttributeValueException e) {
log("InvalidAttributeValueException: " + e);
file://create the JMSServerMBean
try {
jmsServer = (JMSServerMBean)home.findOrCreateAdminMBean(JMSSERVER,
"JMSServer", DOMAIN);
log("Found or Created a JMSServer");
} catch (MBeanCreationException e) {
log("MBeanCreationException: " + e);
file://create the JMSQueueMBean - use methods of
JMSDestinationMBean
file://here we pass the jmsServer as the parent MBean so that the
file://JMSQueueMBean is created as the child of the JMSServerMBean
try {
jmsQueue =
(JMSDestinationMBean)home.findOrCreateAdminMBean(JMSQUEUE, "JMSQueue",
DOMAIN, jmsServer);
if( jmsQueue.getJNDIName() == null) {
jmsQueue.setJNDIName("jmx.jms.myJMSQueue");
log("Created a JMSQueue");
else {
log("looked up JMS Queue: " + jmsQueue.getJNDIName());
} catch (MBeanCreationException e) {
log("MBeanCreationException: " + e);
catch(InvalidAttributeValueException e) {
log("InvalidAttributeValueException: " + e);
file://create the JMSTopicMBean - use methods of
JMSDestinationMBean
file://here we pass the jmsServer as the parent MBean so that the
file://JMSTopicMBean is created as the child of the JMSServerMBean
try {
jmsTopic =
(JMSDestinationMBean)home.findOrCreateAdminMBean(JMSTOPIC, "JMSTopic",
DOMAIN, jmsServer);
if( jmsTopic.getJNDIName() == null) {
jmsTopic.setJNDIName("jmx.jms.myJMSTopic");
log("Created a JMSTopic");
else {
log("looked up JMS Topic: " + jmsTopic.getJNDIName());
} catch (MBeanCreationException e) {
log("MBeanCreationException: " + e);
catch(InvalidAttributeValueException e) {
log("InvalidAttributeValueException: " + e);
file://create the target Arrays
JMSDestinationMBean[] jdm = {jmsQueue,jmsTopic};
TargetMBean[] tm = {srvrMBean};
file://set the Destinations for the jms Server
try {
jmsServer.setDestinations(jdm);
log("Added Destination to the jmsServer");
} catch(Exception e) {
log("Excpn in setting the property for jmsServer:" + e);
/* Now target the JMS Server to the appropriate Server
* As the JMSServerMBean extends the DeploymentMBean, we can
directly
* use the addTarget method of the DeploymentMBean
file://ordering is important
file://Target the JMS ConnectionFactory
try {
jmsConnectionFactory.setTargets(tm);
log("Targetted the Connection Factory to the admin Server");
} catch (Exception e) {
System.out.println("Exception in targetting the
jmsConnectionFactory to the Admin server: " + e);
file://Target the JMS Server
try {
jmsServer.setTargets(tm);
log("Targetted the JMS Server to the admin Server");
} catch (Exception e) {
System.out.println("\nException in targetting the jmsServer to
the Admin server: " + e);
log("Done with registering AdminMBeans for JMS");
private static void log(String s) {
System.out.println("\n[createJMS]: " + s);
"Vijay Bujula" <[email protected]> wrote in message
news:[email protected]...
Hi all,
I am trying to create 2(or more) JMS Destinations (Topics and Queues)in a
JMS Server.
The code looks like:
MBeanHome home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
ServerMBean srvrMBean = (ServerMBean) home.getMBean("examplesServer","Server",
"examples");
JMSServerMBean jmsServer =(JMSServerMBean)home.findOrCreateAdminMBean("examplesServer",
"JMSServer", "examples");
jmsServer.setStore(jmsStore);//jmsStore is JMSJDBCStoreMBean obj
jmsServer.setTargets(srvrMBean);
JMSDestinationMBean jmsTopic1 =(JMSTopicMBean)home.findOrCreateAdminMBean("tempTopic1",
"JMSTopic", "examples", jmsServer);
jmsTopic1.setJNDIName("com.temp.topic1");
jmsServer.addDestination(jmsTopic1);
and the second one is added as:
JMSDestinationMBean jmsTopic2 =(JMSTopicMBean)home.findOrCreateAdminMBean("tempTopic2",
"JMSTopic", "examples", jmsServer);
jmsTopic2.setJNDIName("com.temp.topic2");
jmsServer.addDestination(jmsTopic2);
(Actually, the Topics are added to the jmsServer in a method)
I can see in the console that the first topic is added to the JMS serverand to the
JNDItree of the server instance,
But for some reason, the second topic is not added to the JNDI tree(butit
is added
to the JMS Server).
and I can not look up the second object in JNDI.
Does anybody come across this problem??
what is the right way to add the destinations??
thanks for any help
-Vijay

Get JMS Factory from MBean ??

I am using JMSDestinationRuntime MBean to get back a list of queues and then use the QueueBrowser to peek at the messages in the queues.
          I want to make this generic, so am wondering if there is any way in which i can get the JMSFactory name of each queue from the MBean, such that i can do the following:
          qconFactory = (QueueConnectionFactory) ctx.lookup(jmsFactory);
          qcon = qconFactory.createQueueConnection();
          qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          //queue = (Queue) ctx.lookup(queueName);
          queue = qsession.createQueue("eri01JMSServer/K12MyOrgJMSQueue_eri01");
          qbrowser = qsession.createBrowser(queue);
          qcon.start();
          Thanks,
          Sam

You can look up jms connection factory JNDI names via the associated configuration mbeans (instead of the runtime mbeans). Alternatively, you could simply use one of the default built-in connection factory names - as you probably don't need to use a custom connection factory simply for browsing a destination.
          Another alternative is to use WebLogic 9.0 and later, which provides runtime mbeans for browsing the destinations (no JMS API involved - just JMX). These mbeans are more powerful than the queuebrowser, as the mbeans are capable of viewing all messages in the destination (including "unborn" scheduled messages for example).
          Tom

Bug in JMS adapter?

Hi all,
I'm struggling to integrate ESB JMS adapter with Weblogic. I'm able to produce message, however when I try to consume it seems ESB is not able to handle Weblogic JMSMessageID in format: ID:P<1212131.123123123123>
SEVERE: Activity monitor manager received an unexpected exception while processing the activity messages. Expected name instead of 9.
oracle.xml.parser.v2.XMLParseException: Expected name instead of 9.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1151)
at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1928)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1276)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:319)
at oracle.tip.esb.utils.XmlUtils.getXmlDocument(Unknown Source)
at oracle.tip.esb.monitor.manager.ActivityMessageManager.handleMessage(Unknown Source)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(Unknown Source)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(Unknown Source)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
SEVERE: Failed to process deferred message
oracle.tip.esb.server.common.exceptions.BusinessEventRejectionException: Error occured while handling monitor message dequeued from monitor topic. Message text is "<activityMessages><activityMessage order='1' type='0'><flowId>ID:P<953855.1174931938686.0></flowId><subFlowId>1174932729112</subFlowId><source>BDE44411DB7D11DBAF560BB06EC6AFF7</source><sourceQName>DefaultSystem.JMS_Consume</sourceQName><timestamp>1174932729113</timestamp><operationGUID>BDE75150DB7D11DBAF560BB06EC6AFF7</operationGUID><operationQName>DefaultSystem.JMS_Consume_RS.Consume_Message</operationQName></activityMessage><activityMessage order='1' type='15'><flowId>ID:P<953855.1174931938686.0></flowId><subFlowId>1174932729112</subFlowId><timestamp>1174932729122</timestamp></activityMessage>
Looking forward for your prompt feedback
Marek

Hi,
This link may help you..
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/frameset.htm
Regards,
Srinivas

Bug in creating a foreign jms destination

it is not a real big one, but the server doesn't handle the error of adding a foreign destination with the same same or jndi name very well. maybe someone at BEA can put this into a bug report.
          steps:
          Configure a new Foreign JMSDestination...
          Enter Name, Local JNDI Name, Remote JNDI Name
          Click Create
          Configure a new Foreign JMSDestination...
          Enter the same Name, Local JNDI Name, Remote JNDI Name
          Click Create
          There is an exception trace, and the foreign destination with that naem is no longer displayed in the list of destinations. The destination still exists in the config.xml, but the admin server must be restarted to display the destinations properly again.

Problems like this tend to get more attention if they come through customer support, so please file a case directly with them. If this is too much trouble, let me know, and I'll eventually file the issue with our internal tracking system...
          Thanks,
          Tom Barnes
          BEA WebLogic Performance Team

Worlds problem JMS & JNDI - BUG?

Hi,
We have a message-driven bean that make a lookup to session
bean(stateless).
When trying to cast to home interface we got exception
ClassCastException.
when we try to print the ClassLoader of the object we make lookup ant
our current object and thread context,
we found that the are in difrrent worlds. (This wasn't happen when we do
a lookup + cast to home interface from session to session).
is it a bug?
Thanks & happy new year
Nir Parikman

problem occur only wls6b2
work fine in GA version
Thanks
Nir Parikman
[email protected] wrote:
Please post the stack traces when you these exceptions. That would really
help.
-- Prasad
Nir Parikman wrote:
Hi,
We have a message-driven bean that make a lookup to session
bean(stateless).
When trying to cast to home interface we got exception
ClassCastException.
when we try to print the ClassLoader of the object we make lookup ant
our current object and thread context,
we found that the are in difrrent worlds. (This wasn't happen when we do
a lookup + cast to home interface from session to session).
is it a bug?
Thanks & happy new year
Nir Parikman--
Cheers
- Prasad

Foreign JMS and XA

Hi everybody,
          Is anybody successfully using remote IBM MQseries 5.3 server as
          Foreign JMS in WLS 8.1sp2?
          We're observing some strange behavior in this case. Here is our setup:
          WLS and IBM MQ server deployed on separate boxes.
          WLS version 8.1sp2 running on Windows 2000/Intel
          IBM MQ version 5.3 running on Solaris/SPARC
          We're using "WebSphere MQ classes for Java, version 5.303 - j5303-L030225"
          and "WebSphere MQ Extended Transactional Client Feature, version 5.300 -
          j5303-L030122"
          MQ files added in WLS POST_CLASSPATH variable in WLS starup script.
          Foreign JMS server configured in WLS via fscontext JNDI.
          MDB bean deployed with Transaction attribute "Required".
          Everything seems to work fine, if we're posting message to MQ queue MDB
          receives it and process successfully (just print message content to the
          console for now).
          Problem: In WLS console, under Server->Monitoring->JTA->Monitor inflight
          transactions we can constantly see one transaction enlisted for our MDB
          bean with following details:
          =====================================================
          Transaction ID: BEA1-00DFC5EB4B7B7F28EDB9
          Coordinator: mydomain+myserver
          Name: JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          Status: Active
          Seconds Active: 17
          Resources:
          weblogic.ejb20.JMSConnectionPoller.xxx.xxx.MyMessageProcessorMdb=started
          Properties
          (key=value):
          weblogic.transaction.name=JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          =====================================================
          This transaction seems to be Active for 30 seconds and then rolled back
          (no error messages on WLS console displayed).On JTA statistics page in
          WLS console "Total Rolled Back" counter keeps increneting with every
          rollback.
          Does anybody observerd similar problem? May be it's normal behaviour but
          I'm kind of worrying about those transactions and constant rollback. I'd
          appreciate any feedback.
          Sincerely,
          Dmitri Maximovich


Hi Dmitri,
          The shutdown "suspend" failure has nothing to do with transactions
          or JMS. It looks like the failure is due to a
          java.util.ConcurrentModificationException during undeployment
          which indicates a bug in WL - something is not getting
          synchronized that should be.
          As for MQ, their new extended client supports remote XA, which I think
          is the reason for the product in the first place. Even so, I
          still recommend testing to make sure that its messages
          participate in transactions. (Actually, I recommend such testing
          for any transactional app, including those built on WL JMS.)
          Tom
          Dmitri Maximovich wrote:
          > Hi Tom,
          >
          > Thanks for info, that's a relief. Unfortunately there is no hints in WLS
          > documentation that it's normal, that's why we were worried about it.
          >
          > Now there is one more issue, which I believe is related. You see with
          > those 'in-flight' transactions graceful shutdown of WLS doesn't quite
          > work. There is suspicious exception thrown and after that WLS is still
          > running in some state but console is not available anymore. Please see
          > console messages attached (sorry for long post). at the time of shutdown
          > there is no messages in the queue(s) so as far as I can tell those
          > 'pending transactions' mentioned is those from foreign JMS wrappers.
          >
          > I'd appreciate any comments on that. We have case opened with BEA about
          > this but so far they cannot reproduce it in their lab. That's why I
          > start wondering if we're doing something wrong here, like using remote
          > MQ server for example, may be you not supposed to (I remember there was
          > an issue before with IBM MQ that XA support required binding mode, I was
          > kind of hope that it's not the case anymore)?
          >
          > <Mar 3, 2004 1:47:56 PM EST> <Notice> <WebLogicServer> <BEA-000365>
          > <Server state changed to SUSPENDING>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <Deployer> <BEA-149236> <Preparing
          > to suspend.>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <Deployer> <BEA-149237> <Ready to
          > suspend.>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <WebService> <BEA-220028> <Web
          > Service reliable agents are suspended.>
          > <Mar 3, 2004 1:47:56 PM EST> <Notice> <JTA> <BEA-110476> <The server has
          > detected pending transactions during graceful shutdown. The server will
          > wait for the pending transactions to complete before suspending the RMI
          > service. A force shutdown command can be issued to shutdown the server
          > immediately.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <Management> <BEA-141080> <A request
          > has been received to force shut down of the server.>
          > <Mar 3, 2004 1:48:26 PM EST> <Alert> <WebLogicServer> <BEA-000228> <The
          > disabling of server logins has been requested by <WLS Kernel>>
          > <Mar 3, 2004 1:48:26 PM EST> <Alert> <WebLogicServer> <BEA-000229>
          > <Server logins have been disabled.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <WebService> <BEA-220028> <Web
          > Service reliable agents are suspended.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <EJB> <BEA-010084> <The
          > message-driven beans are being suspended. This may take a minute or two.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010085> <The
          > message-driven beans have all been suspended.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010084> <The
          > message-driven beans are being suspended. This may take a minute or two.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010085> <The
          > message-driven beans have all been suspended.>
          > [MessageDrivenBeanPoolInfoImpl] : Couldn't unregister MBean
          > javax.management.InstanceNotFoundException:
          > mydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.getMBean(MBeanServerImpl.java:1680)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1524)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.EJBTransactionRuntimeMBean_Stub.preDeregister(EJBTransactionRuntimeMBean_Stub.java:433)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.internalDeleteMBean(MBeanHomeImpl.java:996)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.privateDeleteMBean(MBeanHomeImpl.java:982)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.access$000(MBeanHomeImpl.java:74)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl$2.run(MBeanHomeImpl.java:948)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBeanWithKernelID(MBeanHomeImpl.java:944)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBean(MBeanHomeImpl.java:939)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBean(MBeanHomeImpl.java:933)
          >
          > at
          > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:140)
          >
          > at
          > weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.unregisterDependents(EJBRuntimeMBeanImpl.java:58)
          >
          > at
          > weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.unregisterDependents(MessageDrivenEJBRuntimeMBeanImpl.java:50)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.unInitPool(MessageDrivenBeanPoolInfoImpl.java:208)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.onUndeploy(MessageDrivenBeanPoolInfoImpl.java:121)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:628)
          >
          > at weblogic.ejb20.internal.BaseEJBHome.undeploy(BaseEJBHome.java:203)
          > at
          > weblogic.ejb20.internal.MessageDrivenEJBHome.undeploy(MessageDrivenEJBHome.java:260)
          >
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1802)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > --------------- nested within: ------------------
          > weblogic.management.ManagementException: An error has occurred during
          > preDeregister().
          > nullmydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime
          > - with nested exception:
          > [javax.management.InstanceNotFoundException:
          > mydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime]
          >
          > at
          > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:148)
          >
          > at
          > weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.unregisterDependents(EJBRuntimeMBeanImpl.java:58)
          >
          > at
          > weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.unregisterDependents(MessageDrivenEJBRuntimeMBeanImpl.java:50)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.unInitPool(MessageDrivenBeanPoolInfoImpl.java:208)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.onUndeploy(MessageDrivenBeanPoolInfoImpl.java:121)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:628)
          >
          > at weblogic.ejb20.internal.BaseEJBHome.undeploy(BaseEJBHome.java:203)
          > at
          > weblogic.ejb20.internal.MessageDrivenEJBHome.undeploy(MessageDrivenEJBHome.java:260)
          >
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1802)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > <Mar 3, 2004 1:48:33 PM EST> <Info> <Management> <BEA-141082>
          > <ServerRuntime:java.util.ConcurrentModificationException>
          > <Mar 3, 2004 1:48:33 PM EST> <Info> <Management> <BEA-141082>
          > <ServerRuntime:java.util.ConcurrentModificationException
          > at
          > java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:552)
          > at java.util.LinkedList$ListItr.next(LinkedList.java:488)
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1801)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > >
          > <Mar 3, 2004 1:48:35 PM EST> <Critical> <WebLogicServer> <BEA-000217>
          > <Failed to fully suspend the server due to:
          > java.util.ConcurrentModificationException
          > java.util.ConcurrentModificationException
          > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
          > at java.util.HashMap$KeyIterator.next(HashMap.java:818)
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:751)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.forceSuspend(ApplicationService.java:82)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.forceSuspend(SubsystemManager.java:184)
          > at weblogic.t3.srvr.T3Srvr.forceSuspend(T3Srvr.java:1097)
          > at
          > weblogic.t3.srvr.ServerRuntime.uprotectedForceShutdown(ServerRuntime.java:629)
          >
          > at weblogic.t3.srvr.ServerRuntime.access$300(ServerRuntime.java:83)
          > at weblogic.t3.srvr.ServerRuntime$4.run(ServerRuntime.java:563)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:559)
          > at weblogic.t3.srvr.ServerRuntime.shutdown(ServerRuntime.java:547)
          > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          > at
          > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >
          > at
          > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >
          > at java.lang.reflect.Method.invoke(Method.java:324)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.ServerRuntimeMBean_Stub.shutdown(ServerRuntimeMBean_Stub.java:1184)
          >
          > at
          > weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.execute(ServerLifeCycleRuntime.java:585)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > >
          > <Mar 3, 2004 1:48:35 PM EST> <Debug> <Management> <BEA-141132> <Dynamic
          > invocation while executing action shutdown on
          > mydomain:Location=myserver,Name=myserver,Type=ServerRuntime MBean
          > instance failed. The method shutdown with signature [int, boolean] was
          > invoked with parameters as [30, true].
          > java.util.ConcurrentModificationException
          > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
          > at java.util.HashMap$KeyIterator.next(HashMap.java:818)
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:751)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.forceSuspend(ApplicationService.java:82)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.forceSuspend(SubsystemManager.java:184)
          > at weblogic.t3.srvr.T3Srvr.forceSuspend(T3Srvr.java:1097)
          > at
          > weblogic.t3.srvr.ServerRuntime.uprotectedForceShutdown(ServerRuntime.java:629)
          >
          > at weblogic.t3.srvr.ServerRuntime.access$300(ServerRuntime.java:83)
          > at weblogic.t3.srvr.ServerRuntime$4.run(ServerRuntime.java:563)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:559)
          > at weblogic.t3.srvr.ServerRuntime.shutdown(ServerRuntime.java:547)
          > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          > at
          > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >
          > at
          > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >
          > at java.lang.reflect.Method.invoke(Method.java:324)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.ServerRuntimeMBean_Stub.shutdown(ServerRuntimeMBean_Stub.java:1184)
          >
          > at
          > weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.execute(ServerLifeCycleRuntime.java:585)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > >
          >
          > Tom Barnes wrote:
          >
          >> Hi Dmitri,
          >>
          >> This is normal behavior.
          >> The internal rollbacks are a side effect of WL MDBs
          >> necessarily starting a transaction before they (internally)
          >> post a synchronous
          >> receive on the remote foreign JMS server. If the synchronous receive
          >> receives nothing, the tx is rolled back, and another
          >> synch receive is posted with a new tx. (When interacting with
          >> foreign vendors, tx MDBs usually must post synchronous receives
          >> in order to infect the received message - there is no
          >> standard JMS API for infecting asynchronously received messages
          >> with a user transaction.)
          >>
          >> Tom
          >>
          >> Dmitri Maximovich wrote:
          >>
          >>> Hi everybody,
          >>>
          >>> Is anybody successfully using remote IBM MQseries 5.3 server as
          >>> Foreign JMS in WLS 8.1sp2?
          >>> We're observing some strange behavior in this case. Here is our setup:
          >>>
          >>> WLS and IBM MQ server deployed on separate boxes.
          >>> WLS version 8.1sp2 running on Windows 2000/Intel
          >>> IBM MQ version 5.3 running on Solaris/SPARC
          >>>
          >>> We're using "WebSphere MQ classes for Java, version 5.303 -
          >>> j5303-L030225"
          >>> and "WebSphere MQ Extended Transactional Client Feature, version
          >>> 5.300 - j5303-L030122"
          >>>
          >>> MQ files added in WLS POST_CLASSPATH variable in WLS starup script.
          >>>
          >>> Foreign JMS server configured in WLS via fscontext JNDI.
          >>>
          >>> MDB bean deployed with Transaction attribute "Required".
          >>>
          >>> Everything seems to work fine, if we're posting message to MQ queue
          >>> MDB receives it and process successfully (just print message content
          >>> to the console for now).
          >>>
          >>> Problem: In WLS console, under Server->Monitoring->JTA->Monitor
          >>> inflight transactions we can constantly see one transaction enlisted
          >>> for our MDB bean with following details:
          >>>
          >>> =====================================================
          >>> Transaction ID: BEA1-00DFC5EB4B7B7F28EDB9
          >>> Coordinator: mydomain+myserver
          >>> Name: JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          >>> Status: Active
          >>> Seconds Active: 17
          >>> Resources:
          >>> weblogic.ejb20.JMSConnectionPoller.xxx.xxx.MyMessageProcessorMdb=started
          >>> Properties
          >>> (key=value):
          >>> weblogic.transaction.name=JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          >>> =====================================================
          >>>
          >>> This transaction seems to be Active for 30 seconds and then rolled
          >>> back (no error messages on WLS console displayed).On JTA statistics
          >>> page in WLS console "Total Rolled Back" counter keeps increneting
          >>> with every rollback.
          >>>
          >>> Does anybody observerd similar problem? May be it's normal behaviour
          >>> but I'm kind of worrying about those transactions and constant
          >>> rollback. I'd appreciate any feedback.
          >>>
          >>> ---
          >>> Sincerely,
          >>> Dmitri Maximovich
          >>
          >>
          >>

JMS / MBean WL7 bug

Similar Messages

Maybe you are looking for