Page tree
Skip to end of metadata
Go to start of metadata

RUNTIME Migration Notes

The following bugfixes and features are subject to migration. Please perform the described migration tasks if necessary.

 Click here to expand an overview of all RUNTIME migration notes...
RUNTIME VersionNote
2020.9

This RUNTIME drops bug-compatible file system handling on Windows. Repositories older than 2011 will not start on Windows. The cause will be clearly stated in logs.

2020.4

RUN-2599 corrects the behavior of custom constructors in case their parameters are function calls with dynamic parameters. There is a slight chance that existing models have a bug that has been masked by this issue and now the incorrect behavior may surface. 

2019.13
2020.1
2020.2

The transaction logging is broken in this RUNTIME version. Final fix with 2020.3.

2018.11RUN-2264With this RUNTIME we removed support of BRIDGE version 4.1. Repositories that have been compiled with such versions will not start on BRIDGEs with Runtimes as of version 2018.11.
2018.10

RUN-2281
RUN-2383
RUN-2407

RUN-1964
RUN-2388
RUN-2408

With this RUNTIME we finally decided to activate the error log in case of comparison with NULL values (RUN-1964), or navigation to NULL references (RUN-2281) only if the modeler recompiles the service.

You can fix these model errors e.g. as follows:

  • local int = myNullObject.index if myNullObject.exists()
    Also do something in case int did not get initialized.
  • myNullString.exists() and aValidString > myNullString
2018.7RUN-1964
RUN-2388
In RUNTIME 2018.1, we fixed bug RUN-1964 concerning comparison with NULL values. With RUN-2388, we decided to not throw an exception in this case, but to log an error to the bridgeserver log. That way, all services will still run, but the error will come to notice nevertheless.
2018.6RUN-2281
RUN-2383
In RUNTIME 2018.4, we fixed bug RUN-2281 concerning navigation to NULL references. With RUN-2383, we decided to not throw an exception in this case, but to log an error to the bridgeserver log. That way, all services will still run, but the error will come to notice nevertheless.
2018.4RUN-2281With RUN-2281, we fixed a bug concerning navigating to references that are actually NULL. As of this RUNTIME, an exception will be thrown in cases like local int = myNullObject.index.
2018.2RUN-2144

With RUNTIME 2018.2, we fixed a serious bug (RUN-2144) that led to a session commit although an exception had occurred and the session should have been rolled back. If an exception occurred in an action that was followed directly by a decision node, the exception was logged and the activity was aborted, but the xUML RUNTIME assumed nevertheless that execution has been fine and committed the session.
That resulted in SQL, persistent state, JMS and POP3 changes being committed instead of rolled back in case of error. Additionally, no error handlers have been invoked either. Please read Bug: Session Commit on Exception for a more detailed explanation.
RUNTIME 2018.2 is a recommended update, because this bug can lead to inconsistent data.

RUN-1964With RUN-1964, we fixed a bug concerning comparison with NULL values. As of RUNTIME 2018.1, NULL values can only be compared for equality and inequality. All other comparisons like e.g. aValidString > NULL are rejected and an exception will be thrown.
2017.7

As of RUNTIME 2017.7, we had to introduce an implicit dependency to the Windows Universal Runtime.

To run services on Windows systems prior to Windows 10 (Windows 7, 8, 8.1, 2008 Server, 2012 Server) an up-to-date system is required. In particular the KB2999226 update must be installed.
See also Update for Universal C Runtime in Windows on the Microsoft Support pages.

If this update is not installed, some DLLs are missing and xUML services will not start (not reporting any error). The bridgeserver log will be empty. If you try to start the services manually via start.bat (as described on Troubleshooting > E2E xUML Service Startup Fails), you will get

2017.6

With this RUNTIME, we tidied up the system error codes of error domain FUTSM and reduced the error codes to 4 (from more than 20). If you are catching one of the dropped error codes in your model, you need to adapt the code. See System Errors for more information and a mapping of error codes old → new.

2017.5

REST services or adapters compiled with a BUILDER previous to 6.0.22 will not start on a BRIDGE with RUNTIME 2017.5. Please recompile your services in this case.

2017.2Starting from this RUNTIME version, Windows Vista is not supported anymore.
Please find the list of all supported operating systems on BRIDGE Installation Guide.
2014.16Starting from this RUNTIME version, Windows XP is not supported anymore. xUML services will not start-up on XP platforms due to technical implications.
Please find the list of all supported operating systems on BRIDGE Installation Guide.
2013.5With this RUNTIME version, the persistent state database schema changed to version 15. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.
If you have many persistent state objects, the schema update might take several minutes.
6.0.92.0With this RUNTIME version, the persistent state database schema changed to version 14. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.
6.0.91.0The RUNTIME upgrades the asynchronous trace database at first start. Although the new schema is fully backwards-compatible, we do not recommend switching back to an older RUNTIME and then back again to the new one. This might result in a corrupted database, that requires manual intervention to be fixed.
6.0.90.0With this RUNTIME version, the persistent state database schema changed to version 13. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.

Release Notes of the xUML RUNTIME 2020

RUNTIME 2020.10 (19.06.2020)

BugDescriptionDocumentation Link
RUN-2448Nested maps are not correctly deserialized by classToJson()
RUN-2658Memory leak if reverse host lookup fails
RUN-2670JSON deserialization omits attributes before e2e:type
ImprovementDescriptionDocumentation Link
RUN-2673Update J2RE for docker for service to 11.0.7

RUNTIME 2020.9 (08.06.2020)

Compatibility Hints

This RUNTIME drops bug-compatible file system handling on Windows. Repositories older than 2011 will not start on Windows. The cause will be clearly stated in logs.

BugDescriptionDocumentation Link
RUN-2645FileSystemAdapter: Creation of a folder for a network path with forward slashes fails
RUN-2655REST AddOn: Tabfiles not unloaded from memory
RUN-2659Memory leak logging SOAP Requests (Debug log level)
RUN-2661Interactive debugger: Setting values lead to memory leaks
RUN-2662Using security interceptor may leak memory
RUN-2663Memory leaks parsing Timer/EventObserver tabfiles
RUN-2664Memory leak in SAPIDocRecordComposer
RUN-2666Windows: crash on startup when using JSON logger configuration, or when changing log level via Console

RUNTIME 2020.8 (18.05.2020)

BugDescriptionDocumentation Link
RUN-2646Memory leak serializing DateTime to JSON (introduced 2020.5)
New FeatureDescription
RUN-2626Extend logger config format
RUN-2627Logging to channels
RUN-2649Validate pattern strings in logger configuration
ImprovementDescription
RUN-2644xuml Docker image: Oracle Instant Client 19.6 and runtime java 1.4.0
RUN-2650Improve help text of Runtime Command LinexUML Runtime Command Line Options
RUN-2652xuml Docker image: use debian:buster-slim

RUNTIME 2020.7 (09.04.2020)

BugDescriptionDocumentation Link
RUN-2631Startup not aborted if duplicated PS transition names are found.
RUN-2632Cannot select a Boolean using SQLite
RUN-2635Log may not be rotated if there's no log at current date/hour and log settings get adjusted
RUN-2639Infinite busy looping if client closes connection while service is still reading data from it
RUN-2640Cannot start container if repository already existent
RUN-2643Custom transaction log uses microseconds for "elapsed" field (introduced 2020.5)
New FeatureDescriptionDocumentation Link
RUN-2502CURLOPT_NOPROXY missing for URL adapterSetting cURL Options on the URL Adapter > Native cURL Options
ImprovementDescriptionDocumentation Link
RUN-2637Support <<DirectoryAlias>> for File System adapter "copy" action

RUNTIME 2020.6 (18.03.2020)

BugDescriptionDocumentation Link
RUN-2586URLAdapter doesn't send content when method is GET
RUN-2617Start log shows many "Closing connection" logs in last line
RUN-2622Calling LDAPS via URL adapter fails randomly
RUN-2629SQL Adapter: Incorrect computation of BLOB parameter bindings number
RUN-2630Hourly transaction log rotation does not work
ImprovementDescriptionDocumentation Link
RUN-2590Add support for HTTP/2.0 in HTTP based Adapters (URL/REST/etc)
RUN-2618Logging complex types as log details

RUNTIME 2020.5 (10.03.2020)

BugDescriptionDocumentation Link
RUN-2620Crash with intensive transaction logging
RUN-2624Cannot delete persistent state objects offline when using SQLite (introduced 2019.8)
RUN-2625Crash on shutdown when Debug log level is active (since 2019.13)

RUNTIME 2020.4 (28.02.2020)

Compatibility Hints

RUN-2599 corrects the behavior of custom constructors in case their parameters are function calls with dynamic parameters. There is a slight chance that existing models have a bug that has been masked by this issue and now the incorrect behavior may surface. 

BugDescriptionDocumentation Link
RUN-2426URL-Adapter - Error description not populated
RUN-2462Sorting condition cannot access context items
RUN-2599Custom constructor throws senseless errors if called with arguments referring function output
RUN-2603Out of memory sometimes not logged.
RUN-2610SFTP transfer can crash if log level = debug (introduced 5.1.43004)
RUN-2611URL adapter: static HTTP headers produce start-up error: Expected Request element, found "HeaderParameter".
RUN-2612HTTP Service leaks memory when using outputHeaderParameters (introduced 2019.3)
New FeatureDescriptionDocumentation Link
RUN-2608Action 'copy' in FileSystemAdapter
ImprovementDescriptionDocumentation Link
RUN-2403String.replace() should accept empty string
RUN-2607jsonToClass: support dateTime parsing of "/Date(80870400000+0000)/"

RUNTIME 2020.3 (11.02.2020)

BugDescriptionDocumentation Link
RUN-2602

Log rotation does not work (introduced 2019.13)


RUNTIME 2020.2 (27.01.2020)

Known Issues

The transaction logging is broken in this RUNTIME version. Final fix with 2020.3.

BugDescriptionDocumentation Link
RUN-2595Memory leak with URL Adapter when using dynamic addditionalHeaders, proxyType, or commands (since 2014.3)
ImprovementDescriptionDocumentation Link
RUN-2596REST Service: Respond with client error (HTTP 400) instead of server error (HTTP 500) if request body cannot be parsed

RUNTIME 2020.1 (16.01.2020)

Known Issues

The transaction logging is broken in this RUNTIME version. Final fix with 2020.3.

BugDescriptionDocumentation Link
RUN-2591Transaction log level always set to "NONE" (introduced 2019.13)
RUN-2594Crash on PS "reset" RPC Control Port action
New FeatureDescriptionDocumentation Link
RUN-2564xUML Runtime API: change log levelxUML Runtime API Reference
ImprovementDescriptionDocumentation Link
RUN-2592Command line option for license filexUML Runtime Command Line Options

Release Notes of the xUML RUNTIME 2019

RUNTIME 2019.13 (31.12.2019)

Known Issues

The transaction logging is broken in this RUNTIME version. Final fix with 2020.3.

BugDescriptionDocumentation Link
RUN-2583SOAP/REST/HTTP service connections fail
New FeatureDescriptionDocumentation Link
RUN-2534Scalable and configurable logging

RUNTIME 2019.12 (06.12.2019)

BugDescriptionDocumentation Link
RUN-2585Crash in SQLAdapter::getHandle if database connection fails (introduced 2018.3)

RUNTIME 2019.11 (14.11.2019)

BugDescriptionDocumentation Link
RUN-2571XML Parser: Not all entities downloaded with curl

RUNTIME 2019.10 (25.10.2019)

BugDescriptionDocumentation Link
RUN-2542Log fatal errors in bridgeserver.log
RUN-2558Startup crash if SOAP Server has invalid PortNumber element
RUN-2565Service with pstate does not start: [PSADLM][43][Detected objects for which no metadata exist in the repository...]
RUN-2566List of pstate classes has duplicate entries
ImprovementDescriptionDocumentation Link
RUN-2557Automatic migration of <<External>> PS Attributes

RUNTIME 2019.9 (08.10.2019)

BugDescriptionDocumentation Link
RUN-2553Persistent State Engine generates duplicated OBJECT_ID
RUN-2556e2e:type not rendered as part of REST body
New FeatureDescriptionDocumentation Link
RUN-2555Make it possible to use proxy when retrieving online XSDs and DTDs

RUNTIME 2019.8 (24.09.2019)

BugDescriptionDocumentation Link
RUN-2525Startup crash if HTTP Server has empty PortNumber element
RUN-2535xmlToClass: external schemas not looked for in ${INSTANCES_HOME}/resource
RUN-2536xmldsig-core-schema.xsd cannot be retrieved by the xml parser, runtime hangs
RUN-2539Inspection List Settings For Asynchronous Traces of PState Classes Are Not Saved Anymore
New FeatureDescriptionDocumentation Link
RUN-2430External persistence for selected properties of PState classes
ImprovementDescriptionDocumentation Link
RUN-2416Don't raise exception when native XML parser raises a warning
RUN-2458Propagate Transaction ID and Correlation ID in REST/HTTP communications (as with SOAP)
RUN-2532Increase log severity for PSLM log entries
RUN-2546HTTP header X-Sender-Host and X-Sender-ServiceHTTP Protocol Support

RUNTIME 2019.7 (01.07.2019)

BugDescriptionDocumentation Link
RUN-2522Persistent State modifying commands do not work if runtime is stopped (SQL Server only)

RUNTIME 2019.6 (19.06.2019)

BugDescriptionDocumentation Link
RUN-2520Persistent State objects lost due to ownership change

RUNTIME 2019.5 (05.06.2019)

BugDescriptionDocumentation Link
RUN-2493Runtime tries to start trace port for each tab file
RUN-2496ZIP Adapter generates invalid zip for big data
RUN-2499Memory leak 10-20 bytes per REST service call (introduced 2018.5)
RUN-2505getServiceContextValue("tcpip","remoteHostname" or "localHostname") return null and are very slow
RUN-2507Two services with same control port will start (introduced 2018.12)
RUN-2510classToJSON(): unescaped double quotes in generated e2e:type attribute values
RUN-2511URL adapter should always return httpStatus and httpHeaderParameters even with stream
RUN-2513HTTP Service with basic auth returns 403 on success (introduced 2019.3)
New FeatureDescriptionDocumentation Link
RUN-2484Query alias values at runtimeAlias Reader
RUN-2485Utility function to parse and build URLs

RUNTIME 2019.4 (15.04.2019)

BugDescriptionDocumentation Link
RUN-2479User Interface: IE11: SwaggerUI Button rendering
RUN-2490Memory corruption if component name is long
RUN-2492Persistent state: search handles IO_EXIT is wrong
New FeatureDescriptionDocumentation Link
RUN-2442REST interface for persistent state control port actionsxUML Runtime API
RUN-2463Do not serialize DataItem attributes marked by the compilerAttribute Specification > Visibility
ImprovementDescriptionDocumentation Link
RUN-2404User Interface: Respect browser language for custom UI data tables
RUN-2423Reduce severity of reporting missing startup / shutdown activities.
RUN-2480Update libssh2 to 1.8.2
RUN-2481Update OpenSSL to 1.1.1b
RUN-2482Update OpenLDAP to 2.4.47
RUN-2483Update curl to 7.64.1
RUN-2491Update MIT Kerberos to 1.17

RUNTIME 2019.3 (01.03.2019)

BugDescriptionDokumentation Link
RUN-2466Can not stop xUML service with Console <=6.0.58.1 and Builder (introduced 2018.12)
RUN-2468JSON Parser crashes on unbalanced object/array end
RUN-2470REST Service: empty body causes creation of body parameter with wrong metadata
RUN-2472Log level change not fully applied to SOAP and HTTP service (introduced 2016.1)

RUNTIME 2019.2 (08.02.2019)

BugDescriptionDocumentation Link
RUN-2464Persistent State date filters do not work (introduced 2018.12)
RUN-2465Persistent State: Primary Key Search fails if the primary key is defined out of order (introduced 2018.12)
ImprovementDescriptionDocumentation Links
RUN-2459New persistent state algorithm: Favor Objects

RUNTIME 2019.1 (24.01.2019)

BugDescriptionDocumentation Link
RUN-2419Cannot cancel SOAP or REST adapter session (introduced 2018.3)
RUN-2450No bridgeserver.log on the first day of a year
RUN-2454Runtime handles "If-Modified-Since" header incorrectly
ImprovementDescriptionDocumentation Link
RUN-2418REST Header parameter should be ignored if not setImplementing REST Methods > Output: Header Parameter
RUN-2438Improved persistent state performance: deletion of PS objects
RUN-2440Remove 32-bit Windows and Linux platforms

Release Notes of the xUML RUNTIME 2018

Compatibility Hint

BugHint
RUN-2264

With this RUNTIME we removed support of BRIDGE version 4.1. Repositories that have been compiled with such versions will not start on BRIDGEs with Runtimes as of version 2018.11.

RUNTIME 2018.12 (10.12.2018)

BugDescriptionDocumentation Link
RUN-2287Bad interaction between SQL and PS add-ons leads to crash on shutdown
RUN-2422You can no longer query the sessions during shutdown (introduced 2018.11)
RUN-2432Values for 'self' missing from trace for PS transitions
New FeatureDescriptionDocumentation Link
RUN-2406Support blob with content-type as REST operation output.
ImprovementDescriptionDocumentation Link
RUN-2421Provide more information in exceptions (e.g. callstack) for errors regarding NULL comparisons

RUNTIME 2018.11 (24.09.2018)

ImprovementDescription
RUN-2409User Interface: Updated REST test tool (Swagger UI 3.18.3)
RUN-2264Remove support for 4.1 repositories: Do not start if repository uses old formats

RUNTIME 2018.10 (21.08.2018)

Compatibility Hint

BugHint

RUN-2281
RUN-2383
RUN-2407

RUN-1964
RUN-2388
RUN-2408

With this RUNTIME we finally decided to activate the error log in case of comparison with NULL values (RUN-1964), or navigation to NULL references (RUN-2281) only if the modeler recompiles the service.

You can fix these model errors e.g. as follows:

  • local int = myNullObject.index if myNullObject.exists()
    Also do something in case int did not get initialized.
  • myNullString.exists() and aValidString > myNullString

ImprovementDescription
RUN-2407Conditional enable: exception or error in case of object navigation on null references
RUN-2408Conditional enable: error in case of conditions with null

RUNTIME 2018.9 (16.08.2018)

BugDescription
RUN-2402Service does not start: No connection manager "SQL_QUERY" is registered (introduced 2018.4)
ImprovementDescription
RUN-2404User Interface: Respect browser language for custom UI data tables

RUNTIME 2018.8 (02.08.2018)

BugDescription
RUN-2398xUML service may hang shutting down if the license is invalid/missing
ImprovementDescription
RUN-2376Change case sensitive license check for short machine name
RUN-2397SAP connection per xUML session

RUNTIME 2018.7 (2018/07/05

Compatibility Hint

BugHint
RUN-1964
RUN-2388

In RUNTIME 2018.1, we fixed bug RUN-1964 concerning comparison with NULL values. With RUN-2388, we decided to not throw an exception in this case, but to log an error to the bridgeserver log. That way, all services will still run, but the error will come to notice nevertheless.

BugDescription
RUN-2388Behavior for condition has changed

RUNTIME 2018.6 (01.06.2018)

Compatibility Hint

BugHint
RUN-2281
RUN-2383

In RUNTIME 2018.4, we fixed bug RUN-2281 concerning navigation to NULL references. With RUN-2383, we decided to not throw an exception in this case, but to log an error to the bridgeserver log. That way, all services will still run, but the error will come to notice nevertheless.

ImprovementDescription
RUN-2383Runtime logs error in case of object navigation on NULL values

RUNTIME 2018.5 (24.05.2018)

BugDescription
RUN-2226Not all properties properly set on the event object in `onUnhandledSignal`
RUN-2382Runtime prefers JSON regardless what is specified in Accept header
New FeatureDescription
RUN-1955Support for Transfer-Encoding: chunked
RUN-2378Support IPv6 for REST, HTTP and SOAP service
RUN-2380Support providing DB library paths via configuration file or command line

RUNTIME 2018.4 (24.04.2018)

Compatibility Hint

BugHint
RUN-2281

With RUN-2281, we fixed a bug concerning navigating to references that are actually NULL. As of this RUNTIME, an exception will be thrown in cases like local int = myNullObject.index.

BugDescription
RUN-2179Error during startup but service is running: [Fatal][External][PSADLM][15][Command ... is declared twice.]
RUN-2281Runtime allows object navigation on NULL Ref
RUN-2355Crash on shutdown with SQLServer PS database (introduced 2018.2)
RUN-2356Custom transaction handling (ROLLBACK) does not work on SQL Server
RUN-2358Crash if accepting socket cannot be created (since 2017.8)
RUN-2359REST path-parameters are not URL-decoded
RUN-2361JSON Composer does not escape control characters (0x00-0x1F) properly
New FeatureDescription
RUN-2188Access to transaction isolation level via SQLAPI / SQL Alias
RUN-2367REST Adapter does not support media type parameters
RUN-2368Composing compact JSON
RUN-2375Support setting root name and namespace dynamically for `classToXML`
ImprovementDescription
RUN-2191Log errors in case of internal persistent state errors.
RUN-2205Improve the SQL error descriptions with detailed SQL Statement
RUN-2325User Interface: Update ui theme e2e
RUN-2335Log needed xUML Runtime version if a feature is missing
RUN-2370REST: Better behaviour if a response contains data when it shouldn't

RUNTIME 2018.3 (22.02.2018)

BugDescription
RUN-2323Persistent state engine stops working without error
ImprovementDescription
RUN-2147Cancel SQL adapter requests

RUNTIME 2018.2 (14.02.2018)

Compatibility Hints

BugHint
RUN-2144

With RUNTIME 2018.2, we fixed a serious bug (RUN-2144) that led to a session commit although an exception had occurred and the session should have been rolled back. If an exception occurred in an action that was followed directly by a decision node, the exception was logged and the activity was aborted, but the xUML RUNTIME assumed nevertheless that execution has been fine and committed the session.
That resulted in SQL, persistent state, JMS and POP3 changes being committed instead of rolled back in case of error. Additionally, no error handlers have been invoked either. Please read Bug: Session Commit on Exception for a more detailed explanation.
RUNTIME 2018.2 is a recommended update, because this bug can lead to inconsistent data.

RUN-1964

With RUN-1964, we fixed a bug concerning comparison with NULL values. As of RUNTIME 2018.1, NULL values can only be compared for equality and inequality. All other comparisons like e.g. aValidString > NULL are rejected and an exception will be thrown.

BugDescription
RUN-1964Comparison operators do not work correctly with NULL values.
RUN-2133Type DateTime is not supported for castValue()
RUN-2144Exception during iteration is ignored if it is followed by a decision (see also compatibility hint above)
RUN-2172Error LCELM 36 license key has expired on
RUN-2310Decision node after an adapter / call node inhibits automatic error propagation and rollback mechanism (see also compatibility hint above)
RUN-2320Data race during unique name creation
RUN-2328SQL adapter no rollback after exception (see also compatibility hint above)
RUN-2333Wrong behaviour of FileSystemAdapter action rename if new name is missing
RUN-2334Cannot create new PS Schema on MySQL
RUN-2341jsonToClass(): does not convert integers to floats in arrays of floats
New FeatureDescription
RUN-2296Allow static path but dynamic file for File System adapter and Flat File adapter
ImprovementDescription
RUN-2286parseDateTimeExpression throws exception on non-matching strings (if compiled with Builder 7.0.0-beta2 or newer)
RUN-2295Run regression tests with memory leak check (linux64dev)
RUN-2314Allow overriding timestamp when logging custom TRX entries
RUN-2317Add system ip address to serviceContextValues
RUN-2325User Interface: Update ui theme e2e

Release Notes of the xUML RUNTIME 2017

RUNTIME 2017.10 (07.12.2017)

ImprovementDescription
RUN-2316JSON ComposerOptions for REST service and adapter

RUNTIME 2017.9 (17.11.2017)

BugDescription
RUN-2288Java-Adapter logs exceptions on shutdown
RUN-2292Service crashes due to incorrect OpenSSL initialization
RUN-2300HTTP body Blob shouldn't be NUL-Terminated
RUN-2304REST Adapter crashes if response body begins with a NULL byte

RUNTIME 2017.8 (28.09.2017)

BugDescription
RUN-2230Persistent State Adapters: actions have no trx log entries
RUN-2265SOAP calls are getting slow with increasing load if service connection limit is exceeded
RUN-2282Crash on intensiv usage of SSL protocols
RUN-2283Transaction log level of REST Adapter should be IO_EXTERNAL
ImprovementDescription
RUN-2263Remove support for 4.1 repositories: Print error if repository uses old formats
RUN-2284No longer support "Tracing and Mockups Enabled" changes during runtime

RUNTIME 2017.7 (14.09.2017)

Compatibility Hint

As of RUNTIME 2017.7, we had to introduce an implicit dependency to the Windows Universal Runtime.

To run services on Windows systems prior to Windows 10 (Windows 7, 8, 8.1, 2008 Server, 2012 Server) an up-to-date system is required. In particular the KB2999226 update must be installed.
See also Update for Universal C Runtime in Windows on the Microsoft Support pages.

If this update is not installed, some DLLs are missing and xUML services will not start (not reporting any error). The bridgeserver log will be empty. If you try to start the services manually via start.bat (as described on Troubleshooting > E2E xUML Service Startup Fails), you will get

BugDescription
RUN-2267Potential crash if optional repository file is missing
RUN-2279Memory leak if item retrieved from memory does not match expected metadata
RUN-2280Crash if deadlock occurs during SearchHandles
ImprovementDescription
RUN-2009Update Windows Compiler to VC2017
RUN-2192Update SQLite to 3.20
RUN-2250Drop support for RedHat/CentOS 5
RUN-2268Update ICU to 59.1
RUN-2269Update Xerces to 3.2.0
RUN-2270Update SQLAPI to 4.1.11
RUN-2273Update zlib to 1.2.11
RUN-2274Replace Heimdal with MIT Kerberos
RUN-2275Update OpenLDAP to 2.4.45
RUN-2276Update OpenSSL to 1.0.2l
RUN-2277Update curl to 7.55.1

RUNTIME 2017.6 (21.08.2017)

Compatibility Hint

BugHint
RUN-2259

With this RUNTIME, we tidied up the system error codes of error domain FUTSM and reduced the error codes to 4 (from more than 20). If you are catching one of the dropped error codes in your model, you need to adapt the code. See System Errors for more information and a mapping of error codes old → new.

BugDescription
RUN-2244Wrong duration result in DateTime.difference()
RUN-2248JSON parser silently ignores number parsing errors
RUN-2256SQL Error Messages - Duplicate error code 35
RUN-2257Textual error in error message FUMSM_CAST_INTEGER_WRONG_STATIC_TYPE
RUN-2258Typo in log error message
ImprovementDescription
RUN-2224Throw exception if trying to retrieve value of wrong type from the memory adapter
RUN-2246Give more details about file system adapter error FSADSM 22
RUN-2249Remove Solaris-x86 support
RUN-2255Helgrind: DB processed statements
RUN-2259Unused error codes
RUN-2266Remove broken conversion functions

RUNTIME 2017.5 (06.07.2017)

REST compatibility hints

REST services or adapters compiled with a BUILDER previous to 6.0.22 will not start on a BRIDGE with RUNTIME 2017.5. Please recompile your services in this case.
BugDescription
RUN-2148REST AdapterResponse not set in case of non-HTTP errors
RUN-2187PState adapter raises deadlocks on MS SQL Server in load balancing scenario
RUN-2223REST Adapter populates default response object even in error cases with defined ResponseDefinition
RUN-2227Bidirectional object references lead to service crash
RUN-2231REST Adapter may cause service crashes if used as the only URL-accessing adapter
New FeatureDescription
RUN-2213REST Adapter: Support segment composition
RUN-2219REST: Respect 'ignoreHTTPErrors' flag from the alias
RUN-2222REST: Allow setting external names for header and query parameters
RUN-2225REST: support for response headers in method signatures
ImprovementDescription
RUN-2182Java Service: call all lifecycle hooks at appropriate moments

RUNTIME 2017.3 (24.05.2017)

BugDescription
RUN-2158MIME header decoding of multi line Q-encoded string
RUN-2195Service crashes on startup when DB-connection "Options" is empty.
RUN-2197Relative REST path is not set properly
RUN-2198Rest Service does not provide error message into error object
RUN-2199Crash when listing PS classes in offline mode
RUN-2200SOAP with attachment start header is wrong
RUN-2201Float number formatting can't shift more than 10^9
RUN-2202REST Adapter calculates Content-Length with ominous NUL byte
RUN-2206Check for required symbols and fail gracefully
RUN-2207Service crashes while using MIME Adapter
RUN-2212Runtime crashes on SOAP 1.2 fault
RUN-2216Runtime crash: SQL adapter but no Map usage and compiled with Builder before 6.0.18.1
RUN-2217REST call returns HTTP 400 when Query URL ends with '&'

RUNTIME 2017.2 (30.03.2017)

Windows Vista not supported anymore

Starting from this RUNTIME version, Windows Vista is not supported anymore.
Please find the list of all supported operating systems on BRIDGE Installation Guide.
BugDescription
RUN-2183Error 401: Unauthorized - Navision SOAP access with domain user
RUN-2184Not able to access AdapterResponse object of the REST adapter if an exception is thrown because of HTTP Code >= 400
RUN-2185REST-Adapter works slow on Windows-Environment
RUN-2186REST call logs ERROR in transaction log although there was no error
RUN-2190SAP: Empty field of TIMS type is no longer equivalent to 000000

RUNTIME 2017.1 (07.02.2017)

BugDescription
RUN-1920Persistent State: Signal conversation hangs in SafeConnect while handling tRFC protocol
RUN-2152Persistent State: event is not delivered
RUN-2153Persistent State: errors during commit phase remain unhandled
RUN-2161REST Adapter: crashes on unhandled HTTP response code
RUN-2170Persistent State: Objects are not visible anymore when service is stopped
RUN-2176REST Service: Solaris 10: crash if funny HTTP code set for response
RUN-2177Windows: crash on startup when using "Follow Redirects" on URL Alias
RUN-2178URL Adapter: Follow redirects is interpreted as HEX
ImprovementDescription
RUN-1995Persistent State: Speed up persistent state engine performance
RUN-1999Persistent State: Option for safe or fast database access using SQLite
RUN-2024Service will not start if it finds persistent state objects which have no class definition
RUN-2100Persistent State: Replace 'IMAGE' with 'VARBINARY(MAX)' in SQL Server's Persistent State schema.
RUN-2160Persistent State: Block changes to Persistent State primary keys.
RUN-2163Persistent State: Remove legacy MaxDeliveryTrials for signals
RUN-2173REST Adapter sets Content-Lenght=0 for PUT/POST/PATCH without body

Release Notes of the xUML RUNTIME 2016

RUNTIME 2016.9 (16.11.2016)

BugDescription
RUN-1992URL Adapter Session to a SFTP Server hangs
ImprovementDescription
RUN-2122Update libcurl 7.51.0
RUN-2123Update libssh2 1.8.0
RUN-2124Update OpenLDAP 2.4.44
RUN-2125Update OpenSSL 1.0.2
RUN-2151REST Service: rename Response.statusCode to httpStatus

RUNTIME 2016.7 (04.11.2016)

BugDescription
RUN-2136Parsing of SOAP-Fault for SOAP 1.2 not properly implemented
RUN-2142User Interface: Order on REST tags not respected

RUNTIME 2016.6 (06.10.2016)

BugDescription
RUN-2066Prevent XML Entity Injection Denial of Service
RUN-2108Controller Service leaks memory on each request
RUN-2110If array of values for cURL 'list' option contains NULL, the option will be set incorrectly
RUN-2117Missing transaction log for "is alive" check on DB connection (since 2013.4)
RUN-2119SQL adapter: memory leak
RUN-2129Crash if 'options' parameter of XMLtoClass is null
RUN-2132SOAP request fails due wrong generated XMLAttribute
RUN-2134SOAP Headers are not escaped correctly
ImprovementDescription
RUN-2130User Interface: New E2E Logo
New FeatureDescription
RUN-2068REST adapter
RUN-2099Support multiple different responses for a REST service
RUN-2115Support placeholders in SQL statements

RUNTIME 2016.5 (12.07.2016)

BugDescription
RUN-2090classToXML() generates empty out if first element of an array is empty
RUN-2092SQLAdapter returns 1900-01-01 instead of actual value
RUN-2103SAP Message Composer crashes if complex array contains nulls
RUN-2105REST response and code ignored in case of authorization error
ImprovementDescription
RUN-2097Display service name for REST API

RUNTIME 2016.4 (15.06.2016)

BugDescription
RUN-1952Service crashes when deleting object from orphaned persistent state class
RUN-2029Base64 Blob To JSON contains Linebreaks
RUN-2033fetchNext sql adapter call crashes, if a commit was called since getHandle
RUN-2049Misleading Error when client does not send SOAPAction in HTTP Header
RUN-2057REST Service: Changes in log level not always picked up
RUN-2069Unable to start service: failed to read and parse castValue.tab
ImprovementDescription
RUN-2053User Interface: Swagger: XML input template
RUN-2077Add timestamp to Errors
RUN-2083User Interface: REST Service: support for authentication in REST descriptor

RUNTIME 2016.3 (08.04.2016)

BugDescription
RUN-2045SQL Adapter is leaking memory with stored procedure output.
RUN-2047Using Swagger UI: RESTADLM:9 warnings
RUN-2048Mistake in error description FUSSM 5
RUN-2052SOAP RPC Service: wrong "xsd:Unknown" type
RUN-2060SAPNW: Crash in IDocRecordComposer (introduced 2015.5)
ImprovementDescription
RUN-2050User Interface: Remove validation from REST documentation
RUN-2058REST Service: XML response without extra <result> element
New FeatureDescription
RUN-2043Option to enable/disable delimiter for empty values in EDIFACT

RUNTIME 2016.2 (08.03.2016)

BugDescription
RUN-1930In some cases setting cURL options wrongly results in misleading error message
RUN-1931CURLAUTH_NEGOTIATE is not implemented
RUN-1932CURLOPT_HTTPAUTH should be a bitfield, not constant
RUN-1976Cannot start service with SAP NW (missing msvcr80.dll)
RUN-1993SAPNW: Allow to specify default connection pool size
RUN-2002Huge ambigious callstack
RUN-2016Error calling MTOM/XOP service with URL encoded href
RUN-2017FileSystemAdapter status return size 0 but there are data
RUN-2018Parse error if MTOM message does not end with new line
RUN-2030 Fix directory traversal attack vulnerability
ImprovementDescription
RUN-1991SAPNW: Bridge is RFC server: support parallel connections
New FeatureDescription
RUN-1961REST Service
RUN-2021REST Service: Test client (swagger)

RUNTIME 2016.1 (12.01.2016)

BugDescription
RUN-1979SAPNW: Cannot start SAP service if no SAP connection in component diagram is defined
RUN-1981Service crash upon triggering persistent state transition from Console
RUN-1985SAPNW: SAP adapter is slow if pool size is to small
RUN-1987SAPNW: SAP connection is not always closed
RUN-2003SAPNW: Use same SAP pool for identical connection string
ImprovementDescription
RUN-1984SAPNW: Make unrecognised value of SAP FieldPadding a warning instead of error
RUN-1986SAPNW: SAP RFC adapter write into transaction log if pool is exhausted

Release Notes of the xUML RUNTIME 2015

RUNTIME 2015.18 (30.11.2015)

BugDescription
RUN-1971RUNTIME creates PS DB object field as 65kbyte "BLOB" type in MySQL
RUN-1973Service crashes if persistent state database connection is lost (introduced 6.0.92.0)
RUN-1977Displaying persistent state owners: Unknown column 'OBJ.OBJECT_ID' in 'field list'
ImprovementDescription
RUN-1978Upgrade SAP NWRFCSDK to 7.20.38

RUNTIME 2015.17 (10.11.2015)

BugDescription
RUN-1970SOAP message parsing does not handle default namespaces correctly

RUNTIME 2015.16 (04.11.2015)

BugDescription
RUN-1967Stored procedure's INOUT parameters are not returned
ImprovementDescription
RUN-1962SOAP/XML adapter: generate CDATA elements

RUNTIME 2015.15 (16.10.2015)

BugDescription
RUN-1956Can't call stored procedure through ODBC
ImprovementDescription
RUN-1951support result set as return type of stored procedures
New FeatureDescription
RUN-1957Support Unicode and non-Unicode modes for SQL Adapter

RUNTIME 2015.14 (21.09.2015)

BugDescription
RUN-1927Use WINSSPI instead of Heimdal for Windows cURL builds.
ImprovementDescription
RUN-1941Update OpenSSL 1.0.2d
RUN-1947Update libSSH2 to 1.6.0
RUN-1948Update cURL to 7.44.0

RUNTIME 2015.13 (03.09.2015)

Bug
Description
RUN-1943jsonToClass() not working with arrays at top level

RUNTIME 2015.12 (31.08.2015)

Bug
Description
RUN-1925Correct trace details for 'select distinct'

RUNTIME 2015.11 (13.07.2015)

BugDescription
RUN-1922Put hashmap to memory and get value at the same time blocks process
ImprovementDescription
RUN-1923SQLite 3.7.16.2
RUN-1924SQLAPI 4.1.4

RUNTIME 2015.10 (30.06.20115)

BugDescription
RUN-1918Service doesn't start if persistent state database (MySQL) is empty (introduced 2014.1)
RUN-1919After some time no new SAP Connections are made

RUNTIME 2015.9 (26.06.2015)

BugDescription
RUN-1876SAPNW: Service crash if you debug on SAP side
ImprovementDescription
RUN-1911Upgrade OpenSSL to latest 1.0.0 version
RUN-1914SAPNW: Update SAP libraries to patchlevel 35
RUN-1916SAPNW: RFC connections are not limited to 10 per service

RUNTIME 2015.8 (17.06.2015)

BugDescription
RUN-1913SOAP service: empty HTTP headers are reported as error (introduced 2015.3)
ImprovementDescription
RUN-1908Update SQLAPI to version 4.1.5
RUN-1909Upgrade SQLite to 3.8.10.2

RUNTIME 2015.7 (27.05.2015)

BugDescription
RUN-1819FileAdapter: readLine: if a line is very long, RUNTIME can crash
RUN-1901Service stopped unscheduled - SQL Adapter
RUN-1904Error Text for SSPSM 37 not helpful
New FeatureDescription
RUN-1860Trace the expression of the Distinct and GroupBy statements
RUN-1887extend Control Port Command for Trace Deletion

RUNTIME 2015.6 (29.04.2015)

BugDescription
RUN-1862RUNTIME crashes if input and output of iterator node are the same Array
RUN-1892SEARCH HANDLES": 102 42000 Incorrect syntax near 'LIMIT'
ImprovementDescription
RUN-1888New SOAP request for deleting multiple pstate objects
RUN-1897Update SAP nwrfcsdk 7.20.33

RUNTIME 2015.5 (16.04.2015)

BugDescription
RUN-1894Memory map is missing after removing an single element
RUN-1895TransactionID is empty in trace (introduced 2015.3)

RUNTIME 2015.4 (09.04.2015)

BugDescription
RUN-1886Maps nested in parent structure are not copied correctly when parent is copied
RUN-1889JSON Composer's "keepNulls" not applied to nested structures
RUN-1893User Interface: UI: Get JS error, when datetime picker value is empty
ImprovementDescription
RUN-1882Flat File compose: improve performance for zero values

RUNTIME 2015.3 (20.03.2015)

BugDescription
RUN-1858SOAP adapter (doc-encoding) with many parameters creates wrong request
RUN-1862RUNTIME crashes if input and output of iterator node are the same Array
RUN-1865Service crashes upon deleting a mail without subject (POP3 adapter action commit)
RUN-1868RegTest: FlatFile/EdifactOrderRT/Invoice has a problem with pins
RUN-1880Remove null values from JSON composer output
RUN-1881SAP System Errors make funny-looking error messages in logs
ImprovementDescription
RUN-1795JSON composer can write null values
RUN-1873Update openssl to 1.0.0l on linux-64 and solaris-x86
New FeatureDescription
RUN-1877Flat File Parser: add posibility to supress empty strings when parsing

RUNTIME 2015.2 (18.02.2015)

BugDescription
RUN-1771Cannot mock-up memory adapter
RUN-1844Mocked values are being written to trace even though they are not used.
RUN-1851js adapter is not correctly initialized in Persistent State Usage
RUN-1853XML date is changed or not parsed correctly during persistent state processing
RUN-1855RFC Adapter (IDOC_INBOUND_ASYNCHRONOUS) does not throw error when IDOC is inconsistent and SAP refuses it
ImprovementDescription
RUN-1800classToXml is always using "utf-8" in xml header, even if other encodings are required/used
RUN-1843Optimize memory consumption for xmlToClass and SOAP parsing
RUN-1857Security vulnerability: Disable external entities in SOAP service requests

RUNTIME 2015.1 (06.01.2015)

BugDescription
RUN-1822can not handle negative values in function convertTimeTicksToDateTime
RUN-1839classToJSON must not escape forward slash (solidus)
ImprovementDescription
RUN-1838Return HTTP Headers and status code for SOAP adapter

Release Notes of the xUML RUNTIME 2014

RUNTIME 2014.19 (12.12.2014)

BugDescription
RUN-1826getObjectHandles on Oracle and SQLServer DB fails
New FeatureDescription
RUN-1762User Interface: DateTime picker

RUNTIME 2014.18 (10.11.2014)

BugDescription
RUN-1804 Missing data if reading TEXT fields from SQL Server using ODBC
ImprovementDescription
RUN-1813Update ca-bundle.crt
New FeatureDescription
RUN-1515Respond with SOAP 1.2 from services
RUN-1794SendSignal via Console (RUNTIME part)
RUN-1799Report PState control port actions in transaction log

RUNTIME 2014.17 (2014.10.13)

BugDescription
RUN-1782Crash if license file missing or not a valid XML
RUN-1793SOAP 1.2 Array handling
RUN-1801XML validation does not work
New FeatureDescription
RUN-1741Support Kerberos via cURL

RUNTIME 2014.16 (2014.09.05)

Windows XP not supported anymore

Starting from this RUNTIME version, Windows XP is not supported anymore. xUML services will not start-up on XP platforms due to technical implications.
Please find the list of all supported operating systems on BRIDGE Installation Guide.
BugDescription
RUN-1783Can not start service on Solaris 10 (stpcpy: referenced symbol not found)

RUNTIME 2014.15 (2014.08.22)

BugDescription
RUN-1754Cannot set the status code in the postprocessor
RUN-1764Support configurable prefix/namespace for SOAP encoding attribute.
RUN-1765BuildMap throws exception on parameter array of HTTP Parameter
RUN-1766SAP-NW: improve compatibility: float
RUN-1767SAP-NW: improve compatibility: no padding with nested structures
RUN-1770SAP-NW: improve compatibility: empty EDI_DC40
RUN-1778SQL adapter: error SQLSM/9 should not be fatal
RUN-1780User Interface: Don't use any alert but console logs
ImprovementDescription
RUN-1772Memory Adapter needs pretty long to store / retrieve Map object
New FeatureDescription
RUN-1762User Interface: DateTime picker
RUN-1777SAP-NW: padding of RFC data can be disabled

RUNTIME 2014.14 (17.07.2014)

BugDescription
RUN-1750Fatal error executing timeout function "0.4"
RUN-1761Unreadable characters on SOAP_EXIT line in transaction log (introduced 2014.10)

RUNTIME 2014.13 (14.07.2014)

BugDescription
RUN-1759memory leak: select first|last from array with empty result

RUNTIME 2014.12 (09.07.2014)

BugDescription
RUN-1751Cannot create hash map from an array with Group elements
RUN-1755xmlToClass fails if duration has microseconds
RUN-1758User Interface: Fileupload doesn't work on Firefox
ImprovementDescription
RUN-1748Support SOAP 1.2 action attributes
RUN-1753Write HTTP service input and output

RUNTIME 2014.11 (26.05.2014)

BugDescription
RUN-1742SAP-NW firmware must preserve padding spaces
RUN-1743SAP-NW: SAPIdocRecordParser must support empty segments

RUNTIME 2014.10 (12.05.2014)

BugDescription
RUN-1718Transaction log shows wrong URL for SOAP request when url is defined dynamically and statically
RUN-1729RUNTIME crashes at shutdown with SAPNW Service
RUN-1731Windows: Details for network errors are wrong
RUN-1736unable to remove zip file previously opened with the zip adapter

RUNTIME 2014.9 (24.04.2014)

FeatureDescription
RUN-1722

IDoc composer/parser should support the DC40 and DD40 classes

RUNTIME 2014.8 (10.04.2014)

BugDescription
RUN-1723Memory leak if using constructors

RUNTIME 2014.7 (02.04.2014)

BugDescription
RUN-1721SOAP adapter using https fails with errno 131 (server is IIS)
New FeatureDescription
RUN-1515Respond with SOAP 1.2 from services
RUN-1721SOAP and URL adapter: new option CURLOPT_SSL_OPTIONS=CURLSSLOPT_ALLOW_BEAST

RUNTIME 2014.6 (13.03.2014)

BugDescription
RUN-1706PS getObjectHandles results in a invalid SQL when using tagged value 'Max Results'
RUN-1715Cannot access map elements of memory-map
RUN-1716SOAP parser does not work in case of array, href and RPC encoding (introduced 5.1.85.2)

RUNTIME 2014.4 (2014/02/27

Bug
Description
RUN-1699Can not get response from URL adapter after caught exception
RUN-1707Missing files in asynchronous trace
RUN-1708SOAP adapter crashes on HTTP status 500

RUNTIME 2014.3 (20.02.2014)

BugDescription
RUN-1655JavaScript: Crashes RUNTIME when setting unknown record field
RUN-1698Service dies parsing JSON date-time
RUN-1700JavaScript: Cannot assign JavaScript objects containing arrays to bridge items
RUN-1701JavaScript: Cannot assign non-numeric date to bridge DateTime
RUN-1702JavaScript: Bridge strings contain literal "null" or "undefined" when assigned null or not defined value
ImprovementDescription
RUN-1676URL adapter options: allow Boolean and Integer types as values as well
New FeatureDescription
RUN-1660Crypto: Support PKCS#8 key format

RUNTIME 2014.2 (10.02.2014)

BugDescription
RUN-1348Error message upon http call: favicon.ico not found
RUN-1669Solaris: sftp login fails: Failure establishing ssh session
RUN-1670Persistent state getObjectCopy returns empty object (no data)
RUN-1696Header character encoding not taken into account for MIME converter

RUNTIME 2014.1 (23.01.2014)

BugDescription
RUN-1242cannot rollback - no transaction is active
RUN-1667With log level Debug, SOAP request and response is not written in chronological order
RUN-1674PState upgrade to version 15 fails on MySQL
RUN-1682Deadlock if you get the error "Did not find authorization data (db username/password) in repository for database"

Release Notes of the xUML RUNTIME 2013

RUNTIME 2013.5 (15.11.2013)

Incompatible Persistent State Database Schema

With this RUNTIME version, the persistent state database schema changed to version 15. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.
If you have many persistent state objects, the schema update might take several minutes.
BugDescription
RUN-1661Persistent state sqlite error "database busy" during service shutdown
RUN-1662Crash if query persistent state object with filter value <
RUN-1664Several PS objects with the same ID are created if parallel scheduler work on the same file
RUN-1665Persistent state getObjectHandle returns wrong object

RUNTIME 2013.4 (01.11.2013)

BugDescription
RUN-1651RUNTIME error when using StoredProc that returns Boolean
RUN-1652getObjectHandles ignores stateCondition
RUN-1658SQL adapter SQLAPI options did not work (introduced 5.1.82.0)

RUNTIME 2013.3 (22.10.2013)

BugDescription
RUN-1627SOAP Service returns only year in DateTime field, results in Error
RUN-1636Memory leak on Solaris
RUN-1642Memory leaks if storing maps in memory adapter (introduced 2013.1)
RUN-1643File system adapter removes directory recursively (introduced 2013.1)
ImprovementDescription
RUN-1638JSON: support arrays as root elements
RUN-1639URL adapter: support PATCH HTTP method

RUNTIME 2013.2 (18.09.2013)

BugDescription
RUN-1620Interactive debugger: stop at the final activity node
RUN-1630Parsing SOAP requests does not work if namespace prefixes are not unique
RUN-1634The transliteration functions removeAccents() and toASCII() seem to be confused
New FeatureDescription
RUN-1631Basic REST support for <<HTTPPort>> operations

RUNTIME 2013.1 (05.09.2013)

Fix CrashDescription
RUN-1597Service crashes at RUNTIME if FlatFiles' record contains complex type where simple type is expected in Composer
BugDescription
RUN-1579Readline throws: Value is empty
RUN-1591Insert DateTime with microseconds into SQL Server fails
RUN-1607JSON parser does not understand Any type
RUN-1621Repositories with umlauts in path does not start
RUN-1624RUNTIME returns empty response if FlatFileComposer fails.
ImprovementDescription
RUN-1602Hash map should behave like any other class when used in the memory adapter
RUN-1609Improve performance of memory-stored HashMaps by providing direct access interface through memory adapter
RUN-1622Support authentication type 'None'
RUN-1626Support Map class in JavaScript
RUN-1629

jsonToClass(): Convert integer value to float if target field is of float type

New FeatureDescription
RUN-1603String method "transliterate"
RUN-1618Enable removal of folder, even when there are files in the folder

Release Notes of the xUML RUNTIME 6.0

RUNTIME 6.0.92.3 (31.07.2013)

BugDescription
RUN-1588Hash-Map Table not created out of JSON String
RUN-1604Error message during service startup in embedded server
RUN-1605Step over/into at end of service or transition does not proceed at next action
RUN-1606Service starts successfully but cannot be accessed
New FeatureDescription
RUN-1603String method "transliterate"

RUNTIME 6.0.92.2 (10.07.2013)

BugDescription
RUN-1583Hanging ps object and service crash due to huge asynchronous trace

RUNTIME 6.0.92.1 (05.07.2013)

BugDescription
RUN-1584Unexpected error: SOAP Error SOAPADSM 17 - UserName is empty, then server crash
ImprovementDescription
RUN-1587Hash-Map key should support all base types as key

RUNTIME 6.0.92.0 (26.06.2013)

Incompatible Persistent State Database Schema

With this RUNTIME version, the persistent state database schema changed to version 14. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.
BugDescription
RUN-1592Creating persistent state transition with absolute timeout greater 2038-12-31 fails (only MySQL)
RUN-1594Service crash calling parseLocalDateTimeExpression with empty string
RUN-1595Web Service cannot read binary file
ImprovementDescription
RUN-1568Resolve indexes to names in error messages.
RUN-1394Persistent State: Cluster Fail-over (reconnect retry)
RUN-1593Display persistent state objects which are in the initial state

RUNTIME 6.0.91.1 (06.06.2013)

New FeatureDescription
RUN-1582Support mySQL for persistent state
BugDescription

SQL adapter: MySQL: Support multiple SQL queries in one transaction

SQLAPI option "HandleResult" is set to "store".
Without the option, you will get the error: 2014 Commands out of sync; you can't run this command now.
More information on: http://sqlapi.com/ServerSpecific/MySQL.html

RUNTIME 6.0.91.0 (21.05.2013)

Asynchronous Trace DB schema

The RUNTIME upgrades the asynchronous trace database at first start. Although the new schema is fully backwards-compatible, we do not recommend switching back to an older RUNTIME and then back again to the new one. This might result in a corrupted database, that requires manual intervention to be fixed.
BugDescription
RUN-1577Type mismatch for testcase does not lead to error
RUN-1581Wrong order of persistent state transition in asynchronous trace
ImprovementDescription
RUN-1572Offer JavaScript adapter for Solaris

RUNTIME 6.0.90.1 (14.05.2013)

CrashDescription
RUN-1575Service containing JavaScript adapter crashes RUNTIME on shutdown

RUNTIME 6.0.90.0 (30.04.2013)

Incompatible Persistent State Database Schema

With this RUNTIME version, the persistent state database schema changed to version 13. The database content will be converted, once a service uses the new persistent state database.
You cannot go back to an older RUNTIME version after you have started a service. All composite services which use a shared persistent state database must upgrade the RUNTIME at the same time.
BugDescription
RUN-988 history state in a fork/join context does not work
ImprovementDescription
RUN-1567 FlatFile adapter: trace input or output file name
New FeatureDescription
RUN-1306Allow canceling a hanging SOAP/URL adapter call
RUN-1544Add request ID (session ID) to bridgeserver.log

RUNTIME 6.0.89.0 (29.04.2013)

BugDescription
RUN-1569 Incorrect file names in composed MIME messages (introduced 5.1.77.0)
BugHint
RUN-2407
RUN-2408

With this RUNTIME, we finally decided to activate the error log in case of comparison with NULL values only if the modeler recompiles the service.


Documentation Links

On this Page:

  • No labels