JMS Server Current Count

          Hi,
          I have created two JMS Server in the WLS 6.0 Console but still the "CurrentJMSServerCount"
          value returns "ZERO".Am reading the values thro JMX Runtime MBeans.Let me wanna
          know whether any way to get the non zero values.
          Any suggesstions / tips are welcome
          Warm Rgds,
          Bala

Hi Jason
I suggest test step by step.
Are the servers getting the RUNNING state?
Are you able to test the datasource?
Without the service migration, do you see the JMS Servers working properly?
Otherwise, I recommend to enable some debugs to try to figure out what is happening.
Troubleshooting WebLogic JMS - 11g Release 1 (10.3.6)
Best Regards
Luz

Similar Messages

JMS Server Current Count returns value "ZERO" always

          Hi,
          I have created two JMS Server in the WLS 6.0 Console but still the "CurrentJMSServerCount"
          value returns "ZERO".Am reading the values thro JMX Runtime MBeans.Let me wanna
          know whether any way to get the non zero values.
          Any suggesstions / tips are welcome
          Warm Rgds,
          Bala


Did you remember to set the target for each JMS server? I think you will also
          need a restart.
          Bala Subramanian wrote:
          > Hi,
          > I have created two JMS Server in the WLS 6.0 Console but still the "CurrentJMSServerCount"
          > value returns "ZERO".Am reading the values thro JMX Runtime MBeans.Let me wanna
          > know whether any way to get the non zero values.
          >
          > Any suggesstions / tips are welcome
          >
          > Warm Rgds,
          > Bala

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.

MDBs failed to connect to remote JMS server

Hi,
          We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
          In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
          <weblogic-enterprise-bean>
               <ejb-name>MyBean</ejb-name>
               <message-driven-descriptor>
                    <destination-jndi-name>MyTopic</destination-jndi-name>
          <provider-url>t3://myhost:19009,myhost:19011</provider-url>
          <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
          di-name>
               </message-driven-descriptor>
          </weblogic-enterprise-bean>
          When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
          (t3://myhost:19009) but got the same result.
          When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
          I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
          Any help would be greatly appreciated.
          Thanks,
          Thao

I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
          >>> Could you elaborate on the known problem?
          9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
          >>> What else I can try?
          Beyond contacting customer support, I'm not sure.
          Tom

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.

Best way to determine if JMS server is alive in a cluster

Can anyone give me an idea on the best way to find out if a JMS server
          in a cluster
          has failed so I can signal migration to another server in the cluster.
          Thanks Larry
          PS weblogic 7.0 sp1


Hallo Larry,
          you can go via JMX and retrieve the according RuntimeMBeans in order to
          check the health state of the
          JMSServer resp. the server hosting the JMSServer. If they are not available
          or failed you can trigger the
          migration. At least that's the way I'm doing it...
          try
          JMSServerMBean jmsServer = null;
          ServerMBean candidateServer = null;
          MigratableTargetMBean migratableTarget = null;
          * Retrieve all JMSServer defined for the current domain
          Set jmsServerSet = home.getMBeansByType("JMSServer", domainName);
          Object[] jmsServers = jmsServerSet.toArray();
          * Just the first one is picked assuming there is only one defined
          * within the active FHO domain
          if(jmsServers != null && jmsServers.length > 0)
          jmsServer = (JMSServerMBean) jmsServers[0];
          if(s_logger.isDebugEnabled())
          s_logger.debug("JMSServer: " + jmsServer.getName());
          * A JMSServer can only be associated with a single target,
          * thus pick again the first from the list.
          TargetMBean[] targets = jmsServer.getTargets();
          if(targets != null && targets.length > 0)
          boolean hostingServerRunning = false;
          boolean candidateServerRunning = false;
          * Check whether the JMSServer is really associated with
          * a migratable target. Otherwise the migration must be canceled
          * since it cannot be performed!
          if(targets[0] instanceof MigratableTargetMBean)
          migratableTarget = (MigratableTargetMBean) targets[0];
          * Retrieve all available candidates and select a running instance
          * if any. First check for constrained candidate servers, than for
          * all candidate servers
          ServerMBean[] candidates =
          migratableTarget.getConstrainedCandidateServers();
          if(candidates == null || candidates.length == 0)
          candidates = migratableTarget.getAllCandidateServers();
          if(candidates != null && candidates.length > 0)
          ServerMBean hostingServer = migratableTarget.getHostingServer();
          boolean gotHostingServer = false;
          boolean gotCandidateServer = false;
          boolean runningInstance = false;
          * Loop over all candidates as long as hosting server and candidate
          * server are visited and there running state has been determined
          for(int i=0; i< candidates.length; i++)
          ServerRuntimeMBean serverRuntime = null;
          * Retrieve the current state from the according runtime MBean
          * if available
          try
          serverRuntime = (ServerRuntimeMBean) home.getMBean(new
          WebLogicObjectName(candidates.getName(), "ServerRuntime", domainName,
          candidates[i].getName()));
          runningInstance =
          serverRuntime.getState().equalsIgnoreCase(ServerRuntimeMBean.RUNNING);
          catch(InstanceNotFoundException inf)
          * When a server instance is not available, an InstanceNotFoundException will
          be raised
          * by WLS, which can be ignored
          if(hostingServer != null && hostingServer.equals(candidates[i]))
          hostingServerRunning = runningInstance;
          gotHostingServer = true;
          else
          * A running candidate server will be prefered, thus only if no running
          * instance can be detected, another instance is selected
          if(!gotCandidateServer)
          candidateServerRunning = runningInstance;
          candidateServer = candidates[i];
          gotCandidateServer = runningInstance;
          if(gotCandidateServer && gotHostingServer)
          break;
          if(s_logger.isDebugEnabled())
          s_logger.debug("Migratable Target: " + migratableTarget.getName());
          s_logger.debug("Candidate Server: " + candidateServer.getName());
          else
          throw new Exception("JMSServer not deployed on a migratable target!");
          * Retrieve the migration service coordinator for the active domain assuming
          * there exists only one and invoke the migration later on
          MigratableServiceCoordinatorRuntimeMBean coordinator = null;
          Set coordinatorSet =
          home.getMBeansByType("MigratableServiceCoordinatorRuntime", domainName);
          Object[] coordinators = coordinatorSet.toArray();
          if(coordinators.length > 0)
          coordinator = (MigratableServiceCoordinatorRuntimeMBean) coordinators[0];
          if(enforceMigrationOnInstancesDown)
          coordinator.migrate(migratableTarget, candidateServer, hostingServerRunning,
          candidateServerRunning);
          else
          coordinator.migrate(migratableTarget, candidateServer);
          s_logger.info("Migration of JMSServer from node "
          + migratableTarget.getName()
          + " to node "
          + candidateServer.getName()
          + " has been started");
          else
          throw new Exception("MigrationServiceCoordinator cannot be retrieved");
          catch(Exception e)
          s_logger.error("Could not migrate JMSServer", e);
          Regards,
          CK
          "Larry Presswood" <[email protected]> schrieb im Newsbeitrag
          news:[email protected]...
          > Can anyone give me an idea on the best way to find out if a JMS server
          > in a cluster
          > has failed so I can signal migration to another server in the cluster.
          >
          > Thanks Larry
          >
          > PS weblogic 7.0 sp1
          >

Foreign JMS Server Limitation

Hi all,
          Iam facing a limitation with Foreign JMS server.
          We are tyring to migrate from Message Bridge to Foreign JMS server.
          Our current setup is
          We have 3 MQ queues which are bridged to one JMS destination(queue).The MDB is consuming messages from the weblogic queue.
          If we want to replace this setup with Foreign JMS server the MDB can connect to only one MQ queue.
          We want the MDB to consume messages from all the 3 queues.
          How can we acheive this ?
          Thanks,
          Rabbani

U should take my reply with a grain of salt because I'm pretty new at this stuff but I don't think it's within an MDBs design to listen to more than one queue/topic so therefore you'll have to create additional MDBs that either listen to each foreign queue individually and do whatever your single MDB is doing with the data now or create the n MDBS (where n = number of foreign queues currently bridgin to the one) that then publish to an intermediate topic which your existing MDB can listen to.
          Hope this helps, figure if I'm going to be pounding the boards with questions I should try to contribute where I can ;)
          And also, if you do setup the foreign JMS provider feel free to take a look at my topic and provide your experience if you think it will help :D

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

1 JMS Server [3 Queues] OR 3 JMS Servers [1 Q each]

          Hi
          I am still debating myself which configuration is better purely from performance
          perspective whether to have multiple queues hosted my the same JMS server or give
          one JMS server per Queue. Just wondering if someone can throw some light on this
          as I dont see this thing addressed in the JMS performance guide - is it because
          it dosent make any difference?
          I am trying to figure out if in the first setup since all queues will use the
          same store they will end up using a where clause to get data from the Queue and
          in the 2nd case it will be like select * without a where clause? In that case
          the 2nd config will give better performance. I am using file store.
          Its likely that in my configuration one of the Queues is going to be pounded big
          time whereas the other 2 queues message volume will be significantly low.
          Any thoughts/pointers is appreciated.
          thanks
          Anamitra


Internally, the JDBC store does simple
          inserts/deletes/single-record-selects -
          it has notion of destinations.
          I'm fairly sure that the JMS Performance Guide does cover this topic,
          but I don't have time to comb through it. Anyhow, with DB stores
          I think it is likely you will get better performace by using
          multiple stores - provided the introduction of multiple
          stores doesn't start forcing too many transactions to become
          two-phase that were one-phase before. Each store
          counts as an XA resource, so two stores in the same
          transaction forces a 2PC transaction.
          (With file stores one might get worse performance.)
          Tom
          Anamitra wrote:
          > Hi
          > I am still debating myself which configuration is better purely from performance
          > perspective whether to have multiple queues hosted my the same JMS server or give
          > one JMS server per Queue. Just wondering if someone can throw some light on this
          > as I dont see this thing addressed in the JMS performance guide - is it because
          > it dosent make any difference?
          >
          > I am trying to figure out if in the first setup since all queues will use the
          > same store they will end up using a where clause to get data from the Queue and
          > in the 2nd case it will be like select * without a where clause? In that case
          > the 2nd config will give better performance. I am using file store.
          SQL has nothing to do with file stores, so I don't understand
          the question. Anyhow, I happen to
          know that no JDBC store SQL references queues - messages
          are handled individually regardless of queue
          or topic.
          >
          > Its likely that in my configuration one of the Queues is going to be pounded big
          > time whereas the other 2 queues message volume will be significantly low.
          I think there is little point in seperating into seperate stores unless
          all stores would be very active.
          Anyhow, this is all simple enough to test on your own as it
          only involves configuration changes. I highly
          recommend trying it out.
          >
          > Any thoughts/pointers is appreciated.
          > thanks
          > Anamitra

JMS server shuts down when quota_threshold reached

Hi,
Using weblogic 10.3.2. We are using WLS JMS Queues and are having the below issue. We are using filestore as a persistence during peak times huge number of messages are queued and the space on the disk gets filled up where no more messages are able to be persisted but some how WebLogic keeps accepting the messages and we end up restarting the servers to make sure messages starts getting processed. Is there a way if the space on the disk gets full we don't accepts any messages in the queues and once the space gets available start accepting the messages over again. Is there any out-of-the-box functionality available that it automatically detects this kind of behavior and WLS JMS to stop eccepting the new messages till have enough space.
<There was a failure while performing paging I/O
weblogic.messaging.kernel.KernelException: Error writing messages for paging
at weblogic.messaging.kernel.internal.PagingImpl.performPagingIO(PagingImpl.java:578)
at weblogic.messaging.kernel.internal.PagingImpl.run(PagingImpl.java:488)
Caused By: weblogic.store.PersistentStoreException: [Store:280019]There was an error while writing to a file store file
at weblogic.store.io.file.Heap.multiWrite(Heap.java:479)
at weblogic.messaging.kernel.internal.PagingImpl.performPagingIO(PagingImpl.java:576)
at weblogic.messaging.kernel.internal.PagingImpl.run(PagingImpl.java:488)
Caused By: java.io.IOException: Error writing to file, No space left on device, errno=28
at weblogic.store.io.file.direct.DirectIONative.write(Native Method)
at weblogic.store.io.file.direct.DirectFileChannel.write(DirectFileChannel.java:173)
at weblogic.store.io.file.StoreFile.write(StoreFile.java:255)Thanks

Thanks for the info but the question is how do I know what quotas to set. So the one getting the above error weblogic jms should stop taking any messages until there's enough space available. As currently it keeps accepting the messages and we den up restarting the servers.
Currently under JMS Server configurations everything is set to -1 and in connection factory timeout is set to 10 ms.
Thanks

How to deploy a MDBean into cluster with only one JMS server instance running on one of the cluster servers

          I am trying to deploy a MDBean in my cluster ( two servers). The MDBean requires
          the destinestion has to each cluster server. It means that I have to deploy my
          JMS server over the cluster. This will result multiple destinations (queue or
          topic) are created.
          Is there a way to run one JMS server with a clustered MDBean?
          Thanks,
          Taohe


Check out my posting from 4-3 in this thread.
http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=5&jump=true
I think I may have answered your question before you asked it.
In that example I use the picture control to manipulate a bunch of rectangular images of booleans.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

MDB on OC4J consuming from a forign JMS Server

I would like to create MDBs and deploy them to OC4J. But these MDBs need to consume messages from non-AQ JMS Servers. We are currently using MDBs in OC4J that consume from Oracle AQ using resource adapters. But we now have a need to use other JMS servers such as OpenJMS and JbossMQ.
I have read documents that seem to indicate
Message-driven beans are supported only for Oracle JMS.
Does this mean I cannot create a resource adapter for JbossMQ and deploy a MDB to OC4J that consumes from this JMS Server?
Any help would be most appreciated!
Thanks, Paul.

Anybody has faced similar issue?

JMS Server JNDI not being replicated? (clustered environment)

Hello,
First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
My current production and test environments consist, each one of them, of
clusters with one admin server (ProdAdmin) and two managed servers (Prod1
and Prod2). One of the managed servers (Prod1) is the server to which the
JMS server is deployed and everything works fine.
Now I'm trying to add another managed server to the cluster. The idea is to
target the JMS Server (and nothing else) to this node. We don't want the JMS
server to be running in Prod1 and the new server, named ProdJMS, won't even
have any deployed beans or the startup class targeted to it. Just the JMS
server. Here our problems start.
I'm able to start this ProdJMS node with no problems. However, when I start
Prod1 it seems that the JMS server is not binded. This is the exception
we're getting when a message-driven bean is being deployed (I get the same
exception trying to create other):
------- snip -------------
<May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
CacheUpdateBean is unable to connect to the JMS
destination: securityChanges. The EJB container will automatically attempt
to re-establish the connection with the JMS s
erver. This warning may occur during WebLogic Cluster start-up if the JMS
destination is located on another WebLogic Ser
ver instance. When the JMS server connection is re-established, the
Message-Driven EJB will again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Error creating session
Start server side stack trace:
weblogic.jms.common.JMSException: Error creating session
at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------- Linked Exception -----------
weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
Prod1, javax.naming.NameNotFoundException: Un
able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
Unresolved:'S:Prod1' ; remaining name ''
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
.java:260)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
anager.java:307)
at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
------- snip -------------
If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
actually able to see "weblogic.jms.S:Prod1", which is the name that seems
not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
everything works fine. If I deploy the JMS server to a server with only the
JMS server I get the mentioned JNDI exception.
I would appreciate if you could give me help me solving this problem.
Thanks in a dvance for any help.
Andre Mendonca

First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
My current production and test environments consist, each one of them, of
clusters with one admin server (ProdAdmin) and two managed servers (Prod1
and Prod2). One of the managed servers (Prod1) is the server to which the
JMS server is deployed and everything works fine.
Now I'm trying to add another managed server to the cluster. The idea isto
target the JMS Server (and nothing else) to this node. We don't want theJMS
server to be running in Prod1 and the new server, named ProdJMS, won'teven
have any deployed beans or the startup class targeted to it. Just the JMS
server. Here our problems start.
I'm able to start this ProdJMS node with no problems. However, when Istart
Prod1 it seems that the JMS server is not binded. This is the exception
we're getting when a message-driven bean is being deployed (I get the same
exception trying to create other):1. Make sure that you are using a dif multicast address for each cluster
2. Remove the JMS from Prod1 -- double check this!
3. Stop Prod1 and Prod2
4. Start the ProdJMS
5. Restart Prod1 and Prod2
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Andre Mendonca" <[email protected]> wrote in message
news:[email protected]...
Hello,
------- snip -------------
<May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
CacheUpdateBean is unable to connect to the JMS
destination: securityChanges. The EJB container will automatically attempt
to re-establish the connection with the JMS s
erver. This warning may occur during WebLogic Cluster start-up if the JMS
destination is located on another WebLogic Ser
ver instance. When the JMS server connection is re-established, the
Message-Driven EJB will again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Error creating session
Start server side stack trace:
weblogic.jms.common.JMSException: Error creating session
atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------- Linked Exception -----------
weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
Prod1, javax.naming.NameNotFoundException: Un
able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
Unresolved:'S:Prod1' ; remaining name ''
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
.java:260)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
anager.java:307)
atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
------- snip -------------
If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
actually able to see "weblogic.jms.S:Prod1", which is the name that seems
not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
everything works fine. If I deploy the JMS server to a server with onlythe
JMS server I get the mentioned JNDI exception.
I would appreciate if you could give me help me solving this problem.
Thanks in a dvance for any help.
Andre Mendonca

JMS Server is not Migrating to other Managed Server using Databse Leasing

Hi,
WLS 10.3 on Linux Itanium.
I Tried JMS Server migration but its not working.
Below is the Configuration Details :-
1. Cluster with three managed servers( MS1,MS2,MS3 )
2.JMS Server is targeted on MS1(migratable)
3.created Persistant store as JDBC store for JMS Server and targeted it to MS1(migratable)
4.Environment -> Cluster->Migration Tab
-Migration Basis :- Database
-DataSource For Automatic Migration -> DS1
     -Auto Migration Table Name:(ACTIVE)
5.Created a table ACTIVE as per schema given in WL_HOME/server/db/dbname/leasing.ddl (I am using Oracle database at backend and Database is running and accessible)
6.Created Jms module (say module1)
-target module1 to Cluster.
7.Create Subdeployment(say "sub1") and target to JmsServer
8.Create Queue.and select subdeployment as "sub1" which was created above.
9.I am using default JMSXAconnectionfactory
10.Environment -> Migratable Targets->Select MS1(Migratable)->Migration tab
-Service Migration Policy->Auto Migration Exactly Once Service
               -Constrained Cadidate Servers :-
               Selected all the servers in that cluster
but when I check the Current Server for JMS Server (It should be MS1) which is not displayed. The field in the table is blank.
(Environment->Messaging->JMS Server->here i checked the Current Server for JMS Server )
with the above setting I did it successfully on windows platform. I am able to see Current Server as MS1.and when I shutdown MS1 it changes to either MS2 or MS3
but when I am doing it on Winodows I am explicitly creating connection factory and targeting it to cluster.but on linux platform I am not creating any connection factory(default JMS XA Connection Factory is used)
I have tried a lot to find why its not working but didnt get any idea why so happened?
Required your help
Thanks in Advance ........

I managed to start my managedserver.The issue was with startmanagedserver command.I modified it to my need.

JNDI Names of JMS server's queue not replicating to cluster

          Am having some trouble configuring a JMS Server and Queues in a clustered development
          environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
          a single machine.
          The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
          names for the Queues appear in the JNDI tree of Server1, but not in Server2.
          When the sending of a message is attempted on Server2, the following occurs:
          javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
          didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
          This may be a problem with the cluster configuration, but I haven't been able
          to see anything wrong with it.
          Any and all help will be appreciated.
          There is the Config.xml file:
          <?xml version="1.0" encoding="UTF-8"?>
          <Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
          <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
          ListenPort="7001" Name="myserver" NativeIOEnabled="true"
          ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <SSL Enabled="false" HostnameVerificationIgnored="false"
          IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
          <Log Name="myserver" NumberOfFilesLimited="true"/>
          </Server>
          <Security Name="mydomain"
          PasswordPolicy="wl_default_password_policy"
          Realm="wl_default_realm" RealmSetup="true">
          <weblogic.security.providers.authentication.DefaultAuthenticator
          Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authentication.DefaultIdentityAsserter
          ActiveTypes="AuthenticatedUser"
          Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultRoleMapper
          Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultAuthorizer
          Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultAdjudicator
          Name="Security:Name=myrealmDefaultAdjudicator"
          Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
          <weblogic.security.providers.credentials.DefaultCredentialMapper
          Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
          <weblogic.management.security.authentication.UserLockoutManager
          Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
          <weblogic.management.security.Realm
          Adjudicator="Security:Name=myrealmDefaultAdjudicator"
          Auditors="Security:Name=myrealmSTARSIIAuditor"
          AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
          Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
          CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
          DefaultRealm="true" DisplayName="myrealm"
          FullyDelegateAuthorization="true"
          Name="Security:Name=myrealm"
          RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
          <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
          ControlFlag="SUFFICIENT"
          Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
          <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
          ExemptUri="/common/,/images/,/warning.do,/login.do"
          Name="Security:Name=myrealmSTARSIIAuthorizer"
          PolicyDeploymentEnabled="false"
          Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
          <gov.fns.starsii.common.security.audit.STARSIIAuditor
          Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
          </Security>
          <EmbeddedLDAP
          Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
          <SecurityConfiguration
          Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
          Name="mydomain" RealmBootStrapVersion="1"/>
          <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          <FileRealm Name="wl_default_file_realm"/>
          <PasswordPolicy Name="wl_default_password_policy"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII BRSB Pool"
          Password="{3DES}9pslRpr051lR9/NEKdanag=="
          Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
          PoolName="STARSII Store Pool" Targets="MyCluster"/>
          <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
          PoolName="STARSII Store Pool" Targets="MyCluster"/>
          
          <MailSession JNDIName="mail/STARSIIMailSession"
          Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Store Pool"
          Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          Targets="MyCluster"
          TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="AffTest" Password=""
          Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
          PoolName="AffTest" Targets=""/>
          <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
          Name="Spy STARSII BRSB Pool"
          Password="{3DES}9pslRpr051lR9/NEKdanag=="
          Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Store Pool 2"
          Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
          PoolName="STARSII Store Pool" Targets=""/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Stars Pool"
          Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
          Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
          Targets="MyCluster"
          TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <Machine Name="MachineA">
          <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
          </Machine>
          <Server Cluster="MyCluster" ExpectedToRun="false"
          ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
          ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
          Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <ServerDebug Name="Server1"/>
          <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
          <KernelDebug Name="Server1"/>
          <Log Name="Server1"/>
          <ServerStart Name="Server1"
          OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
          Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          <WebServer Name="Server1"/>
          <COM Name="Server1"/>
          <IIOP Name="Server1"/>
          <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
          <JTARecoveryService Name="Server1"/>
          </Server>
          <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
          MulticastAddress="226.0.0.244" Name="MyCluster"/>
          <Server Cluster="MyCluster" ExpectedToRun="false"
          ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
          ListenPort="7002" Machine="MachineB" Name="Server2"
          ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <ServerDebug Name="Server2"/>
          <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
          <KernelDebug Name="Server2"/>
          <Log Name="Server2"/>
          <ServerStart Name="Server2"
          Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          <WebServer Name="Server2"/>
          <COM Name="Server2"/>
          <IIOP Name="Server2"/>
          <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
          <JTARecoveryService Name="Server2"/>
          </Server>
          <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
          Notes="This is a system generated default migratable target for a server.
          Do not delete manually." UserPreferredServer="Server1"/>
          <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
          Notes="This is a system generated default migratable target for a server.
          Do not delete manually." UserPreferredServer="Server2"/>
          <Application Deployed="true" Name="STARSII"
          Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
          <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
          <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
          <EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
          <EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
          <EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
          <EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
          <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
          <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
          <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
          <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
          <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
          </Application>
          <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
          StagingMode="nostage" TwoPhase="true">
          <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
          </Application>
          <Application Name="activeportal"
          Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
          StagingMode="nostage" TwoPhase="true">
          <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
          </Application>
          <JTA Name="mydomain" TimeoutSeconds="300"/>
          <JMSServer Name="JobServer" Targets="Server1 (migratable)">
          <JMSQueue CreationTime="1072820642598"
          JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
          <JMSQueue CreationTime="1072820669345"
          JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
          <JMSQueue CreationTime="1088000795852"
          JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
          <JMSQueue CreationTime="1072820687125"
          JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
          <JMSQueue CreationTime="1072820687125"
          JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
          <JMSQueue CreationTime="1072820687225"
          JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
          <JMSQueue CreationTime="1072820687325"
          JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
          <JMSQueue CreationTime="1072820687425"
          JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
          <JMSQueue CreationTime="1072820687525"
          JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
          <JMSQueue CreationTime="1072820687625"
          JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
          <JMSQueue CreationTime="1072820687725"
          JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
          <JMSQueue CreationTime="1072820687825"
          JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
          <JMSQueue CreationTime="1072820687925"
          JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
          <JMSQueue CreationTime="1072820688025"
          JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
          <JMSQueue CreationTime="1072820688125"
          JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
          <JMSQueue CreationTime="1072820688225"
          JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
          <JMSQueue CreationTime="1072820688325"
          JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
          </JMSServer>
          <Machine Name="MachineB">
          <NodeManager DebugEnabled="true" Name="MachineB"/>
          </Machine>
          </Domain>


Internally, many BEA developers and testers use various versions
          of XP with clustering on a daily basis. I don't know what
          is unique about your machine. I suggest raising the issue
          with customer support and/or posting to the clustering newsgroup...
          Andy Frank wrote:
          > It would seems that my OS and the MultiCast config are to blame. The MultiCast
          > test utility worked fine the Win2K machines I tried. Think I will take another
          > look at MS KB article 827536 and/or think about another dev OS.
          >
          > "Andy Frank" <[email protected]> wrote:
          >
          >>Tom,
          >>Thanks for this info.
          >>
          >>My servers don't look like they are running in different subnets (had
          >>a friend
          >>look this over and he concurs).
          >>
          >>My network admin says he hasn't blocked multicast traffic.
          >>
          >>I think the MultiCast test utility is telling me that I have some kind
          >>of multicast
          >>config problem. Output follows:
          >>
          >>------ Begin MultiCast test utility output: ------
          >>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
          >>237.155.15
          >>5.1 -t 15
          >>***** WARNING ***** WARNING ***** WARNING *****
          >>Do NOT use the same multicast address as a running WLS cluster.
          >>
          >>
          >>Starting test. Hit any key to abort
          >>
          >>
          >>Using multicast address 237.155.155.1:7001
          >>Will send messages under the name server200 every 2 seconds
          >>Will print warning every 15 seconds if no messages are received
          >>
          >> I (server200) sent message num 1
          >> I (server200) sent message num 2
          >> I (server200) sent message num 3
          >> I (server200) sent message num 4
          >> I (server200) sent message num 5
          >> I (server200) sent message num 6
          >> I (server200) sent message num 7
          >>java.net.SocketTimeoutException: Receive timed out
          >> at java.net.PlainDatagramSocketImpl.receive(Native Method)
          >> at java.net.DatagramSocket.receive(DatagramSocket.java:680)
          >> at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
          >> I (server200) sent message num 8
          >> I (server200) sent message num 9
          >> I (server200) sent message num 10
          >> I (server200) sent message num 11
          >> I (server200) sent message num 12
          >>------ End MultiCast test utility output: ------
          >>
          >>No "Received message X from server200" messages. I think I need to look
          >>into
          >>configuring multicast communications on my OK (Windows XP Pro, ver 2002
          >>SP1).
          >>I did see MS KB article 827536 about "An IP multicast may not be sent
          >>correctly
          >
          >>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
          >
          >>but
          >>the resolution scared me some.
          >>
          >>Think I will try some things out on another OS and see what that gets
          >>me.
          >>
          >>Any other thoughts on this will be appreciated.
          >>
          >>
          >>Tom Barnes wrote:
          >>
          >>>I too suspect something is going wrong with clustering, I wonder
          >>>if the servers are running in different subnets (even though
          >>>they are on the same box) and/or your network admin has
          >>>blocked multicast traffic.
          >>>
          >>>The MultiCast test utility should help narrow things down:
          >>>
          >>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
          >>>
          >>>Tom
          >>>
          >>>Andy Frank wrote:
          >>>
          >>>
          >>>>Am having some trouble configuring a JMS Server and Queues in a clustered
          >>>
          >>>development
          >>>
          >>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
          >>>
          >>>both on
          >>>
          >>>>a single machine.
          >>>>
          >>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
          >>
          >>>All the JNDI
          >>>
          >>>>names for the Queues appear in the JNDI tree of Server1, but not in
          >>>
          >>>Server2.
          >>>
          >>>>When the sending of a message is attempted on Server2, the following
          >>>
          >>>occurs:
          >>>
          >>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
          >>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
          >>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
          >>>>
          >>>>This may be a problem with the cluster configuration, but I haven't
          >>>
          >>>been able
          >>>
          >>>>to see anything wrong with it.
          >>>>
          >>>>Any and all help will be appreciated.
          >>>>
          >>>>There is the Config.xml file:
          >>>><?xml version="1.0" encoding="UTF-8"?>
          >>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
          >>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
          >>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
          >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          >>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
          >>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
          >>>
          >>>Name="myserver"/>
          >>>
          >>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
          >>>> </Server>
          >>>> <Security Name="mydomain"
          >>>> PasswordPolicy="wl_default_password_policy"
          >>>> Realm="wl_default_realm" RealmSetup="true">
          >>>> <weblogic.security.providers.authentication.DefaultAuthenticator
          >>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
          >>>>
          >>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
          >>>> ActiveTypes="AuthenticatedUser"
          >>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultRoleMapper
          >>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultAuthorizer
          >>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultAdjudicator
          >>>> Name="Security:Name=myrealmDefaultAdjudicator"
          >>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
          >>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
          >>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.management.security.authentication.UserLockoutManager
          >>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.management.security.Realm
          >>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
          >>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
          >>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
          >>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
          >>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
          >>>> DefaultRealm="true" DisplayName="myrealm"
          >>>> FullyDelegateAuthorization="true"
          >>>> Name="Security:Name=myrealm"
          >>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
          >>>>
          >>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
          >>>> ControlFlag="SUFFICIENT"
          >>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
          >>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
          >>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
          >>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
          >>>> PolicyDeploymentEnabled="false"
          >>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
          >>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
          >>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
          >>>> </Security>
          >>>> <EmbeddedLDAP
          >>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
          >>>
          >>>Name="mydomain"/>
          >>>
          >>>> <SecurityConfiguration
          >>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
          >>>> Name="mydomain" RealmBootStrapVersion="1"/>
          >>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          >>>> <FileRealm Name="wl_default_file_realm"/>
          >>>> <PasswordPolicy Name="wl_default_password_policy"/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII BRSB Pool"
          >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
          >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
          >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
          >>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
          >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
          >>>> 
          >>>> <MailSession JNDIName="mail/STARSIIMailSession"
          >>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
          >>>
          >>>Targets="myserver"/>
          >>>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Store Pool"
          >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          >>>> Targets="MyCluster"
          >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="AffTest" Password=""
          >>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
          >>>> PoolName="AffTest" Targets=""/>
          >>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
          >>>> Name="Spy STARSII BRSB Pool"
          >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
          >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
          >>>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Store Pool 2"
          >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
          >>>> PoolName="STARSII Store Pool" Targets=""/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Stars Pool"
          >>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
          >>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
          >>>> Targets="MyCluster"
          >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>> <Machine Name="MachineA">
          >>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
          >>>> </Machine>
          >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
          >>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
          >>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
          >>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
          >>>
          >>>StdoutSeverityLevel="64">
          >>>
          >>>> <ServerDebug Name="Server1"/>
          >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
          >>>> <KernelDebug Name="Server1"/>
          >>>> <Log Name="Server1"/>
          >>>> <ServerStart Name="Server1"
          >>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
          >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          >>>> <WebServer Name="Server1"/>
          >>>> <COM Name="Server1"/>
          >>>> <IIOP Name="Server1"/>
          >>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
          >>>> <JTARecoveryService Name="Server1"/>
          >>>> </Server>
          >>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
          >>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
          >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
          >>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
          >>>> ListenPort="7002" Machine="MachineB" Name="Server2"
          >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          >>>> <ServerDebug Name="Server2"/>
          >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
          >>>> <KernelDebug Name="Server2"/>
          >>>> <Log Name="Server2"/>
          >>>> <ServerStart Name="Server2"
          >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          >>>> <WebServer Name="Server2"/>
          >>>> <COM Name="Server2"/>
          >>>> <IIOP Name="Server2"/>
          >>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
          >>>> <JTARecoveryService Name="Server2"/>
          >>>> </Server>
          >>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
          >>>> Notes="This is a system generated default migratable target
          >>>
          >>>for a server.
          >>>
          >>>>Do not delete manually." UserPreferredServer="Server1"/>
          >>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
          >>>> Notes="This is a system generated default migratable target
          >>>
          >>>for a server.
          >>>
          >>>>Do not delete manually." UserPreferredServer="Server2"/>
          >>>> <Application Deployed="true" Name="STARSII"
          >>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
          >>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
          >>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
          >>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
          >>
          >>URI="../commonSession"/>
          >>
          >>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
          >>>
          >>>URI="../complianceMessage"/>
          >>>
          >>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
          >>>
          >>>URI="../complianceSession"/>
          >>>
          >>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
          >>
          >>URI="../starsiiEntity"/>
          >>
          >>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
          >>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
          >>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
          >>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
          >>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
          >>>> </Application>
          >>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
          >>>> StagingMode="nostage" TwoPhase="true">
          >>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
          >>>> </Application>
          >>>> <Application Name="activeportal"
          >>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
          >>>> StagingMode="nostage" TwoPhase="true">
          >>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
          >>>> </Application>
          >>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
          >>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
          >>>> <JMSQueue CreationTime="1072820642598"
          >>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
          >>>> <JMSQueue CreationTime="1072820669345"
          >>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
          >>>> <JMSQueue CreationTime="1088000795852"
          >>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
          >>>> <JMSQueue CreationTime="1072820687125"
          >>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
          >>>> <JMSQueue CreationTime="1072820687125"
          >>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
          >>>> <JMSQueue CreationTime="1072820687225"
          >>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
          >>>> <JMSQueue CreationTime="1072820687325"
          >>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
          >>>> <JMSQueue CreationTime="1072820687425"
          >>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
          >>>> <JMSQueue CreationTime="1072820687525"
          >>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
          >>>> <JMSQueue CreationTime="1072820687625"
          >>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
          >>>> <JMSQueue CreationTime="1072820687725"
          >>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
          >>>> <JMSQueue CreationTime="1072820687825"
          >>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820687925"
          >>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
          >>>> <JMSQueue CreationTime="1072820688025"
          >>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
          >>>> <JMSQueue CreationTime="1072820688125"
          >>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820688225"
          >>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820688325"
          >>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
          >>>> </JMSServer>
          >>>> <Machine Name="MachineB">
          >>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
          >>>> </Machine>
          >>>></Domain>
          >>>
          >

JMS Server Current Count

Similar Messages

Maybe you are looking for