Spool list not available in SM37

HI,
       i'm facing a error "spool list not avaiable" when i execute a background job and the job status is in finished state,but when i click the spool button i'm facing this error. I tried the sap note 1372936 and 1174127 but both notes are in cannot be implemented status.I tried hard to search a solution, but couldn't find.Please help if anyone knows the solution.

Hello,
What release and SP level your SAP system has ?
Thanks

Similar Messages

  • Spool list not available from SM37

    Hi All,
    We have scheduled a job and running successfully.
    But spool list not displayed from SM37, whereas spool request generated in SP01 at the same time when the job is completed.
    We've checked with the developer and they dint find anything wrong from program end.
    Kindly suggest what is going wrong here.
    Thanks in advance......

    Hi,
    Apply the following SAP notes to resolve this problem:
    1372936 - Spool lists no longer displayed from SM37 after SP
    1174127 - Job refers to incorrect spool request
    regards,
    Aidan

  • Spool List not available

    I am not able to see the spool when i run my program in background.
    I run it by executing the program in se38 choosing the option as execute in background. I am of the idea that SAP creates a spool on its own when i run any program that has a list output without me having to code anythin explicitly for it.
    please suggest me some ways of checking why is it happening !! this is urgent !!
    Thanks.
    Shiv

    You could write a wrapper program that does a submit.
    Do F1 help to see the extensions of this statement,  you can set the print parameters there.
    SUBMIT <program> to SAP-SPOOL.
    You can also set these parameters if you were to schedule this in a job via SM36.
    You can also set these defaults in your user profile, but this would make it so for ALL reports that you run.  Maybe not such a good idea.
    Also you must verify that you are actually generating ouput.  Do you get the list running in dialog mode?
    Regards,
    Rich Heilman

  • Error in Email via spool list recipient feature in SM37

    Hello Experts.
    I encounter a strange problem. I am not able to send Email to external Email addresses (Lotus Notes) while I am using Distribution list option in spool list recipient option in SM37 background job. I am getting an error in SOST called 'Message cannot be transferred to node SMTP due to connection error (final)'.
    I am Able to get email with spool on my SAP inbox if I use the option 'Internal user' in spool recipient.
    Also, if I send an email in a custom program via function 'SO_NEW_DOCUMENT_ATT_SEND_API1', I am successfully able to send the email to Lotus notes id using the same distribution list. So, I suppose all the basis settings in SCOT, SU01, SICF are correct.
    I checked with my basis team as well but they also see all the email settings as correct.
    My spool is very small one and I have all the access in the system.
    Anyone having any idea for this issue, please share.
    Regards,
    Diwakar

    I found the answer myself.
    In SCOT, SMTP setting, Output format for ABAP list needs to be set as 'PDF' or 'TXT' instead of 'HTM'.
    With HTM, it was going in for error for spool email.
    Regards,
    Diwakar

  • Spool visible in sp01 but not available in sm37

    Hi group,
    I am facing the following problem. There is a pgm that creates two spool requests, and they are visible when i see it in sp01, but when we see it in sm37 only the last spool request is available. Pls help.
    Regards,
    Divya.

    The job status is complete and both the requests are available in sp01. but when we display the spools in sm37 just the last spool is available.
    This is the sample code
    REPORT  zspoolreq1                               .
    DATA: w_param       LIKE pri_params,
          w_valid,
          w_text        LIKE pri_params-prtxt.
    PERFORM open_spool.
    PERFORM open_second_spool.
    FORM open_spool .
      NEW-PAGE PRINT ON PARAMETERS w_param NO DIALOG.
      WRITE: / 'First Spool Request'.
      NEW-PAGE PRINT OFF.
    ENDFORM.                    "open_spool
    FORM open_second_spool.
      NEW-PAGE PRINT ON PARAMETERS w_param NO DIALOG.
      WRITE: / 'Second Spool Request'.
      NEW-PAGE PRINT OFF.
    ENDFORM.
    null
    Message was edited by:
            divya rajendiran

  • Spool  List not printing in Background

    Hi,
       When i try to execute the report in background in development system i can able to see the spool list, whereas when i try to execute the same report in testimg server(may be with more data) i can not see the spool list but the job is in finish status.
    Please can i know the reason for the same.
    Thanks & Regards,
    Sudheer.

    Hi!
    This may be because you started the program with the option, not to create new spool request, or to delete the spool request immediately.
    When you run your program in background, check the printer options also.
    Regards
    Tamá

  • Entries in rsrd_log are not available in sm37

    Hi all,
    I have some "yellow" logs for sending workbooks in the rsrd_log with the message User cannot be used for background processing. But now the user can be used.......
    Now I want to repeat scheduling in the sm37, but the "yellow" jobs are not available.
    I hope you can help me
    Kind regards
    Peter

    Hi,
    Pls refer the below links.
    http://www.tnsr.eu/fileadmin/user_upload/Documenten/PDF/How_To/How_To...Troubleshoot_Information_Broadcasting.pdf
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00738f64-ff95-2b10-0eb1-dfe8859e5bf5
    Hope it helps you,
    Regards,
    Ravindra.

  • Backing up the BB messenger contact list not available

    In the old versions of Blackberry, we had the option to backup the BB messenger contact list to the device, the media card, or remotely to an email. However, this feature is not available in the new BB Z10 !!!!! This feature is significant and necessary for all users Why was it omitted in the Z10 ??

    Your BBM contact list is now attached to, and backed up to, your BlackBerry ID.

  • Spool icon not visible in SM37

    Hi,
    I have created one classical program using 'Write' statement to show output on screen.
    Now i am running this program in background mode by choosing option SE38 -> Program -> Execute in Background
    I can see my finished job in SM37. Now issue is that on same SM37 screen i can't view spool icon also when i select job and press button 'Spool', message is triggered saying  'No List available' though for same job, spool is generated and that no. i can see in Job log.
    User want to view spool from SM37 screen, instead of copying no from job log and inserting into transaction SP01
    Plz help...

    Hi,
    @BreakPoint
    I am not touching any print settings while running program in Background mode. Getting spool output is not my problem. Spool is generated properly for my job only problem i am facing is that i can't view that spool from SM37 transaction every time i need to go to SP01 transaction to view output.
    Few addition:
    Aactually my program has 2 options:-
    1. Online mode: here i am generating spool request using below FM
    * Read, determine, change spool print parameters and archive parameters
      CALL FUNCTION 'GET_PRINT_PARAMETERS'
        EXPORTING
          in_archive_parameters  = lw_arcpar
          in_parameters          = lw_pripar
          layout                 = l_lay
          line_count             = l_lines
          line_size              = l_cols
          no_dialog              = 'X'
        IMPORTING
          out_archive_parameters = lw_arcpar
          out_parameters         = lw_pripar
          valid                  = l_val
        EXCEPTIONS
          archive_info_not_found = 1
          invalid_print_params   = 2
          invalid_archive_params = 3
          OTHERS                 = 4.
    2. Background mode: I have used sy-batch to determine background mode. If program execution is in background then above FM will never trigger. In short for Online mode i am explicitly creating spool using FM
    If program executed in online mode first and then Background then i am getting above issue.
    Anything i am missing?
    Edited by: Amol Deshpande on Oct 19, 2010 7:25 PM

  • Human Task in jDeveloper 11g users list not available

    I have the problem, I defined SQL authenticator in wenlogic, and I want to do assignment at human task. But, human task only see jazn users, alhough I see the users defined in db at weblogic console
    Caused By: ORABPEL-10509
    User not found.
    User "bpmuser1" is not found in configuration "jazn.com"
    Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
    at oracle.tip.pc.services.identity.jps.JpsProvider.lookupUser(JpsProvider.java:795)
    at oracle.tip.pc.services.identity.jps.AuthorizationServiceImpl.lookupUser(AuthorizationServiceImpl.java:223)
    at oracle.tip.pc.services.identity.jps.IdentityServiceImpl.lookupUser(IdentityServiceImpl.java:171)
    at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3670)
    at oracle.bpel.services.workflow.verification.impl.VerificationService.c
    How do I make users from myrealm in WLS available to the worklist app?

    Hi ppssrr,
    Check the providers are in "SUFFICIENT" mode,both, DefaultAutenticator as your own.
    Other way:
    If I remember correctly, you can use "External Routing", creating an allocation rule from an external supplier.
    Then assign participant based on that rule as.
    More info: Configuring Human Tasks - 11g Release 1 (11.1.1.7)
    Greetings.

  • PWA : Timesheet Manager list not available when submitting TS for Approval

    I've set the Timesheet Managers users in PWA settings and unchecked ‘Fixed
    Approval Routing’.
    On
    submitting the TS for approval in the sending request the control to choose the TS manager approver
    is missing... as there was a fixed route, but it's not the case.

    Hi,
    Please refer to this
    article.
    When you uncheck the fixed approval routing, while submitting a timesheet, Project Server will popup the list of predefined timesheet managers so the user can choose who will be approving his timesheet.
    If you check the option, then Project Server will send the timesheet for approval to the timesheet manager of the user (as it used to be in PS2010).
    Hope this helps,
    Guillaume Rouyre, MBA, MVP, P-Seller |

  • Supplier list not available

    Hi,
    I have created sales order successfully using the id proc_sales. while creating PO using proc_agent user, I need to assign the supplier to the sales order qty which is required to be procuired.
    Now when  I am going to select suplier, It is not showing any supplier, I am stuck here How to get the supplier list.
    Please suggest...
    Regards,
    Sanjeev Mourya

    Hi
    Please find the below log files details.
    LOG File details -
    was sent from host with IP= / Name=. Expiration reason was: . RID=
    [EXCEPTION]
    #6#/webdynpro/dispatcher/sap.com/cafeugpuirtwc/WorkCenterRunTime#127.0.0.1#127.0.0.1#Application session has expired. Please restart the application.#7936e4c0e82b11dbbf9b0018fe79f67c#com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionManagementPostProcessing(ClientSession.java:800)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:251)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0018FE79F67C0068000009400000090400042DD5BD5E66D5#1176295935259#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionManagementPostProcessing(ClientSession.java:800)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:251)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0018FE79F67C0068000009420000090400042DD5BD5E6975#1176295935259#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
    Exception id: [0018FE79F67C0068000009400000090400042DD5BD5E66D5]#
    #1.5#0018FE79F67C005E00000D3F0000090400042DD5BD658E5F#1176295935728#com.sap.workflow.wizard.reg.JWFWizardConnector#sap.com/tcwddispwda#com.sap.workflow.wizard.reg.JWFWizardConnector#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###getAllInstances:null#
    #1.5#0018FE79F67C005E00000D400000090400042DD5BD658F2D#1176295935728#com.sap.workflow.wizard.reg.JWFWizardConnector#sap.com/tcwddispwda#com.sap.workflow.wizard.reg.JWFWizardConnector#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###getAllInstances:null#
    #1.5#0018FE79F67C005E00000D410000090400042DD5BD684A37#1176295935916#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#sap.com/tcwddispwda#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###In execute() --- begin#
    #1.5#0018FE79F67C006B00000AC70000090400042DD5BD7791A2#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###javax.resource.spi.EISSystemException: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000AC80000090400042DD5BD77972E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.init(CatalogDataPoolingManager.java:255)#
    #1.5#0018FE79F67C006B00000AC90000090400042DD5BD7797AF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.getCatalog(CatalogDataPoolingManager.java:127)#
    #1.5#0018FE79F67C006B00000ACA0000090400042DD5BD779824#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmManagedConnectionFactory.createManagedConnection(MdmManagedConnectionFactory.java:102)#
    #1.5#0018FE79F67C006B00000ACB0000090400042DD5BD779899#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)#
    #1.5#0018FE79F67C006B00000ACC0000090400042DD5BD779912#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)#
    #1.5#0018FE79F67C006B00000ACD0000090400042DD5BD779986#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:216)#
    #1.5#0018FE79F67C006B00000ACE0000090400042DD5BD7799F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000ACF0000090400042DD5BD779A68#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000AD00000090400042DD5BD779AD6#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000AD10000090400042DD5BD779B55#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000AD20000090400042DD5BD779BD0#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000AD30000090400042DD5BD779C3E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000AD40000090400042DD5BD779CAF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000AD50000090400042DD5BD779D1F#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000AD60000090400042DD5BD779D8D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000AD70000090400042DD5BD779E02#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000AD80000090400042DD5BD779E78#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000AD90000090400042DD5BD779EEF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000ADA0000090400042DD5BD779F63#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000ADB0000090400042DD5BD779FCE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000ADC0000090400042DD5BD77A03C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000ADD0000090400042DD5BD77A0AB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000ADE0000090400042DD5BD77A11D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000ADF0000090400042DD5BD77A190#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000AE00000090400042DD5BD77A203#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000AE10000090400042DD5BD77A275#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000AE20000090400042DD5BD77A2F0#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000AE30000090400042DD5BD77A362#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000AE40000090400042DD5BD77A3D5#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000AE50000090400042DD5BD77A446#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000AE60000090400042DD5BD77A4BC#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000AE70000090400042DD5BD77A52D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000AE80000090400042DD5BD77A59A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000AE90000090400042DD5BD77A608#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000AEA0000090400042DD5BD77A67D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000AEB0000090400042DD5BD77A700#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###javax.resource.spi.EISSystemException: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000AEC0000090400042DD5BD77A778#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.init(CatalogDataPoolingManager.java:255)#
    #1.5#0018FE79F67C006B00000AED0000090400042DD5BD77A7E8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.getCatalog(CatalogDataPoolingManager.java:127)#
    #1.5#0018FE79F67C006B00000AEE0000090400042DD5BD77A859#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmManagedConnectionFactory.createManagedConnection(MdmManagedConnectionFactory.java:102)#
    #1.5#0018FE79F67C006B00000AEF0000090400042DD5BD77A8CD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)#
    #1.5#0018FE79F67C006B00000AF00000090400042DD5BD77A940#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)#
    #1.5#0018FE79F67C006B00000AF10000090400042DD5BD77A9B3#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:216)#
    #1.5#0018FE79F67C006B00000AF20000090400042DD5BD77AA29#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000AF30000090400042DD5BD77AA96#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000AF40000090400042DD5BD77AB04#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000AF50000090400042DD5BD77AB7C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000AF60000090400042DD5BD77ABF5#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000AF70000090400042DD5BD77AC61#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000AF80000090400042DD5BD77ACCF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000AF90000090400042DD5BD77AD3E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000AFA0000090400042DD5BD77ADA9#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000AFB0000090400042DD5BD77AE28#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000AFC0000090400042DD5BD77AE99#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000AFD0000090400042DD5BD77AF0A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000AFE0000090400042DD5BD77AF7C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000AFF0000090400042DD5BD77AFE6#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000B000000090400042DD5BD77B051#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000B010000090400042DD5BD77B0BD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000B020000090400042DD5BD77B12D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000B030000090400042DD5BD77B19E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000B040000090400042DD5BD77B216#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000B050000090400042DD5BD77B287#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000B060000090400042DD5BD77B2F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000B070000090400042DD5BD77B36B#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000B080000090400042DD5BD77B3D8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000B090000090400042DD5BD77B448#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000B0A0000090400042DD5BD77B4BE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000B0B0000090400042DD5BD77B52C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000B0C0000090400042DD5BD77B59C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000B0D0000090400042DD5BD77B608#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000B0E0000090400042DD5BD77B676#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000B0F0000090400042DD5BD77B716#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000B100000090400042DD5BD77BACC#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:226)#
    #1.5#0018FE79F67C006B00000B110000090400042DD5BD77BB43#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000B120000090400042DD5BD77BBAF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000B130000090400042DD5BD77BC1A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000B140000090400042DD5BD77BC96#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000B150000090400042DD5BD77BD0D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000B160000090400042DD5BD77BD7D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000B170000090400042DD5BD77BDEB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000B180000090400042DD5BD77BE59#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000B190000090400042DD5BD77BEC3#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000B1A0000090400042DD5BD77BF36#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000B1B0000090400042DD5BD77BFA4#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000B1C0000090400042DD5BD77C014#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000B1D0000090400042DD5BD77C085#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000B1E0000090400042DD5BD77C0EE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000B1F0000090400042DD5BD77C162#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000B200000090400042DD5BD77C1CD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000B210000090400042DD5BD77C23B#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000B220000090400042DD5BD77C2AB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000B230000090400042DD5BD77C31A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000B240000090400042DD5BD77C388#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000B250000090400042DD5BD77C3F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000B260000090400042DD5BD77C467#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000B270000090400042DD5BD77C4D9#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000B280000090400042DD5BD77C547#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000B290000090400042DD5BD77C5BC#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000B2A0000090400042DD5BD77C629#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000B2B0000090400042DD5BD77C696#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000B2C0000090400042DD5BD77C701#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000B2D0000090400042DD5BD77C76E#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000B2E0000090400042DD5BD77D08A#1176295936931#com.sap.engine.services.ejb#sap.com/XApps_GetSuppliersByProductID_WS_Ear#com.sap.engine.services.ejb#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Java###
    [EXCEPTION]
    #1#com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getSuppliersByProductID.
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:119)
         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.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.NullPointerException
         at com.sap.esadiscovery.mdm.MDM_DAO.disconnectToMDM_Managed(MDM_DAO.java:54)
         at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:699)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)
         ... 25 more
    java.lang.NullPointerException
         at com.sap.esadiscovery.mdm.MDM_DAO.disconnectToMDM_Managed(MDM_DAO.java:54)
         at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:699)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)
         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.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0018FE79F67C005E00000D420000090400042DD5BD77DCA2#1176295936931#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#sap.com/tcwddispwda#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###In execute() --- error#
    #1.5#0018FE79F67C005E00000D430000090400042DD5BD77DD22#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###javax.xml.rpc.soap.SOAPFaultException: Exception in method getSuppliersByProductID.#
    #1.5#0018FE79F67C005E00000D440000090400042DD5BD77E33D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:735)#
    #1.5#0018FE79F67C005E00000D450000090400042DD5BD77E3B5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:857)#
    #1.5#0018FE79F67C005E00000D460000090400042DD5BD77E411#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)#
    #1.5#0018FE79F67C005E00000D470000090400042DD5BD77E46B#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.proxies.Config1BindingStub.getSuppliersByProductID(Config1BindingStub.java:73)#
    #1.5#0018FE79F67C005E00000D480000090400042DD5BD77E4C5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.proxies.Config1BindingStub.getSuppliersByProductID(Config1BindingStub.java:89)#
    #1.5#0018FE79F67C005E00000D490000090400042DD5BD77E51F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.Request_XAppsGetSupplierByProductID_WSViDocument_getSuppliersByProductID.execute(Request_XAppsGetSupplierByProductID_WSViDocument_getSuppliersByProductID.java:89)#
    #1.5#0018FE79F67C005E00000D4A0000090400042DD5BD77E580#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface.execute(SuppliersListCompV2Interface.java:218)#
    #1.5#0018FE79F67C005E00000D4B0000090400042DD5BD77E5DB#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.wdp.InternalSuppliersListCompV2Interface.execute(InternalSuppliersListCompV2Interface.java:171)#
    #1.5#0018FE79F67C005E00000D4C0000090400042DD5BD77E637#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.wdp.InternalSuppliersListCompV2Interface$External.execute(InternalSuppliersListCompV2Interface.java:225)#
    #1.5#0018FE79F67C005E00000D4D0000090400042DD5BD77E694#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWD.execute(COExecWD.java:303)#
    #1.5#0018FE79F67C005E00000D4E0000090400042DD5BD77E6EA#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWD.execute(InternalCOExecWD.java:170)#
    #1.5#0018FE79F67C005E00000D4F0000090400042DD5BD77E742#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWDInterface.execute(COExecWDInterface.java:122)#
    #1.5#0018FE79F67C005E00000D500000090400042DD5BD77E79D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface.execute(InternalCOExecWDInterface.java:132)#
    #1.5#0018FE79F67C005E00000D510000090400042DD5BD77E7F7#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface$External.execute(InternalCOExecWDInterface.java:243)#
    #1.5#0018FE79F67C005E00000D520000090400042DD5BD77E851#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.act.container.VContainer.onPlugFromDispatcher(VContainer.java:367)#
    #1.5#0018FE79F67C005E00000D530000090400042DD5BD77E8AA#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.act.container.wdp.InternalVContainer.wdInvokeEventHandler(InternalVContainer.java:167)#
    #1.5#0018FE79F67C005E00000D540000090400042DD5BD77E903#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)#
    #1.5#0018FE79F67C005E00000D550000090400042DD5BD77E95C#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)#
    #1.5#0018FE79F67C005E00000D560000090400042DD5BD77E9B5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)#
    #1.5#0018FE79F67C005E00000D570000090400042DD5BD77EA0D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)#
    #1.5#0018FE79F67C005E00000D580000090400042DD5BD77EA66#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)#
    #1.5#0018FE79F67C005E00000D590000090400042DD5BD77EABF#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)#
    #1.5#0018FE79F67C005E00000D5A0000090400042DD5BD77EB18#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)#
    #1.5#0018FE79F67C005E00000D5B0000090400042DD5BD77EB73#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)#
    #1.5#0018FE79F67C005E00000D5C0000090400042DD5BD77EBCC#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:727)#
    #1.5#0018FE79F67C005E00000D5D0000090400042DD5BD77EC26#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:663)#
    #1.5#0018FE79F67C005E00000D5E0000090400042DD5BD77EC7F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:229)#
    #1.5#0018FE79F67C005E00000D5F0000090400042DD5BD77ECD8#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)#
    #1.5#0018FE79F67C005E00000D600000090400042DD5BD77ED30#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)#
    #1.5#0018FE79F67C005E00000D610000090400042DD5BD77ED8A#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:877)#
    #1.5#0018FE79F67C005E00000D620000090400042DD5BD77EDE6#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)#
    #1.5#0018FE79F67C005E00000D630000090400042DD5BD77EE3F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_10

  • Pages in offline reading list not available after powering off iPad

    Try this on your iPad:
    1. In safari, save a few web pages to your reading list
    2. Set the iPad to airplane mode
    3. Power off your iPad
    4. Power it back on
    5. Try reading the pages in your reading list
    This is what I did when going on a flight. Most of the pages I had saved could not be displayed once in the air. Some pages could be displayed, but only once. Once I left the page, I could it not bring back up a second time.
    Does anyone experience the same? In my case, the trigger of the problem seems to be powering off the iPad (which is what you are supposed to do during airplane take off).
    Any ideas how I can resolve the issue, other than not powering the iPad off?
    Thank you!

    I could not reproduce the behavior that you are experiencing in Safari. I have no problems at all using the Reading List in Airplane mode after turning the iPad off and on again. You can try some basic housekeeping stuff with Safari and the iPad.
    Clear the Safari cache and see if that helps, reboot the iPad and see if that helps. You can also try closing Safari before you power off so that you are launching Safari all over again rather than just activating it from the inactive state in the task bar.
    Go to Settings>Safari>Clear History, Cookies and Data. Clearing history is not a necessity.
    Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.
    Quit the app completely and relaunch after start up. Go to the home screen first by tapping the home button. Double tap the home button and the task bar will appear with all of your recent/open apps displayed at the bottom. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button or anywhere above the task bar. Restart the iPad and launch Safari again.

  • Want to know table which stores SPOOL LIST RECIPIENT address in SM37.

    I found that for one of teh job name the value of the field is RECOBJKEY "DLI36000000000176 37000000029574" in table TBTCO.So how to get the SO_KEY value from this.
    thanks again in advance.

    The Basic idea is to get the recipient value from the Job name.I found one way of doing is to
    goto SWO1. enter "RECIPIENT" click test
    click full key. pass the logical system as your own logical system like DRXCLNT500 or what ever, and pass DLI36000000000176 37000000029574 in the key. (copy paste exactly as you pick from TBTCO including the spaces).
    but the first issue using the above option is that i dont see any email values in any of the attributes or i am not seeing into the correct attributes.
    Seconldly, Also i have another scenario where the field RECOBJKEY "USR33000000004760           37000000156636" in table TBTCO for which the above the optino is not working.
    Can somone help on this question.

  • Oracle Reports Components list not available in BI Publisher

    I have configured the Oracle Report Security settings in oracle Business intelligence publisher, Add oracle report, when i try to ADD report in region, it didn't display Oracle Reports Components list. Pl suggest, what should i do
    Regards,

    I had a similar issue in 10.3.3.1.
    Try this:
    http://oraclebizint.wordpress.com/2007/11/06/oracle-bi-publisher-and-bi-ee-invisible-admin-tab/

Maybe you are looking for