nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Warning: Receiver only understands CMIS 1.0. It may not able to handle an Item type definition

mtsiak

The above warning lines are been written repeatedly, for the last week in our Alfresco community 5.0 edition production server:

2017-05-09 23:59:45,149 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
2017-05-09 23:59:45,754 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:45,757 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:45,760 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:45,765 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:45,767 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,080 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,082 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,084 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,274 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,276 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,398 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-42] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,400 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-42] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,574 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-42] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
2017-05-09 23:59:46,576 WARN [org.apache.chemistry.opencmis.commons.impl.XMLConverter] [ajp-bio-8009-exec-42] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.

Any suggestions?

Find more posts tagged with

Alfresco Content Services

Accepted answers

angelborroy

It looks like you have an external app connecting your repository by using CMIS 1.0 but trying to use features from CMIS 1.1, does this make sense?

All comments

angelborroy

It looks like you have an external app connecting your repository by using CMIS 1.0 but trying to use features from CMIS 1.1, does this make sense?

mtsiak

One of our testers was checking CmisSync client from a windows 10 machine. I disconnected and reconnected a folder, but I could not reproduce the warnings.

One hypothesis is that there is a problem while synching datalists. What should someone expect when cmis-synching datalists? Files?

Another hypothesis is related to alfresco-esign-cert amp (sorry Angel, it is only a hypothesis!): the debug log of CmisSync client still contain warnings like:

2017-05-16 11:37:24,689 [14] WARN  CmisSync.Lib.Sync.CmisRepo+SynchronizedFolder [(null)] - Unknown object type: 'I:cm:cmobject' (Object) for object DotCMIS.Client.Impl.Folder/87890990-9ae3-4c5b-b97e-0ea507bb1633

where the 87890990-9ae3-4c5b-b97e-0ea507bb1633 node is the one created at alfresco-esign-cert/CustomBehaviour.java at master · keensoft/alfresco-esign-cert · GitHub

The sure thing is that the warnings stopped being procuded when we disconnected the CmisSync client as you reported.

Thank you again for your reply.

douglascrp

I don't think you should expecting for files when synching datalists, as these are contentless objects.

Have you tried to find any useful information in the CmisSync logs?

About the CMIS 1.0 and 1.1 differences, I remember about reading this blog post Cool things you can do in Alfresco with cmis:item support | ECM Architect

There you will see that with 1.1 you can work with contentless objects.

I am not sure if this information is useful to help you solve the problem you are facing.

mtsiak

some warnings from the CmisSync:

2017-05-15 14:03:15,690 [7] WARN  CmisSync.Lib.Sync.CmisRepo+SynchronizedFolder [(null)] - Unknown object type: 'I:cm:cmobject' (Object) for object DotCMIS.Client.Impl.Folder/3fc85558-db5d-435e-81b3-d72652d58c4b
2017-05-15 14:03:15,690 [7] WARN  CmisSync.Lib.Sync.CmisRepo+SynchronizedFolder [(null)] - Unknown object type: 'I:cm:cmobject' (Object) for object DotCMIS.Client.Impl.Folder/3f551972-3e05-4730-bfc2-9044dd768df5
2017-05-15 14:03:15,690 [7] WARN  CmisSync.Lib.Sync.CmisRepo+SynchronizedFolder [(null)] - Unknown object type: 'I:cm:cmobject' (Object) for object DotCMIS.Client.Impl.Folder/95f0f1a1-6928-4310-b448-ae9198e923f6‍‍‍‍‍‍‍‍

and those objects are contentless.