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>

Similar Messages

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]

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/

OSB Service Health Tab Information

Hi All,
I was suppose to do some monitoring and performance testing on some of the OSB services . During this process, I have enabled Monitoring on the required services and was able to find the respective metrics on the Service Health Tab of the OSB Console .
Now my question/requirement is ,
Where does OSB store this information which is shown on the console . Could you please let me know if any of you know about the Table Name
If its not a table, could you please let me know is there a way to access this information in any other way
Thanks
Sandeep

Hi Sandeep,
You can access the statistics using JMX APIs. Using JMX framework you can pull the information.
http://docs.oracle.com/cd/E28280_01/admin.1111/e15867/monitoring_ops.htm#i1107353
There is a sample program provided in below link to retrieve statistics
"Sample Program to Retrieve Statistics for a Proxy Service that is Enabled for Monitoring"
http://docs.oracle.com/cd/E28280_01/admin.1111/e15867/app_jmx_monitoring.htm#CEGFFBFG
Cheers,
Sahil

HTTP connection from OSB web service to external system via a Proxy Server

Dear experts,
May I know has anyone tried to use HTTP protocol to send a request from OSB web service to external system via a proxy server? Heard that we need to establish some sort of tunnel (socket) to talk to Proxy Server. Can you please any have sample code or configuration steps to share?
Thank you very much!!

http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/global_resources.html#wp1137294
Adding Proxy Servers
Use the Summary of Proxy Servers page to add and configure Proxy Server resources and make them available in Oracle Service Bus as a system resource. You must be in an active session to configure or reconfigure Proxy Server resources.
1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
2. Select System Administration > Proxy Servers.
3. Click Add.
4. In the Name field, enter a name for the Proxy Server resource. This is a required field.
5. In the Description field, enter a short description for the Proxy Server resource.
6. In the Host-Port Parameters section, enter the following information:
1. In the Server Host field, enter the host name or IP address of the Proxy Server. This is a required field.
The Server Host name for the Oracle Service Bus proxy server must be identical to the server host name of the actual proxy server.
2. In the Clear Text Port field, enter the Proxy Server clear-text port number.
3. In the SSL Port field, enter the Proxy Server SSL port number. You must enter either a clear text or SSL port number.
4. Click Add.
You can configure multiple Proxy Servers for each Proxy Server resource. This enables Oracle Service Bus to perform load balancing and offer fault tolerance features for the Proxy Server resource.
7. If the Proxy Server performs proxy authentication, enter a user name in the User Name field, and the associated password in the Password and Confirm Password fields.
These fields are optional, and required only if the Proxy Server is secured.
8. Click Save to create and save the Proxy Server resource in the current session.
9. To end the session and deploy the configuration to the run time, click Activate under Change Center.

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

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

Error when starting managed server Message Too Long

          Hi,
          I'm trying to setup clustering with WLS6.1sp2.
          I use the jdk include with wls
          2 servers in the cluster OS=AIX
          1 Adminserver running on Solaris 8
          When I start a managed server on one of the clustered machines
          I see the following error.
          Starting Cluster Service ....
          <Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
          on port 7001, ip address 10.160.3.74>
          <Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
          java.io.IOException: Message too long
          java.io.IOException: Message too long
          at java.net.PlainDatagramSocketImpl.send(Native Method)
          at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
          at java.net.DatagramSocket.send(DatagramSocket.java:341)
          at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
          at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
          at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
          Code))
          at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
          at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
          at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
          at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
          at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)
          >
          <Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
          (cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
          <Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
          Server "s01ap007" for domain "axa" running in Production Mode>
          Also deploying doesn't seem to succeed could this be coused by this error
          I hope someone can help me.
          Best regards,
          Peter Van der Goten


          Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
          I will post this also here.
          The problem was that the upd_sendspace variable was set on
          a mutch to low value (9126) or something in this range
          It had to be set on 32769.
          this was done with no -o udp_sendspace=32769
          Best regards,
          Peter
          "Peter Van der Goten" <[email protected]> wrote:
          >
          >Hi,
          >I'm trying to setup clustering with WLS6.1sp2.
          >I use the jdk include with wls
          >2 servers in the cluster OS=AIX
          >1 Adminserver running on Solaris 8
          >
          >When I start a managed server on one of the clustered machines
          >I see the following error.
          >Starting Cluster Service ....
          ><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
          >listening
          >on port 7001, ip address 10.160.3.74>
          ><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
          >message:
          >java.io.IOException: Message too long
          >java.io.IOException: Message too long
          > at java.net.PlainDatagramSocketImpl.send(Native Method)
          > at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
          > at java.net.DatagramSocket.send(DatagramSocket.java:341)
          > at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
          > at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
          > at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
          >Code))
          > at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
          > at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
          > at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
          > at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
          > at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          > at weblogic.Server.main(Server.java:35)
          >>
          ><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
          >messages
          >(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
          ><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
          >Managed
          >Server "s01ap007" for domain "axa" running in Production Mode>
          >
          >Also deploying doesn't seem to succeed could this be coused by this error
          >
          >I hope someone can help me.
          >Best regards,
          >Peter Van der Goten
          >

ClassNotFoundException When Starting Managed Server with NodeManager

Hi Experts,
ENV:
Weblogic Server 10.3.3
Webcenter 11.1.1.3
My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
oracle.jrf.wls.JRFStartup
oracle.security.jps.wls.JpsWlsStartupClass
oracle.core.ojdl.weblogic.ODLConfiguration
oracle.jrf.AppContextStartup
oracle.ias.cache.Startup
oracle.dms.wls.DMSStartup
My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
Thanks,
Todd

Trying setting the property StartScriptEnabled=true instead of false.
You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd.

Error when starting managed server

Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, Per

Hi Per
I have problems in creating managed server in the default mydomain .Do i need
to configure a new machine if the managed server and admin server are going to be
in the same machine.
I created a new machine that has the following parameters
listen address :localhost
Listen port :7001
As the next step i created a server with the machine name pointing to new one, when
i tried to start this as a managed server it gives an Error
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: java
.security.acl.NotOwnerException - with nested exception:
[java.lang.IllegalAccessError: java.security.acl.NotOwnerException]
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:12
5)
could you please help me on creating a managed server
thanks in advance
karthik
[email protected] (Per Olesen) wrote:
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, Per

Getting error when starting managed server from administration server

          When i start one of my managed server in the cluster i get the following error
          The WebLogic Server did not start up properly.
          Exception raised: java.lang.ArrayIndexOutOfBoundsException
          java.lang.ArrayIndexOutOfBoundsException
          at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
          at com.bea.utils.misc.Process.validate(Process.java:1231)
          at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
          at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
          at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          Please tell if somebody know it


Do you have any other products from BEA other than WLS?
          I can't seem to find the following (com/bea/utils/misc) from WLS source
          line ?
          Kumar
          Ritesh Kapoor wrote:
          > When i start one of my managed server in the cluster i get the following error
          > The WebLogic Server did not start up properly.
          > Exception raised: java.lang.ArrayIndexOutOfBoundsException
          > java.lang.ArrayIndexOutOfBoundsException
          > at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
          > at com.bea.utils.misc.Process.validate(Process.java:1231)
          > at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
          > at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
          > at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          >
          > Please tell if somebody know it
          >
          >

Acl.NotOwnerException when starting managed server

I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan

Hi Joan
Go to the Managedserver Confiuration and give the Correct listen Port and SSL.I hope this will help you.
Nagesh Rao
Joan Silverman wrote:
I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan

Server start arguments ignored when starting managed server

Hi
We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
However those arguments are not picked up when we are starting the managed server.
We are using a shell script to start the managed server using the weblogic.Admin class functionality.
If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
This is the scenario in Weblogic 10.0.0.
Can anybody please explain why the arguments are not picked up?
We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
Is the difference in behavior because of the difference in versions?
Edited by: user1030647 on Aug 29, 2010 12:26 AM

Thanks Jay for the immediate responses.
The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
Do you have any info which points to this discrepancy?

HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marco

Marco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco

Admin console unavailable when a managed server from domain get stuck

We have a weblogic 10.3.2 domain with an admin server and a managed server in two different virtual machines. When for some reason this managed server get stuck (e.g. cpu 100 %) admin consolo starts to go slow up to the point it´s impossible to get access to this.
Did anybody face to this problem before ?
Thanks.

Hi,
Try to find which object causing high cpu usage following Oracle Doc ID 779349.1.
by looking into the files then we can find what would be exact cause of this issue.
Regards,
Kalyan

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

Similar Messages

Maybe you are looking for