Topic
2 replies Latest Post - ‏2011-03-24T14:37:39Z by Nogu
eBolor
eBolor
24 Posts
ACCEPTED ANSWER

Pinned topic "DynamicCache naming not found exception" after migrating Trade application

‏2011-02-23T07:20:29Z |
Hello everyone.

We are testing migration from WAS ND V6.1 to WAS ND V8.0.
WAS V6.1 environment consisted of Dmgr01, Custom01 profiles (on machine 1) and Custom12 profile (on machine 2).
Application"Trade 6" was deployed on Server21 and Server22 cluster of Custom12 profile. Application uses DB2.

After migration, application "Trade 6" is working, but a warning FFDC warning is shown SystemOut.log of in Server21 and Server22, as below.
FFDC log shows DynamicCache naming not found exceptions.

SystemOut.log of Server21:
2/23/11 15:53:20:880 JST 00000042 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/IBM64/WebSphere80/AppServer/profiles/Custom12/logs/ffdc/Server21_14921492_11.02.23_15.53.20.8575257090687458112174.txt com.ibm.websphere.cache.DynamicCacheAccessor.getDistributedMap 99

Server21_14921492_11.02.23_15.53.20.8575257090687458112174.txt:
2/23/11 15:53:20:878 JST FFDC Exception:javax.naming.NameNotFoundException SourceId:com.ibm.websphere.cache.DynamicCacheAccessor.getDistributedMap ProbeId:99 Reporter:java.lang.Class@60dd60dd
javax.naming.NameNotFoundException: Context: Cell01/clusters/Cluster2, name: services/cache/basecache: First component in name basecache not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0

SystemOut.log of Server22:
2/23/11 15:54:05:769 JST 00000040 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/IBM64/WebSphere80/AppServer/profiles/Custom12/logs/ffdc/Server22_2a132a13_11.02.23_15.54.05.7604450528604334750659.txt com.ibm.websphere.cache.DynamicCacheAccessor.getDistributedMap 99

Server22_2a132a13_11.02.23_15.54.05.7604450528604334750659.txt:
2/23/11 15:54:05:767 JST FFDC Exception:javax.naming.NameNotFoundException SourceId:com.ibm.websphere.cache.DynamicCacheAccessor.getDistributedMap ProbeId:99 Reporter:java.lang.Class@65566556
javax.naming.NameNotFoundException: Context: Cell01/clusters/Cluster2, name: services/cache/basecache: First component in name basecache not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Is this FFDC exception a problem? Was there some change in WAS V8.0 dynamic cache? Or is there a problem with migrating "Trade 6" application?

Please have a look at "newest_cell.zip" for "logs" directories of Dmgr, Custom1, and Custom2 profiles, for details.

Anyone who has information regarding this, please let us know.

We appreciate your help
Updated on 2011-03-24T14:37:39Z at 2011-03-24T14:37:39Z by Nogu
  • StevenSchader
    StevenSchader
    12 Posts
    ACCEPTED ANSWER

    Re: "DynamicCache naming not found exception" after migrating Trade application

    ‏2011-02-23T20:15:07Z  in response to eBolor
    Hello,
    I'm checking into this issue.

    Steven.
    • Nogu
      Nogu
      9 Posts
      ACCEPTED ANSWER

      Re: "DynamicCache naming not found exception" after migrating Trade application

      ‏2011-03-24T14:37:39Z  in response to StevenSchader
      Hello,

      I am one of eBolor's coworkers.
      Can you tell me if you have identified the problem ?

      Thanks. Nogu.