Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Configure Timeout Properties

Configure Timeout Properties

To address any potential API timeout errors that may occur during the Operational Reference Store (ORS) specific API generation and the Java Message Service (JMS) schema generation, configure the timeout properties in the
standalone-full.xml
file. You can access the file from the following directory:
<
JBoss installation directory
>/standalone/configuration
. To configure the server properties, run the relevant commands of the configuration from the JBoss Command Line Interface (CLI).
  1. Open the
    standalone-full.xml
    using a text editor.
  2. Find the
    <security-domain>
    tag.
  3. Update read-timeout and write-timeout attribute value as provided in the following section:
    <server name="default-server"> <http-listener name="default" socket-binding="http" max-post-size="50000000" redirect-socket="https" enable-http2="true" read-timeout="180000" write-timeout="180000"/> <https-listener name="https" socket-binding="https" ssl-context="applicationSSC" enable-http2="true"/> <host name="default-host" alias="localhost"> <location name="/" handler="welcome-content"/> <http-invoker http-authentication-factory="application-http-authentication"/> </host> </server>

0 COMMENTS

We’d like to hear from you!