During the past couple of days our Tomcat installation, including the Xamin and login service web services, has not been very stable. This may be due to some error in the Xamin or login service web service but regardless of the origin, it is causing significant problems for Xamin queries. We have reset HEASARC cone and batch queries to use Browse until we identify and rectify the problem. We apologize for the inconvenience to users.
Update: [12/3] We have gone back to using Xamin for Cone and Batch queries.
The vast majority of the queries that the HEASARC receives are through automated interfaces that use either the VO cone search protocol or the Batch protocol we developed for Browse (long before the VO). Starting this week cone searches are running the Xamin interfaces. Usually there are more batch interface queries than cone searches, but there is a lot of variation. Yesterday we had a few more cone search requests and as a result Xamin satisfied more query requests than Browse for the first time, just under 10,000 Xamin queries versus just over 7,000 in Browse.
We’re looking at moving the Batch requests to Xamin in the next couple of weeks. Preliminary tests show it is up to 4x faster. When we do that Xamin will be handling over 90% of the HEASARC’s query load.