ADS: ICM_HTTP_CONNECTION_FAILED
Hello,
I am facing some issues with the ADS configuration. I checked all the programs (FP_TEST_00 and FP_PDF_TEST_00) and i keep getting into this error:
Error Code: 100.101
Error Message: SOAP Runtime Exception: CSOAPExceptionTransport : HTTP receive failed with exception communication_failure.
I also checked the ADS connection and i get the following error:
ICM_HTTP_CONNECTION_FAILED
I am not sure why this issue comes up, but would appreciate any thoughts/comments.
I have gone through the Adobe Configuration documentation multiple times and have also looked at the following SAP notes, but to no avail.
SAP Note 944221
SAP Note 915399
Please advise if there is anything i might be missing.
Thanks,
Bhushan.
Hello,
please ensure that you have active HTTP port in your ICM.
This is needed for the connection to the enigne.
Best regards,
Dezso
Similar Messages
-
Issues faced while setting up SSL for ADS (Java + ABAP)
Hi,
Connection test to test SSL connection to ADS using program FP_PDF_TEST_00 fails with the following exception:
ERROR CODE : 100.101
ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP receive failed with exception communication_failure
SOAP Framework error: SOAP Runtime Exception: CSoapExceptionTransport : HTTP receive failed with exception communication_failure(100.101).
I have exchanged certifcate between Java (ABAP stack client certificate uploaded in trusted CA, also assigned to SSL port socket and is asigned to ADSUSER) and ABAP stacks for authentication.
Using web service navigator to test the ADS web service fails too:
https://cx8.vshodc.lntinfotech.com:50001/AdobeDocumentServicesSec/Config?style=rpc
It displays the page to enter userid password. I have entered correct credentails still the same page is displayed on selecting SUBMIT.
Any help on this would be highly appreciated!
Thanks,
ChitraliCheck the notes and suggestions on this threads,
ADS: ICM_HTTP_CONNECTION_FAILED
Re: Adobe document service error: SOAP Runtime Exception
That might help
Regards
Juan -
ICM_HTTP_CONNECTION_FAILED error in SM59
Hi,
I configured ADS and it was working fine with http service.
Now i configured SSL in Java and ABAP instances.
I need to setup SSL communication between these 2 instances.
I did configuration for that but in SM59 when i do connection test for ADS_HTTPS RFC it is giving me an error ICM_HTTP_CONNECTION_FAILED.
Please can anybody guide me with a solution.
With Regards,
Pradeep.BHi
Take the help from these diffferent similar threads
1.ICM_HTTP_CONNECTION_FAILED
2.ICM_HTTP_CONNECTION_FAILED and Web Services
3.Elster XI HTTP error
Best Regards
Satish kumar -
Hello All,
I am configuring the ADS in our ECC 6.0 system . I am facing two issues :
Issue 1:
I had completed all the steps for configuring ADS in the system. But when I run the Adobe form builder test from sfp transaction for the test form "FP_TEST_00" I am getting an error when executing the test function module for that test form saying :
"Exception SYSTEM_ERROR
Message ID: FPRUNX Message number:
Message:
ADS: com.adobe.ProcessingException: Problem accessing d(200101)
What might be the issue???? We configured the Basic authentication and not SSL.
Issue 2:
Our J2EE is pointing to the client 001 and 800 is the ABAP development client .
We had created a RFC destination by name "ADS" connection type "G" as part of the ADS configuration .
IN SM59 when I do a test connection on both clients ADS Rfc destination is working only in client 001 (J2ee client) and not working in 800 client In client 800 it's telling the error " SR000 : ICM_HTTP_CONNECTION_FAILED".
What might be the issue in 800 client?
Thanks & Regards
venkateshDear venkatesh,
Issue 1:
Have you performed the necessary configuration in visual administrator also....the configuration in visual administrator are more crucial...
Issue2:
The RFC "ADS" is for the java client (001) to connect to the respective service....it is not for the Abap client...thats why it is failing for 800....
Regards,
Siv -
Hello All,
I am configuring the ADS in our ECC 6.0 system . I am facing two issues :
Issue 1:
I had completed all the steps for configuring ADS in the system. But when I run the Adobe form builder test from sfp transaction for the test form "FP_TEST_00" I am getting an error when executing the test function module for that test form saying :
"Exception SYSTEM_ERROR
Message ID: FPRUNX Message number:
Message:
ADS: com.adobe.ProcessingException: Problem accessing d(200101)
What might be the issue???? We configured the Basic authentication and not SSL.
Issue 2:
Our J2EE is pointing to the client 001 and 800 is the ABAP development client .
We had created a RFC destination by name "ADS" connection type "G" as part of the ADS configuration .
IN SM59 when I do a test connection on both clients ADS Rfc destination is working only in client 001 (J2ee client) and not working in 800 client In client 800 it's telling the error " SR000 : ICM_HTTP_CONNECTION_FAILED".
What might be the issue in 800 client?
Thanks for your help in advance.
Thanks,
GreetsonISSUE 1:
If not, then check this thread and run the tests mentioned in it at your end.
Print Preview not working for Adobe forms
ISSUE 2:
Reason and Prerequisites
You are using ICM Release 6.40 or higher for HTTP connections of the SAP Web AS. In other words, your kernel release is 6.40 or higher.
Up to and including Release 7.00, ICM is only used in systems which also have an ABAP stack, and not in J2EE-only systems.
You may also be using the SAP Web Dispatcher.
Solution
The note describes the following:
Client and server roles of the ICM
List of the various ICM timeout parameters
Short description of the icm/conn_timeout parameter
Description of "Processing timeout" and "Keepalive timeout"
Configuration of the ICM parameters for the processing timeout and the keepalive timeout
Timeout parameters in the SAP Web Dispatcher
ICM kernel patches that affect timeouts
There is detailed ICM documentation in the SAP Knowledge Warehouse.
Client and server roles of the ICM
The ICM can forward incoming HTTP connections for further processing to the SAP Web Application Server; the ICM then serves as the HTTP server. The ICM can also forward outgoing HTTP connections from the SAP Web Application Server to other HTTP servers; the ICM then serves as the HTTP client.
Available parameters that control ICM timeouts
icm/conn_timeout
icm/keep_alive_timeout
icm/server_port_< n >
Parameter icm/conn_timeout
icm/conn_timeout is used to set the timeout when setting up the connection. If the timeout is exceeded, an error page is generally displayed with the information "404 Resource not found" "Partner not reached".
Therefore, exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message.
Processing timeout and keepalive timeout
The icm/keep_alive_timeout and icm/server_port_< n > parameters define the keepalive timeout and the processing timeout.
ICM distinguishes between these two types of timeout.
The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.
If the ICM is used as a server for the relevant HTTP request (in other words, when it forwards an incoming request to the SAP Web Application Server), the processing timeout is the time that the ICM will wait until a response is received from the SAP Web Application Server (ABAP or J2EE). This interval may be exceeded with long-running applications in ABAP or the J2EE engine.
If the ICM serves as a client for the relevant HTTP request (that is, when it forwards outgoing requests from the SAP Web Application Server), the processing timeout is the time that the ICM waits until a response is received from the network. This interval may also be exceeded in the case of long-running applications in the network.
The keepalive timeout specifies how long the network should remain open after a request has been processed successfully so that the TCP/IP connection does not have to be reestablished if additional requests are received.
When you set the keepalive timeout, this does not normally lead to timeout errors. You should set the keepalive timeout high enough that the connection does not have to be reestablished for requests that are sent within a short time of each other, but low enough that the number of unused open TCP/IP connections is not unnecessarily high.
Configuration of the ICM parameters for the processing timeout and the keepalive timeout
For the ICM, the parameters mentioned here are in the instance profile.
The processing timeout is set for individual services with the following parameter:
icm/server_port_ < n > = ...,PROCTIMEOUT=< s >.
The keepalive timeout can be set globally for all services of the ICM with the parameter icm/keepalive_timeout.
You can also set it for individual services by using the following parameter:
icm/server_port_ < n > = ...,TIMEOUT=< s >.
If you set this parameter, it overwrites parameter icm/keepalive_timeout for the specified service.
Even if the ICM serves as client for a request, the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol, provided that you have set TIMEOUT or PROCTIMEOUT.
If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
Timeout parameters in the SAP Web Dispatcher
The same timeout parameters are available for the SAP Web Dispatcher as for the ICM. You can change the parameters of the SAP Web Dispatcher in the profile file of the SAP Web Dispatcher (for example, sapwebdisp.pfl). We recommend that you set the same parameters in the SAP Web Dispatcher and ICM.
Known errors in ICM and Web Dispatcher timeout handling
Since 6.40 patch level 64, there have not been any known errors in ICM and Web Dispatcher timeout handling.
In Release 7.00, there are no known errors in ICM and Web Dispatcher Timeout Handling.
Known Internet Explorer errors in the keepalive timeout handling
Known errors in the keepalive handling from Internet Explorer are described in Note 900804. However, these errors are not usually displayed as timeout errors.
KEVIN
Edited by: Kevin Mike on Mar 14, 2008 11:44 AM -
Hello fellow-users of Mozilla Firefox,
I send email ads using 20 different safelists every day. To get credits for sending those ads I click email ads sent by other subscribers.
Since early this year I've been using Click Earner -- http://www.clickearner.net/ -- to help speed up this task. Click Earner "fetched"
the emails from each safelist and opened each URL advertised in each email. This was a very quick job and all I did was close each tab
displaying the URL. Credits for clicking the URL were added to my safelists accounts.
Since a week ago, without me doing anything at all, my Click Earner stopped opening the emails automatically as was the case for
several months since I started using it. Click Earner support claimed Firefox prevented the program from opening the URL in a new tab each time it fetched an email ad. True enough, yesterday when I watched Click Earner in action I saw a pop-up from Firefox saying something like "Firefox prevented..." I couldn't read the rest as the pop-up disappeared immediately. And that was the only
time I saw it.
Right now I have to open each URL manually to see the ad and earn credits. This is a very slow process, just the same as when I open the emails in my gmail account. It's useless for me to subscribe to Click Earner. And it takes forever for me to earn credits from all the safelists.
I'd appreciate it very much if any one of you folks would help me overcome this glitch. I look forward to hearing from you and thank you very much in anticipation.
Regards,
Tom GracianoYou could try turning off Firefox's pop-up blocker.
"3-bar" menu button (or Tools menu) > Options > Content
There you will find a checkbox for "Block pop-up windows". Assuming it's checked, uncheck it.
Does that return to the behavior you want? -
I have an ipad2 and an epson nx430 printer. I tried to print my airline itinerary and it printer 4 pages ,most ofwhich were ads. How can i focus just on the information that i need?
Does the website you're using offer a "printer freindly" button or perhaps the faciltiy to email the intenerary to yourself?
Matt -
Not able to write data in ADS on 636 port
Hi-
A real problem. I have configured my NWO4S UME to access LDAP using SSL, i have performed the following steps:
1)Generated a certificate for my LDAP with the FQDN e.g
xyz.testdomain.com
2)published the certifcate on the domain controller, i hope my AD will pick-up the certificate from here.
3)used the ldp tool and it connected on the 636 port. Alos, using ldifde command i was able to import the users into LDAP from 636 port.
4)Now the SAP doc says, just import the root certficate of the ADS into the trusedstore of the UME. I had a probelm here, my certficate was in .cer format, but engine was accepting the cerificate into .crt or .cert format. So changed the format by using "copy to file" and then changed the format and imported into mu ume.
5)restared the engine, but i am not able to view the contents of the LDAP eventhough the engine comes up. To add to this, on 389 port it works. I am really wondering whats wrong.
I have specified the server name, port, admin user, password, vendor and enable ssl paramaters in the configtool
On 636 port, when i try to "create user" i get some LDAP_53 error. I says some persistence problem. Please let me know what i need to do.
Your knowledge will be gr8ly appreciated.
Regards
Subramanya
Edited by: Subramanya Mudrabetta on Apr 2, 2008 10:44 AMgurpreetbhalla wrote:
Thanks for the help.
I have one doubt
I am already waiting 30 seconds , can the peer application be so slow. ???It's either slow, or there is a bug on the client side.
Btw. Why wait 30 seconds? Don't you want optimal performance?
Kaj -
Any news on ADS in cloud..?
Hi,
In the TechEd presentation SAP Interactive Forms by Adobe – Today and Tomorrow it was mentioned that Adobe Document Services are coming to the cloud... in 2014. I have searched around, but don't find any new information. Has anybody heard any news about ADS in cloud?
Thank you
JānisPost here:
http://www.apple.com/feedback/ -
Error trying to configure ADS for printing from BW reports
hi all,
i am trying to configure ADS for printing off reports from the BW portal. I am using BI 7.0 (BW Portal version 7.0 SP10) and am getting the following error i nthe default trace file.
#1.5#00187177BCAA008D000000DD0000144C00043EE522456586#1195053750220#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1678##BWD#PASS.TEST #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
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)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
#1.5#00187177BCAA008D000000E00000144C00043EE522456FA1#1195053750220#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1678##BWD#PASS.TEST #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException
Log ID: 00187177BCAA008D000000DD0000144C00043EE522456586
Initial cause
Message: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
Stack trace: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
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)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
Message: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
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)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException#
#1.5#00187177BCAA0084000000120000144C00043EE523772516#1195053770252#com.sap.ip.bi.export.xfa.impl.PDFConverter#sap.com/irj#com.sap.ip.bi.export.xfa.impl.PDFConverter#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###EXPORT XFA calcTemplate=Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out#
#1.5#00187177BCAA0084000000130000144C00043EE523772FEE#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###Exception caught: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
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)
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 53 more
#1.5#00187177BCAA0084000000140000144C00043EE523773518#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
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)
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 49 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 53 more
#1.5#00187177BCAA0084000000170000144C00043EE5237744D3#1195053770252#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/irj#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001#Hi Glenn,
i faced the same problem
did you solve yours meanwhile ?
regards,
Carsten -
SSO with KRB/ADS on Enterprise Portal 7
Dear All
while i am trying to configure SSO with KRB/ADS on Enterprise Portal 7 i am getting this on the trace file..completed the configuration through SpNego and when i try to log in its promting for user name password..
i have attched the trace file extract for your advice..
Regards
Buddhike
#1.5 #001CC45E6DA0008000000004000054FC00044F76844D9013#1213270351029#com.sap.engine.services.security.authentication.logincontext#
sap.com/com.sap.security.core.admin
#com.sap.engine.services.security.authentication.logincontext#Guest#0####3e642d50387311ddc2a0001cc45e6da0#Thread[Thread-110,5,SAPEngine_Application_Thread[impl:3]_Group]#
#0#0#Error#1#/System/Security/Authentication#Plain###
LOGIN.FAILED User:N/A Authentication Stack:com.sun.security.jgss.accept
*Login Module Flag Initialize Login Commit Abort Details*1. com.sun.security.auth.module.Krb5LoginModule OPTIONAL ok exception false null#
#1.5 #001CC45E6DA0006E00000029000054FC00044F76844D95C5#1213270351029#com.sap.engine.services.security.authentication.loginmodule.spnego.SPNegoLoginModule#sap.com/com.sap.security.core.admin#com.sap.engine.services.security.authentication.loginmodule.spnego.SPNegoLoginModule#Guest#0####3e669e50387311dda053001cc45e6da0#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Java###Acquiring credentials for realm KEELLS.INT failed
[EXCEPTION]
#1#GSSException: No valid credentials provided (Mechanism level: Attempt to obtain new ACCEPT credentials failed!) at sun.security.jgss.krb5.Krb5AcceptCredential.getKeyFromSubject(Krb5AcceptCredential.java:189)
at sun.security.jgss.krb5.Krb5AcceptCredential.getInstance(Krb5AcceptCredential.java:80)
at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:75)
at sun.security.jgss.GSSManagerImpl.getCredentialElement(GSSManagerImpl.java:149)
at sun.security.jgss.GSSCredentialImpl.add(GSSCredentialImpl.java:334)
at sun.security.jgss.GSSCredentialImpl.<init>(GSSCredentialImpl.java:44)
at sun.security.jgss.GSSManagerImpl.createCredential(GSSManagerImpl.java:102)
at com.sap.security.core.server.jaas.spnego.util.ConfigurationHelper.acquireCredentialsInCurrentThread(ConfigurationHelper.java:236)
at com.sap.security.core.server.jaas.spnego.util.ConfigurationHelper.access$000(ConfigurationHelper.java:29)
at com.sap.security.core.server.jaas.spnego.util.ConfigurationHelper$RunnableHelper.run(ConfigurationHelper.java:337)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Access Denied. at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:297)
at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
at sun.security.jgss.LoginUtility.run(LoginUtility.java:57)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.jgss.krb5.Krb5AcceptCredential.getKeyFromSubject(Krb5AcceptCredential.java:186)
... 9 more
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: Internal server error. An error log with ID [001CC45E6DA0008000000001000054FC00044F76844D8A3F] is created. For more information contact your system administrator.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
... 23 moreHi,
please check if the options defined in the KRB5LoginModule are correct.
First of all check for the option prinicpal. Did you provide this option and also provided the correct value?
This error often occurs if you provided a wrong value for option prinicpal
Cheers -
ADS service (XMLForm.exe) Utilizes 30 to 40 % of Java Stack CPU
We are currently on ECC 6 and EP 7.0; we have started using ADS service (Generating buld PDF forms) and we are noticing that it utilizes upto 30% of CPU on the Java stack.
One thing to inform is that we are using the same Java Stack for Portal, BI and R/3.
30% of CPU seems abnormal to me (At the peak of its usage the Portal Performance goes down).
Will this issue get solved if we use a dedicated Java Stack for R/3? Your Thoughts Please.
Regards,
DeepakSAP recommends very accurate (I better say pessimistic) sizing for server running productive ADS.
The best approach is to use standalone server for productive ADS usage.
IMHO, in that case you still can use the same ADS for productive, quality and even development usage.
Regards,
Petr Perstnev -
How to add Google Ads or similar in "AIR for Android" application?
Hello,
I have developed my android application (AIR for Android) in Flash Professional CS5.5. It's completed and fully tested on multiple android phones. Now I want to add Google Ads in my application to make some money.
What I already know:
I know that Adobe provides AdMob native extension API which allows you to add Google Ads in your app. But unfortunately, it's not free.
What I want:
I want a free resource through which I can add ads in my application.
Please guide me how can I achieve this?
Thanks in advance,
momersaleemYes, its for me broken, too.
I found the link in this thread:
http://forums.adobe.com/message/4036804
Maybe try to contact the author or one of the thread participants for an unbroken version? -
Until recently, I loved Firefox. Lately, when I go to any website and try to download a page, the screen freezes for between 10-20 seconds while ads load. Why the screen freezes is both frustrating and annoying. I have the latest version, nothing on my computer is different, and as I said, it didn't used to do this. Any ideas what's going on?
Create a new profile as a test to check if your current profile is causing the problems.
See "Basic Troubleshooting: Make a new profile":
* https://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.
If that new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.
See:
* http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
See:
* http://kb.mozillazine.org/Firefox_crashes
* https://support.mozilla.com/kb/Firefox+crashes
* https://support.mozilla.com/en-US/kb/latest-firefox-issues
If you have submitted Breakpad crash reports then post the IDs of one or more Breakpad crash reports (bp-xxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxx). You can find the IDs of the submitted crash reports on the about:crashes page. You can open the about:crashes page via the location bar, like you open a website.
See:
* http://kb.mozillazine.org/Breakpad (Mozilla Crash Reporter)
* https://support.mozilla.com/kb/Mozilla+Crash+Reporter
* https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report -
Problem with ADS and LDAP
I have installed Win2000 + sp1 and ADS on a computer. This computer is PDC.
After connection via LDAP I cann't get any object ( users or goups etc. ).
I try connect to ADS by java ( JNDI ).
When I use another clients of LDAP ( eg. Maxware Directory Explorer) I have
the same problem - no objects.
Can anybody help me?
Grzegorz Pszona
my e-mail: [email protected]Thanks a lot.
Softerra's browser is really good.
Thanks
Rashmi
"Anant Kadiyala" <[email protected]> wrote:
>
I used Softerra's LDAP browser. The browser is free. There is also a
java baded
LDAP browser from Univ of Michigan. I found the Softerra browser to be
more easier
to use.
-anant
"rashmi" <[email protected]> wrote:
Hi,
Can you please let me know which exact ADS tool that you used to examine
the
DN. I have Active Directory Users and Computers, Sites and Servicesand
Domain
and Trusts installed on my machine but I am not able to figure out how
to get
the DN?
Thanks
Rashmi
for Stephen Davies <[email protected]> wrote:
Grzegorz,
I have had WLS6.1 & ADS working ok using LDAP V2. Mind you it did take
a
fair bit of messing around to get it going. MS does have a few oddities,
for example the Administrators DN might look something like this:
cn=Administrator,cn=Users,dc=eglobal,dc=net
One tool that I found invaluable came with the additional support tools
for Windows 2000. The 'Active Directory Administration Tool' made it
easy to list the directory contents and examine the DNs.
Regards,
Steve
Stephen Davies
Principal Consultant
eGlobal Services Pty. Ltd.
Sydney, Australia
Ph. +61 2 9283 1033
http://www.eglobal.net/
Maybe you are looking for
-
Hi Gurus Would you please advise the steps I have to follow on BW side to make BIA starts working? Can I use process chain to include the functionality of BIA? Also as I know we have to create one Index per cube for BIA. Do we need to fill them manua
-
Looking for an App that coverts PDF to Word
Hi, looking for an app that converts PDF to Word
-
Printer Queue - How can I hide print job title and username?
Hi, Does anyone know if it is possible to hide print job title and username in the printerqueue? Because of our privacy agreement we would like to hide this information, Workstation OS: Windows 7 x64 Printserver : MS 2008 R2 Thanks in advance Mark
-
How to download RAW plugin for Elements 7
I used to be able to edit RAW files without much trouble but now I can`t . I understand that some plug in is now required but I don`t understand this or how to do it.
-
Conversion Of Text To P.D.F
Dear All We are trying to convert an internal table data into p.d.f format.the problem is the file get converted but we are unable to open that file in p.d.f format. we tried with all the function modules that is available in SAP.But stil