Known Issues for Brand Mobiliser

Learn about known issues and apply workarounds for Sybase® Brand Mobiliser.

Bug #	Description
N/A	Issue: An error appears on the console when Brand Mobiliser is started in Windows using the default out of the box configuration, for example: Wed Oct 10 12:05:47 PDT 2012 Thread[FelixStartLevel,5,main] java.io.FileNotFoundException: C:\..\log\derby.log (The system cannot find the path specified) By default, the location of the Derby database error log is configured for Linux. Workaround: In the derby.properties file, change the location to: derby.stream.error.file=..\\log\\derby.log
N/A	Issue: Event application end time is not honored. An event continues to run with an expired Active To date. This can occur when the event stop date and time are later than the event application Active To date. Workaround: Set the event stop date and time to coincide with the event application Active To date.

Bug #

Description

N/A

Issue: An error appears on the console when Brand Mobiliser is started in Windows using the default out of the box configuration, for example:

Wed Oct 10 12:05:47 PDT 2012 Thread[FelixStartLevel,5,main]
      java.io.FileNotFoundException:
        C:\..\log\derby.log (The system cannot find the path specified)

By default, the location of the Derby database error log is configured for Linux.

Workaround: In the derby.properties file, change the location to:

derby.stream.error.file=..\\log\\derby.log

N/A

Issue: Event application end time is not honored.

An event continues to run with an expired Active To date. This can occur when the event stop date and time are later than the event application Active To date.

Workaround: Set the event stop date and time to coincide with the event application Active To date.