Exchange sp1 ECP hang when one mailbox server is down

i have native exchange sp1
i have 1 cas server and 2 mailbox server
if join on ECP i see total function and see mailbox server 1 and 2
but if shutdown server mbox 1 or server mbox 2= the ecp not responding
i close IE and reboot cas server but when open ECP the autentication working but menu is very slow..
and often block when select : exchange admin center/server/serverdatabase
i see eventlog and cas server tries to connect
to the server off and loop.
I thoughtthat thecasno longer sawthe emailson the serveroff
not that
the whole system went wild
if restart server mbox which before
was off the ecp immediatelyworking perfect
this happens
is if I turn off the server mbox
1 or 2
thanks for help

Hi,
Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases, such as a disk,
server, or network failure.
We can undestand more information from this document.
https://technet.microsoft.com/en-us/library/dd979799(v=exchg.150).aspx
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Similar Messages

Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

Hi,
I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
Is there a way to change this?

SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

IE 5.0 hanging when one is reading HTML from Weblogic 6.0

I have following configuration:
Local network (TCP/IP, Wins server)
SERVER: NT 2000 AdvServer & Weblogic Eval 6.0 Sp2 & Oracle 8.1.7
CLIENTS
1) Win 2000Pro & IE 5.0
2) Win 98 & IE 5.0
Quite often IE (client one) is hanging when one is reading static HTML pages.
Also IE (client two) says that there is fail in Kernel and display dump of memory.
In last case it is occured less often.
I located these static HTML pages in Webdefault catalog.
Also I have two simple JSP pages, one of them is genering current time and is
working constantly.
This situation was not changed when I did the following:
1. Disable Java Plugin
2. Set Weblogic Sp1.
What did I wrong?
Thanks in advance
Eugenia
[email protected]

I play the mp3 files as sprites in the score that are
streaming from the web server. If you selecr "Insert->Media
Element->Shockwave Audio" from the menu in Director you can
choose to import a mp3/swa file. This file will import as a cast
member which will have an external link address. (e.g.
http://www.adobe.com/mysound/myfile.mp3)
I have then dragged this cast member onto channel 1 in the score
spanning for instance 10 frames.
It does not make a difference wether the soundfile is of type
mp3 or swa, I have tried both.

Not able to connect to UCCX IVR when my Pub server is down

Hi,
I Pub and Sub in my call Manager Group(CUCM 7.1) with my UCCX 7.0 , H.323 gateway is used for incoming and outgoing calls.
When my Pub is down the calls to the IVR keeps ringing and Agents are also not able to answer the calls, the calls land to the available agent . no prompt is played for the queue when agents are not available and call keeps ringing.
We have two incoming dial-peer configured on my H.323 gateway with preference command .
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
dial-peer voice 9 voip
preference 1
destination-pattern 9000
session target ipv4:192.168.6.31
voice-class codec 1
dtmf-relay h245-alphanumeric
dial-peer voice 11 voip
preference 2
destination-pattern 9000
session target ipv4:192.168.6.32
voice-class codec 1
dtmf-relay h245-alphanumeric
If i remove the dial-peer 9 when my Publisher server is down everthing starts working fine.
Could anyone help to find if the problem is with the gate or my UCCX server.
Regards,
Veer

Hi Veer
What you need to focus on here is your dial peer.
From your description it sounds more like the IOS gateway is sending calls to 192.168.6.31.
Try testing again and this time wait it out, i suspect your call will drop after 20 seconds of ringing.
You need to make the changes on the IOS gateway as the issue is not with the ccm/uccx.
voice class h323 1
h225 timeout tcp establish 3
dial-peer voice 9 voip
voice-class h323 1
dial-peer voice 11 voip
voice-class h323 1
This should do the trick.
Regards
Hoai Huynh

How can a JMS Listener Notified get when a Topic Server Goes Down?

I'm in the process of looking into pub/sub model for a centeralized data source where vertical applications subscribe to a topic to get updates on person demographic information.
          I was playing with the JMS topic examples and noticed that when I have a Durable Subscriber listener (java main) and the topic Server goes down. It never gets notified. When I restart the Topic server and send msgs to the topic, the Durable Listener doesn't get them.
          Once I restart the Durable Listener (java main), it receives all the messages that were pending.
          I implemented the ExceptionListener and it never gets a shutdown msg either. I shutdown the Topic server via Ctrl-C, Graceful Shutdown and Forced Shutdown.
          Is there a way for the client listener to determine when the Topic Server went down, came backup, and restore the connection to it automatically? Or do we have to implement some type of ping mechanism on the client listener and re-create the connection ourselves?
          Thanks. Later...
          - Wayne
          Edited by wlau1000 at 03/07/2007 8:34 AM

Hi Wayne,
          I think the exception listener should have fired. Some comments/questions:
          - Does your app call "connection.setExceptionListener" in addition to implementing ExceptionListener?
          - Which version and maintenance/service pack are you using?
          - Is the client using the wl* "thin" client jars or the "thick" client jar?
          - Version 9.2 provides an automatic reconnection capability for consumers. This behavior isn't enabled by default due to natural side effects that some apps might not be prepared to handle (needles to say, I recommend reading the doc thoroughly).
          http://edocs.bea.com/wls/docs92/jms/recover.html#wp1320125
          Tom

Deployment of Web Application when the managed Server is down .....

Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

This is currently being fixed in 7.0 line, contact [email protected] and reference
CR110687
Cheers
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log:     Mailbox logon verification
        EMSMDB.Connect()
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - ErrorDetails =
        - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
        - ActivityContext =
    EMSMDB.Connect() completed successfully.
        EMSMDB.DoRpc(Logon)
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
        - ErrorDetails =
        - Latency = 00:00:00.0018801
        - ActivityContext =
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
    - TaskStarted = 11/12/2013 5:15:25 AM
    - TaskFinished = 11/12/2013 5:15:25 AM
    - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State               Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OutlookMapiHttpDeepTestMonitor
Outlook.Protocol              Unhealthy      None
NotApplicable       OutlookRpcDeepTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookRpcSelfTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol
Healthy        None
NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name:      Application
Source:        MSExchangeRepl
Date:          12.11.2013 4:49:46
Event ID:      3169
Task Category: Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">3169</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
    <EventRecordID>1606248</EventRecordID>
    <Channel>Application</Channel>
    <Computer>test-mbx-2.contoso.local</Computer>
    <Security />
</System>
<EventData>
    <Data>DB-01</Data>
    <Data>test-mbx.contoso.local</Data>
    <Data>test-mbx-1.contoso.local</Data>
    <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Session Bean Client Hangs when one Server in Cluster Fails

We are testing several failure scenarios and one has come up that concerns us.
Some background: Were running a WLS6.1 cluster on two separate machines. We
start a test client consisting of 50 active threads and let them start calling
into a session bean. After a couple minutes we pull the network plug out of one
of the machines to simulate an uncontrolled crash of the machine. Once the plug
is pulled the clients hang and of more concern any new clients that we startup
also hang. Has anyone successfully solved this problem?

When we kill one of Weblogic instances in the cluster none of the clients fail.
All of our clients fail-over to the remaining servers. It's pulling the network
plug to our of the server that causes everything to hang. Not just or test client,
but the other servers in the cluster hang. The control panel doesn't respond
at all either. We currently have a support case open with BEA #348184 about this.
We've gotten a prompt response in which we were asked to modify our configuration
by deploying our beans to each individual server rather than the cluster. We
did this, but the results so far have not changed.
Thanks for the feedback,
Howard.
"Ade Barkah" <[email protected]> wrote:
We haven't encountered something like that, so it could be a setup problem.
Can you verify that the t3 url hostname the client threads use resolves
to the
ip addresses of each machine in the cluster? Are all machines in the
cluster
listening at the same port number? Also, does it matter if you kill one
of the
weblogic processes instead of pulling the plug? (i.e., if you leave the
network
layer up?)
Check also that your threads aren't simply blocking each other when the
server
goes down? E.g. start multiple test client processes with one thread
each just
to test.
What we notice is (with round-robin cluster policy), as we bring down
one of
the servers, the clients will continue to work on the second server,
but will slow
down between method invocations as they still attempt to connect to the
downed
server.
After a short period of time (~30 seconds) the clients will fully switch
to the
second machine and processing continues at full speed again, until the
downed
machine is brought back up, at which point work is distributed evenly
again.
Also, when the first server is brought down, some of the clients may
terminate
with a PeerGoneException (or something similar to that.) So unless your
threads
are catching exceptions, they might terminate as well.
regards,
-Ade
"howard spector" <[email protected]> wrote in message news:[email protected]...
We are testing several failure scenarios and one has come up that concernsus.
Some background: Were running a WLS6.1 cluster on two separate machines.We
start a test client consisting of 50 active threads and let them startcalling
into a session bean. After a couple minutes we pull the network plugout of one
of the machines to simulate an uncontrolled crash of the machine. Once the plug
is pulled the clients hang and of more concern any new clients thatwe startup
also hang. Has anyone successfully solved this problem?

Install hanging when registering automation server

I'm tearing my hair out, as well as getting my 4rse kicked by the other half!
We've had iTunes up and running on our Vista Home Premium box for a while, then it just stopped working coming up with an error.
So I've tried re-installing, but 7.3 keeps hanging when trying to register the automation server. Worst still I have to kill it with Task Manager and it leaves a partial install that refuses to uninstall!
Any guidance would be much appreciated.
Thanks,
Stuart

Registering Automation Server hangs are actually a 7.x.x.x thing rather than a 7.3.0.54 thing. I've seen them with 7.2.0.x too.
Perhaps try this strategy.
First download and then install the QuickTime standalone installer:
Latest Quicktime Installers … get the one that doesn’t mention iTunes
If that install goes through properly, then try another iTunes install.
(The theory here is that if your QuickTime is already up to date, the iTunes installer bundle skips the QuickTime part of the install. If the iTunes installer is given less to do, sometimes it gets past the Registering Automation Server hang.)

OSB dashboard Service Health tab broken when a managed server is down

I have shut down one of the managed servers in my three-member OSB 10.3.1 cluster to load test the reduced configuration, and that has broken the "service health" tab on the OSB console dashboard.
The problem is that with the mgd1 server shut down (the one the Singleton marker ear is deployed to, if that matters), in the OSB console's Dashboard everything in the "Service Health" tab is broken. I get the warning message "Unable to obtain metrics data from the server" at the top of the page whenever I go to the dashboard. I can't even look at the displays for the individual (mgd2, mgd3) servers that are running. I get the following error in the log when trying to access the service health for the services in the cluster, or even if I try to get the health of services in either of the two remaining cluster members individually:
+####<Apr 8, 2010 11:00:02 PM EDT> <Error> <AlertLog> <nj09mhm0033.edmz.mcgraw-hill.com> <SS_ESB_Admin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1270782002573> <BEA-000000> <WLDFAccessRuntimeMBean is not available for server SS_ESB_mgd1>+
Also, as part of the load test procedure, I need to collect performance stats from the proxy service pipeline and the business service. To do this, I've written JMX code called out of soapUI scripts to reset the stats on these services before the run, then collect the stats after the run ends; the code connects to the admin server. This too is broken when the mgd1 server is shut down.
I get the error below when trying to collect the cluster stats from the Admin server from the JMX code. This error is fatal, and no statistics come back from the rest of the cluster either. (you can ignore all the groovy stuff in the stack trace, it's the nested Exceptions that are more interesting).
Does anyone have an idea about what's going on, and how I fix this? I would have thought the DomainService Runtime MBean would be able to catch and handle an Exception like this if one of the managed servers were down, and collect the stats from the available part of the cluster, but it looks like that's not the case.
TIA for any help.
/Steve Elkind
java.lang.reflect.UndeclaredThrowableException
at $Proxy6.getBusinessServiceStatistics(Unknown Source)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getAndResetStatsForMonitoredBizService(ServiceStatsRetriever.java:193)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStatsForMonitoredBizService(ServiceStatsRetriever.java:142)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.run(ServiceStatsRetriever.java:652)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.getStats(ServiceStatsRetriever.java:619)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStats(ServiceStatsRetriever.java:779)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$getStats.call(Unknown Source)
at Script1.sleepGetStats(Script1.groovy:75)
at Script1$sleepGetStats.callCurrent(Unknown Source)
at Script1.runBenchMarkTest(Script1.groovy:104)
at Script1$runBenchMarkTest.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:143)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:163)
at Script1.run(Script1.groovy:152)
at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:93)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.runSetupScript(WsdlLoadTest.java:915)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner.start(WsdlLoadTestRunner.java:102)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.run(WsdlLoadTest.java:418)
at com.eviware.soapui.impl.wsdl.panels.loadtest.WsdlLoadTestDesktopPanel$RunLoadTestAction.actionPerformed(WsdlLoadTestDesktopPanel.java:424)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
at java.awt.Component.processMouseEvent(Component.java:6263)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6028)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$ServiceDomainMBeanInvocationHandler.invoke(ServiceStatsRetriever.java:567)
... 46 more
Caused by: com.bea.wli.monitoring.MonitoringException: [Monitoring Runtime:473057]Failed to get statistics for services due to java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:967)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getServiceStatistics(ServiceDomainMBeanImpl.java:802)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getBusinessServiceStatistics(ServiceDomainMBeanImpl.java:366)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:307)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:175)
at com.bea.wli.sb.util.server.AggregatorUtils.getAggregatorServerAdminURL(AggregatorUtils.java:105)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsRetrieverMBean(ServiceDomainMBeanImpl.java:2036)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:933)
... 35 more
java.lang.reflect.UndeclaredThrowableException
at $Proxy6.getBusinessServiceStatistics(Unknown Source)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getAndResetStatsForMonitoredBizService(ServiceStatsRetriever.java:193)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStatsForMonitoredBizService(ServiceStatsRetriever.java:142)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.run(ServiceStatsRetriever.java:652)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.getStats(ServiceStatsRetriever.java:619)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStats(ServiceStatsRetriever.java:779)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$getStats.call(Unknown Source)
at Script1.sleepGetStats(Script1.groovy:75)
at Script1$sleepGetStats.callCurrent(Unknown Source)
at Script1.runBenchMarkTest(Script1.groovy:104)
at Script1$runBenchMarkTest.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:143)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:163)
at Script1.run(Script1.groovy:152)
at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:93)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.runSetupScript(WsdlLoadTest.java:915)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner.start(WsdlLoadTestRunner.java:102)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.run(WsdlLoadTest.java:418)
at com.eviware.soapui.impl.wsdl.panels.loadtest.WsdlLoadTestDesktopPanel$RunLoadTestAction.actionPerformed(WsdlLoadTestDesktopPanel.java:424)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
at java.awt.Component.processMouseEvent(Component.java:6263)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6028)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$ServiceDomainMBeanInvocationHandler.invoke(ServiceStatsRetriever.java:567)
... 46 more
Caused by: com.bea.wli.monitoring.MonitoringException: [Monitoring Runtime:473057]Failed to get statistics for services due to java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:967)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getServiceStatistics(ServiceDomainMBeanImpl.java:802)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getBusinessServiceStatistics(ServiceDomainMBeanImpl.java:366)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:307)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:175)
at com.bea.wli.sb.util.server.AggregatorUtils.getAggregatorServerAdminURL(AggregatorUtils.java:105)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsRetrieverMBean(ServiceDomainMBeanImpl.java:2036)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:933)
... 35 more

As a follow-up, does anyone know if I can simply retarget the two OSB Singleton Marker Apps (shown below from config.xml) to another server instance to fix this and any other Singleton issues (e.g., flie transport, ftp, and email pollers), or is it more involved than that?
<app-deployment>
<name>ALSB Cluster Singleton Marker Application</name>
<target>SS_ESB_mgd1</target>
<module-type>ear</module-type>
<source-path>/opt/bea/osb1031/osb_10.3/lib/common/clustersingletonmarker.ear</source-path>
<deployment-order>80</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>ALSB Domain Singleton Marker Application</name>
<target>SS_ESB_mgd1</target>
<module-type>ear</module-type>
<source-path>/opt/bea/osb1031/osb_10.3/lib/common/domainsingletonmarker.ear</source-path>
<deployment-order>85</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>

Archive REDO When One RAC Node is Down

I have a question about how redo log get archived when one of the instances in a two node RAC cluster is down (not open, not mounted).
For example, let's assume instance1 was shutdown and only instance 2 is running.
I have 6 redo logs:
<font face="courier">
SQL> SELECT GROUP#, THREAD#, SEQUENCE#, STATUS FROM V$LOG;
GROUP# THREAD# SEQUENCE# STATUS
1 1 3390 INACTIVE
2 1 3389 INACTIVE
3 1 3391 ACTIVE
5 2 3886 INACTIVE
4 2 3887 INACTIVE
6 2 3888 CURRENT
</font>
If I run the following statement what will happen?
<font face="courier">
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
</font>
The documentation says +Specify CURRENT to manually archive the current redo log file group of the specified thread, forcing a log switch. If you omit the THREAD parameter, then Oracle Database archives all redo log file groups from all enabled threads, including logs previous to current logs. You can specify CURRENT only when the database is open.+
Would Oracle archive sequence# 3391 from thread 1 even though the instance is not open?

When your instance are not working, it means that it doesn't have any CURRENT redo log. So when you issue switching logfile - it launches archiving only current redo log, for working instance only. That 3391 redo log is not current, it has Active status, that means that it could be needed for recovery purpose, but it had to be archived earlier.

Logs to check if one webi server is down

Hi,
We have set up 3 webi report servers in our environment. We wanted to know if one of the servers goes down, while the other two are still running, which logs do I need to check that says the server is down. Is that the webi logs or tomcat logs?
thanks,
rao.

Hi James,
Thanks for your response. We are not using BO monitoring tool but instead we are using foglight. I'm not sure how it works but I guess it needs to check logs, so I was wondering which log files tell us if one of the services goes down. I appreciate your help.
thanks,
rao.

Proper way to install windows update on Exchange 2010 DAG with one mailbox server in Head Office and 1 mailbox server in DR site both are members of 1 DAG

Hi Guyz,
I have this setup in my exchange environment.
1 DAG with 2 members
- One member is located in Head Office and the other member is located in DR site. All of the mailbox databases are located only in HO (Plan to add additional second member in HO soon). Now what is the proper way to install windows patches on the
member in HO? I don't want to move the databases to DR site as much as possible.
Appreciate your feedback and Many thanks in advance guyz..
More power to all!
Regards,

Hi,
To update the DAG members with new patches, the update process should be managed to prevent all of the DAG members from being offline at the same time.
To do this, I recommend you move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
For detailed steps, here is an article for your reference.
How to Install Updates on Exchange Server 2010 Database Availability Groups
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Long hangs when connecting to server

This has been a long-standing annoyance...
We have an Xserve with 10.5 in the office.
When I click on the "Network" icon in the sidebar on my Mac, it almost
instantly displays a list of all machines on the nework.
I then double click the Xserve's icon and the wait begins: first the
beach ball followed after a while by a message window "Looking up
server.local...".
That continues for more than a whole minute until I'm prompted for my
password (it's stored in the keychain) and finally a window pops up
listing all the available shared folders/volumes on the server.
Double-clicking any of them mounts it immediately on my Mac.
Now I keep aliases for the volumes I need to mount regularly. One of
them connects with only a short delay of around 15 secs and no password
prompts.
However a new alias I created today takes *several minutes* to mount the
respective volume and that just doesn't seem right.
What could possible cause these varied delays?
Why does it do the "looking up" thing if the server can be seen in the
network pane?
Martin

That's consistent with a DNS error and DNS timeouts (or maybe network or routing errors), and the use of the .local mDNS Bonjour domain implies no DNS is configured, and Mac OS X Server expects to have DNS. Put another way, set up DNS services, and get out of the .local domain. [Here's an explanation of configuring DNS services|http://labs.hoffmanlabs.com/node/1436]

Cx_oracle ping (OCIPing) hangs when connection to server lost

The cx_oracle ping function appears to be blocking and will wait forever when the connection to the database is broken but the socket still remains.
we're running cx_oracle 4.4 on an Oracle 11.1 server with python 2.5, and have a remote client pushing data to the server across a flakey link.
The basic structure of our python client is
db = cx_Oracle.connect()
while True:
try:
db.ping()
cursor = cx_Oracle.Cursor(db)
cursor.execute(query, params)
except:
print "DB error"
so the socket pointer will be there which is checked in the ping command, so it will pass that, but then it will attempt to issue a ping to the server which is where it hangs forever.
Any advice on the best way to get around this?

I would suggest to take this kind of question to the cx_Oracle developer himself here for an exact answer.

Exchange sp1 ECP hang when one mailbox server is down

Similar Messages

Maybe you are looking for