syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <>
Subject [jira] [Closed] (SYNCOPE-1209) Syncope console GUI does not allow uploading binary type with file size > 65KB
Date Tue, 19 Sep 2017 06:30:01 GMT


Francesco Chicchiriccò closed SYNCOPE-1209.
    Resolution: Not A Problem

Please check your MariaDB configuration at

In particular:

which will instruct MariaDB to not use plain BLOB (with 65k limitation as reported).

Secondly, I strongly suggest to upgrade from 2.0.1 to the latest 2.0.5 (follow the upgrade
steps provided from [2.0.1 to 2.0.2|]

Finally, please first check in the [user mailing list|]
before opening issues to be confirmed, thanks.

> Syncope console GUI does not allow uploading binary type with file size > 65KB
> ------------------------------------------------------------------------------
>                 Key: SYNCOPE-1209
>                 URL:
>             Project: Syncope
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 2.0.1
>         Environment: MariaDB
>            Reporter: Anh Tuan Nguyen
>         Attachments: core-rest.log, syncope_hang_with_large_image.JPG, syncope_logs.tar.gz
> 1/ I added a new binary schema to user as follow:
> {code}
>   <SyncopeSchema id="avatar"/>
>   <PlainSchema id="avatar" mandatoryCondition="false" mimeType="image/gif,image/jpeg,image/png"
multivalue="0" readonly="0" type="Binary" uniqueConstraint="0" ANYTYPECLASS_ID="BaseUser"
> {code}
> Now when I create new user and upload avatar, it only allows image with 65KB which is
too small and not customizable.
> This is because generated type is for binary is Blob with maximum length of 65,535 bytes,
note that we're using MariaDB.
> 2/ Also, when image with size > 65KB but < 4MB is uploaded, user creation just
stops at Finish without error message.
> When an image with size > 4MB, Next button in the wizard doesn't respond anymore in
Chrome, and no error message. In Firefox, it keeps loading forever.
> Is it possible to handle that scenario properly? At least we should have some decent
error message.

This message was sent by Atlassian JIRA

View raw message