Issue after Java Addin Successfull Installation-- com.sap.engine.services.d
com.sap.engine.services.deploy.container.ExceptionInfo: Naming error.
Hi All,
Please help me to fix the following issue:
After Successfull installation of Java Addin to ECC 6.0 (SR3,Oracle 10.2,Solaris 5.10) i am facing the following issue when i try to access http://<hostname>:50000/nwa and http://<hostname>:50000/useradmin
com.sap.engine.services.deploy.container.ExceptionInfo: Naming error.
And if i try to access http://<hostname>:50000 it works fine.
I have restarted Java stack and also ABAP+Java Stack but still no luck.
Thanks,
Siva Kumar
Hai,
Check the below links.....
access SLD failed
com.sap.engine.services.deploy.container.ExceptionInfo: Naming error
Regards,
Yoganand.V
Similar Messages
-
Com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentExcepti
When I try running my web application from browser after deploying succesfully, I get following error.I checked web.xml & config.xml..they are welformed.
Application cannot be started!
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application sap.com/crm.b2b_hsp.
at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:101)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:383)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:323)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:358)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:116)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:217)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4350)
at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:520)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:341)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:161)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:135)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:349)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:116)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:217)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4350)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2466)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2339)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:41)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:141)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:101)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Cannot get a naming context or initialize the application's naming environment.
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.createNamingContexts(WebApplicationConfig.java:630)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:101)
at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:579)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:541)
at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:50)
... 24 morekinldy let me know what was the solution to this problem
-
Com.sap.engine.services.dbpool.exceptions.BaseResourceException:
Hi
Jcontrol.exe is stopped. I checked in server0 log file.
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection:
Caused by: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server
Caused by: java.net.ConnectException: Connection refused: connectCommunication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
com.sap.caf.eu.gp.mail.cf.core.exceptionhandling.MailCFExceptionHandler.throwMailCFRuntimeException(MailCFExceptionHandler.java:92)
#1.5 #0022198E9491001F000000130000390C00046999A2B0692D#1242008487314#com.sap.jms##com.sap.jms####n/a##6e72d7203dd211decd7d0022198e9491#SAPEngine_System_Thread[impl:5]_90##0#0#Error#1#/System/Server#Plain#JMSServerContainer.onServiceJoin##Configuration problem occurred while accessing JMS configuration resources.#
#1.5 #0022198E9491008E000000010000390C00046999A5B43D17#1242008537907#com.sap.sql.jdbc.direct.DirectPreparedStatement##com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest#0##n/a##8c9ab8303dd211de99680022198e9491#SAPEngine_Application_Thread[impl:3]_2##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL error occurred on connection apsgdc01hwebd:BPE:SAPBPEDB: code=-4,499, state="null", message="[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error";
SQL statement is "SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4".
[EXCEPTION]
#6#-4499#<null>#[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error#apsgdc01hwebd:BPE:SAPBPEDB#SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4#com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
Regards
RaoHi, Please let me know if you managed to solve the problem.. We are facing the same issue
Regards
PN -
Com.sap.engine.services.jndi.persistent.exceptions.NamingException
Hi,
We have just finish apply/update our SAP Netweaver WebAS 6.40 (Java) with the support package (SP25). When we test our application, we encountered the following exception
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
This exception seems to be intermittent. After some time, when we try again, we did not encountered this exception. But after we restart, the error appear again.
Please help.Hi,
On checking the trace log file, I noticed some security exception 'com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.'.
before the 'com.sap.engine.services.jndi.persistent.exceptions.NamingException : Error getting the server-side naming service functionality during getInitialContext operation. '
What could be the cause for 'BaseSecurityException: Caller not authorized' exception?
#1.5 #0003BA7B25C0002B000000000000394600048F300D41A62A#1283336450450#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#
#1.5 #0003BA7B25C0002B000000010000394600048F300D437AAE#1283336450570#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#
#1.5 #0003BA7B25C0002B000000030000394600048F300D47CA6E#1283336450850#com.sap.engine.services.security.authentication.logincontext#sap.com/CRRSRatingEAR#com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Java###Caller not authorized.
[EXCEPTION]
#1#com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:119)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getSessionPool(AuthenticationContextImpl.java:395)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContextFactory(AuthenticationContextImpl.java:740)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContext(AuthenticationContextImpl.java:254)
at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:59)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:139)
at com.mbb.crrs.business.common.InitialContextFactory.getInitalContext(InitialContextFactory.java:81)
at com.mbb.crrs.business.common.ServiceLocator.<init>(ServiceLocator.java:286)
at com.mbb.crrs.business.common.ServiceLocator.getInstance(ServiceLocator.java:308)
at com.mbb.crrs.web.common.dao.ParamCacheDAO.<init>(ParamCacheDAO.java:56)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:182)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:166)
at com.mbb.crrs.common.CRRSInitServlet.init(CRRSInitServlet.java:33)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #0003BA7B25C0002B000000040000394600048F300D499B25#1283336450972#com.sap.engine.services.servlets_jsp.Deploy#sap.com/CRRSRatingEAR#com.sap.engine.services.servlets_jsp.Deploy#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Warning##Plain###application [CRRSWeb] Initialization of servlet <CRRSInitServlet> failed! The error is: com.mbb.crrs.common.exceptions.ApplicationConfigurationException: Unable to connect to WAS at 172.31.40.10:52004: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:143)
at com.mbb.crrs.business.common.InitialContextFactory.getInitalContext(InitialContextFactory.java:81)
at com.mbb.crrs.business.common.ServiceLocator.<init>(ServiceLocator.java:286)
at com.mbb.crrs.business.common.ServiceLocator.getInstance(ServiceLocator.java:308)
at com.mbb.crrs.web.common.dao.ParamCacheDAO.<init>(ParamCacheDAO.java:56)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:182)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:166)
at com.mbb.crrs.common.CRRSInitServlet.init(CRRSInitServlet.java:33)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thanks. -
Unable to login to IB - again com.sap.engine.services.rmi_p4.P4IOException
We have installed a new PI 7.1 system and at he moment I have the problem that I can't login into the IB tools. I found a lot of threads with this problem but I can't find a solution for my specific problem. Have a look at the well known error log:
com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://MYHOST:8100/P4
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:668)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:461)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:133)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:176)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:121)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:109)
at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:960)
at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginAction$1.run(SplashLoginFrame.java:832)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:653)
... 15 more
Caused by: com.sap.engine.interfaces.cross.EXTstinationException: cannot establish connection with any of the available instances:
MYHOST.DOMAIN.EXT:50104 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.24.205.193 and port: 50104
at com.sap.engine.interfaces.cross.EXTstination.getNextAvailableBroker(Destination.java:59)
at com.sap.engine.interfaces.cross.EXTstination.getRemoteBroker(Destination.java:35)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
... 20 more
As you can see I call the IB via a pure hostname "MYHOST". But in the last step you can see the the FQDN "MYHOST.DOMAIN.EXT"was used. That brings me into trouble because these are different IP's. I can't reach the MYHOST.DOMAIN.EXT IP and that's why I can't login into the IB.
If I add an entry in my local host file for MYHOST.DOMAIN.EXT with the IP address I can reach all works fine but this solution is unacceptable.
The key question is why the IB uses this FQDN. I can't find any setting where this FQDN is used. I have checked the complete exchange profile, the sld and and and u2026. I always find only the pure hostname MYHOST.
Additionally I have to say that we have already a PI 7.1 system (DEV) whre I can use all tools. But this is a migrated system (from 3.0). I have only problems with that new installed empty system.Thanks Barry. I've checked all connections. They all use the short name and all work.
Thanks Joel, but I think you get me wrong. That's why I will explain it a little bit better.
I can use the IB if I manipulate my own hosts file but this is in my eyes not the right way. As I have written I can use my PI dev system without that kind of manipulation.
My new PI system is at our computer centre. The PI machine has two network interface and I can use only one of these two. As you can see at the error log the full name points to 172.24.205.193 but I only can reach the 172.20.02.193 address. For this second IP we have an entry at our DNS server. The other one (FQDN) comes from the computer center DNS server. Of course I can overwrite it with an entry in my local hosts file but I think that isn't a good solution.
The key question is: Why the full qualified domain name "MYHOST.DOMAIN.EXT" is used instead of the short name.
I call the IB via the web page
http://MYHOST:50100/dir/start/index.jsp
And as you can se at the log the first call goes to this address. But then a second call goes to MYHOST.DOMAIN.EXT:50104. And I can find any setting (exchange profile and so on) where this full qualified domain name is specified. -
Com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
Hi Subhra/ Asit,
The following is the main information form the log file and attched logfile with full info for your reference.
#1.5#00188B874AFD00320000000A000007B4000447710E97B363#1204450808802#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.default
jsp
fullWidth.jsp [email protected]a6d4d7#
#1.5#00188B874AFD00320000000B000007B4000447710E97BD23#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]a6d4d7#
#1.5#00188B874AFD00200000000B000007B4000447710E97C15A#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.framework
jsp
WAandNavPanel.jsp [email protected]16c192#
#1.5#00188B874AFD00200000000C000007B4000447710E97CCCC#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]16c192#
#1.5#00188B874AFD002900000049000007B4000447710EA4FBF8#1204450809677#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.
[EXCEPTION]
#2#fonterra.com/cmtuwlcmir~dispform/CMIRCreateNotificationDisplay#java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD00290000004A000007B4000447710EA7E5F6#1204450809865#com.tssap.dtr.client.lib.protocol.session.Cookies#sap.com/tcwddispwda#com.tssap.dtr.client.lib.protocol.session.Cookies.setCookie(Cookie)#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Java###rejecting invalid cookie for domain "": #2#.fonterra.com#JSESSIONID#
#1.5#00188B874AFD00290000004B000007B4000447710EA8000D#1204450809880#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD00290000004D000007B4000447710EA803B8#1204450809880#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: java.lang.NullPointerException: null
Exception id: [00188B874AFD00290000004B000007B4000447710EA8000D]#
#1.5#00188B874AFD00290000004E000007B4000447710EA82DD2#1204450809896#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:168)
at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:135)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendBodyText(HttpServletResponseFacade.java:957)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:948)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD002900000050000007B4000447710EA82F56#1204450809896#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
Exception id: [00188B874AFD00290000004E000007B4000447710EA82DD2]#
Regards
Krishna Kkinldy let me know what was the solution to this problem
-
Error: com.sap.engine.services.jndi.persistent
Hello All,
I am getting below error when trying to work with the Module parameter in the sender File Adapter
Attempt to process file failed with com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RequestResponseBean.
-RajeshHello Shabarish,
I am working on PI 7.0 SP 09 .
Can i make use of the bean RequestResponsebean in this version?? Please let me know -
Hi I am getting the following error on link related to Guided procedure step only for few people not for every one. Once i delete the browser cookies are cache it is working fine. Please let me know , if any one could had same issue or if any one know the reason, it is completely showing related to Standard GP service related exception. Also this errors are not coming all the time consistently, it is happening randomly. but when u get the error if you delete the cookies from browser and log off and login again from portal it is working fine.
Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception occured during processing of Web Dynpro application sap.com/caf~eu~gp~ui~inst/AInstantiation. The causing exception is nested.
[EXCEPTION]
java.lang.NullPointerException
at com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.getProcessTemplate(InternalCInstantiation.java:203)
at com.sap.caf.eu.gp.ui.inst.VInstantiation.dispatch(VInstantiation.java:182)
at com.sap.caf.eu.gp.ui.inst.VInstantiation.onEventShowInstantiationView(VInstantiation.java:564)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalVInstantiation.wdInvokeEventHandler(InternalVInstantiation.java:291)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:285)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.wdFireEventShowInstantiationView(InternalCInstantiationInterface.java:174)
at com.sap.caf.eu.gp.ui.inst.CInstantiationInterface.setTemplateId(CInstantiationInterface.java:116)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.setTemplateId(InternalCInstantiationInterface.java:129)
at com.sap.caf.eu.gp.ui.inst.WInstantiationInterfaceView.onPlugDefault(WInstantiationInterfaceView.java:83)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalWInstantiationInterfaceView.wdInvokeEventHandler(InternalWInstantiationInterfaceView.java:105)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:162)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:375)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)Govardan,
Thanks for the reply. We don't have any custom code related to GP or CAF. We created the GP Process and in the process, we attached the PCD objects to the callable object to call.
In the entire error trace it is referring only sap standard classes only. Also we haven't done any customization Except GP Process creation as i mentioned above.
com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732),
if you look at my initial report , there are two exceptions i have mentioned. before coming the above error i have observed the following error in the log file, First it is logging the following error and then next showing the above error. Looks like GPService is not able to lookup .
Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thanks -
Cannot find the class file for com.sap.portal.services.api.connectorgateway
Hi,
I was trying the "How to BI JAVA SDK in a Portal iView and get the following error.
The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.portal.services.api.connectorgateway.IConnectorGatewayService. Fix the classpath and try rebuilding this project.
I have the following in my portalapp.xml file
<property name="SharingReference" value="com.sap.portal.ivs.connectorservice"/>
and i have also added the jar file "com.sap.portal.ivs.connectorservice_api" in the set of lib's
Has some faced a similar issue? or can someone suggest how I could possibly resolve this.
Thanks,
SmithaHi Smitha:
My webdynpro dc was build failed for "This compilation unit indirectly references the missing type com.sap.engine.services.webservices.espbase.client.dynamic.content.GenericObject (typically some required class file is referencing a type outside the classpath)".
How should i do? Thank you! -
Com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException
I get the below error in Develope trace and see all the process are in status :"Inprogress" from many days and the task's related to them are inactive.How can i rectify?
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Invalid char #0x0 (:main:, row:328, col:0)).
at com.sap.engine.services.webservices.espbase.server.additions.StreamEngine.deserializeJEE(StreamEngine.java:386)Hi,
You get this error when null value is passed when the webservice is triggerred. Check for null values and pass any default value when triggering the webservice. This will solve. At the end of the error trace the exact cause for the exception will be mentioned.
Regards,
Shilpa -
Com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl
Hi SAP Expert,
I am trying to understand when I use the JCo library embedded by NetWeaver AS Java, a SessionReferenceProvider named com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl is registered to environment. What can this provider implementation do?
As I know, the session reference provider can be implemented by a runtime environment that has a session concept in order to provide JCo a simple reference to a session. JCo is using the ID associated with a JCoSessionReference internally for stateful function module invocations, i.e. the same physical connection is used for a sequence of function modules. In a generally stateless environment, e.g. JCo standalone, JCoContext.begin(JCoDestination destination) starts such a sequence for a destination. I would like to know what com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl reference a JCo session to? and how to use it.
Thanks,
JianHi Robert,
You can first try stopping a Java application named sessionmgmtjcoapplib from Star&Stop, then register yours sessionReferenceProvider again.
Jian -
In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not FoundIn my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
SAPinst error:- The java class is not found: com.sap.engine.offline.Offlin
Hi,
I am in the midst of Installing SOLMAN on RHEL5-ORACLE
Have installed IBM JDK version 1.4.2_10
During the CREATE SECURE STORE PHASE I am getting the following error:
sapinst_dev log file O/P
WARNING[E] 2008-06-09 18:04:43.225
CJSlibModule::writeError_impl()
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
TRACE 2008-06-09 18:04:43.225 [iaxxejsbas.hpp:483]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
TRACE 2008-06-09 18:04:43.243 [syuxctask.cpp:1382]
CSyTaskImpl::start(bool)
A child process has been started. Pid = 2529
TRACE 2008-06-09 18:04:43.281 [syuxctask.cpp:1382]
CSyTaskImpl::start(bool)
A child process has been started. Pid = 2530
ERROR 2008-06-09 18:04:43.310 [sixxcstepexecute.cpp:951]
FCO-00011 The step createSecureStore with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
TRACE 2008-06-09 18:04:43.317 [iaxxgenimp.cpp:752]
CGuiEngineImp::showMessageBox
<html> <head> </head> <body> <p> An error occurred while processing service SAP Solution Manager 4.0 Support Release 4 > SAP Systems > Oracle > Central System > Central System. You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS. </p> </body></html>
TRACE 2008-06-09 18:04:43.317 [iaxxgenimp.cpp:1255]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
SAPINST.LOG file O/P
WARNING 2008-06-09 18:04:43.224
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.core.server.secstorefs.SecStoreFS /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/exception.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/logging.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar create -s SMD -f /sapmnt/SMD/global/security/data/SecStore.properties -k /sapmnt/SMD/global/security/data/SecStore.key -enc -p XXXXXX" finished with return code 1. Output:
The java class is not found: com.sap.engine.offline.OfflineToolStart
WARNING[E] 2008-06-09 18:04:43.225
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
ERROR 2008-06-09 18:04:43.310
FCO-00011 The step createSecureStore with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
SecurStoreCreate log O/P
The java class is not found: com.sap.engine.offline.OfflineToolStart
Pls suggest how to resolve this issue
Pls help to resolve this issue
Rgds,
AbhijeetHi All,
I Found the Solution.
The SAPinst tool was somehow not able to extracte the
J2EEINSTALL.SAR files from the JAVA Components DVD.
So I manually extracted the the file in the temporary install folder which the SAPinst creates in the /tmp filesystem (on LINUX by deafult) during the installation process.
The following command is used (I used this on Red Hat LINUX 5.2) to extract the J2EEINSTALL.SAR file:-
/sapmnt/SMD/exe/SAPCAR
-xvf /dump/SR4_Java_Components/D51033521/DATA_UNITS/JAVA_J2EE_OSINDEP_J2EE_INST/J2EEINSTALL.SAR
/sapmnt/SMD/exe/SAPCAR -->source directory of the file SAPCAR which is used to extarct CAR / SAR files on UNIX
/dump/SR4_Java_Components/D51033521/DATA_UNITS/JAVA_J2EE_OSINDEP_J2EE_INST/J2EEINSTALL.SAR--> destination dir. where the SAPinst tool will read and execute the file.
Rgds,
Abhijeet K -
Hi all,
I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The entire trace is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Inbound Message
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="3" type="T">Sender scheme external =</Trace>
<Trace level="3" type="T">Sender agency external =</Trace>
<Trace level="3" type="T">Sender party external =</Trace>
<Trace level="3" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="1" type="T">Remote address = 10.66.10.160</Trace>
<Trace level="1" type="T">User = SFUSER</Trace>
<Trace level="1" type="T">Process ID: 760</Trace>
<Trace level="1" type="T">Work Process ID: 10</Trace>
<Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
<Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>
<Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>
<Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>
<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>
<Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>
<Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Skip Inbound Validation =</Trace>
<Trace level="3" type="T">Skip Outbound Validation =</Trace>
<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="THI,
Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
Patch level of XIAF:
1. customers SAP PI level is
Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
2. our SAP PI level is
Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
What do you think ?
Thanks -
SCM2007 on AIX/Ora install error: class com.sap.engine.offline not found
Hello Readers,
I am doing a fresh install of SCM2007 on AIX5.3, Oracle 10.2.0.4. Type of install is central instance (ABAP, Java, DB on one server). After importing ABAP, sapinst proceeds to create secure store. At that point sapinst fails with the message:
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
The log file SecureStoreCreate.log says:
The java class is not found: com.sap.engine.offline.OfflineToolStart
The command being executed is
Execution of the command "/usr/java14_64/bin/java -classpath /tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m -Xj9 com.sap.engine.offline.OfflineToolStart com.sap.security.core.server.secstorefs.SecStoreFS /tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/exception.jar:/tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/logging.jar:/tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar create -s AD1 -f /sapmnt/AD1/global/security/data/SecStore.properties -k /sapmnt/AD1/global/security/data/SecStore.key -enc -p XXXXXX" finished with return code 1.
Output:
The java class is not found: com.sap.engine.offline.OfflineToolStart
Based on another forum suggestion I extracted the J2EEINSTALL.SAR file from the Java components DVD to the temporary installation folder like so but this has not helped so far:
cd /tmp/sapinst_instdir/SCM51/SYSTEM/ORA/CENTRAL/AS
var_file=/installdvds/51032953_javacomp/J2EE_OSINDEP/J2EE-INST/J2EEINSTALL.SAR
/sapmnt/SID/exe/SAPCAR -xvf $var_file
Any suggestions? Have you come across this before? It seems to me that this particular sapinst has some bugs.
Thanks in advance!hi bhalu,
please check whether you have given the correct JCE policy files.
If you have installed IBM java then you to use the IBM JCE policy file in installation.
regards
chandru
Maybe you are looking for
-
Service Desk: Pricing data for partner could not be read
Hi all, I am trying to configure the Service Desk functionality for Service Providers (on EHP1). I follow the SAP Documentation (SAP Solution Manager: Service Desk for Service Providers) and SLA's made easy in SAP Solution Manager. Also some discussi
-
Please help me, I really don't want to start over
-
WVC54GCA appears dead - now what?
I have a WVC54GCA that has been providing me with good service for almost a year and a half. All of a sudden it stopped responding. I took it off the network, did a power-off reset, did a reset via the reset button, let it sit unconnected and withou
-
The change log for BOMs has been functional since the implementation of B1 in September of 2007. Recently, it appears that the change log is not long keeping track of changes. Has anyone ever seen this before, or have any ideas on how fix this issu
-
Dummy parent item that displays dropdown list in smartphones
Does anyone know how to create a dummy parent that will display the child items in the dropdown list? Or do you have to create an actual page for all parent items? I don't have a smartphone so I can't experiment (is there an online site that provides