These notes describe the difference between Vordel release v5.2.9 and the preceding releases
Vordel's products provide the governance, performance, interoperability and security framework which enable enterprises to exploit SOA and Cloud Computing.
Vordel XML Gateway - XML offload with data transformation, routing and acceleration
Vordel Policy Director - Centralized policy management across gateways
Vordel Reporter - Full visibility and reporting on SOA and Cloud usage
Vordel Policy Studio - Create and provision SOA policies
Vordel SOAPbox - Web Services testing
This is a patch release.
The following issues are addressed by v5.2.9.
| Issue Id | Description |
| --- | Fixed an internal implementation detail of the "trace" facility that could cause deadlock between it and the Java VM. This was most likely to occur when outputting Java stack contents to the trace under low memory conditions. |
| --- | Zulu timestamps generated between midnight and 1am would be offset by an hour, giving an incorrect time. RFC822 time format corrected |
| --- | Added support for DB2 |
| --- | Database pooling is now per Gateway process rather than per Database usage |
| --- | Added a check to see if database connection is valid before it's used, thereby preventing a pool becoming unusable if database goes down |
These notes describe the difference between Vordel release v5.2.8 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.8.
| Issue Id | Description |
| --- | Fixed memory leak in Vordel JAX provider in Element.getAttributeNS() - The Vordel JAX provider was leaking a small amount of memory each time Element.getAttributeNS() was invoked. This method is invoked in the following scenarios: when inserting a WS-Security token in a message, when using the Vordel Policy Director server, extracting SAML Attribute assertions, processing Binary Security Tokens in message |
| --- | The functionality to allow setting the timeout for a server refresh has been backported to the 521cp branch. This will get around problems where the server takes >60 seconds to refresh. The setting is defaulted to 5 minutes, and can be set under the Preferences->Server Connection Preferences option in the |
| --- | Allow user the choice of renaming a new circuit or overwriting an existing circuit when an import conflict arises |
| --- | Allow empty HTTP POST of application/x-www-form-urlencoded content type message |
| --- | Read and writing to the CRL cache on the file system is synced |
| --- | Correctly route request using the URI of the protected service as defined in its WSDL |
| --- | The WSA Headers ReplyTo, From, and FaultTo are all of type EndpointReferenceType, so they must place the address within the <wsa:Address> element, for example:- <wsa:ReplyTo><wsa:Address>value</wsa:Address></wsa:ReplyTo>. |
| --- | In the scenario with MQ and the postcard sample it looks like the JMS destination when received can be NULL |
| --- | Address resolution is considered connection failure |
| --- | Allow content types of application/soap+xml; charset=utf-8 to be set in the set message filter |
These notes describe the difference between Vordel release v5.2.7 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.7.
| Issue Id | Description |
| --- | Fixed failure to load/add certificate in Policy Studio due to "Error storing cert in entitystore: Unknown Field: usePublicKeyForKeyId" |
| --- | Fixed error when verifying certificates signed with a DSA key |
These notes describe the difference between Vordel release v5.2.6 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.6.
| Issue Id | Description |
| --- | Maintain character encoding in result serialised string when retrieving XML content from XML payload via XPath |
| --- | Included support for Utimaco HSM drivers |
| --- | Included support for Bull Trustway HSM via using public key as engine id |
| --- | Possible to configure the nonce caching via a loadable module (instructions available via support) |
| --- | Reporter was incorrectly using the shell title instead of the process name to identify the process, this caused issues if you renamed the process |
| --- | Reporter will now listen on 8050 by default instead of 8070 |
| --- | Bug in XSLT for display the list of trace and log files in HTML page is fixed |
| --- | Don't expect a server to honour "Expect: 100-continue" headers if they are not HTTP/1.1 aware. |
| --- | Improved support for SPNEGO |
| --- | Work around IIS server bug whereby it sends unsolicited "100 continue" HTTP responses. |
| --- | DBpurger has been updated to support 5.2 database scheme |
| --- | Clear out message properties that should not be shared between encryption operations |
| --- | Improved support for CRLs in custom java crypto provider. Fixes broken functionality in Policy Studio WRT importing CRLs |
| --- | Allow entity resolver find schemas via their filename, when schemalocation is a relative url |
These notes describe the difference between Vordel release v5.2.5 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.5.
| Issue Id | Description |
| --- | When HTTP 1.0 option selected in Remote Host settings the Gateway will not send any HTTP 1.1 feature headers (i.e. expect continue) |
| 5047 | Crash with assertion being hit "Assertion failed: transaction == 0, file connection.cpp, line 28" |
| --- | Support for getEncoded and getNextUpdate added to Vordel's JCE CRL implementation |
| --- | Support added for verification of ECDSA signed CRLs |
| --- | Minimize the memory required for importing WSDL in Policy Studio and Policy Director Console |
| --- | Case insensitive path matching if environment variable "INSENSITIVE_PATH_MATCH" is present |
| --- | Spurious CRLF sent by IE when running RTM is ignored (http://support.microsoft.com/kb/823099) |
| --- | Entrust GetAccess integration updated to work with non-SOAP XML |
| --- | Do not unload HTTP listeners when there is no circuit associated with a path / firewall |
| --- | The "Use SAML Ids for SAML Elements" option in the XML Signature filter was only handling the case of a SAML Assertion, it did not consider SAML protocol elements. |
| --- | Expand the wildcard references in environmental settings |
| --- | Added the ability for the Vordel XSLT processing engine to interpet "output" properties in XSLT |
| --- | If the signature contains a PublicKey that is found first for and used to verify the signature, ensure that we will extract the certificate too (if it is in the message) if the Verify for AuthN flag is true, and set correct message attrs. |
| --- | Policy Director - Change process ping task so it doesnt block PD users while on the wire to the process |
| --- | Fixed NPE if HTTP GET is called on Threatening Content filter and the user has selected to do MIME Type checking |
These notes describe the difference between Vordel release v5.2.4 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.4.
| Issue Id | Description |
| --- | SNMP alerting leaking UDP file descriptors |
| --- | Force earlier GC of JMS messages |
| --- | S/MIME Encryption content encoding set correctly |
| --- | Close database connection used in attribute retrieval on refresh |
| --- | Option to add headers to body / http headers |
These notes describe the difference between Vordel release 5.2.3 and the preceding releases
This is a patch release.
The following issues are addressed by v5.2.3.
| Issue Id | Description |
| --- | Memory leak in Vordel Reporter which would result in crash of Reporter after a number of days |
| --- | RTM metrics for CPU and memory usage not available on Solaris 10 |
| --- | Crash in XML schema validation when error with SSL connection |
| --- | Stacksize is no longer overridden from entitystore but set in the server's SystemSettings element |
| --- | Crash in Policy Studio when creating a certificate with an emailAddress attribute in the distinguished name |
| --- | RTM monitoring contains more information on the path that is run in the Service Handler filter |
| --- | Trace output contains more information on the what is run in the Service Handler filter |
| --- | Socket logging has been removed |
| --- | Logging HTTP GET request (i.e. no body) to XML file no longer causes NPE |
| --- | Policy Studio displays the inherit trace level from system settings in HTTP and HTTPs dialog |
| --- | LDAP CRLs being extracted from certificates and used incorrectly as DN |
| --- | Exception handling in RTM when writing to database |
| --- | Datasources closed during refresh |
| --- | Add header filter provides the option of where to add the header |
These notes describe the difference between Vordel release 5.2.2 and the preceding releases
This is a patch release. The following new features were added:
The following issues are addressed by 5.2.2
| Issue Id | Description |
| --- | JMS and EMS integration fixes |
| --- | Trace rollover fix with xml and txt files formats |
| --- | SSL tunnelling via proxy functionality fixed |