Skip navigation
2014

Hi,

I’m pleased to announce that Fusesource forums has been migrated to jboss.org forums on Monday 18th of August, 2014.

 

Most of the content has been migrated as archive to Fusesource Archive space at https://community.jboss.org/en/fusesource-archive and then to two individual spaces 

Fuse ESB Enterprise at https://community.jboss.org/en/esb-enterprise and Fuse MQ Enterprise https://community.jboss.org/en/mq-enterprise.

 

All original URLs are permanently redirected to corresponding content at commnity.jboss.org.

 

Statistics

Over 16.000 posts migrated, including 830 attachments.

Over 1.500 new user accounts created. Accounts with same e-mail has been matched.

 

If your account has been newly created use Forgot password at https://community.jboss.org/emailPasswordToken%21input.jspa or  Forgot username https://community.jboss.org/forgot-username%21input.jspa features to access your account.

 

Special thanks go to Jakub Senko who implemented the migration plugin, Vladimir Vasilev who helped with eng-ops part on jboss.org side and Jon Anstey for his help on fusesource.com side.

 

Thanks,

 

Libor Krzyžanek

jboss.org Development Team

People report a bug that when they refresh Maven repository in their web browser (repository.jboss.org), they get different results (missing artifacts). This appears like a big bug, however I would like to shed light into this rather cosmetic problem.

 

It is caused by our new infrastructure behind repository.jboss.org. Originally there was just one server that handled artifacts. As the load increased this solution started not to be good enough. Therefore we added two proxy machines in front of the original one. They serve as mirrors for the original instance and they are load balanced by Apache. A classical mirror is a complete copy of all artifacts. The proxy machines are not classical mirrors though. The files are served using proxy repositories of Sonatype Nexus, that stores just content people ask for on the machines. When an artifact is requested, Nexus delivers it from the local content and if he does not find it locally it tries to obtain it from the master. However directory listing in the web browser is always served from the locally stored content.

 

And this is the reason, why the two machines have different directory listing. If one artifact is requested by someone the load balancer uses one of the mirrors and the artifact is added to the directory listing of that particular instance. But when one display the repository listing and then refreshes it,  what may happen is that the listing will be displayed from the second instance, that does not have the artifact yet .

 

So i you worry about your builds - no worry! Both mirrors are identical and always return all the requested artifacts (even if it appears they are not there). Browsing the repositories using web browser may be confusing though. I will fix the issue somehow buthe builds are fine so the problem is not that big as it appears to be.