Behaviour after network failure

I am running two systems connected via Coherence Extend. I have a nearscheme on each and a backing map is connected via extend. I'd just like to clarify how Coherence should behave in the following scenarios. The backing map of system A is populated with 20 objects, system B now loads an object that resides in the backingmap of system A. B should have access to this object correct? If the WAN between the two systems goes down, should the backing map of both systems then both contain those 20 objects? If while in this 'island' state another 40 documents are saved into system B's backing map (A now has 20 and B has 60) how will the backing maps react once the WAN comes back up? Which objects will have precedence and is there any hook into this process of re-synchronisation so that custom logic can be applied to this process?
Thanks
Richard

Another question to add is this. If I have two members sharing a distributed cache they are part of the same cluster, and my cluster has two members. Now if I connect two members via a distributed cache using extend, I have two clusters with two seperate members. Is there anyway to make my extend members part of the same cluster?
The reason I ask this is as follows. If I have two members on the same box connected via a distributed cache and put 10 objects in member 1, I can then call invokeAll on member 2. This results in roughly 5 objects on each member responding to the invokeAll. This is as I expect as the distributed cache has done its jobs a balanced the load over both members. Now if I run the above scenario in the extend situation, when I call invokeAll on member2 the cache contains no items as they all reside in member1. Is there anyway to force a load balance when the two members of the distributed cache are connected via extend?
Richard

Similar Messages

Cluster node reboots after network failure

hi all,
The suncluster 3.1 8/05 with 2 nodes (E2900) was working fine without any errors in the sccheck.
yesterday one node rebooted saying a network failure,errors in the massage file are
Jan 17 08:00:36 PRD in.mpathd[221]: [ID 594170 daemon.error] NIC failure detected on ce0 of group sc_ipmp0
Jan 17 08:00:36 PRD Cluster.PNM: [ID 890413 daemon.notice] sc_ipmp0: state transition from OK to DOWN.
Jan 17 08:00:47 PRD Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource PROD status on node PRD change to R_FM_DEGRADED
Jan 17 08:00:47 PRD Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource PROD status msg on node PRD change to <IPMP Failure.>
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 529407 daemon.notice] resource group CFS state on node PRD change to RG_PENDING_OFFLINE
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_MON_STOPPING
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_monitor_stop> for resource <PROD>, resource group <CFS>, timeout <300> seconds
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hafoip_monitor_stop> completed successfully for resource <PROD>, resource group <CFS>, time used: 0% of timeout <300 seconds>
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_ONLINE_UNMON
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_STOPPING
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_stop> for resource <PROD>, resource group <CFS>, timeout <300> seconds
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource PROD status on node PRD change to R_FM_UNKNOWN
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource PROD status msg on node PRD change to <Stopping>
Jan 17 08:00:51 PRD ip: [ID 678092 kern.notice] TCP_IOC_ABORT_CONN: local = 172.016.005.025:0, remote = 000.000.000.000:0, start = -2, end = 6
Jan 17 08:00:51 PRD ip: [ID 302654 kern.notice] TCP_IOC_ABORT_CONN: aborted 53 connections
what can be the reason for reabooting?
is there any way to avoid this, with only a failover?
rgds
Message was edited by:
suj

What is in that resource group? The cause is probably something with Failover_mode=HARD set. Check the manual reference section for this. The option would be to set the Failover_mode=SOFT.
Tim
---

Iblck release after computer crash or network failure

We are controlling equipment using ENET/1000 devices. The controlling computer has a redundant computer in case the primary fails. We use iblck to protect the bus when the equipment is under active control and need to restore service quickly if the computer fails. We have confirmed that the ENET/1000 does retain the lock after a failure however have not tested the duration of the timeout. How long does an ENET/1000 maintain a lock after it looses connection to the requesting thread and can this timeout be managed in any way?

Error handling won't work in this case, unless there is something I missed in the documentation. Only the process/thread that issued the IBLCK to an ENET/1000 can release it. If the computer that crashes is the one that issued the IBLCK, then there is no error handling that can be done.
Note we simulated the computer hard crashing by shutting down the network interface which effectively silently severs the connection to the ENET/1000 from that computer.
When we start the application up on the backup computer we cannot start utilizing the ENET/1000 bus until the ENET releases the previous lock from the crashed computer. According to the NI 488.2 driver manual, only the thread issueing the IBLCK can release it. Since that computer effectively hard crashed, there is no way to clear the IBLCK from a command since that thread is gone. I see no error handling that can capture this. We appear to be at the mercy of the ENET/1000 to release the lock. So we are looking to understand if that timeout is consistent, what the duration is, and is there any way to modify the timeout?
Thanks for your response,
Tom

Hard Drvie Failure (twice after network problem!)

Hi I have a MSI K7N2 Delta-L SKT A 8xAGP DDR400 Nforce2 6ch Sound LAN USB 2.0 Motherboard just over a year old. Whilst networking with my laptop the main pc went into blue screen state but as I was able to carry on with my internet connection I left it for about an hour. Upon trying to turn on the next morning it would not recognise my hard drive and it was making an awful noise. I replaced the hard drive and reinstalled windows all ok for the last week (apart from an icon by the clock saying that one LAN connection had limited connectivity issues - my linksys 5 port hub was connected). However last night I again networked but was unable to access the internet on my laptop - this morning the new drive is making an awful noise and I am getting the same disc read errors??????
Is this likely to mean a new MOBO and if so is it possible that the hard drives r ok but something is wrong with the MOBO? Also is it likely that the processor, graphics card and ram r damaged??
Thanks in advance...

The power supply has been upgraded 11 month ago due to the machine restarting after upgrading to the MSI board and quicker processorb with no observed faults. I am running:
Jeantech 400w atx power supply
1 x AMD Athlon XP2500 333FSB 512 L2 Cache Barton Retail Boxed Inc Heatsink & Fan with 3year Warranty
1 x MSI Fx5700-TD128 8x AGP 128MB TV-Out DVI DirectX 9 Retail Box
1 x MSI K7N2 Delta-L SKT A 8xAGP DDR400 Nforce2 6ch Sound LAN USB 2.0 Motherboard
1024mb ram (2x512)
LG DVD rewriter
Plain DVD ROM
Card reader
floppy x 1
160gb Baracuda drive
40gb Maxtor drive
both making bad noises and not being detected at startup by bios
A friend has suggested resetting the bios via the mobo jumper (just gunna check there is 1)
Same fault has happened twice after networking (which had been fine previously) only difference was the blue screen and then the limited connectivity message the second time so i think it is unlikely to be a psu fault as it had been stable for 11 months. More likely to be mobo is my first impression although it has been great upto now.
Thanks

JMS adapter webspehere mq, network failure - stop

Hello,
After a network failure the JMS sender adapter (JMS --> XI) goes red, and doesn't automatically recover after a network failure. It is necessary to manually stop and start the adapter. This is bad design from SAP. You would like it to behave like the ftp adapter which automatically continues to poll for files after a network outage.
What can be done to overcome this bad design?
I'm on XI SP 18.
My Idea is to use the new AAM described in
SAP Note 766332
1. com.sap.aii.af.service.administration.cpa: Channel-related interfaces and APIs
2. com.sap.aii.af.service.administration.monitoring: Monitoring interfaces and APIs
3. com.sap.aii.af.service.administration.i18n: Localization interfaces and APIs
I would like to write a standard j2se application to connect using jndi to list the status of the channels, and then stop and start depending on status.
Which jar files should be included?
Example code?

Hello,
I have now built a workaround solution based on the AAM API.
It is implemented as a J2EE stateless session bean and a J2EE client. The client reads config with information about which channels to restart and calls the bean which checks status on the channels and restarts the ones with errors or in a stopped state. We schedult the program to run every 5 minutes and check the status.
Check the channelstatus.jsp for hints on how to use the api.
It's a pity SAP hasn't got this functionality builtin, it's clearly a design error.
/Otto
Edited by: Otto Frost on Dec 18, 2007 4:32 PM

Sign in has failed. Network failure.

Hi All,
We are half way through updating an iPad issue and after rebooting because the upload was hanging in the Folio Builder we cannot log in due to network failure. Cannot sign into https://digitalpublishing.acrobat.com either under any log in.
http://status.adobedps.com/ is saying everything is fine, is anyone else having the same problem? Was working, if not a little slow, this morning but now we cannot access anything. Our internet connection seems fine and can access everything else.
Any help would be appreciated.
Thanks.

You're not alone, check http://forums.adobe.com/message/5988644#5988644

Upload failed "network failure"

Why is it that I get upload failed "network failure" msg on folio builder, immedieatly hit retry and it goes thru, or after several trys it goes thru? Or sometimes it goes on the first try, and then I make a small change and the upload will not work again? My upload speed is 20 Mbps.

I am getting the same error message - I just updated the Folio producer tools that were released on OCT 10 for 5.5

Oracle 10g CRS autorecovery from network failures - Solaris with IPMP

Hi all,
Just wondering if anyone has experience with a setup similar to mine. Let me first apologise for the lengthy introduction that follows >.<
A quick run-down of my implementation: Sun SPARC Solaris 10, Oracle CRS, ASM and RAC database patched to version 10.2.0.4 respectively, no third-party cluster software used for a 2-node cluster. Additionally, the SAN storage is attached directly with fiber cable to both servers, and the CRS files (OCR, voting disks) are always visible to the servers, there is no switch/hub between the server and the storage. There is IPMP configured for both the public and interconnect network devices. When performing the usual failover tests for IPMP, both the OS logs and the CRS logs show a failure detected, and a failover to the surviving network interface (on both the public and the private network devices).
For the private interconnect, when both of the network devices are disabled (by manually disconnecting the network cables), this results in the 2nd node rebooting, and the CRS process starting, but unable to synchronize with the 1st node (which is running fine the whole time). Further, when I look at the CRS logs, it is able to correctly identify all the OCR files and voting disks. When the network connectivity is restored, both the OS and CRS logs reflect this connection has been repaired. However, the CRS logs at this point still state that node 1 (which is running fine) is down, and the 2nd node attempts to join the cluster as the master node. When I manually run the 'crsctl stop crs' and 'crsctl start crs' commands, this results in a message stating that the node is going to be rebooted to ensure cluster integrity, and the 2nd node reboots, starts the CRS daemons again at startup, and joins the cluster normally.
For the public network, when the 2nd node is manually disconnected, the VIP is seen to not failover, and any attempts to connect to this node via the VIP result in a timeout. When connectivity is restored, as expected the OS and CRS logs acknowledge the recovery, and the VIP for node 2 automatically fails over, but the listener goes down as well. Using the 'srvctl start listener' command brings it up again, and everything is fine. During this whole process, the database instance runs fine on both nodes.
From the case studies above, I can see that the network failures are detected by the Oracle Clusterware, and a simple command run once this failure is repaired restores full functionality to the RAC database. However, is there anyway to automate this recovery, for the 2 cases stated above, so that there is no need for manual intervention by the DBAs? I was able to test case 2 (public network) with the Oracle document 805969.1 (VIP does not relocate back to the original node after public network problem is resolved), is there a similar workaround for the interconnect?
Any and all pointers would be appreciated, and again, sorry for the lengthy post.
Edited by: NS Selvam on 16-Dec-2009 20:36
changed some minor typos

hi
i ve given the shell script.i just need to run that i usually get the op like
[root@rac-1 Desktop]# sh iscsi-corntab.sh
Logging in to [iface: default, target: iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz, portal: 192.168.181.10,3260]
Login to [iface: default, target: iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz, portal: 192.168.181.10,3260]: successfulthe script contains :
iscsiadm -m node -T iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz -p 192.168.181.10 -l
iscsiadm -m node -T iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz -p 192.168.181.10 --op update -n node.startup -v automatic
(cd /dev/disk/by-path; ls -l *sayantan-chakraborty* | awk '{FS=" "; print $9 " " $10 " " $11}')
[root@rac-1 Desktop]# (cd /dev/disk/by-path; ls -l *sayantan-chakraborty* | awk '{FS=" "; print $9 " " $10 " " $11}')
ip-192.168.181.10:3260-iscsi-iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz-lun-1 -> ../../sdc
[root@rac-1 Desktop]# can you post the oput of ls /dev/iscsi ??you may get like this:
[root@rac-1 Desktop]# ls /dev/iscsi
xyz
[root@rac-1 Desktop]#

APP-V 5 SP1 - "Application Failed to Launch. This may be due to a network failure 0x0FD01B25-0000007B"

Hello all,I am having some issues with APP-V 5.
I am having particular issues with starting a packaged SIMS.net. I keep recieving:
"Application Failed to Launch. This may be due to a network failure 0x0FD01B25-0000007B"
...within a second or two of clicking on the app-v created shortcut for this software.
To clarify, I had this software working perfectly previously. I recreated this package due to a software update, but it fails to launch now. I started a new package from scratch as this is a complex piece of software with multiple installers to run etc.
To be honest, I keep seeing this error on other applications. At one point, nearly every published app returned the same error. I spent a day trying to diagnose but the following day, everything mysteriously started working again.
I have had a look on kirks blog & Tim Magan, but to no avail.
Any help would be greatly appreciated, as this is a 'business critical application' (as they say).
Quick overview of my setup:
- Single Server configuration (Management, Publishing & SQL) on Server 2012 VM in 2012 Hyper-V
- Win 2000 Domain with 2003 DC
- Windows 7 Enterprise SP1
- SIMS.net Summer 2013 sequenced on 32bit following best practice guide
- Deploying to 32 bit machine
- Client settings pushed by GPO. Powershell execution policy set to allsigned.

RESOLVED: This error is caused by the "Program Files" missing from the "C:\ProgramData\Microsoft\Windows\Start Menu\" folder.
Firstly, a big thank you Nicke. You may not have solved the problem, but you sent me down the road to resolve this issue.
After trying the step you mentioned, I placed the computer in an OU with inheritance disabled. From this point onwards, I deduced that it was actually a group policy issue.
In my environment, I redirect start menus to generated start menu. This is created using a powershell script to combine locally installed items and network items. This scripts deletes the content of the 'programdata' start menu (i.e all users start menu)
to prevent these items disrupting the start menu.
Now... The app-v packages were breaking because, the 'Start Menu > Programs' folder did not exist. If an empty 'Start Menu > Programs' exists, the packages work correctly.
I can only assume that the two packages that were working correctly - that I installed these for 'current user only', rather than 'all users'.
It seems a little silly to me that app-v should fall over for something so simple. However, you could argue that it serves me right for playing about with system files :)
Thanks again for the help.
Mark

Server side does not detect network failure

Hi folks,
I coded a simple chat program. When a client connects to the multi-thread server, server shows newly connected client's IP address. Now, if the connection between client and server is down, client detects and terminates itself but server does not. The server still shows that client as connected. when I traced the server side, I found out that server was waiting at the readObject (client object input stream) line but it didn't throw any IOException. I tried to send some message to all connected client at every 20 seconds, so I expected to catch IOException when the server did not reach the client. Unfortunately, it didn't work. That is my question how can server side detect network failure?
Thanks for help.
Regards
Bulent

That is how TCP works (noting that it has nothing to do with java.)
Your solution is one of the following or some combination...
- If the server does not receive something every X time period then it disconnects.
- If the server has not received something after X time period it sends a keep alive message to the client. If the client does not respond (or the message fails) then the server disconnects.

Reset TC with Original Settings after Power Failure

TC blinks yellow after power failure. How can I reset to original (before power failure) network settings?

Here you go: How to reset Time Capsule

How to configure V240 auto-boot after power failure?

Hi!
How to configure automatic boot of V240 machine after power failure? After power gets resored, V240 remains in standby mode and one has to press button on front to power it up. It is not convinient because power failure can occur, for example, at night and the machine is not booted until the first user awakens :)

Uhh... I've found publicly accessible document http://docs.sun.com/source/817-5481-11/variables.html :
Looks like this variable controls auto-power-up behaviour:
sc_powerstatememory
The sc_powerstatememory variable enables you to specify the state of the host server as false (keep the host server off) or true (return the server to the state it was in when the power was removed). This is useful in the event of a power failure, or if you physically move the server to a different location.
For example, if the host server is running when power is lost and the sc_powerstatememory variable is set to false, the host server remains off when power is restored. If the sc_powerstatememory variable is set to true, the host server restarts when the power is restored.
The values for this variable are as follows.
true - "Remembers" the state of the host server when power was removed and returns the server to that state when power is reapplied.
false - Keeps the server off when power is applied.

Attempting to download trial - Akamai DM reports "network failure"

Hello,
If there is a more pertinent place for this issue, could a moderator/Adobe employee please move it? Thanks.
Basically, the issue is this. I am attempting to download the Acrobat Pro Extended trial, but the download of the Akamai DM fails with "network failure" error. I have been attempting to download said trial for the past month, each time failing with an identical error. I have checked my firewall (McAfee) nothing seems to be amiss there (I've even attempted to download it with the firewall switched off - made no difference).
This is a standalone machine, no network, no proxy.
I find this REALLY infuriating - why can't Adobe use a normal delivery system like every other software company offering trials? Even downloading from Macro$haft isn't this frustrating!
Sorry for the rant but, after a month of failed attempts to clear the first hurdle, I'm sure you can allow me a small one! Speaking of M$, I must register my frustration that I cannot use my browser of choice (Opera) to even attempt the ADM download - it doesn't appear to support Firefox, or Chrome either. Yep, the only browser that will attempt to connect to Adobe's servers is IE - a browser which, if I had any say in the matter, would be obliterated from the face of the Earth!
Please be gentle with me, I'm NOT a Winblows person (this is my parents' system, running eXtra Problems Home, Supplementary Problems 3). I prefer more sensible, logical OSs, such as those developed by Apple. I'm only back on Winblows because I'm selling my Mac Pro to finance the purchase of a MacBook Pro, as that is more relevant to my current needs.
Thank you very much for any assistance you can give me (and I hope this thread isn't removed!)
Sarah

I'm sorry you are having problems. May I suggest you try to download the trial on your Mac and move the file on to the Windows machine after a successful download. I'm not a fan of downloading utilities, I think with today's faster net its need is minimal, but I do not have the data Adobe does. They must think it is helpful. I'd like them to offer an alternative for people with issues, perhaps loading their ftp site with the trial software for people. However, for the most part we are just users here.
Perhaps this would be a better venue to register your complaint about the downloaders: http://www.adobe.com/bin/webfeedback.cgi
Another alternative is the adobe.com forum.

Cant send or receive pics/network failure messages

Just started today that I cannot send or receive picture messages. I have also been getting a lot of network failure notices when trying to send texts. Also, I have been getting a lot of messages from other people about 4 hours after they sent them, even when I have full service! I did just activate a $20.00 unlimited messaging card yesterday, but that isn't supposed to take effect till Nov. 1st. And that still doesn't explain why I've been getting the Network Failure notices and the delayed messages. Can anyone enlighten me on why this is happening?

http://support.apple.com/kb/ts2755

Portal failed to access remote resource due to network failures

Hi,
We have a portlet that allows users to upload files to a SQL Server database and make it available for other users to access. The portlet code is on our remote servers. Everything works fine in dev environment, but certain files fail in pre-prod and prod within the portal, but work fine when the code is executed outside the portal.
I keep getting this error:
Error - Portal failed to access remote resource due to network failures. Try again later or contact your portal administrator.
What could the problem be?
Thank you for your help.
Rad

If the Studio service looks good on the remote server where Studio is installed (check that
the service is started and look in the Studio logs for any warnings or errors), you should
also verify the configuration settings in the Studio remote server object. Is it properly
configured and pointing to the correct remote server?
If so, check the portal servers access to the Studio server via the port specified in the remote
server (default is 11935). You can test this by doing a telnet test on the portal server. In a cmd
prompt (Windows) or on the CLI (Unix), type 'telnet [studioserver] 11935', where "<servername> is
the name of your Studio remote server. The screen should just go blank, meaning that there is
something accepting connections on that port on the given server. (We would hope it's the Studio
app and not another service occupying that port.) If you get "Could not open connection to the host"
or some such similar result, check that the network between the portal and the Studio remote server
is open (ie, make sure there isn't any port blocking or a firewall in place that would hinder the
communication between the two servers).

Behaviour after network failure

Similar Messages

Maybe you are looking for