ADS vs Polling

hey,
the new documentation states that there's three methods of transport (send data from the server to the client) as streaming, polling and long-polling. Each has its own positive and negative points. So the important thing to understand is that ADS would also require a connection to be alive all the time in order to send the response or it will have to use polling which would only keep the connection live for a small period.
I thought of using ADS because it would reduce the traffic than a simple poll component. But it seems that streaming and long-polling would require more connections to be live most of the time.
So I have this question...
Why should we use active data services other than a simple component to update a user interface which is much more easier to implement than ADS?
Thanks

In simple terms,
- ADS should be used when you want a server push - e.g., a chat application or when you want your application/component to respond for a datachange in db or any source.
- Polling is vice-versa. Polling is done in a particular interval to check for any changes and pull the changes.
Hope this clarifies.
regards,
~Krithika

Similar Messages

  • ADS with af:poll component does not reliably deliver DB change events

    I took the Steve M's sample #156 (http://blogs.oracle.com/smuenchadf/examples) as mentioned in an earlier forum post (Re: ADF BC and the Active Data Service using af:table and modified it to use an af:activeOutputText instead of the adf:table to display the output as a result of database modifications.
    As long as I open 5 or less tabs/browser windows (combination of IE and Firefox Mozilla) with my sample application, I can see the database changes being actively delivered to each of the browser/tabs correctly. However, when I open more than 5 browser/tab windows for my application and make a database change, then most of the times the active event does not seem to be delivered to any of the browser/tab windows and the af:activeOutput text field is not updated with the latest database change. At this stage, the database change active event is not just delayed it just does not seem to fire, the only way at this stage to get the database change to show up is to open another browser tab/window. When you do that, then not only the newly opened tab/window get the latest database change but also the tabs/windows that had been opened earlier suddenly receive the database change that they had not received before the new tab/window was opened. It almost looks like the tabs/windows had received the database change event but it was queued up and for some reason was not able to refresh the browser/tab window.
    I am working off an ADE application view that has the underlying FMWTOOLS_MAIN_GENERIC_110116.1002 label. Is this a known issue and if so when can a fix be expected for this? If you need my application, I can zip it up though I believe I was getting similar behavior even with Steve's original sample 156 for more than 5 browser/tab windows.

    Hi,
    if I am correct, then you are from Oracle and should use internal forums or mailing lists.
    Frank

  • How to do ADS with EJB Datacontrol

    Hi All,
    I have a requirement to implement the ADS using Session EJB. I am using EJB 3.0.
    I should be able to filter/Sort the af:table. Also when any new row gets added in database then that table should be automitacally get updated/refreshed.
    Can anyone have such documents or any reference Urls. Please suggest how should i apporach for this.
    Thanks,
    Babasaheb Chavan

    You can refer this post :
    For displaying data in adf pages using EJB3
    http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/ejb/ejb.html
    The second requirement can be achieved by using adf poll or push mechanism.
    For ADF poll you can refer the blog:
    http://saumoinak.blogspot.com/2011/02/creating-adf-poll.html
    You can refer also this for ADS:
    http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/adv_ads.htm

  • ADS for inputtext component

    Hi
    We are trying to push some notification to adf pages from server side. These notifications will be coming from coherence.
    I know that Active data service(ADS) is available to push the notification from server to client to reflect those changes but it works with the folloiwng JSF component only .
    activeCommandToolbarButton
    activeImage
    activeOutputText
    table
    tree
    All DVT components
    We are trying to update the value in inputtext component from server side push.
    Any suggestions are welcome .
    Thanks
    Raj

    As you already know, ADS does not work with inputText (and as far as I know it only works good in a very limited fashion). If you get your use case (ADS) working with one of the other components you can try to ppr your inputText (which has some EL getting hte value from the other component) on the working ADS component. May be you are lucky and this works.
    If not you still have the option of using af:poll update the value of the inputText periodically.
    Timo

  • Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

    Hello,
    I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
    As i do not have a support account with sun or anything like that, there
    seems to be no other way to do that here (which is of course a very sad
    thing).
    Bug details:
    The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
    if a particular filedescriptor is currently in the set of monitored
    filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
    A quote from the documentation of the poll(7d) manual page taken from
    Solaris9:
    "DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
    the monitored set represented by fd. The fd field of the pollfd structure
    indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
    if the file descriptor is in the set. The events field contains the
    currently polled events. The revents field contains 0. The ioctl returns 0
    if the file descriptor is not in the set. The pollfd structure pointed by
    pfd is not modified. The ioctl returns a -1 if the call fails."
    It says that when you query for an filedescriptor which is currently being
    monitored in the set, that it would return 1, and change the events field of
    the pollfd structure to the events it's currently monitoring that fd for.
    The revents field would be set to zero.
    However the only thing which actually happens here, is that FD_ISPOLLED
    returns 1 when the fd is in the set and 0 if not. When the fd is in the
    set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
    the revents field gets changed.
    A small sample code to illustrate:
    #include <stdio.h>
    #include <unistd.h>
    #include <sys/types.h>
    #include <sys/stat.h>
    #include <fcntl.h>
    #include <sys/devpoll.h>
    main() {
    struct pollfd a;
    int dp_fd = open("/dev/poll", O_WRONLY);
    a.fd = 0; /* stdin */
    a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
    a.revents = 0;
    write(dp_fd, &a, sizeof(a));
    a.fd = 0;
    a.events = 34; /* filled in with bogus number to show malfunctioning */
    a.revents = 0;
    printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
    printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
    a.revents);
    According to the documentation of /dev/poll and namely DP_ISPOLLED this
    program is supposed to print the following:
    DP_ISPOLLED returns: 1
    a.fd=0, a.events=1, a.revents=0
    However it prints the following:
    DP_ISPOLLED returns: 1
    a.fd=0, a.events=34, a.revents=1
    You can take any number instead of '34' and it will simply remain untouched
    after the DP_ISPOLLED ioctl-request.
    I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
    with /dev/poll patch too) DP_ISPOLLED implementation is broken.
    This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
    <snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
    case DP_ISPOLLED:
    pollfd_t pollfd;
    polldat_t *pdp;
    if (pollfd.fd < 0) {
    mutex_exit(&pcp->pc_lock);
    break;
    pdp = pcache_lookup_fd(pcp, pollfd.fd);
    if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
    (pdp->pd_fp != NULL)) {
    pollfd.revents = pdp->pd_events;
    if (copyout(&pollfd, (caddr_t)arg,
    sizeof(pollfd_t))) {
    mutex_exit(&pcp->pc_lock);
    DP_REFRELE(dpep);
    return (set_errno(EFAULT));
    *rvalp = 1;
    </snippet>
    its' clearly visible that the code writes the current monitored events to
    the revents field:
    'pollfd.revents = pdp->pd_events;'
    and that it doesnt set revents to zero.
    It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
    Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
    "The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
    Hopefully this will get fixed.
    I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
    Thanks,
    bighawk

    Have I mentioned how much i love my playbook now Great job on os 2.0

  • How can I stop my Firefox browser from preventing Click Earner, a program that opens email ads on safelists, from opening the URL's in the email ads?

    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 Graciano

    You 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?

  • Ihave an ipad and an epson nx430 printer.  I tried to print my airline itinerary  and it printer 4 pages that was mostly ads.  How can i print just the itinerary which fits on oneage?

    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

  • Restricting polling in sender file adapter

    Hi friends,
    I have a requirement where I need to poll a file from an FTP server. But, if the file is being edited (some other application is writing to it) I need to avoid picking that file. Plz tell me how i can achieve this...waiting for ur replies.
    Regards,
      Shilpa

    Shilpa,
    Check out this sap note :
    [https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267|https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267]
    File Locking / Incomplete Processing
    Q: I sometimes observe that files are processed only partially, i.e., only a fragment from the file's start is converted into an XI message. Nevertheless, the file is usually archived completely. Does the File Sender Adapter honor if another process has locked a file for exclusive use?
    A: Unfortunately, the J2EE 1.3 technology the File Adapter is built upon does not support file locking. This limitation affects the File Adapter's operation. Depending on whether the JRE implementation for the operating system under which the adapter runs uses mandatory file locking or advisory file locking, opening a file that is currently being written to by another process will fail or not.
    If opening the file fails, no problem exists and the adapter will try to open the file each poll interval until it succeeds.
    However, if opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. Since XI 3.0 SP11 / PI 7.0 there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.
    If this option is not available for the settings you would like to use, the following algorithm (to be implemented in your application) may be used to ensure that the File Adapter only processes completely written files:
    Create the file using an extension, which does not get processed by the File Adapter, e.g., ".tmp"
    Write the file content
    Rename the file to its final name, so the File Adapter will notice its existence and pick it up
    Hope this will help.
    Thanks,
    Nilesh

  • Poll: Development in ABAP Objects / Webdynpro vs. classical Dynpro

    Hey there ABAP developers,
    I just want to ask if you can give me one or two minutes of your attention for two poll questions.
    At the moment I´m writing my master thesis about the development of a monitoring tool in ABAP. One of my bigger chapters is about the decision, which programming paradigm should be used for new development projects in SAP. And another important one is about WebDynpro vs. classical Dynpros.
    Because of the fact, that I can´t create any polls in here, I just started this discussion and hope for many replies .
    It would be very nice if some of you could give me an answer to the following questions (only 2 ), so that I can maybe use the result of this poll in my master thesis, if there are enough responses.
    1. What percentage of new development projects are you developing in ABAP Objects? (Not to be considered small reports that just runs for only one time)
         A. 0 %
         B. less than 25%
         C. 25% - 49%
         D. 50% - 75%
         E. more than 75%
    2. Which GUI technology do you prefer?
         A. Classical Dynpro
         B. WebDynpro
         C. Business Server Pages (BSP)
         D. others (please mention)
    I want to thank you in advance for answering the questions,
    Best regards,
    Christoph

    Hi,
    Present SAP Implementation projects are very rare, maximum projects are support and up gradations only .
    If they want Implement the  SAP  newly  , defiantly they should creating ABAP Objects.
    Why Because  ABAP Objects are Object Oriented Concepts,  so,  for  future reference and re usability..etc .
    Now Come to the First Quetion.
    if it is implementation project   ABAP Objects are   25% - 49%.
    if it is Support project ABAP Objects are   25%
    Now Come to the Second Quetion.
    Depend upon Reqmnt, but Most of the Applications are Webdynpro .  i.e 70%.
    Remaining 30% All ( BSP and GUI ....Etc..)
    This is my opinion.
    Sambaiah.Paidipelli.

  • Logical Delete in DB Polling - OSB

    Hello All,
    I have a question in polling. I have a logical delete column with Read value as 'P and unread value as 'N', Unlike BPEL, OSB's polling, does not make a record to 'P' until the process completes successfully. My DB polling adapter polls the same records while the previous instance is under processing or the previous instance ended in error. Is there a way to logically delete the record immediately once the record is read?
    To avoid this scenario, I added an error handler to make the record to 'E' if the instance encountered any error. By the time the error handler kicks in and updates the record, OSB polls the record a few times. I increased my polling frequency from 5 seconds to 30 seconds, but no luck. Any clue how to handle this scenario?
    Thanks,
    Dwarak

    Is there a way to logically delete the record immediately once the record is read?Dont do any logic in db adapter proxy. Instead make the proxy to just write to a jms queue and then have your processing logic in the jms proxy service which reads off the jms queue.

  • 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 AM

    gurpreetbhalla 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ānis

    Post 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 more

    Hi,
    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,
    Deepak

    SAP 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

Maybe you are looking for