opinionate:

It's not necessary for you guys to report every forum error you see anymore. We know it's a problem and Community Server is working on it for us. Sorry for the annoyance in the meantime.

If it alleviates your frustration, however, by all means let it out.

Don't give me an opening like that!!!

But seriously, Nate do you have any idea when this situation might improve?  My IE homepage is the Waymarking Forums... frequently it times out.  Often I try to read threads and it times out or takes a really long time... forget replying most times... takes too long to work, if it does at all.

I'd love to get caught up on all of the threads I've missed but with the limited performance it is very difficult to do so.  I have a lot to read, and would like to.

Help me Obi-Nate-Kenobi.. you're my only hope!

BQ

<the blue quasar> skrev i en meddelelse news:10571@portal.groundspeak.com...

Help me Obi-Nate-Kenobi.. you're my only hope!

BQ

Time to vent again and resurface this in order to keep the issue in the forefront.

I experience so many timeouts and clocking at all times of the day and any day of the week that it seems like only one person can access the forum at a time.  Seriously, I wonder how many concurrent forum readers/posters it takes to bog the forum down.  Or maybe it's some kind of completely random thing that isn't linked to the number of users. (Like a gremlin).

I do multitask to try and manage it, but sometimes it seems I wait for hours for the thing to come back.

hikenutty:

It's weird because it almost seems like some people have more problems with this issue than others.  Although I still get time outs on the forums, it's rare that I ever get a time out on the actual Waymarking.com site.  I used to, but in the last few months it just hasn't been an issue for me.  I wonder if it has to do with what type of browser a person uses?

hikenutty:

It's weird because it almost seems like some people have more problems with this issue than others.  Although I still get time outs on the forums, it's rare that I ever get a time out on the actual Waymarking.com site.  I used to, but in the last few months it just hasn't been an issue for me.  I wonder if it has to do with what type of browser a person uses?

Yes, I agree that posting waymarks is no longer the problem it once was.  I was specifically referring to the forum.  Hope Groundspeak has still got their sights on this.  The problem started last year around July and the prognosis from Groundspeak was that it would be cleared up in about a month (August).  Well that didn't happen.  Looking for a new target for issue resolution.

It took me the normal two steps to see the list of threads with posts I haven't read.  It took three tries to overcome the timeouts and get to page two so I could see the new posts.  And it took two tries to post this reply without an error message.  (On the third attempt, the message did post to the forum, but I still got a "request timed out" error.)  The forum software still isn't ready for prime time.  This cuts down on the amount of time I spend here.

In contrast, the Waymarking site is performing very well for me.  I am not having any issues with it.

Another side effect of forum performance issues is that discussion about categories in the forum could be restricted.  I noticed a category coming through review which was also posted on the forums.  However, I didn't bother to look at the thread because I try to reserve my forum time for only the most important items knowing that looking at just a few discussions can take an eternity due to timeouts.  Now as part of peer review I do have comments that probably would have been better posted in the forum.

Just another reason to focus attention on the forum performance issue (for which groundspeak hasn't come out with information on in quite a while.)

Has there been any progress on this issue?  One would like to think that hopefully some troubleshooting has narrowed it down to either Groundspeak issue or problem in the Community Server software.  I'm tending towards CS 2.0 since nothing on Geocaching seems this flakey and it gets pounded by users far harder than we ever could do here.

I know you guys are probably ties up in various site enhancements... but it seems like its been a while since we've heard from either of you.... 

ping?

BQ

Still getting these.  No noticeable improvement in performance.

Server Error in '/' Application.

---

Request timed out.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

[HttpException (0x80004005): Request timed out.]

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

opinionate:

We have Elias to thank for discovering the source of the timeout errors on Friday. While there are still some issues to be worked out, it looks as though the bulk of the errors have been solved. Hurray!

I think I might just buy that boy a beer (someday)!

with Elias = priceless

BQ

opinionate:

We have Elias to thank for discovering the source of the timeout errors on Friday. While there are still some issues to be worked out, it looks as though the bulk of the errors have been solved. Hurray!

Pay that man a bonus!

sprinterman:

Twice today I have spent 20+ minutes composing a waymark only to have it obliterated with a fatal error when I clicked the submit button. Is anyone else having this problem?

Check out this thread http://portal.groundspeak.com/forums/thread/15330.aspx .  Although the portal performance is greatly improved, the site may still be suffering from continued unexpected behavior.

It's back ....

Server Error in '/' Application.

---

Request timed out.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

[HttpException (0x80004005): Request timed out.]

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300