Are JMS destinations failover save in WL 7?

Are the JMS destinations now failover save in WL 7? In 6.1 they were not and
          I heard there are still issues with in WL 7. We're in the process of
          evaluating WL 7 and possibly we'd like to use it as our JMS provider.
          What are the know issues of WL 7's JMS implementation in regards to failover
          safety?
          Your comments are appreciated.
          Greetings
          Bernie

Hi Bernard,
          To help support HA,
          WL 7 provides a simplified capability to move a JMS server from one WL
          server to another. (This is called migration in the docs).
          Migration does not occur automatically, but can be activated
          via the command-line or by setting up control via an HA
          framework such as Veritas. The
          relevant files must also be moved (or replicated via SAN,
          dual-port-SCSI, Veritas mirror, etc...) - these include JMS file
          stores and transaction logs.
          WL 7 JMS also provides distributed JMS destinations, these can
          continue to work even if one server goes down. These distributed
          destinations are more advanced than the clustered destinations other
          JMS providers, as well as WL 6.1, provide.
          Google search this newsgroup for "HA", high-availability, and/or
          "distributed" for more info. Also check out the JMS programmer's guide
          as well as the WebLogic admin guide...
          Tom, BEA
          Bernhard Lenz wrote:
          > Are the JMS destinations now failover save in WL 7? In 6.1 they were not and
          > I heard there are still issues with in WL 7. We're in the process of
          > evaluating WL 7 and possibly we'd like to use it as our JMS provider.
          >
          > What are the know issues of WL 7's JMS implementation in regards to failover
          > safety?
          >
          > Your comments are appreciated.
          > Greetings
          > Bernie
          >
          >

Similar Messages

Looking up JMS destinations with clustered WLS

          From scanning the postings, it appears that in a clustered WLS environment, the
          JMS servers are not clustered. As a result, the JMS destinations must be unique
          across all of the WLS in the cluster. In addition, there is no failover available
          when a JMS server goes down.
          With that stated, what I want to know is:
          When establishing a JMS connection with a JMS server in a WLS cluster, do I need
          to know the JNDI URL for each specific JMS server that is managing the destination(s)
          I wish to pub/sub?
          Or, is there a 'global' JNDI tree that I can reference and the clustered WLS behind
          the scenes will route me to the appropriate JMS server?
          If resolving the URL is a manual process, I will need to keep track of which destinations
          reside on which JMS servers. This adds an additional maintenance point that I
          would like to avoid if possible.
          Thanks,
          Bob.


One can use Connection Factory to establish connection to particular
          destination (queue/topic). connection factories are clustered. so, one don't
          need to have knowledge of particular WLS.
          "Neal Yin" <[email protected]> wrote in message
          news:[email protected]...
          > Although there is only one JMS server instance, you can lookup it from
          > anywhere in a cluster.
          > In another words, JNDI tree is global in a WLS cluster. Just give cluster
          > DNS name in your
          > URL, you will be fine.
          >
          > -Neal
          >
          >
          > "Bob Peroutka" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > From scanning the postings, it appears that in a clustered WLS
          > environment, the
          > > JMS servers are not clustered. As a result, the JMS destinations must
          be
          > unique
          > > across all of the WLS in the cluster. In addition, there is no failover
          > available
          > > when a JMS server goes down.
          > >
          > > With that stated, what I want to know is:
          > >
          > > When establishing a JMS connection with a JMS server in a WLS cluster,
          do
          > I need
          > > to know the JNDI URL for each specific JMS server that is managing the
          > destination(s)
          > > I wish to pub/sub?
          > >
          > > Or, is there a 'global' JNDI tree that I can reference and the clustered
          > WLS behind
          > > the scenes will route me to the appropriate JMS server?
          > >
          > > If resolving the URL is a manual process, I will need to keep track of
          > which destinations
          > > reside on which JMS servers. This adds an additional maintenance point
          > that I
          > > would like to avoid if possible.
          > >
          > > Thanks,
          > >
          > > Bob.
          > >
          > >
          > >
          >
          >

[svn:bz-trunk] 19866: Set delivery mode to PERSISTENT for JMS destinations that have durable set to true .

Revision: 19866
Revision: 19866
Author:   [email protected]
Date:     2011-01-21 10:05:44 -0800 (Fri, 21 Jan 2011)
Log Message:
Set delivery mode to PERSISTENT for JMS destinations that have durable set to true. If messages aren't persistent they won't be saved by the JMS server. This is kind of important when you want the messages to be durable.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/messaging-config.mods.xml

According to Bea Customer Support this is the normal behavior. If you kill a durable topic subscriber and reconnect it with the same id to another node, the old subscription is deleted and all messages still waiting to be delivered are gone.
          Lesson learned: If you need failover for the server AND client use JMS queues.
          Peter

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!

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.
          > > > >
          > > > >
          > > > >
          > > >
          > > >
          >

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)

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

Setting up Foreign JMS Dest. to MQ: JMS Destination not found

I'm trying to set up a foreign JMS destination to an MQ queue. There are several steps you have to get right for this to work. I thought I did them all correctly, but when I deploy the app with an MDB that references the JNDI name, it says (in the console) that the destination with the particular JNDI name could not be found.
          I first used JMSAdmin to create the JNDI data in the provider URL file location. I created the qcf and the queue. I've displayed my results that I set with that, and it all looks fine. One thing that I'm unsure about with this, however, is that the document on using JMSAdmin doesn't make it clear exactly which field in the "queue" definition is the JNDI name, and which is the MQ queue name. My guess is that the value of the "q" field is the JNDI name, and the value of the "queue" field is the MQ queue name. I'm not certain.
          I then created the foreign JMS info in the WebLogic console. I first created the foreign JMS server, using the "RefFSContextFactory" class, and my file location for the provider URL.
          I then created the foreign JMS ConnectionFactory, specifying my JNDI name in both the "local" and "remote" fields. I don't know what the difference is between those two. I did NOT enter a value in the "User Name" or "Password" fields. I don't know whether that's an issue.
          I then created the foreign JMS destination. I set the "local" and "remote" JNDI values to the JNDI value I set in the "q" field in JMSAdmin.
          I then defined an app using an MDB, with the "destination-jndi-name" set to the same value I set in the "q" field.
          When I deployed the app, I saw an error message on the console saying that when deploying the EJB module, the JNDI name (that I had specified in the "q" field) could not be found.

David,
          first you should check, whether the JNDI-Entry is deployed. You can
          check this by displaying the jndi-tree on the weblogic console. to do
          this, right click on the server entry and select "view jndi tree".
          the point with the jndi-tree you entered as "local jndi destination"
          should be violet.
          in the definitions of foreign jms-destinations and connection factories
          you always set:
          remote jndi name: the entry which you made in JMSADMIN
          local jndi name: the jndi entry you want to use inside weblogic.
          hope this helps,
          Klaas
          David Karr schrieb:
          > I'm trying to set up a foreign JMS destination to an MQ queue. There are several steps you have to get right for this to work. I thought I did them all correctly, but when I deploy the app with an MDB that references the JNDI name, it says (in the console) that the destination with the particular JNDI name could not be found.
          >
          > I first used JMSAdmin to create the JNDI data in the provider URL file location. I created the qcf and the queue. I've displayed my results that I set with that, and it all looks fine. One thing that I'm unsure about with this, however, is that the document on using JMSAdmin doesn't make it clear exactly which field in the "queue" definition is the JNDI name, and which is the MQ queue name. My guess is that the value of the "q" field is the JNDI name, and the value of the "queue" field is the MQ queue
          > name. I'm not certain.
          >
          > I then created the foreign JMS info in the WebLogic console. I first created the foreign JMS server, using the "RefFSContextFactory" class, and my file location for the provider URL.
          >
          > I then created the foreign JMS ConnectionFactory, specifying my JNDI name in both the "local" and "remote" fields. I don't know what the difference is between those two. I did NOT enter a value in the "User Name" or "Password" fields. I don't know whether that's an issue.
          >
          > I then created the foreign JMS destination. I set the "local" and "remote" JNDI values to the JNDI value I set in the "q" field in JMSAdmin.
          >
          > I then defined an app using an MDB, with the "destination-jndi-name" set to the same value I set in the "q" field.
          >
          > When I deployed the app, I saw an error message on the console saying that when deploying the EJB module, the JNDI name (that I had specified in the "q" field) could not be found.

Using a Foreign JMS Destination as a JMS Event Generator Subscription

NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
problem here. From the wliconsole, the only queues listed to have events
generated from are local ones.
Hello,
I'm trying to create a workflow that is started by a JMS message queue
event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
queue
on a remote WebLogic 8.1 installation, publish the incoming messages to
a channel,
then initiate a workflow by subscribing to that channel. Here's a copy
of my configuration
file for the tool:
<message-broker-jms-event-generator-def
source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection
Factory,
and Destination using the Weblogic Admin Console. Below are the
parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name:
weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name:
InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the
following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure
that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in
my configuration.
I found the existing BEA documentation to be a bit too generic,
containing no
specific examples of the proper syntax to use for this task. Can anyone
offer
any advice or better, a working example? Any BEA reps out there?

NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
problem here. From the wliconsole, the only queues listed to have events
generated from are local ones.
Hello,
I'm trying to create a workflow that is started by a JMS message queue
event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
queue
on a remote WebLogic 8.1 installation, publish the incoming messages to
a channel,
then initiate a workflow by subscribing to that channel. Here's a copy
of my configuration
file for the tool:
<message-broker-jms-event-generator-def
source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection
Factory,
and Destination using the Weblogic Admin Console. Below are the
parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name:
weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name:
InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the
following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure
that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in
my configuration.
I found the existing BEA documentation to be a bit too generic,
containing no
specific examples of the proper syntax to use for this task. Can anyone
offer
any advice or better, a working example? Any BEA reps out there?

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.

JMS destinations disappear from JNDI after appserv restart

I am using the PE 8.1 2005Q1 application server. I create a jms resource as jms/myQueue and I can see it using the JNDI browser.
However, after restarting the application server, my destinations still show up under JMS Destinations & Admin Object Resources, but disappear from the JNDI browser and are unavailable to clients!
Do I need to perform an addtional step in order to get the appserver to persist these jndi registrations? There appears to be a disconnect between JMS and JNDI. Any help is greatly appreciated.

JMS has a ForeignJMSProvider config option to do this I believe. 9.0 will also support this more generally.

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

Are JMS destinations failover save in WL 7?

Similar Messages

Maybe you are looking for