• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Classloader, Singleton, Weblogic 8.1 sp4--HELP!

Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I have searched the forum and did not see this question answered, so I am posing it to the group. My application was successful under WebLogic 8.1 with sp2. However, we moved the application to WebLogic 8.1, sp4 and it failed to deploy properly.

When I go look at the code where the deployment is failing, it fails on the section of code that was previously worked, such as ClassEJB.getKey(). When I go looking in the method, the only line change within the method was obtaining a Singleton cacheManager object.

This is from the application logs

This is from the server log:

Could someone point me in the correct direction on solving this issue? From what I have read it appears to be a classloader issue. The Singleton class is not fully active because the application ejbs are loaded first. Therefore the Singleton class had not beeen loaded.

Is there a workaround around this issue in WebLogic? I do not face this issue in WebSphere.

Thank you in advance for taking the time to read my post.


Every snowflake is perfect and unique. And every snowflake contains a very tiny ad.
a bit of art, as a gift, the permaculture playing cards
    Bookmark Topic Watch Topic
  • New Topic