This turns out to be three separate issues: * I was missing dependencies for ivy to handle credentials (ivy silently disabled them, not a good thing to do) * Ivy 2.1.0 rc2 has a bug w.r.t. artifactory and handling credentials * Artifactory has a bug in that it (sometimes) misreports a credential problem as that odd nodetype message
I've reverted to Ivy 2.1.0 rc1, added "Artifactory Realm" to my ivy credentials config and everything is again working. Thank you again for being responsive to the questions. My apologies that it was primarily my own configuration issues. Still, I hope this might help someone else. Doug Yoav Landman-3 wrote: > > Any server-side errors in the log? > Does it work if you try with a brand new (different) deployer? > > Yoav > > On Thu, Sep 17, 2009 at 6:33 PM, DSR1 <[email protected]> wrote: > >> >> Thank you for the quick answer. First I removed and added my user id >> back, >> then I upgraded to 2.0.8. The result is different but not better: >> >> C:\workspace\geodesy\build.xml:129: impossible to publish artifacts for >> org.mitre.itf#geodesy;1.9.6: java.io.IOException: PUT operation to URL >> >> http://maven-proxy/artifactory/libs-releases-local/org/mitre/itf/geodesy/1.9.6/geodesy-1.9.6.jar >> failed with status code 404: Not Found >> >> My user is an admin and also is in a group that has permissions to >> publish >> to libs-releases-local. This has, of course, worked in the past. >> >> Doug >> >> >> Yoav Landman-3 wrote: >> > >> > Hi, >> > >> > Can you try doing the following: >> > >> > - If deployment is not done anonymously - delete and recreate the user >> > used >> > for deployment, or create a new user and use his details for deploying >> > - Upgrade to 2.0.8 >> > >> > Incidentally, the ivy buildnumber task doesn't seem to work properly >> with >> > artifactory - probably their bug since it looks like everything is >> proper >> > in the repository. >> > >> > Thanks, >> > >> > Yoav >> > >> > On Thu, Sep 17, 2009 at 12:28 AM, DSR1 <[email protected]> wrote: >> > >> >> >> >> We're publishing to artifactory via ant and ivy using the ibiblio >> >> resolver. >> >> Things have been working fine in the past, but now it is failing with >> the >> >> following error message: >> >> >> >> "failed with status code 500: Node type: nt:unstructured has no >> >> descriptor." >> >> >> >> which seems related to the JCR store. We are running artifactory >> behind >> >> an >> >> apache server, but this fails with direct access to the open port as >> well >> >> as >> >> when connecting via Apache. Publishing was working prior to this. We >> have >> >> had a couple of failures due to the file system filling up with >> backups >> >> but >> >> there's plenty of room at this point. >> >> >> >> The ant task is: >> >> >> >> <target name="publish" depends="pom, javadoc, sourcejar" >> >> description="Publish directly to a repository"> >> >> <echo>Publishing revision ${ivy.new.revision}</echo> >> >> <ivy:publish resolver="maven-proxy" >> >> revision="${ivy.new.revision}" >> >> update="true" overwrite="true"> >> >> <artifacts pattern="rel/[artifact].[ext]" /> >> >> <artifacts pattern="rel/jars/[artifact].[ext]" >> /> >> >> </ivy:publish> >> >> </target> >> >> >> >> The relevant resolver is: >> >> >> >> <ibiblio name="maven-proxy" namespace="m2" >> >> root=" >> >> http://maven-proxy/artifactory/libs-releases-local"; >> >> m2compatible="true" /> >> >> >> >> The console log shows the following interesting exception (partial >> stack >> >> shown): >> >> >> >> 2009-09-16 17:17:23,215 [ERROR] (o.m.log ) >> >> >> >> >> /artifactory/libs-releases-local/org/mitre/itf/giscore/0.4.11/giscore-0.4.11.jar >> >> org.apache.jackrabbit.ocm.exception.IncorrectPersistentClassException: >> >> Node >> >> type: nt:unstructured has no descriptor. >> >> at >> >> >> >> >> org.apache.jackrabbit.ocm.mapper.impl.AbstractMapperImpl.getClassDescriptorByNodeType(AbstractMapperImpl.java:188) >> >> [jackrabbit-ocm-1.4-jcr-1385.jar:na] >> >> at >> >> >> >> >> org.apache.jackrabbit.ocm.manager.objectconverter.impl.ObjectConverterImpl.getObject(ObjectConverterImpl.java:295) >> >> [jackrabbit-ocm-1.4-jcr-1385.jar:na] >> >> at >> >> >> >> >> org.apache.jackrabbit.ocm.manager.impl.ObjectContentManagerImpl.getObject(ObjectContentManagerImpl.java:264) >> >> [jackrabbit-ocm-1.4-jcr-1385.jar:na] >> >> at >> >> >> >> >> org.artifactory.security.JcrUserGroupManager.loadUserByUsername(JcrUserGroupManager.java:95) >> >> [artifactory-core-2.0.6.jar:na] >> >> at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown >> Source) >> >> [na:na] >> >> at >> >> >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> [na:1.6.0_15] >> >> at java.lang.reflect.Method.invoke(Method.java:597) >> [na:1.6.0_15] >> >> at >> >> >> >> >> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) >> >> [spring-aop-2.5.5.jar:2.5.5] >> >> at >> >> >> >> >> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) >> >> [spring-aop-2.5.5.jar:2.5.5] >> >> at >> >> >> >> >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) >> >> [spring-aop-2.5.5.jar:2.5.5] >> >> at >> >> >> >> >> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) >> >> [spring-tx-2.5.5.jar:2.5.5] >> >> at >> >> >> >> >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) >> >> [spring-aop-2.5.5.jar:2.5.5] >> >> at >> >> >> >> >> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) >> >> [spring-aop-2.5.5.jar:2.5.5] >> >> at $Proxy42.loadUserByUsername(Unknown Source) [na:na] >> >> >> >> How broken is our server and how might I fix this? Thoughts gratefully >> >> accepted. >> >> >> >> Doug >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Publishing-fails-with-500-error-tp25480947p25480947.html >> >> Sent from the Artifactory-Users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> >> is the only developer event you need to attend this year. Jumpstart >> your >> >> developing skills, take BlackBerry mobile applications to market and >> stay >> >> ahead of the curve. Join us from November 9-12, 2009. Register >> >> now! >> >> http://p.sf.net/sfu/devconf >> >> _______________________________________________ >> >> Artifactory-users mailing list >> >> [email protected] >> >> https://lists.sourceforge.net/lists/listinfo/artifactory-users >> >> >> > >> > >> ------------------------------------------------------------------------------ >> > Come build with us! The BlackBerry® Developer Conference in SF, CA >> > is the only developer event you need to attend this year. Jumpstart >> your >> > developing skills, take BlackBerry mobile applications to market and >> stay >> > ahead of the curve. Join us from November 9-12, 2009. Register >> > now! >> > http://p.sf.net/sfu/devconf >> > _______________________________________________ >> > Artifactory-users mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/artifactory-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Publishing-fails-with-500-error-tp25480947p25491960.html >> Sent from the Artifactory-Users mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register >> now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> Artifactory-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/artifactory-users >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users > > -- View this message in context: http://www.nabble.com/Publishing-fails-with-500-error-tp25480947p25510684.html Sent from the Artifactory-Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
