Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim
Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
<gesellschaft>03</gesellschaft>
<filiale>000</filiale>
<satzart>11</satzart>
<datum>00000000</datum>
<kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim
Similar Messages
-
File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi
Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, NavneetHi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet -
SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception
Hi,
I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
This is the error that I get when sending a message to the interface
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
Thanks,
Rashmi.Hi Rashmi,
I also think your problem is data related.
Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
Best Regards, Trevor -
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax
Hello,
Please explain me the error :
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/primavera/integration/server/ServerFacade : cannot initialize class because prior initialization attempt failed
Where should I find the issue and how to correct it.
RegardsHi,
This seems to be related to some deployed components on J2EE-engine being corrupt. Try re-deploy the primavera-component to fix the error. I'm guessing this component is some 3rd party or custom developed component?
Also make sure this component compiles correctly if it's a custom development component.
Br,
Kenneth -
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 -
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. -
Integrated Configurations com.sap.engine.interfaces.messaging.api.exception
Hi guys,
we are using PI 7.11.
With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
This works fine.
Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
Afterwards I treied to restart the message.
Following error occurs.
com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
trying restart the failed message ends up in the error specified aboce.
Anyone faced the same issue already?
Kind regards
JochenHI Jochen,
I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
To do a CPA Cache Refresh from the Adapter Engine:
To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
http://<host>:<port>/CPACache/refresh?mode=delta|full
The Monitoring url is like this:
http://<host>:<port>/CPACache
Check this How-to Guide on Cache, it will be useful:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
Thanks
Dhwani -
Com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException
Hi All,
PI 7.1 is sending the following error:
2009-12-10 15:55:00 Information Trying to put the message into the send queue.
2009-12-10 15:55:00 Error Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK.
2009-12-10 15:55:00 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
2009-12-10 15:55:00 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
I didn't find anything into OSS... =( Does anybody can help me?
I really appreciate your help
Regards,
Gilberto MartínezHi Suman,
Which PI version you are using? Is it double stack?
We also faced a similar problem few days back.
We have tried a below approach and succeeded.
Can you please check with T-code SXMB_MONI if there are any queues are stopped (Red circle symbol written STOP on it).
Go to t-code SMQ1/SMQ2 and click on the line items, it will open another session which will display the details of message status (Green flag-scheduled).
Click on the Resend button on the tool bar, it will show a pop-up there click on Retain button.
This will help you to restart a stucked EOIO/EO messages.
P.S: You have to determine that how many such kind of queues are stopped and so you have to manually restart those scheduled messages.
Also refer to this thread Queue stopped in sxmb_moni
Try this if it helps.
Regards,
Dipen. -
Jar for the package com.sap.engine.interfaces.messaging.api
Dear All,
I am writing a UDF where we want to use the Payload class of package com.sap.engine.interfaces.messaging.api. We are not getting the corresponding jar file.
Please suggest what should be the jar file.
Thanks and Regards,
Rana Brata Dethis you can not use at mapping runtime. You can use this API only in Adapter modules.
What is your requirement?
Edited by: Praveen Gujjeti on Feb 27, 2012 4:38 PM -
SR Log Error - | Message : com.sap.esi.uddi.sr.api.exceptions.SRException
Hi,
We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
SR Log Error
| 11-Nov-11 14:10:45.568
| Method : getClassificationSystems()
| Class : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
| ThreadID : 146
| Message : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name= ConfigurationFlags'
|
| com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
| com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
| sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| java.lang.reflect.Method.invoke(Method.java:585)
| com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
| com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
| $Proxy1087.getClassificationSystems(Unknown Source)
| com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
| sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| java.lang.reflect.Method.invoke(Method.java:585)
| com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
| com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
| com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
| com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
| com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
| com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
| com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
| com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
| com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
| com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
| SoapServlet.doPost(SoapServlet.java:51)
| javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
| javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
| com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
| com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
| com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
| com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
| com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
| com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
| com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
| com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
| com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
| com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
| com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
| com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
| com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
| com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
| com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
| com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
| com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
| com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
| com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
| com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
|Hi,
Refer Error:Service Registyr Configuration PI 7.11
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
Thanks,
Chandra -
Com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail messa
Dear All,
When we try to publish a Web Service using Service Registry, following error appears, even though my user has the roles UDDI_Admin and SERVICE_REGISTRY_READ_WRITE
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.server.proxy.depl.v3.DispositionReport
Note: We have also configured the UDDI destination as described in sap help @ http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
Thanks in Advance,
Immy.Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy. -
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 -
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 -
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
-
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.
Maybe you are looking for
-
Employee Contract Letters need to be Generated
Hi All, I need to generate Employee Contract Letters for this should I use WebADI or XML Publisher or any other solution , kindly suggest me. Regards,
-
Cannot download from Fileserve using FireFox
For a couple of weeks now, I have been unable to download from Fileserve . ( I am a free user, not premium ). I select free download, solve the Capcha , and the count-down starts normally, but when it reaches zero, instead of showing a download link
-
Only BI Administrators can receive cache seed?
Hi: I want to seed cache to everyone, say 10 users, by iBots. So I firstly purged all caches, and then delivery a report, setting the destination as "Oracle BI Server Cache" and Recipients are the 10 users. However, after done, when looking into the
-
Hello! I need to run User.. or System query by Mouse Click event.. I find solution of this problem: Tools->Queries->UserQueries... or SysteQueries (Menu UID..) Maybe there is other way, object for UserQueries... I find the table with all query (OUQR)
-
Hi Guru: We have A/R only and we want to introduce an approval process for all the credit memo greater than 7500$. My question is, is it possible to create a credit memo request without SD? If not, how to setup the workflow without credit memo reques