Welcome to TIBCO BusinessEvents® Extreme - TIBCO Product ...

TIBCO BusinessEvents® Extreme 1.1.1 Release Notes

Welcome to TIBCO BusinessEvents® Extreme

TIBCO BusinessEvents Extreme® is a high-performance event processing platform for

applications that monitor, analyze, and respond to parallel event streams in and across the

enterprise, making decisions, taking action, and running services in real-time. TIBCO

BusinessEvents Extreme delivers dramatic new levels of performance, scalability, and robustness

for demanding Complex Event Processing (CEP) and real-time event-driven applications.

The platform automatically manages consistency for efficient parallel processing and high

vertical scalability, while freeing applications from the complexity of concurrent and distributed

programming. A hybrid Rules and Java programming model enables applications to maximize

the capabilities of both languages, seamlessly share data and events, and integrate to existing

Java assets.

Where to Find Information

See the Getting Started Guide for quickly getting TIBCO BusinessEvents Extreme® up and

running.

The following information is also shipped with the product:

Installation Guide - Installation details.

Application Architect's Guide - Architectural details on rules programming.

Application Developer's Guide - Programmer documentation on rule programming.

Decision Manager User's Guide - User documentation on decision tables.

WebStudio User's Guide - User documentation on WebStudio.

Architect's Guide - Architectural details on the application server platform.

Java Developer's Guide - Java programmer documentation

Administrators's Guide - Administration documentation

Performance Tuning Guide - Application performance tuning documentation

System Sizing Guide - Sizing machine resources for applications

API reference - javadoc for all APIs

Code snippets - source code for the programming snippets in the Java Developer's Guide

Product Compatibility

The TIBCO BusinessEvents® Extreme Data Grid feature is compatible with TIBCO

ActiveSpaces® Enterprise Edition 2.0.2 Hot Fix 9.

Supported Platforms and Browser Versions

TIBCO BusinessEvents® Extreme is supported on these platforms.

Development and deployment are supported on Red Hat Enterprise Linux Server versions

5.8 to 6.4 on 64-bit x86 (x86_64) processors.

Development is supported on Macintosh OS X 10.8 on 64-bit x86 (x86_64) processors.

Development is supported on Windows 7 on 64-bit x86 (x86_64) processors.

The compat-expat1, pstack, gdb, and sysstat packages must be installed when running on Red

Hat. The rpm package manager can be used to query and verify that these packages are installed.

rpm -q compat-expat1 - compat-expat1-1.95.8-8.el6.x86_64

rpm -q pstack - pstack-1.2-7.2.2

rpm -q gdb - gdb-7.0.1-42.el5

rpm -q sysstat - sysstat-7.0.2-11.el5

The pstack, gdb, and sar packages must be installed when running on Red Hat.

Red Hat 6.2 ships with a new implementation of malloc that consumes more heap memory by

default. Details can be found here - 13.4. GNU C Library (glibc). Tuning the

MALLOC_ARENA_MAX environment variable can reduce memory allocation.

TIBCO ActiveSpaces® Administrator supports these browsers. The version number is the

minmum version supported.

Chrome 16

Firefox 9

Internet Explorer 9

Safari 5

Minimum Disk Space and Memory Requirements

Disk Space - 4 GB

Memory - 2GB RAM

Java Compatibility

TIBCO BusinessEvents Extreme® ships with these two JRE versions:

1.7.0_45 - default JRE

1.6.0_30

Deployment is supported on both JRE 1.6 and 1.7

Studio projects must be compiled using a Java compiler compliance level of 1.6. Studio projects

are automatically configured to use a JDK 1.6 compliance. This should not be changed.

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.0_Release_Notes/compiler.html

Major Improvements in TIBCO BusinessEvents® Extreme

1.1.1

Upgraded to TIBCO BusinessEvents® 5.1.1 Hot Fix 8.

Upgrade to TIBCO ActiveSpaces® Enterprise Edition 2.0.2 Hot Fix 9.

On-going stability improvements.

Upgrading to BusinessEvents® Extreme 1.1.1

The following changes must be made to upgrade to TIBCO BusinessEvents® Extreme 1.1.1

from previous releases.

The undocumented ldapauth administration target was renamed to ldap. Any references

to ldapauth must be updated to use the ldap target instead.

Parameter names changed on the undocumented display session administration

command. endpointName changed to endpointname and serviceName changed to

servicename.

Parameter names changed on the undocumented display endpoint administration

command. serviceName changed to servicename.

Support for the javatransaction statistic type was removed from the undocumented

statistic administration target.

The javatransactionclass statistic type was renamed to javatransaction on the

undocumented statistic administration target.

The nodename parameter was removed from the undocumented getadminport node

administration command.

The time parameter was renamed to seconds on the undocumented snapshot statistics


The nodename parameter was removed from the undocumented remove node


The display, expand, and remove commands were removed from the snapshot

administration target.

The force parameter was renamed to type on the undocumented leave cluster


The undocumented update partition administrative command was renamed to migrate

partition.

The undocumented refresh partition administrative command was renamed to update

partition.

Deprecations

The following features were deprecated in this release and will be removed in a future release.

Please update your applications and development environment.

The undocumented runtimestatistcs administration target was renamed to statistics. The

runtimestatistics target still exists for backward compatibility, but it will be removed in a

future release. Please update any tools that use the runtimestatistics target to use the

statistics target instead.

The undocumented create partition administration command is deprecated. Please use

the define partition command instead.

The undocumented restore partition administration command is deprecated. Please use

the define partition command instead.

Support for X.509 credentials is deprecated. There will be no replacement for this feature.

Please use username/password credentials instead.

Support for application logging being available in the domain manager event cache is

deprecated. There is no replacement for this feature planned. Standard Java logging

facilities should be used instead.

Support for scheduled administrative commands run via configuration is deprecated. The

same functionality can be achieved using com.kabira.test.management.Client with any

Java library that provides the appropriate timer functionality. Examples include:

o java.util.TimerTask

o java.util.concurrent.ScheduledExecutorService

o Quartz Scheduler

o cron4j

Please migrate applications to use one of these packages.

1.1.1 Resolved Issues

For resolved issues in embedded products please see these release notes:

TIBCO ActiveSpaces®

TIBCO ActiveSpaces® Transactions

TIBCO BusinessEvents®

Bug

[FLUENCY-5476] - ASTA: displays unknown version and build

[FLUENCY-5957] - BUILDER: script hard-codes BE version

[FLUENCY-6246] - DEPLOY: deploy from windows fails if backslashes in EAR path

[FLUENCY-6258] - STUDIO: project's jar file gets increasingly larger

[FLUENCY-6295] - DOCUMENTATION: registered trade mark symbol doesn't render

correctly

[FLUENCY-6308] - UPGRADE: upgrade.jar is incomplete for BE-X.

[FLUENCY-6378] - RUNTIME: performance of passing concepts with arrays to catalog

functions very poor

[FLUENCY-6383] - DEPLOY: upgrade tool requires bex-runtime.jar

[FLUENCY-6394] - CATALOG: nested concept arrays not refreshed

[FLUENCY-6436] - CATALOG: passing null array causes assertion

[FLUENCY-6461] - CONCEPT: date time arrays cause java.util.GregorianCalendar

cannot be cast to java.util.Date

http://downloads.fluency.kabira.com/fluency/P.AST.JAVASDK-2.3.2-x86_64/documentation/reference/com/kabira/test/management/Client.html

http://docs.oracle.com/javase/6/docs/api/java/util/TimerTask.html

http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ScheduledExecutorService.html

http://www.quartz-scheduler.org/

http://www.sauronsoftware.it/projects/cron4j

https://docs.tibco.com/pub/activespaces/2.0.2-november-2012/TIB_activespaces_2.0.2_relnotes.pdf

https://devzone.tibco.com/display/DOWN/ActiveSpaces+Transactions+2.3.3

https://docs.tibco.com/pub/businessevents/5.1.1_dec_2012/TIB_businessevents-standard_5.1.1_relnotes.pdf

https://devzone.tibco.com/jira/browse/FLUENCY-5476











[FLUENCY-6462] - CATALOG: updates lost when new concept returned

[FLUENCY-6475] - CATALOG: contained concepts not returned correctly

[FLUENCY-6476] - BUILDER: Java Model Exception build EAR file using command

line

Documentation

[FLUENCY-6478] - DOCS: Update copyright to 2014

Improvement

[FLUENCY-6303] - CODEGEN: support serializable on concepts and events

Task

[FLUENCY-5611] - STUDIO: Project library testing with BE-X Studio

[FLUENCY-6315] - 3RDPARTY: upgrade to BE 5.1.1 HF 8

[FLUENCY-6452] - Doc Impact of FLUENCY-6315 3RDPARTY: upgrade to BE 5.1.1

HF 8

[FLUENCY-6479] - 3RDPARTY: Upgrade TIBCO Universal Installer version to 3.2.2

1.1.0 Resolved Issues

For resolved issues in embedded products please see these release notes:


TIBCO ActiveSpaces® Transactions


Bug

[FLUENCY-4582] - DEPLOY: be-x.kds hard-codes version number

[FLUENCY-4587] - BUILD: pom.xml hard-codes BE version number

[FLUENCY-4841] - CODEGEN: missing javadoc on generated Java files

[FLUENCY-4883] - DEPLOY: Incomprehensible error on deploy.jar command line with

CDD option out of order

[FLUENCY-4953] - Doc Impact of FLUENCY-4950 QUERY: generated order key

functions do not support optional key values

[FLUENCY-5001] - STUDIO: assertion while opening the concept editor.

[FLUENCY-5025] - DEPLOY: IOException [error in opening zip file]

[FLUENCY-5061] - QUERY: Instance.getById not working

[FLUENCY-5131] - CLASSLOADER: java.lang.ClassNotFoundException:

com.sun.jdi.ClassLoaderReference

[FLUENCY-5170] - DEVGUIDE: Remove reference to domain objects configuration

[FLUENCY-5206] - DEPLOY: detached deployment problem with descriptor parameter











https://devzone.tibco.com/display/DOWN/ActiveSpaces+Transactions+2.3.2













[FLUENCY-5207] - DEPLOY: Class not found:

com.tibco.cep.container.standalone.BEMain

[FLUENCY-5232] - DEVGUIDE: Update working with external libraries section

[FLUENCY-5240] - Doc Impact of FLUENCY-4864 CATALOG: cannot cast to derived

Event or Concept in catalog function

[FLUENCY-5279] - Doc Impact of FLUENCY-5278 CATALOG: audit against

overloaded catalog functions

[FLUENCY-5302] - RUNTIME: timed event causes java.lang.IllegalAccessError: no

active transaction

[FLUENCY-5304] - INSTALLER: needs to be updated for changes to P.BEX directory

structure

[FLUENCY-5318] - DEPLOY: hot deploy fails with

java.util.ConcurrentModificationException

[FLUENCY-5337] - DEPLOY: improve invalid descriptor parameter message

[FLUENCY-5352] - Doc Impact of FLUENCY-5212 ENTITY: external identifier

mapping generates duplicate extIds

[FLUENCY-5363] - Doc Impact of FLUENCY-5362 CATALOG: nested classes cause

compilation failures

[FLUENCY-5405] - INSTALLER: Installer includes BE DecisionManager assembly

[FLUENCY-5408] - Doc Impact of FLUENCY-5349 CATALOG: array of Long

parameters and return values prevents rule execution

[FLUENCY-5427] - Doc Impact of FLUENCY-4573 CATALOG: first instance of

@Catalog annotation used

[FLUENCY-5448] - DEPLOY: processingunit deploy parameter not passed to BEMain

[FLUENCY-5505] - RUNTIME: Incorrect INFO message for AgentTimeManager

[FLUENCY-5508] - RUNTIME: Rule joins appear to fail under load

[FLUENCY-5515] - DEPLOY: deploy.jar not available for studio-tools tests

[FLUENCY-5522] - INSTALLER: shipping unmodified BE examples

[FLUENCY-5533] - CATALOG: NullPointerException when creating custom Java

function in default package

[FLUENCY-5541] - RUNTIME: duplicate identifiers assigned on restart

[FLUENCY-5548] - RUNTIME: Duplicate key exceptions with highly available

concepts

[FLUENCY-5551] - COMPONENT: ComponentNotifier class not found when packaged

in the ear file

[FLUENCY-5558] - STUDIO: System JVM not installed on project import

[FLUENCY-5559] - RUNTIME: ClassNotFoundException when Concept in project

library

[FLUENCY-5587] - RUNTIME: java.nio.BufferUnderflowException routing events

across nodes

[FLUENCY-5601] - STUDIO: Not able to Import .projlib into project

[FLUENCY-5605] - CATALOG: passing transient event to catalog function cause

assertion

[FLUENCY-5622] - RUNTIME: assert entityImpl.isLoadedFromCache() == true;

[FLUENCY-5630] - RUNTIME: java.lang.RuntimeException: Can't invokeFunction

inside the session itself






























[FLUENCY-5631] - GETTINGSTARTED: Fraud Detection - Debit fraud detection

behavior not behaving as expected

[FLUENCY-5640] - STUDIO: clean not removing build JAR

[FLUENCY-5642] - STUDIO: workspace compiler version must be set to 1.6

compliance

[FLUENCY-5650] - RUNTIME: asserting concept in running RTC causes assertion

[FLUENCY-5663] - DEPLOY: missing processing unit description in usage message

[FLUENCY-5666] - DEPLOY: invalid EAR name causes null pointer exception

[FLUENCY-5673] - CODEGEN: array getter modifying shared memory

[FLUENCY-5674] - EVENT: destination and payload not refreshed from shared memory

[FLUENCY-5679] - RUNTIME: deleting concept in catalog functions causes null pointer

exception

[FLUENCY-5684] - EVENT: null date field causes null pointer exception

[FLUENCY-5685] - STUDIO: java.lang.AssertionError: No catalog functions file in

CatalogFunctions_build5.jar

[FLUENCY-5687] - CATALOG: updating java file containing catalog functions does not

remove previous generated stub file

[FLUENCY-5689] - DEPLOY: Runtime warning unable to process ../sdk/deploy.jar

which isn't part of server-side install

[FLUENCY-5691] - CONCEPT: modifications to asserted concepts not written back to

shared memory

[FLUENCY-5693] - EXAMPLE: Fraud Detection - A default destination is not specified

[FLUENCY-5700] - RUNTIME: concept return values from catalog functions not

refreshed

[FLUENCY-5705] - RUNTIME: double arrays cause ClassCastException

[FLUENCY-5709] - DEPLOY: failing "getOutputDirectory failure: directory permission

problems"

[FLUENCY-5712] - EVENT: Deleting a non-transient event with a TTL causes

java.lang.NullPointerException

[FLUENCY-5716] - EVENT: reloading non-transient event causes duplicate timer

expirations

[FLUENCY-5718] - Doc Impact of FLUENCY-5712 EVENT: Deleting a non-transient

event with a TTL causes java.lang.NullPointerException

[FLUENCY-5719] - CATALOG: array updates in rule language lost when calling

catalog function

[FLUENCY-5729] - BUILDER: command-line build moves CVS files to bin directory

[FLUENCY-5730] - BUILDER: debug tracing always on

[FLUENCY-5732] - BUILDER: does not clean up workspace directory when interrupted

[FLUENCY-5733] - STUDIO: Unable to change java source folder

[FLUENCY-5745] - CODEGEN: generated proxy classes contained unused

com.kabira.platform.ManagedObject import

[FLUENCY-5746] - CODEGEN: generated concept proxy classes have unused local

variable named mc.

[FLUENCY-5747] - Doc Impact of FLUENCY-5533 CATALOG: NullPointerException

when creating custom Java function in default package

[FLUENCY-5748] - EVENT: setChannelContext() cannot be invoked on a remote node































[FLUENCY-5750] - RUNTIME: hot deployment of rule and rule functions not enabled

[FLUENCY-5754] - CATALOG: intermittent catalog function resolution failures

[FLUENCY-5758] - KEY: invalid java identifiers in key name cause compilation failures

[FLUENCY-5765] - Doc Impact of FLUENCY-5642 STUDIO: workspace compiler

version must be set to 1.6 compliance

[FLUENCY-5769] - Doc Impact of FLUENCY-5758 KEY: invalid java identifiers in key

name cause compilation failures

[FLUENCY-5781] - DEPLOY: processingunit parameter not being correctly passed to

BE main.

[FLUENCY-5784] - STUDIO: clean not working on projects outside of workspace

[FLUENCY-5788] - CATALOG: invalid code generated for array of concept parameters

[FLUENCY-5806] - EVENT: rule based time event scheduled incorrectly

[FLUENCY-5809] - BUILDER: enterprise archive sometimes missing files

[FLUENCY-5813] - CATALOG: multiple updates are done mapping concept parameters

[FLUENCY-5815] - EVENT: Trying to assert a NonTransient Event with a payload from

java generates exception

[FLUENCY-5816] - EVENT: TTL Expiration For Events not created on active node

throws ExceptionResourceUnavailable

[FLUENCY-5817] - EVENT: stringToObject fails with exception when trying to find an

event on the non-primary node

[FLUENCY-5826] - BUILDER: java.io.IOException: error=13, Permission denied on

OS X

[FLUENCY-5829] - RUNTIME: nested concepts (and events) not initialized

[FLUENCY-5831] - CATALOG: nested catalog functions not handled correctly

[FLUENCY-5835] - BEAST: crosstalk between regressions

[FLUENCY-5839] - BUILDER: building invalid jar file inside of shared archive file

[FLUENCY-5858] - Doc Impact of FLUENCY-5061 QUERY: Instance.getById not

working

[FLUENCY-5859] - Doc Impact of FLUENCY-5815 EVENT: Trying to assert a

NonTransient Event with a payload from java generates exception

[FLUENCY-5863] - STUDIO: Unsupported IClasspathEntry kind=4 when converting

BE-X project to maven

[FLUENCY-5864] - CODEGEN: error when inherit from concept in project library

[FLUENCY-5865] - STUDIO: unable to find java class imported from project library

[FLUENCY-5869] - RUNTIME: java.lang.RuntimeException does not rollback a

transaction

[FLUENCY-5876] - EVENT: org.xml.sax.SAXParseException when asserting event

with XML payload from Java

[FLUENCY-5879] - DEPLOY: incorrect version in deploy.jar (Windows archive)

[FLUENCY-5885] - WEBSTUDIO: Unable to generate ear using Web Studio

[FLUENCY-5910] - BUILDER: build project not handling relative paths

[FLUENCY-5915] - RUNTIME: deadlock exceptions not being rethrown when creating

proxy objects

[FLUENCY-5921] - EVENT: typo in toString @tty --> @ttl

[FLUENCY-5922] - RUNTIME: enabling tracing causes java.lang.NullPointerException

[FLUENCY-5927] - BUILDER: cannot use "." for the local directory


































[FLUENCY-5930] - INSTALLER: does not define RMS dependency upon sdk

[FLUENCY-5940] - WEBSTUDIO: rmsbuilder.bat fails if project path or output file path

contains spaces

[FLUENCY-5943] - STUDIO: When a key is changed in a concept that has been saved,

the keys sometimes don't take and error messages appear

[FLUENCY-5946] - BUILD: mvn site:site in beast project re-compiles projects a lot

more times than probably necessary

[FLUENCY-5949] - BUILDER: does not include decision table class files in EAR

[FLUENCY-5953] - EVENT: Timed events firing twice

[FLUENCY-5956] - BUILDER: java-only project with no .classpath file fails to compile

[FLUENCY-5962] - RUNTIME: clearing an array not updated in shared memory

[FLUENCY-5966] - BUILDER: removeworkspace default should be false

[FLUENCY-5976] - CATALOG: contained reference modifications not flushed when

calling catalog functions

[FLUENCY-5982] - INSTALLER: does not run on mac with java 1.7

[FLUENCY-5995] - BUILDER: wrapper script not handling SW_HOME correctly

[FLUENCY-6001] - STUDIO: import project library fails during project rebuild

[FLUENCY-6002] - BUILDER: command-line builds fails when import project libraries

[FLUENCY-6003] - BUILDER: error message about com.tibco.cep.thirdparty plugin

when builder re-uses workspace

[FLUENCY-6019] - BUILDER: occasional ProjectLibraries test failure - Resource

'/LibraryB' is not open

[FLUENCY-6021] - BUILDER: test failures due to Ambiguous Reference errors

[FLUENCY-6023] - WEBSTUDIO: null pointer deploying rule template instance

[FLUENCY-6041] - LIBRARY: Project 'ImportTest01' is missing required library

[FLUENCY-6049] - WEBSTUDIO: generate deployable fails if generate classes only

[FLUENCY-6051] - WEBSTUDIO: ResourceException: Problems encountered while

moving resources.

[FLUENCY-6054] - BUILDER: uses invalid /bin/sh arguments

[FLUENCY-6060] - LIBRARY: build error if project and project library have classes

with same name

[FLUENCY-6064] - RUNTIME: null concepts cause bogus assertion

[FLUENCY-6077] - STUDIO: EAR file not over written

[FLUENCY-6089] - BUILDER: be-x 1.1.0 command-line build of be-x 1.0.x project

fails

[FLUENCY-6091] - BUILDER: command-line build fails if rule function contains SOAP

events

[FLUENCY-6093] - CATALOG: project library not cleaned up on project import

[FLUENCY-6094] - STUDIO: classpath jar paths not updated when importing an 1.0.x

model

[FLUENCY-6095] - BUILDER: workspace unusable if previous build fails without

closing project

[FLUENCY-6096] - BUILDER: creates a directory named "be"

[FLUENCY-6097] - BUILDER: can return 0 exit status after failure

[FLUENCY-6105] - LIBRARY: Studio Generates Error Message cannot find Projlib

when its not in the project anymore


































[FLUENCY-6115] - WEBSTUDIO: does not support decision table class file generation

[FLUENCY-6116] - BUILDER: .smap files missing from EARs generated by builder

[FLUENCY-6121] - CATALOG: Build Path not been updated on project import

[FLUENCY-6124] - RUNTIME: Referenced concept not updated into shared memory

[FLUENCY-6128] - HOTDEPLOY: document catalog function changes not supported

[FLUENCY-6132] - RUNTIME: calling catalog functions with concept parameter in

preprocessor causes assertion

[FLUENCY-6133] - RUNTIME: contained arrays of concepts created in preprocessor

lost when catalog function called

[FLUENCY-6135] - LIBRARY: ProjectLibraries/LibraryC build failing

[FLUENCY-6136] - LIBRARY: extending concept from project library fails assertion

[FLUENCY-6138] - BUILDER: remove classpath parameter from build archive and

export library commands

[FLUENCY-6143] - RUNTIME: handle deleted events in timer notifier

[FLUENCY-6144] - Doc Impact of FLUENCY-6115 WEBSTUDIO: does not support

decision table class file generation

[FLUENCY-6145] - LIBRARY: toolstest/ImportLibraryTest failure

[FLUENCY-6147] - Doc Impact of FLUENCY-6138 BUILDER: remove classpath

parameter from build archive and export library commands

[FLUENCY-6149] - RUNTIME: concept update missed calling catalog function

[FLUENCY-6156] - RUNTIME: TTL timer does not expire on consumed events

[FLUENCY-6158] - BUILDER: set default MaxPermSize the same as Studio

[FLUENCY-6159] - BUILDER: disable eclipse history in command-line builds

[FLUENCY-6162] - DEPLOY: update BE-X usage message

[FLUENCY-6163] - DEPLOY: usage message incorrect

[FLUENCY-6173] - WEBSTUDIO: hot deployment failure with WebStudio-generated

EAR

[FLUENCY-6179] - Doc Impact of FLUENCY-5994 WEBSTUDIO: no examples in

default configured ws.scs.rootURL in RMS CDD

[FLUENCY-6184] - Doc Impact of FLUENCY-5966 BUILDER: removeworkspace

default should be false

[FLUENCY-6192] - Doc Impact of FLUENCY-5908 CEP-MAVEN: rename or remove

the cep:ear version parameter

[FLUENCY-6194] - README: Invalid readme shipped

[FLUENCY-6196] - BUILDER: command-line too long error on windows

[FLUENCY-6207] - INSTALLER: BEX_HOME not defined in decisionmanager.ini

[FLUENCY-6209] - LIBRARY: The operator "+" is not compatible with types "String

[FLUENCY-6212] - Doc Impact of FLUENCY-5930 INSTALLER: does not define

RMS dependency upon sdk

[FLUENCY-6216] - BUILDER: buildproject parameter should be private

[FLUENCY-6222] - INSTALLER: unistaller is not cleaning up BE-X installation

[FLUENCY-6235] - BUILD: test artifacts deployed to maven repository

[FLUENCY-6244] - RUNTIME: null concept properties that are set cause bogus

assertion

[FLUENCY-6245] - CONCEPT: mutable property cannot be selected when upgrading



































Documentation

[FLUENCY-4603] - BE-X: integrate BE-X javadoc with AST javadoc

[FLUENCY-4618] - DOCS: Registered trademark symbol incorrectly used for product

name in docs

[FLUENCY-4717] - DEVGUIDE: BE-X developer's guide global variable deployment

settable.

[FLUENCY-4718] - DEVGUIDE: Description of descriptor and processingunit

parameters

[FLUENCY-4890] - DEVGUIDE: need to state that key fields are immutable

[FLUENCY-4938] - ARCHGUIDE: add details on Concept assertion/locking

[FLUENCY-4964] - DEVGUIDE: update CDD chapters to make explicit what is

required for BE-X

[FLUENCY-4996] - DEVGUIDE: clarify/improve logging configuration levels

[FLUENCY-5141] - DEVGUIDE: modifying ignored resources list instructions wrong

[FLUENCY-5280] - AST: release note update Linux

[FLUENCY-5341] - DOCUMENTATION: missing javadoc in the SDK for

com.kabira.test.management.Client and Client.Configuration

[FLUENCY-5342] - DOCUMENTATION: remove internal

com.kabira.platform.swtimer.Configure from SDK javadoc

[FLUENCY-5397] - USERDOC: Update copyright year

[FLUENCY-5403] - WEBSTUDIO: documentation missing from BE-X documentation

[FLUENCY-5404] - DECISIONMANAGER: documentation branded as BE instead of

BE-X

[FLUENCY-5466] - ARCHGUIDE: describe rule priority evaluation

[FLUENCY-5498] - 3RDPARTY: Smart GWT Enterprise Edition 2.5 is missing in BEX

1.0.2

[FLUENCY-5579] - 3RDPARTY: fix vendor name for StringTemplate

[FLUENCY-5588] - 3RDPARTY: Tom Sawyer version is incorrect

[FLUENCY-5598] - 3RDPARTY: AppacheTomcat version

[FLUENCY-5604] - DEVGUIDE: document setting of global variables on command line

[FLUENCY-5627] - GETTINGSTARTED: Fraud Detection example description minor

mixups

[FLUENCY-5662] - DEVGUIDE: setting of the Object Management type in CDD

[FLUENCY-5665] - GETTINGSTARTED: Add Processing Unit parameters in deploy

command

[FLUENCY-5704] - INSTALL: Installation guide is missing

[FLUENCY-5706] - DOCS: Application guides version number incorrect

[FLUENCY-5785] - ARCHGUIDE: describe loading of referenced concepts in

properties and arrays

[FLUENCY-6004] - HOTDEPLOY: add hot deployment documentation

[FLUENCY-6008] - WEBSTUDIO: JMX load/unload interface not documented

[FLUENCY-6057] - ARCHGUIDE: update query load behavior description

[FLUENCY-6157] - DEVGUIDE: Document behavior of consumed events with TTL !=

0

[FLUENCY-6174] - DECISIONMANAGER: missing authentication information

































[FLUENCY-6180] - GETTINGSTARTED: Remove reference to EAR location

Improvement

[FLUENCY-4698] - DEPLOY: too chatty

[FLUENCY-4773] - DEPLOY: application name always

com.tibco.cep.container.standalone.BEMain

[FLUENCY-4790] - INSTALLER: Remove editing of BE's studio.tra to add

TIBCO.BE.function.catalog.getbyuri

[FLUENCY-4805] - Doc Impact of FLUENCY-4804 CODEGEN: package names should

be all lower case

[FLUENCY-4808] - Doc Impact of FLUENCY-4807 FUNCTION: audit that containing

class is public

[FLUENCY-4811] - Doc Impact of FLUENCY-4809 FUNCTIONS: audit that catalog

function methods do not throw an exception

[FLUENCY-4836] - Doc Impact of FLUENCY-4817 CATALOG: Automatically add

java libraries to custom functions build path

[FLUENCY-4944] - Doc Impact of FLUENCY-4907 CODEGEN: change constructor

signatures to only include required fields (keys)

[FLUENCY-5118] - INSTALLER: confirm installers work with new TIBCO installer

feature to select Java installation

[FLUENCY-5195] - DEPLOY: improve performance of EAR archive handling

[FLUENCY-5246] - Doc Impact of FLUENCY-4563 CATALOG: Add support for

Concepts and Events in generated catalog functions

[FLUENCY-5247] - Doc Impact of FLUENCY-5245 EVENT: rename generate method

to assertEvent

[FLUENCY-5248] - CODEGEN: generate primitive field types

[FLUENCY-5350] - JAVADOC: SDK javadoc generation script

[FLUENCY-5418] - Doc Impact of FLUENCY-5417 CATALOG: audit against spaces in

category names

[FLUENCY-5428] - Doc Impact of FLUENCY-5423 CATALOG: support Object arrays

for parameter and return values

[FLUENCY-5463] - EVENT: transient events are managed objects

[FLUENCY-5546] - Doc Impact of FLUENCY-5483 RUNTIME: integrate with log

subsystem

[FLUENCY-5570] - RUNTIME: remove global identifier key from shared memory

[FLUENCY-5573] - Doc Impact of FLUENCY-5463 EVENT: transient events are

managed objects

[FLUENCY-5575] - Doc Impact of FLUENCY-5248 CODEGEN: generate primitive

field types

[FLUENCY-5597] - RUNTIME: disable metric collection

[FLUENCY-5617] - RUNTIME: cache type identifier

[FLUENCY-5619] - RUNTIME: check for entity already loaded into working memory

[FLUENCY-5620] - RUNTIME: remove explicit locking in update/delete

[FLUENCY-5629] - RUNTIME: remove usage of Class.forName() from

Concept.cardinality & Concept.lookupQuery




























[FLUENCY-5656] - RUNTIME: cache ServiceProvider.isRulesEngineActive value

[FLUENCY-5657] - RUNTIME: remove synchronization from

TransactionService.getInstance().

[FLUENCY-5667] - EVENT: add support for destination URI

[FLUENCY-5670] - Doc Impact of FLUENCY-5667 EVENT: add support for

destination URI

[FLUENCY-5682] - CODEGEN: only create GregorianCalendar if required in property

accessor

[FLUENCY-5699] - STUDIO: support upgrading between releases

[FLUENCY-5713] - DEPLOY: update help message for detach=true and EAR location

[FLUENCY-5720] - CATALOG: Add function annotation to generated tooltip

[FLUENCY-5722] - Doc Impact of FLUENCY-5713 DEPLOY: update help message for

detach=true and EAR location

[FLUENCY-5725] - RUNTIME: remove use of isEmpty and replace with exception

[FLUENCY-5726] - RUNTIME: remove call to ASSpace.getOp

[FLUENCY-5727] - RUNTIME: remove call to ManagedObject.isManaged

[FLUENCY-5731] - BUILDER: Allow user to configure where builder workspace

directory is created

[FLUENCY-5740] - STUDIO: Generate jar files to the build output directory

[FLUENCY-5749] - DEPLOY: copy target to server in detached mode

[FLUENCY-5827] - BUILDER: temp directories should be in "." directory

[FLUENCY-5832] - CATALOG: audit against "." in category names

[FLUENCY-5872] - RUNTIME: set be.ontology.concept.session.check to false

[FLUENCY-5874] - Doc Impact of FLUENCY-5832 CATALOG: audit against "." in

category names

[FLUENCY-5888] - BUILDER: default project parameter to current directory

[FLUENCY-5892] - CATALOG: empty java stub files generated if no catalog functions

[FLUENCY-5899] - RUNTIME: improve handling of misconfigured deployment

descriptor

[FLUENCY-5911] - BUILDER: usage message formatting could be better

[FLUENCY-5974] - CONCEPT: raise exception if immutable key field set is attempted

[FLUENCY-5984] - LIBRARY: store imported project libraries outside of .beproject file

[FLUENCY-6012] - BUILDER: remove exception stack from build failure message

[FLUENCY-6017] - CATALOG: clean up stale project JAR files

[FLUENCY-6050] - LIBRARY: store project libraries as class path containers

[FLUENCY-6075] - Doc Impact of FLUENCY-5749 DEPLOY: copy target to server in

detached mode

[FLUENCY-6137] - Doc Impact of FLUENCY-5984 LIBRARY: store imported project

libraries outside of .beproject file

New Feature

[FLUENCY-4780] - BUILDER: support command line builds

[FLUENCY-4842] - STUDIO: include external JAR dependencies in EAR

[FLUENCY-4960] - Doc Impact of FLUENCY-4959 QUERY: add support for query

result cardinality


































[FLUENCY-4980] - Doc Impact of FLUENCY-4966 FUNCTIONS: support migration

of existing catalog functions

[FLUENCY-5099] - CONCEPT: add support for mutable keys

[FLUENCY-5133] - ADMINISTRATION: add deploy specification support for

JRE/JDK location

[FLUENCY-5303] - Doc Impact of FLUENCY-5209 ENTITY: add support for adding

concepts and events to working memory from Java

[FLUENCY-5351] - Doc Impact of FLUENCY-5153 CONCEPT: Add "assert this

object" API

[FLUENCY-5616] - DATAGRID: ship RC file to start up data grid

[FLUENCY-5675] - EVENT: add support for asynchronous responses for builtin

channels

[FLUENCY-5690] - EVENT: Transient events not supported as arguments in distributed

methods

[FLUENCY-5710] - Doc Impact of FLUENCY-5675 EVENT: add support for

asynchronous responses for builtin channels

[FLUENCY-5988] - Doc Impact of FLUENCY-4780 BUILDER: support command line

builds

[FLUENCY-6176] - Doc Impact of FLUENCY-5099 CONCEPT: add support for

mutable keys

Task

[FLUENCY-5104] - DEPLOY: move BE-X system properties settings to bexapp deploy

specification

[FLUENCY-5238] - Doc Impact of FLUENCY-5237 3RDPARTY: upgrade to

ActiveSpaces 2.0.2

[FLUENCY-5510] - Doc Impact of FLUENCY-5307 AST: certify on Red Hat 6.3

[FLUENCY-5516] - STUDIO: review BE-X changes for studio-tools

[FLUENCY-5580] - BUILDER: regressions require an X server

[FLUENCY-5668] - EVENT: add event payload test


[FLUENCY-5912] - INSTALLER: update be-rms.tra for BE-X

[FLUENCY-5959] - BUILDER: remove dependency on defaultjre for internal use

[FLUENCY-5967] - 3RDPARTY: Update Tomcat 7 version


[FLUENCY-6081] - DEPLOY: generate deprecation warnings for legacy BE parameters

[FLUENCY-6134] - Doc Impact of FLUENCY-5633 3RDPARTY: certify on RedHat

6.4

[FLUENCY-6139] - BUILDER: make the build project command private


[FLUENCY-6146] - Doc Impact of FLUENCY-6139 BUILDER: make the build project

command private

[FLUENCY-6171] - INSTALLER: verify installation customization

[FLUENCY-6172] - Doc Impact of FLUENCY-6081 DEPLOY: generate deprecation

warnings for legacy BE parameters






























Known Issues

A summary of the known issues in this release is below.

For known issues in embedded products please see these release notes:



For each issue the following is provided:

Description of issue

Workaround (if any)

Plans for resolution

Key Summary Public Issue Description

FLUENCY-

2482

ADMINISTRA

TION: no error

message

reported if

MDNS disabled

If the MDNS daemon is disabled, no error message is

displayed to the user when using servicename with

administrator. administrator just returns a non-zero error

code. For example: administrator servicename=xxxx display node

echo $?

1

An error message will be returned in a future release.

FLUENCY-

287

ASTA: Browser

refresh logs you

out

Using ActiveSpacesÂ® Transactions Administrator with any

browser, when you reload the current page by any means (for

example, clicking on the browser's "Reload" button, or

pressing ctrl-R), ActiveSpacesÂ® Transactions

Administrator logs you out of all nodes and returns you to the

original login screen.

This issue will be fixed in a future release.

FLUENCY-

3757

ASTA:

Channel.Securit

y.Error starting

monitors

The performance monitors in the administrator report a

Channel.Security.Error when accessed by a client in a

different domain than the node is running.

There is no work-around for this issue.

This wil be resolved in a future release.

FLUENCY-

4569

ASTA: The BE-

X administrator

is not rebranded

The BE-X Administrator was not rebranded. It still

references ActiveSpaces Transactions.

This will be corrected in a future release.


























FLUENCY-

271

ASTA: apache

processes not

stopped when

remove switch

used

Stopping a domain manager node using switchadmin

remove switch does not stop the Apache server processes.

The work-around is to use switchadmin stop switch before

switchadmin remove switch, or to manually kill the Apache

server processes.

This will be resolved in a future release.

FLUENCY-

619

ASTA: domain

manager node

running ASTA

can be

stopped/remove

d

It is possible to stop/remove the Domain Manager node that

runs the ActiveSpacesÂ® Transactions Administrator. If this

happens the web client becomes non-responsive. The

Domain Manager node should not be stopped using

ActiveSpacesÂ® Transactions Administrator.

The workaround is to restart the Domain Manager node if

this happens.

Stopping the Domain Manager node using ActiveSpacesÂ®

Transactions Administrator will be prevented in a future

release.

FLUENCY-

3408

ASTA: numeric

and data

columns in

tables not sorted

correctly

Tables displaying numeric and date data are not sorted

correctly. They are currently sorted in character sort order.

There is no work around for this issue.


FLUENCY-

4930

ASTA: print

statistics not

working

The Print button on the node Statistics tab does not work.



FLUENCY-

3956

ASTA:

reset/delete

buttons handled

incorrectly

following drag

& drop

Changing the order of items in dialog boxes that support drag

& drop does not managed the reset and delete button states

correctly. The reset button is not enabled, and in some cases

the delete button is incorrectly enabled.

The work-around is to close and re-open the dialog.

This issue will be resolved in a future release.

FLUENCY-

3382

ASTA: support

multi-master

merge

There is no support for resolving a multi-master scenario

from ActiveSpacesÂ® Transactions Administrator.

The work-around is to use the administrator command line.










































FLUENCY-

5877

BUILDER:

command-line

tool requires

running X server

The builder command-line tool and WebStudio server

require that an X server be running when deployed on Linux.

If you run builder, or attempt to build an EAR from

WebStudio when there is no X server running and the

DISPLAY environment variable is not set you receive the

following error: [INFO] !ENTRY org.eclipse.core.jobs 4 2 2013-07-

07 09:20:48.376

[INFO] !MESSAGE An internal error occurred

during: "Building workspace".

[INFO] !STACK 0

[INFO] org.eclipse.swt.SWTError: No more handles

[gtk_init_check() failed]

[INFO] at

org.eclipse.swt.SWT.error(SWT.java:4308)

[INFO] at

org.eclipse.swt.widgets.Display.createDisplay(Dis

play.java:909)

[INFO] at

org.eclipse.swt.widgets.Display.create(Display.ja

va:897)

[INFO] at

org.eclipse.swt.graphics.Device.<init>(Device.jav

a:157)

[INFO] at

org.eclipse.swt.widgets.Display.<init>(Display.ja

va:500)

[INFO] at

org.eclipse.swt.widgets.Display.<init>(Display.ja

va:491)

[INFO] at

org.eclipse.swt.widgets.Display.getDefault(Displa

y.java:1681)

[INFO] at

com.tibco.cep.studio.ui.validation.PostValidation

Listener.refresh(Unknown Source)

[INFO] at

com.tibco.cep.studio.ui.validation.PostValidation

Listener.resourceChanged(Unknown Source)

[INFO] at

org.eclipse.core.internal.events.NotificationMana

ger$1.run(NotificationManager.java:291)

[INFO] at

org.eclipse.core.runtime.SafeRunner.run(SafeRunne

r.java:42)

[INFO] at


ger.notify(NotificationManager.java:285)

[INFO] at


ger.broadcastChanges(NotificationManager.java:149

)

[INFO] at







org.eclipse.core.internal.resources.Workspace.bro

adcastPostChange(Workspace.java:395)

[INFO] at

org.eclipse.core.internal.resources.Workspace.end

Operation(Workspace.java:1530)

[INFO] at

org.eclipse.core.internal.events.AutoBuildJob.doB

uild(AutoBuildJob.java:156)

[INFO] at

org.eclipse.core.internal.events.AutoBuildJob.run

(AutoBuildJob.java:241)

[INFO] at

org.eclipse.core.internal.jobs.Worker.run(Worker.

java:54)

If you execute builder or build an EAR from WebStudio

when DISPLAY is set in your environment, but an X server

is not running then you receive an error like the following:

X connection to localhost:10.0 broken (explicit

kill or server shutdown).

The work-around is to run an X server when executing

builder commands or building an EAR in WebStudio on

Linux.


FLUENCY-

6078

BUILDER:

duplicate

warnings when

generating EAR

Duplicate entry messages are received when generating an

EAR with builder. For example: [INFO] !ENTRY com.tibco.cep.studio.core 1 0 2013-

09-16 09:11:00.377

[INFO] !MESSAGE Duplicate entry:pom.xml

[INFO]

[INFO] !ENTRY com.tibco.cep.studio.core 1 0 2013-

09-16 09:11:00.379

[INFO] !MESSAGE Duplicate

entry:Concepts/ConceptA01.concept

These warnings can be safely ignored.

The warnings will be fixed in a future release.

FLUENCY-

6215

BUILDER: help

fails when run

from home

directory

Running builder help from a home directory will fail with

this error message: ERROR: Invalid workspace directory:

/import/home/mallen/.builder. The workspace

cannot be inside the project directory

/import/home/user.

The work-around is to run the help command from a













different directory.


FLUENCY-

4567

CATALOG:

Line number not

provided in

catalog function

markers

The catalog function problem markers are missing the line

number.



FLUENCY-

4574

CATALOG:

Unsupported

built-in

functions

shipped

These built-in functions are shipped, but they are not

supported and do not work.

ActiveSpaces

BusinessWorks

Hawk

Standard --> Cluster

Standard --> Temporal

Standard --> VRF

Do not use these functions in your models.

These functions will be removed in a future release.

FLUENCY-

6165

CATALOG:

Using parameter

of

com.tibco.xp.ru

ntime.Concept

fails to compile

Using a parameter of type of com.tibco.xp.runtime.Concept

to a catalog function generates invalid code. For example: import com.tibco.xp.runtime.Concept;

import com.tibco.xp.studio.annotation.Function;

public class ConceptDisposer extends

TransactionNotifier

{

...

/**

* Schedule a concept for deletion at the end

of the transaction

* @param aConcept Concept to delete

*/

@Function(cautions = "A read or write lock

must be held on aConcept")

public static void dispose(final Concept

aConcept)

{

new ConceptDisposer(aConcept);

}

}

The work-around is to declare the parameter as

com.tibco.xp.runtime.Entity instead. For example:

import com.tibco.xp.runtime.Entity;

import com.tibco.xp.studio.annotation.Function;























public class ConceptDisposer extends

TransactionNotifier

{

...

/**

* Schedule a concept for deletion at the end

of the transaction

* @param aConcept Concept to delete

*/

@Function(cautions = "A read or write lock

must be held on aConcept")

public static void dispose(final Entity

aConcept)

{

new ConceptDisposer(aConcept);

}

}


FLUENCY-

6273

CLASSLOADE

R: DataError

with anonymous

class

implementation

as distributed

POJO method

param.

Using an anonymous class as a parameter to a distributed

method call will fail with an exception like this: A] com.kabira.platform.DataError: Error packing

serialized data.

[A] at

com.kabira.platform.Any.serializeObject(Any.java:

231)

[A] at

com.kabira.platform.AnyBuffer.writeSerializableSt

ream(AnyBuffer.java:381)

[A] at

com.kabira.platform.AnyBuffer.writeObject(AnyBuff

er.java:319)

[A] at

com.kabira.platform.AnyBuffer.writeJavaObject(Any

Buffer.java:337)

[A] at

anontest.AnonTest$Target.invokeCommand(AnonTest.j

ava)

[A] at

anontest.AnonTest$2.run(AnonTest.java:69)

[A] at

com.kabira.platform.Transaction.execute(Transacti

on.java:457)

[A] at


on.java:510)

[A] at

anontest.AnonTest.runTest(AnonTest.java:58)

[A] at

anontest.AnonTest.main(AnonTest.java:26)

[A] at

sun.reflect.NativeMethodAccessorImpl.invoke0(Nati

ve Method)

[A] at

sun.reflect.NativeMethodAccessorImpl.invoke(Unkno











wn Source)

[A] at

sun.reflect.DelegatingMethodAccessorImpl.invoke(U

nknown Source)

[A] at java.lang.reflect.Method.invoke(Unknown

Source)

[A] at

com.kabira.platform.MainWrapper.invokeMain(MainWr

apper.java:65)

[A] Caused by: java.io.NotSerializableException:

anontest.AnonTest$2

[A] at

java.io.ObjectOutputStream.writeObject0(Unknown

Source)

[A] at

java.io.ObjectOutputStream.defaultWriteFields(Unk

nown Source)

[A] at

java.io.ObjectOutputStream.writeSerialData(Unknow

n Source)

[A] at

java.io.ObjectOutputStream.writeOrdinaryObject(Un

known Source)

[A] at

java.io.ObjectOutputStream.writeObject0(Unknown

Source)

[A] at

java.io.ObjectOutputStream.writeObject(Unknown

Source)

[A] at

com.kabira.platform.Any.serializeObject(Any.java:

227)

The work-around for this issue is to use a concrete class

instead.


FLUENCY-

4537

CLASSLOADE

R: autoboxing

and valueof

ClassCastExcept

ion

Using valueOf to update an item in an array of Long in a

Managed Object fails with a ClassCastException. For

example, this snippet fails with:

java.lang.ClassCastException: [J cannot be cast to

[Ljava.lang.Long;

import com.kabira.platform.Transaction;

import com.kabira.platform.annotation.Managed;

public class Bug

{

public static void main(String[] args)

{

new Transaction()

{

public void run()








{

Unhappy clown = new Unhappy();

System.out.println(clown.longs[0]);

}

}.execute();

}

@Managed

static class Unhappy

{

Long longs[] = new Long[1];

Unhappy()

{

longs[0] = Long.valueOf(42);

}

}



FLUENCY-

542

CLASSLOADE

R: can't store a

null reference in

a Java String

array

Arrays of strings in a ManagedObject store a null as an

empty string.

For example, the following assert will fail.

public class StringHolder extends ManagedObject

{

String[] m_string;

void foo()

{

m_string = new String[10];

assert( m_string[0] == null );

//

// m_string[0] will return a valid string

of length 0

//

}

}

This problem will be corrected in a future release.

FLUENCY-

544

CLASSLOADE

R: can't store a

null reference in

a Java enum

array

Arrays of enums stored in a ManagedObject store a null as

the first value in the enum declaration.

For example, the following assert will fail.

enum Relic { BELL, BOOK, CANDLE };

class Holder extends ManagedObject

{

Relic[] m_relic;

void foo()

{

m_relic = new Relic[10];















assert( m_relic[0] == null );

// m_relic[0] is actually set to BELL

}

}

This problem will be corrected in a future release.

FLUENCY-

1129

CLASSLOADE

R: inherited

fields used in

keys are not

audited for

"final"

An inherited field used in a Java key will not be audited for

"final"-ness.

For instance, the following should not be legal:

public class A {

int i;

}

@Managed

@Key(name ="test", fields = {"i"})

public class B extends A { }

FLUENCY-7

CLASSLOADE

R:

java.lang.Illegal

StateException:

recursive

invocation

Attempting to integrate the NetBeans profiler with Fluency

causes this fatal exception: [primary] Profiler Agent: Initializing...

[primary] Profiler Agent: Options:

>/opt/kabira/run/fluency-dev/deploy/profiler-

server-linuxamd64/lib,5140<

[primary] Profiler Agent: Initialized succesfully

[primary] Error occurred during initialization of

VM

[primary] java.lang.IllegalStateException:

recursive invocation

[primary] at

java.lang.ClassLoader.initSystemClassLoader(Class

Loader.java:1303)

[primary] at

java.lang.ClassLoader.getSystemClassLoader(ClassL

oader.java:1286)

[primary] at

java.lang.ClassLoader.defineClass1(Native Method)

[primary] at

java.lang.ClassLoader.defineClass(ClassLoader.jav

a:620)

[primary] at

java.security.SecureClassLoader.defineClass(Secur

eClassLoader.java:124)

[primary] at

java.net.URLClassLoader.defineClass(URLClassLoade

r.java:260)

[primary] at

java.net.URLClassLoader.access$000(URLClassLoader

.java:56)

[primary] at

java.net.URLClassLoader$1.run(URLClassLoader.java

:195)

[primary] at

java.security.AccessController.doPrivileged(Nativ

e Method)
















[primary] at

java.net.URLClassLoader.findClass(URLClassLoader.

java:188)

[primary] at

java.lang.ClassLoader.loadClass(ClassLoader.java:

306)

[primary] at

sun.misc.Launcher$AppClassLoader.loadClass(Launch

er.java:276)

[primary] at

java.lang.ClassLoader.loadClass(ClassLoader.java:

251)

[primary] at

java.lang.ClassLoader.loadClassInternal(ClassLoad

er.java:319)

[primary] at java.lang.Class.forName0(Native

Method)

[primary] at

java.lang.Class.forName(Class.java:247)

[primary] at

java.lang.SystemClassLoaderAction.run(ClassLoader

.java:2015)

[primary] at

java.security.AccessController.doPrivileged(Nativ

e Method)

[primary] at

java.lang.ClassLoader.initSystemClassLoader(Class

Loader.java:1311)

[primary] at

java.lang.ClassLoader.getSystemClassLoader(ClassL

oader.java:1286)

[primary]

[primary] Current thread is 139832737576688

[primary] Dumping core ...

[primary] Caught fatal signal 6 (Aborted)

[primary] utl_dump_stack: Start of stack trace

for pid 10825

There is no work-around for this failure.

This issue appears to be a NetBeans profiler issue.

FLUENCY-

5593

CLASSLOADE

R: methods

inherited from

non-managed

base classes not

distributed

Methods inherited from non-managed types are not correctly

invoked on remote nodes if it is a distributed object.

The work-around is to override all of the parent types

methods and just invoke them via super in the child type.

This may be resolved in a future release.

FLUENCY-

5477

CODEGEN:

changing a

parent's key(s)

or field(s)

If a parent concept's keys or fields are changed, any classes

generated for child concepts will have undetected

compilation failures. The undetected compilation failures can

cause runtime deployment errors.















causes child

compilation

errors The work-around is to perform a project clean when

changing concepts with children.


FLUENCY-

5058

CONCEPT:

@parent always

return null

The @parent attribute on contained concepts always returns

null.



FLUENCY-

6409

CONFIG: Auto-

loading of

configuration

should ignore

files with

unknown

suffixes

During node startup, auto-loading of configuration files

occurs, which loads all configuration files in the node auto-

load configuration directories. Currently this process attempts

to load all files as configuration files, regardless of their

suffix. This can cause node startup failures.

The work-around is to ensure that only kcs files are in the

configuration auto-load directories.


FLUENCY-

3515

DATAGRID:

grid reset not

working

Resetting the data grid in the development appliance is not

working. This prevents the shape of data grid backed

managed objects from changing. When a data grid back

managed object's shape is changed, the next time the data

grid is accessed it will fail with an exception like this: [A] Java main class sandbox.Flushing.main exited

with an exception.

[A]

com.kabira.platform.ResourceUnavailableException:

Error occurred defining space for type

[sandbox.MyDataGridObject]. Error

[TIBAS_SYS_ERROR (space_def_mismatch -

space_name=sandbox_MyDataGridObject)].

[A] at

com.kabira.platform.Transaction.prepare(Native

Method)

[A] at


on.java:304)

[A] at sandbox.Flushing.main(Flushing.java:29)

[A] at


ve Method)

[A] at

sun.reflect.NativeMethodAccessorImpl.invoke(Nativ

eMethodAccessorImpl.java:39)

[A] at

sun.reflect.DelegatingMethodAccessorImpl.invoke(D























elegatingMethodAccessorImpl.java:25)

[A] at

java.lang.reflect.Method.invoke(Method.java:597)

[A] at


apper.java:49)

The only work-around for this issue is to restart the

Development Appliance


FLUENCY-

3678

DATAGRID:

Crash during

JProfiler startup

Attaching JProfiler 6.2.4 to a running AST JVM caused a

SEGV crash due to a library symbol conflict between

JProfiler and DataGrid.


A future release of JProfiler (version 6.2.5) will contain a fix

for this issue.

FLUENCY-

5013

DATAGRID:

Exception

com.tibco.as.spa

ce.ASException:

INVALID_OBJ

ECT

(metaspace_inva

lid) during jvm

termination.

Intermittent data grid errors are seen when shutting down a

node. They look something like: 2012-09-14 15:14:31.567 [

shutdown-hook-job] INFO

runtime.cluster.om.daoprovider - Disconnecting

from metaspace

2012-09-14 15:14:32.050 [y3uk-

policy3uk.0.$smtimeouts.CachePoller] DEBUG

runtime.service - CACHEPOLLER : policy3uk-

policy3uk.0.$smtimeouts.CachePoller, Polling...

0, <= 1347632072050

2012-09-14 15:14:32.074 [y3uk-

policy3uk.0.$smtimeouts.CachePoller] ERROR

root - java.lang.RuntimeException:

com.tibco.as.space.ASException: INVALID_OBJECT

(metaspace_invalid)

2012-09-14 15:14:32.074 [y3uk-


root - at

com.tibco.cep.runtime.service.rmi.RemoteFilterRun

ner.invoke(SourceFile:116)

2012-09-14 15:14:32.074 [y3uk-


root - at


ner.entrySet(SourceFile:46)

2012-09-14 15:14:32.074 [y3uk-


root - at

com.tibco.cep.runtime.service.dao.impl.tibas.ASCo

ntrolDao.entrySet(SourceFile:481)

2012-09-14 15:14:32.074 [y3uk-


















root - at

com.tibco.cep.runtime.service.cluster.scheduler.i

mpl.DefaultCachePoller.getExpiredKeys(DefaultCach

ePoller.java:111)

2012-09-14 15:14:32.074 [y3uk-


root - at

com.tibco.cep.runtime.service.cluster.scheduler.i

mpl.DefaultCachePoller.run(DefaultCachePoller.jav

a:82)

2012-09-14 15:14:32.074 [y3uk-


root - at

com.tibco.cep.runtime.session.BEManagedThread.exe

cute(BEManagedThread.java:458)

2012-09-14 15:14:32.089 [y3uk-


root - at

com.tibco.cep.runtime.session.BEManagedThread.run

_repeating(BEManagedThread.java:436)

2012-09-14 15:14:32.089 [y3uk-


root - at


(BEManagedThread.java:299)

2012-09-14 15:14:32.090 [y3uk-


root - Caused by: com.tibco.as.space.ASException:

INVALID_OBJECT (metaspace_invalid)

2012-09-14 15:14:32.090 [y3uk-


root - at

Native.API_Space_InvokeMembers(ApiSpace.cpp:481)

2012-09-14 15:14:32.090 [y3uk-


root - at

Native.Java_com_tibco_as_space_impl_NativeImpl_sp

aceInvokeMembers(JRemoteService.cpp:62)

2012-09-14 15:14:32.090 [y3uk-


root - at

com.tibco.as.space.impl.NativeImpl.spaceInvokeMem

bers(Native Method)

2012-09-14 15:14:32.090 [y3uk-


root - at

com.tibco.as.space.impl.ASSpace.invokeAll(ASSpace

.java:776)

2012-09-14 15:14:32.090 [y3uk-


root - at

com.tibco.as.space.impl.ASSpace.invokeSeeders(ASS

pace.java:740)

2012-09-14 15:14:32.090 [y3uk-


root - at

com.tibco.as.space.impl.ASSpace.invokeSeeders(ASS

pace.java:734)

2012-09-14 15:14:32.094 [y3uk-


root - at

com.tibco.cep.as.kit.rmi.InvocationHelper.buildAn

dInvoke(SourceFile:140)

2012-09-14 15:14:32.094 [y3uk-


root - at


ner.invoke(SourceFile:111)

2012-09-14 15:14:32.097 [y3uk-


root - ... 7 more

2012-09-14 15:14:32.317 [

shutdown-hook-job] INFO

runtime.cluster.om.daoprovider - Disconnected

from metaspace

These errors can be ignored.


FLUENCY-

3225

DATAGRID:

cardinality for

flushable types

updated at

prepare time

Cardinality for data grid backed managed objects that are not

always cached in shared memory does not include any

objects created in the current transaction - it only returns the

cardinality for completed transactions.

There is no work-around for this inconsistency with non-data

grid backed managed objects.


FLUENCY-

3293

DATAGRID:

class load for

key restore

requires a

transaction

If the class-load action for a keyed, grid-backed type occurs

outside any transaction context, and there are instances of the

type to be restored from the data grid, a

java.lang.NoClassDefFoundError may be thrown.

This occurs as AST will automatically restore any instances

of keyed types that are found in the data grid. Currently, this

restore action requires a transaction. This restriction will be

removed in a future release.

FLUENCY-

3181

DATAGRID:

invalid query

not failing

When running a query against a space, certain illegal query

filters will not fail as expected. Specifically, a query filter

that consists of a single token will find zero elements, rather

than returning an error. An example of a such a filter would

be query space name=foo filter=abc.






















FLUENCY-

3436

DATAGRID:

spurious output

to stdout

Certain log messages from the data grid library will display

to the console, and cannot be disabled. The "member left:",

"ip_address:", and "Connected metaspace ..." messages

should be ignored. This will be corrected in a future release.

FLUENCY-

4714

DEPLOY: Error

when overriding

global variable

on the

command-line.

There is currently no documented support for overriding

global variables on the command line.

The work-around is to use a properties file to set the global

variable, and

specify the properties file on the deployment command-line

like so:

java -jar deploy.jar servicename=abc P.ear

descriptor=P.cdd -p <properties file>

Support for this feature will be added in a future release. The

final support may change the command syntax used in the

work-around described above.,

FLUENCY-

5137

DEPLOY:

application

parameters with

embedded

double quote

mishandled

Application parameters with escaped double quotes do not

get passed properly to the application. Examples: java -jar deploy.jar MyMain \"param2\"

java -jar deploy.jar MyMain param1 "this is

\"param2\""

There is no work-around to this issue.


FLUENCY-63

DEPLOY: client

fails to resolve

services on

macosx

fluency.jar fails to resolve Fluency node services running

on the server appliance hosted on Mac OS X.

The work-around is to use host names and port numbers

instead of service names.


FLUENCY-

4645

DEPLOY:

functions.catalo

g already loaded

from a different

location

warnings

When a deployed BE-X application starts up, warning

message such as this one are emitted: [A] 2012 Jun 05 07:12:45:265 GMT -7 kabira-server

Debug [main] - [root] Ignoring

:file:/opt/kabira/run/be-

x/nodes/A/deploy/resources/deploy-

1338905507192/A_bex.jar!/functions.catalog

already loaded from a different location

These warnings do not indicate an actual problem, and will

be removed in a future release.


































FLUENCY-

6438

DIST: Enabling

"sparse"

partition

performs

incorrect state

transitions.

When a partition is defined and enabled on a node that is not

the active or a replica node for the partition, incorrect

partition state transitions are sent to the other nodes in the

cluster. For example, if node D defined and enabled the

partition, these transitions are seen on the other nodes: 2014-01-20 20:38:25.983054|DST|INFO

|24973|partition.act(3383)|Remote node D

performed a state change for partition p1:

[Initial -> Replicating]

2014-01-20 20:38:25.991315|DST|INFO

|24973|partition.act(3383)|Remote node D

performed a state change for partition p1:

[Replicating -> Active]

The transition to the Replicating state is incorrect since no

object migrations occur for this case.

The work-around is to ignore this transition in partition

notifiers.

This state transition will be corrected, or possibly removed,

in a future release.

FLUENCY-

6141

DIST: Loading

StaticDiscovery

entries with self

included crashes

node.

Attempting to load a static discovery distribution

configuration that includes the local node causes a node

failure. In development builds this assertion failure is seen: csnode.cpp:2104: failed C++ assertion

'm_nodeState == NodeDiscovered ||

m_nodeState == NodeNotifyUp || m_nodeState ==

NodeNotifyDown ||

m_nodeState == NodeUp || m_nodeState == NodeDown'


This will be corrected in a future release, either by reporting

the incorrect configuration at audit time, or by supporting this

configuration.

FLUENCY-

6343

DIST: handle

distribution

configuration

with different

name than the

active

distribution

configuration

Activating a distribution configuration with a different name

than the currently active one will cause multiple

configurations to become active with indeterminate results.

For example, if the active configuration has a name of

myDistributionConfiguration:

configuration "myDistributionConfiguration"

version "1.0" type "distribution"

{

...

}


























Activating one with a name of

anotherDistributionConfiguration

configuration "anotherDistributionConfiguration"

version "2.0" type "distribution"

{

...

}

will cause the problem.

The work-around is to ensure that configuration names are

not changed between distribution configuration versions.

This issue will be resolved in a future release by auditing

against changing configuration names or supporting different

configuration names for distribution configuration.

FLUENCY-

5658

ENTITY: assert

quietly does

nothing if

already loaded

into working

memory

Asserting and event or concept if the event or concept has

already been loaded into working memory quietly does

nothing.

This behavior may change in future releases.

FLUENCY-

4597

EVENT: Cannot

load events by

extId

Loading Event instances via the following built-in functions: Event.getByExtIdByUri()

Event.getByExtId()

Fails.

The work-around is to load Event instances using "id" lookup

functions.


FLUENCY-

4564

EVENT: TTL

always from

parent

Events using inheritance always use the TTL of the parent at

the top of the inheritance hierarchy. There is no way to

override the TTL of a parent in a child Event. This behavior

is currently undocumented.

There is no work-around for this behavior.

This behavior may change in future releases.

FLUENCY-

6068

EVENT: events

not stored under

Event folder

cause assertion

Currently concepts must be contained by a folder named

Concepts and events must be contained by a folder named

Events. If this convention is not followed a runtime failure

will be reported. When running with assertions, an assertion

























like this will be reported: java.lang.AssertionError:

be.gen.Common.Timer.TimerNotification

at

com.tibco.xp.runtime.ServiceProvider.getProxyClas

sByEntityImpl(ServiceProvider.java:1101)

at

com.tibco.xp.runtime.ServiceProvider.createEntity

Proxy(ServiceProvider.java:709)

at

com.tibco.xp.runtime.EntityProxy.createEntityProx

y(EntityProxy.java:256)

at

com.tibco.xp.runtime.EntityProxy.getProxy(EntityP

roxy.java:187)

at

com.tibco.xp.runtime.Transient.updateProperties(T

ransient.java:166)

at

com.tibco.xp.runtime.Event.assertEvent(Event.java

:78)

at

com.tibco.xp.runtime.Transient.assertEvent(Transi

ent.java:80)

This restriction will be eliminated in a future release.

FLUENCY-

5807

EVENT: rule

based time

events

scheduled in

startup functions

can fire twice

Rule based timed events scheduled in startup rule functions

may fire twice if the scheduled duration is in low

milliseconds (approx. < 100 milliseconds).

The work-around is to not schedule rule based timed events

in a startup rule function.


FLUENCY-

5553

INSTALLER:

Duplicate studio

and decision

manager

executables

shipped

On Windows there are duplicate Studio and Decision

Manager icons installed installed in the Start menu. Either

can be used.


FLUENCY-

5134

INSTALLER:

BE-X cannot be

installed under

TIBCO_HOME

with BE

BusinessEvents Extreme will not work correctly if installed

into an existing TIBCO_HOME that contains

BusinessEvents.

The workaround is to always install BusinessEvents Extreme

in it's own TIBCO_HOME

This issue may be resolved in a future release.

FLUENCY- INSTALLER: If BE-X is installed where user cannot write to the


























4637 Studio missing

BE-X

customizations

if run from

install where

user cannot

write

installation area after installation, Studio launches without

BE-X customizations (title/etc says BE Extreme, but key

editor, catalog functions, behaviors, etc do not work).

There is no know work-aound for this issue.


FLUENCY-

6223

INSTALLER:

bogus WARN

while

component

installation.

Installing the Rules Management Server feature or the

Decision Manager feature into an

existing BE-X installation that contains the BE-X Studio

feature will fail.

The work-around is to always install BE-X Studio, Rules

Management Server,

and Decision Manager features together.


FLUENCY-

4577

INSTALLER:

uninstall leaves

a few BE and

AS files

After uninstalling BE-X, these directories remain: ./be/5.1/bin/be-jdbcdeploy

./be/5.1/bin/be-engine

./be/5.1/bin/be-migration

./be/5.1/studio/bin/studio-tools

./as/2.0/lib/as-common.jar

./as/2.0/lib/as-admin.jar

./as/2.0/lib/libas-tibpgm.so

./as/2.0/lib/libas-common.so

./as/2.0/lib/libas-core.so

./as/2.0/lib/libas-tibrv.so

The work-around is to manually remove these files if no

other products existing in TIBCO_HOME.


FLUENCY-

5447

JAVASERVICE

: Crash when

using "ragged"

multi-

dimensional

arrays.

Java supports multi-dimensional arrays where each

dimension has different

sized arrays: raggedArray = new byte[2][];

raggedArray[0] = new byte[2];

raggedArray[1] = new byte[8];

However, this will fail at runtime with an exception like this:

FATAL ERROR in native method: Non-array passed to

JNI array operations

at

com.kabira.platform.ManagedObject.setReference(Na

tive Method)

at MyArray.$_init_Impl(Demo.java:14)






























at MyArray.<init>(Demo.java:13)

at Demo$1.run(Demo.java:67)

at


on.java:457)

at


on.java:510)

at Demo.main(Demo.java:63)

at


ve Method)

at


wn Source)

at


nknown Source)

at

java.lang.reflect.Method.invoke(Unknown Source)

at


apper.java:65)

Node vash failed: Engine x::x with process exit

status (6) triggered

abort of node. Node must be reinstalled.

The work-around is to only use multi-dimensional arrays

with the same dimensions.


FLUENCY-84

JAVASERVICE

: Invalid

com.sun.manage

ment.jmxremote

.port number

crashes node

An invalid value to a system property when starting jconsole,

for example: Error: Invalid com.sun.management.jmxremote.port

number: 192.168.71.128:9876

Brings down the Fluency node with this message:

2008-10-09 14:36:49.629085|KVM|INFO

|10069|ktvmmgr.cpp(1241)|Creating a JVM

VM options:

-

Dcom.sun.management.jmxremote.port=192.168.71.128

:9876

-

Dcom.sun.management.jmxremote.authenticate=false

-

agentlib:jdwp=transport=dt_socket,address=16106,s

erver=y,suspend=n

-

Djava.system.class.loader=com.kabira.platform.cla

ssloader.ClassLoader

-Dkabira.engine.buildType=PRODUCTION

Class path:








/opt/kabira/kis/distrib/kabira/component/ktvm/jav

a/ktvm.jar

/opt/kabira/kis/3rdparty/generic/bcel/5.2/bcel-

5.2.jar

/opt/kabira/run/fluency-

dev/nodes/primary/classpaths/scratch_Main5

java/swbuiltin.jar

java/kis.jar

java/appstats.jar

java/event.jar

java/scheduler.jar

java/switchadmin.jar

java/logger.jar

java/diskmonitor.jar

java/ktvmadmin.jar

java/netchannel.jar

java/ha.jar

java/kdds.jar

java/ktvmnotifier.jar

Initial load classes:

com.kabira.platform.ktvmnotifier.RequestWaiter

2008-10-09 14:36:49.642968|KVM|INFO

|10069|notifiers.cpp(43)|installNotifiers called

with VMID 10069

2008-10-09

14:36:50.526578|USR|FATAL|10088|engine.cpp(73)|An

illegal call to exit() was detected in process

10069 with active engine instances. You must use

the stop() method in swbuiltin to terminate

engines.

This error will be handled without bringing the node down in

a future release.

FLUENCY-

2509

JAVASERVICE

: JVM fails to

start if given the

-showversion

JVM option

The -showversion JVM option will cause the Fluency JVM

to fail during startup.



FLUENCY-

1925

JAVASERVICE

: invalid JVM

options causes

node to crash

Invalid JVM options causes the node to crash. For example

(note duplicate -Xms options): 2010-01-21 13:21:08.162242|KVM|INFO

|31637|ktvmmgr.cpp(1655)|Creating a JVM

VM options:

-

Dcom.kabira.application.class.path=/opt/kabira/ru

n/fluency/nodes/primary/classpaths/snippets_jar3

-Xms256m

-Xms512m -

agentlib:jdwp=transport=dt_socket,address=63315,s














erver=y,suspend=n

-Dcom.kabira.application.detach=true

-

Djava.system.class.loader=com.kabira.platform.cla

ssloader.ClassLoader

-

Dcom.kabira.platform.buildType=DEVELOPMENT

-

Dcom.kabira.platform.management.port=2001

,,.

2010-01-21 13:21:08.199367|KVM|INFO

|31637|notifiers.cpp(130)|installNotifiers called

with VMID 31621

2010-01-21

13:21:08.236792|USR|FATAL|31637|engine.cpp(74)|An

illegal call to exit() was detected in process

31621 with active engine instances. You must use

the stop() method in swbuiltin to terminate

engines.

This will be handled more gracefully in future releases.

FLUENCY-

1922

JAVASERVICE

: iterative JVM

start/stop

memory leak

There is a shared memory leak of approximately 200

kilobytes, seen when JVMs are launched, stopped and then

left stopped. Some of this leak also remains even after the

JVM is removed.

This is only an issue in the development process where many

JVMs are deployed (one for each launch of the application

from the deploy tool).


FLUENCY-

5688

JAVASERVICE

:

jniutils.cpp:138:

failed C++

assertion 'env-

>ExceptionChec

k() ==

JNI_FALSE'

A fatal exception like the following can be seen when using

the debugger to examine fields in a managed object following

an exception. WARNING in native method: JNI call made with

exception pending

WARNING in native method: JNI call made with

exception pending


exception pending


exception pending


exception pending


exception pending


exception pending


exception pending


exception pending


















exception pending


exception pending

jniutils.cpp:138: failed C++ assertion 'env-

>ExceptionCheck() == JNI_FALSE'

utl_dump_stack: Start of stack trace for pid

9742, tid 9832

#0

/opt/kabira/kis/distrib/kabira/devlib/libutils_g.

so:utl_dump_stack

#1

/opt/kabira/kis/distrib/kabira/devlib/libsyssrv_g

.so:dse_bomb(char const*, char const*, int,

DSEBombType)

#2

/opt/kabira/kis/distrib/kabira/devlib/libjavaserv

ice_g.so:JNIUtil::attachProxyObject(JNIEnv_*,

_jobject*, _jfieldID*)

#3


ice_g.so:JNIUtil::getSlotData(JNIEnv_*,

_jobject*, _jfieldID*)

#4


ice_g.so:KTVM_GetByteField

#5

/opt/kabira/distrib/kis/3rdparty/linux/tibcojre/1

.7.0_09_x86_64/lib/amd64/libjdwp.so

[0x7f7018ae2739]

#6



[0x7f7018abe0ab]

#7



[0x7f7018ac9806]

#8



[0x7f7018adc3c1]

#9

/opt/kabira/kis/3rdparty/linux/tibcojre/1.7.0_09_

x86_64/lib/amd64/server/libjvm.so

[0x7f7042849ae7]

#10



[0x7f7042a880c8]

#11



[0x7f7042a88218]

#12



[0x7f7042969c00]

#13 /lib/libpthread.so.0 [0x7f70452693f7]

#14 /lib/libc.so.6:clone


exception pending

This is caused by a limitation in the debugger integration

with JNI.

There is no workaround to this issue.


FLUENCY-

5701

JAVASERVICE

: shutting down

at debugger

breakpoint

causes engine to

fail with an error

Stopping a JVM with a breakpoint set in the debugger will

cause the JVM to exit with an error that requires the node to

be removed and re-installed.

The work-around is to ensure that no break-points are set in a

debugger when shutting down a JVM.


FLUENCY-

2855

KDM: cannot

remove switch

using domain

manager

It is not possible to remove a node using the domain

manager. Attempt to do so will fail with the following error

message: switchadmin servicename=domainmanager

domainnode=replica stop switch

guest@kabira-server:~$ switchadmin

servicename=domainmanager domainnode=replica stop

remove

Invalid response data stream received from remote

node.

The work around is to execute the remove directly to the

target node without the domain manager.


FLUENCY-

2426

KDM: cannot

start node

through KDM

Attempting to start a node through KDM will fail. For

example, executing this command: switchadmin hostname=kabira-server adminport=2000

domainnode=replica username=guest password=guest

start switch

will fail with:

Invalid response data stream received from remote

node.

The work around is to send the command directly to the node




















being started, by passing KDM. For example:

switchadmin hostname=kabira-server adminport=2003

username=guest password=guest start switch

Waiting for application to start

Components started

Loading configurations

Auditing security configuration

Host: kabira-server

Administration Port: 2003

Service Name: "replica"

Node Name: "replica"


FLUENCY-

3073

KDM:

configuration

restore:

incorrect date

conversion

when timezone

offsets of -00xx

The Domain Manager's configuration cache incorrectly

converts negative timezone offsets in a node's installation

time to a positive offset. For example a node installation

timezone offset of -0030 is converted to 0030. This may

cause configuration restore to incorrectly restore, or not,

configuration to a node.



FLUENCY-

4820

KEY: key input

not enabled

when no

properties in

child Concept

When editing a child concept that inherits from a parent

concept with properties, the key editor is not enabled if there

are no properties in the child concept.

The work-around is to add a property in the child concept.

This will enable the key editor.


FLUENCY-

4595

KEY: keys with

removed

concept property

fields not

removed in

children

When a concept property field is removed, any keys in that

concept that contain that property are correctly removed.

However, any keys in children Concepts that contain that

property are not removed.

The work-around is to manually remove the keys in the

children.


FLUENCY-

4912

KEY: renaming

a Concept

property using

refactor fails

Using refactor to rename a Concept property causes a

java.lang.NullPointerException with a stack like the

following and the project is corrupted. java.lang.NullPointerException

at

com.tibco.xp.studio.codegeneration.CodeGeneration































.mapPropertyType(CodeGeneration.java:141)

at

com.tibco.xp.studio.codegeneration.ConceptCodeGen

eration.generateFunctionJavaDoc(ConceptCodeGenera

tion.java:494)

at


eration.addLookupFunctions(ConceptCodeGeneration.

java:421)

at


eration.generate(ConceptCodeGeneration.java:83)

at

com.tibco.xp.studio.codegeneration.JavaFileJob.ge

nerateCode(JavaFileJob.java:182)

at

com.tibco.xp.studio.codegeneration.UpdateJavaFile

Job.runInWorkspace(UpdateJavaFileJob.java:23)

at

org.eclipse.core.internal.resources.InternalWorks

paceJob.run(InternalWorkspaceJob.java:38)

at


java:54)

There is no workaround for this issue.


FLUENCY-

6189

LIBRARY:

build with

project library

fails with

ambiguous

reference errors

When building a project with imported project libraries there

are intermittent failures like this reported and the build fails: [INFO] ERROR: /unittest: line 112: Project

Library: Ambiguous Reference.

Reference must be qualified, as multiple elements

exist with the same name

[/Concepts/ControlData/UsageMonitoringInformation

,/Concepts/ControlData/UsageMonitoringInformation

]

The work-around is to retry the build.


FLUENCY-

6086

LIBRARY:

cannot extend

Java classes

from imported

project without

catalog

functions

Attempting to extend a concept or event from an imported

project library that does not contain any catalog functions

will fail with a java.lang.NoClassDefFoundError

exception.

The work-around is to create a dummy catalog function in

the project library that is being imported.


FLUENCY- LIBRARY: When building a project with imported project libraries there




















6238 occasional

"cannot be

resolved to a

type" errors

when build with

project libraries

are intermittent failures like this reported and the build fails: [INFO] ERROR:

/unittest/Java/com/tibco/test/DiameterRulesTest.j

ava: line 152: TestUserProfile cannot be resolved

to a type

[INFO] ERROR:

/unittest/Java/com/tibco/test/DiameterRulesTest.j

ava: line 152: The method getUserProfile(String,

LockMode)



FLUENCY-

6161

LIBRARY:

org.eclipse.core.

runtime.Assertio

nFailedExceptio

n: assertion

opening concept

from library

Attempting to open a concept in an imported project library

fails with this assertion: org.eclipse.core.runtime.AssertionFailedException

: assertion failed:

at

org.eclipse.core.runtime.Assert.isTrue(Assert.jav

a:110)

at

org.eclipse.core.runtime.Assert.isTrue(Assert.jav

a:96)

at

org.eclipse.ui.part.MultiPageEditorPart.setActive

Page(MultiPageEditorPart.java:1065)

at

org.eclipse.ui.part.MultiPageEditorPart.createPar

tControl(MultiPageEditorPart.java:352)

at

org.eclipse.ui.internal.EditorReference.createPar

tHelper(EditorReference.java:670)

at

org.eclipse.ui.internal.EditorReference.createPar

t(EditorReference.java:465)

at

org.eclipse.ui.internal.WorkbenchPartReference.ge

tPart(WorkbenchPartReference.java:595)

at

org.eclipse.ui.internal.EditorReference.getEditor

(EditorReference.java:289)

at

org.eclipse.ui.internal.WorkbenchPage.busyOpenEdi

torBatched(WorkbenchPage.java:2945)

at

org.eclipse.ui.internal.WorkbenchPage.busyOpenEdi

tor(WorkbenchPage.java:2850)

at

org.eclipse.ui.internal.WorkbenchPage.access$11(W

orkbenchPage.java:2842)

at

org.eclipse.ui.internal.WorkbenchPage$10.run(Work

benchPage.java:2793)

at

















org.eclipse.swt.custom.BusyIndicator.showWhile(Bu

syIndicator.java:70)

at

org.eclipse.ui.internal.WorkbenchPage.openEditor(

WorkbenchPage.java:2789)

at



at



at

com.tibco.cep.studio.ui.util.StudioUIUtils.openSh

aredEntity(Unknown Source)

at

com.tibco.cep.studio.ui.util.StudioUIUtils.openEl

ement(Unknown Source)

at

com.tibco.cep.studio.ui.navigator.view.ProjectExp

lorer.a(Unknown Source)

at

com.tibco.cep.studio.ui.navigator.view.ProjectExp

lorer.handleDoubleClick(Unknown Source)

at

org.eclipse.ui.navigator.CommonNavigator$5.run(Co

mmonNavigator.java:523)

at


r.java:42)

at

org.eclipse.ui.navigator.CommonNavigator$4.double

Click(CommonNavigator.java:521)

at

org.eclipse.jface.viewers.StructuredViewer$1.run(

StructuredViewer.java:845)

at


r.java:42)

at

org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil

.java:49)

at

org.eclipse.jface.util.SafeRunnable.run(SafeRunna

ble.java:175)

at

org.eclipse.jface.viewers.StructuredViewer.fireDo

ubleClick(StructuredViewer.java:843)

at

org.eclipse.jface.viewers.AbstractTreeViewer.hand

leDoubleSelect(AbstractTreeViewer.java:1462)

at

org.eclipse.ui.navigator.CommonViewer.handleDoubl

eSelect(CommonViewer.java:454)



FLUENCY-

4489

MONITOR:

Cannot display

multi-

dimensional

arrays.

The shared memory monitor does not handle java arrays with

multiple dimensions, i.e. running the following example: import com.kabira.platform.Transaction;

import com.kabira.platform.annotation.Managed;

@Managed

class Foo

{

public char[][] m_char;

Foo()

{

m_char = new char[5][5];

char val = 'a';

for (int i = 0; i < 5; i++)

{

for (int j = 0; j < 5; j++)

{

m_char[i][j] = val;

val++;

}

}

}

}

public class Demo

{

public static void main(String[] args)

{

new Transaction("Create")

{

public void run()

{

new Foo();

}

}.execute();

System.out.println("Main: done");

}

}

Then running the monitor and navigating to the foo instance

will result in a

Address out of bounds error displayed for m_char.

A workaround is to use swdiag to display the object data.


FLUENCY-

2491

NODE: display

node does not

show node

description if

MDNS not

running

switchadmin display switch and Kabira Manager do not

include the node description if service discovery is not

running.

With MDNS running here is the output from display switch.

switchadmin adminport=2001 display switch
















Node administration for primary:

Host: localhost


Service Name: "primary"

Node Name: "primary"

Engine fluency::fluency

State: running

Build type: DEVELOPMENT

Contains JVM: No

Principals: guest

Active Principal: guest

Application: kabira/fluency

Node Path: /opt/kabira/run/fluency/nodes/primary

Installation Path: /opt/kabira/kis

Node Description: Fluency Development

Here is the output without MDNS running.

switchadmin adminport=2001 display switch

Node administration for primary:

Host: localhost


Service Name: "None"

Node Name: "primary"

Engine fluency::fluency

State: running

Build type: DEVELOPMENT

Contains JVM: No

Principals: guest

Active Principal: guest

Application: kabira/fluency

Node Path: /opt/kabira/run/fluency/nodes/primary

Installation Path: /opt/kabira/kis

There is not work-around for this issue.


FLUENCY-

4578

QUERY:

generated query

functions should

be Ontology

functions

Query functions are currently classified as Custom

Functions. They should be classified as Ontology

Functions.

This classification will change in a future release.

FLUENCY-

6332

QUERY: lock

mode of none

takes read lock

Specifying a lock mode of none to the query catalog

functions takes a read lock on the returned object. For

example thsi query

Employee.lookupEmployee_ByEmpId("none","1234"); will read-lock the returned *Employee*object.















FLUENCY-

6218

QUERY: lookup

of a concept

created in same

RTC fails

Attempting to lookup a concept that was created in the same

RTC will fail. For example: rule Rules.Work {

attribute {

priority = 5;

forwardChain = true;

}

declare {

Events.DoIt doIt;

}

when {

}

then {

Concepts.Value value =

Concepts.Value.Value("", "SameRtc");

value = Value.lookupByName("none",

"SameRtc"); // FIX THIS -: Will return null

System.debugOut("INFO: Work Value

is " + value);

}

}

The work-around is to call a catalog function with the newly

created concept as a parameter to force the concept to be

created in shared memory.


FLUENCY-

5287

QUERY: update

in RTC lost if

concepts

reloaded via a

query

Updates to a concept in an RTC are lost if the concept is

reloaded via a query in the same RTC.

The work-around is to flush the concept updates to shared

memory by calling a catalog function with the concept as a

parameter before doing the query.

This may be corrected in a future release. However, it is

recommended that applications do not load a concept into

working memory multiple times in an RTC to avoid the

performance impact of loading a concept into working

memory.

FLUENCY-

4474

RT: Creating

key'd instances

via reflection

fails.

Attempting to create a managed object with keys defined

using reflection fails with a duplicate key exception.



FLUENCY-

4889

RULE:

modifications of

Modification of key fields in a Concept should be disallowed

in the rule editor. However, they currently are not. For
























key fields

allowed in rule

editor

example if firstName is a key, the following should report an

error: declare {

Concepts.Customer c;

}

//...

then {

c.firstname = "John";

}

It currently doesn't.


FLUENCY-

5654

RUNTIME:

Attempting to

lock cluster

failure

If a startup rule function does not complete, other nodes that

are started will fail to startup and they will continuously

report Attempting to lock the cluster, retrying.

The work-around is to ensure that startup rule functions

complete in a timely fashion.


FLUENCY-

6484

RUNTIME:

Instance.deleteI

nstance

followed by

create concept

causes duplicate

key in same

RTC

Deleting a keyed concept using Instance.deleteInstance and

recreating the concept in the same RTC using the same key

will fail with a duplicate key exception. This error occurs

because the delete is not flushed to shared memory until the

end of the RTC.

The work-around is to use a catalog function and called

ManagedObject.delete on the concept being deleted.


FLUENCY-

6151

RUNTIME:

Logging cannot

be disabled in

the CDD

Disabling logging in the CDD does not disable the logging at

runtime.

The work-around is to set <roles>user:off</roles> in the

CDD. For example:

<log-configs>

<log-config id="logConfig">

<enabled>false</enabled>

<roles>user:off</roles>

<files>

<enabled>true</enabled>

<dir>logs</dir>

<name/>

<max-number>10</max-number>

<max-size>5000000</max-size>

<append>true</append>

</files>


























<terminal>

<enabled/>

<sys-out-redirect>false</sys-out-

redirect>

<sys-err-redirect>false</sys-err-

redirect>

<encoding/>

</terminal>

<line-layout>

<enabled>false</enabled>

<class/>

<arg/>

</line-layout>

</log-config>

</log-configs>


FLUENCY-

6065

RUNTIME:

Object Not

Found when ttl

fires on replica

node for HA

event

A highly available event created in rules language and then

asserted in Java to execute on a remote node causes an

exception similar to the one below if the event is deleted on

the remote node: java.lang.NullPointerException: Object not found

on remote node B for object

771399:1581472:2777730007624:61, operation

com.tibco.xp.runtime.NonTransient.$toStringImpl()

Ljava/lang/String;.

at

com.kabira.platform.ManagedObject._sendTwoWay(Nat

ive Method)

at

com.kabira.platform.ManagedObject.sendTwoWay(Mana

gedObject.java:393)

at

com.tibco.xp.runtime.NonTransient.toString(NonTra

nsient.java)

at java.lang.String.valueOf(Unknown

Source)

at java.lang.StringBuilder.append(Unknown

Source)

at

com.tibco.xp.runtime.TransactionService$TTLTimer.

$timerNotifyImpl(TransactionService.java:534)

at

com.tibco.xp.runtime.TransactionService$TTLTimer.

timerNotify(TransactionService.java)

[ java stack end ]'

osobjsrv.cpp (445): RETHROW

DSEBuiltin::ExceptionInvalidHandle

cgobjex.cpp (55): RETHROW


swtimer_stb0.cpp (1005): RETHROW
















swtimer_mimpl0.cpp (1227): RETHROW


swtimer_mimpl0.cpp (1229): RETHROW


swtimer_skl0.cpp (1092): RETHROW


osdisp.cpp (1249): DUMP


+++ END +++

This exception can be ignored. It does not cause any

functional problems.

This will be fixed in a future release.

FLUENCY-

6240

RUNTIME:

RejectedExecuti

onException on

node restart

An intermittent exception is seen when deploying an

application: 2013-11-07 12:57:11.531 [ main]

FATAL container.standalone - Task

java.util.concurrent.ScheduledThreadPoolExecutor$

ScheduledFutureTask@27b310e0 rejected from

java.util.concurrent.ScheduledThreadPoolExecutor@

5d18f67c[Terminated, pool size = 0, active

threads = 0, queued tasks = 0, completed tasks =

0]

java.util.concurrent.RejectedExecutionException:

Task

java.util.concurrent.ScheduledThreadPoolExecutor$

ScheduledFutureTask@27b310e0 rejected from

java.util.concurrent.ScheduledThreadPoolExecutor@

5d18f67c[Terminated, pool size = 0, active

threads = 0, queued tasks = 0, completed tasks =

0]

at

java.util.concurrent.ThreadPoolExecutor$AbortPoli

cy.rejectedExecution(Unknown Source)

at

java.util.concurrent.ThreadPoolExecutor.reject(Un

known Source)

at

java.util.concurrent.ScheduledThreadPoolExecutor.

delayedExecute(Unknown Source)

at

java.util.concurrent.ScheduledThreadPoolExecutor.

schedule(Unknown Source)

at

com.tibco.cep.runtime.management.impl.metrics.Asy

ncWorkerDataPublisher.init(AsyncWorkerDataPublish

er.java:52)

at

com.tibco.cep.runtime.management.impl.DefaultMana

gementCentral.onNotify(DefaultManagementCentral.j







ava:185)

at

com.tibco.cep.runtime.service.basic.DependencyWat

cher.notifyDependents(DependencyWatcher.java:71)

at

com.tibco.cep.runtime.session.impl.RuleServicePro

viderImpl.registerDomains(RuleServiceProviderImpl

.java:887)

at


viderImpl.initCluster(RuleServiceProviderImpl.jav

a:744)

at


viderImpl.configure(RuleServiceProviderImpl.java:

260)

at

com.tibco.cep.container.standalone.BEMain.jumpSta

rt(SourceFile:151)

at

com.tibco.cep.container.standalone.BEMain.main(So

urceFile:69)

at


ve Method)

at


wn Source)

at


nknown Source)

at

java.lang.reflect.Method.invoke(Unknown Source)

at

com.tibco.xp.earhandler.MainWrapper.run(MainWrapp

er.java:38)

This exception prevents the application from starting.

The only work-around is to redeploy the application.


FLUENCY-

6062

RUNTIME:

UTF-16 XML

payloads not

working

Creating an Event using an XML payload that uses UTF-16

is not handling correctly.

The work-around is to use UTF-8.


FLUENCY-

6450

RUNTIME:

circular concept

references cause

stack-overflow

A circular concept reference (A.b <--> B.a) between two

concepts will cause a runtime failure due to a stack overflow.















FLUENCY-

5677

RUNTIME:

delete skipped if

created concept

flushed to

shared memory

via catalog

function

The following will cause a concept to fail to be deleted from

shared memory.

1. Create a concept in a rule

2. Flush the concept to shared memory by calling a

catalog function in a separate rule in the same RTC.

3. Delete concept in a rule in the same RTC

The work-around is to avoid this code path, or to explicitly

delete the concept using a catalog function.


FLUENCY-

6219

RUNTIME:

delete skipped in

RTCs triggered

using

Concept.assertC

oncept from

Java

Deleting a concept using Instance.deleteInstance in an RTC

that was triggered using Concept.assertConcept or

Concept.assertConceptWithoutRunToCompletion fails to

delete the concept.

The work-around is to trigger the RTC with an event and use

Concept.load instead, or to call a catalog function and delete

the concept using ManagedObject.delete


FLUENCY-

5091

RUNTIME:

duplicate keys

not reported

when using

Ontology

constructor

Duplicate key exceptions are not returned to the rule or rule

function that caused the exception.



FLUENCY-

6072

RUNTIME:

lookup or

cardinality fail

for concepts

created in same

RTC

The lookup of concepts created in the same RTC will fail to

find the created concept. Calling

ManagedObject.cardinality from Java in a catalog function

will not include any concepts created in the RTC.

The work-around is to create the concept from Java using a

catalog function, or to flush the concept to shared memory by

calling a catalog function with the newly created concept as a

parameter. For example:

/**

* Flush value to shared memory

* @param value Value to flush



































*/

@Function

public static void flush(Value value) { };


FLUENCY-

5873

RUNTIME: no

active

transaction

when using a

work manager

Using a work manager to schedule asynchronous non-

transient events causes an exception like the following: 2013 Jul 03 17:27:07:178 GMT -7 kabira-server

None [main] - [runtime.session] BE Engine kabira-

server started

java.lang.RuntimeException: Quorum seems to be

ok. Operation will be aborted as quorum does not

seem to be the problem.

at

com.tibco.cep.runtime.service.cluster.om.DefaultD

istributedCacheBasedStore.handleException(Default

DistributedCacheBasedStore.java:1659)

at


istributedCacheBasedStore.applyChanges(DefaultDis

tributedCacheBasedStore.java:1085)

at

com.tibco.cep.kernel.core.base.WorkingMemoryImpl.

processRecorded(SourceFile:370)

at

com.tibco.cep.kernel.core.rete.ReteWM.assertObjec

t(SourceFile:1653)

at

com.tibco.cep.runtime.session.impl.RuleSessionImp

l.assertObject(RuleSessionImpl.java:1367)

at

com.tibco.be.functions.engine.EngineFunctions$Ass

ertEventAsyncTask.run(SourceFile:649)

at

java.util.concurrent.ThreadPoolExecutor.runWorker

(Unknown Source)

at

java.util.concurrent.ThreadPoolExecutor$Worker.ru

n(Unknown Source)

at

com.tibco.cep.runtime.util.CustomBEManagedThread.

run(CustomBEManagedThread.java:24)

Caused by: java.lang.RuntimeException:

createEntityProxy: Failed to create proxy object

asyncevent.managed.events.DoItProxy.

at



at

com.tibco.xp.runtime.ServiceProvider.createObject

FromHandle(ServiceProvider.java:826)

at

com.tibco.xp.runtime.ServiceProvider.doCreate(Ser

viceProvider.java:399)

at








com.tibco.xp.runtime.ServiceProvider.insert(Servi

ceProvider.java:287)

at

com.tibco.xp.runtime.TransactionService.insert(Tr

ansactionService.java:38)

at

com.tibco.cep.runtime.model.element.impl.ManagedO

bjectManager.insert(ManagedObjectManager.java:165

)

at

com.tibco.cep.runtime.service.cluster.txn.RtcTran

sactionManager.txnToMom(RtcTransactionManager.jav

a:374)

at


sactionManager.applyTransactionToCache(RtcTransac

tionManager.java:330)

at


sactionManager.applyTransaction(RtcTransactionMan

ager.java:512)

at


sactionManager.publish(RtcTransactionManager.java

:180)

at

com.tibco.cep.runtime.service.cluster.agent.Infer

enceAgent.applyChanges(InferenceAgent.java:2387)

at


istributedCacheBasedStore.applyChanges(DefaultDis

tributedCacheBasedStore.java:1083)

... 7 more

Caused by:

java.lang.reflect.InvocationTargetException

at

sun.reflect.NativeConstructorAccessorImpl.newInst

ance0(Native Method)

at

sun.reflect.NativeConstructorAccessorImpl.newInst

ance(Unknown Source)

at

sun.reflect.DelegatingConstructorAccessorImpl.new

Instance(Unknown Source)

at

java.lang.reflect.Constructor.newInstance(Unknown

Source)

at



... 18 more

Caused by: java.lang.IllegalAccessError: no

active transaction

at

com.kabira.platform.ManagedObject.createSMObject(

Native Method)

at

com.tibco.xp.runtime.NonTransient.<init>(NonTrans

ient.java:48)

at

asyncevent.managed.events.DoIt.<init>(DoIt.java:3

2)

at

asyncevent.managed.events.DoItProxy.<init>(DoItPr

oxy.java:36)

... 23 more

The same thing happens if concepts are created/modified in

rules triggered by the asynchronous event (both transient and

non-transient).



FLUENCY-

5478

SCORECARD:

add support for

scorecards

Scorecards are not supported in this release, however, they

can be created in Studio.


Scorecards will either be supported, or removed from Studio,

in a future release.

FLUENCY-

3859

STATISTICS:

object update

latency does not

include

partitioned

objects

The object update latency reported for distributed and

partitioned objects does not include the network latency.



FLUENCY-

6126

STUDIO: Build

Path dialog

obsolete

The Build Path dialog should not be used to add project

libraries or catalog functions to a project. The standard Java

Build Path dialog should be used instead.

The Build Path dialog will be removed in a future release.

FLUENCY-

5867

STUDIO: Could

not delete jar

file error when

building project

on Windows

This exception stack may be seen when building and cleaning

projects on Windows: !ENTRY org.eclipse.jdt.core 4 4 2013-07-02

13:31:25.522

!MESSAGE JavaBuilder handling

ImageBuilderInternalException while building:

Simple

!STACK 1

org.eclipse.core.internal.resources.ResourceExcep

tion: Problems encountered while deleting

resources.

at

org.eclipse.core.internal.resources.Resource.dele


























te(Resource.java:793)

at

org.eclipse.jdt.internal.core.builder.BatchImageB

uilder.cleanOutputFolders(BatchImageBuilder.java:

114)

at


uilder.build(BatchImageBuilder.java:46)

at

org.eclipse.jdt.internal.core.builder.JavaBuilder

.buildAll(JavaBuilder.java:254)

at


.build(JavaBuilder.java:173)

at

org.eclipse.core.internal.events.BuildManager$2.r

un(BuildManager.java:728)

at


r.java:42)

at

org.eclipse.core.internal.events.BuildManager.bas

icBuild(BuildManager.java:199)

at



at



at


r.java:42)

at



at


icBuildLoop(BuildManager.java:351)

at

org.eclipse.core.internal.events.BuildManager.bui

ld(BuildManager.java:374)

at



at



at


java:54)

Contains: Could not delete

'C:\Users\mallen\work\workspaces\bex-110-projlib-

buildpath\Simple\bin\Simple_bex7.jar'.

org.eclipse.core.runtime.CoreException: Problems

encountered while deleting files.

at

org.eclipse.core.internal.filesystem.local.LocalF

ile.delete(LocalFile.java:125)

at

org.eclipse.core.internal.resources.ResourceTree.

internalDeleteFile(ResourceTree.java:304)

at

org.eclipse.core.internal.resources.ResourceTree.

standardDeleteFile(ResourceTree.java:785)

at

org.eclipse.core.internal.resources.Resource.unpr

otectedDelete(Resource.java:1937)

at

org.eclipse.core.internal.resources.Resource.dele

te(Resource.java:780)

at


uilder.cleanOutputFolders(BatchImageBuilder.java:

114)

at


uilder.build(BatchImageBuilder.java:46)

at


.buildAll(JavaBuilder.java:254)

at


.build(JavaBuilder.java:173)

at



at


r.java:42)

at



at



at



at


r.java:42)

at



at


icBuildLoop(BuildManager.java:351)

at

org.eclipse.core.internal.events.BuildManager.bui

ld(BuildManager.java:374)

at



at



at


java:54)

This exception can be ignored. It has not impact on the

success of the build or clean.


FLUENCY-

5050

STUDIO: EAR

not updated if

only Java code

changes

An updated EAR is not generated is only Java code changed

in the project.

The work-around is to manually remove the EAR before

building a new one.


FLUENCY-

5452

STUDIO: EARs

can be built

while code

generation is

still in progress

EARs can currently be built before all build processes

complete. This causes corrupt EAR files to be generated.

The work-around is to ensure that all back-ground processes

are complete before building an EAR.


FLUENCY-

4979

STUDIO: EARs

can be built with

Java

compilation

errors

EARs can be built in projects that contain Java compilation

errors. This should be prohibited.

The workaround is to ensure that there are no Java

compilation errors in the project before building an EAR.

This will be correct in a future release.

FLUENCY-

4659

STUDIO:

Refactor

(rename) project

name fails

Using refactor to rename a project causes the project to

become corrupted.



FLUENCY-

4584

STUDIO:

cannot deploy

application

directly from

studio

There is currently no support for deploying BE-X

applications directly from Studio.

The work-around is to deploy applications using the BE-X

deployment tool on the command line. For example:

java -jar deploy.jar adminport=9876


































username=guest password=guest App.ear -c

deploy.cdd

This will be fixed in a future release.

FLUENCY-

5897

STUDIO:

generated code

randomly choses

from within

multiple source

folders

There is currently no support for multiple Source paths

specified on the Java Build Path.


This limitation will be removed in a future release.

FLUENCY-

6103

STUDIO: not

recognizing

build path "user"

classpath

variables

Attempting to use class path variables will cause builds to

fail with Unbound classpath variable errors.



FLUENCY-

4568

STUDIO: prints

messages to

stdout

BE-X Studio prints messages to stdout. These should not be

there.



FLUENCY-

5924

STUDIO: read-

only .classpath

results in a

bunch of stack

traces

If Studio cannot write the .classpath file in a project it will

fail with large number of exceptions like this: Caused by:

org.eclipse.core.internal.resources.ResourceExcep

tion: File /FraudDetection/.classpath is read-

only.

at

org.eclipse.core.internal.resources.Workspace.val

idateSave(Workspace.java:2670)

at

org.eclipse.core.internal.resources.File.setConte

nts(File.java:352)

at

org.eclipse.jdt.internal.core.JavaProject.setShar

edProperty(JavaProject.java:3147)

at

org.eclipse.jdt.internal.core.JavaProject.writeFi

leEntries(JavaProject.java:2902)

at

org.eclipse.jdt.internal.core.JavaModelManager$Pe

rProjectInfo.writeAndCacheClasspath(JavaModelMana

ger.java:1339)

at

org.eclipse.jdt.internal.core.JavaModelManager$Pe

rProjectInfo.writeAndCacheClasspath(JavaModelMana

ger.java:1351)

at

org.eclipse.jdt.internal.core.SetClasspathOperati




























on.executeOperation(SetClasspathOperation.java:77

)

at

org.eclipse.jdt.internal.core.JavaModelOperation.

run(JavaModelOperation.java:728)

at

org.eclipse.core.internal.resources.Workspace.run

(Workspace.java:2344)

at

org.eclipse.jdt.internal.core.JavaModelOperation.

runOperation(JavaModelOperation.java:793)

at

org.eclipse.jdt.internal.core.JavaProject.setRawC

lasspath(JavaProject.java:3093)

at



at



at

com.tibco.xp.studio.javanature.AddNature.updateCl

assPath(AddNature.java:335)

at

com.tibco.xp.studio.javanature.AddNature.add(AddN

ature.java:177)

at


.initializePackageFragment(CodeGeneration.java:49

5)

at


.getPackageFragment(CodeGeneration.java:388)

at


.getCompilationUnit(CodeGeneration.java:141)

at


eration.generate(ConceptCodeGeneration.java:49)

at

com.tibco.xp.studio.codegeneration.JavaFileJob.ge

nerateCode(JavaFileJob.java:198)

at

com.tibco.xp.studio.codegeneration.CreateJavaFile

Job.runInWorkspace(CreateJavaFileJob.java:34)

at

org.eclipse.core.internal.resources.InternalWorks

paceJob.run(InternalWorkspaceJob.java:38)

at


java:54)

The work-around is to ensure that Studio has write access to

the .classpath file in a project.


FLUENCY-

6069

STUDIO:

resource out of

sync problem on

project export

This problem may be seen exporting a project archive. Problems were encountered during export:

Error exporting Timer/bin/catalog.store:

Resource is out of sync with the file system:

'/Timer/bin/catalog.store'.

Resource is out of sync with the file system:

'/Timer/bin/catalog.store'.

This problem can be ignored. The export still succeeds.


FLUENCY-

5400

TIMER: HA

timer started in

notifier

constructor not

replicated

HA timers started in the constructor of a partitioned class

which extends

com.kabira.platform.swtimer.TimerNotifier, is not

properly replicated, and becomes lost upon fail over.

The work-around is to create the timer notifiers outside of a

constructor.


FLUENCY-

5461

USAGE: help

for scripted

plugins not

displayed

The help command on the snapshot and runtimestatistics

administration targets does not work with the domainname

parameter. For example: administrator adminport=N domainname=Development

help snapshot



FLUENCY-

5948

WEBSTUDIO:

Rule template

with SOAP

event

Generation of rule instances in Web Studio fails if the rule

uses events that inherit from SOAPEvent with an exception

like this: Exception while invoking rule function

java.lang.RuntimeException:

com.tibco.be.ws.scs.SCSException:

File path specified by

G:/BE511Home/be/5.1/examples/standard/WebStudio\T

estBESOAPSOAPEvent.event does not exist

at

com.tibco.be.ws.functions.WebstudioServerRTBuilde

rFunctions.resolveContainedEntity(SourceFile:325



FLUENCY-

6451

WEBSTUDIO:

SOAP events do

SOAP events do not work in virtual rule templates.

Attempting to use one will cause a runtime failure similar to






























not work in

virtual rule

templates

this: 2014 Jan 24 11:29:35:630 GMT -8 centaur Info

[$default.be.mt$.Worker.3] -

[WebStudio.Core.RuleFunctions.Utils.RT.Builder.Op

s.Fetch.WS_RF_CreateRuleTemplateBuilderConceptFro

mSCSFactory] [WS-Inference-class] Requested fetch

for ruletemplate builder

2014 Jan 24 11:29:35:646 GMT -8 centaur Error

[$default.be.mt$.Worker.3] - [driver.http]

Exception while invoking rule function

java.lang.RuntimeException:

com.tibco.be.ws.scs.SCSException: File path

specified by

/opt/kabira/users/leon/BEX_1.1.1/be/5.1/examples/

standard/WebStudio/RuleTemplateExampleSOAPEvent.e

vent does not exist

at


rFunctions.resolveContainedEntity(SourceFile:325)

at

be.gen.WebStudio.Core.RuleFunctions.Utils.RT.Buil

der.nullWS_RF_TraverseAndBuildSymbolHierarchy$ove

rsizeName.WS_RF_TraverseAndBuildSymbolHierarchy(n

ullWS_RF_TraverseAndBuildSymbolHierarchy$oversize

Name.java:37)

at


der.nullWS_RF_CreateBuilderSymbolHierarchy$oversi

zeName.WS_RF_CreateBuilderSymbolHierarchy(nullWS_

RF_CreateBuilderSymbolHierarchy$oversizeName.java

:31)

at


der.Ops.Fetch.WS_RF_CreateRuleTemplateBuilderConc

eptFromSCS$oversizeName.WS_RF_CreateRuleTemplateB

uilderConceptFromSCS(WS_RF_CreateRuleTemplateBuil

derConceptFromSCS$oversizeName.java:20)

at


der.Ops.Fetch.WS_RF_CreateRuleTemplateBuilderConc

eptFromSCSFactory$oversizeName.WS_RF_CreateRuleTe

mplateBuilderConceptFromSCSFactory(WS_RF_CreateRu

leTemplateBuilderConceptFromSCSFactory$oversizeNa

me.java:21)

at

be.gen.WebStudio.Core.RuleFunctions.Utils.RT.WS_R

F_CreateAbstractRuleTemplateConceptFromSCS$oversi

zeName.WS_RF_CreateAbstractRuleTemplateConceptFro

mSCS(WS_RF_CreateAbstractRuleTemplateConceptFromS

CS$oversizeName.java:22)

at

be.gen.WebStudio.Core.RuleFunctions.Actions.nullW

S_RF_FetchArtifactContentsFromStoreObjectConcept$

.WS_RF_FetchArtifactContentsFromStore(nullWS_RF_F

etchArtifactContentsFromStoreObjectConcept$.java:

118)




at

be.gen.WebStudio.Core.RuleFunctions.Actions.WS_RF

_FetchArtifactContentsFromStore.invoke(WS_RF_Fetc

hArtifactContentsFromStore.java:13)

at


l$1.doTxnWork(RuleSessionImpl.java:699)

at

com.tibco.cep.kernel.core.rete.BeTransaction.run(

SourceFile:156)

at

com.tibco.cep.kernel.core.rete.BeTransaction.exec

ute(SourceFile:101)

at


l.invokeFunction(RuleSessionImpl.java:689)

at


l.invokeFunction(RuleSessionImpl.java:677)

at

com.tibco.cep.driver.http.server.impl.tomcat.serv

let.PageFlowServlet$RuleFunctionExecTask.run(Sour

ceFile:434)

at

com.tibco.cep.runtime.session.BEManagedThread.exe

cute(BEManagedThread.java:458)

at


_from_queue(BEManagedThread.java:398)

at


(BEManagedThread.java:295)

Caused by: com.tibco.be.ws.scs.SCSException: File

path specified by

/opt/kabira/users/leon/BEX_1.1.1/be/5.1/examples/

standard/WebStudio/RuleTemplateExampleSOAPEvent.e

vent does not exist

at

com.tibco.be.ws.scs.impl.file.DefaultFileSystemIn

tegration.showFileContents(SourceFile:176)

at

com.tibco.be.ws.rt.model.ContainerSymbolChildNode

.a(SourceFile:173)

at


.a(SourceFile:233)

at


.resolveEntity(SourceFile:100)

at


rFunctions.resolveContainedEntity(SourceFile:323)

... 16 more



FLUENCY-

6152

WEBSTUDIO:

add examples

There are currently no WebStudio examples shipped with the

release.

This will be correct in a future release.

FLUENCY-

5928

WEBSTUDIO:

cannot generate

EAR on OS X

Generation of EARs on OS X is not supported in this release.

OS X support will be added in a future release.

FLUENCY-

6404

WEBSTUDIO:

fails when

started as root

The Rule Management Server (RMS) will fail to start if

installed as root.

The work-around is to not install RMS as root.


FLUENCY-

5938

WEBSTUDIO:

sometimes fails

to report build

errors

WebStudio will periodically fail to report build failures to the

UI. The build error is still reported to the WebStudio log file.























Welcome to TIBCO BusinessEvents® Extreme - TIBCO Product ...

Documents

Transcript of Welcome to TIBCO BusinessEvents® Extreme - TIBCO Product ...