Configuring JMS over a Weblogic Cluster

I have a setup of 2 Weblogic managed servers configured as part of a cluster.
1) The requirement is to send requests to another system and receive responses using JMS as interface.
2) The request could originate from either of the Managed Servers. So the corresponding response should reach the managed server which originated the request.
3) The external system (to which requests are sent) should not be aware of how many managed servers are in the cluster (not a must have requirement)
How should JMS be configured for meeting these requirments?

Refer:- Re: help in setting up a clustered scalable JMS env
-Akshay

Similar Messages

How to configure JMS server in weblogic

Hi,
I want to configure JMS server in weblogic.So please send me needful link.
Regards
Anup

Hi Anup,
1. The first thing you have to do is create a filestore where messages will be stored. Look at the below link for more detailed instructions:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/stores/CreateFileStores.html
2. Next create a JMS server. Look at the below link for more detailed instructions
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_servers/ConfigureJMSServers.html
3. Now, create a JMS System Module to hold the JMS resources like Queues, Topics, Connection Factory, SAF agents etc..
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModules.html
4. Now, create a resource like connection factory OR queue etc.
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModuleResources.html
For now, lets stick to the basics and create a basic queue using the below documentation unless you exactly know what resource you want to create
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/CreateQueues.html
5. You will also need to create a connection factory to use the resource. See below documentation
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/connection_factories/CreateConnectionFactories.html
Please go through the below JMS architecture diagram as well as documentation that will tell you what JMS on WebLogic is all about in terms of configuration
http://docs.oracle.com/cd/E23943_01/web.1111/e13738/overview.htm#i1084283
Arun

Help configuring jms over http?

I am looking to use jms over port 8080 to both send and receive soap messages. Does anyone know how to configure jms to do this? Any good documentation?
I am using Sun Application Server 8 Platform Edition.
Thanks.

Hi Rabbia,
This is not something which is defined by the JMS standard.
Each vendor has differing approaches to supporting HTTP/HTTPS. Some use proxy servlets in conjunction with web servers etc... Others don't support it at all.
Nirvana from my-channels supports the idea of adding multiple interfaces to a server. Each bound to a specific hostname and port and communicating over a specific protocol (e.g. HTTP or HTTPS). Using Nirvana you would simply add a HTTP interface which is bound to port 8080.
http://www.my-channels.com/developers/nirvana/FAQ/addingANetworkInterface.html
You would then configure your clients to point to that specific interface..
http://www.my-channels.com/developers/nirvana/examples/nJMS/jmsadmin_intro.html
Hope this helps.
Eddie McDaid
www.my-channels.com

How do you configure ORDS in a Weblogic Cluster? Getting "This installation has not yet been configured" on second server...

We currently have ORDS 2.0.9 installed on WLS 10.3.6 running on Windows 2008R2 behind an F5 load balancer. When the load balancer sends the connections to the server we configured first, everything works fine. When the load balancer sends the connections to the scaled out server, we get the ORDS page with "This installation has not yet been configured". The defaults.xml and related directories got created on the second server automatically. We tried changing the debug.debugger and debug.printDebugToScreen entries in the defaults.xml of the second server, but nothing happened. What are we missing? How do we configure the second server?

The issue has been resolved. After looking at the directories and defaults.xml that WLS created on the scaled out server, we figured that the configuration files were not created/copied from the original server. We ran the configuration from "java -jar ords.war setup" on the second server, restarted the application from WLS and everything started working as expected.

How to Configure JMS MQ In WeLogic?

Hello. I am new to this forum. Can anybody gives instructions on how to create or configure JMS MQ in WebLogic ?
Thanks.

I recommending starting by reading through the [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E12839_01/web.1111/e13727/interop.htm#JMSPG553 ] FAQ, in order to assess the various options.
You may also want to look at "[ Integrating WebSphere MQ 6 with BEA Weblogic Server 10 using Weblogic Server Foreign (JMS) Server feature | http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html ]".
If you need exactly-once (transactions), and the MQ server is on a different machine than WebLogic, then you will need to use the MQ Extended Transactional client from IBM (http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf). I think IBM still requires a license for this client.
Finally, you might find some useful information in the following white-paper: "[ Integrating an Oracle Service Bus Cluster with an IBM WebSphere MQ Cluster in a Service-Oriented Architecture | http://www.oracle.com/technology/products/integration/service-bus/docs/osb-websphere-whitepaper.pdf ]".
Tom

Configuring XI over JMS

Hi,
I would like to configure XI over JMS using Bea Weblogic's JMS support,
Can anybody suggest how do i go about doing it? I am new to XI.
Thanks,
vishnu

Hi,
The best place to start is the SAP online help documentation. Try these link for starters (you will see more links on the left navigation too).
http://help.sap.com/saphelp_nw04/helpdata/en/e8/01683c43e87845e10000000a11402f/frameset.htm
Another tip is that you can search SAP documentation directly from SDN in the search on the top left of the SDN site
I hope this helps,
Mike.

Can you specify third party JMS Provider in Weblogic appserver configuration

 Can you specify third party JMS Provider in Weblogic appserver configuration ???
 Only place i know of is that you can specify third party JMS Provider in MDB configuraion.
 DOES Weblogic has some kind of configuration files where you specify JMS Provider
 info (Like you can do that in JBOSS)


You can also specify a third-party JMS provider using the Messaging Bridge,
 which transfers messages from one queue or topic to another.
 And in general, inside WLS you can use any JMS provider you wish anywhere
 that you can also use WLS JMS. In an upcoming release, there will also be
 some support to make foreign JMS providers a little easier to configure.
 But why would you want to use another JMS provider anyway? ;-)
 greg
 "Neeru Munjal" <[email protected]> wrote in message
 news:[email protected]..
 >
 > Can you specify third party JMS Provider in Weblogic appserver
 configuration ???
 >
 > Only place i know of is that you can specify third party JMS Provider in
 MDB configuraion.
 > DOES Weblogic has some kind of configuration files where you specify JMS
 Provider
 > info (Like you can do that in JBOSS)

Help on Coherence + Weblogic Cluster configuration

Hi,
I am new to Coherence. I am exploring coherence to fulfill one of my requirement.
My requirement : I have an application deployed on a Web logic Server clustered environment. I need to cache the application specific data(java maps) and that should be available for all nodes of the WLS cluster. The application data that's being cached, can be updated from any of the node from the WLS cluster and updated application data from the cache should be available for all the nodes of the WLS cluster. The nodes in the WLS cluster resides in different machines from different locations.
Can I use coherence as a caching services for my requirement?
If Yes, do I need to start a coherence cache server on each node of the WLS cluster?
If yes, do I need to specially configure these cache servers, so that these cache servers would communicate each other in case of any data updates in the cache?
It will be great help if you could also provide sample configurations to achieve the above scenarios.
Thanks in advance!
regards,
Srinivas M

You can start one cache server in the network by using for example
# home directory
BEA_HOME="/home/oracle/bea"
export BEA_HOME
# java vendor (for example Oracle or Sun)
JAVA_VENDOR="Oracle"
export JAVA_VENDOR
# cache server klasse
CACHE_SERVER_CLASS="com.tangosol.net.DefaultCacheServer"
export CACHE_SERVER_CLASS
# coherence options
COHERENCE_OPTIONS="-Dtangosol.coherence.management=all"
export COHERENCE_OPTIONS
COHERENCE_OPTIONS="${COHERENCE_OPTIONS} -Dtangosol.coherence.management.remote=true"
#COHERENCE_OPTIONS="${COHERENCE_OPTIONS} -Dtangosol.coherence.cacheconfig=WEB-INF/classes/session-cache-config.xml"
#COHERENCE_OPTIONS="${COHERENCE_OPTIONS} -Dtangosol.coherence.session.localstorage=true"
WL_HOME="${BEA_HOME}/wlserver_10.3"
export WL_HOME
BEA_JAVA_HOME="${BEA_HOME}/jrockit_160_05_R27.6.2-20"
export BEA_JAVA_HOME
SUN_JAVA_HOME="${BEA_HOME}/jdk160_11"
export SUN_JAVA_HOME
if [ "${JAVA_VENDOR}" = "Oracle" ]; then
 JAVA_HOME="${BEA_JAVA_HOME}"
 export JAVA_HOME
 MEM_ARGS="-jrockit -Xms512m -Xmx512m -Xss128k -Xgcprio:throughput"
 export MEM_ARGS
fi
if [ "${JAVA_VENDOR}" = "Sun" ]; then
 JAVA_HOME="${SUN_JAVA_HOME}"
 export JAVA_HOME
 MEM_ARGS="-server -Xmx512m -Xms512m -Xmn256m -Xss128k -XX:PermSize=128m -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:ParallelGCThreads=2 -XX:+UseParallelOldGC -XX:+AggressiveOpts -XX:+UseBiasedLocking"
 export MEM_ARGS
fi
# classpath for the cache server
CLASSPATH="${WL_HOME}/coherence/coherence.jar"
export CLASSPATH
# start the cache server
${JAVA_HOME}/bin/java ${MEM_ARGS} ${COHERENCE_OPTIONS} ${CACHE_SERVER_CLASS}The -Dtangosol.coherence.management=all option gives you some handy information on what the cache is doing by using for example the mbean browser provided by jconsole or jrockit mission control.
You can create an application in which you create a cache, the following shows an example of a servlet
import com.tangosol.net.CacheFactory;
import com.tangosol.net.NamedCache;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
import java.util.Random;
public class TestServlet extends HttpServlet {
 private NamedCache movies;
 public void init() throws ServletException {
 movies = CacheFactory.getCache("repl-movies");
 movies.put(10, new Movie(10, "Rear Window", "Alfred Hitchcock"));
 movies.put(20, new Movie(20, "Vertigo", "Alfred Hitchcock"));
 movies.put(30, new Movie(30, "Double Indemnity", "Billy Wilder"));
 movies.put(40, new Movie(40, "Touch of Evil", "Orson Welles"));
 protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
 Integer[] integers = {10, 20, 30, 40};
 Random random = new Random();
 while (true) {
 movies.get(integers[random.nextInt(4)]);
}Package the servlet into for example a WAR file and deploy it to a configured WebLogic cluster.
By accessing servlet on the different nodes of the cluster a new cache gets created and added to the
already running DefaultServer.
The hard part is to configure your cache. As you can see in the servlet init we ue something like CacheFactory.getCache("repl-movies");
Coherence default with some example cache configurations which are contained in the coherence.jar (coherence-cache-config.xml).
The following entry is used
<cache-mapping>
 <cache-name>repl-*</cache-name>
 <scheme-name>example-replicated</scheme-name>
</cache-mapping>
<replicated-scheme>
 <scheme-name>example-replicated</scheme-name>
 <service-name>ReplicatedCache</service-name>
 <backing-map-scheme>
 <local-scheme>
 <scheme-ref>unlimited-backing-map</scheme-ref>
 </local-scheme>
 </backing-map-scheme>
 <autostart>true</autostart>
</replicated-scheme>A replicated cache is probably what you need as well. As you want all the data to be available on all nodes. If you want to use
your own cache configuration you can add the option -Dtangosol.coherence.cacheconfig (see the start script for the default server)
A good introduction on Coherence can be found here:
http://www.packtpub.com/article/installing-coherence-3.5-and-accessing-the-data-grid-1
and
http://www.packtpub.com/article/installing-coherence-3.5-and-accessing-the-data-grid-2?utm_source=rk_coherence_abr1_0310&utm_medium=content&utm_campaign=ramsai

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.

Installing LC 8.2 on WebLogic cluster

Hi, We are trying to install LC 8.2 on a WebLogic cluster running on Solaris (SunOS 5.10) with a Oracle Database (10.2.0.3) The configuration manager stops during the task 'LiveCycle Component Deployment' with the following output: Loading state from service container Deploying DSC adobe-ejbprovider-dsc.jar DSC already running adobe-ejbprovider-dsc.jar Deploying DSC adobe-soapConnector-dsc.jar DSC already running adobe-soapConnector-dsc.jar Deploying DSC adobe-remotingConnector-dsc.jar DSC already running adobe-remotingConnector-dsc.jar Deploying DSC adobe-usermanager-dsc.jar DSC already running adobe-usermanager-dsc.jar Deploying DSC adobe-usermanager-util-dsc.jar DSC already running adobe-usermanager-util-dsc.jar Deploying DSC adobe-jobmanager-dsc.jar DSC already running adobe-jobmanager-dsc.jar Deploying DSC adobe-scheduler-weblogic-dsc.jar DSC already running adobe-scheduler-weblogic-dsc.jar Deploying DSC adobe-cacheservice-dsc.jar DSC already running adobe-cacheservice-dsc.jar Deploying DSC adobe-event-dsc.jar DSC already running adobe-event-dsc.jar Deploying DSC adobe-emailprovider-dsc.jar DSC already running adobe-emailprovider-dsc.jar Deploying DSC adobe-fileprovider-dsc.jar DSC already running adobe-fileprovider-dsc.jar Deploying DSC adobe-truststore-dsc.jar DSC already running adobe-truststore-dsc.jar Deploying DSC adobe-workflow-dsc.jar DSC already running adobe-workflow-dsc.jar Deploying DSC adobe-repository-dsc.jar DSC already running adobe-repository-dsc.jar Deploying DSC adobe-repository-provider-dsc.jar DSC already running adobe-repository-provider-dsc.jar Deploying DSC adobe-applicationmanager-dsc.jar DSC already running adobe-applicationmanager-dsc.jar Deploying DSC adobe-businesscalendar-dsc.jar DSC already running adobe-businesscalendar-dsc.jar Deploying DSC adobe-email-dsc.jar DSC already running adobe-email-dsc.jar Deploying DSC adobe-fileutils-dsc.jar DSC already running adobe-fileutils-dsc.jar Deploying DSC adobe-ftp-dsc.jar DSC already running adobe-ftp-dsc.jar Deploying DSC adobe-jdbc-dsc.jar DSC already running adobe-jdbc-dsc.jar Deploying DSC adobe-jms-dsc.jar DSC already running adobe-jms-dsc.jar Deploying DSC adobe-ldap-dsc.jar DSC already running adobe-ldap-dsc.jar Deploying DSC adobe-variablelogger-dsc.jar DSC already running adobe-variablelogger-dsc.jar Deploying DSC adobe-webservice-dsc.jar STDOUT fra configurationManager'en siger f.eks. flg: [2008-12-29 16:24:25,132], SEVERE, Thread-29, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, Failed to deploy component /export/home/domadob/projects/livecycle8.2/deploy/adobe-webservice-dsc.jar. com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component /export/home/domadob/projects/livecycle8.2/deploy/adobe-webservice-dsc.jar. at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:39 6) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:149) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask$ActualTask.<init>(DeployDSCsT ask.java:84) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask$1.construct(DeployDSCsTask.ja va:56) at com.adobe.livecycle.lcm.core.tasks.SwingWorker$2.run(SwingWorker.java:114) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: ORA-22990: LOB locators cannot span transactions at com.adobe.pof.adapter.oracle.Oracle9iAdapter.updateObject(Oracle9iAdapter.java:655) at com.adobe.pof.adapter.JDBCAdapter.updateObject(JDBCAdapter.java:479) at com.adobe.pof.omapi.POFObjectManagerImpl.writeObject(POFObjectManagerImpl.java:254)

Hello,
Could you get any answers for this apart from the forum? I face the same situation on a non-clustered WebSphere server. We have a case open but no solution yet...
The error message is as follows:
[2008-12-31 17:55:48,689], SEVERE , Thread-5, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, Failed to deploy component ../working/deployLC/deploy/adobe-scheduler-websphere-dsc.jar.
Regards

Issue listeneing queue from Weblogic Cluster server with multiple managed server

Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
--ManagedServer01(http://server01.myhost.com:7001)
--ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
JMSserver01 targeting: ManagedServer01
JMSserver02 targeting: ManagedServer02
JMSmodule
ConnectionFactory01 targeting:JMSserver01,JMSserver02
UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
mysystemmodule!JMSserver01@UDQueue01
mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
mysystemmodule!JMSserver01@UDQueue01 10
mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
mysystemmodule!JMSserver01@UDQueue01 0
mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.

You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz

JMS in clustered weblogic

Is there any intention of including support for JMS queues clustering? If so, would it include clustering of messages after a server shutdown?
Thanks

Hi Ignacio,
We do not support the JMS API from Coherence. That is one of the APIs that we currently defer to the application server providers, such as BEA. Unfortunately, BEA WebLogic does not currently support Coherence for its clustered queues, but I believe in WebLogic 8.1 you can manually fail-over BEA WebLogic queues in a cluster.
Peace,
Cameron Purdy
Tangosol, Inc.
Coherence: Easily share live data across a cluster!

StreamCorruptedException when starting Weblogic cluster

Hi, I have an application running on Weblogic Server 8.1 sp4 in clustered environment. When the cluster is restarted the first server restarts without errors but the second one has the following error message. What does the error message mean? Some messages have disappeared form the JMS queue when the cluster has been restarted. Does this error message have something to do with the disappeared messages?
 <29.9.2006 14:09:17 EEST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster2 on 237.0.0.6:10603.>
 <29.9.2006 14:09:17 EEST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster2.>
 <29.9.2006 14:09:47 EEST> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server CL2Server2.>
 <29.9.2006 14:09:54 EEST> <Error> <JMS> <BEA-040368> <The following exception has occurred:
 java.io.StreamCorruptedException: Unknown object stream version. 5505025
 at weblogic.jms.store.BufferDataInputStream.readObject(BufferDataInputStream.java:167)
 at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:1024)
 at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:939)
 at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:1140)
 at weblogic.jms.store.JMSStore.recover(JMSStore.java:315)
 at weblogic.jms.backend.BEStore.open(BEStore.java:264)
 at weblogic.jms.backend.BEStore.start(BEStore.java:151)
 at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
 at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
 at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
 at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
 at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
 at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
 at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
 at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
 at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
 at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
 at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
 at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
 at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
 at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
 at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
 at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
 at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:32)

Make sure that the JMS server isn't attempting to load a store that was created from a later version of WLS. Also, make sure that no two JMS servers share the same database table - otherwise they will corrupt each-other's data. I think the latter is likely the problem.
 Tom

What is the association between JMS Server and JMS Module in weblogic 10?

Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....

Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom

Weblogic Cluster with different hardware

Hello,
I want to configure a Bea Weblogic 8.1 Cluster including an itanium and an i686
server.
I have sucessfully configured a weblogic cluter with 2 Sun servers.
Now I want to use for my weblogic cluster an itanium server together with an Intel
i686 server both running on linux with jrockit as jvm.
Is it possible to do this with different hardware platforms to use in a Weblogic
Cluster?
I know that I have to use the same servicepack of WLserver and the same java machine.
On the itanium system i use Redhat AS and on the i686 system i use redhat es
Michael

Yes, this is fine. The only thing you need to watch for is that the system with the least resource is capable of taking over the workload of the system with the larger resources. This will often just be a matter of application configuration or tuning.
Tim
---

Configuring JMS over a Weblogic Cluster

Similar Messages

Maybe you are looking for