Welcome to TIBCO BusinessEvents® Extreme · See the Getting Started Guide for quickly getting...

TIBCO BusinessEvents® Extreme 1.3.2 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

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

6.0 to 6.6 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 24.6.0

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 Oracle JRE versions:

1.7.0_67 - default JRE

1.6.0_65 (Apple JDK) - OS X only

Deployment is supported on JRE 1.7

Studio uses Java 1.7 on all platforms other than OS X, which uses Java 1.6 (Apple version).

TIBCO BusinessEvents Extreme® has also been certified on OpenJDK version 1.7.0_80.

Major Improvements in TIBCO BusinessEvents® Extreme 1.3.2

On-going stability improvements with a focus on distribution and high availability.

Upgraded to use ActiveSpaces Transactions 2.5.2

Upgrading

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

The following changes must be made to upgrade from previous releases.

No changes required.

Deprecations

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

Please update your applications and development environment.

None

1.3.2 Resolved Issues

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

TIBCO ActiveSpaces® Transactions

TIBCO BusinessEvents®

Bug

[FLUENCY-7588] - BEXSTRESS: UPGRADE-EVENT-0010 UPGRADE-EVENT-

0020 description clarification

[FLUENCY-7710] - WEBSTUDIO: Start RMS - glibc detected *** ./be-rms:

munmap_chunk(): invalid pointer (Linux)

Improvement

[FLUENCY-7681] - DISCOVERY: document that the discovery UDP port must

accessible





Task

[FLUENCY-7638] - Doc Impact of FLUENCY-7535 3RDPARTY: certify on OpenJDK




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

https://docs.tibco.com/pub/businessevents-standard/5.1.4/TIB_businessevents-standard_5.1.4_relnotes.pdf

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








Bug

[FLUENCY-5058] - CONCEPT: @parent always return null

[FLUENCY-5928] - BUILDER: cannot generate EAR on OS X

[FLUENCY-6379] - RUNTIME: Attempted to set Instance as the parent while it has

been set to Instance null

[FLUENCY-6589] - TEST: add security definition for administration commands

[FLUENCY-6699] - RUNTIME: null concept properties cause spurious RTC cycle

[FLUENCY-7043] - DEPLOY: Usage error when detach=true is specified

[FLUENCY-7099] - RUNTIME: NullPointerException updating concept with null keys

[FLUENCY-7133] - RUNTIME: Entity.getBEClassName dispatched on remote objects

[FLUENCY-7239] - RUNTIME: Error loading as-common dynamic loadable library

[FLUENCY-7241] - DIST: Missing distribution configuration file

[FLUENCY-7285] - CONCEPT: Invalid javadoc generated for constructors

[FLUENCY-7315] - 3RDPARTY: update to universal installer version 3.3.0

[FLUENCY-7480] - CONCEPT: toString causes StackOverflowErrors

[FLUENCY-7506] - RUNTIME: NullPointerException looking up type identifier

Documentation

[FLUENCY-7323] - DOCS: Update copyright year

Improvement

[FLUENCY-6185] - WEBSTUDIO: improve rmsbuilder management of the builder

workspace

[FLUENCY-6955] - CONCEPT: generate KeyField annotation on key constructors

[FLUENCY-7187] - ENTITY: add more details to toString methods

Task

[FLUENCY-6887] - 3RDPARTY: upgrade to BE 5.1.4

[FLUENCY-6949] - 3RDPARTY: upgrade to TIBCO Universal installer 3.3.0 V3

[FLUENCY-7033] - DOCTOOLS: update Two-Second Advantage tag line on title page

[FLUENCY-7390] - 3RDPARTY: upgrade to BE 5.1.4 - HF 2

[FLUENCY-7521] - Doc Impact of FLUENCY-7477 3RDPARTY: certify AST/BE-X on

RedHat 6.6.

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

-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

-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

-542

CLASSLOAD

ER: 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

CLASSLOAD

ER: can't store

Arrays of enums stored in a ManagedObject store a null as the

first value in the enum declaration.

https://docs.tibco.com/pub/businessevents/5.1.4/TIB_businessevents-express_5.1.4_relnotes.pdf

























a null reference

in a Java enum

array

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

-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

-1129

CLASSLOAD

ER: 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

-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

-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

-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.

There is no work-around for this issue.

This will be corrected 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.





















This issue will be resolved 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

-3757

ASTA:

Channel.Securi

ty.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.


This wil be resolved 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

-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.


FLUENCY

-4474

QUERY:

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

-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

-4537

CLASSLOAD

ER: autoboxing

and valueof

ClassCastExce

ption

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

-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

-4567

CATALOG:

Line number

not provided in

catalog

function

markers

The catalog function problem markers are missing the line

number.



FLUENCY

-4568

STUDIO:

prints messages

to stdout

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



FLUENCY

-4569

ASTA: The

BE-X

administrator is

not rebranded

The BE-X Administrator was not rebranded. It still references

ActiveSpaces Transactions.


FLUENCY

-4574

CATALOG:

Unsupported

built-in

functions

shipped

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

ActiveSpaces

BusinessWorks

Standard --> Cluster

Standard --> Temporal
































Do not use these functions in your models.

These functions will be removed in a future release.

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

-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

-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

-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

-4637

INSTALLER:

Studio missing

BE-X

customizations

if run from

install where

user cannot

write

If BE-X is installed where user cannot write to the 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

-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

-4659

STUDIO:

Refactor

(rename)

project name

fails

Using refactor to rename a project causes the project to become

corrupted.



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

-4820

KEY: key input

not enabled

When editing a child concept that inherits from a parent concept

with properties, the key editor is not enabled if there are no







































when no

properties in

child Concept

properties in the child concept.

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

will enable the key editor.


FLUENCY

-4847

SCORECARD:

add support for

scorecards

Scorecards are not currently supported in this release. Attempting

to use a scorecard will generate an error like this at runtime when

the scorecard is first accessed.

java.lang.RuntimeException: Failed to load Concept by

extId because proxy class

[frauddetection.managed.concepts.FraudCriteriaProxy]

cannot be found.

at

com.tibco.xp.runtime.RuntimeServiceProvider.lookupByE

xtId(RuntimeServiceProvider.java:725)

at

com.tibco.xp.runtime.RuntimeServiceProvider.fetchByEx

tId(RuntimeServiceProvider.java:423)

at

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

tManager.fetchByExtId(ManagedObjectManager.java:58)

at

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

re.getNamedInstance(CoherenceStore.java:355)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.lo

adNamedInstances(RuleSessionImpl.java:598)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl$1.

doTxnWork(RuleSessionImpl.java:363)

at

com.tibco.cep.kernel.core.rete.BeTransaction$1.run(So

urceFile:158)

at

com.tibco.xp.runtime.RuntimeServiceProvider$BEXTransa

ction.run(RuntimeServiceProvider.java:580)

at

com.kabira.platform.Transaction.execute(Transaction.j

ava:457)

at

com.tibco.xp.runtime.RuntimeServiceProvider.txnWork(R

untimeServiceProvider.java:607)

at

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

ceFile:162)

at

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

SourceFile:90)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.st

art(RuleSessionImpl.java:360)

at









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

Agent.onActivate(InferenceAgent.java:990)

at

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

acheAgent.activate(AbstractCacheAgent.java:152)

at

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

acheAgent.start(AbstractCacheAgent.java:165)

at

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

imePolicyManager.tryActivateAgent(AgentRuntimePolicyM

anager.java:173)

at


imePolicyManager.stabilizeCluster(AgentRuntimePolicyM

anager.java:249)

at


imePolicyManager.tryActivateLocalAgents(AgentRuntimeP

olicyManager.java:297)

at

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

entManager.start(DefaultAgentManager.java:99)

at

com.tibco.cep.runtime.service.cluster.MultiAgentClust

er.start(MultiAgentCluster.java:253)

at

com.tibco.cep.runtime.session.impl.RuleServiceProvide

rImpl.startCluster(RuleServiceProviderImpl.java:746)

at


rImpl.configure(RuleServiceProviderImpl.java:253)

at

com.tibco.cep.container.standalone.BEMain.jumpStart(S

ourceFile:144)

at

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

File:67)


Scorecards will be supported in a future release.

FLUENCY

-4889

RULE:

modifications

of key fields

allowed in rule

editor

Modification of key fields in a Concept should be disallowed in

the rule editor. However, they currently are not. For 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

-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.map

PropertyType(CodeGeneration.java:141)

at

com.tibco.xp.studio.codegeneration.ConceptCodeGenerat

ion.generateFunctionJavaDoc(ConceptCodeGeneration.jav

a:494)

at


ion.addLookupFunctions(ConceptCodeGeneration.java:421

)

at


ion.generate(ConceptCodeGeneration.java:83)

at

com.tibco.xp.studio.codegeneration.JavaFileJob.genera

teCode(JavaFileJob.java:182)

at

com.tibco.xp.studio.codegeneration.UpdateJavaFileJob.

runInWorkspace(UpdateJavaFileJob.java:23)

at

org.eclipse.core.internal.resources.InternalWorkspace

Job.run(InternalWorkspaceJob.java:38)

at

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

:54)

There is no workaround for this issue.


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

-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

-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

-5134

INSTALLER:

BE-X cannot

be installed

under

TIBCO_HOM

E 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

-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

-5400

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

-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

-5477

CODEGEN:

changing a

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

generated for child concepts will have undetected compilation











































parent's key(s)

or field(s)

causes child

compilation

errors

failures. The undetected compilation failures can cause runtime

deployment errors.

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

concepts with children.


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

-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

-5593

CLASSLOAD

ER: 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

-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

-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

-5677

RUNTIME:

delete skipped

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

shared memory.














































if created

concept flushed

to shared

memory via

catalog

function

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

-5807

EVENT:

duplicate rule

based timer

events

Rule based timed events scheduled in startup rule functions may

fire twice.

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

startup rule function.


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.ResourceException

: Problems encountered while deleting resources.

at

org.eclipse.core.internal.resources.Resource.delete(R

esource.java:793)

at

org.eclipse.jdt.internal.core.builder.BatchImageBuild

er.cleanOutputFolders(BatchImageBuilder.java:114)

at


er.build(BatchImageBuilder.java:46)

at

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

ldAll(JavaBuilder.java:254)

at


ld(JavaBuilder.java:173)

at

org.eclipse.core.internal.events.BuildManager$2.run(B

uildManager.java:728)

at

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

va:42)

at

org.eclipse.core.internal.events.BuildManager.basicBu

ild(BuildManager.java:199)





















at



at



at


va:42)

at



at


ildLoop(BuildManager.java:351)

at

org.eclipse.core.internal.events.BuildManager.build(B


at

org.eclipse.core.internal.events.AutoBuildJob.doBuild

(AutoBuildJob.java:143)

at

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

oBuildJob.java:241)

at


: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.LocalFile.

delete(LocalFile.java:125)

at

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

rnalDeleteFile(ResourceTree.java:304)

at

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

dardDeleteFile(ResourceTree.java:785)

at

org.eclipse.core.internal.resources.Resource.unprotec

tedDelete(Resource.java:1937)

at

org.eclipse.core.internal.resources.Resource.delete(R

esource.java:780)

at


er.cleanOutputFolders(BatchImageBuilder.java:114)

at


er.build(BatchImageBuilder.java:46)

at


ldAll(JavaBuilder.java:254)

at


ld(JavaBuilder.java:173)

at



at


va:42)

at



at



at



at


va:42)

at



at


ildLoop(BuildManager.java:351)

at

org.eclipse.core.internal.events.BuildManager.build(B


at



at


oBuildJob.java:241)

at


:54)

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

the build or clean.


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.DefaultDistr

ibutedCacheBasedStore.handleException(DefaultDistribu

tedCacheBasedStore.java:1659)

at


ibutedCacheBasedStore.applyChanges(DefaultDistributed

CacheBasedStore.java:1085)

at

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

essRecorded(SourceFile:370)

at

com.tibco.cep.kernel.core.rete.ReteWM.assertObject(So

urceFile:1653)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.as

sertObject(RuleSessionImpl.java:1367)

at

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

ventAsyncTask.run(SourceFile:649)

at

java.util.concurrent.ThreadPoolExecutor.runWorker(Unk

nown Source)

at

java.util.concurrent.ThreadPoolExecutor$Worker.run(Un

known 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

com.tibco.xp.runtime.ServiceProvider.createEntityProx

y(ServiceProvider.java:796)

at

com.tibco.xp.runtime.ServiceProvider.createObjectFrom

Handle(ServiceProvider.java:826)

at

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

Provider.java:399)

at

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

ovider.java:287)

at

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

ctionService.java:38)

at

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

tManager.insert(ManagedObjectManager.java:165)

at

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

ionManager.txnToMom(RtcTransactionManager.java:374)

at


ionManager.applyTransactionToCache(RtcTransactionMana

ger.java:330)

at


ionManager.applyTransaction(RtcTransactionManager.jav

a:512)

at


ionManager.publish(RtcTransactionManager.java:180)

at

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

Agent.applyChanges(InferenceAgent.java:2387)

at


ibutedCacheBasedStore.applyChanges(DefaultDistributed

CacheBasedStore.java:1083)

... 7 more

Caused by:

java.lang.reflect.InvocationTargetException

at

sun.reflect.NativeConstructorAccessorImpl.newInstance

0(Native Method)

at

sun.reflect.NativeConstructorAccessorImpl.newInstance

(Unknown Source)

at

sun.reflect.DelegatingConstructorAccessorImpl.newInst

ance(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(Nati

ve Method)

at

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

.java:48)

at

asyncevent.managed.events.DoIt.<init>(DoIt.java:32)

at

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

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

-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(Display

.java:909)

[INFO] at

org.eclipse.swt.widgets.Display.create(Display.java:8

97)

[INFO] at

org.eclipse.swt.graphics.Device.<init>(Device.java:15

7)

[INFO] at

org.eclipse.swt.widgets.Display.<init>(Display.java:5

00)

[INFO] at

org.eclipse.swt.widgets.Display.<init>(Display.java:4

91)

[INFO] at

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

va:1681)

[INFO] at

com.tibco.cep.studio.ui.validation.PostValidationList

ener.refresh(Unknown Source)

[INFO] at

com.tibco.cep.studio.ui.validation.PostValidationList

ener.resourceChanged(Unknown Source)

[INFO] at

org.eclipse.core.internal.events.NotificationManager$

1.run(NotificationManager.java:291)

[INFO] at


va:42)

[INFO] at

org.eclipse.core.internal.events.NotificationManager.

notify(NotificationManager.java:285)

[INFO] at

org.eclipse.core.internal.events.NotificationManager.

broadcastChanges(NotificationManager.java:149)

[INFO] at

org.eclipse.core.internal.resources.Workspace.broadca

stPostChange(Workspace.java:395)

[INFO] at

org.eclipse.core.internal.resources.Workspace.endOper








ation(Workspace.java:1530)

[INFO] at



[INFO] at


oBuildJob.java:241)

[INFO] at


: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

-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

-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.ResourceException

: File /FraudDetection/.classpath is read-only.

at

org.eclipse.core.internal.resources.Workspace.validat

eSave(Workspace.java:2670)

at

org.eclipse.core.internal.resources.File.setContents(

File.java:352)

at

org.eclipse.jdt.internal.core.JavaProject.setSharedPr

operty(JavaProject.java:3147)

at

org.eclipse.jdt.internal.core.JavaProject.writeFileEn

tries(JavaProject.java:2902)

at

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

jectInfo.writeAndCacheClasspath(JavaModelManager.java

:1339)

at
















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

jectInfo.writeAndCacheClasspath(JavaModelManager.java

:1351)

at

org.eclipse.jdt.internal.core.SetClasspathOperation.e

xecuteOperation(SetClasspathOperation.java:77)

at

org.eclipse.jdt.internal.core.JavaModelOperation.run(

JavaModelOperation.java:728)

at

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

kspace.java:2344)

at

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

peration(JavaModelOperation.java:793)

at

org.eclipse.jdt.internal.core.JavaProject.setRawClass

path(JavaProject.java:3093)

at



at



at

com.tibco.xp.studio.javanature.AddNature.updateClassP

ath(AddNature.java:335)

at

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

e.java:177)

at

com.tibco.xp.studio.codegeneration.CodeGeneration.ini

tializePackageFragment(CodeGeneration.java:495)

at

com.tibco.xp.studio.codegeneration.CodeGeneration.get

PackageFragment(CodeGeneration.java:388)

at

com.tibco.xp.studio.codegeneration.CodeGeneration.get

CompilationUnit(CodeGeneration.java:141)

at


ion.generate(ConceptCodeGeneration.java:49)

at

com.tibco.xp.studio.codegeneration.JavaFileJob.genera

teCode(JavaFileJob.java:198)

at

com.tibco.xp.studio.codegeneration.CreateJavaFileJob.

runInWorkspace(CreateJavaFileJob.java:34)

at

org.eclipse.core.internal.resources.InternalWorkspace

Job.run(InternalWorkspaceJob.java:38)

at


:54)

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

.classpath file in a project.


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.

The work-around is to retry the build.


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\TestB

ESOAPSOAPEvent.event does not exist

at

com.tibco.be.ws.functions.WebstudioServerRTBuilderFun

ctions.resolveContainedEntity(SourceFile:325



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

-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()Ljav

a/lang/String;.

at

com.kabira.platform.ManagedObject._sendTwoWay(Native

Method)

at

com.kabira.platform.ManagedObject.sendTwoWay(ManagedO

bject.java:393)

at

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



























nt.java)

at java.lang.String.valueOf(Unknown Source)

at java.lang.StringBuilder.append(Unknown

Source)

at

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

erNotifyImpl(TransactionService.java:534)

at

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

rNotify(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

-6068

ENTITY:

events not

stored under

Event folder

and Concepts

not stored

under Concept

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.getProxyClassByE

ntityImpl(ServiceProvider.java:1101)

at



at

com.tibco.xp.runtime.EntityProxy.createEntityProxy(En

tityProxy.java:256)












at

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

.java:187)

at

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

ient.java:166)

at

com.tibco.xp.runtime.Event.assertEvent(Event.java:78)

at

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

java:80)

This restriction will be eliminated in a future release.

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

-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

-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

-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

-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

-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

-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

-6152

WEBSTUDIO:

add examples

There are currently no WebStudio examples shipped with the

release.

This will be correct in a future release.

FLUENCY

-6161

LIBRARY:

org.eclipse.core

.runtime.Assert

ionFailedExcep

tion: 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.java:11

0)

at

org.eclipse.core.runtime.Assert.isTrue(Assert.java:96

)

at

org.eclipse.ui.part.MultiPageEditorPart.setActivePage

(MultiPageEditorPart.java:1065)

at

org.eclipse.ui.part.MultiPageEditorPart.createPartCon

trol(MultiPageEditorPart.java:352)

at

org.eclipse.ui.internal.EditorReference.createPartHel

per(EditorReference.java:670)

at

org.eclipse.ui.internal.EditorReference.createPart(Ed

itorReference.java:465)

at

org.eclipse.ui.internal.WorkbenchPartReference.getPar

t(WorkbenchPartReference.java:595)

at

org.eclipse.ui.internal.EditorReference.getEditor(Edi

torReference.java:289)

at

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorB

atched(WorkbenchPage.java:2945)

at

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(

WorkbenchPage.java:2850)















at

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

enchPage.java:2842)

at

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

hPage.java:2793)

at

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

dicator.java:70)

at

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

benchPage.java:2789)

at



at



at

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

Entity(Unknown Source)

at

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

t(Unknown Source)

at

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

r.a(Unknown Source)

at

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

r.handleDoubleClick(Unknown Source)

at

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

Navigator.java:523)

at


va:42)

at

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

k(CommonNavigator.java:521)

at

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

cturedViewer.java:845)

at


va:42)

at

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

a:49)

at

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

java:175)

at

org.eclipse.jface.viewers.StructuredViewer.fireDouble

Click(StructuredViewer.java:843)

at

org.eclipse.jface.viewers.AbstractTreeViewer.handleDo

ubleSelect(AbstractTreeViewer.java:1462)

at

org.eclipse.ui.navigator.CommonViewer.handleDoubleSel

ect(CommonViewer.java:454)



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,/Co

ncepts/ControlData/UsageMonitoringInformation]



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

-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

-6219

RUNTIME:

delete skipped

in RTCs

triggered using

Concept.assert

Concept 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

-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

-6238

LIBRARY:

occasional

"cannot be

resolved to a

type" errors

when build

with project

libraries

When building a project with imported project libraries there are

intermittent failures like this reported and the build fails:

[INFO] ERROR:

/unittest/Java/com/tibco/test/DiameterRulesTest.java:

line 152: TestUserProfile cannot be resolved to a

type

[INFO] ERROR:

/unittest/Java/com/tibco/test/DiameterRulesTest.java:

line 152: The method getUserProfile(String, LockMode)



FLUENCY

-6240

RUNTIME:

RejectedExecut

ionException

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$Sche

































duledFutureTask@27b310e0 rejected from

java.util.concurrent.ScheduledThreadPoolExecutor@5d18

f67c[Terminated, pool size = 0, active threads = 0,

queued tasks = 0, completed tasks = 0]

java.util.concurrent.RejectedExecutionException: Task

java.util.concurrent.ScheduledThreadPoolExecutor$Sche

duledFutureTask@27b310e0 rejected from

java.util.concurrent.ScheduledThreadPoolExecutor@5d18

f67c[Terminated, pool size = 0, active threads = 0,

queued tasks = 0, completed tasks = 0]

at

java.util.concurrent.ThreadPoolExecutor$AbortPolicy.r

ejectedExecution(Unknown Source)

at

java.util.concurrent.ThreadPoolExecutor.reject(Unknow

n Source)

at

java.util.concurrent.ScheduledThreadPoolExecutor.dela

yedExecute(Unknown Source)

at

java.util.concurrent.ScheduledThreadPoolExecutor.sche

dule(Unknown Source)

at

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

rkerDataPublisher.init(AsyncWorkerDataPublisher.java:

52)

at

com.tibco.cep.runtime.management.impl.DefaultManageme

ntCentral.onNotify(DefaultManagementCentral.java:185)

at

com.tibco.cep.runtime.service.basic.DependencyWatcher

.notifyDependents(DependencyWatcher.java:71)

at


rImpl.registerDomains(RuleServiceProviderImpl.java:88

7)

at


rImpl.initCluster(RuleServiceProviderImpl.java:744)

at


rImpl.configure(RuleServiceProviderImpl.java:260)

at

com.tibco.cep.container.standalone.BEMain.jumpStart(S

ourceFile:151)

at

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

File:69)

at

sun.reflect.NativeMethodAccessorImpl.invoke0(Native

Method)

at

sun.reflect.NativeMethodAccessorImpl.invoke(Unknown

Source)

at

sun.reflect.DelegatingMethodAccessorImpl.invoke(Unkno

wn Source)

at java.lang.reflect.Method.invoke(Unknown

Source)

at

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

ava:38)

This exception prevents the application from starting.

The only work-around is to redeploy the application.


FLUENCY

-6273

CLASSLOAD

ER: 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.writeSerializableStream

(AnyBuffer.java:381)

[A] at

com.kabira.platform.AnyBuffer.writeObject(AnyBuffer.j

ava:319)

[A] at

com.kabira.platform.AnyBuffer.writeJavaObject(AnyBuff

er.java:337)

[A] at

anontest.AnonTest$Target.invokeCommand(AnonTest.java)

[A] at anontest.AnonTest$2.run(AnonTest.java:69)

[A] at


ava:457)

[A] at


ava:510)

[A] at anontest.AnonTest.runTest(AnonTest.java:58)

[A] at anontest.AnonTest.main(AnonTest.java:26)

[A] at


Method)

[A] at


Source)

[A] at


wn Source)

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

Source)

[A] at

com.kabira.platform.MainWrapper.invokeMain(MainWrappe

r.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(Unknown

Source)

[A] at

java.io.ObjectOutputStream.writeSerialData(Unknown

Source)

[A] at

java.io.ObjectOutputStream.writeOrdinaryObject(Unknow

n 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

-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

-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

-6409

CONFIGURA

TION: 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

-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

-6451

WEBSTUDIO:

SOAP events

do not work in

virtual rule

templates

SOAP events do not work in virtual rule templates. Attempting to

use one will cause a runtime failure similar to this:

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

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

[WebStudio.Core.RuleFunctions.Utils.RT.Builder.Ops.Fe

tch.WS_RF_CreateRuleTemplateBuilderConceptFromSCSFact

ory] [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/stan

dard/WebStudio/RuleTemplateExampleSOAPEvent.event

does not exist

at


ctions.resolveContainedEntity(SourceFile:325)

at

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

nullWS_RF_TraverseAndBuildSymbolHierarchy$oversizeNam

e.WS_RF_TraverseAndBuildSymbolHierarchy(nullWS_RF_Tra

verseAndBuildSymbolHierarchy$oversizeName.java:37)

at


nullWS_RF_CreateBuilderSymbolHierarchy$oversizeName.W

S_RF_CreateBuilderSymbolHierarchy(nullWS_RF_CreateBui

lderSymbolHierarchy$oversizeName.java:31)

at


Ops.Fetch.WS_RF_CreateRuleTemplateBuilderConceptFromS

CS$oversizeName.WS_RF_CreateRuleTemplateBuilderConcep

tFromSCS(WS_RF_CreateRuleTemplateBuilderConceptFromSC

S$oversizeName.java:20)

at


Ops.Fetch.WS_RF_CreateRuleTemplateBuilderConceptFromS

CSFactory$oversizeName.WS_RF_CreateRuleTemplateBuilde

rConceptFromSCSFactory(WS_RF_CreateRuleTemplateBuilde

rConceptFromSCSFactory$oversizeName.java:21)

at

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

eateAbstractRuleTemplateConceptFromSCS$oversizeName.W

S_RF_CreateAbstractRuleTemplateConceptFromSCS(WS_RF_C

reateAbstractRuleTemplateConceptFromSCS$oversizeName.
















java:22)

at

be.gen.WebStudio.Core.RuleFunctions.Actions.nullWS_RF

_FetchArtifactContentsFromStoreObjectConcept$.WS_RF_F

etchArtifactContentsFromStore(nullWS_RF_FetchArtifact

ContentsFromStoreObjectConcept$.java:118)

at

be.gen.WebStudio.Core.RuleFunctions.Actions.WS_RF_Fet

chArtifactContentsFromStore.invoke(WS_RF_FetchArtifac

tContentsFromStore.java:13)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl$1.

doTxnWork(RuleSessionImpl.java:699)

at

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

ceFile:156)

at

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

SourceFile:101)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.in

vokeFunction(RuleSessionImpl.java:689)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.in

vokeFunction(RuleSessionImpl.java:677)

at

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

PageFlowServlet$RuleFunctionExecTask.run(SourceFile:4

34)

at

com.tibco.cep.runtime.session.BEManagedThread.execute

(BEManagedThread.java:458)

at

com.tibco.cep.runtime.session.BEManagedThread.run_fro

m_queue(BEManagedThread.java:398)

at

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

anagedThread.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/stan

dard/WebStudio/RuleTemplateExampleSOAPEvent.event

does not exist

at

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

ation.showFileContents(SourceFile:176)

at

com.tibco.be.ws.rt.model.ContainerSymbolChildNode.a(S

ourceFile:173)

at

com.tibco.be.ws.rt.model.ContainerSymbolChildNode.a(S

ourceFile:233)

at

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

olveEntity(SourceFile:100)

at


ctions.resolveContainedEntity(SourceFile:323)

... 16 more



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

-6524

CONFIGURA

TION: export

configuration

does not

decode array of

managed

objects

If a configuration class contains a field that is an array of

managed objects then the configuration file exported using export

configuration contains object references for the array elements

instead of the fully decoded elements.



FLUENCY

-6599

DEPLOY:

using a

symbolic link

to rename an

EAR target

causes

assertion

Attempting to deploy an application archive that uses a symbolic

link to rename the archive fails with this exception:

Muir-Beach >> java -jar deploy.jar reset=false

Stress.ear descriptor=Stress.cdd

INFO: Deployment Tool (deploy.jar) version: [TIBCO

BusinessEvents(R) Extreme 1.2.0 (build 140322)]

starting at [Fri Mar 28 12:36:21 PDT 2014]

INFO: JVM remote debugger agent running on [kabira-

server.local:23886] ...

INFO: Node version: [TIBCO BusinessEvents(R) Extreme

1.2.0 (build 140322)]

INFO: Starting [Stress.ear] ...

INFO: [Stress.ear] started on JVM [Stress_ear14].

Listening for transport dt_socket at address: 23886

FATAL: Remote request thread failed for JVM

[Stress_ear14]: RequestThread unexepected

parseResponse: <error>

<code>49</code>

<message>A

[DSEBuiltin::ExceptionResourceUnavailable:

'java.lang.AssertionError

at

com.kabira.platform.ktvmnotifier.RequestWaiter$Comple

tionNotifier.$getDirectoryImpl(RequestWaiter.java:97)

at






























tionNotifier.getDirectory(RequestWaiter.java)

at


tionNotifier.$getPathImpl(RequestWaiter.java:88)

at


tionNotifier.getPath(RequestWaiter.java)

at


tionNotifier.$requestCompleteImpl(RequestWaiter.java:

55)

at


tionNotifier.requestComplete(RequestWaiter.java)

Here is what Stress.ear looks like:

ls -l Stress.ear

Stress.ear@ -> archives/Stress-original.ear

The work-around is to not use symbolic links to rename archives.


FLUENCY

-6650

RUNTIME:

transaction not

started for

Deployment

AdvisoryEvent

The Deployment AdvisoryEvent is not delivered with an active

transaction. This will cause an exception like the following if any

attempt is made to modify Concepts or non-transient Events:

java.lang.IllegalAccessError: no active

transaction2014 Apr 17 07:41:28:692 GMT -7 kabira-

server Info [inference-class-eventQueueListener] -

[runtime.service] Resuming thread: inference-class-

eventQueueListener

at

com.kabira.platform.ManagedObject$ExtentIterator._new

(Native Method)

at

com.kabira.platform.ManagedObject$ExtentIterator.<ini

t>(ManagedObject.java:1202)

at

com.kabira.platform.ManagedObject$Extent.iterator(Man

agedObject.java:1184)

at

com.tibco.Utilities.deleteTempObjects(Utilities.java:

14)

at

hotdeployment.internal.com.tibco._Utilities_2.Utiliti

es_deleteTempObjects(_Utilities_2.java:39)

at

be.gen.RuleFunctions.nullReadDT$.ReadDT(nullReadDT$.j

ava:10)

at

be.gen.Rules.AdvisoryEvt$AdvisoryEvt_a.execute(Adviso








ryEvt.java:65)

at

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

(SourceFile:322)

at

com.tibco.cep.kernel.core.rete.ReteWM.void(SourceFile

:298)

at

com.tibco.cep.kernel.core.rete.ReteWM.assertObject(So

urceFile:1645)

at

com.tibco.cep.runtime.session.impl.RuleSessionImpl.as

sertObject(RuleSessionImpl.java:1373)

at

com.tibco.cep.runtime.session.impl.RuleSessionManager

Impl.notifyHotDeployment(RuleSessionManagerImpl.java:

453)

at

com.tibco.cep.runtime.service.loader.BEClassLoader.up

date(BEClassLoader.java:328)

at

com.tibco.cep.runtime.service.loader.BEClassLoader.lo

ckAndUpdate(BEClassLoader.java:275)

at



at



at


rImpl.notify(RuleServiceProviderImpl.java:1530)

at

com.tibco.cep.repo.hotdeploy.DirectoryDeployer.poll(D

irectoryDeployer.java:88)

at

com.tibco.cep.repo.hotdeploy.DirectoryDeployer.run(Di

rectoryDeployer.java:48)

at java.lang.Thread.run(Unknown Source)

The work-around is to explicitly start a transaction before

modifying any Concepts or non-transient Events.


FLUENCY

-6652

QUERY: add

support for

query scope in

generated

query catalog

functions

The generated query catalog functions only support local queries.

Use a custom catalog function and Java code to perform a

distributed query.

This limitation in the generated query catalog functions will be

removed in a future release.

FLUENCY

-6685

UPGRADE:

fails attempting

There is no support for hot-deployment of models that contain

custom catalog functions. When attempting to upgrade a model













to upgrade

model

containing

custom catalog

functions

containing custom catalog functions, it will generate an exception

like this:

opt/kabira/users/leon/BEX_1.1.2/RUN/A/classpaths/Test

DecisionTable_ear0/TestDecisionTable.ear failed!!!

java.lang.reflect.InvocationTargetException

at


Method)

at


Source)

at


wn Source)

at java.lang.reflect.Method.invoke(Unknown

Source)

at

com.tibco.cep.runtime.service.loader.ClassManager.red

efineClasses(ClassManager.java:410)

at

com.tibco.cep.runtime.service.loader.ClassManager.com

mitChanges(ClassManager.java:322)

at

com.tibco.cep.runtime.service.loader.BEClassLoader.up

date(BEClassLoader.java:311)

at



at



at



at


rImpl.notify(RuleServiceProviderImpl.java:1530)

at

com.tibco.cep.repo.hotdeploy.DirectoryDeployer.poll(D

irectoryDeployer.java:88)

at

com.tibco.cep.repo.hotdeploy.DirectoryDeployer.run(Di

rectoryDeployer.java:48)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.UnsupportedOperationException:

class redefinition failed: attempted to delete a

method

at

sun.instrument.InstrumentationImpl.redefineClasses0(N

ative Method)

at

sun.instrument.InstrumentationImpl.redefineClasses(Un

known Source)

... 14 more








FLUENCY

-6694

MONITOR:

offset values

not decoded

When monitor decoding is in system or primitive, offset fields are

not decoded.



FLUENCY

-6695

CONCEPT:

transient

concepts not

deleted when

catalog

function called

Calling a catalog function with a transient concept (one created

using Instance.newTransientInstance) causes the transient

concept to be flushed to shared memory. It must be explicitly

deleted by the application.

Transient concepts may be deprecated in a future release. Please

only use non-transient concepts.

FLUENCY

-6704

RT: Type

verification

message can

contain bogus

fields.

Incorrect type mismatch log messages can be reported for a child

of a parent that has added or removed fields. For example:

2014-05-07 14:58:52.208925|DST|WARN

|30572|csnode.cpp(3220)|Type mismatch detected for

type

com.tibco.policyframework.userdata.UserProfile from

node MCPCRF1, remote version '-568284671649893289',

local version

'-568284671649893289', mismatch processing will

happen on local node, mismatch reason = 'Mismatch

detected for type

com.tibco.policyframework.userdata.UserProfile,

version '- 568284671649893289'. Changed values: Field

policy3uk.managed.concepts.userdata.UserProfile::prod

ucts was added: Field

policy3uk.managed.concepts.userdata.UserProfile::defa

ultProfile was added.

These messages can be safely ignored.


FLUENCY

-6720

RUNTIME:

shutdown rule

function not

called

Shutdown rule functions are not called when an application is

shutdown.

To work-around this problem a Java runtime hook can be used.

Runtime.getRuntime().addShutdownHook(

new Thread()

{

@Override



























public void run()

{

System.out.println("Goodbye world");

}

});


FLUENCY

-6760

DEPLOY:

spaces in

jvmname

causes

deployment

failure

Spaces in the jvmname deployment tool parameter cause the

deployment to fail with a message like this:

INFO: [sandbox.lifecycle.Jvm] started on JVM [Very

Important].

Listening for transport dt_socket at address: 28238

Java main class sandbox.lifecycle.Jvm.main exited

with an exception.

java.lang.RuntimeException: class

sandbox.lifecycle.Jvm not found

at

com.kabira.platform.MainWrapper.getMainMethodFromClas

s(MainWrapper.java:319)

at

com.kabira.platform.MainWrapper.getMainMethod(MainWra

pper.java:251)

at

com.kabira.platform.MainWrapper.invokeMain(MainWrappe

r.java:53)

INFO: JVM [sandbox.lifecycle.Jvm] exited with status

[-1].

The work-around is to not use spaces when specifying a JVM

name.

This issue will be resolved or audited against in a future release.

FLUENCY

-6786

RUNTIME:

Instance.deleteI

nstance does

not delete

shared memory

object until end

of RTC

The Instance.deleteInstance catalog function does not

immediately delete an object from shared memory. The shared

memory delete occurs at the end of the RTC.

The work-around to ensure that working memory and shared

memory are in sync during an RTC when deleting concepts is to

use a utility rule function like this:

void rulefunction RuleFunctions.DoDelete {

attribute {

validity = ACTION;

}

scope {

Concepts.B b;

}

body {

//

// Remove object from shared


















memory immediately

//

Utilities.deleteManagedObject(b);

//

// Remove object from working

memory

//

Instance.deleteInstance(b);

}

}


FLUENCY

-6847

HA: leave

cluster with

asynchronous

partitions

causes

warnings

Leaving a cluster on a node that hosts an asynchronous replica

partition may generate spurious warnings in the log files while the

leave is executing. For example:

DST|WARN |7518|csmarshal.cpp(2004)|Cannot access

unknown partition 'Leave Cluster (v541980012961857)'

for object type

sandbox.highavailability.LeaveCluster$X on node C.

or

2014-07-03 16:34:59.445105|DST|WARN

|49121|csmarshal.cpp(1125)|Invalid object reference

'1340264:3534776:489635240020741:64' for type

sandbox.highavailability.LeaveCluster$X, operation

destroy, event discarded

These warnings can be safely ignored - they do not affect the

outcome of the leave cluster command.


FLUENCY

-6872

RUNTIME:

ArithmeticExce

ption does not

rollback

transaction

Transactions are not rolled back if an exception is thrown that

extends java.lang.RuntimeException. Any changes to concepts

made during the RTC before the exception is thrown are

incorrectly committed to shared memory.

The work-around is to set up a rule for advisory events and force

the transaction to be rolled back. Here is an example rule that

shows how this can be done:

rule Rules.Notification {

attribute {

priority = 5;

forwardChain = true;

}

declare {

AdvisoryEvent a;
















}

when {

}

then {

System.debugOut("WARN: "

+ a@category

+ ":"

+ a@type

+ ":"

+ a@message);

//

// FIX THIS: Force a rollback -

FLUENCY-6872

//

if (a@category == "Exception")

{

RunTest.rollback(a@message);

}

}

}

Here is the definition of the RunTest.rollback catalog function:

/**

* Rollback current transaction

* @param reason Rollback reason

*/

@Function

public static void rollback(final String

reason)

{

//

// This cannot extend

java.lang.RuntimeException

//

throw new Error(reason);

}

This issue will be corrected in a future release.

FLUENCY

-6882

DIST:

JOIN_CLUST

ER_PURGE

deletes

instances even

if local node is

active node in

partition.

Enabling a partition with JOIN_CLUSTER_PURGE with the

local node as the active node for both the old and new partition

definitions will delete all instances in the partition on the local

node, leaving the partition empty. This is usually not what is

desired.

The work-around is to ensure that JOIN_CLUSTER_PURGE is

not used when enabling partitions on the active node.

Future releases may raise an exception when this is attempted, or

raise a log message and not remove the objects from the partition.

FLUENCY DEVGUIDE: The instructions in deploying the EAR for hot deployment in













-6937 Incorrect hot

deployment

description

Chapter 24 Hot Deployment of the Application Developer's

Guide are incorrect. In the Deploy the EAR File that was

generated by Web Studio section it states that the newly

generated EAR should replace the EAR in the

<node_name>/deploy/resources/deploy<timestamp>_ directory.

This is incorrect. The EAR should be placed into the

<node_name>/classpath/<jvm_name> directory.

This documentation error will be correct in a future release.

FLUENCY

-6942

DEPLOY:

shared memory

allocation

failure with

large JAR files

Attempting to deploy very large target archives in attached mode

will cause shared memory allocation failures on the node.

The work-around is to use detached mode when deploying very

large target archives.


FLUENCY

-6969

MONITOR:

field name tool

tips not

displayed

The tooltips on fields in the monitor are not displayed correctly.



FLUENCY

-7232

CLASSLOAD

ER: object field

null when

passed to

enumeration

method

FLUENCY

-7267

QUERY:

passing

ByValue or

ByReference

fields to

KeyQuery.getO

rCreateSingleR

esult

Populating @ByValue and @ByReference fields in the

additionalFields parameter to

KeyQuery.getOrCreateSingleResult() can cause either application

or node crashes. The workaround is to set these fields directly on

the object returned from getOrCreateSingleResult().

FLUENCY

-7440

NODE: start

node doesn't

start the node

when

coordinator not

running

Starting a node after the coordinator has been terminated only

restarts the coordinator, it does not restart the other node

processes. This is incorrect, it should be starting all other node

processes. For example:

administrator servicename=Stinson-Beach.local

terminate node

administrator start node installpath=Stinson-

Beach.local

//

// Node should be running at this point












































//

administrator servicename=Stinson-Beach.local display

node

Node cannot perform administration commands. Reason:

node not started.

//

// Another start is required - it shouldn't be

//

administrator servicename=Stinson-Beach.local start

node

The work around is to issue another start node.


FLUENCY

-7699

WEBSTUDIO:

RMS fail to

start -

java.net.Unkno

wnHostExcepti

on (OS X)

The RMS engine fails to start on OS X with a

java.net.UnknownHostException:<machine name>:

nodename nor servname provided, or not known.

The work-around for this issue is to update the /etc/hosts file to

include the machine name. The steps are:

1. Open Terminal application.

2. Enter sudo vi /etc/hosts

3. Validate current contents of /etc/hosts: 4. 5. ## 6. # Host Database 7. # 8. # localhost is used to configure the loopback

interface

9. # when the system is booting. Do not change this entry.

10. ##

11. 127.0.0.1 localhost

12. 255.255.255.255 broadcasthost

13. ::1 localhost

14. Add this line: 15.

16. 127.0.0.1 <machine_name>










Date post:	26-May-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Welcome to TIBCO BusinessEvents® Extreme · See the Getting Started Guide for quickly getting...

Documents