Fraska Portal

Exploring the WebSphere Commerce world

In a cluster, most of the times we need to make an investigation based on LOG's rendering, we have to know in which node is going our request stated in the Front End. With multiple nodes, the troubleshooting can be annoying if we have to check every time the log of each node and see if our requested got this node. 

The best way to face this kind of investigations is understand exactly which node is elaborating our request. To get this info we need to have a look at the sessions cookies, in particular at the JSESSIONID.

Most Popular Post

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
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5

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