search

aegif / CmisSync

Synchronize content between a CMIS repository and your desktop. Like Dropbox for Enterprise Content Management!
http://CmisSync.com
163 stars 123 forks source link

Alfresco Receiver only understands CMIS 1.0 #592

Closed lelmarir closed 9 years ago

lelmarir commented 9 years ago

I get a lot of this in the alfresco log. I'm not completely sure it is from cmisSync, but no other should use cmis. May it be? What protocol version does cmisSync use?

2015-07-23 10:06:59,206  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-28] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:00,335  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-61] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:00,845  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-23] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:07:01,044  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:01,045  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-26] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:01,337  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-40] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:07:05,045  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-27] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:07:51,905  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-12] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:52,493  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-36] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:07:52,686  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-61] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:52,687  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-61] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:07:53,321  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-76] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:08:03,612  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-67] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:08:03,818  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-70] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
 2015-07-23 10:08:11,463  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-62] Receiver only understands CMIS 1.0. It may not be able to handle an Item object.
 2015-07-23 10:08:11,591  WARN  [commons.impl.XMLConverter] [http-apr-8080-exec-30] Receiver only understands CMIS 1.0. It may not able to handle an Item type definition.
nicolas-raoul commented 9 years ago

Interesting! CmisSync uses the CMIS 1.1 URL, but does not use CMIS 1.1-specific operations.

Please try to modify CmisSync's configured URL to Alfresco's CMIS 1.0 URL: http://<host>/alfresco/api/-default-/public/cmis/versions/1.0/atom

lelmarir commented 9 years ago

I also get this now: As before, don't know if it is related, but it's likely

[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
[Fatal Error] :1:1: Invalid byte 2 of 2-byte UTF-8 sequence.
[Fatal Error] :1:1: Invalid byte 2 of 3-byte UTF-8 sequence.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Invalid byte 2 of 2-byte UTF-8 sequence.
[Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Invalid byte 2 of 2-byte UTF-8 sequence.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Invalid byte 2 of 4-byte UTF-8 sequence.
[Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
[Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
[Fatal Error] :1:1: Content is not allowed in prolog.
nicolas-raoul commented 9 years ago

This too is in the Alfresco Receiver log? Content is not allowed in prolog is typical of malformed XML. Could be the result of network corruption by a firewall or something.

lelmarir commented 9 years ago

Yes, in the Alfresco log. May be, on a second check i'd notice they starts from yesterday....probably is a server fault. I think this can be closed, sorry.

alfresco@alfresco:/opt/alfresco$ fgrep "[Fatal Error]" -i catalina.out  | sort | uniq -c | sort -rn
    307 [Fatal Error] :1:1: Content is not allowed in prolog.
    173 [Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
     43 [Fatal Error] :1:1: Invalid byte 2 of 2-byte UTF-8 sequence.
     27 [Fatal Error] :1:1: Invalid byte 2 of 3-byte UTF-8 sequence.
     12 [Fatal Error] :1:1: Invalid byte 2 of 4-byte UTF-8 sequence.
      8  [Fatal Error] :1:1: Content is not allowed in prolog.
      5  [Fatal Error] :1:1: Invalid byte 2 of 2-byte UTF-8 sequence.
      4 [Fatal Error] :1:2: Content is not allowed in prolog.
      4  [Fatal Error] :-1:-1: Premature end of file.
      4 [Fatal Error] :1:1: Invalid byte 3 of 3-byte UTF-8 sequence.
      4  [Fatal Error] :1:1: Invalid byte 1 of 1-byte UTF-8 sequence.
      3 [Fatal Error] :1:2: Reference is not allowed in prolog.
      3 [Fatal Error] :1:1: Invalid byte 3 of 4-byte UTF-8 sequence.
      2 [Fatal Error] :2:1: Content is not allowed in prolog.
      2 [Fatal Error] :1:2: Invalid byte 1 of 1-byte UTF-8 sequence.
      1 [Fatal Error] :5:68: Character reference "&#5" is an invalid XML character.
      1 [Fatal Error] :5:68: Character reference "&#4" is an invalid XML character.
      1  [Fatal Error] :5:68: Character reference "&#4" is an invalid XML character.
      1 [Fatal Error] :2:1: Invalid byte 2 of 2-byte UTF-8 sequence.
      1 [Fatal Error] :2:1: Invalid byte 1 of 1-byte UTF-8 sequence.
      1  [Fatal Error] :1:2: Reference is not allowed in prolog.
      1 [Fatal Error] :1:2: Invalid byte 3 of 3-byte UTF-8 sequence.
      1 [Fatal Error] :1:2: Invalid byte 2 of 4-byte UTF-8 sequence.
      1  [Fatal Error] :1:2: Invalid byte 1 of 1-byte UTF-8 sequence.
      1 [Fatal Error] :1:1: Invalid byte 4 of 4-byte UTF-8 sequence.
      1  [Fatal Error] :1:1: Invalid byte 2 of 4-byte UTF-8 sequence.
nicolas-raoul commented 9 years ago

Closing for now, but don't hesitate to comment if you find a solution, or create other issues for anything you think might be CmisSync-related. Cheers! :-)