posted 14 years ago
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