Issue with XLA/JMS

Question

I am trying to test the event handler functionality. I created a database using the input0.dat file included in the install. I then created a simple materialized view:
CREATE MATERIALIZED VIEW xyz.mv AS SELECT * FROM xyz.customer WHERE xyz.customer.region='North';
I modified the level1.java example program to read a longer input file that I created and to sleep between each insert (I also commit after each insert) so that I could have something running during my tests.
I then ran xlalevel3.java and entered:
select * from xyz.mv;
as my SQL. What I see is input messages for both the materialized view and the underlying customer table. I was expecting to only received messages for the materialized view?
Please advise.
Thanks,
Mark

Answer 1

Hi Mark,
There are 2 parts to your question:
1. In order to monitor the updates using XLA, you need to specify the tables or materialized views that you wish to track.
Did you update the JMS/XLA configuration file (jmsxla.xml) in the tt60/demo directory by adding enabledTables="xyz.mv" for the topic "Level3Demo"?
Here is the jmsxla.xml in the demo directory, by default it does not contain any subscriptions for the XlaLevel3 demo.
<?xml version="1.0"?>
<!-- JMS/XLA configuration file -->
<!-- Contains topic definitions and an optional list of tables -->
<!-- for which XLA is enabled. -->
<!-- Each topic consists of a name, a JDBC connection string, -->
<!-- and a prefetch value, which is the number of updates that -->
<!-- will be retrieved at a time. -->
<xlaconfig>
<topics>
<!-- default topic for XlaLevel1 demo -->
<topic name="Level1Demo"
connectionString="DSN=RunData_tt60"
xlaPrefetch="100"
enabledTables="xyz.customer"
/>
<!-- default topic for XlaLevel2 demo -->
<topic name="Level2Demo"
connectionString="DSN=RunData_tt60"
xlaPrefetch="100"
enabledTables="xyz.customer"
/>
<!-- default topic for XlaLevel3 demo, no tables specified here -->
<topic name="Level3Demo"
connectionString="DSN=RunData_tt60"
xlaPrefetch="100"
/>
</topics>
</xlaconfig>
2. In the current TimesTen release (6.0), tables or views subscribed to by one XLA reader are also seen by all other XLA readers. Hence XLA is tracking active subscriptions globally rather than per application.
Since you are getting updates on the xyz.customer table also, it is possible that you have active bookmarks on Level1Demo, Level2Demo etc. A quick test to verify this would be for you to re-create the RunData_tt60 datastore from scratch, and see whether you are now getting updates on xyz.mv only when running the XlaLevel3 demo.
Alternatively, you can do a SELECT * from TRANSACTION_LOG_API and delete the non-required bookmarks by calling the built-in procedure ttxladeletebookmark. And then try running the demo again.
Simon