JMX Removing JMS Destination

Am using the following:
JMSServerMBean to get a list of JMS Destinations and trying to call
the removeDestination I get the following on the weblogic log:
<Nov 26, 2001 5:27:01 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion BECKER will be removed when JMS starts again.>
<Nov 26, 2001 5:27:01 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion BEST will be removed when JMS starts again.>
<Nov 26, 2001 5:27:01 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion PRIMARKI will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion LATTICEB will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion BRASSI will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion ESI will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion Party2 will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion Group4 will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion HARVARD will be removed when JMS starts again.>
<Nov 26, 2001 5:27:02 PM EST> <Info> <JMS> <JMSServer "AutexJMSServer",
des
ion Party1 will be removed when JMS starts again.>
However when I shutdown weblogic and bring it back up the destinations
are still there.. Is there a way to programatically remove destinations
via mbeans
that works. I am aware that I have to use JMSHelper to add them
otherwise
they dont get written to the config file??
BTW the documentation for this stinks.

Hello Ken,
Actually, when you register the destination in the JMS Connector Service, you are also creating an entry in the JNDI Registry of the Web AS, which you can use to look up the destination in your application. Furthermore, using a resource environment reference (relevant for J2EE applications), you can define an arbitrary lookup name for the destination, so the physical one does remain hidden. Hope this answers your question.
Best regards,
Zornitsa

Similar Messages

Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

Hi
This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
* Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
* Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
* Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
* The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
<Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
weblogic.jms.common.JMSException: Destination not found
weblogic.jms.common.JMSException: Destination not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Edited by: user8773992 on Sep 2, 2009 11:31 AM

1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
Tom

Browse jms destinations on managed servers (from admin server)

I need to browse JMS destinations from the admin server (in a WebLogic
9.2 console extension) that are only deployed on the managed servers.
I can get destination attributes via the domain runtime server, but
no JNDI or actually browse the destinations. All destinations in
which I am interested are queues.
I know I can change my initial context, but if that is the way to go, is there a way to determine the managed
servers' URLs at runtime?
Thank you for any help,
Seth

hi
this worked for me (on 8.1). I suppose there are
better ways in 9.2
Context adminCtx = null;
adminCtx = getInitialContextForAdminServer();
MBeanHome adminhome = (MBeanHome)
adminCtx.lookup(MBeanHome.ADMIN_JNDI_NAME);
// Get the list of running managed
ning managed servers and iterate over itSet
Set srSet =
Set srSet =
adminhome.getMBeansByType("ServerRuntime");
Iterator sr_iter = srSet.iterator();
while (sr_iter.hasNext())
ServerRuntimeMBean bean =
timeMBean bean = (ServerRuntimeMBean) sr_iter.next();
// Get the home for the managed
for the managed server
MBeanHome remoteHome = (MBeanHome)
me = (MBeanHome) adminCtx.lookup(MBeanHome.JNDI_NAME
+ "." + bean.getName());
// Get the MBeanServer for the
anServer for the managed server
MBeanServer rmbs =
eanServer rmbs = remoteHome.getMBeanServer();
//invoke it
ObjectName objectName= new
objectName= new ObjectName("$mbean");
rmbs.invoke(objectName,operation,params,types);
Edited by deepshet at 05/05/2007 10:00 AMThank you for the help.
MBeanHome is deprecated as of 9.0, so I was unable to directly use your example. You have helped though, thank you.
As of now I am querying the domain runtime server for:
ObjectName("com.bea:*,Type=ServerRuntime")
I am then iterating through the returned Set to get the server URLs and then setting my InitialContext with a PROVIDER_URL of the managed servers. This allows me to Look Up a Destination without JNDI based on step 4 from [url http://edocs.bea.com/wls/docs92/jms/implement.html#wp1313933]here. I can then browse as needed.
The ugly part is that if I include the Admin URL in my PROVIDER_URL then it does not work, so I am checking for it as I loop through the set of ServerRuntimes and not including it.
Further though slightly less annoying is that the managed server URLs include "t3://" but if I leave it in there, a malformed URL exception is thrown when setting the PROVIDER_URL. So I also remove all of those and then preppend one on the front for PROVIDER_URL as I actually need.
It is not pretty, but it is working on the only cluster I have been able to try thus far.
If anyone was a cleaner suggestion, please share.

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

JMS Destination object not found

Hi everyone,
I have a weird problem with SunONE Message Queue 3.
I have a queue and a connection factory defined (using the SunONE Application Server 7 Admin Console) as well as a physical resource.
I can verify their existance using asadmin....
asadmin>list-jmsdest -u admin server1
queue_1 queue {}
asadmin>list-jms-resources -u admin server1
jms/newqueue_1
jms/newQCF_1
When I attempt to deploy a message driven EJB I get the following error
SEVERE ( 1484): javax.naming.InvalidNameException: JMS Destination object not found:`jms/newqueue_1`
This question has already been asked on the App Server board here http://swforum.sun.com/jive/thread.jspa?threadID=15517&tstart=0 (that post is nine months old btw).
I am posting this here in the hope that someone more familiar with MQ3 may have an idea of how to help us.
Thanks in advance.

I have now solved this problem. External JNDI resources are required in the AppServer.
They can be created with the following commands:
asadmin>create-jndi-resource jndilookupname jms/newQCF_1 resourcetype javax.jms.QueueConnectionFactory factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi:java.naming.security.authentication=none newQCF_1
asadmin>create-jndi-resource jndilookupname jms/queue_1 resourcetype javax.jms.Queue factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi newqueue_1
Both these commands assume that the file system context is being used however the LDAP commands are similar (just more properties).
This step, which seems vital, is missing from the AppServer documentation (in fact it specifically states that this step is not necessary). The irony is that I found the answer in the IBM MQ documentation!

Producing message to temporary JMS destination

Hi,
Has anyone managed to produce a message to a temporary JMS destination using the JMS Adapter? I'm trying to get this request/reply-pattern working:
-Java client connects to a Connection Factory and creates a temporary reply queue (works, CF returns a destination like "TestingJmsServer!TestingJmsServer.TemporaryQueue2")
-The client produces a message with JMSReplyTo pointing to the temporary reply queue (works)
-JMS Adapter consumes the message and assigns jca.jms.JMSDestinationName := jca.jms.JMSReplyTo (works)
-The JMS adapter should now produce the reply message to the provided temporary queue, but it always fails with error BEA-045101:
The destination name passed to createTopic or createQueue "destName" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned.
The same problem occurs with fixed queues, like "TestingJmsModule!ReplyQueue", but I can make them work by adding a "./" in front of the destination name when performing the jca.jms.JMSDestinationName assign, so that it reads "./TestingJmsModule!ReplyQueue". After that the adapter is able to produce the message correctly to the given JMSDestinationName.
Is it significant that with fixed queues I get a destination like "JmsModule!FixedQueueName" (note the module) but with temporary destinations it is like "JmsServer!TempQueueName" (note the server)?
Should the destination name be of some other format? The current value is exactly what the Connection Factory returns, and if the JMS adapter is replaced with another java client, producing the reply message to that destination works just fine.
regards,
Ville

Hi,
I am trying to send messages to the WLS queue through Camel and facing the same issue, which can be eliminated by using queue name as ./<QUEUE_NAME>.
However it only eliminates the error and the next one comes is real pain. It is not able to find the JNDI name of the queue, where as I am able to see it in Admin console JNDI tree.
Exception in thread "Main Thread" org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[Message: Test Message: 0]
     at org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1161)
     at org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:512)
     at org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:441)
     at org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:437)
     at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:125)
     at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:130)
     at org.apache.camel.example.jmstofile.PublishMessage.main(PublishMessage.java:63)
Caused by: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is weblogic.jms.common.JMSException: [JMSExceptions:045102]A destination of name "WLtestQueue" was not found on WLS server "AdminServer".
     at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
     at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168)
     at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469)
     at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:172)
     at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:347)
     at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:303)
     at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:101)
     at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:102)
     at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:104)
     at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:85)
     at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:63)
     at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:345)
     at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:317)
     at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:222)
     at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:317)
     at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:168)
     at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:110)
     at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:123)
     ... 2 more
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045102]A destination of name "WLtestQueue" was not found on WLS server "AdminServer".
     at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
     at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
     at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
     at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
     at weblogic.jms.client.WLSessionImpl.createQueue(WLSessionImpl.java:938)
     at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveQueue(DynamicDestinationResolver.java:101)
     at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveDestinationName(DynamicDestinationResolver.java:66)
     at org.springframework.jms.support.destination.JmsDestinationAccessor.resolveDestinationName(JmsDestinationAccessor.java:100)
     at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.access$200(JmsConfiguration.java:141)
     at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate$3.doInJms(JmsConfiguration.java:174)
     at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
     ... 17 more
Anyone has got any idea?

Additional JMS Destination Attributes

How can I associate additional attributes to an Administered Object in
          JNDI? Specifically, I want to add a JMS Destination (Queue) to the
          JNDI context. I want the Queue to also have 2 additional attributes
          for my application to process. The additional attributes I need to
          associate with the Administered Queue Object are: Reply-To-Queue and a
          boolean value (log message or don't log message).
          I went into the JNDI namespace (iPlanet Directory Server in this
          case), and manually added additional attributes in the
          javaReferenceAddress. The JMS API did not choke on this, but I can't
          figure out a way to expose this either.


I found that if I in the JMS receiver queue tick Specify Additional JMS Message Properties (Maximum of 10) and provide the name JMSReplyTo and the value Sting I can collect the ReplyTo queue name via a parameter in the operation mapping and the value of that parameter I can set to the Dynamic Configuration variable DCJMSMessageProperty0 in a UDF like this:
String x = container.getInputParameters().getString("replyToQueueName");
DynamicConfiguration conf1 = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION) ;
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS", "DCJMSMessageProperty0") ;
conf1.put(key1, x);
return "";

JMS Destinations in a cluster

I'm having a problem getting managed nodes in a cluster to find JMS Queues
          and Topics.
          The Connection Factory is found, but the destinations are not.
          I have targeted the JMS Server to one node in the cluster.
          I have targeted the Connection Factories to the cluster.
          Is there something else that needs to be done to get the destinations
          available to the cluster?
          When I view the JNDI tree of the slave nodes, the destinations just are not
          there. I wait and wait and they don't show up.
          A.M.


I have a question that relates to this discussion.
          When I deploy a topic on a cluster I am only allowed to deploy it on one
          JMSServer. Trying to deploy it on more than one gives me a JNDI error
          (duplicate name). This works fine, however, and messages are delivered to
          all members of the cluster. But if I kill off the server where the
          destination topic exists, that topic disappears from the cluster and further
          messages cannot be delivered. Weblogic tells me that the topic does not
          exist. My question is - how do I get the topic to survive the failure of
          the server on which it is deployed? Why doesn't replication keep the topic
          alive?
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Note that the admin server does not participate in the cluster so
          > it doesn't participate in JNDI replication. If JMS destinations
          > exist on the admin server one must use a JNDI context
          > that is pinned to the admin server to find them... Same deal
          > with connection factories that can talk to the admin server.
          >
          > Zach wrote:
          >
          > > Could you please post your config.xml file (the one that doesn't
          > > work where the JMS server is deployed to the admin server).
          > > _sjz.
          > >
          > > "Asynch Messaging" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > I found that we were attempting to deploy the JMS Server to the
          'admin'
          > > > server, rather than a managed server.
          > > > This apparently is not allowed.
          > > >
          > > > A.M.
          > > >
          > > > "Asynch Messaging" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > I'm having a problem getting managed nodes in a cluster to find JMS
          > > Queues
          > > > > and Topics.
          > > > > The Connection Factory is found, but the destinations are not.
          > > > >
          > > > > I have targeted the JMS Server to one node in the cluster.
          > > > > I have targeted the Connection Factories to the cluster.
          > > > >
          > > > > Is there something else that needs to be done to get the
          destinations
          > > > > available to the cluster?
          > > > > When I view the JNDI tree of the slave nodes, the destinations just
          are
          > > > not
          > > > > there. I wait and wait and they don't show up.
          > > > >
          > > > > A.M.
          > > > >
          > > > >
          > > > >
          > > >
          > > >
          >

[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

A JMS destination limit was reached.

Hi,
I encounter en error when I deploy an application under Application Server 9.
I got the following error message :
A JMS destination limit was reached. Too many Subscribers/Receivers for Queue : NewMessage user=guest, broker=localhost:7676(2832)What I need to configure / change / adapt my code ? I use the Click Framework to retrieve a Facade :
    /** Creates a new instance of Hello */
    public Hello() {
        tableToto = new Table();
        if (newsEntityFacade == null) newsEntityFacade = lookupNewEntityFacade();
        tableToto.setClass("simple");
        tableToto.setPageSize(40);
        tableToto.setName("tableToto");
        tableToto.addColumn(new Column("id"));
        tableToto.addColumn(new Column("title"));
        tableToto.addColumn(new Column("body"));
        index = 0;
        max = newsEntityFacade.count();
        rowByPage = tableToto.getPageSize();
        tableToto.setRowCount(max / rowByPage);
private NewEntityFacadeLocal lookupNewEntityFacade() {
        try {
            Context c = new InitialContext();
            return (NewEntityFacadeLocal) c.lookup("java:comp/env/ejb/NewEntityFacade");
        catch(NamingException ne) {
            Logger.getLogger(getClass().getName()).log(Level.SEVERE,"exception caught" ,ne);
            throw new RuntimeException(ne);
    }And my Facade is declared as @Stateless

I've checked that topic earlier before I have posted mine, but at that time it didn't strike me! Now, I realize the exact problem!
I need to undeploy my message-driven bean tutorial example, which was using the same queue!
Thanks.

Javax.jms.Destination found at the specified.....

I am making a Message Driven EJB, but i get this error when i try to run it."javax.jms.Destination found at the specified destination-location (jms/theTopic) for MessageDrivenBean MessageDrivenEJB".I am using JDeveloper 9.0.5
My ejb-jar
<enterprise-beans>
<message-driven>
<description>Message Driven Bean</description>
<display-name>MessageDrivenEJB</display-name>
<ejb-name>MessageDrivenEJB</ejb-name>
<ejb-class>mypackage1.MessageDrivenEJBBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<resource-ref>
<res-ref-name>TopicFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
</enterprise-beans>
<assembly-descriptor/>
</ejb-jar>
My orion-ejb-jar
<orion-ejb-jar>
<enterprise-beans>
<message-driven-deployment name="MessageDrivenEJB" destination-location="jms/theTopic" connection-factory-location="jms/theTopicConnectionFactory">
<resource-ref-mapping name="The Topic" location=" jms/theTopic"/>
</message-driven-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
and my jms.xml
<topic name="The Topic" location="jms/theTopic">
<description>A dummy topic</description>
</topic>
<topic-connection-factory name="jms/theTopicConnectionFactory" location="jms/theTopicConnectionFactory">
<description>A dummy topic connection factory</description>
</topic-connection-factory>
I hope that there i somebody who can help.. :-)

The files orion-ejb-jar and jms.xml are not defined in JMS or Java EE, so unless there are any Orion experts on this forum you may need to ask in a forum specific to your application server.
Nigel

OSB : Alert Destination not alerting on the JMS destination Topic

Hi,
I am using OSB alert destination to alert on an SLA alert of a proxy service.
The alert destnation configuration has a JMS destination of Topic type. Syntax which i followed is jms://localhost:8011/weblogic.JmsConnectionFactory/weblogic.ReportingTopic
I am able to see the alerts on the dashboard but then i cannot get the alert on topic.
I could see the below exception in log file:
Alert Rule Name: test.
com.bea.wli.sb.transports.TransportException: [JMSClientExceptions:055091]Destination JmsModule!ReportingTopic must be a queue
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:570)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:681)
     at sun.reflect.GeneratedMethodAccessor1206.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy123.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:490)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:346)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:67)
     at com.bea.alsb.alert.sla.SlaAlertManager.generateAlert(SlaAlertManager.java:149)
     at com.bea.alsb.alert.sla.SlaAlertManager.access$100(SlaAlertManager.java:33)
     at com.bea.alsb.alert.sla.SlaAlertManager$RuleListenerForAlertGeneration.onRuleTrue(SlaAlertManager.java:227)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.invokeListener(RuleEngine.java:76)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.access$000(RuleEngine.java:61)
     at com.bea.alsb.rule.RuleEngine.addFact(RuleEngine.java:115)
     at com.bea.alsb.alert.sla.SlaAlertManager.intervalCompleted(SlaAlertManager.java:202)
     at com.bea.alsb.alert.sla.TaskCollector$RuleEvaluationTask.run(TaskCollector.java:177)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:139)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
     at java.lang.Thread.run(Thread.java:619)
In the alert destination i selected the destination type as topic. Is there anything i am missing. I checked the documentation it says that the jms destination in alert destination can be Queue/Topic. Please suggest. Thanks in advance

A topic wont persist the message, unlike a queue, if there are no subscribers attached to it currently or if there are no durable subscriptions. Create a proxy service to consume the alert from the topic and see whether you are getting it within the proxy's pipeline.

JMS Exception - unable to connect to the JMS destination

Hi,
I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
I am geeting the following JMS destination not found exception while starting the Second Managed Server.
There are no errors occurred in the First Managed Server.
{color:#ff0000}<Warning> <EJB> <BEA-010061>
<The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2>{color}
Configuration Details:
##config.xml:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]">
<name>efpdomain</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration>
<name>efpdomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{3DES}Q2xO0EiChbay/HkRiorTjg==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>192.168.12.240</listen-address>
</server>
<server>
<name>efpserver_man1</name>
<listen-port>8011</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>efpserver_man2</name>
<listen-port>8012</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>efpcluster</name>
<cluster-address>192.168.12.240:8011,192.168.12.240:8012</cluster-address>
<multicast-address>239.192.0.0</multicast-address>
</cluster>
<embedded-ldap>
<name>efpdomain</name>
<credential-encrypted>{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
<name>efp</name>
<target>efpcluster</target>
<module-type>ear</module-type>
<source-path>applications\efp.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<xml-registry>
<name>XMLEFP</name>
<document-builder-factory>weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
<sax-parser-factory>weblogic.apache.xerces.jaxp.SAXParserFactoryImpl</sax-parser-factory>
<transformer-factory>weblogic.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
</xml-registry>
<jms-server>
<name>eFpJMSServer</name>
<target>efpserver_man1 (migratable)</target>
<persistent-store>eFpJMSJDBCStore</persistent-store>
</jms-server>
<jms-server>
<name>eFpJMSServer2</name>
<target>efpserver_man2 (migratable)</target>
<persistent-store>eFpJMSJDBCStore2</persistent-store>
</jms-server>
<migratable-target>
<name>efpserver_man1 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<migratable-target>
<name>efpserver_man2 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<jdbc-store>
<name>eFpJMSJDBCStore</name>
<prefix-name>WLJMS_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man1 (migratable)</target>
</jdbc-store>
<jdbc-store>
<name>eFpJMSJDBCStore2</name>
<prefix-name>WLJMS2_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man2 (migratable)</target>
</jdbc-store>
<jms-system-resource>
<name>eFPJMS</name>
<target>efpcluster</target>
<sub-deployment>
<name>eFPServer</name>
<target>eFpJMSServer</target>
</sub-deployment>
<sub-deployment>
<name>eFPServer2</name>
<target>eFpJMSServer2</target>
</sub-deployment>
<descriptor-file-name>jms/efpjms-jms.xml\JMS Description-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>eFpDataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpDataSource-2004-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>eFpNonXADataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpNonXADataSource-6172-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
##JMS Description-jms.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]">
<connection-factory name="ConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/ConnectionFactory</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<connection-factory name="XAConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/XAConnectionFactory</jndi-name>
<transaction-params>
<transaction-timeout>3600</transaction-timeout>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<uniform-distributed-queue name="ActiveActivityQueue">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>queue/efpActiveActivityQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-topic name="AdminTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAdminTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="AuditTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAuditTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ErrorTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpErrorTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="FreeTextTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpFreeTextTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ReportingTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpReportingTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
-----

Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
<Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
e Error was:
oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
ommon.resourcepool.ResourceLimitException: No resources currently available in p
ool TestDataSource to allocate to applications, please increase the size of the
pool and retry..
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
(ResourcePoolImpl.java:555)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:322)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:438)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:317)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
1670)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
468)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:355)
at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
ava:214)
at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
s(JMSConnectionPoller.java:1545)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
on(JMSConnectionPoller.java:2047)
at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
tionPoller.java:787)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
lling(MDConnectionManager.java:244)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
enManager.java:584)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
art(MessageDrivenBeanInfoImpl.java:1334)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
EJBDeployer.java:1669)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
93)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
ListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
ulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
va:1269)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
oduleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
entStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
pContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
tivate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
tivateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Commit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
mmit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
ymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
mit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

MDB cannot connect to JMS destination using Foreign Server

Hi everyone,
I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
I would really appreciate if anyone could help me.
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
MDB annotation looks like this:
@MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public class SmsReceiverBean implements MessageListener
weblogic-ejb-jar.xml excerpt:
     <weblogic-enterprise-bean>
          <ejb-name>SmsReceiver</ejb-name>
          <message-driven-descriptor>
               <pool>
                    <max-beans-in-free-pool>10</max-beans-in-free-pool>
                    <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
               </pool>
               <connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <transaction-descriptor>
               <trans-timeout-seconds>600</trans-timeout-seconds>
          </transaction-descriptor>
<dispatch-policy>MdbSmsWorkManager</dispatch-policy>
     </weblogic-enterprise-bean>
and the configuration of foreign-server:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
<foreign-server name="serverr">
<sub-deployment-name>Subdeployment</sub-deployment-name>
<foreign-destination name="sms queue>
<local-jndi-name>xcg2/smsInQueue</local-jndi-name>
<remote-jndi-name>jmsxcg.out</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="Connection Factory">
<local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
<remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
</foreign-server>
</weblogic-jms>
PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configuration

Hmm - I'm not sure what's going on. Two thoughts --
Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
@MessageDriven(
name = "MyMDB",
activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType",
                              propertyValue = "javax.jms.Queue"),
    @ActivationConfigProperty(propertyName = "destinationJndiName",
                              propertyValue = "MyQueue") // Ext. JNDI Name
)HTH,
Tom

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

JMX Removing JMS Destination

Similar Messages

Maybe you are looking for