Re: [Artifactory-users] Failed to parse metadata

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Thanks for the response.

I've only just started administrating this Artifactory install and the archived logs only go back to Friday, probably due to the spam of it checking every few seconds. So I can't determine where the original error occurred.

The Jboss repository is an external repository, assuming this is then cached in the jboss-cached repository, I can try trawling through to find the errant meta data or zap the cache and hope it rebuilds when required?

JDK  is 1.6.0_17
Artifactory version is Artifactory Pro Power Pack 2.6.4 (rev. 13153)
I  believe we are still using the default derby database

Is there a way to improve the debug so that it outputs the actual meta-data file that Artifactory is having an issue with?

Regards,

Dan

From: Pacileo, Ken [mailto:ken...@uh...]
Sent: 03 December 2012 15:13
To: art...@li...
Subject: Re: [Artifactory-users] Failed to parse metadata

Hi Dan,

What version of Artifactory, JDK & DB are you using?

We've had a similar problem from time to time. We usually identify the corrupt file and delete it as soon as Artifactory is restarted otherwise Artifactory becomes unresponsive again.

The error messages indicate it is a maven metadata file in the jboss repo. Look in the log file when the error first started to identify the file. Then delete it using Artifactory's UI after you have restarted Artifactory.

HTH,
Ken

From: Russell, Daniel [mailto:Dan...@ex...]<mailto:[mailto:Dan...@ex...]>
Sent: Monday, December 03, 2012 9:36 AM
To: art...@li...<mailto:art...@li...>
Subject: [Artifactory-users] Failed to parse metadata

Afternoon,

I keep seeing the messages below repeated over and over in our artifactory logs and Artifactory has become slow and unresponsive; about to restart Artifactory, but what is the best way to resolve it?

Regards,

Dan

2012-12-03 13:02:49,476 [pool-1-thread-17] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fr
om repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tt
ext-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:02:49,498 [pool-1-thread-19] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fr
om repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tt
ext-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:03:26,596 [pool-1-thread-4] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fro
m repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tte
xt-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:03:26,619 [pool-1-thread-20] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fr
om repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tt
ext-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:03:39,564 [pool-1-thread-17] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fr
om repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tt
ext-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:03:39,585 [pool-1-thread-19] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fr
om repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tt
ext-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:04:27,340 [pool-1-thread-9] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fro
m repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tte
xt-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .
2012-12-03 13:04:27,426 [pool-1-thread-6] [ERROR] (o.a.r.v.i.MavenMetadataInterceptor:170) - IO exception retrieving maven metadata content fro
m repo 'jboss': Failed to parse metadata: end tag name </head> must be the same as start tag <meta> from line 7 (position: TEXT seen ...{\n\tte
xt-decoration: underline;\n\tcolor: #999999;\n}\n</style>\n</head>... @86:8) .

Information in this e-mail and any attachments is confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient. Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer virus, you are advised to take your own steps to ensure that they are actually virus free.
Companies Act information: Registered name: Experian Limited. Registered office: Landmark House, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and Wales. Registered number: 653331

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.