Fraska Portal

Exploring the WebSphere Commerce world

The WebSphere Dynacache- the main tool WebSphere integrates for caching strategies- can be imagined like an HashTable stored in the JVM Heap, with disk offload options and rules defined for retrieve and invalidate objects. In addition, Dynacache is supported in a cluster environment using the Distribute Replication Service- DRS.

The invalidation is a powerful feature of Dynacache but sometimes- like in the case I'm reporting- it has its logic split between XML configuration and JSP coding.

In particular, I refer to the fragments invalidation. Let's take the following example:

  • JSP Page (root): page1.jsp
    • Fragment 1 (1st level child): fragment1.jspf
      • Fragment 2 (2nd level child): fragment2.jspf

In terms of code, page1.jsp will have something like:

...

<% out.flush() %>
<c:import file="${filedir}page1.jsp"/>
<% out.flush() %>

...

and so do fragment1.jspf. 

In addition, cachespec.xml will have the following configuration:

<class>servlet</class>
		<name>/directory/page1.jsp</name>
		<property name="do-not-consume">true</property>
		<property name="save-attributes">false</property>
		<property name="consume-subfragments">true</property>
...

The problem: despite the configuration is the IBM's InfoCenter suggested one, the fragments do not seem to be invalidated properly. In other words, when something changes in the fragments page1.jsp does not change at all.

Posted by on in Data Load

If you need to populate the Commerce User's Wish List you cannot demand it to an Out Of The Box Business Mediator (like it happens- for example- with Catalog Entries, Prices or Attribute Dictionaries) but you will need to use a generic TableObjectBuilder/TableObjectMediator.

Posted by on in Data Load

How to handle the Data Load process- without customize OOB WCS component- when CSV source data is complex and unstructured

In some cases the WCS Data Load could be really painful if the source data- typically deriving from .CSV files- is quite different from Commerce's one.

Suggested reading: Definitions of Thread, Pool, DeadLock and Hung in WebSphere Application Server 

How to investigate deadlock issues

  1. Collect javacores;
  2. Look for deadlock messages
  3. Look for threads in waiting status
  4. Look for threads owns monitor lock
  5. Compare threads and compare monitors

 

Most Popular Post

WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5
WebSphere Commerce, the SOLR extension index
Administration
Rate this blog entry:
4
WebSphere Commerce, Data Load and SOLR Delta Index
Data Load
Rate this blog entry:
0

Latest Blogs

WebSphere Commerce, CommandLevelAuthorizationCache
Cache
Rate this blog entry:
0
WebSphere Commerce v8, toolkit exception, ClassNotFound db2
Administration
Rate this blog entry:
1
WebSphere Commerce, ATP migration
Store
Rate this blog entry:
0
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5
WebSphere Commerce, Performance analysis of few European stores
Performance
Rate this blog entry:
0