Snapnames.com is down with errors...

[DN BROKER]

anyone else experiencing this issue?

SnapNames: Application Error Page


--------------------------------------------------------------------------------

The SnapNames Application generated an error while attempting to service your request. The details of the error are printed below.

Likely, the conditions that resulted in this error are temporary. Should you receive this message again, please contact SnapNames customer support at (800)385-4075. You may wish to print this page to assist the support representative.


Exception details:
Class:
javax.servlet.jsp.JspException
Message:
Problem while trying to get auction count.
Stack Trace:
javax.servlet.jsp.JspException: Problem while trying to get auction count.
at com.snapnames.webapps.auction.taglib.AuctionCountTag.makeCountString(AuctionCountTag.java:172)
at com.snapnames.webapps.auction.taglib.AuctionCountTag.retrieveCountString(AuctionCountTag.java:198)
at com.snapnames.webapps.auction.taglib.AuctionCountTag.doStartTag(AuctionCountTag.java:122)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:708)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:298)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:413)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at com.snapnames.webapps.auction.filters.AuctionSessionFilter.doFilter(AuctionSessionFilter.java:152)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at com.snapnames.webapps.common.filters.NoCacheFilter.doFilter(NoCacheFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:694)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:626)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644)
at java.lang.Thread.run(Thread.java:619)

Parameter Listing:
badPage = "index.jsp"
Request Attribute Listing:
javax.servlet.include.request_uri = "/error.jsp"
javax.servlet.include.context_path = ""
javax.servlet.include.servlet_path = "/error.jsp"
javax.servlet.include.query_string = "badPage=index.jsp"
javax.servlet.jsp.jspException = "javax.servlet.jsp.JspException: Problem while trying to get auction count."
javax.servlet.error.status_code = "500"
javax.servlet.error.servlet_name = "jsp"
javax.servlet.error.exception = "javax.servlet.jsp.JspException: Problem while trying to get auction count."
javax.servlet.error.request_uri = "/index.jsp"

 

[PowerUp]

Lately, their website's always been down. I think it started about the same time it was bought over by another company (I think is Oversee).

 

[hawkaw]

Yeah, wonder if they're upgrading their system, cause it's been very buggy for the last couple of weeks. Still cannot access their page (timeout)

 

[Shane]

Ooo I bet thats caused some problems for customers!

 

[mahadeva]

During the last outage of SnapNames, at least the Registrar site manage.snapnames.com was up - but not this time!

 

[hawkaw]

I also notice that domains recently acquired by SnapNames and parked at their servers don't show up either. Guess the problems must be seriously affecting their revenue made from parking....

 

[The Stealthy One]

Now their site isn't even showing up at all. Just getting an Error 404 page.

 

[canswift]

It's 12.20pm PST here and Snapnames is unavailable for me (still). This is becoming quite a regular situation now, and not one that ever seems to get explained by Snapnames. I had a name on backorder that was supposed to drop today, and will be very PO'd if Snapnames wasn't able to even try and grab it because of the outage...

 

[gazzip]

I know how you feel, I have one I really wanted to get today but I had'nt placed a backorder on it yet because other people would notice, now I have no chance


About time they sorted it out, it was much better before Oversee owned it.



.

 

[jmcc]

It seems that the recent changes on domain tasting cut off one of Snapnames' revenue streams.

Regards...jmcc

 

[canswift]

Does anyone know whether the "back-end" (so to speak..) of Snapnames goes down as well as the "front-end" at a time like this? Are Snap still catching the domains and only having to postpone the auctions?

 

[gazzip]

Does anyone know whether the "back-end" (so to speak..) of Snapnames goes down as well as the "front-end" at a time like this? Are Snap still catching the domains and only having to postpone the auctions?

I'm not sure but a couple of weeks ago i tried to get one but snap went down for a few days, the domain now shows as

Name Server: NS1.EXPIREDDOMAINS.REGISTER.COM

but the expiry date shows as 2009 - The domain does'nt show as dropping anymore in Snap, guess I'll have a very long wait till it gets back into the real drop system :td:


.

 

[canswift]

Is there a rep from Snapnames on this forum? With the 2+ day outage at the beginning of July , and now this (24 hours and counting...) it would be good to have some official word from Snapnames. Even after the lengthy outage last month, all we really got was a bare-bones bog standard "our apologies for the inconvenience" email from Snapnames, with no word of real explanation.

Considering how much business many NPers do with Snapnames, we really deserve better than this...

 

[michaeldotcom]

Is there a rep from Snapnames on this forum?

If I'm not mistaken, Monte Cahn is the president of Snapnames, as well as the CEO of Moniker, and he comes on NP from time to time.

Would be nice if he could come and reply to the questions asked in this thread.

 

[hawkaw]

Snapnames just sent this statement to all of their customers:

As you may already be aware, the SnapNames service has been unavailable since Saturday evening, U.S. Pacific time. Since then, our technical team has been working to restore service. Our current estimate is for the service to be on line in the next 18 hours. Should that estimate change, we will post an update at www.snapnames.com .

We recognize this is the third outage for our service within the last several weeks. The problem is related to one of our vendors' systems, unfortunately, and our team has been working nonstop with the vendor to correct the issue.

Outages of this nature and duration of course are very unusual for SnapNames; since we began our service in 2001, outages have been extremely rare and our record for technical service, customer care and integrity has been well regarded by our customers and partners. It's very important to us to maintain that confidence in our service and our team, and we're working as quickly as we can to make sure the problem is resolved correctly.

If you currently have bids placed for auctions that were scheduled to end Sunday or today, those names will now be scheduled to complete auctions tomorrow and Wednesday, respectively. Again, if there is a change to that schedule, we will post a notice at the SnapNames site.

 

[djmadfx]

I'm guessing we can assume that the backend systems are down and not actively catching names.

 

[canswift]

I just got one of these emails too. Snapnames still doesn't say whether they were able to continue catching drops to fulfill advance orders during this outage. They only address the question of existing auctions. If they haven't been able to do any catches at all, then this must be costing them a small fortune, again...

 

[stever]

Snapnames still doesn't say whether they were able to continue catching drops to fulfill advance orders during this outage.

I asked them that. They said they were still acquiring names and that auctions for those would start when they were back up.

 

[canswift]

Thanks stever, now I can stop worrying. I usually wait till the last minute to put in an advance bid as I don't want to signal interest to others looking at the lists. For some reason this time I advance bid a day ahead, otherwise I'd be locked out of the auction (whenever it happens) by now.

I'm sure that the visible pre-bid practise has not been to Snapnames benefit in this outage, as many domainers now do wait till the last minute to advance bid. Unless Snapnames essentially re-sets their whole site to the point where the outage occurred, presumably all these potential advance bids would be lost?

 

[canswift]

All Snapnames customers will have probably received the email this morning saying they are back in business, and listing the drops they caught during the outage. There's only about 118 names on that list. Would that be their usual haul of names over a 48 hour period? It doesn't seem a lot to me, and sounds like they must have missed a boatload of drops...