JMS cluster configuration problem

Problem description:
I have a OC4J cluster with two OC4J instances (referred to as I1 and I2) each having their own JMS Server (referred to JMS1 and JMS2). For certain messaging scenarios (not all) it is necessary that I1 puts a message on a queue of I2.
In order to do that I use the following configuration:
I2 -> jms.xml
<jms-server host="[ALL]" port="9127">
<queue-connection-factory location="xyz.ConnectionFactory" host="I1" />
<queue name="queue1" location="xyz.queue" persistence-file="queue1.file"/>
I1 -> jms.xml
<jms-server host="[ALL]" port="9127">
<queue-connection-factory location="xyz.ConnectionFactory" />
<queue name="queue1" location="xyz.queue" persistence-file="queue1.file"/>
When I try to send a message from I2 to I1, using the connection factory stored under xyz.ConnectionFactory I get the following exception:
Caused by: javax.transaction.RollbackException at com.evermind.server.ApplicationServerTransaction.handleCommitSystemException(ApplicationServerTransaction.java:749) at com.evermind.server.ApplicationServerTransaction.twoPhaseCommit(ApplicationServerTransaction.java:688) at com.evermind.server.ApplicationServerTransaction.commitBasedOnResourceCount(ApplicationServerTransaction.java:514) at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:246) at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:126)
at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:757)
... 45 more
Caused by: oracle.as.j2ee.transaction.tpc.ConnectionLostException: Handing off to RecoveryManager due to lost connection to resource or RMERR. Branch: [null, Xid( Global Id da.f9.b0.f7.ff.ff.ff.ff.0a.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00, Format Id 4660, Branch Id e8.df.1f.91.00.00.00.00.00.00.00.00.00.00.00.01), null, state={ACTIVE}, exception error code=-3]
at oracle.as.j2ee.transaction.tpc.Coordinator.lostResourceCleanup(Coordinator.java:628)
at oracle.as.j2ee.transaction.tpc.Coordinator.checkForLostConnection(Coordinator.java:600)
at oracle.as.j2ee.transaction.tpc.Coordinator.actOnEligibleBranch(Coordinator.java:553)
at oracle.as.j2ee.transaction.tpc.Coordinator.doRollback(Coordinator.java:499)
at oracle.as.j2ee.transaction.tpc.Coordinator.doRollbackWithRollbackException(Coordinator.java:229)
at oracle.as.j2ee.transaction.tpc.Coordinator.doPrepare(Coordinator.java:216)
at oracle.as.j2ee.transaction.tpc.Coordinator.doResolve(Coordinator.java:278)
at oracle.as.j2ee.transaction.tpc.Coordinator.resolve(Coordinator.java:115)
at oracle.as.j2ee.transaction.tpc.TwoPhaseCommitEngine.commit(TwoPhaseCommitEngine.java:93)
at com.evermind.server.ApplicationServerTransaction.twoPhaseCommit(ApplicationServerTransaction.java:686)
... 50 more
Question:
1: Do I use the right configuration for above messaging scenario (the Oracle documentation I’ve read about this subject (High Availability Guide) is very vague) ?
2: So yes, what do I do wrong?
Any help would be greatly appreciated!

Above problem could be resolved.
1. The problem only occured when sending a message within a transaction. Without transaction everything worked fine.
2. Due to this strange behaviour we assumed that this is a bug - and it was. This bug has the issue nummer: 5331629. In version 10.1.3.1.0 this issue is resolved. We tested it and indeed it worked as excpected.

Similar Messages

Sun zfs storage cluster configuration problem

Good day, friends!
I've a very strange problem.
Got two zfs storage *7320* controllers and want to make a cluster. according to manual I should make several clicks to do this, but...
first appliance is configured the second is showing in console :
This appliance is being configured as a member of a cluster.
Please wait while initial configuration takes place.
Initializing cluster ...
for five days!!! i've rebooted the second appliance - no change, still initializing.
Can anyone help? please!!!

I've seen this a bunch of times on our storage. The basic problem is that the head you want to cluster is already "configured". This doesn't necessarily mean you did anything wrong! The usual problem is that someone did the "initial configuration" on both heads. However, it can mean that something may have gone wrong in the initial cluster configuration.
The only way to get past it that I've seen is to add "-c" to the kernel line in Grub when it comes up from a reboot. This does a full factory reset again. So when Grub comes up before the device begins the rest of the boot process, press "e" to edit, then scroll down to the "kernel" line, press "e" again to edit that line, add " -c" to the end of the kernel line, press "escape", then press "b" to boot.
If this seems complicated, contact Support.oracle.com to have a tech do it for you. It's straightforward if you're already familiar with Grub, but not so much if you're not.

JMS Listener configuration problem

I am installing IDM6.0 and trying to use the password synch feature with Active Directory. Below are my environment details
tomcat 5.0.28 on linux
Sun Message Queue 3.6 for JMS
When I am configuring the JMS Listener adapter I am getting the below error. I have installed the Sun Message Queue and storing the administered objects in a file.
Test connection failed for resource(s):
JMS Listener: javax.naming.NameNotFoundException
If anyone has ever done that earlier it will be very helpful for me.
Thanks in advance

Just an update on my last comment
I had tested this on the windows box. The problem may not be there in the Linux

Different behaviour in JMS Cluster automatic failover

Hi,
          I am problem in JMS clustering, now let me explain the scenario.
          I have 2 managed servers participating in the weblogic cluster, now since JMS is a singleton service what i did is i have created 2 JMS servers and targeted them to Managedservers 1 and 2 respectively.I have also created a Distributed Destination and deploy they with the deployment "wizard" ("autodeploy") to all the member of the cluster.
          Now in my case I created two different type of client
          Asynchronous and synchronous .
          The first one register himself as MessageListener and also as ExceptionListener. When I bring down the managed server in which the client is connect the call back method onException is called.
          The second client instead register himself as ExceptionListener but not as MessageListener. It call in different thread the receive method on the destination.
          In this case if i I bring down the managed server in which the client is connect the call back method onException is NOT called, instead i receive the JMSException on all the call "receive".
          I expected that the behaviour was the same of the firts client.
          Thanks in advance.
          dani

Its not clear from your description what you're trying to do, as typical apps use a single module, including those that use distributed destinations, and typical apps do not use the convention of specifying a module name in their JNDI name. (The "!" syntax makes me suspect that you're not using JNDI to lookup destinations, rather you're using the rarely recommended JMS session "createQueue()" call.).
Never-the-less, I suspect the problem is simply that your using a distributed queue and haven't realized that queue browsers and consumers pin themselves to a single queue member. To ensure full coverage of a distributed queue, the best practice is to use a WebLogic MDB: WebLogic MDBs automatically ensure that each queue member has consumers.
By the way, if you are using a distributed queues, then the best practice config is as follows for each homogeneous set of JMS servers:
-- Configure a custom WL store per server, target to the server's default migratable target.
-- Configure a JMS server per server, target to the server's default migratable target, set the store for the JMS server to be the same as the custom store.
-- Configure a single JMS module, target to the cluster.
-- Configure a single subdeployment for the module that references each JMS server (and nothing else).
-- Configure one or more distributed queues for the module. Never use default targeting -- instead use advanced subdeployment targeting to target each distributed queue to the single subdeployment you defined earlier.
-- Configure one or more custom connection factories in the module, use default targeting.
I recommend that you read through the JMS admin and programmer's guides in the edocs if you haven't done so already. You might find that the JMS chapter of the new book "Professional Oracle WebLogic" is helpful.
Tom
Edited by: TomB on Nov 4, 2009 10:12 AM

JMS cluster and happen JMS Queue Exception javax.naming.NameAlreadyBoundExc

Hi,
Sorry I not sure how to setup JMS cluster in WLS 10.3.2. We have two manager server in two machine. And will join into one cluster. After configure the JMS module & JMS server. We found it only can work in one server. And will faill in another server. And reply the error message as below :
Any one can help to tell me why one server success. And other is fail !
javax.naming.NameAlreadyBoundException: JMS_Queue_misdel_a is already bound; rem
aining name ''
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.jav
==> config for JMS
<jms-server>
<name>JMS_Server_cim_a</name>
<target>ebowls05</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<jms-server>
<name>JMS_Server_cim_b</name>
<target>ebowls06</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<migratable-target>
<name>ebowls06 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls06</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<migratable-target>
<name>ebowls05 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls05</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<jms-system-resource>
<name>JMS_ConnFactory_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_ConnFactory_cim/JMS_ConnFactory_cim-jms.xml</d
escriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_promis</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_promis/JMS_Queue_promis-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Template_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_Template_cim/JMS_Template_cim-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_a</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_a/JMS_Queue_misdel_a-jms.xml</des
criptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_b</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_b/JMS_Queue_misdel_b-jms.xml</des
criptor-file-name>
</jms-system-resource>

1 - JMS clustering is an advanced concept, and, in most cases, uses "distributed queues". In case you haven't already, I highly recommend reading the JMS chapter of the new book "Professional Oracle WebLogic" as well as the related chapters in the JMS Programmer's Guide in the edocs.
2 - The basic problem below is that you have two different queues that have matching JNDI names, but are in the same cluster.
3 - The config snippet supplied below does not include the queue configuration. Queue configuration is embedded within the referenced module files.
4 - Please ensure that you follow configuration best practices, as per: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG

Can't run form from Form Builder 10g - Port configuration problem?

Hi,
I have installed the Database (10.2.0.1.0) and the Developer Suite (10.1.2.0.2) on two Linux machines (Red Hat Enterprise Linux ES 4 Basic).
If I enter the frmservlet-URL manually everything seems to be fine.
In one case I enter http://127.0.0.1:8890/forms/frmservlet, in the other http://127.0.0.1:8889/forms/frmservlet; in BOTH cases I get eventually a dark square and the status bar says "Applet oracle.forms.engine.Main started".
HOWEVER, if I create a simple form with Form Builder and click on the Button with the green traffic light ("Run Form"), the form runs only on the machine where frmservlet listens on port 8890.
On the other machine (frmservlet configured to listen on port 8889) Firefox pops up, the URL "http://127.0.0.1:32979/6dOrpwghCqnp8PhMT7KVT533m3IaArqFbPqPBOztZXWYSsNy" gets called, and nothing else happens. The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and it stays like this forever.
I assume this is a port configuration problem, but I don't have a clue where to start.
Any suggestions how I should proceed are greatly appreciated.
Thank you very much in advance!

Hi Frank,
Thank you for your reply.
I doublechecked my configuration.
In the dialog Edit --> Preferences --> Runtime the Application Server URL is set to "127.0.0.1:8889/forms/frmservlet".
However, when I attempt to run the form, the URL "http://127.0.0.1:33140/W2dwbV9eXS2fPkuKlxNhCxFWdEihwDviat2uV7ycrSotqwDN" gets called.
The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and that's it.
I wonder how the port number 33140 got selected. Interestingly, this time it is a different number; last time it was port 32979. In fact, the port number seems to change each time; I tried again and now it is 33189.
I will now try to set the port number for the frmservlet to 8890.
I choose Edit --> Preferences --> Runtime and set the application server URL to "127.0.0.1:8890/forms/frmservlet".
I stop the container, open /home/oracle/OraHome_1/j2ee/DevSuite/config/default-web-site.xml and change the port number to 8890:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE web-site PUBLIC "Oracle Application Server 10g XML Web-site" "http://xmlns.oracle.com/ias/dtds/web-site.dtd">



<web-site port="8890" protocol="http"
display-name="Oracle Developer Suite 10g instance of Oracle Containers for J2EE Web Site">

     
     
     <default-web-app application="default" name="defaultWebApp" root="/j2ee" />

<web-app application="forms" name="formsweb" root="/forms" />


<web-app application ="reports" name="web" root="/reports" />
<web-app application = "reports" name="demo" root="/repdemo" />
     
     <access-log path="../log/default-web-access.log" />
</web-site>
I restart the container, start Form Builder, connect to the database, and open my test form.
When attempting to run the form, the URL "http://127.0.0.1:33437/Pl0n3ky9vmU5z37A7ScBnQhsGwq3jwuzJpgTAKWPMOYIzT8K" gets called (again a new port number, apparently picked radomly within a certain range) and nothing happens: "Waiting for 127.0.0.1...".
However, when I enter the URL http://127.0.0.1:8890/forms/frmservlet I do (eventually, after confirming that I trust the certificate etc.) get a darc rectangle and the status message "Applet oracle.forms.engine.Main started", which tells me that my setup can't be that far off target.
Here is the output of netstat:
[root@localhost ~]# netstat -anp --tcp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 2779/rpc.statd
tcp 0 0 0.0.0.0:23910 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2759/portmap
tcp 0 0 0.0.0.0:1521 0.0.0.0:* LISTEN 4265/tnslsnr
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN 2983/xinetd
tcp 0 0 127.0.0.1:7830 0.0.0.0:* LISTEN 4429/spamd --port 7
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2928/cupsd
tcp 0 0 0.0.0.0:9240 0.0.0.0:* LISTEN 5269/java
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3002/sendmail: acce
tcp 0 0 0.0.0.0:8890 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:32795 0.0.0.0:* LISTEN 4231/ora_d000_orcl
tcp 0 0 127.0.0.1:1521 127.0.0.1:32817 ESTABLISHED 4265/tnslsnr
tcp 0 0 127.0.0.1:32817 127.0.0.1:1521 ESTABLISHED 4209/ora_pmon_orcl
tcp 0 0 127.0.0.1:33425 127.0.0.1:1521 ESTABLISHED 5298/frmbld
tcp 0 0 127.0.0.1:1521 127.0.0.1:33425 ESTABLISHED 5311/oracleorcl
tcp 1 0 80.133.127.83:33485 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33484 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33494 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33520 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 80.133.127.83:33529 209.132.177.100:443 ESTABLISHED 4060/python
tcp 0 0 80.133.127.83:33528 209.132.177.100:443 ESTABLISHED 4060/python
tcp 1 0 80.133.127.83:33460 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33470 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 :::22 :::* LISTEN 2968/sshd
tcp 0 0 ::ffff:127.0.0.1:33437 :::* LISTEN 5298/frmbld
tcp 697 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33439 CLOSE_WAIT -
tcp 348 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33440 CLOSE_WAIT -
[root@localhost ~]#
The question remains: Where do those port numbers come from?
Regards,
jme

Oracle cluster installation problem

hi forums
i need experienced one to discuss with me about this problem and help me to put plan
i install oracle cluster ware 10.2 on my lab
first i install VMWare Workstation 6.5-7x
and i install windows server 2003 and do this configuration
-create 4 scsi harad with size 10 G
-create 5 scsi hard with size 1 g ( 3 for voting dist - 2 for OCR)
- enable automount for windows
- disable sense for new Network card
- 2 network card for public and other for private
- identifying network nodes in the host file
- rename this machin by rac1
- colne this machine and rename it to rac2 and change the public and private ip
----- now i have tow machine rac1,rac2
- check from rac1
cluster media\ckuvfy\runcluvfu.bat stage -pre crsinst -n rac1,rac2 -verbose
was successful
cluster media\ckuvfy\runcluvfu.bat comp ssa -n rac1,rac2
was sc\uccessful
and another check ......................
i begin installing oracle cluster ware
no problem
but after installing on creating cluster configuration assistant it was failed
the question is why this error happen ,although i check on any thing before install !?
i reed more and more and i found this problem happen because terminal service
use this commend
mstsc -v:servername /f - console
but i install local not remote
if any exprince with this please show to me why this error happen !?*
and what is the solution ?
for oracle rac in windows what is the best use VMWare or windows alone ?

Hi,
Check the below link to match your steps and verify according:
http://www.oracle-base.com/articles/10g/OracleDB10gR2RACInstallationOnWindows2003UsingVMware.php
For practise and test purpose VMWARE is definetly a better choice.Check the below link which can help
you why it is better to use VMWARE.
http://blogs.vmware.com/performance/2007/11/ten-reasons-why.html
Best regards,
Rafi.
http://rafioracledba.blogspot.com/

Jms adapter configuration and testing

Hi,
Please inform the JMS adapter configuration and testing.
Thanks
Naidu

Hi,
tried to reach JMS adapter but was not sure about what to inform it with
Ok, just being silly there... About your problem:
Overview - not complete and a little dated but notetheless good starting point
Exploring JMS and SAP-XI JMS Adaper
JMS FAQ Note - valuable official statements for various questions. Many linked notes which may also be of interrest
http://service.sap.com/sap/support/notes/856346
Driver deployment note
http://service.sap.com/sap/support/notes/1138877
Some other valuable links provided by Chirag Gohil
Re: jms senarios
HTH for starters
Cheers
Jens

Windows 2003 Standard Edition (Cluster Configuration Storage page)

I am trying to install RAC R2 on windows Server 2003 (Standard Edition). I am using FireWire 800 SIIG to connect to Maxtor OneTouch III External HDD.
When installing cluster Services, i do not see the Cluster Storage Devices. When i go to Computer Management, i see all the partitions of the raw device.
One "Cluster Configuration Storage" page, the Available Disks show no partitions.
Oracle installtion documentation says "On the Cluster Configuration Storage page, identify the disks that you want to use for the Oracle Clusterware files and, optionally, Oracle Cluster File System (OCFS) storage. Highlight each of these disks one at a time and click Edit to open the Specify Disk Configuration page where you define the details for the selected disk"
In my case, i do not see any disks. What am i missing?
Any Thoughts. Please advise
Thanks
-Prasad
Message was edited by:
pinjam

You have a more fundamental problem, Firewire disks will not work for RAC on Windows. The storage needs to be shared, Firewire disks can't be shared on Windows. On Linux, Oracle took the open source firewire driver and modified it to allow more than one host to connect. On Windows the driver is closed source so they can't do that.
I presume you are wanting to try-out RAC on Windows, If so another solution may be to download one of the many iSCSI Servers that are available. Microsoft ship an iSCSI Initiator for Windows, this allows you to share a 'block device' which is what RAC needs - then you can choose your RAC Database storage method of choice, ASM, OCFS, RAW. I prefer ASM

No partitions avalilable on Page Cluster configuration storage

hello all,
I am trying to install RAC R2 on windows Server 2003 (Standard Edition) with 2 nodes.
When installing Clusterware. I can't see all the partitions of the raw device but When i go to Computer Management, i see all of them.
One "Cluster Configuration Storage" page, the Available Disks show no partitions.
I have check the next document:
http://download.oracle.com/docs/cd/B19306_01/install.102/b14207/storage.htm#sthref244 But Unfortunately I can´t solve the problem
Please Advice, Thanks in advance.
Regards
Ivan R

I presume you have tried and failed to install a few times and each time the list of partitions available has decreased.
if you have access to metalink you should see note :341214.1 on how to correctly clean up a failed install.

The local node entry in Cluster Configuration information does not match wi

In installing 10.1.0.3 CRS on Solaris 8 x86, I keep getting the error, "The local node entry in Cluster Configuration information does not match with the entry in /etc file." Both addresses are defined in the /etc/inet/hosts and are pingable. There seems to be no way to get past this issue. Earlier I installed 10.2.0.1 CRS on SLES9 SP2 on a system with the same network settings and had no problem. Is there some way to force the installer to accept the addresses given and proceed past this step?

All,
I think there can be two problems
1.
if your host file looks as follows
# Public
192.168.2.x rac1.localdomain rac1
192.168.2.x rac2.localdomain rac2
#Private
192.168.0.x rac1-priv.localdomain rac1-priv
192.168.0.x rac2-priv.localdomain rac2-priv
#Virtual
192.168.2.x rac1-vip.localdomain rac1-vip
192.168.2.x rac2-vip.localdomain rac2-vip
then you should be able to do rsh or ssh sucessfully for each aliases at least one from each nodes
(ex)
on node rac1
ssh rac1 date
ssh rac1.localdomain date
ssh rac2 date
ssh rac2.localdomain date
2. you should create user equivalance on all the nodes as follows
Edit the /etc/hosts.equiv file to include all the RAC nodes:
+rac1 oracle
+rac2 oracle
+rac1-priv oracle
+rac2-priv oracle

Really strange cluster isolation problem....

We are still using Coherence 3.6.0 and is experiencing a really strange problem with two test clusters:
Cluster 1 uses wka a.b.c.d:9000 and cluster name "cluster1"
Cluster 2 uses wka e.f.g.h:9000 and cluster name "cluster2"
I can using JMX and log files see that both clusters have started successfully with node 1 (the single wka) using port 9000.
A client program first connects successfully to cluster 1 (using cluster 1 wka and cluster name as above). After the program terminate the same client program is run again this time versus cluster 2 (using cluster 2 wka and cluster name as above) but this time the connection is refused and to our total surprise the error message indicates that the Cluster 1 wka node a.b.c.d:9000 has refused connection and that the cluster name should be "Cluster 1"!!!!!!! We have checked and re-checked that the right combination of wka and cluster name (for cluster 2) is specified on the command line the second time....
Short of a DNS configuration problem (we are in fact using server names rather than physical IPs in the command line overrides) that would resolve the two wka node names to the same physical IP I cant see any solution (not involving woodo, alien intervention and/or the Bermuda triangle) to this behaviour. I actually tried pinging the two host names and could see that they indeed resolved to different IPs to eliminate this, unlikely but possible, problem...
It is my understanding that when specifying a unique wka for two clusters there is no need to set up unique multicast addresses / ports (since multicast is not at all used in this case) - can somebody confirm that this is indeed true or if this could have anything to do with our problem?!
Any suggestions or ideas (in addition to hiring a shaman to exorcise our servers :-)) are warmly appreciated...
/Magnus

After studying the problem more in detail I have come to the conclusion that this indeed seem to be a bug in Coherence 3.6.0. It does however not occur with 3.6.1 or 3.7.0 but if the problem is unknown I would have checked it out...
The problem is really easy to reproduce. Create two clusters (can be single storage node, local or remote does not matter) each with a unique WKA port (of course).
Execute a simple client program (non storage enabled) first against the one cluster then against the other. The program I used just looked up a cache ("near-test") and printed its size (in this case zero since I never loaded anything into the cluster).
You don't need to enable pof or anything specia. The cache-config iin the coherence.jar works fine. I have tested this both on distributed clusters on Linux and locally on a single Windows box.
You will notice that the program works against the first cluster but fails when run against the second.
/Magnus

Weblogic JMS Cluster

Hi,
          I have a 6.1 cluster that has a JMS server A and a JMS Server B
          deployed and running on each of the managed nodes. As destination I
          created a topic with the same name for each JMS Server. The connection
          factories I deployed to the cluster only.
          My problem is, when I start the second managed server, I get the
          following error:
          <Error> <Cluster> <Conflict start: You tried to bind an object under
          the name
          com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          have bound
          from 169.59.5.26 is non clusterable and you have tried to bind more
          than once
          from two or more servers. Such objects can only deployed from one
          server.>
          When I understand correctly, this happens because the JNDI tree gets
          distributed to all nodes of the cluster, so there would be two object
          with the same name. How do I solve this situation? Do I have the
          specify different names for topics in different JMSServer running in a
          cluster? How would the load balancing work?
          Please help. Thanks in advance
          Juerg


Tom,
          Thanks for your help so far, I installed the patch and got things
          working. However I still have some open points where you might be able
          to help.
          Let's assume I don't have these smart forwarders and I have four
          topics per JMSServer deployed to two managed nodes. Connection
          factories deployed to the cluster. When I connect N publishers
          through the cluster, messages from one publisher end up in the
          appropriate topic on nodeA, messages from another publisher end up in
          the appropriate topic on nodeB. Now when I connect a durable
          subscriber via the cluster I only get messages from topics from one of
          the managed nodes, right? (This is exactly what I am seeing in my
          tests) Connecting durable subscribers to each managed node is not
          possible because of JNDI (throws exception like
          InstanceAlreadyExists). How would I connect a subscriber so that it
          subscribes to the right topics on the right node ( one the works with
          the previously described publisher)?
          All this leads me to the conclusion, that without the forwarders, a
          JMS cluster with Weblogic 6.1 is not so powerful, it basically does
          just load balacing.
          Is this correct or am I missing something important here?
          Thanks a lot and have a nice weekend
          Juerg
          Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > Juerg Staub wrote:
          > > Tom,
          > >
          > > Thanks a lot. Bascially I did everything right, just need the patch.
          > >
          > > In the other hand I'd like to know what the benefits of the smart
          > > forwarders would be. When I understand correctly, every message would
          > > be forwarded to the appropriate topic in the different JMS servers.
          > > What would that bring in the case of a failure(one node of a cluster
          > > goes down)? As far as I can see, I still would need to 're-establish'
          > > the connection factory, topic session, topic and publisher in order to
          > > publish messages again?
          > >
          >
          > Yep. I think we are on the same page:
          >
          > The "smart-forwarders" would do what the 7.0 distributed topic
          > forwarders do for you. They would forward messages bound to
          > a particular physical topic to all instances of the topic.
          > This can be implemented via a durable subscription on a
          > member topic by each remote member topic's host.
          > MDBs could be used to service the durable subscription,
          > as they already have the reconnect logic built in.
          > (Durable subscriptions are used if you wish to guard against
          > lost messages). The forwarders
          > need to change a property on the message to indicate
          > that the message is already forwarded, and forward
          > only messages that have'nt been forwarded (to prevent
          > endless loops!).
          >
          >
          > > Thanks
          > >
          > > Juerg
          > >
          > > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > >
          > >>I suggest you read the "emulating 7.0 distributed destinations"
          > >>section of the JMS performance white-paper available on dev2dev.bea.com.
          > >>You will need to apply the referenced enhancement patch on top of SP3 to
          > >>disable JNDI replication (or update to 6.1SP4).
          > >>
          > >>If you need to create a true distributed topic, you will also need to
          > >>write your own "smart-forwarders" to forward messages
          > >>between the different physical instances of the topic. Or simply
          > >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
          > >>
          > >>Tom
          > >>
          > >>Juerg Staub wrote:
          > >>
          > >>>Hi,
          > >>>
          > >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
          > >>>deployed and running on each of the managed nodes. As destination I
          > >>>created a topic with the same name for each JMS Server. The connection
          > >>>factories I deployed to the cluster only.
          > >>>
          > >>>My problem is, when I start the second managed server, I get the
          > >>>following error:
          > >>>
          > >>><Error> <Cluster> <Conflict start: You tried to bind an object under
          > >>>the name
          > >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          > >>>have bound
          > >>>from 169.59.5.26 is non clusterable and you have tried to bind more
          > >>>than once
          > >>>from two or more servers. Such objects can only deployed from one
          > >>>server.>
          > >>>
          > >>>
          > >>>When I understand correctly, this happens because the JNDI tree gets
          > >>>distributed to all nodes of the cluster, so there would be two object
          > >>>with the same name. How do I solve this situation? Do I have the
          > >>>specify different names for topics in different JMSServer running in a
          > >>>cluster? How would the load balancing work?
          > >>>
          > >>>
          > >>>Please help. Thanks in advance
          > >>>
          > >>>Juerg
          > >>

Good afternoon.I have a computer with W Vista 8, Windows office home and business 2013. I recently tried to install Photoshop Elements by CD with serial number but on the desktop appears the following message: error 1 (configuration problem) try to uninst

What's error 1 in adobe photoshop elements configuration? I have a computer with W Vista 8, Windows office home and business 2013. I recently tried to install Photoshop Elements by CD with serial number but on the desktop appears the following message: error 1 (configuration problem) try to uninstall and reinstall. I have done this but the message continues to appear

You haven't mentioned which version of PSE. If it is PSE 13, that requires a minimum of windows 7.

Itunes starts but fails to open due to audio configuration problem

Hi
I have been running itunes 7.1 quite successfully until today. Running on windows xp/toshiba laptop.
Problem occurs when i select itunes on desktop, itunes appears on task bar below, after a number of seconds the following error message appears "itunes cannot run because it has detected a problem with your audio configuration", once I click ok on this message itunes terminates.
No changes have been made to my audio configuration (to the best of my knowledge), i can run Windows Media Player and that works fine, so too real player.
I reinstalled itunes, but this did not resolve the problem. I also ran itunes from another logon on my laptop and that presented the same error. I checked all my audio settings in the control panel and also ran the diagnostics on each device and all appears to be fine.
Has anybody faced the same issue, and could anybody advise on any diagnistic tool that could assist in pinpointing the configuration problem?.
Thanks
Toshiba Satellite Windows XP Pro

Hi
Got it resolved, thanks for the prompt responses all!.
Resolved by removal current version of Quicktime thru the control panel (add/remove programs), and then reinstalled from the website.
Phew!
Toshiba Satellite Windows XP Pro

JMS cluster configuration problem

Similar Messages

Maybe you are looking for