One interface of pair goes down

Hi
If two interfaces are paired into one group and one interface of pair goes down, will the second interface will be declared as down by IPS?

Hi,
I I have a problem connected to this issue.
I have only one IPS4270-20 with software 7.0(7)E4 and I use 2 IF pairs on it. Both IF pairs are for the same operation, and they were implemented for HA purposes. We have two 6500 chassis in VSS and all of the IPS ports connected to these switches. Gi3/0-Gi3/1 and Gi1/2-Gi3/3 are in pair, and Gi3/0-Gi3/2 are the inbound and Gi3/1-Gi3/3 are the outbound interfaces, so it achieves the hardwer failover requirements. Inbound IFs creat an Etherchannel, and outbound IFs creat an other Etherchannel, so we try to prevent an L2 loop when VSS breaks.
The issue what I can't solve is the following:
If I shut down the 6500 IF what is connected to the IPS Gi3/0 I would like Gi3/1 to goes down, but it isn't the case.
I tried to use LACP in the Etherchannel, so when Gi3/0 goes down, the 6500 port which connected to the IPS Gi3/1 should be removed from the Etherchannel, but it isn't the case also.
Do you have an idea, what could be the problem, or I should redesign the topology?
Thanks,
Miki

Similar Messages

VIC2-2BRI NT/TE - link going down

Hi,
I have VIC2-2BRI NT/TE on router 2801.
If there are no calls for some time, the interfaces are going down, and none outbound call can't be placed.
Only when inbound call is placed, the link is going up, and everything is working 'till next time.
Does anybody know what could be the reason?
Thanks

I remember i've got a similar problem sometimes ago on the same router and on my 3825 router too.
But the difference is that the VIC2-2BRI NT/TE remains up until i place calls. The first call goes through one port of the interface, and after that, this port changes state to down. The second call uses the second port of the interface, and after goes down. then i can no more place calls. But i can receive calls from PSTN, and just before, the interfaces change state to UP. And i can place two other calls again and the same problem occur.
To issue this problem, i entered the command
" isdn transition-delay 1" at each BRI interface
And things now go well.
But i would like to get more information about this command, if you can help me

One of ESSBASE services is going down continuosly

HI,
One of my ESSBASE services is going down continuosly, even if i restart the service its going down when i refresh the services list.
Any help.
Thanks,
RRB.
Edited by: 813627 on 29-Jun-2011 07:36

HI These are the warnings in the log
<30-Jun-2011 08:32:33 o'clock BST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<30-Jun-2011 08:32:33 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<30-Jun-2011 08:32:33 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<30-Jun-2011 08:32:34 o'clock BST> <Warning> <Server> <BEA-002611> <Hostname "127.0.0.1", maps to multiple IP addresses: 10.148.128.29, 127.0.0.1>
<30-Jun-2011 08:32:34 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.148.128.29:13080 for protocols iiop, t3, ldap, http.>
<30-Jun-2011 08:32:34 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:13080 for protocols iiop, t3, ldap, http.>
<30-Jun-2011 08:32:34 o'clock BST> <Notice> <WebLogicServer> <BEA-000357> <Started WebLogic Independent Managed Server "aps" for domain "WebLogic9" running in Development Mode>
<30-Jun-2011 08:32:34 o'clock BST> <Warning> <Server> <BEA-002611> <Hostname "bsfhhdtpt5", maps to multiple IP addresses: 10.148.128.29, 127.0.0.1>
<30-Jun-2011 08:32:34 o'clock BST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<30-Jun-2011 08:32:34 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<30-Jun-2011 08:32:34 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Thanks,
RRB.

Interface goes down with mds9140

Hi
I've a problem with both MDS 9140. The fc interface goes down and don't go up when I reboot a device connected to them with a fiber. To solved the problem I need to remove the gbic and plug it back again. I use the following version of software
Software
BIOS: version 1.0.8
loader: version 1.1(2)
kickstart: version 1.2(1a)
system: version 1.2(1a)
Fabrice

It is probably a software defect where if a port is up for over 248 days, Once link is lost, it will not come back w/o a shut/no shut or manual intervention as you describe. This issue is resolved in the 1.3.4b and above code. For a 91xx, this would be a disruptive upgrade. Or, simply issue a shut/no shut on an affected port and you'll be good for another 248 days.

Server instance is going down very frequently

Hi,
Please help me solving one problem. The details are as follows:
Two web applications built on struts framework are running on one server. The server is SAPJ2EE 6.20 server which is running on SUSE LINUX.
I have SAPJ2EE 6.20 client interface using which I deploy these applications. Now once the applications are deployed, it runs perfect but after some time the instance of SAPJ2EE 6.20 application server goes down in linux and it remove these two application.
To make these two applications avaliable to the users I have to restart the instance of application server on linux and again deploy the applications. The behaviour of the same is very dynamic. Sometime it goes down 2 - 3 times in a day, sometime once in a day,
sometime once in 3 - 4 days and sometime once in a week.
On server I checked the logs but I didn't get any clue. The logs contains normal java exceptions like NULLPointerException, ExhaustResultSetException, IOException etc.
I guess the application is throwing some error because of which the server instance is going down and these errors are not showing in logs.( By error I don't mean exceptions, I mean errors like MemoryError etc.)
Am I thinking correct or is their any other issue? How to verify what is going wrong?
Please please please guide me on this as this is very important for me.
thanks and regards

Hi,
I would suggest to have look at the application server console. Do you see any OutOfMemory or any sort of Exception over there
Please paste it here
regards
Vivek Nidhi.

Wireless APs going down randomly

Hi All
We have a situation where wireless access points are just going down randomly on our network. The situation is as follows:
We have 2 Cisco 5508 WLCs (licensed for 250 APs each, with more licenses en-route), both running software version 7.2.103.0. Then we have a large-ish number (±300) of Cisco AIR-CAP3502I-E-K9 APs connecting to these two controllers. The APs are either connected to Cisco WS-C2960S switches, or in "older" areas of the network they are connected to WS-C2950 switches. We do not have PoE switches installed yet, so all APs are powered by power injectors (AIR-PWRINJ4=).
Anyhat, all the access points are in FlexConnect (previously HREAP) mode, and they all connect via trunk ports to the switches in order to get the VLAN per SSID working. Both controllers are in the same mobility group, and both are in the DNS as "cisco-capwap-controller" as they are load balancing. The APs are installed about 25m apart in most areas. There is one installation where two APs are about 10m apart, but this is due to the shape of the building in which they are installed. We have no autonomous APs deployed at all...
The problem is that some access points work for about a day, and then they just disassociate with whichever controller they were associated to, and then they just fall off the network completely. Both WLCs, the NCS, and the network monitoring system (WhatsUp Gold) show the affected APs as physically unreachable. Looking at the trunk port on the switch, it shows that the port is up and the line protocol is up, input rate is 0 bits/sec, and output rate is up to 70,000bits/sec. There are no input or output errors on the switch port. Here is the output from one such switch port:
FastEthernet0/19 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is dc7b.9439.da13 (bia dc7b.9439.da13)
Description: Link to NC_K22-AP1
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:50:20, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 71000 bits/sec, 91 packets/sec
     977358 packets input, 80661413 bytes, 0 no buffer
     Received 29925 broadcasts (16038 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 16038 multicast, 0 pause input
     0 input packets with dribble condition detected
     37567889 packets output, 3624164243 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out
Connecting a console cable to an affected AP is fruitless, as the AP appears to be unresponsive while it is "down". Rebooting the AP, then connecting a console cable works, but then you've lost your syslogs. Looking at the Ethernet interface on the AP, it appears as if the interface is picking up a lot of errors, especially CRC errors, which would indicate a physical cable problem.
I got our cabling contractor out to do a cable test again, and it passes every time. We have them test both the Systimax and the Molex cable installations of affected APs, and all is OK. They use a Fluke MicroScanner² cable tester which certifies the Cat 6 cable from patch lead to flylead. No problems there, and I trust that the cable is 100% as tested.
So I swap the power injector of an affected AP (let's call it AP A) with an AP that is not affected by this (let's call this one AP B), and AP A goes down again after a day, or sometimes only a couple of hours. AP B remains operational as usual. If I swap AP A out with a new AP (AP C), then AP C starts showing the same symptoms after about a day, and then it also just goes down. When "suspect" AP A is installed somewhere else, then it works and stays operational for, well, 58 days now. Changing the switch/switch port also makes no difference.
This happens to one of the APs that are part of the "10m apart deployment", but it also happens to another AP that is completely on its own in a building far away from any other wireless source, so I cannot think that this could be the problem. I happens to an AP that is less than 100m away from its closest WLC, and it happens to an AP that is more than 350km away from its closest controller. All the other APs deployed in our remote campus (350km fibre link) are 100% OK. It happens to APs connected to the older WS-C2950 switches as well as the brand new WS-C2960S switches.
I am at wits end with this one. Where could the problem be? I trust the "Big Green" company that does our cable installations, and I trust the equipment they use. I also trust both Systimax and Molex to be very good products. And I do trust Cisco, as this is the only network equipment we deploy.
Where to from here?
Regards
Connie

This issue has now been resolved. Details can be found here: http://www.cisco.com/en/US/partner/ts/fn/635/fn63537.html.
Here is the short version:
Problem Description:
Calibration between DRAM and processor on AIR-CAP350x and AIR-LAP126x results in Access Points (APs) failing to boot properly. One symptom includes a white LED and no console output.
Background:
The root cause is the DDR memory calibration process that was performed on the Access Points (APs) at the time of manufacture. The fix recalibrates the existing memory hardware, so it will operate more reliably.
Workaround/Solution:
The fix for this issue is now publicly available. Go to www.cisco.com to obtain Access Point (AP) IOS code version: 15.2(2)JA or later and/or WLC software version: 7.0.235.3 (or later 7.0 release), 7.2.111.3 (or later 7.2 release) or 7.3.101.0 (or later 7.3 release).
As of June 2012, new AP3500 and AP1260 products with version ID (VID) V02 are free of this issue.

WLAN goes down when WAN goes down

Hi
I have 4 AP with EAP enabled. The authentication servers are located globally and the authentication request goes to the server situated in another country. My problem is that when my WAN goes down my WLAN also goes down immediately. Does the AP communicte with the server even after authentication, Atleast after authentication it should keep my authenticated machines in the network
any help is appreciated
ashish gupta

if you use a Cisco ACS server, click on "Interface Configuration" and "Radius (Cisco Aironet)" Make sure that "Aironet-session-time" is checked.
Then, you can change the session timeout in user or group level.
Other ways to resolve the problem:
1. install redundant links to the site
2. configure a second radius server on all access point. The second radius server can be one of the APs locally. If you configure "radius-server deadtime ?", the AP will not communicate to the radius server for a period of time if the radius server does not respond for 3 times. Of course, you have to populate the centralize user database to a number of APs.

Planning server goes down when I try to delete a member in Planning Web

Hi,
Planning server goes down when I try to delete a member in Planning Web. I am using Hyperion Planning 4 with Tomcat 4.1.30 and Windows Server 2003.
I am not sure whats happening. This is the exception log I am looking at:
2009-07-24 18:19:22 ApplicationDispatcher[HyperionPlanning] Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
     at org.apache.catalina.valves.ErrorDispatcherValve.custom(ErrorDispatcherValve.java:420)
     at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve.java:327)
     at org.apache.catalina.valves.ErrorDispatcherValve.throwable(ErrorDispatcherValve.java:277)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:179)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
java.lang.OutOfMemoryError
2009-07-24 18:19:22 ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=500, location=/Error.jsp]
javax.servlet.ServletException
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
     at org.apache.catalina.valves.ErrorDispatcherValve.custom(ErrorDispatcherValve.java:420)
     at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve.java:327)
     at org.apache.catalina.valves.ErrorDispatcherValve.throwable(ErrorDispatcherValve.java:277)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:179)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
java.lang.OutOfMemoryError
Please do help me........ how to resolve this.
Thanks.

Hi,
You could try increasing the java heap size, though sometimes an issue can occur if you are trying to delete a member when a workflow process has started, do you have one running?
Cheers
John
http://john-goodwin.blogspot.com/

My wifi goes down at least once a day and I have to unplug the time capsule and reboot it and then it works fine. Any idea why this is happening/what I can do to fix it?

My wifi goes down at least once a day and I have to unplug the time capsule and reboot it and then it works fine. Any idea why this is happening/what I can do to fix it?

I was having this problem while still using Mavericks -- it started after a Mavericks update last spring. During the initial Yosemite beta runs over the summer, it seemed to be fixed, but after the official launch in October, I had all sorts of problems keeping connected. Its gotten a little better, but still happens to at least one of my devices every day. Weird that we still cannot figure out why the connection keeps dropping on some devices, but not others, and then the next day, one of the devices that didn't disconnect the previous day will disconnect, but the ones that did disconnect, stay connected. It's just sloppy, poorly written software for technology that isn't working the way it should. If you turn off Continuity and Handoff on all your devices, you will probably see that everything stays connected. With those turned off on all devices, TC stayed connected to everything for over a month. The day I turned Continuity back on, all the problems started again. It had something to do with the bluetooth version being used, the wifi routine, and Apple's AirPlay technology not quite getting along with each other.

WLSE doesn't seem to notice it when an Aironet device goes down

WLSE type: 1105, version 2.7
Aironet 1100 devices (267 pieces), IOS 12.2(13)JA4
After the upgrade from version 2.6 to 2.7 we have a problem with the WLSE. Device discoveries and inventories run without a problem, but whenever a device goes down the WLSE doesn't seem to notice.
With a sniffer we found the WLSE's polling the device, but there's no follow-up when there's no reply. As a result the device stays green.
All configurations are the same with the exeption of one location. Here we've configured the WDS and this is the only location on which the WLSE reacts in the correct way.
On several other locations there might be one or two devices on which the WLSE reacts correctly, but these are exeptions. We have compared configuration files, but can't find any differences between the devices.
Whenever the WLSE does discover a failing device (with no WDS configured) it generates a P1 severity fault (default was P2).
In case these devices have become reachable again the P1 severity fault is automatically acknowledged and remains this way. So far I haven't been able to clear these faults and therefor the device will keep it's alert status in the reportview.
I do hope somebody has some idea about what's going on.
After I encountered these problems after the upgrade I've started from scratch and used a clean installation of version 2.7. and a new discovery of our network.
I really don't know what went wrong. Anybody with any suggestions is very welcome to vent them.
Thanks for your help,
Corine

I'm having a similar issue. 500+ AP1200 units, IOS 15JA, newest WLSE version. Most of the time when a unit goes down, it will generate a SNMP unreachable fault message, and we are set to have the WLSE send an email in the event of a SNMP unreachable. That's great. Except once in awhile, it won't generate the fault. The device could be powered completely down for three or four days, and I'd never get a fault message. It's driving me nuts. All these AP's are configured the same using the exact same template, with only the IP info changed.

Domain Controller going down after IDM implemented

Hi,
We have implemented IDM 7.1 and are using the PSS (Password Self Service), Password Syncronization functionality for 2 AD and 6 ABAP systems. This PSS is implemented to support our company ESS which is on the internet so that users can reset their own password. Hence to support it we have a architecture having one AD on the DMZ and another internal.
Both the AD repositories have been configured pointing to a perticular DC (Domain Contorller) . All the DC's have Phook installed on them.
Since Go-live we have not had any issue with the DC on the DMZ but the internal DC keeps going down once in a while and it doesnt have a pattern. We tried switching to different DC's also which didnt work. Right now we are keeping a close watch on the DC and we carryout a restart whenever it happens.
Did anyone come across such kind of a issue, if so then please let me know.
Thanks.

Hi Ahmed,
Thank you for your quick response! Our secondary domain controller IP settings were set properly according to the recommendation, but the primary (the one having the issues) was not. I went ahead and changed the settings and did an ipconfig /registerdns
and restarted the netlogon service. Nothing changed after that. I ran a dcdiag and the only one that failed was this:
      Starting test: NCSecDesc
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=ForestDnsZones,DC=*hidden*,DC=*hidden*
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=DomainDnsZones,DC=*hidden*,DC=*hidden*
         ......................... *hidden PDC Name* failed test NCSecDesc
I'm going to restart the server tonight after those IP changes and let you know my outcome.
Thanks again!

What happens to client session when host goes down?

I have a windows 2012 R2 RDP environment. 1 Broker and 3 Session Host Servers.
My question is as follows:
User connects via broker to one of the Host servers. Host server goes down, while user is still connected. Session is written in Broker database. User wants to connect again, but broker sends him on to the server which is down and so he cannot connect.
Other situation is similar, User connects to host, administrator drains host, stopping new connections. User disconnects session, session is still in Broker, when user tries to reconnect is sent to drained server but cannot login, as he is considered new
connection.
What am I missing?
Aaron

Hi Aaron,
Thank you for posting in Windows Server Forum.
We need to configure RDSH in a load balance farm where it can be managed by RD Connection Broker. For that we need to use DNS RR where need to make entry for all RDSH server which will be handled by RDCB Server or we can use any load balancing method to load
balance the different RDSH server and thus that connection will allow the disconnected session for reconnection and can identify the connection.
The RD Connection Broker for RDS serves the following main purposes:
• Determining the best RD Session Host server to connect to - this is based on the amount of current sessions per RD Session Host Server as a form of load balancing.
• Reconnecting a user to an existing session, in case there is one - this is called reconnecting to disconnected sessions.
• Being a resource for RD Web Access to deliver information about what Remote Apps are available on RD Session Host Servers that are a member of the broker.
More information.
Remote Desktop Server farms explained (Part 1
& Part 2) (Link is for Server 2008 R2 but it’s only for reference).
Step by Step Windows 2012 R2 Remote Desktop Services – Part 3 (For Server 2012 R2)
Hope it helps!
Thanks.
Dharmesh Solanki

Sender Communication Channel going down

Hi Experts,
We are on XI 7.0 with patch level SP12. We are having one problem. when we are starting the Sender JDBC communicaton channel it is working fine for the first time. but the moment there is any change in the sender or Receiver RFC communication channel. may be due to wrong system ID etc. the Sender JDBC channel goes down. Actually it shows it is running but it does not poll / pick up any records.
pl. note that subsequent changes which we had done to either to Sender JDBC channel or Receiver RFC has been rectified & re-deployed.
This problem get solved if we create a New Sender JDBC Channel.(But i guess that should not be the soluation)
I have used the following Modules in Sender JDBC channel.
AF_Modules/RequestResponseBean
localejbs/CallSapAdapter
AF_Modules/ResponseOnewayBean
Pl. Help.....
Regards,
Umesh

Does it go down even if a message is processed succefully or just if there is some error with the configuration?

Cannot keep Server up and running. Shutdown requested by OVM. The system is going down for system halt NOW!

I have OVS 3.x.x and OVM 3.x.x running on the same physical server. I had some issues trying to configure storage via OVM and I issued a shutdown (I think) from the OVM Web Interface. Now I am unable to keep the server up and running. Everytime I turn on the server, after Oracle VM Manager starts, it shuts down the server automatically within a minute or two after startup.
I am able to login to the server via Putty and stop ovmm service manually. When Oracle VM Manager service is stopped, (SERVICE OVMM STOP) the server does not shutdown automatically. However as soon as I restart the OVMM service, it shuts down the server with message...
Shutdown requested by OVM. The system is going down for system halt NOW!
How do I find out what is causing OVM to issue the shutdown command and edit and fix via command line?

Since your server was continually rebooting, do you remember if you issued a shutdown or reboot from OVM web interface? Mine was just shutting down. Have you tried to use the Oracle Virtual Manage Web Interface to either reboot or shutdown the server after your upgrade to 3.2.4? FYI I do not have support. This is my sandbox.
user5728486 wrote:
After a week or so without a resolution from support, I noticed ....
Are you saying that even paying for Oracle Support, they did not resolve this issue?

SOA managed derver is going down frequently

Hi,
We are facing one specific issue in SOA 11g environment .
SOA managed server is hosted on WebLogic Server Version: 10.3.4.0.
Server is keep on going down even after restart, after each restart it iwll come up for 15-20 minutes max and then again soa managed serve will go down.
Also in nohup logs we observed below warning :
oracle.adf.share.ADFContext> <BEA-000000>
+<Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is
performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of
oracle.adf.share.ADFContext to FINEST>
Also some error messages like :
+<BEA-000000> <ServletContainerAdapter manager not initialized correctly.>+
+<BEA-000000> <Could not find saved view state for token lb617ahaj>+
Could some once please let us know what could be reason for this .
Please suggest if there is any solution for the same.
Regards,
Nupur

Hi,
We are facing one specific issue in SOA 11g environment .
SOA managed server is hosted on WebLogic Server Version: 10.3.4.0.
Server is keep on going down even after restart, after each restart it iwll come up for 15-20 minutes max and then again soa managed serve will go down.
Also in nohup logs we observed below warning :
oracle.adf.share.ADFContext> <BEA-000000>
+<Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is
performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of
oracle.adf.share.ADFContext to FINEST>
Also some error messages like :
+<BEA-000000> <ServletContainerAdapter manager not initialized correctly.>+
+<BEA-000000> <Could not find saved view state for token lb617ahaj>+
Could some once please let us know what could be reason for this .
Please suggest if there is any solution for the same.
Regards,
Nupur

One interface of pair goes down

Similar Messages

Maybe you are looking for