[JFrog JIRA] Created: (RTFACT-1661) Deployment should fail if MySQL max_allowed_packet is too small
|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
 |
[JFrog JIRA] Created: (RTFACT-1661) Deployment should fail if MySQL max_allowed_packet is too small
by JIRA jira@jfrog.org
::
Rate this Message:
Deployment should fail if MySQL max_allowed_packet is too small
--------------------------------------------------------------- Key: RTFACT-1661 URL: http://issues.jfrog.org/jira/browse/RTFACT-1661 Project: Artifactory Issue Type: Bug Components: Artifact Storage Affects Versions: 2.0.5 Reporter: Yoav Landman Assignee: Frederic Simon Fix For: 2.0.6 Jackrabbit swallows the exception and retries with a stream that is already consumed, so it ends up with 0 bytes being stored in the datastore. Since the datastore hash doesn't change on future deployments there is no way to overwrite the deployed 0 length file, even if max_allowed_packet is now properly configured. The only way to get rid of the badly deployed file on an existing repo is to delete the file, wait for the the datastore garbage collector to double-scan it so it is truly removed from the datastore (the default for this to happen is 2 hours, unless the artifactory.gcIntervalMins system property is temporarily tweaked), then redeploy the good file. We should stop the deployment with and error when max_allowed_packet is too small, by overriding the default Jackrabbit mechanism that swallows the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.jfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Artifactory-developers mailing list Artifactory-developers@... https://lists.sourceforge.net/lists/listinfo/artifactory-developers |
|
|
[JFrog JIRA] Resolved: (RTFACT-1661) Deployment should fail if MySQL max_allowed_packet is too small
by JIRA jira@jfrog.org
::
Rate this Message:
[ http://issues.jfrog.org/jira/browse/RTFACT-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoav Landman resolved RTFACT-1661. ---------------------------------- Resolution: Fixed > Deployment should fail if MySQL max_allowed_packet is too small > --------------------------------------------------------------- > > Key: RTFACT-1661 > URL: http://issues.jfrog.org/jira/browse/RTFACT-1661 > Project: Artifactory > Issue Type: Bug > Components: Artifact Storage > Affects Versions: 2.0.5 > Reporter: Yoav Landman > Assignee: Frederic Simon > Fix For: 2.0.6 > > > Jackrabbit swallows the exception and retries with a stream that is already consumed, so it ends up with 0 bytes being stored in the datastore. > Since the datastore hash doesn't change on future deployments there is no way to overwrite the deployed 0 length file, even if max_allowed_packet is now properly configured. The only way to get rid of the badly deployed file on an existing repo is to delete the file, wait for the the datastore garbage collector to double-scan it so it is truly removed from the datastore (the default for this to happen is 2 hours, unless the artifactory.gcIntervalMins system property is temporarily tweaked), then redeploy the good file. > We should stop the deployment with and error when max_allowed_packet is too small, by overriding the default Jackrabbit mechanism that swallows the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.jfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Artifactory-developers mailing list Artifactory-developers@... https://lists.sourceforge.net/lists/listinfo/artifactory-developers |
| Free embeddable forum powered by Nabble | Forum Help |
