tibco businessevents® extreme 1.3.1 release notes …red hat 6.2 ships with a new implementation of...
TRANSCRIPT
TIBCO BusinessEvents® Extreme 1.3.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
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.1
On-going stability improvements with a focus on distribution and high availability.
Upgraded to use ActiveSpaces Transactions 2.5.1
Certified on OpenJDK
Upgrading
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.1 Resolved Issues
For resolved issues in embedded products please see these release notes:
TIBCO ActiveSpaces® Transactions
TIBCO BusinessEvents®
Task
[FLUENCY-7638] - Doc Impact of FLUENCY-7535 3RDPARTY: certify on OpenJDK
1.3.0 Resolved Issues
For resolved issues in embedded products please see these release notes:
TIBCO ActiveSpaces® Transactions
TIBCO BusinessEvents®
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:
TIBCO BusinessEvents®
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
CLASSLOADER: 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
CLASSLOADER: 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-
619
ASTA: domain manager node
running ASTA can be
stopped/removed
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
CLASSLOADER: 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"
This will be resolved in a future release.
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.
This will be resolved in a future release.
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.
This will be resolved in a future release.
FLUENCY-
3757
ASTA: Channel.Security.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- STATISTICS: object update
latency does not include
The object update latency reported for distributed and
partitioned objects does not include the network
3859 partitioned objects latency.
There is no work-around for this issue.
This will be corrected in a future release.
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-
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.
There is no work-around for this issue.
This will be resolved in a future release.
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.
This will be corrected in a future release.
FLUENCY-
4537
CLASSLOADER: autoboxing and
valueof ClassCastException
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);
}
}
There is no work-around for this issue.
This will be resolved in a future release.
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.
There is no work-around for this issue.
This will be resolved in a future release.
FLUENCY-
4568
STUDIO: prints messages to
stdout
BE-X Studio prints messages to stdout. These should not
be there.
There is no work-around for this issue.
This will 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-
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.
This will be corrected in a future release.
FLUENCY- STUDIO: cannot deploy There is currently no support for deploying BE-X
4584 application directly from studio 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.
This will be corrected in a future release.
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.
This issue will be resolved in a future release.
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.
This will be resolved in a future release.
FLUENCY-
4645
DEPLOY: functions.catalog
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.
There is no work-around for this issue.
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-
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.
This will be resolved in a future release.
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.lookupBy
ExtId(RuntimeServiceProvider.java:725)
at
com.tibco.xp.runtime.RuntimeServiceProvider.fetchByEx
tId(RuntimeServiceProvider.java:423)
at
com.tibco.cep.runtime.model.element.impl.ManagedObj
ectManager.fetchByExtId(ManagedObjectManager.java:
58)
at
com.tibco.cep.runtime.service.cluster.om.CoherenceStor
e.getNamedInstance(CoherenceStore.java:355)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl.loa
dNamedInstances(RuleSessionImpl.java:598)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl$1.d
oTxnWork(RuleSessionImpl.java:363)
at
com.tibco.cep.kernel.core.rete.BeTransaction$1.run(Sou
rceFile:158)
at
com.tibco.xp.runtime.RuntimeServiceProvider$BEXTrans
action.run(RuntimeServiceProvider.java:580)
at
com.kabira.platform.Transaction.execute(Transaction.jav
a:457)
at
com.tibco.xp.runtime.RuntimeServiceProvider.txnWork(
RuntimeServiceProvider.java:607)
at
com.tibco.cep.kernel.core.rete.BeTransaction.run(Source
File:162)
at
com.tibco.cep.kernel.core.rete.BeTransaction.execute(S
ourceFile:90)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl.star
t(RuleSessionImpl.java:360)
at
com.tibco.cep.runtime.service.cluster.agent.InferenceAg
ent.onActivate(InferenceAgent.java:990)
at
com.tibco.cep.runtime.service.cluster.agent.AbstractCac
heAgent.activate(AbstractCacheAgent.java:152)
at
com.tibco.cep.runtime.service.cluster.agent.AbstractCac
heAgent.start(AbstractCacheAgent.java:165)
at
com.tibco.cep.runtime.service.cluster.agent.AgentRunti
mePolicyManager.tryActivateAgent(AgentRuntimePolicy
Manager.java:173)
at
com.tibco.cep.runtime.service.cluster.agent.AgentRunti
mePolicyManager.stabilizeCluster(AgentRuntimePolicyM
anager.java:249)
at
com.tibco.cep.runtime.service.cluster.agent.AgentRunti
mePolicyManager.tryActivateLocalAgents(AgentRuntime
PolicyManager.java:297)
at
com.tibco.cep.runtime.service.cluster.agent.DefaultAgen
tManager.start(DefaultAgentManager.java:99)
at
com.tibco.cep.runtime.service.cluster.MultiAgentCluster.
start(MultiAgentCluster.java:253)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.startCluster(RuleServiceProviderImpl.java:746)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.configure(RuleServiceProviderImpl.java:253)
at
com.tibco.cep.container.standalone.BEMain.jumpStart(S
ourceFile:144)
at
com.tibco.cep.container.standalone.BEMain.main(Sourc
eFile:67)
There is no work-around for this issue.
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.
This will be corrected in a future release.
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.ma
pPropertyType(CodeGeneration.java:141)
at
com.tibco.xp.studio.codegeneration.ConceptCodeGener
ation.generateFunctionJavaDoc(ConceptCodeGeneration
.java:494)
at
com.tibco.xp.studio.codegeneration.ConceptCodeGener
ation.addLookupFunctions(ConceptCodeGeneration.java
:421)
at
com.tibco.xp.studio.codegeneration.ConceptCodeGener
ation.generate(ConceptCodeGeneration.java:83)
at
com.tibco.xp.studio.codegeneration.JavaFileJob.generat
eCode(JavaFileJob.java:182)
at
com.tibco.xp.studio.codegeneration.UpdateJavaFileJob.r
unInWorkspace(UpdateJavaFileJob.java:23)
at
org.eclipse.core.internal.resources.InternalWorkspaceJo
b.run(InternalWorkspaceJob.java:38)
at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:5
4)
There is no workaround for this issue.
This issue will be resolved in a future release.
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.
This will be corrected in a future release.
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.
There is no work-around for this issue.
This will be corrected in a future release.
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- QUERY: update in RTC lost if Updates to a concept in an RTC are lost if the concept is
5287 concepts reloaded via a query 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.
This will be resolved in a future release.
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.
This will be corrected in a future release.
FLUENCY-
5477
CODEGEN: changing a parent's
key(s) or field(s) causes child
compilation errors
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.
The work-around is to perform a project clean when
changing concepts with children.
This will be corrected in a future release.
FLUENCY-
5478
SCORECARD: add support for
scorecards
Scorecards are not supported in this release, however,
they can be created in Studio.
There is no work-around for this issue.
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.
This issue will be resolved in a future release.
FLUENCY-
5593
CLASSLOADER: 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.
This issue may be resolved in a future release.
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 if
created concept flushed to
shared memory via catalog
function
The following will cause a concept to fail to be deleted
from shared memory.
Create a concept in a rule
Flush the concept to shared memory by calling a catalog
function in a separate rule in the same RTC.
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.
This will be resolved in a future release.
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.
This will be corrected 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.ResourceException:
Problems encountered while deleting resources.
at
org.eclipse.core.internal.resources.Resource.delete(Reso
urce.java:793)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cl
eanOutputFolders(BatchImageBuilder.java:114)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.b
uild(BatchImageBuilder.java:46)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(J
avaBuilder.java:254)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(Jav
aBuilder.java:173)
at
org.eclipse.core.internal.events.BuildManager$2.run(Buil
dManager.java:728)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:199)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:239)
at
org.eclipse.core.internal.events.BuildManager$1.run(Buil
dManager.java:292)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:295)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
Loop(BuildManager.java:351)
at
org.eclipse.core.internal.events.BuildManager.build(Buil
dManager.java:374)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(Au
toBuildJob.java:143)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoB
uildJob.java:241)
at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:5
4)
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.interna
lDeleteFile(ResourceTree.java:304)
at
org.eclipse.core.internal.resources.ResourceTree.standar
dDeleteFile(ResourceTree.java:785)
at
org.eclipse.core.internal.resources.Resource.unprotecte
dDelete(Resource.java:1937)
at
org.eclipse.core.internal.resources.Resource.delete(Reso
urce.java:780)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cl
eanOutputFolders(BatchImageBuilder.java:114)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.b
uild(BatchImageBuilder.java:46)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(J
avaBuilder.java:254)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(Jav
aBuilder.java:173)
at
org.eclipse.core.internal.events.BuildManager$2.run(Buil
dManager.java:728)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:199)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:239)
at
org.eclipse.core.internal.events.BuildManager$1.run(Buil
dManager.java:292)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:295)
at
org.eclipse.core.internal.events.BuildManager.basicBuild
Loop(BuildManager.java:351)
at
org.eclipse.core.internal.events.BuildManager.build(Buil
dManager.java:374)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(Au
toBuildJob.java:143)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoB
uildJob.java:241)
at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:5
4)
This exception can be ignored. It has not impact on the
success of the build or clean.
This will be corrected in a future release.
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.DefaultDistrib
utedCacheBasedStore.handleException(DefaultDistribute
dCacheBasedStore.java:1659)
at
com.tibco.cep.runtime.service.cluster.om.DefaultDistrib
utedCacheBasedStore.applyChanges(DefaultDistributedC
acheBasedStore.java:1085)
at
com.tibco.cep.kernel.core.base.WorkingMemoryImpl.pr
ocessRecorded(SourceFile:370)
at
com.tibco.cep.kernel.core.rete.ReteWM.assertObject(So
urceFile:1653)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl.ass
ertObject(RuleSessionImpl.java:1367)
at
com.tibco.be.functions.engine.EngineFunctions$AssertEv
entAsyncTask.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.ru
n(CustomBEManagedThread.java:24)
Caused by: java.lang.RuntimeException:
createEntityProxy: Failed to create proxy object
asyncevent.managed.events.DoItProxy.
at
com.tibco.xp.runtime.ServiceProvider.createEntityProxy(
ServiceProvider.java:796)
at
com.tibco.xp.runtime.ServiceProvider.createObjectFrom
Handle(ServiceProvider.java:826)
at
com.tibco.xp.runtime.ServiceProvider.doCreate(ServiceP
rovider.java:399)
at
com.tibco.xp.runtime.ServiceProvider.insert(ServiceProvi
der.java:287)
at
com.tibco.xp.runtime.TransactionService.insert(Transacti
onService.java:38)
at
com.tibco.cep.runtime.model.element.impl.ManagedObj
ectManager.insert(ManagedObjectManager.java:165)
at
com.tibco.cep.runtime.service.cluster.txn.RtcTransaction
Manager.txnToMom(RtcTransactionManager.java:374)
at
com.tibco.cep.runtime.service.cluster.txn.RtcTransaction
Manager.applyTransactionToCache(RtcTransactionMana
ger.java:330)
at
com.tibco.cep.runtime.service.cluster.txn.RtcTransaction
Manager.applyTransaction(RtcTransactionManager.java:
512)
at
com.tibco.cep.runtime.service.cluster.txn.RtcTransaction
Manager.publish(RtcTransactionManager.java:180)
at
com.tibco.cep.runtime.service.cluster.agent.InferenceAg
ent.applyChanges(InferenceAgent.java:2387)
at
com.tibco.cep.runtime.service.cluster.om.DefaultDistrib
utedCacheBasedStore.applyChanges(DefaultDistributedC
acheBasedStore.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.newInsta
nce(Unknown Source)
at
java.lang.reflect.Constructor.newInstance(Unknown
Source)
at
com.tibco.xp.runtime.ServiceProvider.createEntityProxy(
ServiceProvider.java:769)
... 18 more
Caused by: java.lang.IllegalAccessError: no active
transaction
at
com.kabira.platform.ManagedObject.createSMObject(N
ative 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.j
ava:36)
... 23 more
The same thing happens if concepts are
created/modified in rules triggered by the asynchronous
event (both transient and non-transient).
There is no work-around for this issue.
This will be resolved in a future release.
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.jav
a:909)
[INFO] at
org.eclipse.swt.widgets.Display.create(Display.java:897)
[INFO] at
org.eclipse.swt.graphics.Device.<init>(Device.java:157)
[INFO] at
org.eclipse.swt.widgets.Display.<init>(Display.java:500)
[INFO] at
org.eclipse.swt.widgets.Display.<init>(Display.java:491)
[INFO] at
org.eclipse.swt.widgets.Display.getDefault(Display.java:1
681)
[INFO] at
com.tibco.cep.studio.ui.validation.PostValidationListener
.refresh(Unknown Source)
[INFO] at
com.tibco.cep.studio.ui.validation.PostValidationListener
.resourceChanged(Unknown Source)
[INFO] at
org.eclipse.core.internal.events.NotificationManager$1.r
un(NotificationManager.java:291)
[INFO] at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
[INFO] at
org.eclipse.core.internal.events.NotificationManager.not
ify(NotificationManager.java:285)
[INFO] at
org.eclipse.core.internal.events.NotificationManager.bro
adcastChanges(NotificationManager.java:149)
[INFO] at
org.eclipse.core.internal.resources.Workspace.broadcast
PostChange(Workspace.java:395)
[INFO] at
org.eclipse.core.internal.resources.Workspace.endOpera
tion(Workspace.java:1530)
[INFO] at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(Au
toBuildJob.java:156)
[INFO] at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoB
uildJob.java:241)
[INFO] at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:5
4)
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.
This will be resolved 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.
There is no work-around for this issue.
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.validateSa
ve(Workspace.java:2670)
at
org.eclipse.core.internal.resources.File.setContents(File.j
ava:352)
at
org.eclipse.jdt.internal.core.JavaProject.setSharedProper
ty(JavaProject.java:3147)
at
org.eclipse.jdt.internal.core.JavaProject.writeFileEntries(J
avaProject.java:2902)
at
org.eclipse.jdt.internal.core.JavaModelManager$PerProj
ectInfo.writeAndCacheClasspath(JavaModelManager.jav
a:1339)
at
org.eclipse.jdt.internal.core.JavaModelManager$PerProj
ectInfo.writeAndCacheClasspath(JavaModelManager.jav
a:1351)
at
org.eclipse.jdt.internal.core.SetClasspathOperation.exec
uteOperation(SetClasspathOperation.java:77)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(Jav
aModelOperation.java:728)
at
org.eclipse.core.internal.resources.Workspace.run(Work
space.java:2344)
at
org.eclipse.jdt.internal.core.JavaModelOperation.runOpe
ration(JavaModelOperation.java:793)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath
(JavaProject.java:3093)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath
(JavaProject.java:3055)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath
(JavaProject.java:3108)
at
com.tibco.xp.studio.javanature.AddNature.updateClassP
ath(AddNature.java:335)
at
com.tibco.xp.studio.javanature.AddNature.add(AddNatu
re.java:177)
at
com.tibco.xp.studio.codegeneration.CodeGeneration.init
ializePackageFragment(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
com.tibco.xp.studio.codegeneration.ConceptCodeGener
ation.generate(ConceptCodeGeneration.java:49)
at
com.tibco.xp.studio.codegeneration.JavaFileJob.generat
eCode(JavaFileJob.java:198)
at
com.tibco.xp.studio.codegeneration.CreateJavaFileJob.ru
nInWorkspace(CreateJavaFileJob.java:34)
at
org.eclipse.core.internal.resources.InternalWorkspaceJo
b.run(InternalWorkspaceJob.java:38)
at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:5
4)
The work-around is to ensure that Studio has write
access to the .classpath file in a project.
This issue may be resolved in a future release.
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.
This will be corrected in a future release.
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\
TestBESOAPSOAPEvent.event does not exist
at
com.tibco.be.ws.functions.WebstudioServerRTBuilderFu
nctions.resolveContainedEntity(SourceFile:325
There is no work-around for this issue.
This will be resolved in a future release.
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.
This issue will be resolved in a future release.
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(Man
agedObject.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
DSEBuiltin::ExceptionInvalidHandle
swtimer_stb0.cpp (1005): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_stb0.cpp (1073): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_stb0.cpp (1075): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_stb0.cpp (1526): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_mimpl0.cpp (1227): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_mimpl0.cpp (1229): RETHROW
DSEBuiltin::ExceptionInvalidHandle
swtimer_skl0.cpp (1092): RETHROW
DSEBuiltin::ExceptionInvalidHandle
osdisp.cpp (1249): DUMP
DSEBuiltin::ExceptionInvalidHandle
+++ 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.getProxyClassByEn
tityImpl(ServiceProvider.java:1101)
at
com.tibco.xp.runtime.ServiceProvider.createEntityProxy(
ServiceProvider.java:709)
at
com.tibco.xp.runtime.EntityProxy.createEntityProxy(Enti
tyProxy.java:256)
at
com.tibco.xp.runtime.EntityProxy.getProxy(EntityProxy.j
ava:187)
at
com.tibco.xp.runtime.Transient.updateProperties(Transi
ent.java:166)
at
com.tibco.xp.runtime.Event.assertEvent(Event.java:78)
at
com.tibco.xp.runtime.Transient.assertEvent(Transient.ja
va: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.
This issue will be resolved in a future release.
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) { };
This will be resolved in a future release.
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.
This will be resolved 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.
There is no work-around for this issue.
This will be resolved in a future release.
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>
This will be resolved in a future release.
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.Asserti
onFailedException: 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:110)
at
org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
at
org.eclipse.ui.part.MultiPageEditorPart.setActivePage(M
ultiPageEditorPart.java:1065)
at
org.eclipse.ui.part.MultiPageEditorPart.createPartContro
l(MultiPageEditorPart.java:352)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(
EditorReference.java:670)
at
org.eclipse.ui.internal.EditorReference.createPart(Editor
Reference.java:465)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(
WorkbenchPartReference.java:595)
at
org.eclipse.ui.internal.EditorReference.getEditor(EditorR
eference.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(Workben
chPage.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
org.eclipse.ui.internal.WorkbenchPage.openEditor(Work
benchPage.java:2773)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(Work
benchPage.java:2764)
at
com.tibco.cep.studio.ui.util.StudioUIUtils.openSharedEnt
ity(Unknown Source)
at
com.tibco.cep.studio.ui.util.StudioUIUtils.openElement(
Unknown Source)
at
com.tibco.cep.studio.ui.navigator.view.ProjectExplorer.a
(Unknown Source)
at
com.tibco.cep.studio.ui.navigator.view.ProjectExplorer.h
andleDoubleClick(Unknown Source)
at
org.eclipse.ui.navigator.CommonNavigator$5.run(Comm
onNavigator.java:523)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.ui.navigator.CommonNavigator$4.doubleClic
k(CommonNavigator.java:521)
at
org.eclipse.jface.viewers.StructuredViewer$1.run(Struct
uredViewer.java:845)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.jav
a:42)
at
org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at
org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.jav
a:175)
at
org.eclipse.jface.viewers.StructuredViewer.fireDoubleCli
ck(StructuredViewer.java:843)
at
org.eclipse.jface.viewers.AbstractTreeViewer.handleDou
bleSelect(AbstractTreeViewer.java:1462)
at
org.eclipse.ui.navigator.CommonViewer.handleDoubleSe
lect(CommonViewer.java:454)
There is no work-around for this issue.
This will be resolved in a future release.
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,/C
oncepts/ControlData/UsageMonitoringInformation]
The work-around is to retry the build.
This will be corrected 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.
This issue will be resolved in a future release.
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.
This issue will be resolved in a future release.
FLUENCY-
6219
RUNTIME: delete skipped in
RTCs triggered using
Concept.assertConcept 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
This issue will be resolved in a future release.
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.
This will be resolved in a future release.
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)
The work-around is to retry the build.
This will be corrected in a future release.
FLUENCY-
6240
RUNTIME:
RejectedExecutionException 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@5d1
8f67c[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@5d1
8f67c[Terminated, pool size = 0, active threads = 0,
queued tasks = 0, completed tasks = 0]
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rej
ectedExecution(Unknown Source)
at
java.util.concurrent.ThreadPoolExecutor.reject(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor.delay
edExecute(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor.sched
ule(Unknown Source)
at
com.tibco.cep.runtime.management.impl.metrics.Async
WorkerDataPublisher.init(AsyncWorkerDataPublisher.jav
a:52)
at
com.tibco.cep.runtime.management.impl.DefaultManag
ementCentral.onNotify(DefaultManagementCentral.java:
185)
at
com.tibco.cep.runtime.service.basic.DependencyWatche
r.notifyDependents(DependencyWatcher.java:71)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.registerDomains(RuleServiceProviderImpl.java:887)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.initCluster(RuleServiceProviderImpl.java:744)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.configure(RuleServiceProviderImpl.java:260)
at
com.tibco.cep.container.standalone.BEMain.jumpStart(S
ourceFile:151)
at
com.tibco.cep.container.standalone.BEMain.main(Sourc
eFile:69)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unkn
own Source)
at java.lang.reflect.Method.invoke(Unknown
Source)
at
com.tibco.xp.earhandler.MainWrapper.run(MainWrappe
r.java:38)
This exception prevents the application from starting.
The only work-around is to redeploy the application.
This will be resolved in a future release.
FLUENCY-
6273
CLASSLOADER: 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.ja
va:319)
[A] at
com.kabira.platform.AnyBuffer.writeJavaObject(AnyBuff
er.java:337)
[A] at
anontest.AnonTest$Target.invokeCommand(AnonTest.ja
va)
[A] at anontest.AnonTest$2.run(AnonTest.java:69)
[A] at
com.kabira.platform.Transaction.execute(Transaction.jav
a:457)
[A] at
com.kabira.platform.Transaction.execute(Transaction.jav
a:510)
[A] at anontest.AnonTest.runTest(AnonTest.java:58)
[A] at anontest.AnonTest.main(AnonTest.java:26)
[A] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[A] at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
[A] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unkn
own 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(Unknow
n Source)
[A] at
java.io.ObjectOutputStream.writeSerialData(Unknown
Source)
[A] at
java.io.ObjectOutputStream.writeOrdinaryObject(Unkno
wn 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.
This will be corrected 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.
There is no work-around for this issue.
This will be corrected 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.
This may be resolved in a future release.
FLUENCY-
6409
CONFIGURATION: 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.
This issue will be resolved in a future release.
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.
There is no work-around for this issue.
This will be resolved in a future release.
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.Fetc
h.WS_RF_CreateRuleTemplateBuilderConceptFromSCSFa
ctory] [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.even
t does not exist
at
com.tibco.be.ws.functions.WebstudioServerRTBuilderFu
nctions.resolveContainedEntity(SourceFile:325)
at
be.gen.WebStudio.Core.RuleFunctions.Utils.RT.Builder.n
ullWS_RF_TraverseAndBuildSymbolHierarchy$oversizeN
ame.WS_RF_TraverseAndBuildSymbolHierarchy(nullWS_
RF_TraverseAndBuildSymbolHierarchy$oversizeName.jav
a:37)
at
be.gen.WebStudio.Core.RuleFunctions.Utils.RT.Builder.n
ullWS_RF_CreateBuilderSymbolHierarchy$oversizeName
.WS_RF_CreateBuilderSymbolHierarchy(nullWS_RF_Crea
teBuilderSymbolHierarchy$oversizeName.java:31)
at
be.gen.WebStudio.Core.RuleFunctions.Utils.RT.Builder.O
ps.Fetch.WS_RF_CreateRuleTemplateBuilderConceptFro
mSCS$oversizeName.WS_RF_CreateRuleTemplateBuilde
rConceptFromSCS(WS_RF_CreateRuleTemplateBuilderCo
nceptFromSCS$oversizeName.java:20)
at
be.gen.WebStudio.Core.RuleFunctions.Utils.RT.Builder.O
ps.Fetch.WS_RF_CreateRuleTemplateBuilderConceptFro
mSCSFactory$oversizeName.WS_RF_CreateRuleTemplat
eBuilderConceptFromSCSFactory(WS_RF_CreateRuleTem
plateBuilderConceptFromSCSFactory$oversizeName.java
:21)
at
be.gen.WebStudio.Core.RuleFunctions.Utils.RT.WS_RF_C
reateAbstractRuleTemplateConceptFromSCS$oversizeNa
me.WS_RF_CreateAbstractRuleTemplateConceptFromSC
S(WS_RF_CreateAbstractRuleTemplateConceptFromSCS
$oversizeName.java:22)
at
be.gen.WebStudio.Core.RuleFunctions.Actions.nullWS_R
F_FetchArtifactContentsFromStoreObjectConcept$.WS_
RF_FetchArtifactContentsFromStore(nullWS_RF_FetchAr
tifactContentsFromStoreObjectConcept$.java:118)
at
be.gen.WebStudio.Core.RuleFunctions.Actions.WS_RF_F
etchArtifactContentsFromStore.invoke(WS_RF_FetchArti
factContentsFromStore.java:13)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl$1.d
oTxnWork(RuleSessionImpl.java:699)
at
com.tibco.cep.kernel.core.rete.BeTransaction.run(Source
File:156)
at
com.tibco.cep.kernel.core.rete.BeTransaction.execute(S
ourceFile:101)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl.inv
okeFunction(RuleSessionImpl.java:689)
at
com.tibco.cep.runtime.session.impl.RuleSessionImpl.inv
okeFunction(RuleSessionImpl.java:677)
at
com.tibco.cep.driver.http.server.impl.tomcat.servlet.Pag
eFlowServlet$RuleFunctionExecTask.run(SourceFile:434)
at
com.tibco.cep.runtime.session.BEManagedThread.execu
te(BEManagedThread.java:458)
at
com.tibco.cep.runtime.session.BEManagedThread.run_fr
om_queue(BEManagedThread.java:398)
at
com.tibco.cep.runtime.session.BEManagedThread.run(B
EManagedThread.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.even
t does not exist
at
com.tibco.be.ws.scs.impl.file.DefaultFileSystemIntegratio
n.showFileContents(SourceFile:176)
at
com.tibco.be.ws.rt.model.ContainerSymbolChildNode.a(
SourceFile:173)
at
com.tibco.be.ws.rt.model.ContainerSymbolChildNode.a(
SourceFile:233)
at
com.tibco.be.ws.rt.model.ContainerSymbolChildNode.re
solveEntity(SourceFile:100)
at
com.tibco.be.ws.functions.WebstudioServerRTBuilderFu
nctions.resolveContainedEntity(SourceFile:323)
... 16 more
There is no work-around for this issue.
This will be corrected in a future release.
FLUENCY-
6484
RUNTIME:
Instance.deleteInstance
followed by create concept
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
causes duplicate key in same
RTC
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.
This issue will be resolved in a future release.
FLUENCY-
6524
CONFIGURATION: 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.
There is no work-around for this issue.
This will be corrected in a future release.
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$Compl
etionNotifier.$getDirectoryImpl(RequestWaiter.java:97)
at
com.kabira.platform.ktvmnotifier.RequestWaiter$Compl
etionNotifier.getDirectory(RequestWaiter.java)
at
com.kabira.platform.ktvmnotifier.RequestWaiter$Compl
etionNotifier.$getPathImpl(RequestWaiter.java:88)
at
com.kabira.platform.ktvmnotifier.RequestWaiter$Compl
etionNotifier.getPath(RequestWaiter.java)
at
com.kabira.platform.ktvmnotifier.RequestWaiter$Compl
etionNotifier.$requestCompleteImpl(RequestWaiter.java
:55)
at
com.kabira.platform.ktvmnotifier.RequestWaiter$Compl
etionNotifier.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.
This will be resolved in a future release.
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._ne
w(Native Method)
at
com.kabira.platform.ManagedObject$ExtentIterator.<ini
t>(ManagedObject.java:1202)
at
com.kabira.platform.ManagedObject$Extent.iterator(Ma
nagedObject.java:1184)
at
com.tibco.Utilities.deleteTempObjects(Utilities.java:14)
at
hotdeployment.internal.com.tibco._Utilities_2.Utilities_d
eleteTempObjects(_Utilities_2.java:39)
at
be.gen.RuleFunctions.nullReadDT$.ReadDT(nullReadDT$.
java: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.ass
ertObject(RuleSessionImpl.java:1373)
at
com.tibco.cep.runtime.session.impl.RuleSessionManager
Impl.notifyHotDeployment(RuleSessionManagerImpl.jav
a:453)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.upd
ate(BEClassLoader.java:328)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:275)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:281)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:270)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.notify(RuleServiceProviderImpl.java:1530)
at
com.tibco.cep.repo.hotdeploy.DirectoryDeployer.poll(Dir
ectoryDeployer.java:88)
at
com.tibco.cep.repo.hotdeploy.DirectoryDeployer.run(Dir
ectoryDeployer.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.
This will be resolved in a future release.
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 to
upgrade model containing
custom catalog functions
There is no support for hot-deployment of models that
contain custom catalog functions. When attempting to
upgrade a model 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
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unkn
own Source)
at java.lang.reflect.Method.invoke(Unknown
Source)
at
com.tibco.cep.runtime.service.loader.ClassManager.rede
fineClasses(ClassManager.java:410)
at
com.tibco.cep.runtime.service.loader.ClassManager.com
mitChanges(ClassManager.java:322)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.upd
ate(BEClassLoader.java:311)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:275)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:281)
at
com.tibco.cep.runtime.service.loader.BEClassLoader.lock
AndUpdate(BEClassLoader.java:270)
at
com.tibco.cep.runtime.session.impl.RuleServiceProviderI
mpl.notify(RuleServiceProviderImpl.java:1530)
at
com.tibco.cep.repo.hotdeploy.DirectoryDeployer.poll(Dir
ectoryDeployer.java:88)
at
com.tibco.cep.repo.hotdeploy.DirectoryDeployer.run(Dir
ectoryDeployer.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
There is no work-around for this issue.
This may be resolved in a future release.
FLUENCY-
6694
MONITOR: offset values not
decoded
When monitor decoding is in system or primitive, offset
fields are not decoded.
There is no work-around for this issue.
This will be resolved in a future release.
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::defau
ltProfile was added.
These messages can be safely ignored.
This will be corrected in a future release.
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");
}
});
This will be resolved in a future release.
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.getMainMethodFro
mClass(MainWrapper.java:319)
at
com.kabira.platform.MainWrapper.getMainMethod(Mai
nWrapper.java:251)
at
com.kabira.platform.MainWrapper.invokeMain(MainWr
apper.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.deleteInstance 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);
}
}
This issue will be resolved in a future release.
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.
This issue will be resolved in a future release.
FLUENCY-
6872
RUNTIME: ArithmeticException
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- DIST: JOIN_CLUSTER_PURGE Enabling a partition with JOIN_CLUSTER_PURGE with the
6882 deletes instances even if local
node is active node in partition.
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-
6937
DEVGUIDE: Incorrect hot
deployment description
The instructions in deploying the EAR for hot deployment
in 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.
This issue will be resolved in a future release.
FLUENCY-
6969
MONITOR: field name tool tips
not displayed
The tooltips on fields in the monitor are not displayed
correctly.
There is no work-around for this issue.
This will be corrected in a future release.
FLUENCY- CLASSLOADER: object field null
when passed to enumeration
7232 method
FLUENCY-
7245
CLASSLOADER: Managed object
slot descriptions are sensitive to
Java version.
Nodes running in the same cluster must be running the
same major JDK version, e.g. JDK 7 or JDK 8. Mixed JDK
versions in a cluster will cause invalid type mismatch
errors.
This restriction will be removed in a future release.
FLUENCY-
7267
QUERY: passing ByValue or
ByReference fields to
KeyQuery.getOrCreateSingleRes
ult
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.
This issue will be resolved in a future release.