Configuring SAF for JMS

Hi, all!
I have an ALSB domain on one server, and WLP 10 on another.
Trying to send jms messages from jsp on WLP to a proxy service on ALSB through SAF.
I'm able to send messages directly from a test program to the queue on ALSB used by the proxy service.
Also I'm able to send messages to the queue configured by the SAF as a remote destination.
I've configured SAF context URL as t3://someip:7001
Also tried to configure it as t3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory
with and without username and password
configured remote destinations queue Remote JNDI Name as it appears in the jndi tree of the ALSB server.
But somehow messages are not forwarded, they just stay in the queue of SAF on WLP.
Did I miss something?
Or could anybody provide an example on real situation?
Thanks in advance.

i have this lines in AdminServer logs while messaging/saf debug enabled:
####<20.06.2007 19:56:40 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347800046> <BEA-000000> <Forwarder connectTarget()>
####<20.06.2007 19:56:40 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347800046> <BEA-000000> <Retry for 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory' to 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory'>
####<20.06.2007 19:56:46 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347806500> <BEA-000000> <Forwarder reconnect(): remoteInitialCtx= null>
####<20.06.2007 19:56:46 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347806500> <BEA-000000> <Forwarder connectTarget()>
####<20.06.2007 19:56:46 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347806500> <BEA-000000> <Retry for 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory' to 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory'>
####<20.06.2007 19:57:00 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347820062> <BEA-000000> <Forwarder reconnect(): remoteInitialCtx= null>
####<20.06.2007 19:57:00 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347820062> <BEA-000000> <Forwarder connectTarget()>
####<20.06.2007 19:57:00 BDT> <Debug> <JMSSAF> <dls> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1182347820062> <BEA-000000> <Retry for 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory' to 't3://192.168.88.196:7001/weblogic.jms.XAConnectionFactory'>
...

Similar Messages

  • How to Configure Selector For JMS Bridge

    Hi,
    I was trying with Selector option in working with multiple Bridges, here is the scenario i applied.
    Created five Queues ( Q1, Q2, Q3, Q4 and Q5 ) and configured JMS Bridge Destinations having each queue with unique connection factory ( CF1, CF2, CF3, CF4 and CF5 ) and named it as D1, D2, D3, D4 and D5.
    Then created JMS Bridges as JB2 with source as D1 and destination as D2. Similarly JB3 as D1-D3, JB4 as D1-D4 and JB5 as D1-D5.
    And set Sector for each of JB2, JB3, JB4 and JB5 as Two, Three, Four and Five respectively and did restart after the changes.
    Now i am expecting the following scenario to work
    Pushing message to Q1/CF1 having Two in the content of message, hence expecting the message to be delivered to Q2/CF2 through JB2, but the messages is not moved through JB2.
    Similarly, Pushed message to Q1/CF1 having Three in the content of message, hence expecting the message to be delivered to Q3/CF3 through JB3, but the messages is not moved through JB3. Similar behavior for other messages having Four and Five in the message content.
    During the bridge configuration, selected QOS as "Atmost-Once".
    Note: All the configurations were done in same domain and the WL version is 10.3.6.0.*
    The sample message i am pushing to Q1/CF1 say "Two Test Data"* and expecting to reach Queue Q2/CF2
    Regards
    Venkata Madhu
    Edited by: vv**** on Sep 12, 2012 1:05 PM

    Hi Venkata,
    The expected selector syntax is the standard SQL-like JMS syntax. There's an extensive description of the syntax in the javadoc for javax.jms.Message.
    Selectors should normally only reference message header fields and message properties. I don't normally recommend using a selector that is based on message body as this requires using a proprietary WebLogic extension based on "xpath" XML expressions, and can have an large impact on performance. (The performance hit is caused by two factors - the need for the JMS server to unmarshal/decompress/page-in the body in order to get at its contents, and the natural cost of scanning a message body to see if it matches a string.)
    HTH,
    Tom

  • Hi can anyone tell me about SAF for  solutiondatabase in icwc

    Hi ,
    Can anyone tell me about how to configure SAF  for the solution database in ICWC.What are the steps required to customize the enterprise intelligence for SAF for useing solution/knowledge  database in CRM.
    Harish rentla

    Hi
    upon setting up SAF in the enterprise intelligence area you need to create the subject profile for the solution database for the maintanence of problems and solutions with the damage code location code and reasons codes and you need to do full indexing for the SDB for problems and solutions after pairing (joining)the 1 problem with one solution. you can access TREXADMIN transaction type for the trex config settings to view the index table status.
    Trex RFC connectivity needs to be established between SAP and CRM systems then only you can use the wizard for the SAF tool to customise
    please do reward points if helpful
    Regards
    Dinaker vikas

  • How to config SAF for searching in CRM

    Dear Sir,
    I would like to configure SAF for seach the Knowledge search in CRM, Do you have any step or manual ??
    Thank you and best regards,
    Vimol

    i can find the solution

  • Configuration for JMS Adapter Sensor action and JMS Queue sensor action..!!

    Hi,
    Id like my BPEL process to send an XML message to JMS on Websphere,I was able to do this through a JMS adapter.But I would more like to add sensors into my process which would really do the same thing - send an XML message to JMS Q.
    Now I understand that there are two ways to do this,JMS Queue and JMS Adapter - thorugh bpel sensor action.
    I am able to use JMS Queue and it works fine , but adds its own xml tags to the message,Is there any way I could send only my xml payload as a message to the queue??
    Also could any1 tell me what is the configuration for JMS Adapter sensor action?
    Any suggestions how do I go about it??

    Hey Anirudh,
    Thanx for the response :-)
    All these hold good when I have an AQ adaptor right,But the thing is I want to send a message to a 'JMS' queue with out actually using an adapter configuration wizard and everythng..So I resolved to JMS queue Sensor action..Heres the xml snippet from the sensorAction.xml files which is generated..
    <actions targetNamespace="http://xmlns.oracle.com/Test_JMS_Logging" xmlns="http://xmlns.oracle.com/bpel/sensor" xmlns:tns="http://xmlns.oracle.com/Test_JMS_Logging" xmlns:pc="http://xmlns.oracle.com/bpel/sensor">
    <action name="JMS_LogEntry" publishName="" publishType="JMSQueue" enabled="true" filter="" publishTarget="jms/L_Queue">
    <property name="JMSConnectionFactory">jms/L_QueueCF</property>
    <sensorName>ActivitySensor_JMS</sensorName>
    </action>
    </actions>
    This works grt and adds messages to the queue..But adds its own header info according to the sensor.xsd loacted at the Oracle_home\bpel\system\xmllib\ folder.
    Right now the XML message added to the Queue is:-
    <actionData xmlns="http://xmlns.oracle.com/bpel/sensor">
    <header>
    <sensor sensorName="ActivitySensor_JMS" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="AddLEntr
    y" xmlns:pc="http://xmlns.oracle.com/bpel/sensor" xmlns:ns2="http://www.ulrhome.com/2008/10/L_Entry" xmlns:tns="http://xmlns.oracle.com/Test_JMS">
    <activityConfig evalTime="completion">
    <variable outputDataType="string" outputNamespace="http://www.w3.org/2001/XMLSchema" target="$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName"/>
    </activityConfig>
    </sensor>
    <instanceId>950016</instanceId>
    <processName>Test_JMS</processName>
    <processRevision>v2009_04_15__40833</processRevision>
    <domain>default</domain>
    <timestamp>2009-04-15T11:21:23.596-04:00</timestamp>
    <midTierInstance>app01.ulrhome.com:9700</midTierInstance>
    </header>
    <payload>
    <activityData>
    <activityType>scope</activityType>
    <evalPoint>completion</evalPoint>
    <durationInSeconds>0.011</durationInSeconds>
    <duration>PT0.011S</duration>
    </activityData>
    <variableData>
    <dataType>12</dataType>
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    <queryName/>
    <target>$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName</target>
    <updaterName>AddL_Entry</updaterName>
    <updaterType>scope</updaterType>
    </variableData>
    </payload>
    </actionData>
    My requirement is that I need to add a sensor to the BPEL process which posts 'Only my payload message to the JMS queue'..
    What I would want the message in the Queue to be is : -
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    Also while creating a Sensor action I get another option as JMS Adaptor,I am not sure of what value to type in this wizard..Heres what I keyed in..M sure this is not right..Cos it dosnt work :-)
    <action name="SensorAction_JMS" publishName="" publishType="JMSAdapter" enabled="true" filter="" publishTarget="jms/LoggingQueue">
    <property name="JMSConnectionName">Log</property>
    </action>
    </actions>
    Could any 1 tel me what values are the right values..And does JMS Adapter mean that I have to create a JMS Apator in the project and give that connection name as a Value..
    I am not finding sufficiant Documentation for 'JMS Adapter' so M clueless and right now any help will be appriciated :-)
    Regards,
    Akshatha.

  • How to configure OEM for a database which is under OFS(Oracle Fail Safe).

    Hi,
    We have customer who is using database 11g and also using OFS(Oracle Fail Safe) for switching to other machine if there is any problem with current machine. So how to configure Agent in this scenario.
    What i have done is i have installed the agent on node1 and configured to monitor the database. it is monitoring properly. no issues.
    But when database started from node2, here agent will not be there. Do i need to install the agent on node2 as well. Thanks in-advance for your support.
    Regards
    DBA.

    Hi,
    You need to a script and run it on os level. Here is an example:-
    emcli relocate_targets -src_agent=agentmachine1.domain:3872
    -dest_agent=agentmachine2.domain:3872 -target_name=RACDB
    -target_type=oracle_database -copy_from_src -force=yes
    -changed_param=MachineName:agentmachine2.domain
    Regards
    Jomon
    Edited by: JohnJomon on Nov 17, 2011 2:27 PM

  • Error while passing ODI variable in JNDI Url for JMS Queue XML

    Hi,
    Facing a weird problem while passing ODI variable in JNDI Url for JMS Queue XML.
    Below is the JNDI Url configured under ODI Topology:
    JNDI Url: t3://<host_location>?d=#TEST.SCHEMA_FILE&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
    where,
    #TEST.SCHEMA_FILE --> ODI variable storing xsd name and location
    Issue Description:
    If we restart ODI server then for the first run of any ODI interface using JMS Queue XML, it is unable to get the value for ODI variable present in JNDI Url (d=#TEST.SCHEMA_FILE).
    It throws error message saying: No XSD found
    Temporary Resolution:
    As a temporary fix if we hard-code and pass the value in that ODI variable as shown below, it will successfully go through.
    eg: JNDI Url: t3://<host_location>?d=C:\XSD\test.xsd&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
    Reverting it back to variable later will have no issues and subsequent run will succeed.
    But again anytime later if server is restarted then first run will have this issue.
    Want to have permanent fix for it.
    Any one having idea on it please share. Appreciate your help!

    What ODI version are you using? It could be related to the bug in the older version as described in support note Doc ID 1290326.1

  • Dynamic configuration bean in JMS Adapter

    Hello Experts,
    My scenario is JMS(Active MQ) to File.Its just Passthrough scenario and no mapping involved.
    Filename will be coming in one of the JMS Property (say businessId) and I need to set this filename to file adapter.
    I have refered the stefan's blog and used the Dynamic configuration bean module in sender JMS adapter.
    getFilename key.1 write http://sap.com/xi/System/JMS DCJMSMessageProperty4
    getFilename value.1 module.filename
    setFilename key.1 read http://sap.com/xi/System/File FileName
    setFilename value.1 module.filename
    But required filename is not populated in the target File.Any other configuration is missing here?

    Hi Karthiga
    Did you set the ASMA properties in both your sender JMS channel and receiver File channel?
    For the JMS adapter, as shown below, you will need to enter the DCJMSMessageProperty4 into the table
    Configuring the Sender JMS Adapter - Configuring the JMS Adapter in the Integration Directory/PCK - SAP Library
    If you want to set additional JMS message attributes, select Specify Additional JMS Message Properties (Maximum of 10).
    In the table, enter the names of the JMS message properties whose values are to be included in the message header of the PI message.
    The technical names of the additional attributes are DCJMSMessageProperty0, DCJMSMessageProperty1, ..., DCJMSMessageProperty9.
    For the File adapter, you need to check the ASMA FileName attribute.
    Once you have this configured, in your message, you should be able to see that the value is in the DynamicConfiguration section of the SOAP header.
    Rgds
    Eng Swee

  • Failed to generate Alert for JMS Sender adapter

    Hi Folks,
                  My scenario is JMS to IDOC..
    I have configured the Alert rules and the alerts are working fine for the Integration engine errors.. and apart from the alert rule there is one more alert rule configured for capturing the alerts of the adapter engine..
    When i provide the queue name as invalid one .. i am able to receive the alerts for the same via alert rule of adapter engine..
    When I force to make the channel to error with the invalid headers of RFH2 (with correct queuename) the channel status is showing error ..but interestingly no alert for the same...
    Now My question here is how to test the generation of  the alerts by forcing the JMS sender channel to error. ? 
    I already checked the report SXMSALERT_LOGREADER for verification but no luck..
    Can some one throw light on this?
    Forgot to mention i am using IBM MQ ...
    Regards
    Rajesh
    Edited by: Rajesh on Jul 8, 2010 10:08 AM

    Hi Raj,
             Thanks for your reply...I am fetching the RFH headers using UDF via Dynamic config only..
    Apart from the configurations errors mentioned for alerts(as i am success in this case)...I am testing if there any data related errors like wrong RFH Headers for JMS sender adapter though the channels showing error status in this case ...but its not throwing the alerts...
    I want to know whether the alert will be triggered for this or not...if not why ..as it should..
    if yes i am unable to get.. what troubleshooting can be done for this...
    if you have any other cases (aprt from config issues)for alert trigger...and also apart from RFH headers case..can u pls share..so that i will try the same..
    MY only question here is why the adapter not trigering the alerts when wrong RFH Headers are sent along the message..but showing the channel status as red..(is it a bug ?)
    Thanks in Advance
    Rajesh

  • Alerts for JMS Adapter

    Hi All
    I am working on Alert Configuration for Communication channels . I am getting alerts for communication channel  but not alerts for Receiver JMS adapter
    Created alert catergory & classification
    Create alert rule in RWB
    Personlized for sending mail .
    I tried with new rule for only jms adapter .
    I don't want use UDF trigger alerts .
    Please help me on this , thank in advance for your help

    Hi,
    When you getting alerts for other channel means you have to get it for JMS too alert,JMS adapter part of JAVA STACK ,you can maintain alert rule as AE engine failure errors.
    still if it is not working out then
    When are you triggering ALERT??when JMS channel fails to connect MQ??when you expecting ALERT from JMS channel,pls check check the channel status in Communicataion channel monitroing.
    1)Create one more alert rule to specific to your JMS interface,then test it .
    Regards,
    Raj

  • Examples for JMS Error Queue implementation in BPEL

    Hi ,
    Please anyone provide me examples for JMS error queue implementaion in BPEL.
    Regards
    Narsi p

    Hi Narsi p,
    Please remember to mark answers accordingly... Helpful or correct, following the forum rules
    https://forums.oracle.com/forums/ann.jspa?annID=330
    Can you tell us more about what are you trying to achieve here?
    If you are just trying to configure an error queue to put the messages that couldn't be delivered, you can do this in weblogic directly.
    Configuring an Error Destination for Undelivered Messages
    http://docs.oracle.com/cd/E17904_01/web.1111/e13727/manage_apps.htm#JMSPG254
    Cheers,
    Vlad

  • Added additional user. How do I configure password for this user?

    Have two different accounts. Second accound added but don't understand how to cinfigure password for this account.

    A bit confused by your query, so can you clarify a few points.
    re: added additional user
    You do not add additional users to Thunderbird, so I presume you mean you have tried to create another mail account for someone else in your own profile.
    You do not configure passwords for other peoples email addresses as that would be a privacy issue and only they should do it.
    Lets start at the begining.
    If more than one person is using a computer, they should have their own User Account which they access via a password they choose. This gives them their own desktop view and access to programs installed on computer, such as Thunderbird.
    Thunderbird will be available for them to use.
    When you run it for the first time in their User Account, it will create a Profile in their User Account.
    Thunderbird will also then ask you to create a mail account in that Profile.
    The details you enter will ask for Name. email address and a password.
    That password is the same password they use to access their email in their webmail account using a browser, so only they should know that password and they should not divulge it to anyone - however in some cases, eg: spouses, they may know each others password.
    You can choose whether Thunderbird remembers the password or not before creating the account, but the password would still be required to configure the mail account.
    This method means that no one can see that persons emails nor access their password details because they do not know the password to the computer User Account.
    If you have only the one admin User Account which several people use, then anyone has access to anything on that computer. This may be fine if eg; spouses share the computer, but it is not a practise that should be used in any other environment.
    If you have mail accounts created in the same Thunderbird profile, then all mail and passwords are freely available for anyone to see and this may not be desired.
    Some people use only the one User Account, but they have their own Profile created in Thunderbird.
    When Thunderbird was initially run, it created a defult Profile, but you can add additional Profiles using the Profile Manager.
    The mail account is created in that Profile and then they can apply a Master Password in Thunderbird.
    This means that anyone can still see anyone's emails as on startup as anyone can select any Profile.
    But, the access to passwords is locked and removal of Master Password will remove all stored paswords to safe guard privacy.
    Some info on Master Passwords:
    * http://kb.mozillazine.org/Master_password
    Some info on creating additional Profiles using Profile Manager:
    * http://kb.mozillazine.org/Profile_Manager

  • Configuring XI over JMS

    Hi,
    I would like to configure XI over JMS using Bea Weblogic's JMS support,
    Can anybody suggest how do i go about doing it? I am new to XI.
    Thanks,
    vishnu

    Hi,
    The best place to start is the SAP online help documentation. Try these link for starters (you will see more links on the left navigation too).
    http://help.sap.com/saphelp_nw04/helpdata/en/e8/01683c43e87845e10000000a11402f/frameset.htm
    Another tip is that you can search SAP documentation directly from SDN in the search on the top left of the SDN site
    I hope this helps,
    Mike.

  • 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

  • Using MySQL DB on Weblogic 10.3.2 for JMS Store and etc.

    Hi,
    I am planning to use MySQL DB w Weblogic 10.3.2 server.
    I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
    Can anyone please help me understand any serious issues or considerations of this combination?
    Thanks
    Sagar

    Hi,
    I am planning to use MySQL DB w Weblogic 10.3.2 server.
    I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
    Can anyone please help me understand any serious issues or considerations of this combination?
    Thanks
    Sagar

Maybe you are looking for

  • Graphic Card Installation for HP Sleekbook b007ee

    Hi there.... I've a hp sleekbook b007ee laptop (i3 processor) coming with an 1 GB nvidia integrated graphics.. Now I need to upgrade my laptop with an additional graphic card.. is this possible, if yes which is the best graphic card for this laptop..

  • Close open Po's

    Hi experts , How to close open PO's , we have n number of open po's , but it has to get close .??? And , with closing the PO , whether it possible to delete all po's . Suggest how to do the above scenrio's .. Thnaks

  • No Longer Quiet since 10.4.8

    I was fine after the firmware update, but with 10.4.8 update yesterday I now have constant fan noise vs CPU whine. REALLY annoying. Anyone have suggestions?

  • Hyphenation sometimes not working in FM9

    Hello, FM9p196, XP SP3 Sometimes words are hyphenated but no hyphen appears. Anyone noticed this? Best regards, Mats

  • Quick Selection Tool Doesn't Use Shift in the Expected Manner

    Generally speaking, if you click somewhere with a tool that you stroke on an image, then hold the Shift key down and click somewhere else, the tool will be stroked in a straight line from the prior point to the current point.  This is very handy unde