WLST create JMS Server

Does anyone know the difference between the following commands to create JMS resources using WLST?
cmo.createJMSServer('myJMSServer');
vs
create('myJMSServer', 'JMSServer')

Hello,
You can use both.
the cmo.createJMSServer is 'java' code.
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst

Similar Messages

Offline WLST changes JMS Server Target From a Migratable target

I have a simple WL 9.2mp2 domain which has 2 managed servers, one JMS Server and two migratable targets (one for each managed server) and the JMS server is targeted to one of the migratable targets. When I read the domain into WLST offline, the JMS server's target is changed from the migratable target to the preferred server defined in the migratable target. Is this a bug in WLST? Am I missing some option on WLST that can fix this?
          I saw a similar posting for 8.1 and no resolution.
          Thanks in advance,
          Mark.

Hi
          Please find my answers below:
          Q1:
          It depends how you configured the JMSSevers.
          If both the JMSServers are targeted to the same MigratableTarget, then you do the migration only once, that will move both of them to the new active server.
          If not, you have to perform the migration once for each MT.
          Q2:
          No, you dont have to start the Managed Server II, unless otherwise you wanted it to be readily available for the migration next time.
          Q3:
          You can just repeat the migration process by specifying the destination as Maganged Server-I this time. You dont need change the configuration for this, since the MT, shall already have the Candidate servers M1 and M2 and both JMSServers are targeted to MT.
          Q4:
          Yes, as long as the CF is targeted to the cluster, your connection is valid. But your destinations references will become invalid after migration, so you have to have some logic in the exception listeners to reconnect again.
          Hope this helps.

Creating data server for JMS Queues in ODI

hi,
I am trying to create data server for JMS Queues in ODI.
I am getting following error:
java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: Cannot find the Connection Factory (jms/QueueConnectionFactory) in JNDI'.
To implement this, I am giving following parameters:
JNDI driver : com.evermind.server.rmi.RMIInitialContextFactory
JNDI url : ormi://localhost/default
JNDI resource : jms/QueueConnectionFactory
Please help.
Thanks,
Monika

Hi,
according to docs
http://docs.oracle.com/cd/E23943_01/integrate.1111/e12644/hypersonic_sql.htm#ODIKM590
i see
JDBC Driver: org.hsqldb.jdbcDriver
JDBC URL: jdbc:hsqldb:hsql://<host>:<port>
could you modify
JDBC Driver : org.hsqldb.jdbc.JDBCDriver
JDBC Url : jdbc:hsqldb:hsql://localhost
according to docs?
Thanks

When to create a separate JMS Server

Gurus
Please provide/point to guidelines on when to create a separate JMS server within the Weblogic server 11g, the Pros and Cons of doing the same.
From Oracle JMS Guide for Weblogic , the main value add I am able to see is the separate Persistent store and a separate logical container for JMS resources related to my project. These will be important value additions since we will be using a shared environment where artifacts from multiple projects will be deployed.
I researched online , but could not get more inputs. Appreciate any pointers.
regards
Basu

There is a JMS Server and Persistent Store section in the JMS configuration best practices book.
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#CACGFHDJ
Hope this is helpful to you.

Create jms queue xml data server

Hi,
What's the difference between jms queue and jms queue xml data servers and how to create jms queue xml data server.
Thanks.

Hello,
JMS messages can principally be processed by Oracle Data Integrator in two formats:
- JMS Messages: containers for rows of data, handled through JMS Queue/JMS Topic Technologies. With JMS Queue/JMS Topic technologies, each JMS destination is defined similarly to a flat file datastore. Each message in the destination is a record in the datastore.
- XML Messages: containers for XML files, handled through JMS XML Queue/JMS XML Topic Technologies. With JMS XML Queue/JMS XML Topic technologies, each messages payload contains a complete XML data structure. This structure is mapped into a relational schema (XML Schema) which appears as a model. This use the Oracle DI Driver for XML (see the driver documentation in Oracle DI documentation).
Find below a step by step creation process for such a destination:
1. Data Server
To create a JMS XML Queue data server, you declare a simple JNDI connection. The only JMS XML specific information is added to the URL. This information defines the XML file format.
The JNDI URL should be : <JMS_RESOURCE>?d=<DTD_FILE>&f=<XML_FILE>&s=<SCHEMA>&JMS_DESTINATION=<JMS_DESTINATION_NAME>
- JMS_RESOURCE: JNDI resource corresponding to your JMS queue that will contain the XML payload. You would specify this URL if you were managing normal JMS messages.
- DTD_FILE: path to a DTD file that describes the XML structure. Mandatory if the parameter XML_FILE is omitted.
- XML_FILE: path to the XML file with a structure similar to the expected XML messages. Mandatory if the DTD_FILE parameter is omitted.
- SCHEMA: schema name that will contain the XML structure. This value must match the one set for the physical schema attached to this data server. This parameter is mandatory.
- JMS_DESTINATION_NAME: name of the JMS queue or topic. This parameter is mandatory.
2. Schema
Creation is straightforward: In the Schema (Schema) and Schema (Work Schema), enter the name of the <SCHEMA> defined in the data server JNDI URL.
3. Model
Use standard reverse-engineering. As the Oracle DI Driver for XML is used the XML structure will be reversed as a relational structure.
Regards,
- FX

JMSHelper throws 'JMS server is not targetted' creating distributed queue

I am trying to use the 8.1 weblogic.jms.extensions.JMSHelper to create a distributed queue. The target JMS servers are all migratable servers. When calling method createDistributedQueueAsync() I get a JMSException thrown compaining that the [first] JMS server is not targetted. Looking at the code provided in [http://forums.bea.com/bea/thread.jspa?messageID=200023386] which is based on the JMSHelper class source, the exception may be thrown because the target MBean is of class MigratableTargetMBean, whereas the JMSHelper is expecting class TargetMBean. Yet, the 9.0 documentation (which at least documents it) suggests that MigratableTargetMBean is derived from TargetMBean
          Does anyone have experience of this issue or its resolution, short of crafting the code by hand as per the above-referenced reply?

Hi,
Just to remember the configuration: 2 managed servers configured as cluster that should be deployed on 2 different machine.
Following summary of the tests:
     - node manager + admin server + 1 managed server running on the first machine --> server failed to init with error "Server is not in the majority cluster partition"
     - node manager + admin server + 2 managed servers running on the one machine --> servers are running without errors
     - node manager + admin server + 1 managed server running on the first machine / node manager runs on the second machine --> server on the first machine runs without errors without the famous error ' Server is not in the majority cluster partition'.
Bottom line, seems that if the node manager is not running on the remote machine, the cluster is not in a stable state and so the single managed server failed to initialize.
Is it according the documentation / expectations ?
Thanks,
Yaakov

How to create a server through WLST ( Weblogic Scripting Tool ) ?

How to create a server through WLST ( Weblogic Scripting Tool ) ?
Thanks in advance...
Sanjay

Hi Murugesh,
Thanks a lot for you reply..
I was able to create a server using create(). Is it possible to clone a server ?
When i create a server following tags is added to config.xml
<server>
<name>testServer_lab1</name>
<listen-port>43000</listen-port>
</server>
And if i do a clone through admin console, following is added to config.xml
<server>
<name>testServer2_lab1</name>
<machine xsi:nil="true"></machine>
<listen-port>7001</listen-port>
<cluster xsi:nil="true"></cluster>
<listen-address></listen-address>
<graceful-shutdown-timeout>120</graceful-shutdown-timeout>
</server>
If incase, cloning is not possible through WLST, can i add following
<machine xsi:nil="true"></machine>
<listen-port>7001</listen-port>
<cluster xsi:nil="true"></cluster>
<listen-address></listen-address>
<graceful-shutdown-timeout>120</graceful-shutdown-timeout>
under <server> tag which is created through WLST ?
I am using 9.2 version.
Regards
Sanjay

[OSB10.3.1] err creating JMS stuff in OSB cluster from recorded WLS session

Hi all,
I've setup an OSB cluster with 2 managed servers.
From WLS console I created successfully the below JMS resources:
1. new file store, name and directory: MyFileStore_m01, target: bnk01osbm01 migratable
2. new file store, name and directory: MyFileStore_m02, target: bnk01osbm02 migratable
3. new jms server, name: MyJMSServer_m01, persistent store: MyFileStore_m01, target: bnk01osbm01 migratable
4. new jms server, name: MyJMSServer_m02, persistent store: MyFileStore_m02, target: bnk01osbm02 migratable
5. new jms module, name: MyJMSSystemModule, targets: cluster bnk01osbcluster + all servers in the cluster
6. new xa conn factory, name: MyXAConnectionFactory, jndi name: MyXAConnectionFactory
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ XA Connection Factory Enabled: true
7. new Distributed Queue, name: MyDistributedQueue1, jndi name: MyDistributedQueue1, load balancing policy: round-robin
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ allocate members uniformly: true
and I recorded that into the included recorded_by_wls.py. As said no error has been raised.
Then I removed the above JMS resources and I executed the recorded_by_wls.py from command line getting the error that I reported at the end of the email.
I changed slightly the original py produced by WLS by adding only the below first 5 lines:
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
I included also the recorded_by_wls.py source at the end of the email.
For information I reported also what I saw on WLS console when I created manually my JMS resources.
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?
Any help will be very appreciate.
Thanks in advance.
Regards
ferp
Error:
java weblogic.WLST recorded_by_wls.py Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting the script ...
Connecting to t3://wasdv1r3n1.dev.b-source.net:7031 with userid weblogic ...
Successfully connected to Admin Server 'bnk01osbadm' that belongs to domain 'bnk01osb'.
Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to edit tree. This is a writable tree with
DomainMBean as the root. To make changes you will need to start an edit session via startEdit().
For more help, use help(edit)
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Activation completed
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
This Exception occurred at Mon Sep 07 15:31:33 CEST 2009.
weblogic.application.ModuleException: ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:618)
at weblogic.jms.module.ModuleCoordinator.prepareUpdate(ModuleCoordinator.java:487)
at weblogic.application.internal.flow.DeploymentCallbackFlow$5.next(DeploymentCallbackFlow.java:514)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepareUpdate(DeploymentCallbackFlow.java:280)
at weblogic.application.internal.BaseDeployment$PrepareUpdateStateChange.next(BaseDeployment.java:679)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepareUpdate(BaseDeployment.java:444)
at weblogic.application.internal.SingleModuleDeployment.prepareUpdate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepareUpdate(DeploymentStateChecker.java:221)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepareUpdate(AppContainerInvoker.java:149)
at weblogic.deploy.internal.targetserver.operations.DynamicUpdateOperation.doPrepare(DynamicUpdateOperation.java:130)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045050]A destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has a jms-create-destination-identifier of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1. However, another destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named wlsbJMSServer_auto_2.
at weblogic.jms.backend.BackEnd.addDestination(BackEnd.java:1527)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:195)
at weblogic.jms.backend.udd.UDDEntity.prepare(UDDEntity.java:444)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:936)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:841)
at weblogic.jms.module.JMSModule.access$1500(JMSModule.java:87)
at weblogic.jms.module.JMSModule$JMSModuleListener.prepareUpdate(JMSModule.java:1485)
at weblogic.descriptor.internal.DescriptorImpl$Update.prepare(DescriptorImpl.java:481)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdateDiff(DescriptorImpl.java:195)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdate(DescriptorImpl.java:174)
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:614)
Problem invoking WLST - Traceback (innermost last):
File "/products/software/tmp/recorded_by_wls.py", line 92, in ?
File "<iostream>", line 364, in activate
WLSTException: Error occured while performing activate : Error while Activating changes.ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2 Use dumpStack() to view the full stacktrace
recorded_by_wls.py source
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m01')
cd('/FileStores/MyFileStore_m01')
cmo.setDirectory('MyFileStore_m01')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m02')
cd('/FileStores/MyFileStore_m02')
cmo.setDirectory('MyFileStore_m02')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m01')
cd('/Deployments/MyJMSServer_m01')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m01'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m02')
cd('/Deployments/MyJMSServer_m02')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m02'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSSystemResource('MyJMSSystemModule')
cd('/SystemResources/MyJMSSystemModule')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbcluster,Type=Cluster')], ObjectName))
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createConnectionFactory('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setJNDIName('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/SecurityParams/MyXAConnectionFactory')
cmo.setAttachJMSXUserId(false)
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/TransactionParams/MyXAConnectionFactory')
cmo.setTransactionTimeout(3600)
cmo.setXAConnectionFactoryEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createUniformDistributedQueue('MyDistributedQueue1')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/UniformDistributedQueues/MyDistributedQueue1')
cmo.setJNDIName('MyDistributedQueue1')
cmo.setLoadBalancingPolicy('Round-Robin')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
-- source end --
ON WLS console
Name Type Target
MyFileStore_m01 FileStore bnk01osbm01 (migratable)
MyFileStore_m02 FileStore bnk01osbm02 (migratable)
FileStore_auto_1 FileStore bnk01osbm01
FileStore_auto_2 FileStore bnk01osbm02
WseeFileStore_auto_1 FileStore bnk01osbm01
WseeFileStore_auto_2 FileStore bnk01osbm02
Name Persistent Store Target Current Server
MyJMSServer_m01 MyFileStore_m01 bnk01osbm01 (migratable) bnk01osbm01
MyJMSServer_m02 MyFileStore_m02 bnk01osbm02 (migratable) bnk01osbm02
wlsbJMSServer_auto_1 FileStore_auto_1 bnk01osbm01 bnk01osbm01
wlsbJMSServer_auto_2 FileStore_auto_2 bnk01osbm02 bnk01osbm02
WseeJmsServer_auto_1 Wsee FileStore_auto_1 bnk01osbm01 bnk01osbm01
WseeJmsServer_auto_2 Wsee FileStore_auto_2 bnk01osbm02 bnk01osbm02
Name Type
MyJMSSystemModule System
configwiz-jms System
jmsResources System
WseeJmsModule System
Name Type JNDI Name Subdeployment Targets
MyDistributedQueue1 Uniform Distributed Queue MyDistributedQueue1 Default Targetting bnk01osbcluster
MyXAConnectionFactory Connection Factory MyXAConnectionFactory Default Targetting bnk01osbcluster

Hi Ferp,
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?It should not fail. Each and every successfully (activation has been done without reporting an error/conflict) recorded session will execute on other servers successfully until a unique name constraint gets violated.
In your case this violation has happened. Your script is trying to create a distributed destination "MyDistributedQueue1" under module "MyJMSSystemModule", targetted to JMS Server "wlsbJMSServer_auto_2" but a Distributed Queue with same JNDI name already exists there.
Please check.
Regards,
Anuj

How to create JMS queues using Scripts

Hi All,
I want to create JMS queue in weblogic server 8.1 by running scripts .
Can anybody provide me the scripts and how to run the scripts ...
i have the WLshell scripts to create the JMS queues and JNDI , but i dont know how to run the scripts .
Please help me on the same.
Thanks,
Kartheek

Hi Brad ,
Thanks for your reply.
I went through the above link but I am gettint a error when I am executing the WLST script.
Please look into the problem.
wls:/offline> execfile
<java function execfile at 1584086>
wls:/offline> execfile ('c:/bea/configJMSSystemResource.py')
Traceback (innermost last):
File "<console>", line 1, in ?
IOError: File not found - c:\bea\configJMSSystemResource.py (The system cannot f
ind the file specified)
wls:/offline> execfile ('c:/bea/configJMSSystemResource.py')
Traceback (innermost last):
File "<console>", line 1, in ?
IOError: File not found - c:\bea\configJMSSystemResource.py (The system cannot f
ind the file specified)
wls:/offline> execfile('c:/bea/configJMSSystemResource.py')
Traceback (innermost last):
File "<console>", line 1, in ?
IOError: File not found - c:\bea\configJMSSystemResource.py (The system cannot f
ind the file specified)
Thanks,
Kartheek.

Problem creating JMS Error Destination via Ant in WLS 8.1

We've got several JMS queues in our application. We create the server via Ant (using the wlconfig task).
All is well, the queues have been working fine, until we try to add an error destination queue (after several attempts to handle the message, it'll be sent to the error queue for later troubleshooting).
Here's an example of what we've got now:
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
</create>We create another queue to handle the errors, and then add an attribute to the first to point to the second:
<create type="JMSQueue" name="batchErrorQueue" property="batchErrorQueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchErrorQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
</create>
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
    <set attribute="ErrorDestination" value="${batchErrorQueue}"/>
</create>This seems logical, because if we do this same exact operation via the console, the config.xml goes from this:
<JMSQueue JNDIName="net.nike.cdm.batchQueue"
            Name="batchQueue" RedeliveryLimit="5"/>to this:
<JMSQueue ErrorDestination="batchErrorQueue"
            JNDIName="net.nike.cdm.batchQueue"
            Name="batchQueue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="net.nike.cdm.batchErrorQueue" Name="batchErrorQueue"/>The error we get when trying to do this via Ant is:
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue" on JMS server "cdmdomain"). Also, an ErrorDestination can not be null if the ExpirationPolicy for a destination is "redirect" and a destination can not specify itself as its ErrorDestination.Flipping on -verbose in Ant, the actual exception is:
[wlconfig] SET -mbean cdmdomain:Name=batchQueue,Type=JMSQueue -property ErrorDestination cdmdomain:Name=batchErrorQueue,Type=JMSQue
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue"
s its ErrorDestination.
      [if] Error in class net.sf.antcontrib.logic.IfTask
BUILD FAILED
file:C:/viewstore/CDM_R6.5_Development/B2B_CDM/dev/build.xml:1399: Error invoking MBean command: java.lang.NullPointerException
       at weblogic.ant.taskdefs.management.WLConfig.handleException(WLConfig.java:567)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCommand(WLConfig.java:381)
       at weblogic.ant.taskdefs.management.WLConfig.invokeSetCommand(WLConfig.java:235)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:163)
       at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:167)
       at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
       at weblogic.ant.taskdefs.management.WLConfig.execute(WLConfig.java:89)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:117)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at net.sf.antcontrib.logic.IfTask.execute(Unknown Source)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)
       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at org.apache.tools.ant.Target.execute(Target.java:309)
       at org.apache.tools.ant.Target.performTasks(Target.java:336)
       at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
       at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
       at org.apache.tools.ant.Main.runBuild(Main.java:609)
       at org.apache.tools.ant.Main.start(Main.java:196)
       at org.apache.tools.ant.Main.main(Main.java:235)So, my question is, what are we doing wrong? What IS the syntax to set an error destination for a JMS queue via Ant for WLS 8.1?
Any help would be greatly appreciated
Thanks,
Douglas Bullard

I get exactly the same problem - was a resolution to this issue found?
Thanks,
Richard Marriott
[email protected]

Ant to delete JMS Server

          I am trying to use an Ant script to configure a new domain for weblogic server
          8.1
          Ideally I want to run the script and have it configure all resources I will need
          (jdbc, jms, etc.). Currently I am having issues with the configuring of the JMS
          Server. I am using the following line of code to delete the JMS Server instance
          if it currently exist.
          <delete mbean="${domain.name}:Name=cgJMSServer,Type=JMSServer"/>
          This seems to be ignored by Ant because when I call the create task I get an InstanceAlreadyExist
          error. I assume my delete task is failing but giving no error. I'd like to be
          able to delete the current JMS server if one exist and then recreate it. I was
          wondering what the correct task or syntax would be for deleting the JMS server
          through Ant.
          Additionally, I'd like to use wlserver to create a new Integration Domain. I havent
          seen any documentation on how to specify a template to use when using the wlserver
          task, so I am not sure if this is possible or not.


Hi Allen,
          I think you may need to set the target of the JMS server
          to null first.
          I think the "JMSML" utility on dev2dev does this sort of
          task. You might want to take a look at its source to
          divine what steps it goes through.
          Tom
          Allan wrote:
          > I am trying to use an Ant script to configure a new domain for weblogic server
          > 8.1
          >
          > Ideally I want to run the script and have it configure all resources I will need
          > (jdbc, jms, etc.). Currently I am having issues with the configuring of the JMS
          > Server. I am using the following line of code to delete the JMS Server instance
          > if it currently exist.
          >
          > <delete mbean="${domain.name}:Name=cgJMSServer,Type=JMSServer"/>
          >
          > This seems to be ignored by Ant because when I call the create task I get an InstanceAlreadyExist
          > error. I assume my delete task is failing but giving no error. I'd like to be
          > able to delete the current JMS server if one exist and then recreate it. I was
          > wondering what the correct task or syntax would be for deleting the JMS server
          > through Ant.
          >
          > Additionally, I'd like to use wlserver to create a new Integration Domain. I havent
          > seen any documentation on how to specify a template to use when using the wlserver
          > task, so I am not sure if this is possible or not.

JMS server targeted to several clusters

Hello,
I am facing a problem with my JMS configuration in weblogic (version 10.3.4.0). I have two clusters. Following the [JMS best practice|http://forums.oracle.com/forums/message.jspa?messageID=9455261#9455261] I have created a JMS server in each Managed server within the clusters. I have created only one JMS Module with a subdeployment. The JMS Module is targeted to all managed servers within both clusters, and the subdeployment is targeted to all JMS servers within the clusters.
At the JMS module I have created a connection Factory targeted to the subdeployment, till there everything is ok.
Afterwards I try to create a uniform distributed queue (UDQ) targeted to the subdeployment and WebLogic throws the following error:
A UDD must be targeted to servers within a single cluster or a single stand-alone server, rather than Cluster ClusterA and Cluster ClusterB
The only solution that I found is to create one JMS Module-subdeployment per JMS Server. Is there a way to have just a JMS Module and use it in all the managed server in several clusters? or I have to set up the same parameters (ConnectionFactories + queue +quota) in each JMS Module.
Thank you very much in advance.
Cheers,
Oscar

Hi Oscar,
The correct way to step-up a UDQ is something like below
C-1 => MS-1 + MS-2
JMSServer-1 => MS-1
JMSServer-2 => MS-2
JMSModule-1 => C-1
Sub_UDQ => JMSServer-1 + JMSServer-2
UDQ => Sub_UDQ
CF => C-1
Where:
======
MS-x are the managed servers
C-x are the Cluster
UDQ is the Uniform Distributed Queue
Sub_UDQ is the Sub-Deployment for UDQ
CF is the Connection Factory
*=>* mean Targeted.
Also to get more information on it you can have a look at the below link which has the step by step instructions which would surely help you out
Topic: Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Regards,
Ravish Mody

How to create JMS Queue in soa 11g?do we need to create jmsuser user in db

Hi All,
We r using SOA 11.1.1.3 version do we get jmsuser user while installing itself. we r unable to see this user. Can anyone suggest how to create a JMS queue in soa 11g.
Thanks,
RR

Hi,
Oracle SOA runs over weblogic application server 10.3.3
If you want to create a JMS queue, then you have to create it on weblogic server. For creating a JMS queue, first of all create a JMS server on weblogic admin console (by default http://localhost:7001/console) (Services --> Messaging --> JMS Servers) and target it to a server/cluster as desired. Now create a JMS module (Services --> Messaging --> JMS Modules) and target it to same server/cluster.
Now create a sub-deployment in JMS Module (Services --> Messaging --> JMS Modules --> Your JMS Module --> Subdeployments tab) and select the JMS server you created initially as a target of this subdeployment.
Now create a connection factory in that JMS module and in advanced targetting select the subdeployment you created. Now create a JMS queue in the same JMS module and in subdeployment select the subdeployment you created.
If you want to access this queue from an application then JMS URL should be like -
jms://hostname:port/connFactoryJNDIName/QueueJNDIName
Regards,
Anuj

Load balancing MQ 7.0 Foreign JMS Server and Weblogic 10 MDBs?

We have the following configuration and we are trying to troubleshoot what appears to be a load balancing issue.
We have 3 Solaris servers. Each Solaris server has two Weblogic managed servers running on it. There are a total of 6 managed servers in the Weblogic cluster.
MQ Series 7.0 is also installed on each Solaris server. The MQ queue managers are in a MQ cluster. Each queue manager has the same queues defined.
We have a foreign JMS Server configured on Weblogic that has destinations and a connection factory defined. There aren't many configuration options available for the connection factory. The destinations are bound to the queues defined on MQ using the MQ bindings file.
The MQ bindings file was generated using the TRANSPORT(BIND) mechanism. Each bindings file points to the queue manager running on that machine. So the 2 managed servers running on one machine are accepting messages from the queue manager on that machine.
The MDB's listenning for messages on the MQ queues are configured as follows in the weblogic-ejb-jar.xml:
<max-beans-in-free-pool>16</max-beans-in-free-pool>
We also created a custom work manager with min threads constraint=5 and max threads constraint=16. The dispatch-policy of all the MDBs is set to the custom work manager.
The open input count on each MQ queue managers shows up as 32 which is expected.
The default load algorithm on the cluster is round-robin.
When we run a load test (injecting 40 messages per second on one MQ queue), we notice that one managed server ends up being significantly loaded than the other. Each MQ queue manager in the MQ cluster receives approximately the same number of messages in the load test. But it seems like one managed server is preferred over the other in Weblogic.
What can be done to equally balance the load among the two managed servers on each Solaris server?
Thanks for the help.

Load balancing generally applies at determing how many consumer threads has to be created on each of the clustered queue instance. In that sense you have achieved perfect load balancing as your queue instances has the same no of consumer threads.
Once you have set 'x' consumer threads on a queue, it is upto messaging provider to decide which thread to deliver a particular message and you will hardly have any control over this. Since your 32 threads are listening on the same queue, MQ can select any thread for delivering the message and the behaviour could be non deterministic.
One option to change your design is to have a dispacther mdb which picks the messages off the MQ and then routes to a weblogic distributed destination and you can have your core mdb which does all processing listen to this distributed destination. You can enable load balancing when the disaptcher mdb routes the message to the distributed destination. Since dispatcher MDB is nothing more than a router, the unbalanced consumption off the MQ shouldn't seriously affect the server.

Oracle Queue Error creating JMS-120: Dequeue failed

Hi Guys,
We are facing serious problems with Oracle queue when dequeuing messages from the queue.
Our configuration is the following:
- SOA Suit 10.g (10.1.3.5.0)
- Dehydration storage - Oracle Database 11gR2 in Exadata Cloud
We use standard JMS Adabpter from AS10g to dequeue messages from the Oracle queue.
Suddenly dequeue stop working pooling the flowing errors into the log.xml log file in $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_SOA_GROUP_1/oc4j directory.
<MSG_TEXT>Failed to process deferred message</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[oracle.tip.esb.server.dispatch.QueueHandlerException: Error creating "JMS-120: Dequeue failed"
     at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:197)
     at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:178)
     at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:135)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:825)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.jms.AQjmsException: JMS-120: Dequeue failed
     at oracle.jms.AQjmsError.throwEx(AQjmsError.java:308)
     at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:2094)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:922)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:835)
     at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:776)
     at oracle.j2ee.ra.jms.generic.CommonConsumerWrapper.receive(CommonConsumerWrapper.java:203)
     at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:175)
     ... 7 more
then:
<COMPONENT_ID>j2ee</COMPONENT_ID>
    <MSG_ID>J2EE JTA-00107</MSG_ID>
<MSG_TEXT>Error in resource driver during rollback: oracle.jdbc.xa.OracleXAException, errorCode : -7</MSG_TEXT>
and this message comes out every second:
    <MSG_TEXT>Attempt to use an invalid handle : 'oracle_jdbc_driver_LogicalConnection_Proxy@10af88e3'.</MSG_TEXT>
Any help, suggestions, hints would be much appreciated.
cheers!!
eMarcel

Hi there
I have got the same problem i.e
oracle.jms.AQjmsException: JMS-120: Dequeue failed
     at oracle.jms.AQjmsError.throwEx(AQjmsError.java:283)
     at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:2178)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1013)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:950)
     at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:897)
     at com.cramer.cdd.mytest.QueueReceive2.init(QueueReceive2.java:122)
     at com.cramer.cdd.mytest.QueueReceive2.main(QueueReceive2.java:152)
Exception in thread "main
Please help me in debugging this.
I have a standalone java application to listen to the aqJMS queue.
Regards
Paul

WLST create JMS Server

Similar Messages

Maybe you are looking for