One of managed in OBIEE server shows "Unkown"state

The Admin server log shows the following

 <1356412515693> <BEA-149504> <The adminstration server was unable to establish JMX Connectivity with the FoundationServices3 at the JMX Service URL of service:jmx:t3://[2001:0:4137:9e76:30de:d4f:3f57:febe]:28080/jndi/weblogic.management.mbeanservers.runtime.>

Managed server logs shows

####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:141:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:c486:1403:ffe4:42e7:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:30de:d4f:3f57:febe:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default" is now listening on 2001:0:4137:9e76:30de:d4f:3f57:febe:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[6]" is now listening on 0:0:0:0:0:0:0:1:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.1.65:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<2012-12-28 上午12时18分31秒 CST> <Notice> <Server> <HFM11APP5> <FoundationServices3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356625111286> <BEA-002613> <Channel "Default[5]" is now listening on 127.0.0.1:28080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>

Solution

Consult network administrator to configure IPv6 to make machines in this network  communicate with each other correctly via IPv6.

If above solution is not available, following workaround is available

IPv4 can be used instead of IPv6 as listen address by one of following method.
1. Add -Djava.net.preferIPv4Stack=true in script, e.g.,
in <domain>/bin/setDoaminEnv.cmd/sh, add following to the end:

Windows:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.net.preferIPv4Stack=true
Unix:
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true"
export JAVA_OPTIONS

2. add the listen address to config.xml directly(before modification, please remember to backup config.xml), like:
Stop AdminServer and managedServer firstly, and then modify configuration of managedServer in config.xml as:

<server>
  <name>FoundationServices3</name>
  <ssl>
    <enabled>true</enabled>
    <listen-port>28443</listen-port>
  </ssl>
  <machine>hfm11app5</machine>
  <listen-port>28080</listen-port>
  <cluster>FoundationServices</cluster>
  <listen-address>192.168.1.65</listen-address>
  <jta-migratable-target>
    <user-preferred-server>FoundationServices3</user-preferred-server>
    <cluster>FoundationServices</cluster>
  </jta-migratable-target>
</server>

 And then restart adminServer and managedServers.

Or

3. Firstly, stop managedServer, make sure that the state managed server is "Shutdown" on console
Secondly, add listen address in console to managed server. After activate, start managedServer.
NOTE: Do NOT modify the listen address of managed server on console when managed server is running. This would lead to adminServer hangs at waitForCompletion because it can not connect to managed Server.

Thanks,

Sandeep

SHARE SHARE SHARE

About test