Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

BEA-100049 with wl 8.1

 
charlie silver
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I've been checking my logs and I have this error message all over the place:

<Error> <HTTP Session> <BEA-100049> <Error looking up session with id:JlTD5GGBL8FpgGnTygcr0HvXLpG1sD38BWvFJyR0v
73DdMyjy2FY!404149623!NONE
java.lang.NullPointerException


I reviewed BEA edocs and they only got this information for this error:

BEA-100049

Error: Error looking up session with id:id

Description

Error looking up session with id:id - session refresh failed
Cause

Got RemoteException looking up session from the secondary
Action

Check if the secondary server is down. Note that it is not recommended to kill both the primary and secondary server at the same time. Remember the replication happens lazily, upon request. So if you need to bring down the secondary server too give sufficient time so that the active end users hit their sessions and they get replicated.

But that does not tell me the possible causes of this in my environment. I know that anything could be the root cause of this problem, that it depends on many factors, all of them tied to my specific environment, but is there a general or basic cause of this problem?

Any comment is highly appreciated.

Thanks
 
Hareesh Ram Chanchali
Ranch Hand
Posts: 110
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Will you be able to see that these message time stamps has some pattern?
Like at a specific time ? Any idea if your Managed servers are being shutdown abruptly? seems to be mostly a message in Fail-over scenario.
 
Dongyun Tian
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is cluster´╝čdo you config session replicated in you app?
the log seems to tell you that you put a object in session in the first server,when you get the object's value form the second server when the first one is going down.
add
<session-descriptor>

<session-param>

<param-name>PersistentStoreType</param-name>

<param-value>replicated</param-value>

</session-param>

</session-descriptor>

in your weblogic.xml(between <weblogic-web-app> </weblogic-web-app>),but it must be cluster env.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic