javax.management.MBeanException: WARNING: Element Type: MANAGED_SERVER Element Id: bi_server2 Operation Result: FAILED_CONTACTING_MANAGED_SERVERS Detail Message: Specified BI Managed Servers are shut down: bi_server2.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by Svaradar-Oracle, 1 year ago
WARNING: Element Type: MANAGED_SERVER Element Id: bi_server2 Operation Result: FAILED_CONTACTING_MANAGED_SERVERS Detail Message: Specified BI Managed Servers are shut down: bi_server2.
via Oracle Community by Jorge Bastos, 1 year ago
Failed to start J2EE BI component: bi_cluster:bisearch#11.1.1
via Oracle Community by 2789861, 1 year ago
WARNING: Element Type: DOMAIN Element Id: null Operation Result: FAILED_TO_APPLY_CHANGES Detail Message: Timeout; Waiting for all managed servers to push configuration changes; [180 secs]; bi_server1
via Oracle Community by Girimarich, 1 year ago
WARNING: Element Type: DOMAIN Element Id: null Operation Result: FAILED_TO_APPLY_CHANGES Detail Message: Timeout; Waiting for all managed servers to push configuration changes; [180 secs]; bi_server1
via Oracle Community by user13263578, 1 year ago
MDS-00160: no local name has been specified for a resource [exec] MDS-00160: no local name has been specified for a resource [exec] MDS-00160: no local name has been specified for a resource [exec]
via wpthm.com by Unknown author, 2 years ago
MDS-00160: no local name has been specified for a resource MDS-00160: no local name has been specified for a resource MDS-00160: no local name has been specified for a resource
javax.management.MBeanException: WARNING: Element Type: MANAGED_SERVER Element Id: bi_server2 Operation Result: FAILED_CONTACTING_MANAGED_SERVERS Detail Message: Specified BI Managed Servers are shut down: bi_server2.
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.