topic Re: Issue upgrading from 5.17 to 5.19.0.2 in Alfresco Archive

Issue upgrading from 5.17 to 5.19.0.2

srini_n — Mon, 08 Feb 2016 17:25:16 GMT

Hi,I am trying to upgrade from 5.17.0 to 5.19.0.2. After updating the version in our POM for "activiti-webapp-explorer2", "activiti-engine", "activiti-explorer" & "activiti-ldap", I deployed the application in my local STS Pivotal TC. Here are the issues I am facing:1. Activiti Modeler isn't wor

Re: Issue upgrading from 5.17 to 5.19.0.2

srini_n — Mon, 08 Feb 2016 21:11:41 GMT

Update:

1. I dropped the Activiti Schema
2. Started Activiti-Explorer 5.19.0.2. It created all the schema objects by running activiti.oracle.create.engine.sql, activiti.oracle.create.history.sql & activiti.oracle.create.identity.sql.
3. Version in act_ge_property table is 5.20.0.1
4. Same issue with Activiti Modeler (blank editor)

Re: Issue upgrading from 5.17 to 5.19.0.2

srini_n — Mon, 08 Feb 2016 22:49:33 GMT

Update 2:

1. Rolled back to 5.17.0 (5.19.0.2 –> 5.19.0 –> 5.18.0 –> 5.17.0) by doing a fresh install everytime!!
2. 5.17.0, things start to work again
3. Upon going back to any version above 5.17.0, Chrome Debug Tool reveals the following:
"GET http://localhost:8080/activiti-explorer/service/model/1/json 403 (Forbidden)"
4. In 5.17.0, i don't see any such issue and the json is accessible.

Will continue to dig into it. Anyone else running version > 5.17.0?

Re: Issue upgrading from 5.17 to 5.19.0.2

srini_n — Tue, 09 Feb 2016 04:31:04 GMT

Update 3:

1. The model is present in the DB. Not sure why access to it is forbidden.
2. Issue present in Chrome 45 & FireFox 38 (a similar issue is called out in the release notes quoted below)
3. Access Log from localhost tomcat ("GET /activiti-explorer/service/model/1/json HTTP/1.1" 403 1054)

From Release Notes:
Known issues

There's a known issue with Chrome and the Activiti Explorer / Vaadin 6. You can get a blank screen in the details part of the Explorer. This is a known issue for Vaadin 6 and Chrome 43 and 44. There are bug fixes under way with Chrome 45, so that might fix it. Other browsers like Firefox work fine.

Re: Issue upgrading from 5.17 to 5.19.0.2

jbarrez — Tue, 09 Feb 2016 08:00:38 GMT

I've tried running the 5.19.0.2 here … but here it just works (Mac, Chrom v 48).

Re: Issue upgrading from 5.17 to 5.19.0.2

srini_n — Tue, 09 Feb 2016 16:19:35 GMT

Thanks for confirming. Not sure what is going on here at my end with access and 404 issues. Here is the log after upgrading to Chrome 48.

<code>http://localhost:8080/favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)
http://localhost:8080/activiti-explorer/service/model/2501/json Failed to load resource: the server responded with a status of 403 (Forbidden)
app.js:107 Error loading model with id 2501 <!DOCTYPE html><html><head><title>Pivotal tc Runtime 3.0.2.SR2/8.0.15.B.RELEASE - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 403 - </h1><div class="line"></div><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>Access to the specified resource has been forbidden.</u></p><hr class="line"><h3>Pivotal tc Runtime 3.0.2.SR2/8.0.15.B.RELEASE</h3></body></html></code>

Re: Issue upgrading from 5.17 to 5.19.0.2

jbarrez — Thu, 11 Feb 2016 09:07:38 GMT

wow that's very odd … the blank page was a known … but the 403 is new … and I don't see how that could be releated to the server.

I see you're running Pivotal… does the same happen with a vanilla Tomcat?

Re: Issue upgrading from 5.17 to 5.19.0.2

srini_n — Thu, 11 Feb 2016 15:05:52 GMT

Update: Issue Resolved

We had implemented a custom LoginHandler which was not setting the AUTHENTICATED_USER_ID (_currentUser) on the Session. Due to this, ExplorerFilter was unable to authenticate incoming requests directed to "/service" and was returning a 403.

This check in ExplorerFilter was introduced in 5.18 and not before.

Re: Issue upgrading from 5.17 to 5.19.0.2

jbarrez — Tue, 16 Feb 2016 11:11:31 GMT

Ok, thanks for posting back.
I can't even remember that this filter was added back then