Monitoring clustered level 2 cache invalidation for Hibernate / JBossCache in EAP 5

Solution Unverified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 5
  • Hibernate 3
  • JBossCache

Issue

  • Trace inbound / outbound communication between clustered servers for level 2 cache (L2C) invalidation
  • Need to verify that L2C entity invalidation messages are broadcast and received by other nodes in a cluster

Resolution

Enable TRACE for org.jboss.cache and org.jgroups (captures the most information) or narrow TRACE to the following categories:

  • org.jgroups.protocols.UDP
  • org.jboss.cache.marshall
  • org.jboss.cache.interceptors
  • org.jboss.cache.lock
  • org.jboss.cache.commands.write.InvalidateCommand

Diagnostic Steps

Outbound Log Entries

... TRACE [org.jgroups.protocols.UDP] (<thread-id>) sending msg to null, src=99.99.99.99:55200, headers are MsgDisp: [Header: name=MsgDisp, type=REQ, id=1431584101628, rsp_expected=true], dest_mbrs=[99.99.99.99:55200], NAKACK: [MSG, seqno=3121], UDP: [channel_name=MY-CLUSTER-mvcc-entity]

Inbound Log Entries

... TRACE [org.jgroups.protocols.UDP] (<thread-id>) message is [dst: <null>, src: 99.99.99.99:55200 (3 headers), size=927 bytes], headers are MsgDisp: [Header: name=MsgDisp, type=REQ, id=1431584101628, rsp_expected=true], dest_mbrs=[99.99.99.99:55200], NAKACK: [MSG, seqno=3121], UDP: [channel_name=MY-CLUSTER-mvcc-entity]
...
... TRACE [org.jboss.cache.commands.write.InvalidateCommand] (<thread-id>) Invalidating fqn:/persistence.unit: unitName=my.ear/my.jar#MyPersistenceUnit/...org.myorg.MyEvent#1168584
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.