15 Replies Latest reply on Mar 24, 2017 6:10 AM by dbologna RSS
    dbologna Apprentice

    Thingworx Composer return HTTP Status 401 - Could not handle request

    Hi All,

    today I installed on my PC Oracle Client 12.0 and then I uninstalled it.

    After that I started Tomcat and I'm connect to Composer in local thingworx instance, the url returned the following message :

    I'm not requested to enter the login/password andf the url returned the page before.

    Any suggestion .. I would like to avoid to reinstall all the environment.

    In case I have to reinstall  how canI restore data (stored in neo4j).

    Is it possibile afther the new installation to link the old db ?

    Many Thanks

    BR

    Dimitri

      • Re: Thingworx Composer return HTTP Status 401 - Could not handle request
        supandey Collaborator

        Hi Dimitri, what's the error message in the tomcat's catalina log? is the Tomcat running while you get that error? You might want to confirm if somehow the Java settings are changed/updated for the Tomcat after you uninstalled the Oracle client.

         

        Edit:

        Could you please attach the Tomcat to your reply.

        • Re: Thingworx Composer return HTTP Status 401 - Could not handle request
          polinao Collaborator

          Could you please verify that your Tomcat java path is set to (with your own java version):

          Java\jre1.8.0_121\bin\server\jvm.dll

            • Re: Thingworx Composer return HTTP Status 401 - Could not handle request
              dbologna Apprentice

              Hi Polina,

              the path is correct

              BR

              Dimitri

              • Re: Thingworx Composer return HTTP Status 401 - Could not handle request
                dbologna Apprentice

                Hi Polina,

                Thank you very much for your support,

                I'm sorry for the delay in sending you the information.

                In Thingworx/logs/ApplicationLog.log there area the following rows

                017-03-20 15:24:18.058+0100 [L: INFO] [O: c.t.s.ThingWorxPersistenceHandler] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Default Persistence Provider Name = ThingworxPersistenceProvider

                2017-03-20 15:24:18.058+0100 [L: INFO] [O: c.t.s.ThingWorxPersistenceHandler] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Default Persistence Provider Package Name = H2PersistenceProviderPackage

                2017-03-20 15:25:07.819+0100 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: SuperUser] [S: ] [T: C3P0PooledConnectionPoolManager[identityToken->139rofi9m1tidp7cidmc1|669a5377]-HelperThread-#5] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@7abac999 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:

                2017-03-20 15:25:07.819+0100 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: SuperUser] [S: ] [T: C3P0PooledConnectionPoolManager[identityToken->139rofi9m1tidp7cidmc1|669a5377]-HelperThread-#5] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@70e9c33e is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.

                2017-03-20 15:25:07.835+0100 [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] [message: Connections could not be acquired from the underlying database!]

                2017-03-20 15:25:07.835+0100 [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] *** Web Application STATE is being set to ERROR! ***

                In Thingworx/logs/SecurityLog.log there area the following rows

                2017-03-20 15:25:07.852+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Could not load session timeout from database, using default: null

                2017-03-20 15:25:09.026+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-2] Could not handle request

                2017-03-20 15:25:09.026+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-1] Could not handle request

                2017-03-20 15:25:09.026+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-3] Could not handle request

                2017-03-20 15:26:06.885+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-5] Could not handle request

                2017-03-20 15:26:08.850+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-6] Could not handle request

                2017-03-20 15:26:09.037+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-7] Could not handle request

                2017-03-20 15:30:34.453+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Could not load session timeout from database, using default: null

                2017-03-20 15:30:35.574+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-1] Could not handle request

                2017-03-20 15:35:12.997+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-5] Could not handle request

                2017-03-20 15:35:31.607+0100 [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-6] Could not handle request

                BR

                Dimitri