Continuous query cache in c++ occur infinite IllegalstateException in 3.6.1

Hi,
I'm getting an infinite loop of illegal state exception when I try to add data concurrently using
Entryprocessor. I will stop at last crashing the server. What can I do it skip this exception in 3.6.1
Of C++ release.
Thanks and regards,
Sura

Similar Messages

Problem in continuous query cache with PofExtractor

Hi,
I am creating a CQC with a filter having PofExtractor. When I try to insert any record in cache it is giving me exception at server side.
When I do not use PofExtractor it is working fine.
If any one know about this prblem please help.
I am using C# as my client application
Regards
Nitin Jain

Hi JK,
I have made some changes in my server. Now I am not using any pof definition on server side. I think that's why it is giving me the error.
2010-04-13 15:39:07.481/20.593 Oracle Coherence GE 3.5.1/461 <Error> (thread=DistributedCache, member=1): Exception occured during filter evaluation: MapEventFilter(mask=INSERTED|UPDATED_ENTERED|UPDATED_WITHIN, filter=GreaterEqualsFilter(PofExtractor(target=VALUE, navigator=SimplePofPath(indices=0)), Nitin)); removingthe filter...
2010-04-13 15:39:07.481/20.593 Oracle Coherence GE 3.5.1/461 <Error> (thread=DistributedCache, member=1):
(Wrapped) java.io.StreamCorruptedException: unknown user type: 1001
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:261)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ConverterFromBinary.convert(DistributedCache.CDB:4)
at com.tangosol.util.ConverterCollections$ConverterMapEvent.getNewValue(ConverterCollections.java:3594)
at com.tangosol.util.filter.MapEventFilter.evaluate(MapEventFilter.java:172)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.prepareDispatch(DistributedCache.CDB:82)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.postInvoke(DistributedCache.CDB:10)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.put(DistributedCache.CDB:156)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onPutRequest(DistributedCache.CDB:37)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$PutRequest.run(DistributedCache.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:12)
at com.tangosol.coherence.component.net.message.requestMessage.distributedCacheKeyRequest.ExtendedKeyRequest.onReceived(ExtendedKeyRequest.CDB:4)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:9)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:136)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.StreamCorruptedException: unknown user type: 1001
at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3289)
at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2600)
at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:348)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2673)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:257)
... 15 more
Is there any way by which we can apply continuous query cache without providing object definition at server side?
Regards
Nitin Jain

Continuous Query Caching - Expensive?

Hello,
I have had a look at the documentation but I still cannot find a reasonable answer to the following question : How expensive are continuous query caches?
Is it appropriate to have many of them?
Is the following example an acceptable usage of Continuous query caching (does it scale?)
In the context of a web application:
User logs onto a website
User performs a "Search" for financial instruments
A continuous query cache is created with a filter for those instruments returned (say, 50) to listen to price updates.
If the user pages, or does another search, the query cache is released and a new one, with an updated filter, is created.
Does it make a difference if we are using the extend client?

Hi,
So 100 CQCs is probably not too excessive depending on the configuration of the process instantiating the CQCs and the cluster size etc.
Each CQC will hold its own set of deserialized keys and values, so yes they are distinct objects, although a CQC of 50 entries would not be very big.
One query I have - you mention that this is a Web Application but you also mention an Extend Client. Is your Web App and Extend Client of the main cluster? Is there are reason why you did this, most people would make a Web App a storage disabled cluster member so it would perform a bit better. Providing the Web App sits on a server that is very close in network terms to the cluster (i.e. same switch) then I would make it part of the cluster - or is the Web App the thing that is in the "regional environment".
If you are running CQCs over Extend then there used to be some issues with this if the Extend connection was lost. AFAIK this is supposed to be fixed in later patches so I would get 3.7.1.8 and make sure you test that the Web App continues to work and properly fails over if you kill its Extend connection. When the CQC fails over it will reinitialize all its data so you will need to cope with that if you are pushing changes based on the CQC.
JK

Missed and duplicate events with Continues Query Cache

We have seen missed events and duplicate events when we register to receive events (using Continues Query Cache) on an entry in the cache while the entry is updating.
Use case:
Start a Node
Start a Proxy
Start Extend Client
Implementation of the Extend Client
Create Cache
Add Entry to Cache
Initiate Thread 1 {
      For each ( 1 to 30)
          Run Update Entry Processor on cache entry; Entry Processor increments the Cache Entry value by 1
Initiate Thread 2 {
     wait until Cache entry is updated 10 times
     Create MAP Listener {
          For Entry Insert Event {
                        Print event
               set Initial value = new value
          For Entry Update Event {
                        Print event
               set Update value = + 1
     Initiate Continues Query Cache (cache, Always Filter, MAP Listener)
Start Thread 1
Start Thread 2
Waits until Thread 1 and Thread2 are terminated
Expected Result = read the value of the entry from cache
Actual result = Initial value + Update value
Results we have seen in two tests_
Test1: Expected Result > Actual results: Missing events
Entry Inserted Event: MapEvent{ContinuousQueryCache inserted: key=1, value=UpdateObject [intNumber=1, longNumber=13]}
+Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=13], new value=UpdateObject [intNumber=1, longNumber=15]}+*
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=15], new value=UpdateObject [intNumber=1, longNumber=16]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=16], new value=UpdateObject [intNumber=1, longNumber=17]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=17], new value=UpdateObject [intNumber=1, longNumber=18]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=18], new value=UpdateObject [intNumber=1, longNumber=19]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=19], new value=UpdateObject [intNumber=1, longNumber=20]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=20], new value=UpdateObject [intNumber=1, longNumber=21]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=21], new value=UpdateObject [intNumber=1, longNumber=22]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=22], new value=UpdateObject [intNumber=1, longNumber=23]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=23], new value=UpdateObject [intNumber=1, longNumber=24]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=24], new value=UpdateObject [intNumber=1, longNumber=25]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=25], new value=UpdateObject [intNumber=1, longNumber=26]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=26], new value=UpdateObject [intNumber=1, longNumber=27]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=27], new value=UpdateObject [intNumber=1, longNumber=28]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=28], new value=UpdateObject [intNumber=1, longNumber=29]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=29], new value=UpdateObject [intNumber=1, longNumber=30]}
Expected Result: 30
Actual Result: 29
Issue:+ Event on 14th update was not sent
Test 2: Expected Result < Actual Result: Duplicate events
Entry Inserted Event: MapEvent{ContinuousQueryCache inserted: key=1, value=UpdateObject [intNumber=1, longNumber=13]}
*Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=13], new value=UpdateObject [intNumber=1, longNumber=13]}*+
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=13], new value=UpdateObject [intNumber=1, longNumber=14]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=14], new value=UpdateObject [intNumber=1, longNumber=15]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=15], new value=UpdateObject [intNumber=1, longNumber=16]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=16], new value=UpdateObject [intNumber=1, longNumber=17]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=17], new value=UpdateObject [intNumber=1, longNumber=18]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=18], new value=UpdateObject [intNumber=1, longNumber=19]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=19], new value=UpdateObject [intNumber=1, longNumber=20]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=20], new value=UpdateObject [intNumber=1, longNumber=21]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=21], new value=UpdateObject [intNumber=1, longNumber=22]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=22], new value=UpdateObject [intNumber=1, longNumber=23]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=23], new value=UpdateObject [intNumber=1, longNumber=24]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=24], new value=UpdateObject [intNumber=1, longNumber=25]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=25], new value=UpdateObject [intNumber=1, longNumber=26]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=26], new value=UpdateObject [intNumber=1, longNumber=27]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=27], new value=UpdateObject [intNumber=1, longNumber=28]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=28], new value=UpdateObject [intNumber=1, longNumber=29]}
Entry Updated Event: MapEvent{ContinuousQueryCache updated: key=1, old value=UpdateObject [intNumber=1, longNumber=29], new value=UpdateObject [intNumber=1, longNumber=30]}
Expected Result: 30
Actual Result: 31
Issue:+ Event on 13th update was sent in Insert and Update events both
reg
Dasun.

Hi Paul,
I tested with 3.7.1.4 and 3.7.1.5. In both versions I can see the issue.
reg
Dasun.

Continuous Query Cache Local caching meaning

Hi,
I'm enconter following problem when I was working with continuous query cache with local caching TRUE.
I was able to insert data into coherence cache and read as well.
Then I stopped the process and try to read the data in the cache for keys which I inserted earlier.
But I received NULL as the result.
NamedCache::Handle hCache = DerivedCQC::create(CacheFactory::getCache("dist-AccountGCE"), AlwaysFilter::getInstance(), true);
DerivedCQC.hpp
* File: DerivedCQC.hpp
* Author: srathna1
* Created on 15 July 2011, 02:47
#ifndef DERIVEDCQC_HPP
#define DERIVEDCQC_HPP
#include "coherence/lang.ns"
#include "coherence/net/cache/ContinuousQueryCache.hpp"
#include "coherence/net/NamedCache.hpp"
#include "coherence/util/Filter.hpp"
#include "coherence/util/MapListener.hpp"
using namespace coherence::lang;
using coherence::net::cache::ContinuousQueryCache;
using coherence::net::NamedCache;
using coherence::util::Filter;
using coherence::util::MapListener;
class DerivedCQC
: public class_spec<DerivedCQC,
extends<ContinuousQueryCache> >
friend class factory<DerivedCQC>;
protected:
DerivedCQC(NamedCache::Handle hCache,
Filter::View vFilter, bool fCacheValues = false, MapListener::Handle hListener = NULL)
: super(hCache, vFilter, fCacheValues, hListener) {}
public:
virtual bool containsKey(Object::View vKey) const
return m_hMapLocal->containsKey(vKey);
#endif /* DERIVEDCQC_HPP */
When I switch off the local storage flag to FALSE.
I was able to read the data.
NamedCache::Handle hCache = DerivedCQC::create(CacheFactory::getCache("dist-AccountGCE"), AlwaysFilter::getInstance(), false);
Ideally I'm expecting in true scenario when I'm connected with coherence all keys and values with locally synced up with cache and store it locally and for each update also it will get synched up.
In false scenario it will hook into the coherence cache and read it from their for each key and cache values from that moment onwards. Please share how it is implemented underneath
Thanks and regards,
Sura

Hi Wei,
I found the issue when you declare you cache as an global variable then you won't get data in TRUE scenario and if you declare the cache during a method then you will retrieve data.
Try this.......
#include <iostream>
#include <coherence/net/CacheFactory.hpp>
#include "coherence/lang.ns"
#include <coherence/net/NamedCache.hpp>
#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>
#include <coherence/net/cache/ContinuousQueryCache.hpp>
#include <coherence/util/filter/AlwaysFilter.hpp>
#include <coherence/util/filter/EntryFilter.hpp>
#include "DerivedCQC.hpp"
#include <fstream>
#include <string>
#include <sstream>
#include <coherence/util/Set.hpp>
#include <coherence/util/Iterator.hpp>
#include <sys/types.h>
#include <unistd.h>
#include <coherence/stl/boxing_map.hpp>
#include "EventPrinter.hpp"
using namespace coherence::lang;
using coherence::net::CacheFactory;
using coherence::net::NamedCache;
using coherence::net::ConcurrentMap;
using coherence::net::cache::ContinuousQueryCache;
using coherence::util::filter::AlwaysFilter;
using coherence::util::filter::EntryFilter;
using coherence::util::Set;
using coherence::util::Iterator;
using coherence::stl::boxing_map;
NamedCache::Handle hCache = DerivedCQC::create(CacheFactory::getCache("gce-Account"), AlwaysFilter::getInstance(), true);
int main(int argc, char** argv) {
std::cout << "size: " << hCache->size() << std::endl;
in above example you will see size is 0 for true case and size is equal to data size in the cache in false scenario.
But if you declare the cache as below you will get the expected results as the documentation.
int main(int argc, char** argv) {
NamedCache::Handle hCache = DerivedCQC::create(CacheFactory::getCache("gce-Account"), AlwaysFilter::getInstance(), true);
std::cout << "size: " << hCache->size() << std::endl;
Is this a bug or is this the expected behaviour. According to my understanding this is a bug?
Thanks and regards,
Sura

Is a continuous query aggregator possible?

How can I make something like this a continuous query so I'm constantly aware of the count of working Orders in the orderCache?
Filter f2 = new EqualsFilter("isWorking", true);
Integer workingOrdersCount = (Integer)orderCache.aggregate(f2, new com.tangosol.util.aggregator.Count() );Thanks,
Andrew

Hi Andrew,
We do not have a continuous aggregator at this time. The specific use case you suggest could be accomplished by maintaining a continuous query cache (CQC) and calling it's size() method. The resource consumption of the CQC can be kept to a minimum by configuring it to only cache the matching keys, and to not hold the values.
thanks,
mark
Coherence Development Team

SAP BW 3.5 Query Cache - no data for queries

Dear experts,
we do have a problem with the SAP BW Query Cache (BW 3.5). Sometimes the
problem arise that after the queries have been pre-calculated using web templates there are no figures available when running a web-report, or when doing a drilldown or filter navigation. A solution to solve that issue is to delete the cache for that query, however this solution is not reasonable or passable. The problem occurs non-reproducible for different queries.
Is this a "normal" error of the SAP BW we have to live with, or are there any solutions for it? Any hints are greatly appreciated.
Thanks in advance & kind regards,
daniel

HI Daniel
Try to wirk without cache for those queries.
Anyway, you should check how the cache option is configured for those queries .
You can see that, in RSRV tx
Hope this help

Coherence-Extend and Continuous Query performance

Hi,
I am trying to evaluate the performance impact of continous queries, when using coherence extend (TCP). The idea is that desktop clients will be running continuous queries against a cluster, and other processes will be updating the data in that cluster. The clients themselves take a purely read-only view of the data.
In my tests, I find that the updater process takes about 250ms to update 5000 values in the cache (using a putAll operation). When I have a continuous query running against a remote cache, linked with coherence extend, the update time increases to about 1500ms. This is not CPU bound.
Is this what people would expect?
If so this raises questions to me about:
1) slow subscribers - what if one of my clients is very badly behaved? Can I detect this and/or take action?
2) conflation of updates - can Coherence do conflation?
3) can I get control to send object deltas over the wire rather than entire objects?
Is this a use case for which CoherenceExtend and continuous queries were designed?
Robert

Yes, it is certainly possible, although depending on your requirements it may be more or less additional coding. You have a few choices. For example, since you have a CQC on the cache, you could conceivably aggregate locally (on any event). In other words, since all the data are local, there is no need to do the parallel aggregation (unless it is CPU limited). Depending on the aggregation, you may only have to recalculate part of it.
You can access the internal data structure (Map) within the CQC as follows:
Map map = cqc.getInternalCache();
// now we can do aggregation
NamedCache cache = new WrapperNamedCache(map);
cache.aggregate(..);More complex approaches would only recalculate portions based on the event, or (depending on the function) might use the event to adjust the aggregated results.
Peace,
Cameron Purdy | Oracle Coherence
http://coherence.oracle.com/

Query Cache Behavior

Hi Experts,
I'm running 12.0.5, and have enjoyed 6 months or more of uptime for our production server, until Thursday when an electrical strom coupled with an odd occurance with our UPS system brought it to an abrupt halt.
Dev and Test environments came up OK, however the icon related to the J2EE server on production remained yellow. We were unable to access MII, or NWA for that matter.
I handed the problem over to our Basis team, who couldn't figure it out then passed a note to SAP. While waiting for a response, I decided to do some more poking around, as it was now 8:00pm Friday night and any hope of doing anything over the weekend (other than work) was quickly fading.
Poking around in the NW database, I found that the XMII_QUERYCACHE table had >2.5M rows (that seemed odd). Initital attempts to Truncate the table were unsuccessful (something about resources and NOWAIT, should have captured that error), however I was able to Truncate by shutting down the server, then executing just as the database was starting, and VOILA!, NW and MII came online.
My assumption is that either the table is read on startup, or perhaps an attempt is made to 'delete' all rows on startup (delete would attempt to build a rollback segment in order to execute), is that the case? Also, are 'expired' cache entries supposed to be hanging around?
I found that I have a single frequently executed query that was the culprit, query caching was enabled with a duration of 2Hours (many jobs use this query). I'll correct that situation, but I wanted to try and correct the root cause.
Thanks,
Rod

I entered a ticket and just received a resolution from SAP, as follows..
We have added this feature in both MII 12.0 and MII 12.1.
The changes will be available with next SP release on SAP Service
Marketplace.
MII 12.0 SP12 will be available on 15-Dec-2010.
My assumption is that there will be a system job that clears out expired query cache rows at some frequency, nightly maybe.
Wanted to update the thread with the resolution in case anyone was having the same problem.
Rod

Reducing Database Call Techniques...query caching the only way?

What's the most efficient way to reuse data that gets called on practically every page of an application?
For instance, I have a module that handles all my gateways, sub pages and subgateways etc etc. This will only change whenever a change is made to the page structure in the admin portion of the application. It's really not necessary to hit the database everytime a page loads. Is this a good instance to use query caching? What are the pros, cons and alternatives? I thought an alternative might be to store in a session, but that doesn't sound too ideal.
Thanks!
Paul

What's the most efficient way to reuse data that gets called on practically every page of an application?
That sounds like a question from the certification exam. The answer is to store the data in session or applicaton scope, depending on the circumstances. If the data depends on the user, then the answer is session. If the data persists from user to user, then it is application.
admin portion of the application.
Suggests users must log in. Otherwise you cannot distinguish admin from non-admin.
This will only change whenever a change is made to the page structure in the admin portion of the application.
Then I would go for storing the data in application scope, as the admin determines the value for everybody else. However, the session acope also has something to do with it. Since the changes are only going to occur in the admin portion, I would base everything on a variable, session.role.
You cache the query by storing it directly in application scope within onApplicationStart in Application.cfc, like this:
<cfquery name="application.myQueryName">
</cfquery>
The best place for the following code is within onSessionStart in Application.cfc.

<cfif session.role is 'admin'>

</cfif>
Added edit: On second thought, the best place for setting the application variable is in onApplicationStart.

BW3.5 - Query Cache - InfoObject decimal formatting

Hello all,
I built a bw query, which displays key figures. Each key figure uses the decimal place formatting from the key figure infoobject (In Query Designer, the properties for each keyfigure for Decimal places, is set to "[From Key Figure 0.00]").
I decided to change the InfoObject key figure to have 0 decimals places (in BEx formatting tab for the Key Figure). Now, when I open up query designer, and look at the properties for the Key figure, it still is set to "[From Key Figure 0.00]" (it should be "[From Key Figure 0]" to reflect the Key Figure Infoobject change.
I tried to generate the report using RSRT, and deleting the query cache, but it still shows up with two decimal places. Has anyone encountered this problem before? I am trying to avoid removing the Key Figure infoobject from the query and readding it to reflect the change.
Thanks!

Hello Brendon
You have changed the KF infoObject to show only 0 decimal( no decimal)..that is okay but in query KF property you have selected with 2 decimal so data will be displayiing in 2 decimal...the query setting is local and have priority over KF InfoObject settings...
If you notice in KF property in query u will have one option from the field somethjing which means whatever is defined by KF infoObject...just select that now onwards u will get only those many decimal which u have defined in KF InfoObject
Thanks
Tripple k

VO Auto Refresh error - Unsupported query for Continuous Query Notification

I created a read only view object and set the auto refresh property to true. According to the documentation that was all that need to be done in order to enable auto-refresh for a view instance of a shared application module (which I am using to retrieve reference data). When I run a test, I get the following error:
[371] DCBindingContainer.reportException :oracle.jbo.SQLStmtException
[372] oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT
CCIPO_REF_SENSITIVITY_LEVEL.SENSITIVITY_ID SENSITIVITY_ID,
CCIPO_REF_SENSITIVITY_LEVEL.SENSITIVITY_DESC SENSITIVITY_DESC
FROM
CCIPO_REF_SENSITIVITY_LEVEL
     at oracle.jbo.server.BaseSQLBuilderImpl.processException(BaseSQLBuilderImpl.java:3721)
     at oracle.jbo.server.OracleSQLBuilderImpl.processException(OracleSQLBuilderImpl.java:4722)
     at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:1386)
     at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:928)
     at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:6968)
     at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:1183)
     at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:1037)
     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2774)
     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2751)
     at oracle.jbo.server.ViewRowSetIteratorImpl.first(ViewRowSetIteratorImpl.java:1580)
     at oracle.jbo.server.ViewRowSetImpl.first(ViewRowSetImpl.java:3500)
     at oracle.jbo.server.ViewObjectImpl.first(ViewObjectImpl.java:9943)
     at oracle.adf.model.binding.DCIteratorBinding.setupRSIstate(DCIteratorBinding.java:779)
     at oracle.adf.model.binding.DCIteratorBinding.refreshControl(DCIteratorBinding.java:679)
     at oracle.jbo.uicli.binding.JUIteratorBinding.refreshControl(JUIteratorBinding.java:474)
     at oracle.adf.model.binding.DCIteratorBinding.refresh(DCIteratorBinding.java:4437)
     at oracle.adf.model.binding.DCExecutableBinding.refreshIfNeeded(DCExecutableBinding.java:347)
     at oracle.adf.model.binding.DCIteratorBinding.getRowSetIterator(DCIteratorBinding.java:1605)
     at oracle.jbo.jbotester.panel.BindingPanel.setBindingContext(BindingPanel.java:116)
     at oracle.jbo.jbotester.panel.BindingPanel.<init>(BindingPanel.java:88)
     at oracle.jbo.jbotester.panel.BindingPanel.<init>(BindingPanel.java:71)
     at oracle.jbo.jbotester.form.BindingForm.createMasterPanel(BindingForm.java:63)
     at oracle.jbo.jbotester.form.BindingForm.init(BindingForm.java:98)
     at oracle.jbo.jbotester.form.JTForm.<init>(JTForm.java:72)
     at oracle.jbo.jbotester.form.BindingForm.<init>(BindingForm.java:50)
     at oracle.jbo.jbotester.form.FormType$1.createForm(FormType.java:63)
     at oracle.jbo.jbotester.form.FormType.createForm(FormType.java:199)
     at oracle.jbo.jbotester.form.FormType.createTab(FormType.java:270)
     at oracle.jbo.jbotester.form.FormType.showForm(FormType.java:248)
     at oracle.jbo.jbotester.form.FormType.showForm(FormType.java:207)
     at oracle.jbo.jbotester.form.FormType.showForm(FormType.java:203)
     at oracle.jbo.jbotester.tree.ObjTreeNode.showForm(ObjTreeNode.java:140)
     at oracle.jbo.jbotester.tree.ObjTreeNode.showForm(ObjTreeNode.java:123)
     at oracle.jbo.jbotester.tree.Tree.processTreeMouseClicked(Tree.java:728)
     at oracle.jbo.jbotester.tree.Tree.access$100(Tree.java:96)
     at oracle.jbo.jbotester.tree.Tree$TreeMouseListener.mouseClicked(Tree.java:141)
     at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:253)
     at java.awt.Component.processMouseEvent(Component.java:6292)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
     at java.awt.Component.processEvent(Component.java:6054)
     at java.awt.Container.processEvent(Container.java:2041)
     at java.awt.Component.dispatchEventImpl(Component.java:4652)
     at java.awt.Container.dispatchEventImpl(Container.java:2099)
     at java.awt.Component.dispatchEvent(Component.java:4482)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4247)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
     at java.awt.Container.dispatchEventImpl(Container.java:2085)
     at java.awt.Window.dispatchEventImpl(Window.java:2478)
     at java.awt.Component.dispatchEvent(Component.java:4482)
     at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
     at java.awt.EventQueue.access$000(EventQueue.java:85)
     at java.awt.EventQueue$1.run(EventQueue.java:603)
     at java.awt.EventQueue$1.run(EventQueue.java:601)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
     at java.awt.EventQueue$2.run(EventQueue.java:617)
     at java.awt.EventQueue$2.run(EventQueue.java:615)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.sql.SQLException: ORA-29983: Unsupported query for Continuous Query Notification
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:924)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1261)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1419)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3806)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1667)
     at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:1262)
     ... 65 more
The query is selecting two varchar2 columns and according to the criteria in the documentation is valid to be registered for QRCN in Guaranteed Mode. Any thoughts?
JDev version: JDeveloper 11.1.1.5.0.

Well, could be a DB bug. I seem to remember that there was a bug in that area in an older version of 11g.
Or you could use jnettrace to trace the calls made by the driver to the DB. That should show you what's going wrong.
Sascha

Issues with Query Caching in MII

Hi All,
I am facing a strange problem with Query caching in MII query. Have created one xacute query and set cache duration 30 sec. The associated BLS with the query retrieves data from SAP system. In the web page this value is populated by executing an iCommand. Followings are the steps I followed -
Query executed for first time, it retrives data from SAP correctly. Lets say value is val1
At 10th sec Value in SAP changed to val2 from val1.
Query excuted at 15th sec, it gives value as val1. Which is expected as it gives from cache.
Query is executed 1t 35th sec, it gives value as val2 retriving from SAP system. Which is correct.
Query executed at 40th sec, it gives value as val1 from cache. Which is not expected.
I have tried with java cache clear in browser and JCo cache of the server.
Same problem I have seen for tag query also..
MII Version - 12.0.6 Build(12)
Any thoughts on this.
Thanks,
Soumen

Soumen Mondal,
If you are facing this problem from the same client PC and in the same session, it's very strange.. but if there are two sessions running on the same PC this kind of issue may come..
Something about caching:
To decide whether to cache a query or not, consider the number of times you intend to run the query in a minute. For data changing in seconds, and queried in minutes, I would recommend not to cache query at all.
I may give a typical example for query caching in a query on material master cached for 24 hours, where we know that after creating material master, we are not creating a PO on the same day.
BR,
SB

Named query cache not hit

Hi,
I'm using Toplink ORM 10.1.3.
I have a table called STORE_CONFIG which has a primary key called KEYWORD (a VARCHAR2). The POJO mapped to this table is called StoreConfig.
In the JDeveloper (10.1.3.1.0) mapping workbench I've defined a named query to query by the PK called "getConfigPropertyByKeyword". The type of the named query is ReadObjectQuery.
SELECT keyword, key_value
FROM STORE_CONFIG
WHERE (keyword = #key)
Under the options tab I have the following settings:
Cache Statement: true
Bind Parameters: true
Cache Usage: Check Cache by Primary Key
The application logs show that the same database queries are executed multiple times for the same PK (keyword)! Why is that? Shouldn't it be checking the Object Cache rather than going to the DB?
I've tried it with "Cache Statement: false" and "Bind Parameters: false" with the same problem.
If I click the Advanced tab and check "Cache Query Results" then the database is not hit twice for the same record. However it was my understanding that since I am querying by PK that I wouldn't need to set "Cache Query Results".
Doesn't "Cache Query Results" apply to the Query Cache and not the Object Cache?

Your issue seems to be that you are using custom SQL for the query, not a TopLink expression. When you use an Expression query TopLink's know if the query is by primary key and can get a cache hit.
When you use custom SQL, TopLink does not know that the SQL is by primary key, so does not get a cache hit.
You could either use an Expression for the query,
or when using custom SQL you should be able to name your query argument the same as your database field defined as the primary key in your descriptor (case sensitive).
i.e.
SELECT keyword, key_value
FROM STORE_CONFIG
WHERE (keyword = #KEYWORD)

ORA-29983: Unsupported query for Continuous Query Notification

Hi, i'm having a LOV with auto refresh. If i add "Order by " to the LOV query , the following exception is thrown.
SQL error during statement preparation. Statement: SELECT * FROM (SELECT DISTINCT XXXX FROM YYYY) QRSLT ORDER BY "XXXX"
Error ORA-29983: Unsupported query for Continuous Query Notification
I tried to override the create method of the VO, with "this.setNestedSelectForFullSql(false);" .. But this one disables the auto referesh property...
Could some one help to solve this. Thanks .

Hi, i looked into the ADF run-time source code and i can see that , the connection object " OracleDatabaseChangeListenerWrapper" class setting the mode as "BEST_EFFORT".
I would assume , by default adf run-time using the best effort mode , not the guaranteed mode.
The data base doc also says in best effort mode "order by" clause as well as key word "like" can be used for continuous query notification. But still i'm getting "ORA-29983".
Could some one clarify me. Thanks .

Continuous query cache in c++ occur infinite IllegalstateException in 3.6.1

Similar Messages

Maybe you are looking for