cancel
Showing results for 
Search instead for 
Did you mean: 

500 Internal Server Error SAP NetWeaver Application Server/Java AS

Former Member
0 Kudos

Hello Experts,

I have successfully deployed all the patches to the AS JAVA System and it all went fine with the upgrade to NW 7.31 (AS JAVA) and MMC the server and DAA agent is up and running.

However, When I am trying to connect to Administrator or System information following is the error. Please help me out with few tips.

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

Hello

Instead of pasting the trace as replies try to zip the log and attach it to the thread.

Check the hint provided in this SAP note helps.

1562141 - Application Server Java cannot start during upgrade to 7.30

As I see exitcode 2150 in the trace you may also check this SAP note.

1945047 - AS Java stops with exitcode 2150

If possible stop the SAP system, restart the Windows server and start SAP.

If the issue appears again supply the latest default trace (attached as a zip file to your reply).

Regards

RB

Former Member
0 Kudos

Thanks for your help.

Error was solved after updating several patches.

Note : 1794179 was very helpful in that

Thanks and regards

Siddharth

Answers (4)

Answers (4)

Former Member

Hi,

Please check whether the patch deployment is 100% successful. If yes, restart the java engine completely. If still problem exists, paste the recent last 300 lines of std_server logs(to confirm whether java is started successfully or not)

gururaj_srinivasa
Participant
0 Kudos

Hi,

Did you bounce the system post deployment?, if not try bouncing the server.

Also can you provide the URL you are getting when you click on System info

Guru

Former Member
0 Kudos

Bouncing the server???

Can you please eloborate?

divyanshu_srivastava3
Active Contributor
0 Kudos

Bouncing means restarting the server.

Please refer the note that was told you before.

Divyanshu

Former Member
0 Kudos

Hello

Alongwith the 500 Internal Server Error, you will see a "log id" on the browser screen. Search the "log id" in the latest defaultTrace file of server node to get the detailed exception trace. If you do not get a clue about the root cause, paste the complete log here and i will check and advice further.

Cheers,
Tapan

Former Member
0 Kudos

please find the default trace log as a reply to an above comment.

regards

siddharth

Former Member
0 Kudos

Hello

The log attached from defaultTrace file does not contain the Log ID shown in the screenshot of "500 Internal server Error" page. Can you please reproduce the issue, search the resulting Log ID in the latest defaultTrace file of server node, and paste here only that particular log snippet?

Cheers,

Tapan

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Siddharth,

Can you goto JCMON or JSMON and check the mode and process.

If your system is in safe mode, turn it off from config tool.

Also, share default trace and application logs.

Divyanshu

Former Member
0 Kudos

Due to huge size of log i'm replying in several parts....

Default trace....

part 1

=============================================================================

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[./log/defaultTrace_00.trc]/-->
<!--PATTERN[defaultTrace_00.trc]/-->
<!--FORMATTER[com.sap.tc.logging.ListFormatter]/-->
<!--ENCODING[UTF8]/-->
<!--FILESET[0, 20, 10485760]/-->
<!--PREVIOUSFILE[defaultTrace_00.19.trc]/-->
<!--NEXTFILE[defaultTrace_00.1.trc]/-->
<!--ENGINEVERSION[7.31.3710.148365.20111012091351]/-->
<!--LOGHEADER[END]/-->
#2.0
#2014 07 09 06:22:38:327#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000224###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 06:22:46:185#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000100000224#3448650000000531##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####1b26712b076c11e4b65c00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:22:46:186#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000300000224#3448650000000531##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####1b26712b076c11e4b65c00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:23:14:217#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE00080000000200000224#3448650000000588##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####1b26712b076c11e4b65c00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 06:23:21:090#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000C0000001400000224#3448650000001055##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 06:23:21:825#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00160000000600000224#3448650000001158##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 06:23:22:248#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE001A0000000100000224#3448650000001191##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 06:23:24:867#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001C0000000000000224#3448650000001404##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 06:23:24:934#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001C0000000100000224#3448650000001404##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 06:23:28:741#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00050000000500000224#3448650000001458##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####1B26712B076C11E4B65C00155D336301#1b26712b076c11e4b65c00155d336301#1b26712b076c11e4b65c00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 06:24:15:658#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00210000000100000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [15] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:15:658#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00210000000200000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [15] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:24:16:106#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00100000000900000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [18] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:16:106#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00100000000A00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [18] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:24:20:527#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00100000000C00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [128] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:20:527#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00100000000D00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [128] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 06:24:20:964#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001B0000000D00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1578] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:20:964#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001B0000000E00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1578] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 06:24:24:260#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00300000000200000224#3448650000002764#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Application [51]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 09 06:24:26:119#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00150000000800000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [240] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:26:119#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00150000000900000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [240] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 5caff326
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 06:24:32:079#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00150000000B00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [5426] ms on server process [3448650]: #

#2.0
#2014 07 09 06:24:32:079#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00150000000C00000224#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####370F9336076C11E4A279000000349F4A#370f9336076c11e4a279000000349f4a#370f9336076c11e4a279000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [5426] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: eb5ac4b
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: eb5ac4b
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 06:29:08:770#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003F0000000100000224#3448650000000003##com.sap.engine.services.deploy.server.TransactionManager####0160DBB1076D11E4880D000000349F4A#0160dbb1076d11e4880d000000349f4a#0160dbb1076d11e4880d000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [9] ms on server process [3448650]: #

#2.0
#2014 07 09 06:29:08:796#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003F0000000200000224#3448650000000003##com.sap.engine.services.deploy.server.TransactionManager####0160DBB1076D11E4880D000000349F4A#0160dbb1076d11e4880d000000349f4a#0160dbb1076d11e4880d000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [9] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:29:08:931#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000C0000001700000224#3448650000000003##com.sap.engine.services.deploy.server.TransactionManager####0160DBB1076D11E4880D000000349F4A#0160dbb1076d11e4880d000000349f4a#0160dbb1076d11e4880d000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 09 06:29:08:932#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000C0000001800000224#3448650000000003##com.sap.engine.services.deploy.server.TransactionManager####0160DBB1076D11E4880D000000349F4A#0160dbb1076d11e4880d000000349f4a#0160dbb1076d11e4880d000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:29:09:568#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00410000000000000224#3448650000001665##com.sap.engine.core.service630.container.ServiceWrapper####0160DBB1076D11E4880D000000349F4A#0160dbb1076d11e4880d000000349f4a#0160dbb1076d11e4880d000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 06:29:09:760#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00430000000100000224#3448650000001399##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###1b26712b076c11e4b65c00155d336301##0#Application [32]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 06:29:09:760#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00440000000000000224#3448650000001404##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###1b26712b076c11e4b65c00155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 06:29:12:834#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00480000000000000224#3448650000002294##com.sap.engine.core.service630.container.ServiceWrapper#####0160dbb1076d11e4880d000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 06:29:12:929#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE001C0000000500000224#3448650000002258##com.sap.engine.core.service630.container.ServiceWrapper#####0160dbb1076d11e4880d000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 06:29:13:050#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE004C0000000000000224#3448650000002447##com.sap.engine.core.service630.container.ServiceWrapper#####0160dbb1076d11e4880d000000349f4a##0#Event Processor [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 09 06:29:13:098#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004C0000000100000224#3448650000002447##com.sap.engine.core.service630.container.ContainerObjectRegistry#####0160dbb1076d11e4880d000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 06:29:13:110#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE004D0000000100000224#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####1b26712b076c11e4b65c00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 09 06:29:13:110#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE004D0000000200000224#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####1b26712b076c11e4b65c00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:29:16:491#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE004F0000000000000224#3448650000001388##com.sap.engine.services.wsrm#####1b26712b076c11e4b65c00155d336301##0#System [12]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:30:44:859#0-700#Warning#com.sap.engine.core.thread.impl3.ThreadManagerImpl#
com.sap.ASJ.krn_thd.000113#BC-JAS-COR#kernel.sda#C000AC1D32BE00000000000100001408###com.sap.engine.core.thread.impl3.ThreadManagerImpl########Thread[main,5,main]#Plain##
The server process is in SAFE mode. No applications will be started#

#2.0
#2014 07 09 06:30:49:692#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000D00001408###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 06:30:57:307#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000100001408#3448650000000539##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####3f0509f0076d11e4837e00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:30:57:308#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000300001408#3448650000000539##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####3f0509f0076d11e4837e00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:31:03:287#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A0000000200001408#3448650000000593##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####3f0509f0076d11e4837e00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 06:31:08:037#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000E0000000200001408#3448650000001086##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 06:31:08:467#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00040000000200001408#3448650000001087##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 06:31:10:514#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000E0000000400001408#3448650000001192##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 06:31:10:631#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00180000000100001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Could not register with the Timeout Manager because it does not exist.#

#2.0
#2014 07 09 06:31:10:633#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00180000000300001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Error syncing credential expiry changes:
com.adobe.ads.service.configuration.ConfigurationException: Could not register with the Timeout Manager because it does not exist.
at com.adobe.ads.service.configuration.ConfigurationService.registerTimeoutListener(Unknown Source)
at com.adobe.ads.service.configuration.ConfigurationService.configurationChanged(Unknown Source)
at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:165)
at com.sap.engine.core.configuration.impl.event.ListenerCaller.run(ListenerCaller.java:53)
at java.lang.Thread.run(Thread.java:722)
#

#2.0
#2014 07 09 06:31:10:654#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00190000000100001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Could not register with the Timeout Manager because it does not exist.#

#2.0
#2014 07 09 06:31:10:654#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00190000000300001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Error syncing credential expiry changes:
com.adobe.ads.service.configuration.ConfigurationException: Could not register with the Timeout Manager because it does not exist.
at com.adobe.ads.service.configuration.ConfigurationService.registerTimeoutListener(Unknown Source)
at com.adobe.ads.service.configuration.ConfigurationService.configurationChanged(Unknown Source)
at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:165)
at com.sap.engine.core.configuration.impl.event.ListenerCaller.run(ListenerCaller.java:53)
at java.lang.Thread.run(Thread.java:722)
#

#2.0
#2014 07 09 06:31:10:699#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000400001408#3448650000001245##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:704#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000600001408#3448650000001258##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:705#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001A0000000100001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Could not register with the Timeout Manager because it does not exist.#

#2.0
#2014 07 09 06:31:10:705#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001A0000000300001408###com.adobe.service.sap.configuration####47EF4A1F076D11E4AE5A00155D336301#47ef4a1f076d11e4ae5a00155d336301#47ef4a1f076d11e4ae5a00155d336301#0#Thread[Configuration Manager listener caller,5,SystemThreadGroup]#Plain##
Error syncing credential expiry changes:
com.adobe.ads.service.configuration.ConfigurationException: Could not register with the Timeout Manager because it does not exist.
at com.adobe.ads.service.configuration.ConfigurationService.registerTimeoutListener(Unknown Source)
at com.adobe.ads.service.configuration.ConfigurationService.configurationChanged(Unknown Source)
at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:165)
at com.sap.engine.core.configuration.impl.event.ListenerCaller.run(ListenerCaller.java:53)
at java.lang.Thread.run(Thread.java:722)
#

#2.0
#2014 07 09 06:31:10:763#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000800001408#3448650000001259##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:776#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000A00001408#3448650000001260##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:830#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000C00001408#3448650000001261##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:834#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000000E00001408#3448650000001270##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:844#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00110000000500001408#3448650000001276##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:10:862#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00130000000200001408#3448650000001293##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:084#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00020000000300001408#3448650000001317##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:221#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000B0000001100001408#3448650000001333##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:230#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001B0000000100001408#3448650000001344##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:258#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00040000000800001408#3448650000001354##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:273#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001C0000000100001408#3448650000001363##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:278#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001C0000000300001408#3448650000001376##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:301#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000B0000001500001408#3448650000001393##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:356#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00030000000400001408#3448650000001429##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:361#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00030000000600001408#3448650000001446##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:368#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00030000000800001408#3448650000001456##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:404#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00010000000800001408#3448650000001470##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:423#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00050000000200001408#3448650000001483##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:434#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00070000000800001408#3448650000001506##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:488#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00130000000600001408#3448650000001528##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:542#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE001E0000000200001408#3448650000001544##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:618#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00110000000800001408#3448650000001557##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:714#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00150000000600001408#3448650000001570##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:12:846#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000D0000000200001408#3448650000001601##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:13:690#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000E0000000600001408#3448650000001632##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:13:724#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00210000000100001408#3448650000001646##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:13:743#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000E0000000900001408#3448650000001661##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:14:085#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00210000000400001408#3448650000001675##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:14:090#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00210000000700001408#3448650000001689##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:14:156#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00220000000000001408#3448650000001666##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 06:31:14:370#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00220000000100001408#3448650000001666##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 06:31:14:867#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00150000000C00001408#3448650000001710##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:14:996#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00220000000300001408#3448650000001724##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:15:206#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000C0000000900001408#3448650000001739##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:15:598#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00220000000600001408#3448650000001752##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:15:643#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00170000001400001408#3448650000001766##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:15:648#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00220000000900001408#3448650000001779##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:15:784#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00100000000C00001408#3448650000001796##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:16:049#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00150000000F00001408#3448650000001818##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:16:053#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00150000001100001408#3448650000001832##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:16:920#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00070000000B00001408#3448650000001845##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:17:870#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00090000000B00001408#3448650000001859##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:18:207#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000C0000000C00001408#3448650000001850##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 06:31:18:237#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE000B0000001700001408#3448650000001892##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:18:286#0-700#Error#com.adobe.service.sap.configuration#
#BC-SRV-FP#com.adobe~DocumentServicesConfiguration#C000AC1D32BE00100000000E00001408#3448650000001911##com.adobe.service.sap.configuration####3F0509F0076D11E4837E00155D336301#3f0509f0076d11e4837e00155d336301#3f0509f0076d11e4837e00155d336301#0#Event Processor [com.adobe~DocumentServicesConfiguration]#Plain##
An error occurred while registering the Adobe Document Services Configuration Service (instance: unknown) JMS message handler: Object not found in lookup of ADSTopicConnectionFactory.#

#2.0
#2014 07 09 06:31:18:645#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000100001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
Configuration [DocumentServicesLicense] not found in [root]

Stack Trace:
com.sap.engine.frame.core.configuration.NameNotFoundException: Configuration [DocumentServicesLicense] not found in [root]
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.determineMissingConfiguration(ConfigurationHandlerImpl.java:1715)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.determineMissingConfiguration(ConfigurationHandlerImpl.java:1686)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:1047)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:992)
at com.adobe.service.sap.licensing.LicenseService.mf__SetConfigurationValue(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.doStartupValueChecks(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.containerStarted(Unknown Source)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:154)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:31:18:646#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000300001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
Configuration [DocumentServicesLicense] not found in [root] #

#2.0
#2014 07 09 06:31:18:659#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000500001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
A config entry with the name "HourOfStatusCheck could not be found in the configuration "DocumentServicesLicense".

Stack Trace:
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "HourOfStatusCheck could not be found in the configuration "DocumentServicesLicense".
at com.sap.engine.core.configuration.impl.ConfigurationData.modifyValueEntry(ConfigurationData.java:731)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:820)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:784)
at com.adobe.service.sap.licensing.LicenseService.mf__SetConfigurationValue(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.doStartupValueChecks(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.containerStarted(Unknown Source)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:154)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:31:18:659#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000700001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
A config entry with the name "HourOfStatusCheck could not be found in the configuration "DocumentServicesLicense".#

#2.0
#2014 07 09 06:31:18:675#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000900001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
A config entry with the name "MinuteOfStatusCheck could not be found in the configuration "DocumentServicesLicense".

Stack Trace:
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "MinuteOfStatusCheck could not be found in the configuration "DocumentServicesLicense".
at com.sap.engine.core.configuration.impl.ConfigurationData.modifyValueEntry(ConfigurationData.java:731)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:820)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:784)
at com.adobe.service.sap.licensing.LicenseService.mf__SetConfigurationValue(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.doStartupValueChecks(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.containerStarted(Unknown Source)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:154)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:31:18:675#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE00160000000B00001408#3448650000000001##com.adobe.service.sap.licensing####4F03A118076D11E48E32000000349F4A#4f03a118076d11e48e32000000349f4a#4f03a118076d11e48e32000000349f4a#0#Event Processor [com.adobe~LicenseService]#Plain##
A config entry with the name "MinuteOfStatusCheck could not be found in the configuration "DocumentServicesLicense".#

#2.0
#2014 07 09 06:32:04:804#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00360000000300001408#3448650000000027##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_nty],5,Managed_Application_Thread]#Plain##
SL container:Initializing context, ID: 147#

#2.0
#2014 07 09 06:32:08:517#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00360000000500001408#3448650000000027##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_nty],5,Managed_Application_Thread]#Plain##
SL Domain: LD Data imported for C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_nty.SL-SDA1404912724231\\sap.com~sc~di_nty.SL-SDA#

#2.0
#2014 07 09 06:32:08:518#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00360000000700001408#3448650000000027##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_nty],5,Managed_Application_Thread]#Plain##
SLDeploymentFactory: LD file to delete : C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\edencnthandler\\1404912724693147\\ldcontent_2965739595100805508.zip.  Status: true#

#2.0
#2014 07 09 06:32:08:519#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00360000000900001408#3448650000000027##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_nty],5,Managed_Application_Thread]#Plain##
SL Container: Cleaning up, ID:147#

#2.0
#2014 07 09 06:32:08:524#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00390000000300001408#3448650000000036##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~adssap],5,Managed_Application_Thread]#Plain##
SL container:Initializing context, ID: 165#

#2.0
#2014 07 09 06:32:10:877#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00390000000500001408#3448650000000036##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~adssap],5,Managed_Application_Thread]#Plain##
SL Domain: LD Data imported for C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sc~adssap.SL-SDA1404912727780\\sc~adssap.SL-SDA#

#2.0
#2014 07 09 06:32:10:878#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00390000000700001408#3448650000000036##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~adssap],5,Managed_Application_Thread]#Plain##
SLDeploymentFactory: LD file to delete : C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\edencnthandler\\1404912727928165\\ldcontent_6479552252983582293.zip.  Status: true#

#2.0
#2014 07 09 06:32:10:879#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00390000000900001408#3448650000000036##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~adssap],5,Managed_Application_Thread]#Plain##
SL Container: Cleaning up, ID:165#

#2.0
#2014 07 09 06:32:10:882#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE003A0000000300001408#3448650000000045##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_dtr],5,Managed_Application_Thread]#Plain##
SL container:Initializing context, ID: 147#

#2.0
#2014 07 09 06:32:12:031#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE003C0000002C00001408#3448650000000061##com.sap.engine.bootstrap#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesSupportFiles],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [xdc_directories] with id [C0030] from component [com.adobe~DocumentServicesSupportFiles] is empty#

#2.0
#2014 07 09 06:32:12:032#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE003C0000002D00001408#3448650000000061##com.sap.engine.bootstrap#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesSupportFiles],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [custom_jobProfiles] with id [C0029] from component [com.adobe~DocumentServicesSupportFiles] is empty#

#2.0
#2014 07 09 06:32:12:036#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE003C0000002E00001408#3448650000000061##com.sap.engine.bootstrap#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesSupportFiles],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [jobProfiles] with id [C0028] from component [com.adobe~DocumentServicesSupportFiles] is empty#

#2.0
#2014 07 09 06:32:12:038#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE003C0000002F00001408#3448650000000061##com.sap.engine.bootstrap#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesSupportFiles],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [xslt] with id [C0027] from component [com.adobe~DocumentServicesSupportFiles] is empty#

#2.0
#2014 07 09 06:32:12:040#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE003C0000003000001408#3448650000000061##com.sap.engine.bootstrap#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesSupportFiles],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [xcixdc] with id [C0026] from component [com.adobe~DocumentServicesSupportFiles] is empty#

#2.0
#2014 07 09 06:32:12:938#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE003A0000000500001408#3448650000000045##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_dtr],5,Managed_Application_Thread]#Plain##
SL Domain: LD Data imported for C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_dtr.SL-SDA1404912728785\\sap.com~sc~di_dtr.SL-SDA#

#2.0
#2014 07 09 06:32:12:939#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE003A0000000700001408#3448650000000045##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_dtr],5,Managed_Application_Thread]#Plain##
SLDeploymentFactory: LD file to delete : C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\edencnthandler\\1404912728842147\\ldcontent_372361789153190934.zip.  Status: true#

#2.0
#2014 07 09 06:32:12:939#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE003A0000000900001408#3448650000000045##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_dtr],5,Managed_Application_Thread]#Plain##
SL Container: Cleaning up, ID:147#

#2.0
#2014 07 09 06:32:13:244#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.0020330#BC-JAS-DPL#deploy#C000AC1D32BE003D0000001100001408#3448650000000068##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~fp~config],5,Managed_Application_Thread]#Plain##
Folder [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~tc~fp~config.ear1404912732905] failed to be deleted#

#2.0
#2014 07 09 06:32:13:244#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.002033#BC-JAS-DPL#deploy#C000AC1D32BE003D0000001200001408#3448650000000068##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~fp~config],5,Managed_Application_Thread]#Plain##
File [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~tc~fp~config.ear1404912732905\\sap.com~tc~fp~config.ctc] could not be deleted.#

#2.0
#2014 07 09 06:32:17:406#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00410000000300001408#3448650000000124##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
SL container:Initializing context, ID: 161#

#2.0
#2014 07 09 06:32:19:424#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00410000000500001408#3448650000000124##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
SL Domain: LD Data imported for C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cms.SL-SDA1404912737358\\sap.com~sc~di_cms.SL-SDA#

#2.0
#2014 07 09 06:32:19:425#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00410000000700001408#3448650000000124##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
SLDeploymentFactory: LD file to delete : C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\edencnthandler\\1404912737400161\\ldcontent_3497235876256641668.zip.  Status: true#

#2.0
#2014 07 09 06:32:19:425#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00410000000900001408#3448650000000124##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
SL Container: Cleaning up, ID:161#

#2.0
#2014 07 09 06:32:19:474#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.0020330#BC-JAS-DPL#deploy#C000AC1D32BE00410000001D00001408#3448650000000122##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
Folder [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cms.SL-SDA1404912737358] failed to be deleted#

#2.0
#2014 07 09 06:32:19:474#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.002033#BC-JAS-DPL#deploy#C000AC1D32BE00410000001E00001408#3448650000000122##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cms],5,Managed_Application_Thread]#Plain##
File [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cms.SL-SDA1404912737358\\sap.com~sc~di_cms.SL-SDA] could not be deleted.#

#2.0
#2014 07 09 06:32:19:743#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00420000000300001408#3448650000000132##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
SL container:Initializing context, ID: 161#

#2.0
#2014 07 09 06:32:21:972#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00420000000500001408#3448650000000132##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
SL Domain: LD Data imported for C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cbs.SL-SDA1404912739686\\sap.com~sc~di_cbs.SL-SDA#

#2.0
#2014 07 09 06:32:21:973#0-700#Info#com.sap.sdt.sldeploymentlib.SLDeploymentFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00420000000700001408#3448650000000132##com.sap.sdt.sldeploymentlib.SLDeploymentFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
SLDeploymentFactory: LD file to delete : C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\edencnthandler\\1404912739736161\\ldcontent_461109072398881069.zip.  Status: true#

#2.0
#2014 07 09 06:32:21:974#0-700#Info#com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#
#BC-UPG-OCS-SPJ#edencnthandler#C000AC1D32BE00420000000900001408#3448650000000132##com.sap.sdt.slconvenienceapi.systemaccess.SlDomainSystemWBEMFactory#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
SL Container: Cleaning up, ID:161#

#2.0
#2014 07 09 06:32:22:011#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.0020330#BC-JAS-DPL#deploy#C000AC1D32BE00420000001D00001408#3448650000000130##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
Folder [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cbs.SL-SDA1404912739686] failed to be deleted#

#2.0
#2014 07 09 06:32:22:011#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.002033#BC-JAS-DPL#deploy#C000AC1D32BE00420000001E00001408#3448650000000130##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_sc~di_cbs],5,Managed_Application_Thread]#Plain##
File [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~sc~di_cbs.SL-SDA1404912739686\\sap.com~sc~di_cbs.SL-SDA] could not be deleted.#

#2.0
#2014 07 09 06:32:24:333#0-700#Warning#com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#
com.sap.ASJ.dpl_ds.003009#BC-CTS-DTR-SRV#sap.com/tc~jdi~heartbeat~enterpriseapp#C000AC1D32BE00480000000300001408#3448650000000181##com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~jdi~heartbeat~enterpriseapp],5,Managed_Application_Thread]#Plain##
JLinEE validation of application [sap.com/tc~jdi~heartbeat~enterpriseapp] returned result Messages for application "sap.com/tc~jdi~heartbeat~enterpriseapp" reported by JLinEE checks:
WARNINGS:
Security Role Test: com.sap.ASJ.webjlin.000028 Value "DtrSecurityRole" of <role-name> sub-tag of <auth-constraint> tag is not valid. The value must match a defined security role name in the web application., file: sap.com~tc~jdi~heartbeat~webapp.war\#WEB-INF/web.xml, severity: warning
.#

#2.0
#2014 07 09 06:32:25:001#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-CTS-DTR-SRV#sap.com/tc~jdi~heartbeat~enterpriseapp#C000AC1D32BE00480000003400001408#3448650000000181##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~jdi~heartbeat~enterpriseapp],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~jdi~heartbeat~enterpriseapp] finished with non-critical warnings for [976] ms on server process [3448650]: #

#2.0
#2014 07 09 06:32:25:001#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-CTS-DTR-SRV#sap.com/tc~jdi~heartbeat~enterpriseapp#C000AC1D32BE00480000003500001408#3448650000000181##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~jdi~heartbeat~enterpriseapp],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~jdi~heartbeat~enterpriseapp] finished with non-critical warnings for [976] ms on server process [3448650]: [
>>> Warnings <<<
1). Security Role Test: com.sap.ASJ.webjlin.000028 Value "DtrSecurityRole" of <role-name> sub-tag of <auth-constraint> tag is not valid. The value must match a defined security role name in the web application., file: sap.com~tc~jdi~heartbeat~webapp.war\#WEB-INF/web.xml, severity: warning]#

#2.0
#2014 07 09 06:32:25:004#0-700#Warning#com.sap.engine.services.dc.gd.impl#
com.sap.ASJ.dpl_dc.005102#BC-JAS-DPL#tc~bl~deploy_controller#C000AC1D32BE00480000003600001408#3448650000000181##com.sap.engine.services.dc.gd.impl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~jdi~heartbeat~enterpriseapp],5,Managed_Application_Thread]#Plain##
[Server 00 00_34486] (21) :Deploy Service's deploy operation has finished with warnings. CSN component of deployment item is [BC-CTS-DTR-SRV].
[
Warning occurred on server 3448650 during deploy of sap.com/tc~jdi~heartbeat~enterpriseapp : Security Role Test: com.sap.ASJ.webjlin.000028 Value "DtrSecurityRole" of <role-name> sub-tag of <auth-constraint> tag is not valid. The value must match a defined security role name in the web application., file: sap.com~tc~jdi~heartbeat~webapp.war\#WEB-INF/web.xml, severity: warning

CSN component of deployment item is BC-CTS-DTR-SRV]#

#2.0
#2014 07 09 06:32:25:592#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.0020330#BC-JAS-DPL#deploy#C000AC1D32BE00470000002D00001408#3448650000000182##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~cvers~proxy],5,Managed_Application_Thread]#Plain##
Folder [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~tc~SL~CMS~cvers~proxy.ear1404912743878] failed to be deleted#

#2.0
#2014 07 09 06:32:25:593#0-700#Warning#com.sap.engine.services.deploy.server.DUtils#
com.sap.ASJ.dpl_ds.002033#BC-JAS-DPL#deploy#C000AC1D32BE00470000002E00001408#3448650000000182##com.sap.engine.services.deploy.server.DUtils#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~cvers~proxy],5,Managed_Application_Thread]#Plain##
File [C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\server0\\temp\\deploy\\sap.com~tc~SL~CMS~cvers~proxy.ear1404912743878\\sap.com~tc~SL~CMS~cvers~proxy.wsar] could not be deleted.#

#2.0
#2014 07 09 06:32:27:146#0-700#Warning#com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#
com.sap.ASJ.dpl_ds.003009#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE004A0000000300001408#3448650000000276##com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~xxxEar],5,Managed_Application_Thread]#Plain##
JLinEE validation of application [sap.com/tc~SL~CMS~xxxEar] returned result Messages for application "sap.com/tc~SL~CMS~xxxEar" reported by JLinEE checks:
WARNINGS:
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Deployer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning
.#

#2.0
#2014 07 09 06:32:27:918#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE004A0000005300001408#3448650000000276##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~xxxEar],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~SL~CMS~xxxEar] finished with non-critical warnings for [1215] ms on server process [3448650]: #

#2.0
#2014 07 09 06:32:27:919#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE004A0000005400001408#3448650000000276##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~xxxEar],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~SL~CMS~xxxEar] finished with non-critical warnings for [1215] ms on server process [3448650]: [
>>> Warnings <<<
1). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning
2). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Deployer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning]#

#2.0
#2014 07 09 06:32:27:920#0-700#Warning#com.sap.engine.services.dc.gd.impl#
com.sap.ASJ.dpl_dc.005102#BC-JAS-DPL#tc~bl~deploy_controller#C000AC1D32BE004A0000005500001408#3448650000000276##com.sap.engine.services.dc.gd.impl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~xxxEar],5,Managed_Application_Thread]#Plain##
[Server 00 00_34486] (21) :Deploy Service's deploy operation has finished with warnings. CSN component of deployment item is [BC-CTS-CMS].
[
Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~xxxEar : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~xxxEar : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Deployer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~xxxweb.war\#WEB-INF/web.xml, severity: warning

===========================================================================

Former Member
0 Kudos

part 2

===========================================================================

CSN component of deployment item is BC-CTS-CMS]#

#2.0
#2014 07 09 06:32:28:407#0-700#Warning#com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#
com.sap.ASJ.dpl_ds.003009#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE004B0000000300001408#3448650000000313##com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesLicenseManager],5,Managed_Application_Thread]#Plain##
JLinEE validation of application [com.adobe/DocumentServicesLicenseManager] returned result Messages for application "com.adobe/DocumentServicesLicenseManager" reported by JLinEE checks:
WARNINGS:
References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: adobe-DocumentServicesLicenseManager.ear, severity: warning
.#

#2.0
#2014 07 09 06:32:29:019#0-700#Warning#com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#
com.sap.ASJ.dpl_ds.003009#BC-CTS-CMS#sap.com/tc~SL~CMS~PCS#C000AC1D32BE004D0000000A00001408#3448650000000311##com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~PCS],5,Managed_Application_Thread]#Plain##
JLinEE validation of application [sap.com/tc~SL~CMS~PCS] returned result Messages for application "sap.com/tc~SL~CMS~PCS" reported by JLinEE checks:
WARNINGS:
EJB Model Builder: J2EE Security role sap.com/tc~SL~CMS~PCS*xml|sap.com~tc~SL~CMS~PCS~java.jar*xml|all included in a 'security-role-map' tag in the additional xml, doesn't contain corresponding 'server-role-name' sub tag (tags).[message resource bundle missing], file: sap.com~tc~SL~CMS~PCS~java.jar\#sap.com~tc~SL~CMS~PCS~java.jar, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "SCDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileUpload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Organizer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "OrganizerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Manager" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "ManagerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "delConfDB/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "recovery" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "rss/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
.#

#2.0
#2014 07 09 06:32:29:084#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE004B0000003900001408#3448650000000313##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesLicenseManager],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [com.adobe/DocumentServicesLicenseManager] finished with non-critical warnings for [992] ms on server process [3448650]: #

#2.0
#2014 07 09 06:32:29:084#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE004B0000003A00001408#3448650000000313##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesLicenseManager],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [com.adobe/DocumentServicesLicenseManager] finished with non-critical warnings for [992] ms on server process [3448650]: [
>>> Warnings <<<
1). References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: adobe-DocumentServicesLicenseManager.ear, severity: warning]#

#2.0
#2014 07 09 06:32:29:086#0-700#Warning#com.sap.engine.services.dc.gd.impl#
com.sap.ASJ.dpl_dc.005102#BC-JAS-DPL#tc~bl~deploy_controller#C000AC1D32BE004B0000003B00001408#3448650000000313##com.sap.engine.services.dc.gd.impl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_DocumentServicesLicenseManager],5,Managed_Application_Thread]#Plain##
[Server 00 00_34486] (21) :Deploy Service's deploy operation has finished with warnings. CSN component of deployment item is [BC-SRV-FP].
[
Warning occurred on server 3448650 during deploy of com.adobe/DocumentServicesLicenseManager : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: adobe-DocumentServicesLicenseManager.ear, severity: warning

CSN component of deployment item is BC-SRV-FP]#

#2.0
#2014 07 09 06:33:01:118#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-CTS-CMS#sap.com/tc~SL~CMS~PCS#C000AC1D32BE004D000000ED00001408#3448650000000311##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~PCS],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~SL~CMS~PCS] finished with non-critical warnings for [33044] ms on server process [3448650]: #

#2.0
#2014 07 09 06:33:01:118#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-CTS-CMS#sap.com/tc~SL~CMS~PCS#C000AC1D32BE004D000000EE00001408#3448650000000311##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~PCS],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [sap.com/tc~SL~CMS~PCS] finished with non-critical warnings for [33044] ms on server process [3448650]: [
>>> Warnings <<<
1). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Manager" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
2). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileUpload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
3). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "ManagerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
4). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "SCDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
5). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "rss/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
6). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "delConfDB/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
7). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Organizer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
8). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "OrganizerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
9). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning
10). EJB Model Builder: J2EE Security role sap.com/tc~SL~CMS~PCS*xml|sap.com~tc~SL~CMS~PCS~java.jar*xml|all included in a 'security-role-map' tag in the additional xml, doesn't contain corresponding 'server-role-name' sub tag (tags).[message resource bundle missing], file: sap.com~tc~SL~CMS~PCS~java.jar\#sap.com~tc~SL~CMS~PCS~java.jar, severity: warning
11). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "recovery" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning
12). Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning]#

#2.0
#2014 07 09 06:33:01:120#0-700#Warning#com.sap.engine.services.dc.gd.impl#
com.sap.ASJ.dpl_dc.005102#BC-JAS-DPL#tc~bl~deploy_controller#C000AC1D32BE004D000000EF00001408#3448650000000311##com.sap.engine.services.dc.gd.impl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[sap.com_tc~SL~CMS~PCS],5,Managed_Application_Thread]#Plain##
[Server 00 00_34486] (21) :Deploy Service's deploy operation has finished with warnings. CSN component of deployment item is [BC-CTS-CMS].
[
Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Manager" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileUpload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "ManagerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "SCDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "rss/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "delConfDB/index.xml" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "Organizer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "OrganizerAuth" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "FileDownload" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~download.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : EJB Model Builder: J2EE Security role sap.com/tc~SL~CMS~PCS*xml|sap.com~tc~SL~CMS~PCS~java.jar*xml|all included in a 'security-role-map' tag in the additional xml, doesn't contain corresponding 'server-role-name' sub tag (tags).[message resource bundle missing], file: sap.com~tc~SL~CMS~PCS~java.jar\#sap.com~tc~SL~CMS~PCS~java.jar, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "recovery" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

Warning occurred on server 3448650 during deploy of sap.com/tc~SL~CMS~PCS : Mapping Test: com.sap.ASJ.webjlin.000026 Invalid value "LogViewer" in <url-pattern> tag. For consistency with the Servlet API, use absolute paths (e.g. starting with "/")., file: sap.com~tc~SL~CMS~PCS~web.war\#WEB-INF/web.xml, severity: warning

CSN component of deployment item is BC-CTS-CMS]#

#2.0
#2014 07 09 06:33:07:501#0-700#Warning#com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#
com.sap.ASJ.dpl_ds.003009#BC-SRV-FP#com.adobe/AdobeDocumentServices#C000AC1D32BE00540000000600001408#3448650000000496##com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_AdobeDocumentServices],5,Managed_Application_Thread]#Plain##
JLinEE validation of application [com.adobe/AdobeDocumentServices] returned result Messages for application "com.adobe/AdobeDocumentServices" reported by JLinEE checks:
WARNINGS:
References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: AdobeDocumentServices.ear, severity: warning
.#

#2.0
#2014 07 09 06:33:24:981#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-FP#com.adobe/AdobeDocumentServices#C000AC1D32BE0054000000DB00001408#3448650000000496##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_AdobeDocumentServices],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [com.adobe/AdobeDocumentServices] finished with non-critical warnings for [18834] ms on server process [3448650]: #

#2.0
#2014 07 09 06:33:24:982#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-FP#com.adobe/AdobeDocumentServices#C000AC1D32BE0054000000DC00001408#3448650000000496##com.sap.engine.services.deploy.server.TransactionManager#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_AdobeDocumentServices],5,Managed_Application_Thread]#Plain##
Global [deploy] operation of application [com.adobe/AdobeDocumentServices] finished with non-critical warnings for [18834] ms on server process [3448650]: [
>>> Warnings <<<
1). References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: AdobeDocumentServices.ear, severity: warning]#

#2.0
#2014 07 09 06:33:24:983#0-700#Warning#com.sap.engine.services.dc.gd.impl#
com.sap.ASJ.dpl_dc.005102#BC-JAS-DPL#tc~bl~deploy_controller#C000AC1D32BE0054000000DD00001408#3448650000000496##com.sap.engine.services.dc.gd.impl#Administrator#0##4F0315D2076D11E4A00B000000349F4A#4f0315d2076d11e4a00b000000349f4a#4f0315d2076d11e4a00b000000349f4a#0#Thread[DeployThread[com.adobe_AdobeDocumentServices],5,Managed_Application_Thread]#Plain##
[Server 00 00_34486] (21) :Deploy Service's deploy operation has finished with warnings. CSN component of deployment item is [BC-SRV-FP].
[
Warning occurred on server 3448650 during deploy of com.adobe/AdobeDocumentServices : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [com.adobe/LicenseService] (described in the META-INF/application-j2ee-engine.xml), file: AdobeDocumentServices.ear, severity: warning

CSN component of deployment item is BC-SRV-FP]#

#2.0
#2014 07 09 06:33:47:770#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00160000000E00001408#3448650000000102##com.sap.engine.core.service630.container.ContainerObjectRegistry#####a0a8a630076d11e48a16000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 06:33:47:773#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE001D0000000C00001408#3448650000000094##com.sap.engine.core.service630.container.ServiceWrapper#####a0a8a630076d11e48a16000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 06:33:47:779#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000500001408#3448650000000104##com.sap.engine.core.service630.container.ContainerObjectRegistry#####a0a8a630076d11e48a16000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 06:33:47:963#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00650000000000001408#3448650000001666##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###3f0509f0076d11e4837e00155d336301##0#Application [12]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 06:33:47:963#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00660000000100001408#3448650000001637##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###3f0509f0076d11e4837e00155d336301##0#Application [6]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 06:33:51:083#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00690000000000001408#3448650000001581##com.sap.engine.core.service630.container.ServiceWrapper#####a0a8a630076d11e48a16000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 06:33:51:086#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00640000000100001408#3448650000001564##com.sap.engine.core.service630.container.ServiceWrapper#####a0a8a630076d11e48a16000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 06:33:51:373#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006C0000000100001408#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3f0509f0076d11e4837e00155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 09 06:33:51:373#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006C0000000200001408#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3f0509f0076d11e4837e00155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:33:51:374#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006D0000000100001408#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3f0509f0076d11e4837e00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 09 06:33:51:374#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006D0000000200001408#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3f0509f0076d11e4837e00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:33:54:709#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE000E0000000B00001408#3448650000001651##com.sap.engine.services.wsrm#####3f0509f0076d11e4837e00155d336301##0#System [22]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 06:33:55:217#0-700#Error#com.sap.esi.esp.service.server.SOABatchManipulatorImpl#
#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE006F0000000000001408#3448650000000330##com.sap.esi.esp.service.server.SOABatchManipulatorImpl#Administrator#0###4f0315d2076d11e4a00b000000349f4a##0#Application [29]#Plain##
sleep interrupted
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.esi.esp.service.server.SOABatchManipulatorImpl$PostServerStart.run(SOABatchManipulatorImpl.java:102)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 06:34:23:391#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000016A0###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDomainsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 06:34:31:487#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000001000016A0#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####beae32c9076d11e4853500155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:34:31:487#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000003000016A0#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####beae32c9076d11e4853500155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 06:34:37:821#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A00000002000016A0#3448650000000621##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####beae32c9076d11e4853500155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 06:34:42:657#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE000A00000006000016A0#3448650000001046##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 06:34:42:871#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE000500000001000016A0#3448650000001047##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 06:34:44:792#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000500000003000016A0#3448650000001210##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 06:34:48:915#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000008000016A0#3448650000001679##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 06:34:49:290#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000009000016A0#3448650000001679##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 06:34:51:101#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE001D00000001000016A0#3448650000001850##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 06:34:57:323#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000500000011000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [250] ms on server process [3448650]: #

#2.0
#2014 07 09 06:34:57:324#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000500000012000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [250] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:34:57:811#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-CTS-DI#sap.com/tc~di~nty~broker~ear#C000AC1D32BE00050000004F000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~di~nty~broker~ear] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:34:57:811#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-CTS-DI#sap.com/tc~di~nty~broker~ear#C000AC1D32BE000500000050000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~di~nty~broker~ear] finished with errors for [482] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:34:57:862#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000400000008000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [78] ms on server process [3448650]: #

#2.0
#2014 07 09 06:34:57:862#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000400000009000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [78] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 06:34:58:694#0-700#Error#com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl#
#BC-JAS-SEC#tc~sec~securestorage~service#C000AC1D32BE002500000000000016A0#3448650000000951#sap.com/tc~di~nty~broker~ear#com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(String objectID)#Guest#0##CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Application [49]#Plain##
Could not retrieve object NWDIAccess.
Root cause is:
[EXCEPTION]
com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID: sap~com~tc~di~nty~broker~ear
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:220)
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:707)
at com.sap.tc.di.nty.broker.secstore.SecureStore700.retrieve(SecureStore700.java:81)
at com.sap.tc.di.nty.broker.MutableConfiguration.getSecureStore(MutableConfiguration.java:135)
at com.sap.tc.di.nty.broker.MutableConfiguration.addSecureStoreData(MutableConfiguration.java:118)
at com.sap.tc.di.nty.broker.MutableConfiguration.readGlobalProperties(MutableConfiguration.java:48)
at com.sap.tc.di.nty.broker.MessageBrokerConfiguration.readConfiguration(MessageBrokerConfiguration.java:238)
at com.sap.tc.di.nty.broker.MessageBrokerConfiguration.getInstance(MessageBrokerConfiguration.java:108)
at com.sap.tc.di.nty.broker.web.ShowConfigServlet.init(ShowConfigServlet.java:62)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:513)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 06:34:58:721#0-700#Error#com.sap.security.core.server.securestorage.remote.RemoteSecureStorageAdministratorContextImpl#
#BC-JAS-SEC#tc~sec~securestorage~service#C000AC1D32BE002500000001000016A0#3448650000000951#sap.com/tc~di~nty~broker~ear#com.sap.security.core.server.securestorage.remote.RemoteSecureStorageAdministratorContextImpl#Guest#0##CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Application [49]#Plain##
Could not delete object NWDIAccess of client 2 sap~com~tc~di~nty~broker~ear
[EXCEPTION]
com.sap.engine.frame.core.configuration.NameNotFoundException: Configuration [sap~com~tc~di~nty~broker~ear] not found in [securestorage/webapps]
at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(ConfigurationDataCacheAllImpl.java:102)
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:916)
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:885)
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageAdministratorContextImpl.deleteObject(RemoteSecureStorageAdministratorContextImpl.java:196)
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.deleteObject(RemoteSecureStorageClientContextImpl.java:636)
at com.sap.tc.di.nty.broker.secstore.SecureStore700.store(SecureStore700.java:165)
at com.sap.tc.di.nty.broker.MutableConfiguration.getSecureStore(MutableConfiguration.java:141)
at com.sap.tc.di.nty.broker.MutableConfiguration.addSecureStoreData(MutableConfiguration.java:118)
at com.sap.tc.di.nty.broker.MutableConfiguration.readGlobalProperties(MutableConfiguration.java:48)
at com.sap.tc.di.nty.broker.MessageBrokerConfiguration.readConfiguration(MessageBrokerConfiguration.java:238)
at com.sap.tc.di.nty.broker.MessageBrokerConfiguration.getInstance(MessageBrokerConfiguration.java:108)
at com.sap.tc.di.nty.broker.web.ShowConfigServlet.init(ShowConfigServlet.java:62)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:513)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)


#

#2.0
#2014 07 09 06:34:59:242#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-CTS-CBS#sap.com/tc.CBS.Appl#C000AC1D32BE002700000038000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc.CBS.Appl] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:34:59:243#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-CTS-CBS#sap.com/tc.CBS.Appl#C000AC1D32BE002700000039000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc.CBS.Appl] finished with errors for [754] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:35:02:261#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00040000000B000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [254] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:02:261#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00040000000C000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [254] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 06:35:03:960#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-CTS-CMS#sap.com/tc~SL~CMS~cvers~proxy#C000AC1D32BE001C00000020000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~cvers~proxy] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:35:03:960#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-CTS-CMS#sap.com/tc~SL~CMS~cvers~proxy#C000AC1D32BE001C00000021000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~cvers~proxy] finished with errors for [8297] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:35:04:573#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000005A000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1451] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:04:573#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000005B000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1451] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 06:35:05:522#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE000B00000033000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [com.adobe/DocumentServicesLicenseManager] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:35:05:523#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE000B00000034000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [com.adobe/DocumentServicesLicenseManager] finished with errors for [9125] ms on server process [3448650] [
>>> without errors <<<] [
>>> Warnings <<<
1). Loader for reference: VM system loader of component: system:Frame not found!].#

#2.0
#2014 07 09 06:35:06:024#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE000B00000036000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [com.adobe/DocumentServicesLicenseManager] finished with non-critical warnings for [9629] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:06:025#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-FP#com.adobe/DocumentServicesLicenseManager#C000AC1D32BE000B00000037000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [com.adobe/DocumentServicesLicenseManager] finished with non-critical warnings for [9629] ms on server process [3448650]: [
>>> Warnings <<<
1).
Warning occurred on server 3448650 during startInitiallyApp of com.adobe/DocumentServicesLicenseManager : Loader for reference: VM system loader of component: system:Frame not found!]#

#2.0
#2014 07 09 06:35:06:846#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-SRV-FP#com.adobe/AdobeDocumentServices#C000AC1D32BE000B000000BE000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [com.adobe/AdobeDocumentServices] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:35:06:846#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-SRV-FP#com.adobe/AdobeDocumentServices#C000AC1D32BE000B000000BF000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [com.adobe/AdobeDocumentServices] finished with errors for [818] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:35:06:980#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE003300000002000016A0#3448650000001987#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Application [10]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 09 06:35:07:897#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00040000000E000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [52] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:07:897#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00040000000F000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [52] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 22d0fc44
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 06:35:08:307#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000400000011000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [53] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:08:308#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000400000012000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [53] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 6e2800ae
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 6e2800ae
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 06:35:09:881#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE003800000004000016A0#3448650000002179#com.adobe/AdobeDocumentServices#com.adobe.service.sap.licensing#Administrator#0##CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Application [50]#Plain##
A config entry with the name "DBMigrationVersion could not be found in the configuration "DocumentServicesLicense".

Stack Trace:
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "DBMigrationVersion could not be found in the configuration "DocumentServicesLicense".
at com.sap.engine.core.configuration.impl.ConfigurationData.modifyValueEntry(ConfigurationData.java:731)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:820)
at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.modifyConfigEntry(WriteAccessConfiguration.java:784)
at com.adobe.service.sap.licensing.LicenseService.mf__SetConfigurationValue(Unknown Source)
at com.adobe.service.sap.licensing.LicenseService.migrateDBTable(Unknown Source)
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.adobe.web.RegisterMBean.migrateLicenseDBTable(Unknown Source)
at com.adobe.web.RegisterMBean.init(Unknown Source)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 06:35:09:881#0-700#Error#com.adobe.service.sap.licensing#
#BC-SRV-FP#com.adobe~LicenseService#C000AC1D32BE003800000006000016A0#3448650000002179#com.adobe/AdobeDocumentServices#com.adobe.service.sap.licensing#Administrator#0##CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Application [50]#Plain##
A config entry with the name "DBMigrationVersion could not be found in the configuration "DocumentServicesLicense".#

#2.0
#2014 07 09 06:35:11:433#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE001C0000006A000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~xxxEar] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:35:11:433#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE001C0000006B000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~xxxEar] finished with errors for [5847] ms on server process [3448650] [
>>> without errors <<<] [
>>> Warnings <<<
1). Loader for reference: VM system loader of component: system:Frame not found!].#

#2.0
#2014 07 09 06:35:11:725#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE001C0000006D000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~SL~CMS~xxxEar] finished with non-critical warnings for [6140] ms on server process [3448650]: #

#2.0
#2014 07 09 06:35:11:725#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-CTS-CMS#sap.com/tc~SL~CMS~xxxEar#C000AC1D32BE001C0000006E000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~SL~CMS~xxxEar] finished with non-critical warnings for [6140] ms on server process [3448650]: [
>>> Warnings <<<
1).
Warning occurred on server 3448650 during startInitiallyApp of sap.com/tc~SL~CMS~xxxEar : Loader for reference: VM system loader of component: system:Frame not found!]#

#2.0
#2014 07 09 06:35:13:340#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-CTS-CMS#sap.com/tc~SL~CMS~PCS#C000AC1D32BE001C000000EA000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~PCS] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:35:13:340#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-CTS-CMS#sap.com/tc~SL~CMS~PCS#C000AC1D32BE001C000000EB000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~SL~CMS~PCS] finished with errors for [1608] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:36:44:888#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-SRV-FP#sap.com/tc~fp~adscall#C000AC1D32BE000B00000103000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~fp~adscall] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:36:44:900#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-SRV-FP#sap.com/tc~fp~adscall#C000AC1D32BE000B00000104000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~fp~adscall] finished with errors for [26196] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:36:57:700#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-SRV-FP#sap.com/tc~fp~parallelization#C000AC1D32BE000B0000014B000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~fp~parallelization] failed with errors on server process [3448650].#

#2.0
#2014 07 09 06:36:57:700#0-700#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-SRV-FP#sap.com/tc~fp~parallelization#C000AC1D32BE000B0000014C000016A0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####CDC99A0B076D11E4B6F4000000349F4A#cdc99a0b076d11e4b6f4000000349f4a#cdc99a0b076d11e4b6f4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startInitiallyApp] operation of application [sap.com/tc~fp~parallelization] finished with errors for [11131] ms on server process [3448650] [
>>> without errors <<<] [
>>> without warnings <<<].#

#2.0
#2014 07 09 06:49:54:576#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003F00000000000016A0#3448650000001679##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##BEAE32C9076D11E4853500155D336301#beae32c9076d11e4853500155d336301#beae32c9076d11e4853500155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 09 23:09:21:322#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004500000001000016A0#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [148] ms on server process [3448650]: #

#2.0
#2014 07 09 23:09:21:322#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004500000002000016A0#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [148] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:09:23:073#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE004500000004000016A0#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [134] ms on server process [3448650]: #

#2.0
#2014 07 09 23:09:23:074#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE004500000005000016A0#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [134] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:09:25:593#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE004D00000000000016A0#3448650000001790##com.sap.engine.core.service630.container.ServiceWrapper####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 23:09:25:871#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005400000001000016A0#3448650000001945##com.sap.engine.core.service630.container.ContainerObjectRegistry####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:09:25:871#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005300000001000016A0#3448650000001958##com.sap.engine.core.service630.container.ContainerObjectRegistry####BADC1B8A07F811E49A8F000000349F4A#badc1b8a07f811e49a8f000000349f4a#badc1b8a07f811e49a8f000000349f4a#0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:09:26:393#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003F00000002000016A0#3448650000001679##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###beae32c9076d11e4853500155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 23:09:26:395#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE005D00000001000016A0#3448650000001665##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###beae32c9076d11e4853500155d336301##0#Application [24]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 23:09:29:562#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005F00000004000016A0#3448650000004047##com.sap.engine.core.service630.container.ServiceWrapper#####badc1b8a07f811e49a8f000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 23:09:29:567#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE006000000000000016A0#3448650000004124##com.sap.engine.core.service630.container.ServiceWrapper#####badc1b8a07f811e49a8f000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 23:09:30:234#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006000000001000016A0#3448650000004239##com.sap.engine.core.service630.container.ContainerObjectRegistry#####badc1b8a07f811e49a8f000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:09:30:240#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE006200000000000016A0#3448650000004229##com.sap.engine.core.service630.container.ServiceWrapper#####badc1b8a07f811e49a8f000000349f4a##0#Service Stopper [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 09 23:09:30:263#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006300000001000016A0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####beae32c9076d11e4853500155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 09 23:09:30:263#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006400000001000016A0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####beae32c9076d11e4853500155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 09 23:09:30:264#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006400000002000016A0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####beae32c9076d11e4853500155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:09:30:264#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006300000002000016A0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####beae32c9076d11e4853500155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:09:34:957#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE000700000006000016A0#3448650000001638##com.sap.engine.services.wsrm#####beae32c9076d11e4853500155d336301##0#System [35]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:16:23:649#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001A14###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDomainsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 23:16:30:902#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000100001A14#3448650000000572##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####b8e14ecc07f911e4ad5b00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:16:30:903#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000300001A14#3448650000000572##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####b8e14ecc07f911e4ad5b00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:16:37:275#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE00020000000300001A14#3448650000000626##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####b8e14ecc07f911e4ad5b00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 23:16:43:182#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE00110000000100001A14#3448650000001039##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 23:16:44:906#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00120000000000001A14#3448650000001125##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 23:16:46:237#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000F0000000200001A14#3448650000001206##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 23:16:50:576#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00010000000B00001A14#3448650000001661##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 23:16:50:977#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00010000000C00001A14#3448650000001661##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 23:16:53:245#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000D0000000400001A14#3448650000001858##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####B8E14ECC07F911E4AD5B00155D336301#b8e14ecc07f911e4ad5b00155d336301#b8e14ecc07f911e4ad5b00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 23:16:59:391#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00050000000600001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [78] ms on server process [3448650]: #

#2.0
#2014 07 09 23:16:59:391#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00050000000700001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [78] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:16:59:664#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000100001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [35] ms on server process [3448650]: #

#2.0
#2014 07 09 23:16:59:664#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000200001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [35] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:17:01:609#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000D0000000600001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [121] ms on server process [3448650]: #

#2.0
#2014 07 09 23:17:01:609#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000D0000000700001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [121] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 23:17:02:633#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000000900001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [633] ms on server process [3448650]: #

#2.0
#2014 07 09 23:17:02:633#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000000A00001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [633] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 23:17:03:963#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00310000000200001A14#3448650000002041#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Application [49]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 09 23:17:04:820#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00050000000C00001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [23] ms on server process [3448650]: #

#2.0
#2014 07 09 23:17:04:820#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00050000000D00001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [23] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 5a01ae80
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:17:05:021#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00050000000F00001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [31] ms on server process [3448650]: #

#2.0
#2014 07 09 23:17:05:022#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00050000001000001A14#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####C961326907F911E4A0B2000000349F4A#c961326907f911e4a0b2000000349f4a#c961326907f911e4a0b2000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [31] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 518ddbee
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 518ddbee
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:18:47:303#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000B0000000800001A14#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [8] ms on server process [3448650]: #

#2.0
#2014 07 09 23:18:47:303#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000B0000000900001A14#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [8] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:18:47:431#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000B0000000B00001A14#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 09 23:18:47:431#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000B0000000C00001A14#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:18:48:110#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE001B0000000A00001A14#3448650000001811##com.sap.engine.core.service630.container.ContainerObjectRegistry####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:18:48:114#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00070000000900001A14#3448650000001841##com.sap.engine.core.service630.container.ContainerObjectRegistry####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:18:48:146#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00500000000000001A14#3448650000002036##com.sap.engine.core.service630.container.ServiceWrapper####0D1844DD07FA11E4C09E000000349F4A#0d1844dd07fa11e4c09e000000349f4a#0d1844dd07fa11e4c09e000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 23:18:48:267#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00540000000000001A14#3448650000001661##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###b8e14ecc07f911e4ad5b00155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 23:18:48:273#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00550000000100001A14#3448650000001646##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###b8e14ecc07f911e4ad5b00155d336301##0#Application [9]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 23:18:51:395#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00570000000100001A14#3448650000003543##com.sap.engine.core.service630.container.ServiceWrapper#####0d1844dd07fa11e4c09e000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 23:18:51:396#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE000B0000000D00001A14#3448650000003591##com.sap.engine.core.service630.container.ServiceWrapper#####0d1844dd07fa11e4c09e000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 23:18:51:524#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE000D0000000900001A14#3448650000003728##com.sap.engine.core.service630.container.ContainerObjectRegistry#####0d1844dd07fa11e4c09e000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:18:54:932#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE000A0000000400001A14#3448650000001633##com.sap.engine.services.wsrm#####b8e14ecc07f911e4ad5b00155d336301##0#System [21]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:25:55:946#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000117C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 23:26:09:101#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A000000020000117C#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####0e6e5c7907fb11e48d6400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:26:09:102#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A000000040000117C#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####0e6e5c7907fb11e48d6400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:26:16:477#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000B000000020000117C#3448650000000624##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####0e6e5c7907fb11e48d6400155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 23:26:20:923#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE0003000000020000117C#3448650000001050##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 23:26:20:998#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE0012000000000000117C#3448650000001052##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 23:26:23:532#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000A000000070000117C#3448650000001218##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 23:26:27:658#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0009000000050000117C#3448650000001680##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 23:26:27:979#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0009000000060000117C#3448650000001680##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 23:26:30:189#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE0003000000060000117C#3448650000001863##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 23:26:37:870#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0009000000090000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [52] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:37:871#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00090000000A0000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [52] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:26:38:389#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00140000001F0000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [202] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:38:389#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0014000000200000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [202] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:26:41:497#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE0012000000080000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [232] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:41:497#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE0012000000090000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [232] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 23:26:42:488#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0002000000040000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [970] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:42:488#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0002000000050000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [970] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 23:26:44:548#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002E000000020000117C#3448650000002095#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Application [48]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#


Former Member
0 Kudos

part 3

===============================================================

#2.0
#2014 07 09 23:26:44:711#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0002000000070000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [31] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:44:711#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0002000000080000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [31] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 62692b0b
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:26:45:253#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00020000000A0000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [77] ms on server process [3448650]: #

#2.0
#2014 07 09 23:26:45:253#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00020000000B0000117C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####2169763707FB11E4C451000000349F4A#2169763707fb11e4c451000000349f4a#2169763707fb11e4c451000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [77] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 392fd10d
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 392fd10d
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:41:33:707#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0038000000000000117C#3448650000001680##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##0E6E5C7907FB11E48D6400155D336301#0e6e5c7907fb11e48d6400155d336301#0e6e5c7907fb11e48d6400155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 09 23:41:33:902#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003A000000010000117C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [5] ms on server process [3448650]: #

#2.0
#2014 07 09 23:41:33:903#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003A000000020000117C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [5] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:41:34:017#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003B000000010000117C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 09 23:41:34:017#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003B000000020000117C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:41:34:671#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004F000000010000117C#3448650000001949##com.sap.engine.core.service630.container.ContainerObjectRegistry####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:41:34:681#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE0053000000000000117C#3448650000001934##com.sap.engine.core.service630.container.ServiceWrapper####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 23:41:34:694#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0045000000020000117C#3448650000001932##com.sap.engine.core.service630.container.ContainerObjectRegistry####3BAB167507FD11E4AC6F000000349F4A#3bab167507fd11e4ac6f000000349f4a#3bab167507fd11e4ac6f000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:41:34:832#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0038000000020000117C#3448650000001680##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###0e6e5c7907fb11e48d6400155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 23:41:34:892#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE005B000000010000117C#3448650000001665##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###0e6e5c7907fb11e48d6400155d336301##0#Application [33]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 23:41:37:956#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005C000000010000117C#3448650000003367##com.sap.engine.core.service630.container.ServiceWrapper#####3bab167507fd11e4ac6f000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 23:41:37:957#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE005D000000000000117C#3448650000003390##com.sap.engine.core.service630.container.ServiceWrapper#####3bab167507fd11e4ac6f000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 23:41:38:162#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005F000000000000117C#3448650000003549##com.sap.engine.core.service630.container.ContainerObjectRegistry#####3bab167507fd11e4ac6f000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:41:38:171#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE0060000000010000117C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####0e6e5c7907fb11e48d6400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 09 23:41:38:172#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE0060000000020000117C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####0e6e5c7907fb11e48d6400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:41:41:455#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE0011000000020000117C#3448650000001651##com.sap.engine.services.wsrm#####0e6e5c7907fb11e48d6400155d336301##0#System [33]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:43:24:304#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000404###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 23:43:30:103#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000C0000000100000404#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####7ed2564c07fd11e4a77a00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:43:30:104#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000C0000000300000404#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####7ed2564c07fd11e4a77a00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:43:34:759#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000B0000000200000404#3448650000000617##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####7ed2564c07fd11e4a77a00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 23:43:39:724#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE00140000000100000404#3448650000001002##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 23:43:40:838#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00150000000000000404#3448650000001066##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 23:43:43:530#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000C0000000600000404#3448650000001214##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 23:43:46:253#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000C0000000D00000404#3448650000001739##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 23:43:46:310#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000C0000000E00000404#3448650000001739##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 23:43:49:605#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00070000000500000404#3448650000001895##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####7ED2564C07FD11E4A77A00155D336301#7ed2564c07fd11e4a77a00155d336301#7ed2564c07fd11e4a77a00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 23:43:54:095#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00080000000600000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [13] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:54:096#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00080000000700000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [13] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:43:54:199#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00120000001400000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [31] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:54:200#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00120000001500000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [31] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:43:55:728#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE002D0000000100000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [55] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:55:730#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE002D0000000200000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [55] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 23:43:57:889#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002F0000000200000404#3448650000001994#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Application [47]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 09 23:43:57:959#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00120000001700000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1373] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:57:959#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00120000001800000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1373] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 23:43:58:334#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000C0000001200000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [21] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:58:335#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000C0000001300000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [21] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 1b1a24eb
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:43:58:431#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000C0000001500000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: #

#2.0
#2014 07 09 23:43:58:432#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000C0000001600000404#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####8CCACA6807FD11E4BEA4000000349F4A#8ccaca6807fd11e4bea4000000349f4a#8ccaca6807fd11e4bea4000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5de03e21
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5de03e21
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:48:36:126#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00070000000700000404#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [5] ms on server process [3448650]: #

#2.0
#2014 07 09 23:48:36:126#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00070000000800000404#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [5] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:48:36:268#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00380000000100000404#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [5] ms on server process [3448650]: #

#2.0
#2014 07 09 23:48:36:269#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00380000000200000404#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [5] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:48:36:763#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00180000000B00000404#3448650000001794##com.sap.engine.core.service630.container.ContainerObjectRegistry####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:48:36:834#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE004E0000000000000404#3448650000001926##com.sap.engine.core.service630.container.ServiceWrapper####375EA25D07FE11E4992B000000349F4A#375ea25d07fe11e4992b000000349f4a#375ea25d07fe11e4992b000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 23:48:36:905#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00500000000100000404#3448650000001998##com.sap.engine.core.service630.container.ContainerObjectRegistry#####375ea25d07fe11e4992b000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:48:36:964#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00530000000000000404#3448650000001739##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###7ed2564c07fd11e4a77a00155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 23:48:36:994#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00540000000100000404#3448650000001723##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###7ed2564c07fd11e4a77a00155d336301##0#Application [40]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 23:48:40:003#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00580000000000000404#3448650000003548##com.sap.engine.core.service630.container.ServiceWrapper#####375ea25d07fe11e4992b000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 23:48:40:004#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00570000000100000404#3448650000003517##com.sap.engine.core.service630.container.ServiceWrapper#####375ea25d07fe11e4992b000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 23:48:40:212#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE00520000000100000404#3448650000003704##com.sap.engine.core.service630.container.ServiceWrapper#####375ea25d07fe11e4992b000000349f4a##0#Event Processor [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 09 23:48:40:212#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00520000000200000404#3448650000003704##com.sap.engine.core.service630.container.ContainerObjectRegistry#####375ea25d07fe11e4992b000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:48:40:216#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE005A0000000100000404#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####7ed16a6407fd11e49c4d00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 09 23:48:40:217#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE005A0000000200000404#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####7ed16a6407fd11e49c4d00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:48:43:483#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE001A0000000500000404#3448650000001683##com.sap.engine.services.wsrm#####7ed2564c07fd11e4a77a00155d336301##0#System [31]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:49:22:703#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001304###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 09 23:49:29:012#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00090000000100001304#3448650000000566##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####5465a21b07fe11e49a8900155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:49:29:013#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00090000000300001304#3448650000000566##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####5465a21b07fe11e49a8900155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 09 23:49:33:959#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE00040000000400001304#3448650000000620##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####5465a21b07fe11e49a8900155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 09 23:49:38:593#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE00120000000100001304#3448650000001009##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 09 23:49:39:519#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00090000000400001304#3448650000001128##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 09 23:49:42:618#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00030000000200001304#3448650000001230##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 09 23:49:44:699#0-700#Error#com.adobe.service.logging.Logger#
#BC-SRV-FP#com.adobe~XMLFormService#C000AC1D32BE00010000000C00001304#3448650000001420##com.adobe.service.logging.Logger####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Service Runner [com.adobe~PDFManipulation]#Plain##
error getting ssl flag, using non-SSL mode: null#

#2.0
#2014 07 09 23:49:45:532#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000E0000001900001304#3448650000001731##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 09 23:49:45:621#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000E0000001A00001304#3448650000001731##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 09 23:49:47:944#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE001A0000000300001304#3448650000001909##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####5465A21B07FE11E49A8900155D336301#5465a21b07fe11e49a8900155d336301#5465a21b07fe11e49a8900155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 09 23:49:57:881#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00070000000600001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 09 23:49:57:881#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00070000000700001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:49:57:961#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000D00001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [56] ms on server process [3448650]: #

#2.0
#2014 07 09 23:49:57:961#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000E00001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [56] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:49:59:793#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00240000001000001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [92] ms on server process [3448650]: #

#2.0
#2014 07 09 23:49:59:793#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00240000001100001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [92] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 09 23:50:01:426#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00320000000100001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1421] ms on server process [3448650]: #

#2.0
#2014 07 09 23:50:01:426#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00320000000200001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1421] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 09 23:50:02:078#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00340000000200001304#3448650000001951#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Application [47]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 09 23:50:02:545#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00320000000400001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [18] ms on server process [3448650]: #

#2.0
#2014 07 09 23:50:02:545#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00320000000500001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [18] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 625b5f17
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:50:02:696#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00320000000700001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: #

#2.0
#2014 07 09 23:50:02:696#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00320000000800001304#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####626091D907FE11E4BF31000000349F4A#626091d907fe11e4bf31000000349f4a#626091d907fe11e4bf31000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5e8caf16
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5e8caf16
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 09 23:55:44:466#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00100000000300001304#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [6] ms on server process [3448650]: #

#2.0
#2014 07 09 23:55:44:466#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00100000000400001304#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [6] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:55:44:595#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00140000000400001304#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 09 23:55:44:595#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00140000000500001304#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 09 23:55:45:140#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00500000000000001304#3448650000001872##com.sap.engine.core.service630.container.ServiceWrapper####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 09 23:55:45:206#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00550000000100001304#3448650000001855##com.sap.engine.core.service630.container.ContainerObjectRegistry####36AE53E307FF11E49688000000349F4A#36ae53e307ff11e49688000000349f4a#36ae53e307ff11e49688000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:55:45:282#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00620000000100001304#3448650000001912##com.sap.engine.core.service630.container.ContainerObjectRegistry#####36ae53e307ff11e49688000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:55:45:286#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00630000000000001304#3448650000001731##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###5465a21b07fe11e49a8900155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 09 23:55:45:290#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00640000000100001304#3448650000001711##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###5465a21b07fe11e49a8900155d336301##0#Application [39]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 09 23:55:48:360#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00440000000100001304#3448650000003620##com.sap.engine.core.service630.container.ServiceWrapper#####36ae53e307ff11e49688000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 09 23:55:48:370#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00670000000100001304#3448650000003682##com.sap.engine.core.service630.container.ServiceWrapper#####36ae53e307ff11e49688000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 09 23:55:48:582#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE00690000000000001304#3448650000003807##com.sap.engine.core.service630.container.ServiceWrapper#####36ae53e307ff11e49688000000349f4a##0#Event Processor [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 09 23:55:48:583#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00690000000100001304#3448650000003807##com.sap.engine.core.service630.container.ContainerObjectRegistry#####36ae53e307ff11e49688000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 09 23:55:48:588#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006A0000000100001304#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####5465a21b07fe11e49a8900155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 09 23:55:48:589#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006A0000000200001304#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####5465a21b07fe11e49a8900155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 09 23:55:51:872#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE00080000000200001304#3448650000001697##com.sap.engine.services.wsrm#####5465a21b07fe11e49a8900155d336301##0#System [37]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:01:41:863#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000008F0###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 00:01:47:301#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000900000001000008F0#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####0cf1616e080011e4bdab00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:01:47:302#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000900000003000008F0#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####0cf1616e080011e4bdab00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:01:51:898#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000100000003000008F0#3448650000000621##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####0cf1616e080011e4bdab00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 00:01:58:390#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE001300000001000008F0#3448650000001067##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 00:01:58:975#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE001700000001000008F0#3448650000001272##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 00:01:59:137#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE001100000001000008F0#3448650000001274##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 00:02:02:102#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001900000001000008F0#3448650000001819##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 00:02:02:159#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001900000002000008F0#3448650000001819##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 00:02:05:017#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE001100000008000008F0#3448650000001962##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####0CF1616E080011E4BDAB00155D336301#0cf1616e080011e4bdab00155d336301#0cf1616e080011e4bdab00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 00:02:09:597#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE002100000001000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [66] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:09:597#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE002100000002000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [66] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:02:09:609#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001A00000008000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [23] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:09:609#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001A00000009000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [23] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:02:11:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001A0000000B000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [39] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:11:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001A0000000C000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [39] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 00:02:11:832#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001200000009000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [435] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:11:832#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00120000000A000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [435] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 00:02:13:471#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002F00000002000008F0#3448650000002034#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Application [50]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 00:02:13:867#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00120000000C000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [16] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:13:867#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00120000000D000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [16] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 29c7eb53
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:02:14:004#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00120000000F000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [23] ms on server process [3448650]: #

#2.0
#2014 07 10 00:02:14:004#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001200000010000008F0#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####19B4DE80080011E49623000000349F4A#19b4de80080011e49623000000349f4a#19b4de80080011e49623000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [23] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 55281d4e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 55281d4e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

Former Member
0 Kudos

part 4

======================================================================

#2.0
#2014 07 10 00:09:51:831#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003B00000001000008F0#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####2FC1A15C080111E4C9DB000000349F4A#2fc1a15c080111e4c9db000000349f4a#2fc1a15c080111e4c9db000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 10 00:09:51:831#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003B00000002000008F0#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####2FC1A15C080111E4C9DB000000349F4A#2fc1a15c080111e4c9db000000349f4a#2fc1a15c080111e4c9db000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:09:51:960#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001B00000004000008F0#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####2FC1A15C080111E4C9DB000000349F4A#2fc1a15c080111e4c9db000000349f4a#2fc1a15c080111e4c9db000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 10 00:09:51:960#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001B00000005000008F0#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####2FC1A15C080111E4C9DB000000349F4A#2fc1a15c080111e4c9db000000349f4a#2fc1a15c080111e4c9db000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:09:52:558#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005600000001000008F0#3448650000001824##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:09:52:652#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE005D00000000000008F0#3448650000001948##com.sap.engine.core.service630.container.ServiceWrapper#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 10 00:09:52:684#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006000000001000008F0#3448650000001917##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:09:52:696#0-700#Error#com.sap.engine.messaging.impl.core.status.SystemMatrixImpl#
#BC-XI-CON-MSG#com.sap.aii.af.ms.svc#C000AC1D32BE006100000000000008F0#3448650000003430##com.sap.engine.messaging.impl.core.status.SystemMatrixImpl.update(String sourceClass, String errorCode, String errorText, String errorCategory, String connectionName, Throwable cause)#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [tc~esi~esp~wsrm~srv]#Plain##
Exception during MS event processing: java.util.ConcurrentModificationException. Alert might not be triggered! Event was raised for: com.sap.engine.messaging.runtime.MessagingSystem, MS.PROTOCOL.REGISTRATION, Successfully unregister EventHandler for protocol WS-RM., 0, <null>#

#2.0
#2014 07 10 00:09:52:711#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE006200000000000008F0#3448650000001819##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###0cf1616e080011e4bdab00155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 10 00:09:52:722#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE006300000001000008F0#3448650000001804##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###0cf1616e080011e4bdab00155d336301##0#Application [11]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 10 00:09:55:784#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00540000000D000008F0#3448650000003577##com.sap.engine.core.service630.container.ServiceWrapper#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 10 00:09:55:795#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE006500000000000008F0#3448650000003600##com.sap.engine.core.service630.container.ServiceWrapper#####2fc1a15c080111e4c9db000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 10 00:09:56:011#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006900000000000008F0#3448650000003763##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2fc1a15c080111e4c9db000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:09:56:019#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006A00000001000008F0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####0cf1616e080011e4bdab00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 10 00:09:56:019#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006A00000002000008F0#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####0cf1616e080011e4bdab00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:09:59:301#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE000D00000003000008F0#3448650000001750##com.sap.engine.services.wsrm#####0cf1616e080011e4bdab00155d336301##0#System [27]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:14:37:044#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000AB4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 00:14:47:410#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000100000AB4#3448650000000565##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####dafd5ae8080111e49ec400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:14:47:410#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000300000AB4#3448650000000565##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####dafd5ae8080111e49ec400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:14:53:387#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE00090000000200000AB4#3448650000000619##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####dafd5ae8080111e49ec400155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 00:14:58:652#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE00110000000100000AB4#3448650000001017##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 00:14:59:770#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00120000000000000AB4#3448650000001073##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 00:15:01:578#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000F0000000300000AB4#3448650000001220##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 00:15:04:652#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00170000000D00000AB4#3448650000001744##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 00:15:04:710#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00170000000E00000AB4#3448650000001744##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 00:15:07:151#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00110000000400000AB4#3448650000001900##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DAFD5AE8080111E49EC400155D336301#dafd5ae8080111e49ec400155d336301#dafd5ae8080111e49ec400155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 00:15:12:562#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000A0000000600000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [41] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:12:562#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000A0000000700000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [41] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:15:12:761#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00120000000600000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [27] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:12:761#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00120000000700000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [27] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:15:14:642#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00310000000100000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [175] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:14:642#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00310000000200000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [175] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 00:15:15:444#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00170000001E00000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [785] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:15:444#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00170000001F00000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [785] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 00:15:16:434#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00330000000200000AB4#3448650000001951#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Application [48]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 00:15:17:029#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00120000000900000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:17:030#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00120000000A00000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 70f6f694
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:15:17:155#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00120000000C00000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [36] ms on server process [3448650]: #

#2.0
#2014 07 10 00:15:17:156#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00120000000D00000AB4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EBE71DFD080111E488A8000000349F4A#ebe71dfd080111e488a8000000349f4a#ebe71dfd080111e488a8000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [36] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 42b8aa3f
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 42b8aa3f
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:19:13:669#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000E0000000200000AB4#3448650000000014##com.sap.engine.services.deploy.server.TransactionManager####7EA09C05080211E4CDA2000000349F4A#7ea09c05080211e4cda2000000349f4a#7ea09c05080211e4cda2000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 10 00:19:13:670#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000E0000000300000AB4#3448650000000014##com.sap.engine.services.deploy.server.TransactionManager####7EA09C05080211E4CDA2000000349F4A#7ea09c05080211e4cda2000000349f4a#7ea09c05080211e4cda2000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:19:13:791#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00040000000D00000AB4#3448650000000014##com.sap.engine.services.deploy.server.TransactionManager####7EA09C05080211E4CDA2000000349F4A#7ea09c05080211e4cda2000000349f4a#7ea09c05080211e4cda2000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [5] ms on server process [3448650]: #

#2.0
#2014 07 10 00:19:13:791#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00040000000E00000AB4#3448650000000014##com.sap.engine.services.deploy.server.TransactionManager####7EA09C05080211E4CDA2000000349F4A#7ea09c05080211e4cda2000000349f4a#7ea09c05080211e4cda2000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [5] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:19:14:362#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00590000000000000AB4#3448650000002298##com.sap.engine.core.service630.container.ServiceWrapper#####7ea09c05080211e4cda2000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 10 00:19:14:421#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005F0000000100000AB4#3448650000002236##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7ea09c05080211e4cda2000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:19:14:423#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004D0000000200000AB4#3448650000002403##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7ea09c05080211e4cda2000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:19:14:462#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00610000000000000AB4#3448650000001744##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###dafd5ae8080111e49ec400155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 10 00:19:14:488#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00620000000100000AB4#3448650000001728##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###dafd5ae8080111e49ec400155d336301##0#Application [36]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 10 00:19:17:490#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE000A0000000800000AB4#3448650000003908##com.sap.engine.core.service630.container.ServiceWrapper#####7ea09c05080211e4cda2000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 10 00:19:17:495#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00110000000500000AB4#3448650000003890##com.sap.engine.core.service630.container.ServiceWrapper#####7ea09c05080211e4cda2000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 10 00:19:17:697#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00640000000000000AB4#3448650000004074##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7ea09c05080211e4cda2000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:19:17:701#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE00650000000100000AB4#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####dafd5ae8080111e49ec400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 10 00:19:17:702#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE00650000000200000AB4#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####dafd5ae8080111e49ec400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:19:20:991#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE000C0000000400000AB4#3448650000001688##com.sap.engine.services.wsrm#####dafd5ae8080111e49ec400155d336301##0#System [14]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:20:04:740#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001794###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 00:20:10:381#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000100001794#3448650000000572##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####9e19459e080211e4981300155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:20:10:381#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000300001794#3448650000000572##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####9e19459e080211e4981300155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:20:14:850#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A0000000200001794#3448650000000626##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####9e19459e080211e4981300155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 00:20:19:270#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE00090000000300001794#3448650000001168##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 00:20:19:386#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00140000000000001794#3448650000001169##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 00:20:23:104#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00170000000100001794#3448650000001268##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 00:20:24:695#0-700#Error#com.adobe.service.logging.Logger#
#BC-SRV-FP#com.adobe~DocumentServicesLicenseSupportService#C000AC1D32BE001C0000000700001794#3448650000001461##com.adobe.service.logging.Logger####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Service Runner [com.adobe~PDFManipulation]#Plain##
error getting ssl flag, using non-SSL mode: null#

#2.0
#2014 07 10 00:20:26:243#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00170000000200001794#3448650000001766##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 00:20:26:301#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00170000000300001794#3448650000001766##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 00:20:28:450#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE001B0000000300001794#3448650000001949##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####9E19459E080211E4981300155D336301#9e19459e080211e4981300155d336301#9e19459e080211e4981300155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 00:20:33:319#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00190000000600001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [34] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:33:319#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00190000000700001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [34] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:20:33:336#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00190000000900001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [14] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:33:336#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00190000000A00001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [14] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:20:35:089#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000E0000001000001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [50] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:35:089#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000E0000001100001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [50] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 00:20:36:070#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000E0000001300001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [536] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:36:070#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000E0000001400001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [536] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 00:20:37:362#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002F0000000200001794#3448650000002042#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Application [46]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 00:20:37:832#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE001A0000001500001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [15] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:37:833#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE001A0000001600001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [15] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 7cd8041a
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:20:37:966#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001A0000001800001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: #

#2.0
#2014 07 10 00:20:37:967#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001A0000001900001794#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####AB66BFB9080211E4B984000000349F4A#ab66bfb9080211e4b984000000349f4a#ab66bfb9080211e4b984000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5b531130
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5b531130
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:26:10:564#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003C0000000100001794#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####7720435D080311E48482000000349F4A#7720435d080311e48482000000349f4a#7720435d080311e48482000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 10 00:26:10:564#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003C0000000200001794#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####7720435D080311E48482000000349F4A#7720435d080311e48482000000349f4a#7720435d080311e48482000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:26:10:709#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003D0000000100001794#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####7720435D080311E48482000000349F4A#7720435d080311e48482000000349f4a#7720435d080311e48482000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 10 00:26:10:709#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003D0000000200001794#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####7720435D080311E48482000000349F4A#7720435d080311e48482000000349f4a#7720435d080311e48482000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:26:11:286#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00550000000100001794#3448650000001817##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7720435d080311e48482000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:26:11:327#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00580000000000001794#3448650000001985##com.sap.engine.core.service630.container.ServiceWrapper#####7720435d080311e48482000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 10 00:26:11:346#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00590000000100001794#3448650000001955##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7720435d080311e48482000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:26:11:375#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE005C0000000000001794#3448650000001766##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###9e19459e080211e4981300155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 10 00:26:11:377#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE005D0000000100001794#3448650000001751##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###9e19459e080211e4981300155d336301##0#Application [31]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 10 00:26:14:369#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005E0000000100001794#3448650000003591##com.sap.engine.core.service630.container.ServiceWrapper#####7720435d080311e48482000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 10 00:26:14:373#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE005F0000000000001794#3448650000003633##com.sap.engine.core.service630.container.ServiceWrapper#####7720435d080311e48482000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 10 00:26:14:585#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00620000000000001794#3448650000003777##com.sap.engine.core.service630.container.ContainerObjectRegistry#####7720435d080311e48482000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 00:26:14:585#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE00630000000000001794#3448650000003771##com.sap.engine.core.service630.container.ServiceWrapper#####7720435d080311e48482000000349f4a##0#Service Stopper [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 10 00:26:14:590#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE00640000000100001794#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####9e19459e080211e4981300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 10 00:26:14:590#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE00640000000200001794#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####9e19459e080211e4981300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:26:17:860#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE00180000000400001794#3448650000001737##com.sap.engine.services.wsrm#####9e19459e080211e4981300155d336301##0#System [27]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 00:26:39:973#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000754###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 00:26:45:653#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00070000000200000754#3448650000000566##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####89f68bd5080311e4c12b00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:26:45:653#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00070000000400000754#3448650000000566##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####89f68bd5080311e4c12b00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:26:50:526#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE00090000000200000754#3448650000000620##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####89f68bd5080311e4c12b00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 00:26:55:275#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE00030000000300000754#3448650000001062##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 00:26:55:613#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00110000000000000754#3448650000001063##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 00:26:57:933#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000A0000000300000754#3448650000001205##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 00:27:00:385#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001D0000000000000754#3448650000001697##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 00:27:00:449#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001D0000000100000754#3448650000001697##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 00:27:03:571#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00120000000700000754#3448650000001883##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####89F68BD5080311E4C12B00155D336301#89f68bd5080311e4c12b00155d336301#89f68bd5080311e4c12b00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 00:27:08:396#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00230000000100000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [17] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:08:396#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00230000000200000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [17] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:27:08:576#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000100000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [118] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:08:576#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00240000000200000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [118] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:27:11:159#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00230000000400000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [480] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:11:159#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00230000000500000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [480] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 00:27:11:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000B0000000E00000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [48] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:11:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000B0000000F00000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [48] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 00:27:12:840#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00320000000200000754#3448650000001966#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Application [40]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 00:27:13:412#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000B0000001100000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [207] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:13:412#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000B0000001200000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [207] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 230f0031
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:27:13:544#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000B0000001400000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [19] ms on server process [3448650]: #

#2.0
#2014 07 10 00:27:13:544#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000B0000001500000754#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####96EAEAEB080311E4CF59000000349F4A#96eaeaeb080311e4cf59000000349f4a#96eaeaeb080311e4cf59000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [19] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 4c9d7a2e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 4c9d7a2e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:36:06:806#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000013A4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 00:36:24:567#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000001000013A4#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####de072285080411e4859600155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:36:24:568#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000003000013A4#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####de072285080411e4859600155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 00:36:31:657#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A00000002000013A4#3448650000000624##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####de072285080411e4859600155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 00:36:37:178#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000100000002000013A4#3448650000001116##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 00:36:37:328#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE000400000002000013A4#3448650000001117##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 00:36:39:207#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000600000005000013A4#3448650000001228##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 00:36:43:903#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000004000013A4#3448650000001696##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 00:36:44:352#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000005000013A4#3448650000001696##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 00:36:46:705#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000700000006000013A4#3448650000001879##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 00:36:55:665#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000100000007000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [93] ms on server process [3448650]: #

#2.0
#2014 07 10 00:36:55:666#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000100000008000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [93] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:36:56:086#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000800000005000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [156] ms on server process [3448650]: #

#2.0
#2014 07 10 00:36:56:086#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000800000006000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [156] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 00:36:59:714#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00010000000A000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [486] ms on server process [3448650]: #

#2.0
#2014 07 10 00:36:59:714#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00010000000B000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [486] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 00:37:00:115#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000800000008000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [846] ms on server process [3448650]: #

#2.0
#2014 07 10 00:37:00:115#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000800000009000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [846] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 00:37:01:882#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE003100000002000013A4#3448650000001991#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Application [47]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 00:37:02:662#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000D00000005000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 10 00:37:02:663#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000D00000006000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 62a86375
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:37:02:951#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000D00000008000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [55] ms on server process [3448650]: #

#2.0
#2014 07 10 00:37:02:951#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE000D00000009000013A4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####F329451F080411E4A17A000000349F4A#f329451f080411e4a17a000000349f4a#f329451f080411e4a17a000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [55] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 3226fb4d
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 3226fb4d
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 00:51:48:855#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003C00000000000013A4#3448650000001696##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##DE072285080411E4859600155D336301#de072285080411e4859600155d336301#de072285080411e4859600155d336301#0#Application [6]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 10 01:48:32:490#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004100000001000013A4#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####F89EA525080E11E49FF2000000349F4A#f89ea525080e11e49ff2000000349f4a#f89ea525080e11e49ff2000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 10 01:48:32:498#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004100000002000013A4#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####F89EA525080E11E49FF2000000349F4A#f89ea525080e11e49ff2000000349f4a#f89ea525080e11e49ff2000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 01:48:33:298#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001E00000005000013A4#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####F89EA525080E11E49FF2000000349F4A#f89ea525080e11e49ff2000000349f4a#f89ea525080e11e49ff2000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 10 01:48:33:298#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001E00000006000013A4#3448650000000007##com.sap.engine.services.deploy.server.TransactionManager####F89EA525080E11E49FF2000000349F4A#f89ea525080e11e49ff2000000349f4a#f89ea525080e11e49ff2000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 01:48:33:915#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005500000001000013A4#3448650000001903##com.sap.engine.core.service630.container.ContainerObjectRegistry####F89EA525080E11E49FF2000000349F4A#f89ea525080e11e49ff2000000349f4a#f89ea525080e11e49ff2000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 01:48:33:975#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006100000001000013A4#3448650000001958##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f89ea525080e11e49ff2000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 01:48:33:977#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE006200000000000013A4#3448650000001927##com.sap.engine.core.service630.container.ServiceWrapper#####f89ea525080e11e49ff2000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 10 01:48:34:075#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003C00000002000013A4#3448650000001696##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###de072285080411e4859600155d336301##0#Application [6]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 10 01:48:34:077#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE006400000001000013A4#3448650000001681##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###de072285080411e4859600155d336301##0#Application [44]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:218)

#

#2.0
#2014 07 10 01:48:37:189#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE006700000000000013A4#3448650000003374##com.sap.engine.core.service630.container.ServiceWrapper#####f89ea525080e11e49ff2000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 10 01:48:37:190#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE006600000001000013A4#3448650000003357##com.sap.engine.core.service630.container.ServiceWrapper#####f89ea525080e11e49ff2000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 10 01:48:37:468#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE006900000000000013A4#3448650000003542##com.sap.engine.core.service630.container.ServiceWrapper#####f89ea525080e11e49ff2000000349f4a##0#Event Processor [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 10 01:48:37:468#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006900000001000013A4#3448650000003542##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f89ea525080e11e49ff2000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 01:48:37:479#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006A00000001000013A4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####de072285080411e4859600155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 10 01:48:37:479#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006A00000002000013A4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####de072285080411e4859600155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 01:48:40:852#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE001000000003000013A4#3448650000001667##com.sap.engine.services.wsrm#####de072285080411e4859600155d336301##0#System [42]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 01:53:14:748#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000011BC###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 01:53:29:291#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000001000011BC#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####a2c9042d080f11e4873200155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 01:53:29:291#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B00000003000011BC#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####a2c9042d080f11e4873200155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 01:53:36:059#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A00000002000011BC#3448650000000624##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####a2c9042d080f11e4873200155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 01:53:41:447#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000300000003000011BC#3448650000001045##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 01:53:41:507#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE001500000000000011BC#3448650000001046##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 01:53:43:826#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE001A00000001000011BC#3448650000001217##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 01:53:47:805#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000005000011BC#3448650000001698##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 01:53:48:267#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000100000006000011BC#3448650000001698##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 01:53:50:409#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000B00000009000011BC#3448650000001869##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 01:53:57:762#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001000000005000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [142] ms on server process [3448650]: #

#2.0
#2014 07 10 01:53:57:762#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001000000006000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [142] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 01:53:58:137#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000A00000006000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [116] ms on server process [3448650]: #

#2.0
#2014 07 10 01:53:58:137#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000A00000007000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [116] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 01:54:01:828#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001700000011000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [420] ms on server process [3448650]: #

#2.0
#2014 07 10 01:54:01:829#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001700000012000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [420] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 01:54:02:160#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000A00000009000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1002] ms on server process [3448650]: #

#2.0
#2014 07 10 01:54:02:160#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000A0000000A000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1002] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 01:54:03:875#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE003400000002000011BC#3448650000001981#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Application [49]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 01:54:04:624#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000A0000000C000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 10 01:54:04:624#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE000A0000000D000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 784425c
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 01:54:04:916#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001700000014000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [57] ms on server process [3448650]: #

#2.0
#2014 07 10 01:54:04:916#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001700000015000011BC#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B6798940080F11E49C63000000349F4A#b6798940080f11e49c63000000349f4a#b6798940080f11e49c63000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [57] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 75d7ad6
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 75d7ad6
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 02:08:53:376#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE004000000000000011BC#3448650000001698##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##A2C9042D080F11E4873200155D336301#a2c9042d080f11e4873200155d336301#a2c9042d080f11e4873200155d336301#0#Application [36]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 10 02:21:33:647#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004200000001000011BC#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####95977568081311E4C127000000349F4A#95977568081311e4c127000000349f4a#95977568081311e4c127000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [6] ms on server process [3448650]: #

#2.0
#2014 07 10 02:21:33:647#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE004200000002000011BC#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####95977568081311E4C127000000349F4A#95977568081311e4c127000000349f4a#95977568081311e4c127000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [6] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 02:21:33:830#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE004300000001000011BC#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####95977568081311E4C127000000349F4A#95977568081311e4c127000000349f4a#95977568081311e4c127000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 10 02:21:33:830#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE004300000002000011BC#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####95977568081311E4C127000000349F4A#95977568081311e4c127000000349f4a#95977568081311e4c127000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 02:21:34:438#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005400000001000011BC#3448650000001920##com.sap.engine.core.service630.container.ContainerObjectRegistry####95977568081311E4C127000000349F4A#95977568081311e4c127000000349f4a#95977568081311e4c127000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 02:21:34:568#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE004000000002000011BC#3448650000001698##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###a2c9042d080f11e4873200155d336301##0#Application [36]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 10 02:21:34:577#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005F00000001000011BC#3448650000001813##com.sap.engine.core.service630.container.ContainerObjectRegistry#####95977568081311e4c127000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 02:21:34:598#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE006100000000000011BC#3448650000001956##com.sap.engine.core.service630.container.ServiceWrapper#####95977568081311e4c127000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 10 02:21:34:604#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE006300000001000011BC#3448650000001684##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###a2c9042d080f11e4873200155d336301##0#Application [44]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:218)

#

#2.0
#2014 07 10 02:21:37:705#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005C00000002000011BC#3448650000003735##com.sap.engine.core.service630.container.ServiceWrapper#####95977568081311e4c127000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 10 02:21:37:713#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE004F00000005000011BC#3448650000003758##com.sap.engine.core.service630.container.ServiceWrapper#####95977568081311e4c127000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 10 02:21:37:917#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE002000000001000011BC#3448650000003918##com.sap.engine.core.service630.container.ContainerObjectRegistry#####95977568081311e4c127000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 10 02:21:37:925#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006900000001000011BC#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####a2c9042d080f11e4873200155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 10 02:21:37:925#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006800000001000011BC#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####a2c9042d080f11e4873200155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 10 02:21:37:925#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006900000002000011BC#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####a2c9042d080f11e4873200155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 02:21:37:925#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006800000002000011BC#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####a2c9042d080f11e4873200155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 02:21:41:191#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE006B00000000000011BC#3448650000001657##com.sap.engine.services.wsrm#####a2c9042d080f11e4873200155d336301##0#System [37]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 10 02:23:33:119#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001748###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 10 02:23:39:312#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000100001748#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####de23cfb5081311e4b1cb00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 02:23:39:313#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B0000000300001748#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####de23cfb5081311e4b1cb00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 10 02:23:43:575#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A0000000200001748#3448650000000617##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####de23cfb5081311e4b1cb00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 10 02:23:47:833#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE000B0000000B00001748#3448650000000960##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 10 02:23:49:281#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00120000000000001748#3448650000001047##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 10 02:23:51:501#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00130000000100001748#3448650000001212##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 10 02:23:53:322#0-700#Error#com.adobe.service.logging.Logger#
#BC-SRV-FP#com.adobe~DocumentServicesBinaries2#C000AC1D32BE00150000000C00001748#3448650000001416##com.adobe.service.logging.Logger####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Service Runner [com.adobe~PDFManipulation]#Plain##
error getting ssl flag, using non-SSL mode: null#

#2.0
#2014 07 10 02:23:55:272#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001C0000000200001748#3448650000001784##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 10 02:23:55:330#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001C0000000300001748#3448650000001784##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 10 02:23:57:406#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00020000000900001748#3448650000001905##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 10 02:24:01:959#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00050000000500001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [23] ms on server process [3448650]: #

#2.0
#2014 07 10 02:24:01:959#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00050000000600001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [23] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 02:24:02:073#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00020000000C00001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [24] ms on server process [3448650]: #

Former Member
0 Kudos

part 5

===================================================================

#2.0
#2014 07 10 02:24:02:073#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00020000000D00001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [24] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 10 02:24:03:893#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00020000000F00001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [48] ms on server process [3448650]: #

#2.0
#2014 07 10 02:24:03:893#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00020000001000001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [48] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 10 02:24:05:390#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000000800001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1118] ms on server process [3448650]: #

#2.0
#2014 07 10 02:24:05:391#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00050000000900001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1118] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 10 02:24:06:183#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002D0000000200001748#3448650000001947#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Application [48]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 10 02:24:06:685#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00160000001200001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [27] ms on server process [3448650]: #

#2.0
#2014 07 10 02:24:06:685#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00160000001300001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [27] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 59d53274
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 10 02:24:06:804#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00160000001500001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: #

#2.0
#2014 07 10 02:24:06:804#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00160000001600001748#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EB7BD096081311E49BAA000000349F4A#eb7bd096081311e49baa000000349f4a#eb7bd096081311e49baa000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [20] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2121bf06
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2121bf06
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 10 02:26:15:490#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE003F0000000100001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#1##28D36804081411E49670000000349F4A#393f4dae081411e4bae2000000349f4a#393f4dae081411e4bae2000000349f4a#0#Thread[HTTP Worker [@975193155],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LC0003ME20011H07668465420015J2EE-Engine_MSS".#

#2.0
#2014 07 10 02:26:15:492#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE003F0000000200001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#1##28D36804081411E49670000000349F4A#393f4dae081411e4bae2000000349f4a#393f4dae081411e4bae2000000349f4a#0#Thread[HTTP Worker [@975193155],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 02:26:15:493#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE003F0000000300001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#1##28D36804081411E49670000000349F4A#393f4dae081411e4bae2000000349f4a#393f4dae081411e4bae2000000349f4a#0#Thread[HTTP Worker [@975193155],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.isExtendableLocal(Admin.java:1292)
at com.sap.security.core.server.likey.Admin.isExtendable(Admin.java:1127)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.isExtendable(LicensingManagerImpl.java:766)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getAttributes(LicensingManagerImpl.java:727)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getLicensingInformation(LicensingManagerImpl.java:279)
at com.sap.engine.services.licensing.LicensingProcessor.getLicensingInformation(LicensingProcessor.java:53)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.getLicensingInformation(LicensingRuntimeInterfaceImpl.java:37)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:90)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.getAttribute(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:361)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.getAttribute(ITSAMUIMBeanServerConnectionWrapper.java:244)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService.java:409)
at com.sap.lm.itsam.ui.licensing.LicensingView.bindContextNodes(LicensingView.java:696)
at com.sap.lm.itsam.ui.licensing.LicensingView.refresh(LicensingView.java:720)
at com.sap.lm.itsam.ui.licensing.LicensingView.wdDoInit(LicensingView.java:139)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdDoInit(InternalLicensingView.java:234)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:59)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:731)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.getView(ViewManager.java:668)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.bindRoot(ViewManager.java:563)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.init(ViewManager.java:183)
at com.sap.tc.webdynpro.progmodel.window.InterfaceView.manageEmbeddedViewManager(InterfaceView.java:141)
at com.sap.tc.webdynpro.progmodel.window.EmbeddedInterfaceView.onInstanceAvailable(EmbeddedInterfaceView.java:94)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.fireInstanceAvailable(ComponentUsage.java:936)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:425)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:352)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplicationInternal(FloorPlan.java:2154)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplication(FloorPlan.java:448)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.init(FloorPlan.java:651)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadProfessionalApplication(FloorPlan.java:1182)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalFloorPlan.loadProfessionalApplication(InternalFloorPlan.java:867)
at com.sap.lm.itsam.ui.floorplan.IDPView.onActionGoTo(IDPView.java:2179)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalIDPView.wdInvokeEventHandler(InternalIDPView.java:1316)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 10 02:39:01:841#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00400000000000001748#3448650000001784##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 10 02:46:32:784#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00420000000100001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#2##0CA2AB27081711E4C60E000000349F4A#3e72a680081411e4891d000000349f4a#3e72a680081411e4891d000000349f4a#0#Thread[HTTP Worker [@998940260],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LC0003ME20011H07668465420015J2EE-Engine_MSS".#

#2.0
#2014 07 10 02:46:32:785#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00420000000200001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#2##0CA2AB27081711E4C60E000000349F4A#3e72a680081411e4891d000000349f4a#3e72a680081411e4891d000000349f4a#0#Thread[HTTP Worker [@998940260],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 02:46:32:785#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00420000000300001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#2##0CA2AB27081711E4C60E000000349F4A#3e72a680081411e4891d000000349f4a#3e72a680081411e4891d000000349f4a#0#Thread[HTTP Worker [@998940260],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.isExtendableLocal(Admin.java:1292)
at com.sap.security.core.server.likey.Admin.isExtendable(Admin.java:1127)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.isExtendable(LicensingManagerImpl.java:766)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getAttributes(LicensingManagerImpl.java:727)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getLicensingInformation(LicensingManagerImpl.java:279)
at com.sap.engine.services.licensing.LicensingProcessor.getLicensingInformation(LicensingProcessor.java:53)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.getLicensingInformation(LicensingRuntimeInterfaceImpl.java:37)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:90)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.getAttribute(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:361)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.getAttribute(ITSAMUIMBeanServerConnectionWrapper.java:244)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService.java:409)
at com.sap.lm.itsam.ui.licensing.LicensingView.bindContextNodes(LicensingView.java:696)
at com.sap.lm.itsam.ui.licensing.LicensingView.refresh(LicensingView.java:720)
at com.sap.lm.itsam.ui.licensing.LicensingView.wdDoInit(LicensingView.java:139)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdDoInit(InternalLicensingView.java:234)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:59)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:731)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.getView(ViewManager.java:668)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.bindRoot(ViewManager.java:563)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.init(ViewManager.java:183)
at com.sap.tc.webdynpro.progmodel.window.InterfaceView.manageEmbeddedViewManager(InterfaceView.java:141)
at com.sap.tc.webdynpro.progmodel.window.EmbeddedInterfaceView.onInstanceAvailable(EmbeddedInterfaceView.java:94)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.fireInstanceAvailable(ComponentUsage.java:936)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:425)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:352)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplicationInternal(FloorPlan.java:2154)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplication(FloorPlan.java:448)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.init(FloorPlan.java:651)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadProfessionalApplication(FloorPlan.java:1182)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalFloorPlan.loadProfessionalApplication(InternalFloorPlan.java:867)
at com.sap.lm.itsam.ui.floorplan.IDPView.onActionGoTo(IDPView.java:2179)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalIDPView.wdInvokeEventHandler(InternalIDPView.java:1316)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 10 04:53:34:253#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00560000000100001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#56735b56082811e4cdf9000000349f4a#56735b56082811e4cdf9000000349f4a#0#Thread[HTTP Worker [@1609169780],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LC0003ME20011H07668465420015J2EE-Engine_MSS".#

#2.0
#2014 07 10 04:53:34:255#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00560000000200001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#56735b56082811e4cdf9000000349f4a#56735b56082811e4cdf9000000349f4a#0#Thread[HTTP Worker [@1609169780],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 04:53:34:255#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00560000000300001748#3448650000000004#sap.com/tc~lm~itsam~ui~licensing~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#56735b56082811e4cdf9000000349f4a#56735b56082811e4cdf9000000349f4a#0#Thread[HTTP Worker [@1609169780],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.isExtendableLocal(Admin.java:1292)
at com.sap.security.core.server.likey.Admin.isExtendable(Admin.java:1127)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.isExtendable(LicensingManagerImpl.java:766)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getAttributes(LicensingManagerImpl.java:727)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getLicensingInformation(LicensingManagerImpl.java:279)
at com.sap.engine.services.licensing.LicensingProcessor.getLicensingInformation(LicensingProcessor.java:53)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.getLicensingInformation(LicensingRuntimeInterfaceImpl.java:37)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:90)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.getAttribute(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:361)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.getAttribute(ITSAMUIMBeanServerConnectionWrapper.java:244)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService.java:409)
at com.sap.lm.itsam.ui.licensing.LicensingView.bindContextNodes(LicensingView.java:696)
at com.sap.lm.itsam.ui.licensing.LicensingView.refresh(LicensingView.java:720)
at com.sap.lm.itsam.ui.licensing.LicensingView.wdDoInit(LicensingView.java:139)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdDoInit(InternalLicensingView.java:234)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:59)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:731)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.getView(ViewManager.java:668)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.bindRoot(ViewManager.java:563)
at com.sap.tc.webdynpro.progmodel.window.ViewManager.init(ViewManager.java:183)
at com.sap.tc.webdynpro.progmodel.window.InterfaceView.manageEmbeddedViewManager(InterfaceView.java:141)
at com.sap.tc.webdynpro.progmodel.window.EmbeddedInterfaceView.onInstanceAvailable(EmbeddedInterfaceView.java:94)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.fireInstanceAvailable(ComponentUsage.java:936)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:425)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:352)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplicationInternal(FloorPlan.java:2154)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplication(FloorPlan.java:448)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.init(FloorPlan.java:651)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadProfessionalApplication(FloorPlan.java:1182)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.navigateNFtoEmbeddedApplication(FloorPlan.java:1818)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalFloorPlan.wdInvokeEventHandler(InternalFloorPlan.java:974)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.invokeEventHandler(DelegatingComponent.java:248)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverview.wdFireEventNavigateToEmbeddedApplication(InternalWorkCenterOverview.java:315)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.WorkCenterOverview.fireEventNavigateToEA(WorkCenterOverview.java:381)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverview.fireEventNavigateToEA(InternalWorkCenterOverview.java:222)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.WorkCenterOverviewView.onActionNavigate(WorkCenterOverviewView.java:440)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverviewView.wdInvokeEventHandler(InternalWorkCenterOverviewView.java:221)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 10 04:55:03:630#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000100001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LK0003ME20011R15834187110015J2EE-Engine_MSS".#

#2.0
#2014 07 10 04:55:03:631#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000200001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011R15834187110015J2EE-Engine_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 04:55:03:631#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000300001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011R15834187110015J2EE-Engine_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.checkAndInsertKey(Admin.java:2136)
at com.sap.security.core.server.likey.Admin.installFromFile(Admin.java:1914)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.installLicense(LicensingManagerImpl.java:394)
at com.sap.engine.services.licensing.LicensingProcessor.installLicense(LicensingProcessor.java:169)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.installLicense(LicensingRuntimeInterfaceImpl.java:76)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.installLicense(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:165)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.invoke(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:318)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:468)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:547)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:365)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:289)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(ITSAMUIMBeanServerConnectionWrapper.java:379)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.installLicense(SAP_ITSAMJ2eeLicensingManagementService.java:184)
at com.sap.lm.itsam.ui.licensing.LicensingView.licenseFileChosen(LicensingView.java:447)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdInvokeEventHandler(InternalLicensingView.java:309)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.wdFireEventLicenseFileChosen(InternalLicensingComponent.java:343)
at com.sap.lm.itsam.ui.licensing.LicensingComponent.chooseLicenseFile(LicensingComponent.java:264)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.chooseLicenseFile(InternalLicensingComponent.java:263)
at com.sap.lm.itsam.ui.licensing.ChooseFileView.onActionOk(ChooseFileView.java:196)
at com.sap.lm.itsam.ui.licensing.wdp.InternalChooseFileView.wdInvokeEventHandler(InternalChooseFileView.java:138)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 10 04:55:03:813#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000600001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LK0003ME20011R15834187110015Maintenance_MSS".#

#2.0
#2014 07 10 04:55:03:815#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000700001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011R15834187110015Maintenance_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 04:55:03:815#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000800001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011R15834187110015Maintenance_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.checkAndInsertKey(Admin.java:2136)
at com.sap.security.core.server.likey.Admin.installFromFile(Admin.java:1914)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.installLicense(LicensingManagerImpl.java:394)
at com.sap.engine.services.licensing.LicensingProcessor.installLicense(LicensingProcessor.java:169)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.installLicense(LicensingRuntimeInterfaceImpl.java:76)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.installLicense(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:165)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.invoke(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:318)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:468)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:547)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:365)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:289)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(ITSAMUIMBeanServerConnectionWrapper.java:379)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.installLicense(SAP_ITSAMJ2eeLicensingManagementService.java:184)
at com.sap.lm.itsam.ui.licensing.LicensingView.licenseFileChosen(LicensingView.java:447)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdInvokeEventHandler(InternalLicensingView.java:309)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.wdFireEventLicenseFileChosen(InternalLicensingComponent.java:343)
at com.sap.lm.itsam.ui.licensing.LicensingComponent.chooseLicenseFile(LicensingComponent.java:264)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.chooseLicenseFile(InternalLicensingComponent.java:263)
at com.sap.lm.itsam.ui.licensing.ChooseFileView.onActionOk(ChooseFileView.java:196)
at com.sap.lm.itsam.ui.licensing.wdp.InternalChooseFileView.wdInvokeEventHandler(InternalChooseFileView.java:138)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 10 04:55:03:841#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000D00001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LC0003ME20011H07668465420015J2EE-Engine_MSS".#

#2.0
#2014 07 10 04:55:03:842#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000E00001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 10 04:55:03:842#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00570000000F00001748#3448650000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#3##BD1FF6C0082011E4B084000000349F4A#ca273132082811e4862c000000349f4a#ca273132082811e4862c000000349f4a#0#Thread[HTTP Worker [@264128875],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LC0003ME20011H07668465420015J2EE-Engine_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.Admin.isExtendableLocal(Admin.java:1292)
at com.sap.security.core.server.likey.Admin.isExtendable(Admin.java:1127)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.isExtendable(LicensingManagerImpl.java:766)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getAttributes(LicensingManagerImpl.java:727)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.getLicensingInformation(LicensingManagerImpl.java:279)
at com.sap.engine.services.licensing.LicensingProcessor.getLicensingInformation(LicensingProcessor.java:53)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.getLicensingInformation(LicensingRuntimeInterfaceImpl.java:37)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:90)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.getAttribute(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:361)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:662)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:423)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:231)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:235)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:161)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.getAttribute(ITSAMUIMBeanServerConnectionWrapper.java:244)
at com.sap.engine.services.licensing.itsam._gen.SAP_ITSAMJ2eeLicensingManagementService$Impl.getLicenses(SAP_ITSAMJ2eeLicensingManagementService.java:409)
at com.sap.lm.itsam.ui.licensing.LicensingView.bindContextNodes(LicensingView.java:696)
at com.sap.lm.itsam.ui.licensing.LicensingView.licenseFileChosen(LicensingView.java:481)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingView.wdInvokeEventHandler(InternalLicensingView.java:309)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.wdFireEventLicenseFileChosen(InternalLicensingComponent.java:343)
at com.sap.lm.itsam.ui.licensing.LicensingComponent.chooseLicenseFile(LicensingComponent.java:264)
at com.sap.lm.itsam.ui.licensing.wdp.InternalLicensingComponent.chooseLicenseFile(InternalLicensingComponent.java:263)
at com.sap.lm.itsam.ui.licensing.ChooseFileView.onActionOk(ChooseFileView.java:196)
at com.sap.lm.itsam.ui.licensing.wdp.InternalChooseFileView.wdInvokeEventHandler(InternalChooseFileView.java:138)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 11 01:58:30:448#0-700#Error#com.sap.engine.core.locking.impl3.LockingManagerImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005C0000000000001748###com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#Guest#0##87A2F98708D911E4BBF5000000349F4A#87a2f98708d911e4bbf5000000349f4a#87a2f98708d911e4bbf5000000349f4a#0#Thread[SAPEngine_EnquReader,5,main]#Plain##
EncomiHandle.ReceiveMessage(): receive failed (Software caused connection abort: recv failed) closing connection)#

#2.0
#2014 07 11 01:58:30:450#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE005D0000000000001748#3448650000025523##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()####DB3FD0FB081311E4B5D300155D336301#db3fd0fb081311e4b5d300155d336301#db3fd0fb081311e4b5d300155d336301#0#SAP J2EE Engine|MS Socket Listener#Plain##
java.net.SocketException: Software caused connection abort: recv failed#

#2.0
#2014 07 11 01:58:30:488#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE005D0000000100001748#3448650000025523##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()####DB3FD0FB081311E4B5D300155D336301#db3fd0fb081311e4b5d300155d336301#db3fd0fb081311e4b5d300155d336301#0#SAP J2EE Engine|MS Socket Listener#Plain##
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:513)
at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:184)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1858)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.receiveRawMessage(MSConnectionImpl.java:46)
at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:101)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
#

#2.0
#2014 07 11 01:58:30:762#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000600001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".#

#2.0
#2014 07 11 01:58:30:763#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000700001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 01:58:30:764#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000900001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 11 01:58:30:764#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000A00001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 01:58:30:766#0-700#Error#com.sap.tc.cbs.server.rt.sync.AccessOrc#
#BC-CTS-CBS#tc.CBS.Service#C000AC1D32BE001B0000000C00001748#3448650000001208##com.sap.tc.cbs.server.rt.sync.AccessOrc####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
Access orchestrator failure
[EXCEPTION]
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:A database error occurred while processing the entries in the access queue.
Original Cause: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:563)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
... 3 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
... 6 more

#

#2.0
#2014 07 11 01:58:30:768#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000E00001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".#

#2.0
#2014 07 11 01:58:30:768#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000000F00001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 01:58:30:769#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000001100001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 11 01:58:30:769#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001B0000001200001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 01:58:30:770#0-700#Error#com.sap.tc.cbs.server.rt.sync.AccessOrc#
#BC-CTS-CBS#tc.CBS.Service#C000AC1D32BE001B0000001400001748#3448650000001208##com.sap.tc.cbs.server.rt.sync.AccessOrc####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
Access orchestrator failure
[EXCEPTION]
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:A database error occurred while processing the entries in the access queue.
Original Cause: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:563)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
... 3 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
... 6 more

#

#2.0
#2014 07 11 02:02:14:098#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE005F0000000100001748#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "INSERT INTO "BC_MON_AGREGATES" ("ID","MONITOR_ID","START_TIME","AGR_INTERVAL","AVG_VALUE","STD_DEVIATION","MIN_VALUE","MAX_VALUE","COUNTS") VALUES (?,?,?,?,?,?,?,?,?)".#

#2.0
#2014 07 11 02:02:14:098#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE005F0000000200001748#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "INSERT INTO "BC_MON_AGREGATES" ("ID","MONITOR_ID","START_TIME","AGR_INTERVAL","AVG_VALUE","STD_DEVIATION","MIN_VALUE","MAX_VALUE","COUNTS") VALUES (?,?,?,?,?,?,?,?,?)".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeWrappedBytes(IOBuffer.java:3257)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeInt(IOBuffer.java:3167)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeRPCInt(IOBuffer.java:3693)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.buildExecParams(SQLServerPreparedStatement.java:595)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doPrepExec(SQLServerPreparedStatement.java:625)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(SQLServerPreparedStatement.java:1282)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtBatchExecCmd.doExecute(SQLServerPreparedStatement.java:1209)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1173)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:268)
at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:300)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1226)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.deleteAgregations(DBAgregationWriter.java:224)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.cleanOldAgregates(PersistenceManager.java:188)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.access$100(PersistenceManager.java:17)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager$AgregationCleaner.run(PersistenceManager.java:67)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 02:02:14:100#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE005F0000000400001748#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 11 02:02:14:100#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE005F0000000500001748#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1229)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.deleteAgregations(DBAgregationWriter.java:224)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.cleanOldAgregates(PersistenceManager.java:188)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.access$100(PersistenceManager.java:17)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager$AgregationCleaner.run(PersistenceManager.java:67)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 02:02:14:101#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE005F0000000600001748#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
Monitoring history database writer disabled#

#2.0
#2014 07 11 02:02:14:101#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE005F0000000700001748#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
History persistence cleaner thread had stopped. DB writing has been disabled#

#2.0
#2014 07 11 02:02:14:101#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE005F0000000800001748#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####EB7AE257081311E4C270000000349F4A#eb7ae257081311e4c270000000349f4a#eb7ae257081311e4c270000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1229)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.deleteAgregations(DBAgregationWriter.java:224)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.cleanOldAgregates(PersistenceManager.java:188)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.access$100(PersistenceManager.java:17)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager$AgregationCleaner.run(PersistenceManager.java:67)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeWrappedBytes(IOBuffer.java:3257)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeInt(IOBuffer.java:3167)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeRPCInt(IOBuffer.java:3693)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.buildExecParams(SQLServerPreparedStatement.java:595)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doPrepExec(SQLServerPreparedStatement.java:625)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(SQLServerPreparedStatement.java:1282)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtBatchExecCmd.doExecute(SQLServerPreparedStatement.java:1209)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1173)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:268)
at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:300)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1226)
... 9 more

#

#2.0
#2014 07 11 02:29:33:613#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00590000000400001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS Resource Orc,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_PROPERTIES" WHERE "PROPERTYNAME" = ?".#

#2.0
#2014 07 11 02:29:33:613#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00590000000500001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS Resource Orc,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_PROPERTIES" WHERE "PROPERTYNAME" = ?".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.DBRead.listNotCompletedIntegrations(DBRead.java:2971)
at com.sap.tc.cbs.server.proc.strategy.Reinitializer.repairAfterIncompleteIntegrations(Reinitializer.java:66)
at com.sap.tc.cbs.server.rt.impl.ResourceOrc.act(ResourceOrc.java:241)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 02:29:33:614#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00590000000700001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS Resource Orc,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 11 02:29:33:614#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00590000000800001748#3448650000001208##com.sap.sql.jdbc.direct.DirectPreparedStatement####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS Resource Orc,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.DBRead.listNotCompletedIntegrations(DBRead.java:2971)
at com.sap.tc.cbs.server.proc.strategy.Reinitializer.repairAfterIncompleteIntegrations(Reinitializer.java:66)
at com.sap.tc.cbs.server.rt.impl.ResourceOrc.act(ResourceOrc.java:241)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 11 02:29:33:616#0-700#Error#com.sap.tc.cbs.server.rt.impl.ResourceOrc#
#BC-CTS-CBS#tc.CBS.Service#C000AC1D32BE00590000000A00001748#3448650000001208##com.sap.tc.cbs.server.rt.impl.ResourceOrc####DE23CFB5081311E4B1CB00155D336301#de23cfb5081311e4b1cb00155d336301#de23cfb5081311e4b1cb00155d336301#0#Thread[CBS Resource Orc,5,SystemThreadGroup]#Plain##
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:Failed to list not completed integrations
Original Cause: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.tc.cbs.server.db.impl.DBRead.listNotCompletedIntegrations(DBRead.java:2983)
at com.sap.tc.cbs.server.proc.strategy.Reinitializer.repairAfterIncompleteIntegrations(Reinitializer.java:66)
at com.sap.tc.cbs.server.rt.impl.ResourceOrc.act(ResourceOrc.java:241)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.DBRead.listNotCompletedIntegrations(DBRead.java:2971)
... 4 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
... 7 more
#

#2.0
#2014 07 11 03:28:52:531#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00600000000300001748#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####2748882D08E611E4C061000000349F4A#2748882d08e611e4c061000000349f4a#2748882d08e611e4c061000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [2] ms on server process [3448650]: #

#2.0
#2014 07 11 03:28:52:537#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00600000000400001748#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####2748882D08E611E4C061000000349F4A#2748882d08e611e4c061000000349f4a#2748882d08e611e4c061000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [2] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 11 03:28:53:113#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00630000000100001748#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####2748882D08E611E4C061000000349F4A#2748882d08e611e4c061000000349f4a#2748882d08e611e4c061000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 11 03:28:53:113#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00630000000200001748#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####2748882D08E611E4C061000000349F4A#2748882d08e611e4c061000000349f4a#2748882d08e611e4c061000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 11 03:28:53:811#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00890000000000001748#3448650000001878##com.sap.engine.core.service630.container.ServiceWrapper#####2748882d08e611e4c061000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 11 03:28:53:829#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE008B0000000100001748#3448650000001882##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2748882d08e611e4c061000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 11 03:28:53:845#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00680000000200001748#3448650000001871##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2748882d08e611e4c061000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 11 03:28:53:920#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00400000000200001748#3448650000001784##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###de23cfb5081311e4b1cb00155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 11 03:28:53:921#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE008D0000000100001748#3448650000001769##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###de23cfb5081311e4b1cb00155d336301##0#Application [39]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 11 03:28:57:054#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE008F0000000000001748#3448650000003951##com.sap.engine.core.service630.container.ServiceWrapper#####2748882d08e611e4c061000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 11 03:28:57:059#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00820000000100001748#3448650000003922##com.sap.engine.core.service630.container.ServiceWrapper#####2748882d08e611e4c061000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 11 03:28:57:288#0-700#Error#com.sap.sql.jdbc.direct.DirectConnection#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00910000000200001748#3448650000004097##com.sap.sql.jdbc.direct.DirectConnection#####2748882d08e611e4c061000000349f4a##0#Service Stopper [dbpool]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "COMMIT".#

#2.0
#2014 07 11 03:28:57:288#0-700#Error#com.sap.sql.jdbc.direct.DirectConnection#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00910000000300001748#3448650000004097##com.sap.sql.jdbc.direct.DirectConnection#####2748882d08e611e4c061000000349f4a##0#Service Stopper [dbpool]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "COMMIT".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6106)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$1ConnectionCommand.doExecute(SQLServerConnection.java:1756)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(SQLServerConnection.java:1761)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.commit(SQLServerConnection.java:1938)
at com.sap.sql.jdbc.basic.BasicConnection.commit(BasicConnection.java:74)
at com.sap.sql.jdbc.direct.DirectConnection.commit(DirectConnection.java:428)
at com.sap.sql.jdbc.common.CommonPooledConnection.cleanup(CommonPooledConnection.java:713)
at com.sap.sql.connect.datasource.DBDataSourceImpl.cleanup(DBDataSourceImpl.java:1079)
at com.sap.sql.connect.datasource.DBDataSourceImpl.cleanup(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.cleanup(CreatedObjectsPool.java:409)
at com.sap.sql.connect.pool.Pool.release(Pool.java:526)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:875)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionClosed(DBDataSourceImpl.java:422)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionClosed(CommonPooledConnection.java:1053)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionHandleClosed(CommonPooledConnection.java:421)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:1329)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:366)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.commonDestroy(LocalTXManagedConnectionImpl.java:257)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.destroy(LocalTXManagedConnectionImpl.java:119)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroyConnections(ConnectionHashSet.java:542)
at com.sap.engine.services.connector.jca.ConnectionHashSet.clear(ConnectionHashSet.java:530)
at com.sap.engine.services.connector.jca.AdapterCache.close(AdapterCache.java:130)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:297)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:317)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.stopDataSource(ContainerImpl.java:1435)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.destroyDefaultDataSource(ContainerImpl.java:933)
at com.sap.engine.services.dbpool.PoolFrame.stop(PoolFrame.java:150)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 11 03:28:57:289#0-700#Error#com.sap.engine.services.connector.jca.ConnectionHashSet#
com.sap.ASJ.conn.000130#BC-JAS-TRH#connector#C000AC1D32BE00910000000400001748#3448650000004097##com.sap.engine.services.connector.jca.ConnectionHashSet#####2748882d08e611e4c061000000349f4a##0#Service Stopper [dbpool]#Plain##
ConnectionHashSet, Exception:
[EXCEPTION]
java.lang.NullPointerException: while trying to invoke the method com.sap.sql.jdbc.ConnectionContext.getConnectionID() of an object loaded from field com.sap.sql.jdbc.common.CommonPooledConnection.connContext of an object loaded from local variable 'this'
at com.sap.sql.jdbc.common.CommonPooledConnection.destroyConnection(CommonPooledConnection.java:832)
at com.sap.sql.connect.datasource.DBDataSourceImpl.closePooledConnection(DBDataSourceImpl.java:698)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:1004)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.destroy(CreatedObjectsPool.java:138)
at com.sap.sql.connect.pool.Pool.release(Pool.java:537)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:875)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionClosed(DBDataSourceImpl.java:422)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionClosed(CommonPooledConnection.java:1053)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionHandleClosed(CommonPooledConnection.java:421)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:1329)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:366)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.commonDestroy(LocalTXManagedConnectionImpl.java:257)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.destroy(LocalTXManagedConnectionImpl.java:119)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroyConnections(ConnectionHashSet.java:542)
at com.sap.engine.services.connector.jca.ConnectionHashSet.clear(ConnectionHashSet.java:530)
at com.sap.engine.services.connector.jca.AdapterCache.close(AdapterCache.java:130)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:297)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:317)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.stopDataSource(ContainerImpl.java:1435)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.destroyDefaultDataSource(ContainerImpl.java:933)
at com.sap.engine.services.dbpool.PoolFrame.stop(PoolFrame.java:150)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

Former Member
0 Kudos

part 6

=========================================================

#2.0
#2014 07 11 03:28:57:293#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE00920000000000001748#3448650000004101##com.sap.engine.core.service630.container.ServiceWrapper#####2748882d08e611e4c061000000349f4a##0#Service Stopper [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 11 03:28:57:293#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00720000000300001748#3448650000004110##com.sap.engine.core.service630.container.ContainerObjectRegistry#####2748882d08e611e4c061000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 11 03:28:57:320#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE00930000000100001748#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####de23e923081311e4cfa300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 11 03:28:57:320#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE00930000000200001748#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####de23e923081311e4cfa300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 11 03:29:00:596#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE00030000000200001748#3448650000001694##com.sap.engine.services.wsrm#####de23cfb5081311e4b1cb00155d336301##0#System [13]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 03:30:09:900#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000013B4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 14 03:30:26:336#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000700000002000013B4#3448650000000565##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####d7d003da0b4111e4bc8400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 03:30:26:337#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000700000004000013B4#3448650000000565##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####d7d003da0b4111e4bc8400155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 03:30:33:103#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000900000002000013B4#3448650000000619##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####d7d003da0b4111e4bc8400155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 14 03:30:38:469#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE001200000002000013B4#3448650000001118##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 14 03:30:38:644#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE000D00000001000013B4#3448650000001119##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 14 03:30:40:066#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE001200000004000013B4#3448650000001229##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 14 03:30:43:833#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001300000004000013B4#3448650000001712##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 14 03:30:44:172#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001300000005000013B4#3448650000001712##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 14 03:30:45:867#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000700000006000013B4#3448650000001882##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####D7D003DA0B4111E4BC8400155D336301#d7d003da0b4111e4bc8400155d336301#d7d003da0b4111e4bc8400155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 14 03:30:53:768#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE002300000001000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [97] ms on server process [3448650]: #

#2.0
#2014 07 14 03:30:53:768#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE002300000002000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [97] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:30:54:121#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001600000008000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [172] ms on server process [3448650]: #

#2.0
#2014 07 14 03:30:54:121#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001600000009000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [172] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:30:57:565#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00160000000B000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [331] ms on server process [3448650]: #

#2.0
#2014 07 14 03:30:57:565#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00160000000C000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [331] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 14 03:30:57:890#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001B00000003000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [779] ms on server process [3448650]: #

#2.0
#2014 07 14 03:30:57:890#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001B00000004000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [779] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 14 03:30:59:681#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE003200000002000013B4#3448650000001979#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Application [49]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 14 03:31:00:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00160000000E000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 14 03:31:00:365#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00160000000F000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 21af14f0
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 14 03:31:00:776#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001600000011000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [66] ms on server process [3448650]: #

#2.0
#2014 07 14 03:31:00:776#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001600000012000013B4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####EA7C16DB0B4111E4A529000000349F4A#ea7c16db0b4111e4a529000000349f4a#ea7c16db0b4111e4a529000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [66] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 6429ab27
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 6429ab27
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 14 03:44:00:867#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003E00000001000013B4#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 14 03:44:00:868#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003E00000002000013B4#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:44:00:976#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003F00000001000013B4#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 14 03:44:00:976#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003F00000002000013B4#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:44:01:563#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE005500000000000013B4#3448650000001826##com.sap.engine.core.service630.container.ServiceWrapper####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 14 03:44:01:607#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005A00000001000013B4#3448650000001825##com.sap.engine.core.service630.container.ContainerObjectRegistry####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:44:01:609#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005B00000001000013B4#3448650000001833##com.sap.engine.core.service630.container.ContainerObjectRegistry####C3FF62AB0B4311E49C19000000349F4A#c3ff62ab0b4311e49c19000000349f4a#c3ff62ab0b4311e49c19000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:44:01:726#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE006100000000000013B4#3448650000001712##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###d7d003da0b4111e4bc8400155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 14 03:44:01:736#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE006200000001000013B4#3448650000001697##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###d7d003da0b4111e4bc8400155d336301##0#Application [24]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 14 03:44:04:899#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE006500000000000013B4#3448650000003866##com.sap.engine.core.service630.container.ServiceWrapper#####c3ff62ab0b4311e49c19000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 14 03:44:04:899#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005600000001000013B4#3448650000003777##com.sap.engine.core.service630.container.ServiceWrapper#####c3ff62ab0b4311e49c19000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 14 03:44:05:050#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006800000000000013B4#3448650000003969##com.sap.engine.core.service630.container.ContainerObjectRegistry#####c3ff62ab0b4311e49c19000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:44:05:054#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE006900000001000013B4#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####d7d003da0b4111e4bc8400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 14 03:44:05:055#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE006900000002000013B4#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####d7d003da0b4111e4bc8400155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 03:44:08:333#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE001E00000001000013B4#3448650000001670##com.sap.engine.services.wsrm#####d7d003da0b4111e4bc8400155d336301##0#System [9]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 03:47:24:332#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001730###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 14 03:47:29:589#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000200001730#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####3e564c8b0b4411e4be8800155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 03:47:29:589#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000A0000000400001730#3448650000000563##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####3e564c8b0b4411e4be8800155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 03:47:34:500#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000B0000000200001730#3448650000000620##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####3e564c8b0b4411e4be8800155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 14 03:47:39:079#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000F0000000400001730#3448650000001166##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 14 03:47:39:499#0-700#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
#BC-ESI-WS-JAV-RT#webservices_lib#C000AC1D32BE00190000000000001730#3448650000001172##com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Event Processor [ssl]#Plain##
Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server [http://localhost:50013/SAPControl.cgi] returned message [Unauthorized]. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:588)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:65)
at com.sap.engine.services.ssl.server.SAPStartupAccessor.getHTTPSPorts(SAPStartupAccessor.java:56)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.getPortSpecificPSEs(KeyStoreConnector.java:49)
at com.sap.engine.services.ssl.keystore.KeyStoreConnector.portSpecificPSEsCheck(KeyStoreConnector.java:120)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.preparePortSpecificPSEs(ServerContainerEventListener.java:61)
at com.sap.engine.services.ssl.server.ServerContainerEventListener.serviceStarted(ServerContainerEventListener.java:55)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:162)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:112)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)


#

#2.0
#2014 07 14 03:47:42:766#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00030000000200001730#3448650000001250##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 14 03:47:45:555#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00070000000400001730#3448650000001767##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 14 03:47:45:741#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00070000000500001730#3448650000001767##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 14 03:47:47:841#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00090000000800001730#3448650000001923##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####3E564C8B0B4411E4BE8800155D336301#3e564c8b0b4411e4be8800155d336301#3e564c8b0b4411e4be8800155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 14 03:47:52:654#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00100000001A00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [15] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:52:654#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00100000001B00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [15] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:47:52:896#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000F0000000800001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [94] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:52:896#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE000F0000000900001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [94] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:47:54:955#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001A0000000700001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [67] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:54:955#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001A0000000800001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [67] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 14 03:47:56:657#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000F0000000B00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1859] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:56:657#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE000F0000000C00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1859] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 14 03:47:56:972#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00300000000200001730#3448650000002058#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Application [50]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 14 03:47:57:334#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE001A0000000A00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [31] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:57:334#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE001A0000000B00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [31] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 7680474f
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 14 03:47:57:463#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001A0000000D00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [34] ms on server process [3448650]: #

#2.0
#2014 07 14 03:47:57:463#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE001A0000000E00001730#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####4B82940A0B4411E4A5D8000000349F4A#4b82940a0b4411e4a5d8000000349f4a#4b82940a0b4411e4a5d8000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [34] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2812149e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2812149e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 14 03:55:30:037#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003C0000000100001730#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####5ECD4EBA0B4511E48D57000000349F4A#5ecd4eba0b4511e48d57000000349f4a#5ecd4eba0b4511e48d57000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 14 03:55:30:037#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE003C0000000200001730#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####5ECD4EBA0B4511E48D57000000349F4A#5ecd4eba0b4511e48d57000000349f4a#5ecd4eba0b4511e48d57000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:55:30:166#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003C0000000400001730#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####5ECD4EBA0B4511E48D57000000349F4A#5ecd4eba0b4511e48d57000000349f4a#5ecd4eba0b4511e48d57000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 14 03:55:30:166#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE003C0000000500001730#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####5ECD4EBA0B4511E48D57000000349F4A#5ecd4eba0b4511e48d57000000349f4a#5ecd4eba0b4511e48d57000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 03:55:30:657#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00470000000000001730#3448650000001787##com.sap.engine.core.service630.container.ServiceWrapper####5ECD4EBA0B4511E48D57000000349F4A#5ecd4eba0b4511e48d57000000349f4a#5ecd4eba0b4511e48d57000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 14 03:55:30:782#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE005B0000000000001730#3448650000001767##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###3e564c8b0b4411e4be8800155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 14 03:55:30:789#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005C0000000100001730#3448650000001796##com.sap.engine.core.service630.container.ContainerObjectRegistry#####5ecd4eba0b4511e48d57000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:55:30:790#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE005D0000000100001730#3448650000001752##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###3e564c8b0b4411e4be8800155d336301##0#Application [20]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 14 03:55:30:798#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE005F0000000100001730#3448650000001915##com.sap.engine.core.service630.container.ContainerObjectRegistry#####5ecd4eba0b4511e48d57000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:55:33:912#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00650000000000001730#3448650000004001##com.sap.engine.core.service630.container.ServiceWrapper#####5ecd4eba0b4511e48d57000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 14 03:55:34:005#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00660000000000001730#3448650000003951##com.sap.engine.core.service630.container.ServiceWrapper#####5ecd4eba0b4511e48d57000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 14 03:55:34:113#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00440000000100001730#3448650000004136##com.sap.engine.core.service630.container.ContainerObjectRegistry#####5ecd4eba0b4511e48d57000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 03:55:34:121#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE00670000000100001730#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3e564c8b0b4411e4be8800155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 14 03:55:34:121#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE00670000000200001730#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####3e564c8b0b4411e4be8800155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 03:55:37:384#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE00040000000200001730#3448650000001711##com.sap.engine.services.wsrm#####3e564c8b0b4411e4be8800155d336301##0#System [12]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 04:01:31:549#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000110C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 14 04:01:38:024#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000010000110C#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####378a074c0b4611e4cfa100155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 04:01:38:024#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000030000110C#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####378a074c0b4611e4cfa100155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 04:01:43:046#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A000000030000110C#3448650000000621##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####378a074c0b4611e4cfa100155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 14 04:01:49:007#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE0004000000030000110C#3448650000001125##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 14 04:01:52:702#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE0002000000030000110C#3448650000001256##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 14 04:01:55:476#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001E000000020000110C#3448650000001742##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 14 04:01:55:542#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE001E000000030000110C#3448650000001742##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 14 04:01:57:353#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE0012000000070000110C#3448650000001925##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

Former Member
0 Kudos

part 7

====================================================

#2.0
#2014 07 14 04:02:01:884#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001F000000020000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [13] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:01:884#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001F000000030000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [13] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 04:02:02:303#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0007000000040000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [22] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:02:303#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0007000000050000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [22] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 04:02:03:816#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001F000000050000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [37] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:03:816#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001F000000060000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [37] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 14 04:02:05:269#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0017000000040000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [651] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:05:270#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0017000000050000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [651] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 14 04:02:06:296#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE0033000000020000110C#3448650000002041#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Application [47]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 14 04:02:06:731#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0036000000010000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [23] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:06:731#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0036000000020000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [23] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 70fd10b5
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 14 04:02:07:005#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE0036000000040000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [26] ms on server process [3448650]: #

#2.0
#2014 07 14 04:02:07:006#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE0036000000050000110C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####45DD33760B4611E4BCF5000000349F4A#45dd33760b4611e4bcf5000000349f4a#45dd33760b4611e4bcf5000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [26] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2db46524
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2db46524
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 14 04:17:02:094#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0046000000000000110C#3448650000001742##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##378A074C0B4611E4CFA100155D336301#378a074c0b4611e4cfa100155d336301#378a074c0b4611e4cfa100155d336301#0#Application [31]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 14 05:51:14:504#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0050000000010000110C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####89D83E510B5511E4A618000000349F4A#89d83e510b5511e4a618000000349f4a#89d83e510b5511e4a618000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [7] ms on server process [3448650]: #

#2.0
#2014 07 14 05:51:14:505#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0050000000020000110C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####89D83E510B5511E4A618000000349F4A#89d83e510b5511e4a618000000349f4a#89d83e510b5511e4a618000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [7] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 05:51:15:172#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0051000000010000110C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####89D83E510B5511E4A618000000349F4A#89d83e510b5511e4a618000000349f4a#89d83e510b5511e4a618000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 14 05:51:15:172#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0051000000020000110C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####89D83E510B5511E4A618000000349F4A#89d83e510b5511e4a618000000349f4a#89d83e510b5511e4a618000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 05:51:15:742#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE0066000000000000110C#3448650000001872##com.sap.engine.core.service630.container.ServiceWrapper#####89d83e510b5511e4a618000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 14 05:51:15:742#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0060000000010000110C#3448650000001792##com.sap.engine.core.service630.container.ContainerObjectRegistry#####89d83e510b5511e4a618000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 05:51:15:742#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0062000000010000110C#3448650000001811##com.sap.engine.core.service630.container.ContainerObjectRegistry#####89d83e510b5511e4a618000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 05:51:15:834#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0046000000020000110C#3448650000001742##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###378a074c0b4611e4cfa100155d336301##0#Application [31]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 14 05:51:15:836#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE006A000000010000110C#3448650000001713##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###378a074c0b4611e4cfa100155d336301##0#Application [30]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 14 05:51:18:973#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE005F000000030000110C#3448650000003561##com.sap.engine.core.service630.container.ServiceWrapper#####89d83e510b5511e4a618000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 14 05:51:18:981#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE0067000000010000110C#3448650000003596##com.sap.engine.core.service630.container.ServiceWrapper#####89d83e510b5511e4a618000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 14 05:51:19:211#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006F000000000000110C#3448650000003742##com.sap.engine.core.service630.container.ContainerObjectRegistry#####89d83e510b5511e4a618000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 14 05:51:19:228#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE0070000000010000110C#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####378a074c0b4611e4cfa100155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 14 05:51:19:228#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE0070000000020000110C#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####378a074c0b4611e4cfa100155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 05:51:22:609#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE0020000000010000110C#3448650000001741##com.sap.engine.services.wsrm#####378a074c0b4611e4cfa100155d336301##0#System [38]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 14 05:52:04:805#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001A08###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 14 05:52:12:752#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00010000000200001A08#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####a98fb3f70b5511e4b58700155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 05:52:12:753#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE00010000000400001A08#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####a98fb3f70b5511e4b58700155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 05:52:19:043#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A0000000200001A08#3448650000000621##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####a98fb3f70b5511e4b58700155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 14 05:52:26:367#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE00150000000100001A08#3448650000001158##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 14 05:52:27:159#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00140000000200001A08#3448650000001255##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 14 05:52:30:981#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000B0000000800001A08#3448650000001736##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 14 05:52:31:295#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000B0000000900001A08#3448650000001736##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 14 05:52:32:929#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00190000000200001A08#3448650000001906##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 14 05:52:39:477#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00220000000100001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [38] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:39:478#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00220000000200001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [38] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 05:52:39:806#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00010000000B00001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [90] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:39:806#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00010000000C00001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [90] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 05:52:42:471#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00010000000E00001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [237] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:42:471#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00010000000F00001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [237] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 14 05:52:43:713#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00220000000400001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [705] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:43:713#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE00220000000500001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [705] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 14 05:52:45:256#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00310000000200001A08#3448650000002019#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Application [46]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 14 05:52:46:052#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00010000001100001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [34] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:46:052#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00010000001200001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [34] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 65e61c7e
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 14 05:52:46:553#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00010000001400001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [189] ms on server process [3448650]: #

#2.0
#2014 07 14 05:52:46:553#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00010000001500001A08#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####B9050C970B5511E48B05000000349F4A#b9050c970b5511e48b05000000349f4a#b9050c970b5511e48b05000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [189] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 320081cc
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 320081cc
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 14 06:07:38:435#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003D0000000000001A08#3448650000001736##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##A98FB3F70B5511E4B58700155D336301#a98fb3f70b5511e4b58700155d336301#a98fb3f70b5511e4b58700155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 14 06:17:51:905#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000CE4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 14 06:18:05:469#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000C0000000100000CE4#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####440554db0b5911e4b2e700155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 06:18:05:470#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000C0000000300000CE4#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####440554db0b5911e4b2e700155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 14 06:18:12:393#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000B0000000200000CE4#3448650000000624##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####440554db0b5911e4b2e700155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 14 06:18:17:252#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE00150000000100000CE4#3448650000001061##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 14 06:18:19:341#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE00150000000300000CE4#3448650000001224##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 14 06:18:23:846#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00050000000400000CE4#3448650000001731##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 14 06:18:24:196#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE00050000000500000CE4#3448650000001731##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 14 06:18:25:505#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE00200000000100000CE4#3448650000001861##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 14 06:18:33:891#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00020000000700000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [129] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:33:892#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00020000000800000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [129] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 06:18:34:305#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00030000001100000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [102] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:34:305#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00030000001200000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [102] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 14 06:18:37:275#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000B0000000600000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [138] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:37:275#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE000B0000000700000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [138] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 14 06:18:38:268#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001C0000000400000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [925] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:38:268#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001C0000000500000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [925] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 14 06:18:39:786#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE00310000000200000CE4#3448650000002022#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Application [51]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 14 06:18:40:489#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00020000000A00000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [64] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:40:489#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE00020000000B00000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [64] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 115c79f7
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 14 06:18:40:976#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00020000000D00000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [85] ms on server process [3448650]: #

#2.0
#2014 07 14 06:18:40:976#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00020000000E00000CE4#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####56ECBB110B5911E4BCCE000000349F4A#56ecbb110b5911e4bcce000000349f4a#56ecbb110b5911e4bcce000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [85] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2a548583
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 2a548583
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 14 06:33:30:500#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003C0000000000000CE4#3448650000001731##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##440554DB0B5911E4B2E700155D336301#440554db0b5911e4b2e700155d336301#440554db0b5911e4b2e700155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 15 00:38:03:449#0-700#Warning#com.sap.engine.monitor.infoapp.SystemInfoFactory#
#BC-JAS-ADM-ADM#sap.com/tc~monitoring~systeminfo#C000AC1D32BE00460000000500000CE4#3448650000000004#sap.com/tc~monitoring~systeminfo#com.sap.engine.monitor.infoapp.SystemInfoFactory#Administrator#3##449F2E090B5911E49DD200155D336301#449f2e090b5911e49dd200155d336301#449f2e090b5911e49dd200155d336301#0#Thread[HTTP Worker [@1719972320],5,Dedicated_Application_Thread]#Plain##
unable to retrieve URL of central SLD
[EXCEPTION]
com.sap.security.core.server.destinations.api.DestinationException: [com.sap.ASJ.dest.sv0707] Application or service sap.com/tc~monitoring~systeminfo tried to access destination SLD_DataSupplier of type HTTP which does not currently exist in the destination service. You can create destinations in the NWA under Configuration Management-Infrastructure-Destinations.
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestination(DestinationServiceImpl.java:424)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSldUrl(SystemInfoFactory.java:501)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSystemInfo(SystemInfoFactory.java:426)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getInfo(SystemInfoFactory.java:259)
at com.sap.engine.monitor.infoapp.ComponentInfoServlet.doGet(ComponentInfoServlet.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)


#

#2.0
#2014 07 15 00:38:04:365#0-700#Warning#com.sap.engine.monitor.infoapp.SystemInfoFactory#
#BC-JAS-ADM-ADM#sap.com/tc~monitoring~systeminfo#C000AC1D32BE00490000000200000CE4#3448650000000004#sap.com/tc~monitoring~systeminfo#com.sap.engine.monitor.infoapp.SystemInfoFactory#Administrator#6##449F2E0C0B5911E4C84200155D336301#449f2e0c0b5911e4c84200155d336301#449f2e0c0b5911e4c84200155d336301#0#Thread[HTTP Worker [@424998779],5,Dedicated_Application_Thread]#Plain##
unable to retrieve URL of central SLD
[EXCEPTION]
com.sap.security.core.server.destinations.api.DestinationException: [com.sap.ASJ.dest.sv0707] Application or service sap.com/tc~monitoring~systeminfo tried to access destination SLD_DataSupplier of type HTTP which does not currently exist in the destination service. You can create destinations in the NWA under Configuration Management-Infrastructure-Destinations.
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestination(DestinationServiceImpl.java:424)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSldUrl(SystemInfoFactory.java:501)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSystemInfo(SystemInfoFactory.java:426)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getInfo(SystemInfoFactory.java:259)
at com.sap.engine.monitor.infoapp.SystemInfoServlet.doGet(SystemInfoServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)


#

#2.0
#2014 07 15 02:32:06:515#0-700#Warning#com.sap.engine.monitor.infoapp.SystemInfoFactory#
#BC-JAS-ADM-ADM#sap.com/tc~monitoring~systeminfo#C000AC1D32BE004F0000000200000CE4#3448650000000004#sap.com/tc~monitoring~systeminfo#com.sap.engine.monitor.infoapp.SystemInfoFactory#Administrator#11##449F5B740B5911E4B6CE00155D336301#449f5b740b5911e4b6ce00155d336301#449f5b740b5911e4b6ce00155d336301#0#Thread[HTTP Worker [@1325570410],5,Dedicated_Application_Thread]#Plain##
unable to retrieve URL of central SLD
[EXCEPTION]
com.sap.security.core.server.destinations.api.DestinationException: [com.sap.ASJ.dest.sv0707] Application or service sap.com/tc~monitoring~systeminfo tried to access destination SLD_DataSupplier of type HTTP which does not currently exist in the destination service. You can create destinations in the NWA under Configuration Management-Infrastructure-Destinations.
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestination(DestinationServiceImpl.java:424)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSldUrl(SystemInfoFactory.java:501)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSystemInfo(SystemInfoFactory.java:426)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getInfo(SystemInfoFactory.java:259)
at com.sap.engine.monitor.infoapp.ComponentInfoServlet.doGet(ComponentInfoServlet.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)


#

#2.0
#2014 07 15 02:32:07:306#0-700#Warning#com.sap.engine.monitor.infoapp.SystemInfoFactory#
#BC-JAS-ADM-ADM#sap.com/tc~monitoring~systeminfo#C000AC1D32BE00520000000200000CE4#3448650000000004#sap.com/tc~monitoring~systeminfo#com.sap.engine.monitor.infoapp.SystemInfoFactory#Administrator#14##449F8CCD0B5911E4B4BC00155D336301#449f8ccd0b5911e4b4bc00155d336301#449f8ccd0b5911e4b4bc00155d336301#0#Thread[HTTP Worker [@607375119],5,Dedicated_Application_Thread]#Plain##
unable to retrieve URL of central SLD
[EXCEPTION]
com.sap.security.core.server.destinations.api.DestinationException: [com.sap.ASJ.dest.sv0707] Application or service sap.com/tc~monitoring~systeminfo tried to access destination SLD_DataSupplier of type HTTP which does not currently exist in the destination service. You can create destinations in the NWA under Configuration Management-Infrastructure-Destinations.
at com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestination(DestinationServiceImpl.java:424)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSldUrl(SystemInfoFactory.java:501)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getSystemInfo(SystemInfoFactory.java:426)
at com.sap.engine.monitor.infoapp.SystemInfoFactory.getInfo(SystemInfoFactory.java:259)
at com.sap.engine.monitor.infoapp.SystemInfoServlet.doGet(SystemInfoServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)


#

#2.0
#2014 07 15 02:35:01:144#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00140000000500000CE4#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 15 02:35:01:145#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE00140000000600000CE4#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Deploy Parallel Stop Thread 2#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 15 02:35:01:270#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00570000000100000CE4#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 15 02:35:01:270#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00570000000200000CE4#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Deploy Parallel Stop Thread 4#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 15 02:35:01:835#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE00680000000000000CE4#3448650000001976##com.sap.engine.core.service630.container.ServiceWrapper####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 15 02:35:01:840#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00660000000100000CE4#3448650000001984##com.sap.engine.core.service630.container.ContainerObjectRegistry####4AE171070C0311E49C38000000349F4A#4ae171070c0311e49c38000000349f4a#4ae171070c0311e49c38000000349f4a#0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 15 02:35:01:960#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006B0000000100000CE4#3448650000001950##com.sap.engine.core.service630.container.ContainerObjectRegistry#####4ae171070c0311e49c38000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 15 02:35:02:136#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003C0000000200000CE4#3448650000001731##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###440554db0b5911e4b2e700155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 15 02:35:02:139#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE00710000000100000CE4#3448650000001688##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###440554db0b5911e4b2e700155d336301##0#Application [27]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 15 02:35:05:176#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE00740000000000000CE4#3448650000003659##com.sap.engine.core.service630.container.ServiceWrapper#####4ae171070c0311e49c38000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 15 02:35:05:226#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE00750000000000000CE4#3448650000003625##com.sap.engine.core.service630.container.ServiceWrapper#####4ae171070c0311e49c38000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 15 02:35:05:323#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE00780000000000000CE4#3448650000003810##com.sap.engine.core.service630.container.ContainerObjectRegistry#####4ae171070c0311e49c38000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 15 02:35:05:323#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE00790000000000000CE4#3448650000003804##com.sap.engine.core.service630.container.ServiceWrapper#####4ae171070c0311e49c38000000349f4a##0#Service Stopper [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 15 02:35:05:328#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE007A0000000100000CE4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####440554db0b5911e4b2e700155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 15 02:35:05:328#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE007B0000000100000CE4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####440554db0b5911e4b2e700155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 15 02:35:05:328#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE007A0000000200000CE4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####440554db0b5911e4b2e700155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 15 02:35:05:328#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE007B0000000200000CE4#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####440554db0b5911e4b2e700155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 15 02:35:08:609#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE00080000000300000CE4#3448650000001662##com.sap.engine.services.wsrm#####440554db0b5911e4b2e700155d336301##0#System [35]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 15 02:56:24:015#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000108C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.RemoveDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 15 02:56:42:268#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000010000108C#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####4b41efd00c0611e4ba2300155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 15 02:56:42:269#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000030000108C#3448650000000570##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####4b41efd00c0611e4ba2300155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 15 02:56:50:062#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE000A000000020000108C#3448650000000624##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####4b41efd00c0611e4ba2300155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 15 02:56:54:793#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#tc~je~webservices~srv#C000AC1D32BE000D000000030000108C#3448650000001010##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 15 02:56:57:936#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE0005000000030000108C#3448650000001211##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 15 02:57:03:473#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0010000000060000108C#3448650000001682##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 15 02:57:03:801#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0010000000070000108C#3448650000001682##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 15 02:57:05:822#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000B0000000B0000108C#3448650000001852##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 15 02:57:15:090#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001D000000010000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [71] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:15:091#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE001D000000020000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [71] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 15 02:57:15:525#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0005000000090000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [102] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:15:525#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE00050000000A0000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [102] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 15 02:57:18:688#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00050000000C0000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [106] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:18:688#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE00050000000D0000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [106] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 15 02:57:19:837#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001D000000040000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1105] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:19:837#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE001D000000050000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [1105] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 15 02:57:21:272#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE002C000000020000108C#3448650000001989#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Application [51]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 15 02:57:22:166#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0013000000080000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [30] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:22:166#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0013000000090000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 4#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [30] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 2eac6923
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
   [sap.com/tc~js~nwa~cfg~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 15 02:57:22:752#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00050000000F0000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [84] ms on server process [3448650]: #

#2.0
#2014 07 15 02:57:22:752#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE0005000000100000108C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####6188246B0C0611E483C1000000349F4A#6188246b0c0611e483c1000000349f4a#6188246b0c0611e483c1000000349f4a#0#Deploy Parallel Start Thread 1#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [84] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5d34de68
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 5d34de68
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 15 03:12:08:437#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003F000000000000108C#3448650000001682##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Application [44]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 16 02:48:28:933#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE004D000000000000108C#3448650000026171##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()####444848D60C0611E483BB00155D336301#444848d60c0611e483bb00155d336301#444848d60c0611e483bb00155d336301#0#SAP J2EE Engine|MS Socket Listener#Plain##
java.net.SocketException: Software caused connection abort: recv failed#

#2.0
#2014 07 16 02:48:28:933#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE004D000000010000108C#3448650000026171##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()####444848D60C0611E483BB00155D336301#444848d60c0611e483bb00155d336301#444848d60c0611e483bb00155d336301#0#SAP J2EE Engine|MS Socket Listener#Plain##
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:513)
at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:184)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1858)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.receiveRawMessage(MSConnectionImpl.java:46)
at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:101)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
#

#2.0
#2014 07 16 02:48:28:974#0-700#Error#com.sap.engine.core.locking.impl3.LockingManagerImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004E000000000000108C###com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#Guest#0##56F675CF0CCE11E4AB86000000349F4A#56f675cf0cce11e4ab86000000349f4a#56f675cf0cce11e4ab86000000349f4a#0#Thread[SAPEngine_EnquReader,5,main]#Plain##
EncomiHandle.ReceiveMessage(): receive failed (Software caused connection abort: recv failed) closing connection)#

#2.0
#2014 07 16 02:48:28:981#0-700#Error#com.sap.engine.core.locking.impl3.LockingManagerImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004E000000010000108C###com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#Guest#0##56F675CF0CCE11E4AB86000000349F4A#56f675cf0cce11e4ab86000000349f4a#56f675cf0cce11e4ab86000000349f4a#0#Thread[SAPEngine_EnquReader,5,main]#Plain##
EncomiHandle.Connect(): connection 1: failed to connect to host INPUNEME01 on port 3201 1 times, No route to host: connect()--> Check the status of the enqueue server and your network connection#

#2.0
#2014 07 16 02:48:28:981#0-700#Error#com.sap.engine.core.locking.impl3.LockingManagerImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE004E000000020000108C###com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#Guest#0##56F675CF0CCE11E4AB86000000349F4A#56f675cf0cce11e4ab86000000349f4a#56f675cf0cce11e4ab86000000349f4a#0#Thread[SAPEngine_EnquReader,5,main]#Plain##
ReadRunnable.tryToReconnect(): connection 1 failed to connect to server 1 times, trying to reconnect endlessly  --> Check the status of the enqueue server#

#2.0
#2014 07 16 02:48:29:291#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000050000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".#

#2.0
#2014 07 16 02:48:29:291#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000060000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:48:29:292#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000080000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 16 02:48:29:292#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000090000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:48:29:294#0-700#Error#com.sap.tc.cbs.server.rt.sync.AccessOrc#
#BC-CTS-CBS#tc.CBS.Service#C000AC1D32BE001A0000000B0000108C#3448650000001207##com.sap.tc.cbs.server.rt.sync.AccessOrc####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
Access orchestrator failure
[EXCEPTION]
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:A database error occurred while processing the entries in the access queue.
Original Cause: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:563)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
... 3 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
... 6 more

#

Former Member
0 Kudos

part 8

======================================================

#2.0
#2014 07 16 02:48:29:295#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A0000000D0000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".#

#2.0
#2014 07 16 02:48:29:295#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A0000000E0000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "SELECT * FROM "CBS_ACCESSQUEUE" ORDER BY 2,1".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:48:29:296#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000100000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 16 02:48:29:297#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE001A000000110000108C#3448650000001207##com.sap.sql.jdbc.direct.DirectPreparedStatement####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:48:29:298#0-700#Error#com.sap.tc.cbs.server.rt.sync.AccessOrc#
#BC-CTS-CBS#tc.CBS.Service#C000AC1D32BE001A000000130000108C#3448650000001207##com.sap.tc.cbs.server.rt.sync.AccessOrc####4B41EFD00C0611E4BA2300155D336301#4b41efd00c0611e4ba2300155d336301#4b41efd00c0611e4ba2300155d336301#0#Thread[CBS AccessQueue Orchestrator,5,SystemThreadGroup]#Plain##
Access orchestrator failure
[EXCEPTION]
com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:A database error occurred while processing the entries in the access queue.
Original Cause: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:563)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.processAccessQueue(AccessOrc.java:164)
at com.sap.tc.cbs.server.rt.sync.AccessOrc.run(AccessOrc.java:75)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:317)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:241)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)
at com.sap.tc.cbs.server.db.impl.AdminDB.processAccessQueue(AdminDB.java:534)
... 3 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:102)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:313)
... 6 more

#

#2.0
#2014 07 16 02:54:51:674#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000010000108C#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "INSERT INTO "BC_MON_AGREGATES" ("ID","MONITOR_ID","START_TIME","AGR_INTERVAL","AVG_VALUE","STD_DEVIATION","MIN_VALUE","MAX_VALUE","COUNTS") VALUES (?,?,?,?,?,?,?,?,?)".#

#2.0
#2014 07 16 02:54:51:675#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000020000108C#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "INSERT INTO "BC_MON_AGREGATES" ("ID","MONITOR_ID","START_TIME","AGR_INTERVAL","AVG_VALUE","STD_DEVIATION","MIN_VALUE","MAX_VALUE","COUNTS") VALUES (?,?,?,?,?,?,?,?,?)".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeWrappedBytes(IOBuffer.java:3257)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeInt(IOBuffer.java:3167)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeRPCInt(IOBuffer.java:3693)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.buildExecParams(SQLServerPreparedStatement.java:595)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doPrepExec(SQLServerPreparedStatement.java:625)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(SQLServerPreparedStatement.java:1282)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtBatchExecCmd.doExecute(SQLServerPreparedStatement.java:1209)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1173)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:268)
at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:300)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1226)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.executeInsert(DBAgregationWriter.java:211)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:204)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:676#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
com.sap.sql_0001#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000040000108C#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="null", message="The connection is closed.".#

#2.0
#2014 07 16 02:54:51:676#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000050000108C#3448650000000001##com.sap.sql.jdbc.direct.DirectPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
SQL error occurred: code=0, state="<null>", message="The connection is closed.".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.checkClosed(SQLServerStatement.java:978)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.cancel(SQLServerStatement.java:1070)
at com.sap.sql.jdbc.basic.BasicStatement.cancel(BasicStatement.java:105)
at com.sap.sql.jdbc.direct.DirectStatement.cancelStatement(DirectStatement.java:903)
at com.sap.sql.jdbc.common.AbstractCommonStatement.cancelStatement(AbstractCommonStatement.java:326)
at com.sap.sql.jdbc.common.CommonConnectionImpl.cancelStatements(CommonConnectionImpl.java:1244)
at com.sap.sql.jdbc.common.CommonPooledConnection.cancelStatements(CommonPooledConnection.java:818)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:1065)
at com.sap.sql.connect.datasource.DBDataSourceImpl.interruptExecution(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.interruptExecution(CreatedObjectsPool.java:452)
at com.sap.sql.connect.pool.Pool.setAndExecuteAdminAction(Pool.java:1068)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionErrorOccurred(DBDataSourceImpl.java:444)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:1106)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionErrorOccurred(CommonPooledConnection.java:410)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionErrorOccurred(DirectPooledConnection.java:888)
at com.sap.sql.jdbc.direct.DirectPooledConnection.connectionHandleErrorOccurred(DirectPooledConnection.java:387)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:998)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1229)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.executeInsert(DBAgregationWriter.java:211)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:204)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:677#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0051000000060000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error
OpenSQLExceptionCategories: [RECOVERABLE]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1229)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1046)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.executeInsert(DBAgregationWriter.java:211)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:204)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeWrappedBytes(IOBuffer.java:3257)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeInt(IOBuffer.java:3167)
at com.microsoft.sqlserver.jdbc.TDSWriter.writeRPCInt(IOBuffer.java:3693)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.buildExecParams(SQLServerPreparedStatement.java:595)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doPrepExec(SQLServerPreparedStatement.java:625)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(SQLServerPreparedStatement.java:1282)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtBatchExecCmd.doExecute(SQLServerPreparedStatement.java:1209)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1173)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:268)
at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:300)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1226)
... 8 more

#

#2.0
#2014 07 16 02:54:51:679#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000080000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 02:54:51:679#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000090000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:680#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE00510000000A0000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:680#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00510000000C0000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 02:54:51:680#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE00510000000D0000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:681#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE00510000000E0000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:681#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000100000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 02:54:51:682#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000110000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:682#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0051000000120000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:683#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000140000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 02:54:51:683#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000150000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:683#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0051000000160000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:684#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000180000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 02:54:51:684#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0051000000190000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:685#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE00510000001A0000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.getSetterDispatcher(CommonPreparedStatement.java:149)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setInt(CommonPreparedStatement.java:479)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setInt(PreparedStatementWrapper.java:373)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.writeAgregate(DBAgregationWriter.java:195)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter$DBWriterJob.run(DBAgregationWriter.java:98)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 02:54:51:686#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE00510000001B0000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Too many reconnection attempts. Database access unavailable#

#2.0
#2014 07 16 02:54:51:686#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE00510000001C0000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-32,5,SystemThreadGroup]#Plain##
Monitoring history database writer disabled#

#2.0
#2014 07 16 02:56:15:985#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE0052000000010000108C###com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawRequest()#Guest#0##6D52B2F20CCF11E49060000000349F4A#6d52b2f20ccf11e49060000000349f4a#6d52b2f20ccf11e49060000000349f4a#0#Thread[SAP J2EE Engine|MS Ping Thread,5,main]#Plain##
java.lang.InterruptedException: No answer in 15000 msec. Listenerkey: 13077, errorKey: 13077#

#2.0
#2014 07 16 02:56:15:985#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE0052000000020000108C###com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawRequest()#Guest#0##6D52B2F20CCF11E49060000000349F4A#6d52b2f20ccf11e49060000000349f4a#6d52b2f20ccf11e49060000000349f4a#0#Thread[SAP J2EE Engine|MS Ping Thread,5,main]#Plain##
java.lang.InterruptedException: No answer in 15000 msec. Listenerkey: 13077, errorKey: 13077
at com.sap.engine.core.cluster.impl6.ms.MSNotificationListener.WaitForReply(MSNotificationListener.java:156)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawRequest(MSRawConnection.java:1304)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendRawRequest(MSConnectionImpl.java:46)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection$MSPingRunner.niPingAndWait(MSRawConnection.java:2650)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection$MSPingRunner.run(MSRawConnection.java:2591)
at java.lang.Thread.run(Thread.java:722)
#

#2.0
#2014 07 16 02:56:15:986#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE0052000000030000108C###com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendPingAndWait()#Guest#0##6D52B2F20CCF11E49060000000349F4A#6d52b2f20ccf11e49060000000349f4a#6d52b2f20ccf11e49060000000349f4a#0#Thread[SAP J2EE Engine|MS Ping Thread,5,main]#Plain##
com.sap.engine.frame.cluster.ClusterException: Client MSG_SERVER did not return a response in the specified timeout of 15000 ms.#

#2.0
#2014 07 16 02:56:15:986#0-700#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C000AC1D32BE0052000000040000108C###com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendPingAndWait()#Guest#0##6D52B2F20CCF11E49060000000349F4A#6d52b2f20ccf11e49060000000349f4a#6d52b2f20ccf11e49060000000349f4a#0#Thread[SAP J2EE Engine|MS Ping Thread,5,main]#Plain##
com.sap.engine.frame.cluster.ClusterException: Client MSG_SERVER did not return a response in the specified timeout of 15000 ms.
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawRequest(MSRawConnection.java:1308)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendRawRequest(MSConnectionImpl.java:46)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection$MSPingRunner.niPingAndWait(MSRawConnection.java:2650)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection$MSPingRunner.run(MSRawConnection.java:2591)
at java.lang.Thread.run(Thread.java:722)
#

#2.0
#2014 07 16 03:09:19:334#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0053000000010000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..#

#2.0
#2014 07 16 03:09:19:335#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedStatement#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE0053000000020000108C#3448650000000001##com.sap.sql.jdbc.common.CommonPreparedStatement####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
Exception of type com.sap.sql.log.OpenSQLException caught: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error..
[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1030)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.deleteAgregations(DBAgregationWriter.java:224)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.cleanOldAgregates(PersistenceManager.java:188)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.access$100(PersistenceManager.java:17)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager$AgregationCleaner.run(PersistenceManager.java:67)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 03:09:19:335#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0053000000030000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
Monitoring history database writer disabled#

#2.0
#2014 07 16 03:09:19:335#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0053000000040000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##
History persistence cleaner thread had stopped. DB writing has been disabled#

#2.0
#2014 07 16 03:09:19:335#0-700#Error#com.sap.engine.library.monitor.history.persistence.PersistenceManager#
#BC-JAS-ADM-MON#monitortree#C000AC1D32BE0053000000050000108C#3448650000000001##com.sap.engine.library.monitor.history.persistence.PersistenceManager####61877F130C0611E4A45A000000349F4A#61877f130c0611e4a45a000000349f4a#61877f130c0611e4a45a000000349f4a#0#Thread[Thread-33,5,SystemThreadGroup]#Plain##

[EXCEPTION]
com.sap.sql.log.OpenSQLException: Statement object com.sap.sql.jdbc.common.CommonPreparedStatement@37dfe310 has already been closed because of a fatal connection error.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.common.AbstractCommonStatement.validate(AbstractCommonStatement.java:641)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:1030)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:299)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeBatch(PreparedStatementWrapper.java:307)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.flush(DBAgregationWriter.java:244)
at com.sap.engine.library.monitor.history.persistence.DBAgregationWriter.deleteAgregations(DBAgregationWriter.java:224)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.cleanOldAgregates(PersistenceManager.java:188)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager.access$100(PersistenceManager.java:17)
at com.sap.engine.library.monitor.history.persistence.PersistenceManager$AgregationCleaner.run(PersistenceManager.java:67)
at java.lang.Thread.run(Thread.java:722)

#

#2.0
#2014 07 16 04:18:45:394#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0054000000030000108C#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####F340503A0CDA11E48322000000349F4A#f340503a0cda11e48322000000349f4a#f340503a0cda11e48322000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 16 04:18:45:401#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0054000000040000108C#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####F340503A0CDA11E48322000000349F4A#f340503a0cda11e48322000000349f4a#f340503a0cda11e48322000000349f4a#0#Deploy Parallel Stop Thread 5#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 04:18:45:835#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0058000000010000108C#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####F340503A0CDA11E48322000000349F4A#f340503a0cda11e48322000000349f4a#f340503a0cda11e48322000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [2] ms on server process [3448650]: #

#2.0
#2014 07 16 04:18:45:836#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0058000000020000108C#3448650000000005##com.sap.engine.services.deploy.server.TransactionManager####F340503A0CDA11E48322000000349F4A#f340503a0cda11e48322000000349f4a#f340503a0cda11e48322000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [2] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 04:18:46:175#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE006D000000000000108C#3448650000001994##com.sap.engine.core.service630.container.ServiceWrapper####F340503A0CDA11E48322000000349F4A#f340503a0cda11e48322000000349f4a#f340503a0cda11e48322000000349f4a#0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 16 04:18:46:210#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006E000000010000108C#3448650000002034##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f340503a0cda11e48322000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 04:18:46:215#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0070000000010000108C#3448650000001981##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f340503a0cda11e48322000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 04:18:46:381#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE0074000000010000108C#3448650000001667##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###4b41efd00c0611e4ba2300155d336301##0#Application [40]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.0
#2014 07 16 04:18:46:381#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE003F000000020000108C#3448650000001682##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###4b41efd00c0611e4ba2300155d336301##0#Application [44]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 16 04:18:49:521#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE0076000000000000108C#3448650000003769##com.sap.engine.core.service630.container.ServiceWrapper#####f340503a0cda11e48322000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 16 04:18:49:521#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE0077000000000000108C#3448650000003854##com.sap.engine.core.service630.container.ServiceWrapper#####f340503a0cda11e48322000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 16 04:18:49:648#0-700#Error#com.sap.sql.jdbc.direct.DirectConnection#
com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE007B000000010000108C#3448650000003947##com.sap.sql.jdbc.direct.DirectConnection#####f340503a0cda11e48322000000349f4a##0#Service Stopper [dbpool]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "COMMIT".#

#2.0
#2014 07 16 04:18:49:649#0-700#Error#com.sap.sql.jdbc.direct.DirectConnection#
#BC-JAS-PER-SQL#opensqlkernel#C000AC1D32BE007B000000020000108C#3448650000003947##com.sap.sql.jdbc.direct.DirectConnection#####f340503a0cda11e48322000000349f4a##0#Service Stopper [dbpool]#Plain##
FATAL SQL error occurred on connection INPUNEME01\\ME2:ME2:SAPME2DB: code=0, state="08S01", message="Connection reset by peer: socket write error";
SQL statement is "COMMIT".
[EXCEPTION]
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6120)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6106)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$1ConnectionCommand.doExecute(SQLServerConnection.java:1756)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(SQLServerConnection.java:1761)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.commit(SQLServerConnection.java:1938)
at com.sap.sql.jdbc.basic.BasicConnection.commit(BasicConnection.java:74)
at com.sap.sql.jdbc.direct.DirectConnection.commit(DirectConnection.java:428)
at com.sap.sql.jdbc.common.CommonPooledConnection.cleanup(CommonPooledConnection.java:713)
at com.sap.sql.connect.datasource.DBDataSourceImpl.cleanup(DBDataSourceImpl.java:1079)
at com.sap.sql.connect.datasource.DBDataSourceImpl.cleanup(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.cleanup(CreatedObjectsPool.java:409)
at com.sap.sql.connect.pool.Pool.release(Pool.java:526)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:875)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionClosed(DBDataSourceImpl.java:422)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionClosed(CommonPooledConnection.java:1053)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionHandleClosed(CommonPooledConnection.java:421)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:1329)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:366)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.commonDestroy(LocalTXManagedConnectionImpl.java:257)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.destroy(LocalTXManagedConnectionImpl.java:119)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroyConnections(ConnectionHashSet.java:542)
at com.sap.engine.services.connector.jca.ConnectionHashSet.clear(ConnectionHashSet.java:530)
at com.sap.engine.services.connector.jca.AdapterCache.close(AdapterCache.java:130)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:297)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:317)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.stopDataSource(ContainerImpl.java:1435)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.destroyDefaultDataSource(ContainerImpl.java:933)
at com.sap.engine.services.dbpool.PoolFrame.stop(PoolFrame.java:150)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 04:18:49:650#0-700#Error#com.sap.engine.services.connector.jca.ConnectionHashSet#
com.sap.ASJ.conn.000130#BC-JAS-TRH#connector#C000AC1D32BE007B000000030000108C#3448650000003947##com.sap.engine.services.connector.jca.ConnectionHashSet#####f340503a0cda11e48322000000349f4a##0#Service Stopper [dbpool]#Plain##
ConnectionHashSet, Exception:
[EXCEPTION]
java.lang.NullPointerException: while trying to invoke the method com.sap.sql.jdbc.ConnectionContext.getConnectionID() of an object loaded from field com.sap.sql.jdbc.common.CommonPooledConnection.connContext of an object loaded from local variable 'this'
at com.sap.sql.jdbc.common.CommonPooledConnection.destroyConnection(CommonPooledConnection.java:832)
at com.sap.sql.connect.datasource.DBDataSourceImpl.closePooledConnection(DBDataSourceImpl.java:698)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:1004)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:43)
at com.sap.sql.connect.pool.CreatedObjectsPool.destroy(CreatedObjectsPool.java:138)
at com.sap.sql.connect.pool.Pool.release(Pool.java:537)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:875)
at com.sap.sql.connect.datasource.DBDataSourceImpl.connectionClosed(DBDataSourceImpl.java:422)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionClosed(CommonPooledConnection.java:1053)
at com.sap.sql.jdbc.common.CommonPooledConnection.connectionHandleClosed(CommonPooledConnection.java:421)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:1329)
at com.sap.sql.jdbc.common.CommonConnectionImpl.close(CommonConnectionImpl.java:366)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.commonDestroy(LocalTXManagedConnectionImpl.java:257)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.destroy(LocalTXManagedConnectionImpl.java:119)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroyConnections(ConnectionHashSet.java:542)
at com.sap.engine.services.connector.jca.ConnectionHashSet.clear(ConnectionHashSet.java:530)
at com.sap.engine.services.connector.jca.AdapterCache.close(AdapterCache.java:130)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:297)
at com.sap.engine.services.connector.ResourceObjectFactory.stopConnectionFactory(ResourceObjectFactory.java:317)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.stopDataSource(ContainerImpl.java:1435)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.destroyDefaultDataSource(ContainerImpl.java:933)
at com.sap.engine.services.dbpool.PoolFrame.stop(PoolFrame.java:150)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 04:18:49:653#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE007C000000000000108C#3448650000003957##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f340503a0cda11e48322000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 04:18:49:676#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE007E000000010000108C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####4b41efd00c0611e4ba2300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 16 04:18:49:676#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE007D000000010000108C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####4b41efd00c0611e4ba2300155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]#

#2.0
#2014 07 16 04:18:49:676#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE007E000000020000108C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####4b41efd00c0611e4ba2300155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 04:18:49:676#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE007D000000020000108C#3448650000000005##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####4b41efd00c0611e4ba2300155d336301##0#Thread[Thread-16,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-16,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 04:18:52:986#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE0016000000060000108C#3448650000001640##com.sap.engine.services.wsrm#####4b41efd00c0611e4ba2300155d336301##0#System [27]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:11:53:439#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000087C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:12:01:104#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000010000087C#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####610e7edf0ce211e4c93a00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbschemacontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 16 05:12:01:104#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#
com.sap.ASJ-dpl.ds-000463#N/A#tc~je~dbcontainer~srv#C000AC1D32BE000B000000030000087C#3448650000000567##com.sap.engine.services.deploy.server.utils.container.ContainerInfoValidator#####610e7edf0ce211e4c93a00155d336301##0#Event Processor [tc~je~dbcontainer~srv]#Plain##

Warnings:
   The [dbcontentcontainer] container reports that is registered from [null] service, but really it is registered by [tc~je~dbcontainer~srv].
Solution: Please contact the container holder to fix these warnings.#

#2.0
#2014 07 16 05:12:06:111#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#security#C000AC1D32BE0003000000020000087C#3448650000000621##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#####610e7edf0ce211e4c93a00155d336301##0#Event Processor [security]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [com.sap.security.login-modules]. Different properties are: [
The Priority property of container info is different. XML Container Priority is [0] and Real Container Priority is [100].
The ClassLoad Priority property of container info is different. XML Container Class Load Priority is [0] and Real Container Class Load Priority is [100].]#

#2.0
#2014 07 16 05:12:13:325#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-RT#tc~je~webservices~srv#C000AC1D32BE000A000000020000087C#3448650000001071##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Event Processor [tc~je~webservices~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [webservices_container]. Different properties are: [
The isNeedStartInitially property of container info is different. XML Container isNeedStartInitially is [false] and Real Container isNeedStartInitially is [true].]#

#2.0
#2014 07 16 05:12:17:119#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#N/A#com.sap.portal.prt.sapj2ee#C000AC1D32BE000A000000040000087C#3448650000001209##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Service Runner [com.sap.portal.prt.sapj2ee]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [PortalRuntimeContainer]. Different properties are: [
The J2EEModuleName property of container info is different. XML J2EE Module name is [null] and Real J2EE Module name is [java].]#

#2.0
#2014 07 16 05:12:21:653#0-700#Error#com.sap.aii.af.service.alerting.Connection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000F000000070000087C#3448650000001686##com.sap.aii.af.service.alerting.Connection.newJcoClientForCentralMonitoringServer()####610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.0
#2014 07 16 05:12:21:986#0-700#Error#com.sap.aii.af.service.scheduler.SelfManagedJobBroker#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE000F000000080000087C#3448650000001686##com.sap.aii.af.service.scheduler.SelfManagedJobBroker.JobDispatcherClient.getDestinationURL()####610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Service Runner [com.sap.aii.af.svc]#Plain##
failed to obtain the target URL#

#2.0
#2014 07 16 05:12:23:482#0-700#Warning#com.sap.engine.services.deploy.server.utils.container.ContainerWrapper#
com.sap.ASJ.dpl_ds.002011#BC-ESI-WS-JAV-CFG#tc~esi~esp~srv#C000AC1D32BE000C000000040000087C#3448650000001869##com.sap.engine.services.deploy.server.utils.container.ContainerWrapper####610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Service Runner [tc~esi~esp~srv]#Plain##
The container info object, created from containers-info.xml and the one returned from getContainerInfo() method are not the same. Container name is: [ConfigurationsContainer]. Different properties are: [
The FileNames property of container info is different. XML Container FileNames is [[sca-contribution.xml]] and Real Container FileNames is [[META-INF/sca-contribution.xml]].]#

#2.0
#2014 07 16 05:12:30:194#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000A000000120000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [61] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:30:195#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE000A000000130000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 5#Plain##
Global [startApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [61] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 05:12:30:358#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001B000000040000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [25] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:30:359#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE001B000000050000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [25] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 05:12:32:641#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001B000000070000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [43] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:32:641#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-SOV#sap.com/tc~lm~itsam~ui~tspreg~app#C000AC1D32BE001B000000080000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 3#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~ui~tspreg~app] finished with non-critical warnings for [43] ms on server process [3448650]: [
>>> Warnings <<<
1). com.sap.ASJ.web.000607 (Failed in component: sap.com/tc~lm~itsam~ui~tspreg~app, BC-NWA-SOV) Initialization of servlet [TechSysProReg] failed. Check init() method of servlet. Error is: [java.lang.NoClassDefFoundError: com/sap/sld/api/std/tech/SLD_ApplicationSystem]]#

#2.0
#2014 07 16 05:12:34:141#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0017000000030000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [850] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:34:142#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-XI-IS-WKB#sap.com/com.sap.xi.mdt.soa#C000AC1D32BE0017000000040000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.mdt.soa] finished with non-critical warnings for [850] ms on server process [3448650]: [
>>> Warnings <<<
1). Application sap.com/com.sap.xi.rwb is not deployed, but resolving of application sap.com/com.sap.xi.mdt.soa continues because it has weak reference to this application.]#

#2.0
#2014 07 16 05:12:35:556#0-700#Warning#com.sap.archtech.daservice#
#BC-ILM-DAS#sap.com/tc~TechSrv~XML_DAS#C000AC1D32BE0031000000020000087C#3448650000001975#sap.com/tc~TechSrv~XML_DAS#com.sap.archtech.daservice#Administrator#0##719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Application [49]#Plain##
MasterMethod: An error occurred during the System Landscape Directory synchronization: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
[EXCEPTION]
com.sap.sldserv.exception.SldServiceRuntimeException: Getting WBEMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:158)
at com.sap.archtech.daservice.commands.MasterMethod.synchronizeSystemLandscapeDirectory(MasterMethod.java:430)
at com.sap.archtech.daservice.DASmain.init(DASmain.java:229)
at javax.servlet.GenericServlet.init(GenericServlet.java:270)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:528)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:1129)
at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:282)
at com.sap.engine.services.deploy.server.utils.concurrent.impl.CleanRunnable.run(CleanRunnable.java:54)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getWbemClient(SldApplicationService.java:109)
... 14 more

#

#2.0
#2014 07 16 05:12:36:860#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0017000000060000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [63] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:36:861#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-UIF#sap.com/tc~js~nwa~nav_engine~ear#C000AC1D32BE0017000000070000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~js~nwa~nav_engine~ear] finished with non-critical warnings for [63] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.js.nwa.nav_engine.init.NavEngineInitServlet
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~js~nwa~nav_engine~ear]
Loader hash code: 1fea9cd8
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~js~nwa~cfg~ear]
   [sap.com/tc~lm~webadmin~mainframe~persist~ear]
Resources:
   C:\\usr\\sap\\ME2\\J00\\j2ee\\cluster\\apps\\sap.com\\tc~js~nwa~nav_engine~ear\\servlet_jsp\\sap.com~tc~js~nwa~nav_engine~war\\root\\WEB-INF\\classes
---------------------------------------------------------------].]#

#2.0
#2014 07 16 05:12:37:072#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE0017000000090000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [29] ms on server process [3448650]: #

#2.0
#2014 07 16 05:12:37:072#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-NWA-INC-DEV#sap.com/tc~lm~itsam~nwa~tools~ear#C000AC1D32BE00170000000A0000087C#3448650000000001##com.sap.engine.services.deploy.server.TransactionManager####719F9F9A0CE211E4A07B000000349F4A#719f9f9a0ce211e4a07b000000349f4a#719f9f9a0ce211e4a07b000000349f4a#0#Deploy Parallel Start Thread 2#Plain##
Global [startApp] operation of application [sap.com/tc~lm~itsam~nwa~tools~ear] finished with non-critical warnings for [29] ms on server process [3448650]: [
>>> Warnings <<<
1). Cannot load servlet [com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean]. Error is: [java.lang.ClassNotFoundException: com.sap.tc.lm.itsam.nwa.tools.web.example.regservlet.RegisterExampleMbean
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 1373e9cc
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].
2). Cannot load servlet [com.sap.lm.itsam.testmbean.TestMbeans]. Error is: [java.lang.ClassNotFoundException: com.sap.lm.itsam.testmbean.TestMbeans
------------------------- Loader Info -------------------------
ClassLoader name: [sap.com/tc~lm~itsam~nwa~tools~ear]
Loader hash code: 1373e9cc
Living status: alive
Direct parent loaders:
   [system:Frame]
   [interface:webservices]
   [interface:cross]
   [interface:security]
   [interface:transactionext]
   [library:webservices_lib]
   [library:opensql]
   [library:jms]
   [library:ejb20]
   [service:p4]
   [service:ejb]
   [service:servlet_jsp]
   [sap.com/tc~lm~itsam~ui~application~api]
No resources !
---------------------------------------------------------------].]#

#2.0
#2014 07 16 05:21:35:276#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0041000000010000087C#3448650000000002##com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#6##63AE70E457A51000C1A9C201EA60043E#63ae70e457a51000c1a9c201ea60043e#63ae70e457a51000c1a9c201ea60043e#0#Thread[RMI/IIOP Worker [0],5,Dedicated_Application_Thread]#Plain##
Cannot get installed license key. KEY: "0002LK0003ME20011H07668465420015Maintenance_MSS".#

#2.0
#2014 07 16 05:21:35:284#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0041000000020000087C#3448650000000002##com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#6##63AE70E457A51000C1A9C201EA60043E#63ae70e457a51000c1a9c201ea60043e#63ae70e457a51000c1a9c201ea60043e#0#Thread[RMI/IIOP Worker [0],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011H07668465420015Maintenance_MSS could not be found in the configuration "Licensing".#

#2.0
#2014 07 16 05:21:35:285#0-700#Warning#com.sap.engine.core.licensing.impl0.PersistenceImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0041000000030000087C#3448650000000002##com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(java.lang.String)#Administrator#6##63AE70E457A51000C1A9C201EA60043E#63ae70e457a51000c1a9c201ea60043e#63ae70e457a51000c1a9c201ea60043e#0#Thread[RMI/IIOP Worker [0],5,Dedicated_Application_Thread]#Plain##
com.sap.engine.frame.core.configuration.NameNotFoundException: A config entry with the name "0002LK0003ME20011H07668465420015Maintenance_MSS could not be found in the configuration "Licensing".
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:1104)
at com.sap.engine.core.licensing.impl0.PersistenceImpl.getKey(PersistenceImpl.java:207)
at com.sap.security.core.server.likey.LicenseChecker.check(LicenseChecker.java:379)
at com.sap.engine.core.licensing.impl0.LicensingManagerImpl.checkLicense(LicensingManagerImpl.java:147)
at com.sap.engine.services.licensing.LicensingProcessor.checkLicense(LicensingProcessor.java:209)
at com.sap.engine.services.licensing.LicensingRuntimeInterfaceImpl.checkLicense(LicensingRuntimeInterfaceImpl.java:90)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementService_Impl.checkLicense(SAP_ITSAMJ2eeLicensingManagementService_Impl.java:201)
at com.sap.engine.services.licensing.itsam.SAP_ITSAMJ2eeLicensingManagementServiceWrapper.invoke(SAP_ITSAMJ2eeLicensingManagementServiceWrapper.java:311)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:468)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:547)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:365)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:289)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:154)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:103)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:462)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.0
#2014 07 16 05:21:35:285#0-700#Warning#com.sap.engine.core.licensing.impl0.LicensingManagerImpl#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0041000000050000087C#3448650000000002##com.sap.engine.core.licensing.impl0.LicensingManagerImpl.checkLicense(String)#Administrator#6##63AE70E457A51000C1A9C201EA60043E#63ae70e457a51000c1a9c201ea60043e#63ae70e457a51000c1a9c201ea60043e#0#Thread[RMI/IIOP Worker [0],5,Dedicated_Application_Thread]#Plain##
The installed license for software product "Maintenance_MSS" is NOT valid. The concerned component may only run with restricted functionality. In case of "J2EE-Engine" the system will shut down.#

#2.0
#2014 07 16 05:27:24:323#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0045000000000000087C#3448650000001686##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0##610E7EDF0CE211E4C93A00155D336301#610e7edf0ce211e4c93a00155d336301#610e7edf0ce211e4c93a00155d336301#0#Application [40]#Plain##
TrexException - couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : TrexException in Method: TrexManager: getTrexConfiguration(). Couldn't get Trex configuration for index. Message: Class: com.sap.aii.af.service.trex.TrexException : SLDException in Method: Util: getIndex(). Couldn't get the SLD instance name. Therefore the index ID couldn't be inititialized. - Message: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties); To-String: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties).#

#2.0
#2014 07 16 05:33:08:080#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE00480000000C0000087C#3448650000000016##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~bootstrap],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [JSPMBootstrap] with id [C0013] from component [sap.com~tc~sdt~app~jspm~bootstrap] is empty#

#2.0
#2014 07 16 05:33:08:082#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00480000000D0000087C#3448650000000016##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~bootstrap],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [executable] with id [C0012] from component [sap.com~tc~sdt~app~jspm~bootstrap] found; file [go.bat] will be substituted#

#2.0
#2014 07 16 05:33:08:082#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00480000000E0000087C#3448650000000016##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~bootstrap],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [executable] with id [C0012] from component [sap.com~tc~sdt~app~jspm~bootstrap] found; file [jspm_cmd.bat] will be substituted#

#2.0
#2014 07 16 05:33:08:198#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000026###C000AC1D32BE00480000000F0000087C#3448650000000016##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~bootstrap],5,Managed_Application_Thread]#Plain##
      Files that need permissions change or depend on profile entries will be forcefully synchronized#

#2.0
#2014 07 16 05:33:08:202#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000028###C000AC1D32BE0048000000100000087C#3448650000000016##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~bootstrap],5,Managed_Application_Thread]#Plain##
      Failed to delete folder [C:\\usr\\sap\\ME2\\J00\\j2ee\\JSPM\\exe]; possible reason: folder not empty or access permissions are not set#

#2.0
#2014 07 16 05:33:10:240#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00490000000B0000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\param\\jspm_config.txt] will be substituted#

#2.0
#2014 07 16 05:33:10:241#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00490000000C0000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\server\\jspm.xml] will be substituted#

#2.0
#2014 07 16 05:33:10:241#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00490000000D0000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\data\\variables\\Jspm.xml] will be substituted#

#2.0
#2014 07 16 05:33:10:241#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00490000000E0000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\param\\jspm-rui_config.txt] will be substituted#

#2.0
#2014 07 16 05:33:10:241#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE00490000000F0000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\server\\sdtserver.xml] will be substituted#

#2.0
#2014 07 16 05:33:10:242#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE0049000000100000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\param\\jspm-cmd_config.txt] will be substituted#

#2.0
#2014 07 16 05:33:10:242#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE0049000000110000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\server\\sdtserver_rui.xml] will be substituted#

#2.0
#2014 07 16 05:33:10:242#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000008###C000AC1D32BE0049000000120000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
         Old format descriptor of file set [SdtJspmApx] with id [C0014] from component [sap.com~tc~sdt~app~jspm] found; file [deploy\\param\\jspm-srv_config.txt] will be substituted#

#2.0
#2014 07 16 05:33:10:246#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000026###C000AC1D32BE0049000000130000087C#3448650000000026##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm],5,Managed_Application_Thread]#Plain##
      Files that need permissions change or depend on profile entries will be forcefully synchronized#

#2.0
#2014 07 16 05:33:15:532#0-700#Warning#com.sap.engine.bootstrap#
com.sap.ASJ.boostrp.000102###C000AC1D32BE004A000000090000087C#3448650000000036##com.sap.engine.bootstrap#Administrator#8##2C1EF3C858461000982E826BE33E16BD#2c1ef3c858461000982e826be33e16bd#2c1ef3c858461000982e826be33e16bd#0#Thread[DeployThread[sap.com_tc~sdt~app~jspm~ext],5,Managed_Application_Thread]#Plain##
         Substitution list for file set [ExtLibs] with id [C0011] from component [sap.com~tc~sdt~app~jspm~ext] is empty#

#2.0
#2014 07 16 05:37:34:909#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0054000000010000087C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####F6311ECC0CE511E486B5000000349F4A#f6311ecc0ce511e486b5000000349f4a#f6311ecc0ce511e486b5000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: #

#2.0
#2014 07 16 05:37:34:909#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-JAS-COR-SES#sap.com/sessionmgmt~jco~applib#C000AC1D32BE0054000000020000087C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####F6311ECC0CE511E486B5000000349F4A#f6311ecc0ce511e486b5000000349f4a#f6311ecc0ce511e486b5000000349f4a#0#Deploy Parallel Stop Thread 1#Plain##
Global [stopApp] operation of application [sap.com/sessionmgmt~jco~applib] finished with non-critical warnings for [4] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 05:37:35:118#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005540#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0018000000070000087C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####F6311ECC0CE511E486B5000000349F4A#f6311ecc0ce511e486b5000000349f4a#f6311ecc0ce511e486b5000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: #

#2.0
#2014 07 16 05:37:35:118#0-700#Warning#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0005541#BC-SRV-TXV#sap.com/textverticalization_textapi#C000AC1D32BE0018000000080000087C#3448650000000006##com.sap.engine.services.deploy.server.TransactionManager####F6311ECC0CE511E486B5000000349F4A#f6311ecc0ce511e486b5000000349f4a#f6311ecc0ce511e486b5000000349f4a#0#Deploy Parallel Stop Thread 3#Plain##
Global [stopApp] operation of application [sap.com/textverticalization_textapi] finished with non-critical warnings for [3] ms on server process [3448650]: [
>>> Warnings <<<
1). The use of application hooks during start and stop is deprecated and will not be supported in the next major release. The applicaiton developer should remove the current hooks completely and replace them with EJB hooks.
Hints:
1) Details about the deprecation can be found on the following link: "https://jst.wdf.sap.corp/display/DeployTeam/(Deploy)+Application+Library+Container", section "Start and Stop Application Hooks".
2) You can request more implementation details about how to create EJB hooks by mail to DL NW F EJB.]#

#2.0
#2014 07 16 05:37:35:898#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-SEC#sap.com/ssl#C000AC1D32BE006C000000000000087C#3448650000001971##com.sap.engine.core.service630.container.ServiceWrapper#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [ssl]#Plain##
Management interface for service [ssl] is not registered and cannot be removed#

#2.0
#2014 07 16 05:37:35:977#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE006B000000010000087C#3448650000001802##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [com.adobe~DocumentServicesLicenseSupportService]#Plain##
Service interface for service com.adobe~DocumentServicesLicenseSupportService is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 05:37:35:977#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0073000000010000087C#3448650000001830##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [com.adobe~DocumentServicesBinaries2]#Plain##
Service interface for service com.adobe~DocumentServicesBinaries2 is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 05:37:36:038#0-700#Error#com.sap.aii.af.service.trex.TrexScheduler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1D32BE0045000000020000087C#3448650000001686##com.sap.aii.af.service.trex.TrexScheduler.TrexScheduler: run()#Guest#0###610e7edf0ce211e4c93a00155d336301##0#Application [40]#Plain##
InterruptedException: thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown. Message: sleep interrupted; To-String: java.lang.InterruptedException: sleep interrupted.#

#2.0
#2014 07 16 05:37:36:039#0-700#Warning#com.sap.aii.security.ServiceThread#
#BC-XI-CON-AFW-SEC#com.sap.aii.sec.svc#C000AC1D32BE0076000000010000087C#3448650000001657##com.sap.aii.security.ServiceThread.ServiceThread.run()#Guest#0###610e7edf0ce211e4c93a00155d336301##0#Application [44]#Plain##
InterruptedException will be thrown if another thread has interrupted the current thread. The interrupted status of the current thread is cleared when this exception is thrown.
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.aii.security.ServiceThread.run(ServiceThread.java:171)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:218)

#

#2.0
#2014 07 16 05:37:39:180#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-BTC#sap.com/scheduler~runtime#C000AC1D32BE0078000000000000087C#3448650000003845##com.sap.engine.core.service630.container.ServiceWrapper#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [scheduler~runtime]#Plain##
Management interface for service [scheduler~runtime] is not registered and cannot be removed#

#2.0
#2014 07 16 05:37:39:183#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-ESI-WS-JAV-RT#sap.com/tc~je~webservices~srv#C000AC1D32BE0064000000030000087C#3448650000003819##com.sap.engine.core.service630.container.ServiceWrapper#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [tc~je~webservices~srv]#Plain##
Management interface for service [tc~je~webservices~srv] is not registered and cannot be removed#

#2.0
#2014 07 16 05:37:39:405#0-700#Warning#com.sap.engine.core.service630.container.ContainerObjectRegistry#
#BC-JAS-COR#kernel.sda#C000AC1D32BE0079000000000000087C#3448650000004003##com.sap.engine.core.service630.container.ContainerObjectRegistry#####f6311ecc0ce511e486b5000000349f4a##0#Event Processor [connector]#Plain##
Service interface for service connector is not registered in registry and cannot be removed.#

#2.0
#2014 07 16 05:37:39:406#0-700#Warning#com.sap.engine.core.service630.container.ServiceWrapper#
com.sap.ASJ.krn_srv.000068#BC-JAS-TRH#sap.com/connector#C000AC1D32BE005B000000010000087C#3448650000003994##com.sap.engine.core.service630.container.ServiceWrapper#####f6311ecc0ce511e486b5000000349f4a##0#Service Stopper [connector]#Plain##
Management interface for service [connector] is not registered and cannot be removed#

#2.0
#2014 07 16 05:37:39:414#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#BC-JAS-COR#kernel.sda#C000AC1D32BE007A000000010000087C#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####610e7edf0ce211e4c93a00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]#

#2.0
#2014 07 16 05:37:39:415#0-700#Warning#com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#
com.sap.ASJ.krn_thd.000109#N/A#p4lib#C000AC1D32BE007A000000020000087C#3448650000000004##com.sap.engine.core.thread.impl3.UncaughtExceptionHandler#####610e7edf0ce211e4c93a00155d336301##0#Thread[Thread-17,5,SystemThreadGroup]#Plain##
The following unhandled exception: [java.lang.ThreadDeath] was detected in [Thread[Thread-17,5,SystemThreadGroup]]
[EXCEPTION]
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:823)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.ThreadWrapper.stopIt(ThreadWrapper.java:36)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeMessanger.stop(FinalizeMessanger.java:59)
at com.sap.engine.services.rmi_p4.garbagecollector.finalize.FinalizeInformer.close(FinalizeInformer.java:176)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.close(P4ObjectBrokerServerImpl.java:123)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.stop(P4SessionProcessor.java:130)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.stop(P4ServiceFrame.java:288)
at com.sap.engine.core.service630.container.ServiceStopper.stopFrame(ServiceStopper.java:138)
at com.sap.engine.core.service630.container.ServiceStopper.stopService(ServiceStopper.java:107)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:58)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:37:42:664#0-700#Error#com.sap.engine.services.wsrm#
#BC-ESI-WS-JAV-RT#tc~esi~esp~wsrm~srv#C000AC1D32BE0002000000030000087C#3448650000001685##com.sap.engine.services.wsrm#####610e7edf0ce211e4c93a00155d336301##0#System [12]#Plain##
SequenceDataOptimizer.java\#1 $run()
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.services.wsrm.util.SequenceDataOptimizer.run(SequenceDataOptimizer.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:39:20:543#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000A6C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:39:22:657#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000A6C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####367350f90ce611e49d5500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:39:22:658#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000A6C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####367350f90ce611e49d5500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:39:22:679#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000A6C#3448650000000001##com.sap.engine.core.Framework#####367350f90ce611e49d5500155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:39:36:432#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000008B4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:39:38:158#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000008B4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####3fa03e030ce611e48ed500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:39:38:158#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000008B4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####3fa03e030ce611e48ed500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:39:38:161#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000008B4#3448650000000001##com.sap.engine.core.Framework#####3fa03e030ce611e48ed500155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:39:50:336#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000AB8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:39:52:078#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000AB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####480146660ce611e4b2e200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:39:52:080#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000AB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####480146660ce611e4b2e200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:39:52:084#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000AB8#3448650000000001##com.sap.engine.core.Framework#####480146660ce611e4b2e200155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:40:04:476#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000A98###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:40:06:331#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000A98#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####506d7dcc0ce611e481c800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:40:06:331#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000A98#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####506d7dcc0ce611e481c800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:40:06:336#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000A98#3448650000000001##com.sap.engine.core.Framework#####506d7dcc0ce611e481c800155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:42:28:393#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B4C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:42:30:201#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000B4C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a639733a0ce611e4c3bd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:42:30:201#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000B4C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a639733a0ce611e4c3bd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:42:30:204#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000B4C#3448650000000001##com.sap.engine.core.Framework#####a639733a0ce611e4c3bd00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:42:42:719#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000D48###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:42:44:459#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000D48#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####aeb7e83b0ce611e4b5f500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:42:44:468#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000D48#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####aeb7e83b0ce611e4b5f500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:42:44:477#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000D48#3448650000000001##com.sap.engine.core.Framework#####aeb7e83b0ce611e4b5f500155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:42:57:571#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000067C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:42:59:021#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000010000067C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b77147a70ce611e4a6e300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:42:59:022#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000020000067C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b77147a70ce611e4a6e300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:42:59:025#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0002000000040000067C#3448650000000001##com.sap.engine.core.Framework#####b77147a70ce611e4a6e300155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:43:12:090#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001744###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:43:13:811#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100001744#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####c03710a40ce611e4843a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:43:13:812#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200001744#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####c03710a40ce611e4843a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:43:13:823#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400001744#3448650000000001##com.sap.engine.core.Framework#####c03710a40ce611e4843a00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:45:06:791#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000C84###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:45:08:383#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000C84#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####047bd5550ce711e498a400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:45:08:387#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000C84#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####047bd5550ce711e498a400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:45:08:392#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000C84#3448650000000001##com.sap.engine.core.Framework#####047bd5550ce711e498a400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:45:21:136#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000013B4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:45:22:547#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000013B4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####0ceeabdd0ce711e4c54600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:45:22:548#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000013B4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####0ceeabdd0ce711e4c54600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:45:22:553#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000013B4#3448650000000001##com.sap.engine.core.Framework#####0ceeabdd0ce711e4c54600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:45:34:065#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001534###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:45:35:740#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100001534#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####14cd2bc20ce711e4a8d000155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:45:35:741#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200001534#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####14cd2bc20ce711e4a8d000155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:45:35:746#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400001534#3448650000000001##com.sap.engine.core.Framework#####14cd2bc20ce711e4a8d000155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 05:45:48:591#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000163C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 05:45:50:135#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000163C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####1d67c0830ce711e494dd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 05:45:50:135#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000163C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####1d67c0830ce711e494dd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 05:45:50:139#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000163C#3448650000000001##com.sap.engine.core.Framework#####1d67c0830ce711e494dd00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 06:00:35:091#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001230###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 06:00:37:765#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100001230#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####2e6dea710ce911e4a82e00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 06:00:37:766#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200001230#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####2e6dea710ce911e4a82e00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 06:00:37:773#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400001230#3448650000000001##com.sap.engine.core.Framework#####2e6dea710ce911e4a82e00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 06:00:51:998#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000E6C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 06:00:53:649#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000E6C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####37fa649a0ce911e49c9700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 06:00:53:650#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000E6C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####37fa649a0ce911e49c9700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 06:00:53:682#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000E6C#3448650000000001##com.sap.engine.core.Framework#####37fa649a0ce911e49c9700155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 06:01:06:292#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000430###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 06:01:07:833#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000430#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####407278c60ce911e4b84600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 06:01:07:834#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000430#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####407278c60ce911e4b84600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 06:01:07:839#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000430#3448650000000001##com.sap.engine.core.Framework#####407278c60ce911e4b84600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 06:01:21:201#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001558###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 06:01:23:075#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100001558#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####498261960ce911e4a32700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 06:01:23:075#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200001558#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####498261960ce911e4a32700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 06:01:23:085#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400001558#3448650000000001##com.sap.engine.core.Framework#####498261960ce911e4a32700155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:01:00:978#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B80###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:01:02:763#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000B80#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9f3092070cf111e4a7fe00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:01:02:764#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000B80#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9f3092070cf111e4a7fe00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:01:02:780#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000B80#3448650000000001##com.sap.engine.core.Framework#####9f3092070cf111e4a7fe00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:01:17:012#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000015CC###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:01:18:624#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000015CC#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a8a6f12d0cf111e49ed600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:01:18:624#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000015CC#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a8a6f12d0cf111e49ed600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:01:18:626#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000015CC#3448650000000001##com.sap.engine.core.Framework#####a8a6f12d0cf111e49ed600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:01:31:544#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000014F0###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:01:33:487#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000014F0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b171b8bd0cf111e4cf3b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:01:33:488#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000014F0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b171b8bd0cf111e4cf3b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:01:33:516#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000014F0#3448650000000001##com.sap.engine.core.Framework#####b171b8bd0cf111e4cf3b00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:01:46:740#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000014B8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:01:48:615#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000014B8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####ba742bcf0cf111e4889200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:01:48:616#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000014B8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####ba742bcf0cf111e4889200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:01:48:625#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000014B8#3448650000000001##com.sap.engine.core.Framework#####ba742bcf0cf111e4889200155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:02:21:134#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000017A8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:02:23:138#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000017A8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####cf03dd7b0cf111e4cb0900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:02:23:138#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000017A8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####cf03dd7b0cf111e4cb0900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:02:23:180#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000017A8#3448650000000001##com.sap.engine.core.Framework#####cf03dd7b0cf111e4cb0900155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:02:36:764#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000978###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:02:38:550#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000978#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####d83f24060cf111e481e100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:02:38:553#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000978#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####d83f24060cf111e481e100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:02:38:566#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000978#3448650000000001##com.sap.engine.core.Framework#####d83f24060cf111e481e100155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:02:52:093#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B24###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:02:53:923#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000B24#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####e16c5fbf0cf111e486a100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:02:53:923#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000B24#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####e16c5fbf0cf111e486a100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:02:53:929#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000B24#3448650000000001##com.sap.engine.core.Framework#####e16c5fbf0cf111e486a100155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:03:07:453#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000017B8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:03:09:376#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000017B8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####ea942b910cf111e48a2b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:03:09:376#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000017B8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####ea942b910cf111e48a2b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:03:09:381#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000017B8#3448650000000001##com.sap.engine.core.Framework#####ea942b910cf111e48a2b00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:10:18:138#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000027C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:10:19:978#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000027C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####eb4424100cf211e4987800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:10:19:979#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000027C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####eb4424100cf211e4987800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:10:19:996#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000027C#3448650000000001##com.sap.engine.core.Framework#####eb4424100cf211e4987800155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:10:33:671#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000E9C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:10:35:191#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000E9C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####f449be780cf211e4bbd300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:10:35:191#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000E9C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####f449be780cf211e4bbd300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

Former Member
0 Kudos

part 9

===============================================================

#2.0
#2014 07 16 07:10:35:194#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000E9C#3448650000000001##com.sap.engine.core.Framework#####f449be780cf211e4bbd300155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:10:47:846#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000170C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:10:49:646#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000170C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####fd03f58b0cf211e4b0a500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:10:49:647#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000170C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####fd03f58b0cf211e4b0a500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:10:49:676#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000170C#3448650000000001##com.sap.engine.core.Framework#####fd03f58b0cf211e4b0a500155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:11:02:733#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000874###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:11:04:666#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000874#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####05e07e7c0cf311e4855d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:11:04:666#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000874#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####05e07e7c0cf311e4855d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:11:04:670#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000874#3448650000000001##com.sap.engine.core.Framework#####05e07e7c0cf311e4855d00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:12:28:544#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000C8C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.RemoveDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:12:30:500#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000C8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####38ffdeca0cf311e4c66000155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:12:30:501#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000C8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####38ffdeca0cf311e4c66000155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:12:30:578#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000C8C#3448650000000001##com.sap.engine.core.Framework#####38ffdeca0cf311e4c66000155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:12:43:947#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000010F8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:12:45:881#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000010F8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####422f0ec10cf311e49bc400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:12:45:882#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000010F8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####422f0ec10cf311e49bc400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:12:45:886#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000010F8#3448650000000001##com.sap.engine.core.Framework#####422f0ec10cf311e49bc400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:12:59:287#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001678###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:13:01:142#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100001678#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####4b4fcb880cf311e4c48900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:13:01:148#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200001678#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####4b4fcb880cf311e4c48900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:13:01:152#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400001678#3448650000000001##com.sap.engine.core.Framework#####4b4fcb880cf311e4c48900155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:13:14:364#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B64###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:13:16:303#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000B64#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####545849d20cf311e4b4f900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:13:16:303#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000B64#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####545849d20cf311e4b4f900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:13:16:307#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000B64#3448650000000001##com.sap.engine.core.Framework#####545849d20cf311e4b4f900155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:16:50:465#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000820###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDomainsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:16:52:344#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000820#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####d526eb0b0cf311e4817c00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:16:52:352#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000820#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####d526eb0b0cf311e4817c00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:16:52:356#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000820#3448650000000001##com.sap.engine.core.Framework#####d526eb0b0cf311e4817c00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:17:05:765#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000159C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:17:07:542#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000010000159C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####de2031ba0cf311e4a94400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:17:07:542#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000020000159C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####de2031ba0cf311e4a94400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:17:07:552#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0002000000040000159C#3448650000000001##com.sap.engine.core.Framework#####de2031ba0cf311e4a94400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:17:20:688#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000016E8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:17:22:364#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000016E8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####e702860e0cf311e4972800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:17:22:364#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000016E8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####e702860e0cf311e4972800155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:17:22:380#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000016E8#3448650000000001##com.sap.engine.core.Framework#####e702860e0cf311e4972800155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 07:17:35:951#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000C8C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 07:17:37:573#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000C8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####f022d1d00cf311e4bf8d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 07:17:37:575#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000C8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####f022d1d00cf311e4bf8d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 07:17:37:579#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000C8C#3448650000000001##com.sap.engine.core.Framework#####f022d1d00cf311e4bf8d00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:14:10:968#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000AB0###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:14:13:838#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000AB0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####92f2d94d0d7911e4bf2900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:14:13:838#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000AB0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####92f2d94d0d7911e4bf2900155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:14:13:838#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000AB0#3448650000000001##com.sap.engine.core.Framework#####92f2d94d0d7911e4bf2900155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:14:29:344#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000D50###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:14:31:272#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000D50#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9d4b419e0d7911e4b8bd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:14:31:272#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000D50#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9d4b419e0d7911e4b8bd00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:14:31:303#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000D50#3448650000000001##com.sap.engine.core.Framework#####9d4b419e0d7911e4b8bd00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:14:45:570#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000012CC###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.MonitorSessionsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:14:47:451#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000012CC#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a6f4d3c90d7911e481df00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:14:47:451#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000012CC#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a6f4d3c90d7911e481df00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:14:47:451#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000012CC#3448650000000001##com.sap.engine.core.Framework#####a6f4d3c90d7911e481df00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:15:01:965#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000068C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:15:03:721#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000068C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b0b80afa0d7911e4a0f500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:15:03:721#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000068C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b0b80afa0d7911e4a0f500155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:15:03:752#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000068C#3448650000000001##com.sap.engine.core.Framework#####b0b80afa0d7911e4a0f500155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:48:58:446#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000007C8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:49:00:227#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000007C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####6e8d98ac0d7e11e4911300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:49:00:227#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000007C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####6e8d98ac0d7e11e4911300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:49:00:242#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000007C8#3448650000000001##com.sap.engine.core.Framework#####6e8d98ac0d7e11e4911300155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:49:14:585#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000077C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:49:16:054#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000077C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####77ee61350d7e11e489f100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:49:16:054#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000077C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####77ee61350d7e11e489f100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:49:16:054#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000077C#3448650000000001##com.sap.engine.core.Framework#####77ee61350d7e11e489f100155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:49:30:131#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000006F8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:49:32:131#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000006F8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####81755b9e0d7e11e4bdc100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:49:32:131#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000006F8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####81755b9e0d7e11e4bdc100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:49:32:147#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000006F8#3448650000000001##com.sap.engine.core.Framework#####81755b9e0d7e11e4bdc100155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 16 23:49:46:521#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000007A0###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.DatashareMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 16 23:49:48:412#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000001000007A0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####8b3547a00d7e11e4c75100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 16 23:49:48:427#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000100000002000007A0#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####8b3547a00d7e11e4c75100155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 16 23:49:48:427#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000100000004000007A0#3448650000000001##com.sap.engine.core.Framework#####8b3547a00d7e11e4c75100155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:10:36:435#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000007E8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:10:38:372#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000007E8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####74398fa10d8111e4b6c300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:10:38:372#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000007E8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####74398fa10d8111e4b6c300155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:10:38:388#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000007E8#3448650000000001##com.sap.engine.core.Framework#####74398fa10d8111e4b6c300155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:10:52:761#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B3C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:10:54:183#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000B3C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####7dad18d50d8111e4948a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:10:54:199#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000B3C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####7dad18d50d8111e4948a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:10:54:199#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000B3C#3448650000000001##com.sap.engine.core.Framework#####7dad18d50d8111e4948a00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:11:08:853#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001150###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:11:10:619#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100001150#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####8789a2920d8111e480d400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:11:10:619#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200001150#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####8789a2920d8111e480d400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:11:10:634#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400001150#3448650000000001##com.sap.engine.core.Framework#####8789a2920d8111e480d400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:11:25:055#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B74###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:11:26:820#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100000B74#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####91343cb80d8111e49e0d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:11:26:820#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200000B74#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####91343cb80d8111e49e0d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:11:26:836#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400000B74#3448650000000001##com.sap.engine.core.Framework#####91343cb80d8111e49e0d00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:57:39:781#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000073C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListSessionContextsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:57:41:687#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000010000073C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####07144fac0d8811e4b8d600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:57:41:687#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0002000000020000073C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####07144fac0d8811e4b8d600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:57:41:687#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0002000000040000073C#3448650000000001##com.sap.engine.core.Framework#####07144fac0d8811e4b8d600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:57:55:922#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B0000107C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:57:57:438#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000010000107C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####107079300d8811e4cd8d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:57:57:438#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE0001000000020000107C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####107079300d8811e4cd8d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:57:57:438#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE0001000000040000107C#3448650000000001##com.sap.engine.core.Framework#####107079300d8811e4cd8d00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:58:11:203#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001318###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:58:13:094#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100001318#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####19cf02630d8811e4881d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:58:13:094#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200001318#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####19cf02630d8811e4881d00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:58:13:110#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400001318#3448650000000001##com.sap.engine.core.Framework#####19cf02630d8811e4881d00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 00:58:27:641#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001084###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessDomRecMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 00:58:29:594#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100001084#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####239187fa0d8811e4946200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 00:58:29:610#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200001084#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####239187fa0d8811e4946200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 00:58:29:610#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400001084#3448650000000001##com.sap.engine.core.Framework#####239187fa0d8811e4946200155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:02:32:581#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000B98###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:02:34:472#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000B98#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b597a6340d8811e4a30a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:02:34:472#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000B98#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b597a6340d8811e4a30a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:02:34:488#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000B98#3448650000000001##com.sap.engine.core.Framework#####b597a6340d8811e4a30a00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:02:48:691#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000A8C###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:02:50:050#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000A8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####beea49770d8811e4895700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:02:50:050#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000A8C#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####beea49770d8811e4895700155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:02:50:066#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000A8C#3448650000000001##com.sap.engine.core.Framework#####beea49770d8811e4895700155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:03:03:972#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000013C8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDBOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:03:05:878#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000013C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####c848ca300d8811e4a37b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:03:05:878#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000013C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####c848ca300d8811e4a37b00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:03:05:878#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000013C8#3448650000000001##com.sap.engine.core.Framework#####c848ca300d8811e4a37b00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:06:32:026#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000006F4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListAllOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:06:33:948#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000006F4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####444b58b30d8911e4a28400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:06:33:948#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000006F4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####444b58b30d8911e4a28400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:06:33:963#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000006F4#3448650000000001##com.sap.engine.core.Framework#####444b58b30d8911e4a28400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:06:48:010#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000009F4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:06:49:526#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000009F4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####4d941d5b0d8911e4883a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:06:49:526#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000009F4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####4d941d5b0d8911e4883a00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:06:49:541#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000009F4#3448650000000001##com.sap.engine.core.Framework#####4d941d5b0d8911e4883a00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:07:04:041#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000008C8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.SessLogFilterMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:07:05:869#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000008C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####576532220d8911e4bf8c00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:07:05:869#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000008C8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####576532220d8911e4bf8c00155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:07:05:885#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000008C8#3448650000000001##com.sap.engine.core.Framework#####576532220d8911e4bf8c00155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:07:20:401#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000E44###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListDomainsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:07:22:214#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000E44#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####6120b6e10d8911e49b4600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:07:22:214#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000E44#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####6120b6e10d8911e49b4600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:07:22:229#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000E44#3448650000000001##com.sap.engine.core.Framework#####6120b6e10d8911e49b4600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:15:59:222#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00001154###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:16:01:097#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000100001154#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####966a89a60d8a11e4b06600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:16:01:097#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00010000000200001154#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####966a89a60d8a11e4b06600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:16:01:144#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00010000000400001154#3448650000000001##com.sap.engine.core.Framework#####966a89a60d8a11e4b06600155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:16:15:488#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000BB8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:16:17:207#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000BB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9fd9bb910d8a11e4990400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:16:17:207#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000BB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####9fd9bb910d8a11e4990400155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:16:17:207#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE00020000000400000BB8#3448650000000001##com.sap.engine.core.Framework#####9fd9bb910d8a11e4990400155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:16:31:395#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B000005A4###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.StatisticsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:16:33:254#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000001000005A4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a9979aba0d8a11e48a7200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:16:33:254#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE000200000002000005A4#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####a9979aba0d8a11e48a7200155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]
java.lang.NoSuchFieldError: ipaddress
at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)
at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)
at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

#

#2.0
#2014 07 17 01:16:33:254#0-700#Fatal#com.sap.engine.core.Framework#
com.sap.ASJ.krn_frm.000019#BC-JAS-COR#kernel.sda#C000AC1D32BE000200000004000005A4#3448650000000001##com.sap.engine.core.Framework#####a9979aba0d8a11e48a7200155d336301##0#Service Runner [cross]#Plain##
Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]#

#2.0
#2014 07 17 01:16:47:786#0-700#Warning#com.sap.engine.core.session.Manager#
com.sap.ASJ.ses.cf0023#BC-JAS-COR-SES#kernel.sda#C000AC1D32BE00000000000B00000BB8###com.sap.engine.core.session.Manager########Thread[main,5,main]#Plain##
Could not register com.sap.engine.session.mbeans.ListConfigsOpenMBean. Exception is: java.lang.InstantiationException: com.sap.engine.session.mbeans.MonitorSessionsOpenMBean#

#2.0
#2014 07 17 01:16:49:645#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000059#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000100000BB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b35597e30d8a11e48e1600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; contact the component owner for resolving the problem#

#2.0
#2014 07 17 01:16:49:645#0-700#Error#com.sap.engine.core.service630.container.ServiceRunner#
com.sap.ASJ.krn_srv.000069#BC-JAS-COR-RMT#sap.com/cross#C000AC1D32BE00020000000200000BB8#3448650000000001##com.sap.engine.core.service630.container.ServiceRunner#####b35597e30d8a11e48e1600155d336301##0#Service Runner [cross]#Plain##
Service [cross] failed to start; nested exception is:
[EXCEPTION]

divyanshu_srivastava3
Active Contributor
divyanshu_srivastava3
Active Contributor
0 Kudos

Update you kernel in short as per the note.