Quantcast
Channel: SCN: Message List
Viewing all 8065 articles
Browse latest View live

Re: 500 Internal Server Error SAP NetWeaver Application Server/Java AS

July 21, 2014, 4:57 am
$
0
0

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

#

↧
Search
↧

Re: Chennai Ptax calculation during Withdrawn stage in mid month

July 21, 2014, 4:57 am
$
0
0

Your termination action seems to be configured incorrectly

 

when an employee terminate It will not pick during payroll execution.

↧

Re: Account Maintenance Charge

July 21, 2014, 4:57 am
$
0
0

The Condition is tagged to Settlement Category.

↧

Re: settlement rule for production orders

July 22, 2014, 5:07 am
$
0
0

Hi,

 

did you search SAPNET notes using "CO07" and "settlement rule" as search parameters? I find 27 notes, maybe you find what you are looking for...

 

BR Christian

↧

Re: Chart x-axis should show the values even if there is nodata

July 22, 2014, 5:07 am
$
0
0

Hi Tanveer,

 

Charts and Groups in a report do not display values that are not present in the database.

 

Create a table in your database with all the dates (if that's possible) and Left Join it to the current table in CR.

 

This way the report should display future months even when there aren't any records.

 

You would then need a Record Selection Formula as well that will restrict records to the current fiscal year.

 

Otherwise, follow Jamie's blog here:

 

http://scn.sap.com/community/crystal-reports/blog/2011/12/13/displaying-all-missing-dates-in-a-range--a-custom-function-sample

 

-Abhilash

↧
↧

Re: Downloading screen from SM35 LOG

July 22, 2014, 5:06 am
$
0
0

Don't hesitate to use search tool (this is a FAQ) - either use keywords like "BDC", "session" or "Batch input" with complementary keywords "read" "log" (Once you find RSTS_READ start reading previously posted answers)

 

Regards,

Raymond

↧

Using IDOCS or LSMW can we achieve

July 22, 2014, 5:07 am
$
0
0

HI Experts,

 

I have a Excel with material data as below

 

Material_Number  Material_Group_Num   amount

 

111111111           33333333333               11111.00

222222222           44444444444               22222.00

444444444          55555555555                33333.00

 

I have to update  in the SAP Tables, for a particular material_Number the material_group_num has to be updated

 

Any idea or Suggesion

 

Thanks

Madhu

↧

Re: Free Good Should not be Modified

July 22, 2014, 5:07 am
$
0
0

Hi

 

As righty said by Eduardo please use that userexit. You can also put restriction to delete line item using this or may be some other userexit but all exits are there in MV45AFZZ program. I remember I had done this using MV45AFZZ and we had to try in different exits one by one. I had the same requirement from my client and if I remember correctly we used USEREXIT_FIELD_MODIFICATION and

USEREXIT_MOVE_FIELD_TO_VBAP exits.

 

 

Thank$

↧
Search

Re: Update cart business partner(s).

July 22, 2014, 5:08 am
$
0
0

Hello Stacy,

 

      But it would only help you to change in PO not in SC. And I guess you are looking for SC.I do have a Z-report which helps me to change the Requestor for PO.

 

Thanks

Gaurav Gautan

↧
↧

Re: Enable parallel processing of two data sources when refreshing/ resetting one of them

July 22, 2014, 5:08 am
$
0
0

Hi Jörg,

 

do you type in the technical names of the queries (data sources) or the descriptions. I used the technical names, but I'm not sure whether this is correct, as the macro doesn't seem to execute anything.

 

Thank you and regards,
Sarah

↧

Re: error in updating table J_1IEXCHDR,J_1IEXCDTL in tcode J1IJ

July 22, 2014, 5:09 am
$
0
0

Hi,

 

 

we have checked plant setting.it is properly maintained.

But still we are facing the same problem 'error in updating table' in J1IJ.

error message - 'Table entry not exist in VBUK TABLE'

 

 

Reagrds,

↧

Re: Making Sandbox server with production data

July 22, 2014, 5:09 am
↧

Re: CDB has data but the device isn't getting none on Sync

July 22, 2014, 5:09 am
$
0
0

Are you still facing this issue ?

↧
↧

Re: How to install SAP incentive Administration by VISTEX

July 23, 2014, 8:20 pm
$
0
0

Hi,

 

Are you working with SAP Business one? If NO, this is not right forum to post and find correct forum.

 

Thanks & Regards,

Nagarajan

↧

Re: Connectivity with SAP Sever

July 23, 2014, 8:19 pm
$
0
0

Hi M G,

 

I can give you two options:

 

1. You can use Citrix (but I think it's expensive) .

 

2. You need to setup a Terminal Server (so your client will use Remote Desktop Connection). In our infrastructure, we subscribed from our Internet provider IP-VPN it has an added cost but not as expensive as Citrix. (You can ask your provider for this feature).

 

 

 

Wr,

 

Paul Caballero

↧
Search

Re: EHP7 upgrade stuck in SCANDIR_EPS0

July 23, 2014, 8:22 pm
$
0
0

Hi Gaurav,

 

I was able to change the owner, but still error persists

Yes, there a separate mount for running the tool and for the media.

↧

Re: DTW error Cost Center wise Budget uploading BGT2

July 23, 2014, 8:23 pm
↧
↧

Re: CE_CONVERSION in ABAP AMDP method

July 23, 2014, 8:23 pm
$
0
0

Then i get the following error

 

SQLScript: Attribute not found in column table: DEMO_PRICES

 

  prices= CE_CONVERSION(:demo_prices, [family = 'currency',
  method = 'ERP',
  client = '900',
  conversion_type = 'M',
  target_unit = 'EUR',
  source_unit = 'DKK',
  reference_date = "01.07.2014",
  output_unit_column = "BAPICURR"],
  

[ demo_prices AS out_amount ] );

 

I have also tried the following, but then i get the error: sap column name BAPICURR defined multiple times in output table

 

  et_amount = CE_CONVERSION(:demo_prices, [family = 'currency',
  method = 'ERP',
  client = '900',
  conversion_type = 'M',
  target_unit = 'EUR',
  source_unit = 'DKK',
  reference_date = "01.07.2014",
  output_unit_column = "BAPICURR"]);
 
↧

Re: Sales Service

July 23, 2014, 8:23 pm
↧

Re: SAP B1 8.82 Server Installation (HANA) - could not create Database

July 23, 2014, 8:25 pm
$
0
0

Hi San Xu,

 

It's work!! Thank you very much.

 

regards,

Winnie

↧
Viewing all 8065 articles
Browse latest View live
More Pages to Explore .....
Search

Latest Images

Nonprofit donates custom home in this East Bay city for Marine injured in...

Nonprofit donates custom home in this East Bay city for Marine injured in...

April 23, 2024, 7:00 am
New private rooms on Tokaido Shinkansen change the way we travel from Tokyo...

New private rooms on Tokaido Shinkansen change the way we travel from Tokyo...

April 22, 2024, 6:00 am
Ukraine bans military from online gambling amid addiction concerns

Ukraine bans military from online gambling amid addiction concerns

April 22, 2024, 5:17 am
ಮಂಡ್ಯದಿಂದ ಸುಮಲತಾ ದೂರ; ಹೆಚ್‌ಡಿಕೆ ಪರ ಪ್ರಚಾರಕ್ಕಿಳಿಯದ ಸಂಸದೆ –ಬರ್ತಾರೆ ನೋಡೋಣ ಎಂದ...

ಮಂಡ್ಯದಿಂದ ಸುಮಲತಾ ದೂರ; ಹೆಚ್‌ಡಿಕೆ ಪರ ಪ್ರಚಾರಕ್ಕಿಳಿಯದ ಸಂಸದೆ –ಬರ್ತಾರೆ ನೋಡೋಣ ಎಂದ...

April 20, 2024, 8:08 pm
OCBC Bank Singapore Offers Up to 2.8% p.a. Fixed Deposit Promotion from 21...

OCBC Bank Singapore Offers Up to 2.8% p.a. Fixed Deposit Promotion from 21...

April 20, 2024, 12:38 pm
National Poetry Month 2024: Maxine Starr

National Poetry Month 2024: Maxine Starr

April 19, 2024, 9:56 am
Vegan Chicken Pot Pie

Vegan Chicken Pot Pie

April 19, 2024, 9:18 am
Firefox UX: On Purpose: Collectively Defining Our Team’s Mission Statement

Firefox UX: On Purpose: Collectively Defining Our Team’s Mission Statement

April 19, 2024, 7:03 am
New $4.5 million East Bay trail path will connect bicyclists, pedestrians to...

New $4.5 million East Bay trail path will connect bicyclists, pedestrians to...

April 18, 2024, 11:05 am
Photographer Gifts for Clients / Print Packaging / 4x6 Photo Box by...

Photographer Gifts for Clients / Print Packaging / 4x6 Photo Box by...

April 17, 2024, 6:48 pm