This page lists all the known issues in the different releases of OpenSplice RnR Manager.
There is also a list of fixed bugs and changes in the different versions of OpenSplice RnR manager.
Version 6.10.4
| Report ID. | Description |
|---|---|
| RNR-748 | Import and export : support multiple topics with field of same name with different types. If two topics have the same field name with different types, importing will fail with an exception. |
| RNR-740 | The storage import will crash if the number of unique topics in the storage file exceeds 200. StorageController.c topic caching causing seg faults when number of topics exceeds 200. |
| RNR-642 | Update tool's storage configuration maxFileSize parameter to use new symbols. (OSPL-7346) New data size symbols were introduced into the configuration processing for the RnR service . The configuration processing supports floating point values and the following units: b, B (bytes), KiB, kB, K, k(=1024 bytes), MiB, MB, M, m(=1024KiB), GiB, GB, G, g(=1024MiB), TiB, T, t(=1024GiB). Workaround: The new symbols are supported, the floating point values are not. |
| RNR-637 | Domain browser view - Federation, services, tree items are not cleaned up. If a remote federation is started up and shut down, the node, federation, and services tree items are left behind. This effect is additive with every time the remote federation is restarted, a new federation folder gets placed and left behind in the tree. Workaround: Disconnecting and connecting to the domain again clears up the browser. |
| RNR-636 | Service status view - the view gives inconsistent results when multiple services start up on different nodes. If a remote federation other than the one RnR Manager is connected to, is started up and is running an RnR service of its own, the service status view is sometimes not properly updated. This often results in the "RnR Service Id/Node" column not being populated, or multiple rows for the service appearing. Workaround: Disconnecting and connecting to the domain again clears up the service status view with valid data. |
| RNR-634 | Deadlock sometimes occurs when RnR Manager force disconnects on loss of communication to OSPL. When RnR Manager encounters an unexpected loss of communication with OSPL and goes through the disconnect routine to handle it, an intermittent situation can occur where the tool operation halts and is frozen in deadlock. Workaround: Kill the RnR Manager process, and start it up again. |
| RNR-632 | ospl-info.log warning output from rnrManager process on storage import of CDR storage file. In Linux, When importing a storage, the following info log gets generated and placed in RnRManager's process directory. ============================================================== Report : WARNING Date : Fri Nov 06 09:49:31 PST 2015 Description : Incorrect storage attributes specified: used XML when opening an CDR storage Node : ubuntu Process : rnrManager <2343> Thread : 492db70 Internals : V6.5.2/3193fc7/00268a2/rr_storageAttrFromXML/ rr_storageAttrXML.c/80/0/1446832171.241958793 Aside from the warning, the import completes successfully and no other issues with the storage or its contents are noted. |
| RNR-529 | Export storage - storage file does not get properly initialized if using relative path. If the full file path and name is not specified, two sets of storage files gets created in different directories. As of version 6.6.0, warnings are displayed in the wizard if the path is not absolute, or if the current domain connection is to a remote host. Workaround: Always specify the full file path for the file name parameter in the Export Storage wizard. |
| RNR-618 | Historical scenario commands are lost on disconnect/reconnect. If the user creates a scenario with some commands, they are meant to be published transiently. Functionally, this means that if the scenario editor for a given scenario is closed and then reopened, the previously published commands will appear in the commands table. However, if the user disconnects and reconnects to the domain, and then the scenario editor is brought up again, the scenario commands do not appear in the commands table, and the transient samples are lost. |
| RNR-538 | Storage import fails if storage samples contain greater than 999 fields. Due to a limitation in the SQLite engine (used to store imported storages in the tool workspace), it cannot handle inserting samples whose data type contains 999 fields or greater. |
| RNR-447 | Exception occurs when using Save As.. function in scenario editor. Any attempt to save a scenario file with a filepath that has a space, will throw an exception IF the installed jre is version 1.6. Workaround 1: Install Java JRE version 1.7. Workaround 2: Save scenario file to a filepath with no spaces. |
| RNR-254 | SELinux Install To install to SELinux, run the following commands in a terminal as root: $ /usr/sbin/setenforce 0 $ rnrManager install directory/install.sh $ /usr/sbin/setenforce 1 $ chcon -R -t textrel_shlib_t '/opt/ADLINK/VortexOpenSpliceRnRManager' |
| RNR-632 | ospl-info.log warning output from rnrManager process on storage import of CDR storage file. In Linux, When importing a storage, the following info log gets generated and placed in RnRManager's process directory. ============================================================== Report : WARNING Date : Fri Nov 06 09:49:31 PST 2015 Description : Incorrect storage attributes specified: used XML when opening an CDR storage Node : ubuntu Process : rnrManager <2343> Thread : 492db70 Internals : V6.5.2/3193fc7/00268a2/rr_storageAttrFromXML/ rr_storageAttrXML.c/80/0/1446832171.241958793 Workaround: Aside from the warning, the import completes successfully and no other issues with the storage or its contents are noted. |
Version 6.10.3
| Report ID. | Description |
|---|---|
| RNR-740 | The storage import will crash if the number of unique topics in the storage file exceeds 200. StorageController.c topic caching causing seg faults when number of topics exceeds 200. |
| RNR-642 | Update tool's storage configuration maxFileSize parameter to use new symbols. (OSPL-7346) New data size symbols were introduced into the configuration processing for the RnR service . The configuration processing supports floating point values and the following units: b, B (bytes), KiB, kB, K, k(=1024 bytes), MiB, MB, M, m(=1024KiB), GiB, GB, G, g(=1024MiB), TiB, T, t(=1024GiB). Workaround: The new symbols are supported, the floating point values are not. |
| RNR-637 | Domain browser view - Federation, services, tree items are not cleaned up. If a remote federation is started up and shut down, the node, federation, and services tree items are left behind. This effect is additive with every time the remote federation is restarted, a new federation folder gets placed and left behind in the tree. Workaround: Disconnecting and connecting to the domain again clears up the browser. |
| RNR-636 | Service status view - the view gives inconsistent results when multiple services start up on different nodes. If a remote federation other than the one RnR Manager is connected to, is started up and is running an RnR service of its own, the service status view is sometimes not properly updated. This often results in the "RnR Service Id/Node" column not being populated, or multiple rows for the service appearing. Workaround: Disconnecting and connecting to the domain again clears up the service status view with valid data. |
| RNR-634 | Deadlock sometimes occurs when RnR Manager force disconnects on loss of communication to OSPL. When RnR Manager encounters an unexpected loss of communication with OSPL and goes through the disconnect routine to handle it, an intermittent situation can occur where the tool operation halts and is frozen in deadlock. Workaround: Kill the RnR Manager process, and start it up again. |
| RNR-632 | ospl-info.log warning output from rnrManager process on storage import of CDR storage file. In Linux, When importing a storage, the following info log gets generated and placed in RnRManager's process directory. ============================================================== Report : WARNING Date : Fri Nov 06 09:49:31 PST 2015 Description : Incorrect storage attributes specified: used XML when opening an CDR storage Node : ubuntu Process : rnrManager <2343> Thread : 492db70 Internals : V6.5.2/3193fc7/00268a2/rr_storageAttrFromXML/ rr_storageAttrXML.c/80/0/1446832171.241958793 Aside from the warning, the import completes successfully and no other issues with the storage or its contents are noted. |
| RNR-529 | Export storage - storage file does not get properly initialized if using relative path. If the full file path and name is not specified, two sets of storage files gets created in different directories. As of version 6.6.0, warnings are displayed in the wizard if the path is not absolute, or if the current domain connection is to a remote host. Workaround: Always specify the full file path for the file name parameter in the Export Storage wizard. |
| RNR-618 | Historical scenario commands are lost on disconnect/reconnect. If the user creates a scenario with some commands, they are meant to be published transiently. Functionally, this means that if the scenario editor for a given scenario is closed and then reopened, the previously published commands will appear in the commands table. However, if the user disconnects and reconnects to the domain, and then the scenario editor is brought up again, the scenario commands do not appear in the commands table, and the transient samples are lost. |
| RNR-538 | Storage import fails if storage samples contain greater than 999 fields. Due to a limitation in the SQLite engine (used to store imported storages in the tool workspace), it cannot handle inserting samples whose data type contains 999 fields or greater. |
| RNR-610 | Connecting via JNI does not work when using Java 8. When running RnR Manager with a Java 8 jre, connecting via domain URI or domain ID fails. Workaround: Connect to OpenSplice domain using SOAP connection. |
| RNR-447 | Exception occurs when using Save As.. function in scenario editor. Any attempt to save a scenario file with a filepath that has a space, will throw an exception IF the installed jre is version 1.6. Workaround 1: Install Java JRE version 1.7. Workaround 2: Save scenario file to a filepath with no spaces. |
| RNR-254 | SELinux Install To install to SELinux, run the following commands in a terminal as root: $ /usr/sbin/setenforce 0 $ rnrManager install directory/install.sh $ /usr/sbin/setenforce 1 $ chcon -R -t textrel_shlib_t '/opt/ADLINK/VortexOpenSpliceRnRManager' |
| RNR-632 | ospl-info.log warning output from rnrManager process on storage import of CDR storage file. In Linux, When importing a storage, the following info log gets generated and placed in RnRManager's process directory. ============================================================== Report : WARNING Date : Fri Nov 06 09:49:31 PST 2015 Description : Incorrect storage attributes specified: used XML when opening an CDR storage Node : ubuntu Process : rnrManager <2343> Thread : 492db70 Internals : V6.5.2/3193fc7/00268a2/rr_storageAttrFromXML/ rr_storageAttrXML.c/80/0/1446832171.241958793 Workaround: Aside from the warning, the import completes successfully and no other issues with the storage or its contents are noted. |
Version 6.7.0
| Report ID. | Description |
|---|---|
| RNR-642 | Update tool's storage configuration maxFileSize parameter to use new symbols. (OSPL-7346) New data size symbols were introduced into the configuration processing for the RnR service . The configuration processing supports floating point values and the following units: b, B (bytes), KiB, kB, K, k(=1024 bytes), MiB, MB, M, m(=1024KiB), GiB, GB, G, g(=1024MiB), TiB, T, t(=1024GiB). Workaround: The new symbols are supported, the floating point values are not. |
| RNR-637 | Domain browser view - Federation, services, tree items are not cleaned up. If a remote federation is started up and shut down, the node, federation, and services tree items are left behind. This effect is additive with every time the remote federation is restarted, a new federation folder gets placed and left behind in the tree. Workaround: Disconnecting and connecting to the domain again clears up the browser. |
| RNR-636 | Service status view - the view gives inconsistent results when multiple services start up on different nodes. If a remote federation other than the one RnR Manager is connected to, is started up and is running an RnR service of its own, the service status view is sometimes not properly updated. This often results in the "RnR Service Id/Node" column not being populated, or multiple rows for the service appearing. Workaround: Disconnecting and connecting to the domain again clears up the service status view with valid data. |
| RNR-634 | Deadlock sometimes occurs when RnR Manager force disconnects on loss of communication to OSPL. When RnR Manager encounters an unexpected loss of communication with OSPL and goes through the disconnect routine to handle it, an intermittent situation can occur where the tool operation halts and is frozen in deadlock. Workaround: Kill the RnR Manager process, and start it up again. |
| RNR-633 | Java 7 VM warning when starting RnR Manager in Linux 32 bit. On Linux 32 bit platforms, the following Java warning gets printed to the console on start of RnR Mananger. Aside from the warning, the RnR Manager tool behaviour is not affected. |
| RNR-632 | ospl-info.log warning output from rnrManager process on storage import of CDR storage file. In Linux, When importing a storage, the following info log gets generated and placed in RnRManager's process directory.
Aside from the warning, the import completes successfully and no other issues with the storage or its contents are noted. |
| RNR-529 | Export storage - storage file does not get properly initialized if using relative path. If the full file path and name is not specified, two sets of storage files gets created in different directories. As of version 6.6.0, warnings are displayed in the wizard if the path is not absolute, or if the current domain connection is to a remote host. Workaround: Always specify the full file path for the file name parameter in the Export Storage wizard. |
| RNR-618 | Historical scenario commands are lost on disconnect/reconnect. If the user creates a scenario with some commands, they are meant to be published transiently. Functionally, this means that if the scenario editor for a given scenario is closed and then reopened, the previously published commands will appear in the commands table. However, if the user disconnects and reconnects to the domain, and then the scenario editor is brought up again, the scenario commands do not appear in the commands table, and the transient samples are lost. |
| RNR-538 | Storage import fails if storage samples contain greater than 999 fields. Due to a limitation in the SQLite engine (used to store imported storages in the tool workspace), it cannot handle inserting samples whose data type contains 999 fields or greater. |
| RNR-610 | Connecting via JNI does not work when using Java 8. When running RnR Manager with a Java 8 jre, connecting via domain URI or domain ID fails. Workaround: Connect to OpenSplice domain using SOAP connection. |
| RNR-447 | Exception occurs when using Save As.. function in scenario editor. Any attempt to save a scenario file with a filepath that has a space, will throw an exception IF the installed jre is version 1.6.
|
| RNR-254 | SELinux Install
|