Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

[Lipscomb, Gary]

Just to close this off for the archives.
Tomcat wasn't updating the contents of  /var/lib/tomcat/webapps/idp directory when the new idp.war was deployed. (on 2/8 servers).
Steps to fix
- Stop tomcat
- Deleted/var/lib/tomcat/webapps/idp/*
- Restart tomcat

Regards
Gary

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of John C. Pfeifer
Sent: Friday, 18 May 2018 22:20
To: Shib Users <users at shibboleth.net>
Subject: Re: Upgrade to IdP v3.3.3 still shows v3.3.2 in logs

I just tested my IdP running in tomcat on linux and all three option report 3.3.3.

> On May 18, 2018, at 6:40 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
> 
> 
>> Is it me?
> 
> I just tested my test-the-upgrade windows IdP.  
> 
>> ### Operating Environment Information
>> operating_system: Windows 7
>> operating_system_version: 6.1
>> operating_system_architecture: amd64
>> jdk_version: 1.8.0_171
>> available_cores: 2
>> used_memory: 106 MB
>> maximum_memory: 2048 MB
>> 
>> ### Identity Provider Information
>> idp_version: 3.3.3
>> start_time: 2018-05-18T11:25:37+01:00
>> current_time: 2018-05-18T11:25:40+01:00
>> uptime: 2589 ms
> 
> I realize that this is apples and orangutans  but the windows installer is built from the standard distribution so it is a data
> point.  Are you using Tomcat?
> 
> /R
> 
> -- 
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


//
John Pfeifer
Division of Information Technology
University of Maryland, College Park

-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net