Re: retiring of application version causes application to be

This sounds like a bug. I would suggest a support case.

<Risto Urb> wrote in message news:300015018@newsgroups.bea.com...
We use the WebLogic-Application-Version in the manifest file to version our 
application war files. The "silent updating process" is being done
using WLS 
console. Usually updating the application succeeds - the old version retires 
after specified amount of seconds - but a few days ago we ran into a 
problem.

After the update was complete, the new version went into ACTIVE state. The 
old version had pending sessions:
-------------------------------------------------
<BEA-149060> <Module ehl.war of application ehl 
[LibSpecVersion=3.7.1.150,LibImplVersion=10069] successfully tra
nsitioned from STATE_ADMIN to STATE_ACTIVE on server ThujaNode1.>

<BEA-149059> <Module ehl.war of application ehl [Version=3.7.1.150] is

transitioning from STATE_ACTIVE to STATE
_ADMIN on server ThujaNode1.>

<BEA-101350> <Web application(s) /ehl of module ehl.war of application
ehl 
[Version=3.7.1.150] has 41 pending ses
sion(s) respectively.>

<BEA-101351> <Server has detected pending sessions while gracefully 
transitioning webapp module ehl.war of applic
ation ehl [Version=3.7.1.150] from running to admin mode. Server will wait 
for pending sessions to either become invalidated or timed out. The current 
timeout
 value is 18,000 seconds. To terminate sessions immediately, use the -force 
option.>

<BEA-101354> <Web application(s) /ehl of module ehl.war of application
ehl 
[Version=3.7.1.150] still have pending
 sessions after 0 minutes of initiating transition from running to admin 
mode. Waiting for pending sessions to finish.>
-------------------------------------------------

At this point we were able to log on into the new version and called it a 
successful update.

-------------------------------------------------
exactly after one hour the retiring version logged the following:
<BEA-149059> <Module ehl.war of application ehl [Version=3.7.1.150] is

transitioning from STATE_ACTIVE to STATE_
PREPARED on server ThujaNode1.>

<BEA-149059> <Module ehl.war of application ehl [Version=3.7.1.150] is

transitioning from STATE_ACTIVE to STATE_
PREPARED on server ThujaNode1.>

<000000> <Closing Spring root WebApplicationContext>

<BEA-149060> <Module ehl.war of application ehl [Version=3.7.1.150] 
successfully transitioned from STATE_ACTIVE
to STATE_PREPARED on server ThujaNode1.>

<BEA-149060> <Module ehl.war of application ehl [Version=3.7.1.150] 
successfully transitioned from STATE_ACTIVE
to STATE_PREPARED on server ThujaNode1.>

<BEA-149059> <Module ehl.war of application ehl [Version=3.7.1.150] is

transitioning from STATE_PREPARED to STAT
E_NEW on server ThujaNode1.>

<BEA-149059> <Module ehl.war of application ehl [Version=3.7.1.150] is

transitioning from STATE_PREPARED to STAT
E_NEW on server ThujaNode1.>

<BEA-149060> <Module ehl.war of application ehl [Version=3.7.1.150] 
successfully transitioned from STATE_PREPARE
D to STATE_NEW on server ThujaNode1.>

<BEA-149060> <Module ehl.war of application ehl [Version=3.7.1.150] 
successfully transitioned from STATE_PREPARE
D to STATE_NEW on server ThujaNode1.>
-------------------------------------------------

Now things got complicated - the application goes back to ADMIN state and 
block the running version:

-------------------------------------------------
<BEA-101352> <There are no active sessions. The webapp module ehl.war
of 
application ehl [Version=3.7.1.150] is r
eady to go into admin mode.>

<BEA-149060> <Module ehl.war of application ehl [Version=3.7.1.150] 
successfully transitioned from STATE_NEW to
 STATE_ADMIN on server ThujaNode1.>
-------------------------------------------------

After taht the newer version was still in ACTIVE state, but all request were 
routed to the old version, which was inaccessible (ADMIN state).

Has someone encountered similar problems when performing application