Skip to main content
S
Srinivas_25612-Amethyst
12-Amethyst
May 16, 2025
Solved

ESI Response File Generation

  • May 16, 2025
  • 1 reply
  • 773 views

Version: Windchill 12.1

 

Use Case: Taking hours of time to get ESI response file Generation


Description:

After we upgraded Windchill 11.1 to 12.1 and also to database update to 19c,we are seeing significant increase in ESI response file generation. In Windchill 11.1,BOM with 500 parts with Options and assigned expressions used to take less than one minute and now it is taking more than 8 minutes. In most of business cases, we release more than 5 BOMs in sign ECN and that is taking 40 minutes to generate ESI Response file. Checked with PTC,they are saying that is expected behavior but it is not the case in Windchill 11.1. Posting the message here to check If anyone experienced similar issue.

 

Any insights or suggestions would be greatly appreciated.

Best answer by Srinivas_256

Hi,

 

There is bug in PTC Code,they are fixing it now.Below article and SPR raised for this

Article - CS449461 - Windchill ESI Response xml is taking lot of time to generate when the new unchanged Release Activity is created for the same choice

1 reply

Fadel
Fadel23-Emerald I
23-Emerald I
May 16, 2025
  • Belo some points to check : 
    1. within the ESIResponseMetaInfo.xml -> setting the 'Unchanged_Specifications' to false
    2. within the Site Preferences -> Setting the 'ESI - Settings - Result - Log Failed Subtransactions' to 'No'
    3. Review the running Workflow processes via Site > Utilities > Workflow Process Administration with selecting ESI Process Template to check whether there are a mass of running processes
    4. Terminate any old ESI workflow for which the publication has completed
  • Increase maximum number of database connections allowed
    • Increase wt.pom.maxDbConnections property in Windchill/db/db.properties
    • Caution: Increasing the number of database connections can lead to low memory problems in the MethodServer to validate on test server 
Buiꓘa
    S
    Srinivas_25612-AmethystAuthor
    12-Amethyst
    May 20, 2025

    Hi Fade,

    Thank you very much for your response.

      1. within the ESIResponseMetaInfo.xml -> setting the 'Unchanged_Specifications' to falseWe need this detail,because our ERP interface is conifgured such a way it will look for this detail.
      2. within the Site Preferences -> Setting the 'ESI - Settings - Result - Log Failed Subtransactions' to 'No'
      3. Review the running Workflow processes via Site > Utilities > Workflow Process Administration with selecting ESI Process Template to check whether there are a mass of running processes
      4. Terminate any old ESI workflow for which the publication has completed - We dont have old or long running queries
    • Increase maximum number of database connections allowed
      • Increase wt.pom.maxDbConnections property in Windchill/db/db.properties
      • Caution: Increasing the number of database connections can lead to low memory problems in the MethodServer to validate on test server
        I increased DB connections but no luck,
        We are looking at tuning our oracle database to see If we can find ways to reduce the response time.Will keep here posted.

    Thank you

    Srinivas

    S
    Srinivas_25612-AmethystAuthorAnswer
    12-Amethyst
    July 29, 2025

    Hi,

     

    There is bug in PTC Code,they are fixing it now.Below article and SPR raised for this

    Article - CS449461 - Windchill ESI Response xml is taking lot of time to generate when the new unchanged Release Activity is created for the same choice

    Terms & ConditionsCookie settingsAccessibility statement