pa-larkin - 2012-11-21


I am getting the following exception in the server logs for Domain Health:-

<21-Nov-2012 11:23:03 o'clock GMT> <Warning> <DomainHealth> <BEA-000000> <domainhealth.backend.retriever.RetrieverBackgroundServic
e timed-out when retrieving data from one or more servers in the domain>
<21-Nov-2012 11:23:03 o'clock GMT> <Error> <DomainHealth> <BEA-000000> <domainhealth.backend.retriever.DataRetrievalException: Pro
blem logging destination resources for server adminsvr>
domainhealth.backend.retriever.DataRetrievalException: Problem logging destination resources for server adminsvr
        at domainhealth.backend.jmxpoll.StatisticCapturerJMXPoll.logDestinationsStats(
        at domainhealth.backend.retriever.StatisticCapturer.captureAndlogServerStats(
        at domainhealth.backend.retriever.RetrieverBackgroundService$1.doRun(
Caused by: domainhealth.core.jmx.WebLogicMBeanException: The client has been closed.
        at domainhealth.core.jmx.WebLogicMBeanConnection.getTextAttr(
        at domainhealth.backend.jmxpoll.StatisticCapturerJMXPoll.logDestinationsStats(
        … 6 more
Caused by: The client has been closed.
        at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(
        at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.gotIOException(
        at domainhealth.core.jmx.WebLogicMBeanConnection.getTextAttr(
        … 7 more
<21-Nov-2012 11:23:03 o'clock GMT> <Error> <DomainHealth> <BEA-000000> <Statistics Retriever Background Service - unable to retrie
ve statistics for specific server 'adminsvr' for this iteration>

Statistics Retriever Background Service - unable to retrieve statistics for specific server

This is only occuring on a windows development machine, with a single admin server and no managed servers running OSB. Any ideas as to what might be the cause? We had issues trying to set OSB server initially, but everything seems ok now apart from this error.

Just so as you know, this is running fine on our unix development server which have admin/managed instances, so it looks like it is just an issue with how we have configured the windows instance.