Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9520

Change temporary WSDL and XSD file names in JBossWS

    XMLWordPrintable

    Details

    • Affects:
      Release Notes
    • Workaround Description:
      Hide

      Only create your Service object once, and create it using a locally stored WSDL (including any external resources).

      Show
      Only create your Service object once, and create it using a locally stored WSDL (including any external resources).
    • Release Notes Text:
      Hide
      An issue was identified with the creation of temporary files which could result in inconsistencies in a load-balanced environment, also OutOfMemory errors in cases where millions of temporary files were created. The previous method added a random number to each temporary file's name but this meant naming was not consistent across restarting or rebooting an instance, also instances in a load-balanced environment. The new method uses an MD5 hash to uniquely identify each file, avoiding the issues resulting from the previous method.
      Show
      An issue was identified with the creation of temporary files which could result in inconsistencies in a load-balanced environment, also OutOfMemory errors in cases where millions of temporary files were created. The previous method added a random number to each temporary file's name but this meant naming was not consistent across restarting or rebooting an instance, also instances in a load-balanced environment. The new method uses an MD5 hash to uniquely identify each file, avoiding the issues resulting from the previous method.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      Currently JBossWS creates temporary files using File.createTempFile(). This has several issues:

      • In a load balanced environment, imported WSDL names aren't consistent between nodes.
      • There is a situation where a web service client can fill up the classloader's black list with temporary file names if the Service object is regenerated millions of times, causing OutOfMemoryErrors.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  klape Kyle Lape
                  Reporter:
                  klape Kyle Lape
                  Writer:
                  Russell Dickenson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: