Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.

More information about the channel is in the wiki.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2019-03-14 12:50:42 GMT <alfresco-discord> <digcat> hi @Francesco Corti an adf question do you know if there is any intention to expand adf to also work with activiti cloud community version?

2019-03-14 12:56:08 GMT <alfresco-discord> <yreg> @digcat ADF-3.0 released shortly after DevCon does already support Activiti 7

2019-03-14 12:56:17 GMT <alfresco-discord> <yreg> through its ProcessCloud module

2019-03-14 12:56:46 GMT <alfresco-discord> <yreg> it should be the same module for APS 2.0, as that one will have the same set of APIs as Activiti community

2019-03-14 12:57:02 GMT <alfresco-discord> <digcat> ah ha, i missed that, thanks @yreg

2019-03-14 12:57:33 GMT <alfresco-discord> <yreg> I haven't had a look yet at that ProcessCloud module

2019-03-14 12:58:03 GMT <alfresco-discord> <yreg> but I am hoping it won't be as sloppy and crappy as the the stuff there for APS 1.x

2019-03-14 12:58:11 GMT <alfresco-discord> <digcat> as long as the intention is there, i will persevere with activiti

2019-03-14 12:58:28 GMT <alfresco-discord> <yreg> (just to list tasks, 3-4 backend requests, and in frontend merge ... )

2019-03-14 13:03:53 GMT <alfresco-discord> <Francesco Corti> Hi guys

2019-03-14 13:05:06 GMT <alfresco-discord> <Francesco Corti> @digcat check this

2019-03-14 13:05:06 GMT <alfresco-discord> <Francesco Corti> https://www.alfresco.com/abn/adf/docs/process-services-cloud/

2019-03-14 13:05:20 GMT <alfresco-discord> <Francesco Corti> All of this work with Activiti 7 Community tooo

2019-03-14 13:05:48 GMT <alfresco-discord> <Francesco Corti> There are some missing parts

2019-03-14 13:05:56 GMT <alfresco-discord> <Francesco Corti> (just for you to be aware)

2019-03-14 13:07:17 GMT <alfresco-discord> <Francesco Corti> but in ADF 3.1 (release end of march) will cover some gaps

2019-03-14 13:07:19 GMT <alfresco-discord> <Francesco Corti> not all

2019-03-14 13:12:31 GMT <alfresco-discord> <digcat> ahh thats useful, hmm were not allowed to see https://issues.alfresco.com/jira/browse/ADF-3296

2019-03-14 13:12:34 GMT <alfbot> Title:Log in - Alfresco JIRA (at issues.alfresco.com)

2019-03-14 13:12:39 GMT <alfresco-discord> <digcat> even when logged in?

2019-03-14 13:12:50 GMT <alfresco-discord> <digcat> in the roadmap we cant see the epics

2019-03-14 13:13:09 GMT <AFaust> Why would you expect to be able to?

2019-03-14 13:13:27 GMT <alfresco-discord> <digcat> as its listed on https://www.alfresco.com/abn/adf/docs/release-notes/relnote300/#activiti-7-support-experimental

2019-03-14 13:13:44 GMT <AFaust> Hahaha. just because it is listed in some public document...

2019-03-14 13:14:03 GMT <alfresco-discord> <digcat> who would have thought it should be public, what was i thinking!

2019-03-14 13:15:29 GMT <AFaust> ...especially a release notes document, where there has always been a wild mix of private / public issues...

2019-03-14 13:16:25 GMT <AFaust> I especially love it when an Enterprise customer comes to me asking about a specific issue in the release notes where the name says something about a potential security risk, but the issue itself is private, so there is no way to determine if they need to / should update or not

2019-03-14 13:17:35 GMT <alfresco-discord> <yreg> is it only me or there are much more bugs than features in that document ?

2019-03-14 13:18:19 GMT <alfresco-discord> <yreg> It also looks like bugs are split in two buckets, I wonder what's the difference between bug and feature bug!

2019-03-14 13:18:34 GMT <AFaust> A feature bug is a bug that was planned in a previous sprint.

2019-03-14 13:19:08 GMT <AFaust> Or that is a "no surprise" bug, because a conscious decision was made that later caused people to complain about a stupid behaviour

2019-03-14 13:19:15 GMT <alfresco-discord> <digcat> a question to enterprise partners, is ADF something which carries a fee ?

2019-03-14 13:19:30 GMT <AFaust> Nope, ADF doesn't

2019-03-14 13:19:41 GMT <AFaust> I mean, I am not a partner...

2019-03-14 13:19:59 GMT <AFaust> But it was clear at DevCon that only Digital Workspace is an Enterprise only product.

2019-03-14 13:20:04 GMT <alfresco-discord> <digcat> yes, so i would have thought it should be wide open to get adoption ?

2019-03-14 13:20:14 GMT <AFaust> And even then I doubt it has an extra fee, similar to how Share never had an extra fee.

2019-03-14 13:20:30 GMT <AFaust> How would you handle license management etc. with a client-only application?

2019-03-14 13:21:10 GMT <alfresco-discord> <digcat> so again whats to be gained from having all its issues and roadmap locked down so they cant be viewed by the community ?

2019-03-14 13:21:41 GMT <AFaust> Why have (some/a lot of) Alfresco JIRAs for the open core been locked down all this time?

2019-03-14 13:22:18 GMT <alfresco-discord> <digcat> maybe @Francesco Corti is this something which can be changed? ie open up the tickets so people trying to use it, can at least get some idea to be able to help?

2019-03-14 13:22:19 GMT <AFaust> Because someone (in support / from a partner) was not smart enough to create a ticket without sensitive information, so Alfresco locked it down as private to not risk disclosing that sensitive information

2019-03-14 13:23:18 GMT <AFaust> And even when there are no sensitive details in an issue, it can still be locked down.

2019-03-14 13:24:12 GMT <AFaust> With one customer of mine, we frequently have support come back to us with "we logged this with your information as MNT-XXXXX" and we can't access it, despite us not having provided anything that could be considered sensitive.

2019-03-14 13:24:17 GMT <alfresco-discord> <yreg> not even that, I had jiras created for my cases which were not accessible even to me, even though my whole support ticket didn't contain any thing even remotely resembling sensitive information

2019-03-14 13:24:31 GMT <AFaust> And even if we request our own JIRA'S to be made public, it often is not being followed...

2019-03-14 13:24:58 GMT <alfresco-discord> <yreg> same

2019-03-14 13:25:45 GMT <AFaust> That's why I said I would be fine with the move of ALF to GitHub under the condition that ALL JIRA issues move to GitHub, since on GitHub there are no private issues.

2019-03-14 13:26:33 GMT <alfresco-discord> <digcat> ok so perhaps these jira tickets relate to https://github.com/Alfresco/alfresco-ng2-components/issues, so this document would be far more use if their was a github issue link

2019-03-14 13:33:05 GMT <angelborroy> AFaust did you see that all my Community Points have flown?

2019-03-14 13:33:20 GMT <angelborroy> I changed my e-mail and it looks like scoring is related to this value

2019-03-14 13:33:22 GMT <angelborroy> :)

2019-03-14 13:33:33 GMT <angelborroy> Iā€™m a newbie again!

2019-03-14 13:34:07 GMT <AFaust> I have not checked points in a while... Progress has stagnated quite a bit because of a lot of shitty questions, so I have less things I can (want to) answer...

2019-03-14 13:34:19 GMT <angelborroy> the same

2019-03-14 13:34:54 GMT <AFaust> But I believe the points change is due to your change of status to Alfresco employee

2019-03-14 13:35:06 GMT <angelborroy> do you think so?

2019-03-14 13:35:12 GMT <angelborroy> probably

2019-03-14 13:35:28 GMT <angelborroy> I just was trying to see if I can change it

2019-03-14 13:35:30 GMT <angelborroy> And I can

2019-03-14 13:35:39 GMT <angelborroy> So probably anyone can be Alfresco Employee

2019-03-14 13:35:40 GMT <angelborroy> :D

2019-03-14 13:59:41 GMT <alfresco-discord> <yreg> lol

2019-03-14 14:13:50 GMT <alfresco-discord> <Francesco Corti> sorry guys (included @digcat) but cannot follow all the flow

2019-03-14 14:14:01 GMT <alfresco-discord> <Francesco Corti> ADF is shipped for free and open source

2019-03-14 14:14:47 GMT <alfresco-discord> <Francesco Corti> Digital Workspace is an ADF app developed useing the open source components, and it is customized and officially supported

2019-03-14 14:16:42 GMT <alfresco-discord> <Francesco Corti> The Jira issue you are pointing does not contains too many useful info (believe me)

2019-03-14 14:16:55 GMT <alfresco-discord> <Francesco Corti> more notes done in the past

2019-03-14 14:17:04 GMT <alfresco-discord> <Francesco Corti> and it is mainly a mirror of

2019-03-14 14:17:04 GMT <alfresco-discord> <Francesco Corti> https://issues.alfresco.com/jira/browse/ADF-3349

2019-03-14 14:17:15 GMT <alfresco-discord> <Francesco Corti> Any other question I can answer?

2019-03-14 14:19:49 GMT <alfresco-discord> <digcat> hi @Francesco Corti i guess what i was hoping was that document which is useful, would be more useful if we can follow through the issues, if moving to github, then perhaps the closed issues from github could be referenced in the future ?

2019-03-14 14:21:01 GMT <alfresco-discord> <digcat> but thankyou for pointing out that adf-3349 link

2019-03-14 14:21:51 GMT <alfresco-discord> <Francesco Corti> ok, I'm trying to clean the Jira board (it was not ideal)

2019-03-14 14:22:15 GMT <alfresco-discord> <Francesco Corti> For your purpose adf-3349 is the best place

2019-03-14 14:23:10 GMT <alfresco-discord> <Francesco Corti> let me know if you have needs to "work more in the open", but from what I can see ADF is definitely doing it.

2019-03-14 14:23:34 GMT <alfresco-discord> <digcat> ok thats good to hear, so these are legacy items so going forward it will be easier

2019-03-14 14:23:48 GMT <alfresco-discord> <Francesco Corti> which one?

2019-03-14 14:23:57 GMT <alfresco-discord> <Francesco Corti> no legacy stuff in ADF for the moment

2019-03-14 14:25:29 GMT <AFaust> He was referring to the messed up JIRA issue / permission

2019-03-14 14:25:41 GMT <alfresco-discord> <digcat> ok so https://issues.alfresco.com/jira/browse/ADF-3296 was the one i couldnt see, going forward 3349 should be this

2019-03-14 14:25:43 GMT <alfbot> Title:Log in - Alfresco JIRA (at issues.alfresco.com)

2019-03-14 14:26:32 GMT <alfresco-discord> <digcat> i can see others ill report back other ones we cant see

2019-03-14 14:26:33 GMT <alfresco-discord> <Francesco Corti> yes, forget 3296 (it is old)

2019-03-14 14:26:33 GMT <alfresco-discord> <Francesco Corti> yes, feel free to report me jira issues

2019-03-14 14:26:36 GMT <alfresco-discord> <digcat> ok cool thanks, typical i find that one šŸ˜ƒ

2019-03-14 14:26:53 GMT <alfresco-discord> <Francesco Corti> well... you give me the opportunity to imporve it šŸ˜›

2019-03-14 15:09:49 GMT <alfresco-discord> <LuisColorado> We have a bit of debate about this question, and I'm hoping to get some insights or a definitive answer. As you know, the recommended architecture for performance is to have a a cluster of Alfresco nodes with separate Solr servers with their own read-only Alfresco instances for tracking. The question is: should those Solr nodes be cluster enabled?

2019-03-14 15:11:21 GMT <alfresco-discord> <LuisColorado> I'm referring to this doc: https://www.alfresco.com/sites/www.alfresco.com/files/alfresco_content_services_5.2_reference_architecture.pdf

2019-03-14 15:13:41 GMT <alfresco-discord> <yreg> I would say no

2019-03-14 15:13:50 GMT <alfresco-discord> <yreg> It's even better if they are not

2019-03-14 15:13:52 GMT <alfresco-discord> <LuisColorado> Page 10 shows no clustering at the index tier, but page 15 (for Solr 6) shows clustering.

2019-03-14 15:14:43 GMT <alfresco-discord> <yreg> they are supposed to only access data from each transaction once for indexing it, and there should be no need for clustering at

2019-03-14 15:15:06 GMT <alfresco-discord> <yreg> actually clustering would only cripple it putting a bit of overhead on performance

2019-03-14 15:17:15 GMT <alfresco-discord> <yreg> I am not even sure if Solr APIs are passing through caches or not (maybe AFaust can confirm)

2019-03-14 15:17:50 GMT <alfresco-discord> <yreg> but if they do, what you could do is that you disable caching altogether on these instances if you are afraid that data might change within 5 minutes timeframe (default OOTB cache lifetime in ACS), and could cause your index servers to pick outdated data on the next round

2019-03-14 15:19:53 GMT <alfresco-discord> <yreg> by disabling cache I mean minimising the TTL config on the cache forcing ACS to go straight to DB at every call (not sure if there is an easier way to do it)

2019-03-14 15:20:57 GMT <AFaust> So the SOLRTrackingComponent has an explizit preCacheNodes operation, so obviously the SOLR indexing passes through the caches (why shouldn't it - caches are used on the DAO layer and cannot be circumvented unless special SQL queries are used)

2019-03-14 15:21:39 GMT <AFaust> One thing that SOLRTrackingComponent does as part of that preCacheNodes operation: set a transaction scope flag that disables shared caches.

2019-03-14 15:22:03 GMT <alfresco-discord> <yreg> for the record, default solr frequency is 15s, but most big repos I have seen do increase that to 2m to 10m, and obviously if your tracking frequency is >=5m there is nothing to worry about here

2019-03-14 15:22:06 GMT <AFaust> Meaning, the global caches - those that are kept in synch as part clustering, unless configured to be local-only - are not used

2019-03-14 15:22:45 GMT <AFaust> So all that pre-caching only fills the transactional caches

2019-03-14 15:23:02 GMT <AFaust> and "filling" is only done from DB, not from shared cache

2019-03-14 15:23:09 GMT <alfresco-discord> <yreg> ok then, so You can leave your ACS instances for indexing out of the cluster safely and with nothing to worry about @LuisColorado

2019-03-14 15:24:02 GMT <AFaust> Ahem... I was not done yet (I am following the call chain at the same time as writing, to make sure I did not forget anything / miss any recent changes)

2019-03-14 15:24:11 GMT <alfresco-discord> <LuisColorado> Thank you, @yreg and @AFaust

2019-03-14 15:24:31 GMT <alfresco-discord> <LuisColorado> oops!

2019-03-14 15:24:53 GMT <alfresco-discord> <LuisColorado> (lol) sorry, Axel!

2019-03-14 15:24:55 GMT <AFaust> It is actually not all caches that ignore the shared cache - it is actually limited to the node.nodesSharedCache, which handles node identity + version

2019-03-14 15:25:24 GMT <alfresco-discord> <yreg> How about ACLs

2019-03-14 15:25:42 GMT <alfresco-discord> <yreg> those also get indexed

2019-03-14 15:25:50 GMT <AFaust> But since every change modifies the version ID, and the version ID is used as part of the cache key in other caches, all other node caches (aspects / properties) would be automatically consistent

2019-03-14 15:26:12 GMT <alfresco-discord> <yreg> yep, figured that out already

2019-03-14 15:26:24 GMT <alfresco-discord> <yreg> but ACLs/ACEs could still be an issue

2019-03-14 15:26:32 GMT <alfresco-discord> <yreg> no ?

2019-03-14 15:26:40 GMT <AFaust> ^^ just wanted to be clear in case someone didn't figure that already

2019-03-14 15:27:53 GMT <AFaust> Well, ACLs are loaded by ACL changesets and that part actually circumvents the normal DAO with special SQL for SOLR tracking

2019-03-14 15:28:08 GMT <AFaust> So yes, ACLs are fine without clusterling as they do not use a cache at all#

2019-03-14 15:28:49 GMT <AFaust> And ACEs / readers check has its own variant of "ignore shared cache" operation

2019-03-14 15:29:16 GMT <AFaust> One code comment actually reads: // We don't want the caches to lie and we may not be part of the cluster

2019-03-14 15:30:47 GMT <AFaust> So, to sum up: SOLR would be fine with repository not in cluster

2019-03-14 15:33:10 GMT <alfresco-discord> <LuisColorado> Wow! That was an excellent discussion, thank you.

2019-03-14 15:34:55 GMT <alfresco-discord> <LuisColorado> Still, I have to note that Solr6 seems to need clustering, according to the diagram in page 15 of the 5.2 ref architecture

2019-03-14 15:34:56 GMT <alfresco-discord> <LuisColorado> https://www.alfresco.com/sites/www.alfresco.com/files/alfresco_content_services_5.2_reference_architecture.pdf

2019-03-14 15:35:35 GMT <AFaust> "reference" architecture

2019-03-14 15:42:17 GMT <AFaust> I don't see that "clustering" requirement on page 15

2019-03-14 15:42:42 GMT <AFaust> Ah . not page 15 of the PDF, but page 15 based on what it says on the page...

2019-03-14 15:42:49 GMT <AFaust> I hate it if page numbering is not consistent

2019-03-14 15:43:52 GMT <AFaust> What page 15 refers to is the Sharding use case.

2019-03-14 15:44:10 GMT <AFaust> And they mean that the SOLR servers / shards form a "cluster"

2019-03-14 15:44:18 GMT <AFaust> That is not about the Repository

2019-03-14 15:44:22 GMT <AFaust> as far as I understand

2019-03-14 15:44:46 GMT <AFaust> The Repository is the lower half of that index layer stack, and you only see the sharding applied to the upper half

2019-03-14 15:46:10 GMT <alfresco-discord> <LuisColorado> You are right. I'm not quite clear what they mean with clustering here. Perhaps Solr6 has its own clustering used to optimize the replication of shards across servers?

2019-03-14 15:54:36 GMT <AFaust> Not really..

2019-03-14 15:55:04 GMT <AFaust> I believe they only refer to the various HTTP-based management interoperations / query distribution

2019-03-14 20:29:13 GMT <alfresco-discord> <marinoborges> Hello, is this the channel for asking about Alfresco Community issues?

2019-03-14 20:30:02 GMT <alfresco-discord> <douglascrp> @marinoborges about alfresco in general

2019-03-14 20:32:32 GMT <alfresco-discord> <marinoborges> I'm facing an issue with Alfresco 6 community fresh install using Oracle backend. I tried this https://github.com/krumboeck/oracle-alfresco with no success. Apparently, the last version for the AMP is supported until Alfresco 5. The message I see in catalina.out is: Error parsing SQL Mapper Configuration. Cause: org.apache.ibatis.builder.BuilderException: Failed to get resource:

2019-03-14 20:32:32 GMT <alfresco-discord> alfresco/ibatis/#resource.dialect#/activities-insert-SqlMap.xml

2019-03-14 20:32:33 GMT <alfbot> Title:GitHub - krumboeck/oracle-alfresco: Oracle Server support for Alfresco Community (at github.com)

2019-03-14 20:44:55 GMT <alfresco-discord> <douglascrp> that is not going to work for sure

2019-03-14 20:45:17 GMT <alfresco-discord> <douglascrp> Alfresco Community is compatible only with PostgreSQL or MySQL/MariaDB

2019-03-14 20:45:48 GMT <alfresco-discord> <douglascrp> don't even waste your time trying to do so if you don't know Alfresco really really really well

2019-03-14 20:47:06 GMT <alfresco-discord> <MorganP> + as far as I remember, I believe this add-on was taken from the Alfresco Enterprise source code so it's not really legal to use it

2019-03-14 20:48:02 GMT <alfresco-discord> <MorganP> There were discussions about this add-on a few months/years ago in the channel

2019-03-14 20:48:51 GMT <alfresco-discord> <MorganP> I would personally not try to use it. If you want to use Alfresco Community, then stick to the supported DBs which @douglascrp mentioned.

2019-03-14 20:49:09 GMT <alfresco-discord> <MorganP> PostgreSQL is the best anyway for Alfresco so there is no reason to look for anything else šŸ˜ƒ

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco