webMethods Integration Server 6.5 SP3 Pub Sub Fix 6 April 2009 _________________________________________________________________ This file provides important information for applying webMethods Integration Server 6.5 SP3 Pub Sub Fix 6 to webMethods Integration Server 6.5. For additional information about webMethods Integration Server, see the readme in the directory in which you installed webMethods Integration Server. Contents: 1.0 Fix Name 2.0 Product(s) Affected 3.0 Fix Requirements 4.0 Fix Contents 5.0 Platform Support 6.0 Installation 7.0 Cautions and Warnings 8.0 Globalization 9.0 Copyright 10.0 Contacting Us 1.0 Fix Name webMethods Integration Server 6.5 SP3 Pub Sub Fix 6. 2.0 Product(s) Affected This fix affects webMethods Integration Server 6.5. 3.0 Fix Requirements IS_6-5_SP3 IS_6-5_SP3_Core_Fix6 or the latest fix that supersedes this fix. IS_6-5_SP3_Audit_Fix2 or the latest fix that supersedes this fix. Broker_API_Java_6-5_SP2_Fix2 or the latest fix that supersedes this fix OR Broker_API_Java_6-5-2_Fix2 or the latest fix that supersedes this fix. 4.0 Fix Contents This fix addresses the following issues: 1-1WDQPA Integration Server does not start due to size of JoinTriggerState context in the repository. When a trigger rejects a message, Integration Server creates a record in the JoinTriggerState context in the repository. At start up, Integration Server removes these records from the JoinTriggerState context. However, if the JoinTriggerState context gets too large, Integration Server cannot start. Now, Integration Server removes entries from the JoinTriggerState context at run time, which prevents the JoinTriggerState context from becoming so large as to prevent start up. 1-1UCCPV (IS_6-5_SP3_PubSub_Fix5) If client-side queueing is disabled, documents are lost upon Broker restart. If you disable client-side queueing using the Integration Server configuration parameter "watt.server.publish.useCSQ=never", and restart the Broker while a large number of documents are being published, many documents may become lost. This issue appears in all versions of Integration Server. The error condition that was causing this problem has now been fixed, and the setting can be used without document loss. 1-1SM1IL (IS_6-5_SP3_PubSub_Fix4) Document is not processed and appears to be lost when a trigger service fails and cannot write data to the audit database because the connection to audit database is not available. When a trigger service that generates audit data is unable to write the data because the connection to the audit database is unavailable and the audit subsystem is configured to write logged data synchronously (watt.server.auditSync=true), Integration Server acknowledges the document to the Broker. The Broker then removes the document from the associated trigger client queue on the Broker. This occurs even if the document was not processed successfully by the trigger service. Additionally, because Integration Server was not able to write logged data to the audit database, the document is not available for resubmission. Integration Server now includes a server configuration parameter named watt.server.trigger.suspendOnAuditErrorWhen that you can use to indicate that Integration Sever should suspend a trigger when: - The trigger service fails, and - The trigger service cannot write audit data to the audit database because an audit exception occurs. When Integration Server suspends a trigger, it halts document processing and document retrieval for the trigger. Suspending the trigger prevents Integration Server from acknowledging the document and prevents the Broker from discarding the document. After suspending the trigger, Integration Server monitors the connection to the audit database and resumes the trigger (document processing and document retrieval) when the connection to the audit database is re-established. Integration Server retrieves the unacknowledged document from the Broker and attempts to process it again. The watt.server.trigger.suspendOnAuditErrorWhen parameter can have the following values: Never -- Indicates that Integration Server does not suspend a trigger if the trigger service ends because of an error and an audit exception occurs when the trigger service attempts to write data to the audit database. Error -- Indicates that Integration Server suspends a trigger if the trigger service ends because of an error and an audit exception occurs when the trigger service attempts to write data to the audit database.. ErrorPipelineEnabled -- Indicates that Integration Server suspends a trigger if the trigger service ends because of an error, the trigger service is configured to include the service pipeline in the audit log, and an audit exception occurs when the trigger service attempts to write data to the audit database. The default is ErrorPipelineEnabled. Integration Server must be restarted for any changes to this parameter to take effect. This server configuration parameter only applies when the audit subsystem is configured to write data synchronously (watt.server.auditSync=true). 1-1TARQM (IS_6-5_SP3_PubSub_Fix3) Problems occur when trying to create a document type from a Broker document type. In some situations, Integration Server 6.5 SP3 encounters errors when trying to create a document type from a Broker document type. Specifically, the problem occurs if the Broker document type was created for a publishable document type that references a schema. When Integration Server tries to create a document type in this situation, it issues the following error: com.wm.app.b2b.broker.conv.TypeCoderException: java.lang.ClassCastExceptioncom.wm.app.b2b.broker.conv.TypeCoderE xception: java.lang.ClassCastException. This problem has been resolved. 1-1RWEHC (IS_6-5_SP3_PubSub_Fix3) Developer does not notify user when a request to delete a Broker document type has failed. This problem occurs when a Developer user, within a single Developer session, changes a document from publishable to unpublishable, back to publishable, and finally back to unpublishable. In addition, the document being changed has a subscribing trigger. The first time the user changes the document to unpublishable, Developer prompts the user for permission to delete the associated Broker document type. If the user responds Yes, Developer displays a message stating that the Broker document type cannot be deleted because of dependencies. If, without refreshing Developer, the user changes the document back to publishable and then to unpublishable, and again responds Yes when asked for permission to delete the Broker document type, the user does not see the error message, leading the user to believe the Broker document type has been deleted, when in fact it has not. With this update, Developer will display the message stating that the Broker document type could not be deleted because of its dependencies. 1-1RQDH0 (IS_6-5_SP3_PubSub_Fix2) Client sessions for triggers increase after Broker restarts. If Broker restarts while Integration Server processes documents received by triggers, trigger client sessions on the Broker unexpectedly increase. This issue is now resolved. Triggers will not create more client sessions than allowed. 1-1PDWFC (IS_6-5_SP3_PubSub_Fix1) Dispatcher is not initialized properly. When Integration Server is not configured to connect to a Broker and the watt.server.broker.replyConsumer.multiclient parameter is set to a value greater than 1, the dispatcher is not properly initialized. Now, the dispatcher will initialize properly in the situation described above. 1-1HQWB1 (IS_6-5_SP3_PubSub_Fix1) Documents in a trigger client queue on the Broker are not distributed to the trigger. On the Broker, documents placed in a client queue for a serial trigger appear to be stuck. The trigger on Integration Server will only receive the documents if the Broker Server on which the Broker resides is restarted. Now, documents will not get stuck in a client queue for a serial trigger. 5.0 Platform Support webMethods Integration Server 6.5 SP3 Pub Sub Fix 6 is supported on the same platforms and operating systems and with the same JREs as webMethods Integration Server 6.5 SP3. 6.0 Installation 1. If you have not already done so, install any required fixes and service packs identified in section 3.0. 2. Start Integration Server if it is not running. 3. On Windows platforms, unzip IS_6-5_SP3_PubSub_Fix6.zip into \IntegrationServer. On UNIX platforms, extract the contents of IS_6-5_SP3_PubSub_Fix6.zip into \IntegrationServer. To do this, use the following jar utility: (from the IntegrationServer directory) ../jvm//bin/jar -xvf /IS_6-5_SP3_PubSub_Fix6.zip 4. From the Integration Server Administrator, in the "Packages" area of the navigation panel, select "Management". 5. Click "Install Inbound Releases". 6. From the "Release file name" list, select "WmRoot_6-5_SP3_PubSub_Fix6.zip". 7. Click "Install Release". 8. Restart Integration Server. 7.0 Cautions and Warnings None. 8.0 Globalization This fix conforms to the internationalization standards of the webMethods product suite and includes support for operation in any country, locale, or language as specified in the webMethods Installation Guide. It was not tested with non-English configurations and non-ASCII data. However, this fix has no globalization impact and can be applied to systems running in any supported locale or configuration. 8.1 Localization This fix does not require an updated Language Pack. It might contain new messages and these messages will appear in English. 9.0 Copyright Copyright (c) 2009 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their suppliers. All rights reserved. The name Software AG, webMethods, and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners. 10.0 Contacting Us Authorized technical support contacts can reach Software AG Global Support in the following ways: Web: http://advantage.webMethods.com (online support center) E-mail: support@webMethods.com Phone: North America +1-888-222-8215 or +1 703 460 2584 Europe +800 963 84-637 or +31 20 581 4151 Asia Pacific +1-888 222 8215 Japan 0120-979-762 (Toll Free in Japan) or +81-3-5405-4294 Contact information for other customer areas can be found at http://advantage.webmethods.com/contact_us. Self-service support is also available in the Advantage Knowledge Base and in Advantage Customer Forums at http://advantage.webMethods.com.