SAP Knowledge Base Article - Preview

2979960 - ASE Cockpit failing to start after installation/configuration - SAP ASE

Symptom

After installation ASE 16 Cockpit, service is not able to start, from the agent.log:

2020-10-13 11:55:51,447 [INFO ] [rmi.RMIService ] [main] - RMI Service using dynamic listener address with java.rmi.server.hostname=xldsyb01.swacorp.com
2020-10-13 11:55:51,447 [INFO ] [rmi.RMIService ] [main] - Starting RMI Service...
2020-10-13 11:55:51,493 [INFO ] [rmi.RMIService ] [main] - RMI registry service started at port 4003.
2020-10-13 11:55:51,557 [INFO ] [rmi.RMIService ] [main] - RMI Service listener address : xldsyb01/10.34.52.149
2020-10-13 11:55:51,557 [INFO ] [rmi.RMIService ] [main] - RMI Service using dynamic listener address with java.rmi.server.hostname=xldsyb01.swacorp.com
2020-10-13 11:55:51,559 [INFO ] [rmi.RMIService ] [main] - Starting JMX Connector Server with address xldsyb01/10.34.52.149...
2020-10-13 11:55:51,586 [FATAL] [rmi.RMIService ] [main] - Failed to start RMI Connector server.
java.io.IOException: Cannot bind to URL [rmi://xldsyb01.swacorp.com:4003/agent]: javax.naming.CommunicationException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: filter status: REJECTED]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
at com.sybase.ua.services.rmi.RMIService.startJmxConnectorServer(Unknown Source)
at com.sybase.ua.services.rmi.RMIService.doStart(Unknown Source)
at com.sybase.ua.service.AgentServiceBase.start(Unknown Source)
at com.sybase.ua.services.AgentLifecycleManager.startService(Unknown Source)
at com.sybase.ua.services.AgentLifecycleManager.startServices(Unknown Source)
at com.sybase.ua.services.AgentLifecycleManager.startAgent(Unknown Source)
at com.sybase.ua.services.Agent.doStart(Unknown Source)
at com.sybase.ua.service.AgentServiceBase.start(Unknown Source)
at com.sybase.ua.services.Agent.startAgent(Unknown Source)
at com.sybase.ua.startup.Main.startAgent(Unknown Source)
at com.sybase.ua.startup.Main.start(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sybase.ua.startup.Startup.doLoadMainClass(Unknown Source)
at com.sybase.ua.startup.Startup.start(Unknown Source)
at com.sybase.ua.startup.Startup.main(Unknown Source)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: filter status: REJECTED]





Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0
  • ASE Cockpit 16.0

Product

SAP Replication Server 15.7

Keywords

ASE Cockpit, service, 16.0 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.