mapguide hangs after 20 users access maps

[amitmarty]

System: 8 Processor / Win 2003 / Mapguide 2.0.2 Same Behavior occurs on Same machine but with centos 4.6 with 2.0.2 compiled from tar file and Patch from Ticket #726 applied

API: Java API Server: Tomcat/Apache/

Data: One Layer Only. Feature Objects are being queried from mySQL Database.

after access by about 20 to 25 users mgserver process will stop accepting any connections and user sees a indefinite hang.

I reported another issue with 2.1 a few minutes ago. Is there any enterprise level MG is being used with Tomcat ? Or is everyone running on PHP and not seeing the issues I am.

Thanks

[amitmarty]

Here is the trace log when mapguide is hung.

<2009-12-02T10:47:16> MgClientHandler::Initialize() - Address: 127.0.0.1:2812 <2009-12-02T10:47:16> MgServerSiteService::Authenticate() <2009-12-02T10:47:16> MgServerSiteService::Authenticate() <2009-12-02T10:47:16> MgServerSiteService::CreateSession() <2009-12-02T10:47:16> MgServerResourceService::CreateRepository() <2009-12-02T10:47:42> MgClientHandler::Initialize() - Address: 97.0.200.158:2812 <2009-12-02T10:47:42> MgServerSiteService::Authenticate() <2009-12-02T10:47:42> MgClientHandler::Initialize() - Address: 97.0.200.158:2811 <2009-12-02T10:47:42> MgServerSiteService::Authenticate() <2009-12-02T10:47:42> MgServerResourceService::GetResourceData() <2009-12-02T10:47:42> MgServerResourceService::GetResourceData() <2009-12-02T10:47:42> MgServerResourceService::GetResourceContent() <2009-12-02T10:49:36> MgClientHandler::handle_close() <2009-12-02T10:49:36> MgClientHandler::handle_close() <2009-12-02T10:50:36> MgClientHandler::handle_close()

[zspitzer]

What viewer technlogy are you using? fusion or classic?

Can you reproduce the problem with the sheyboygan dataset?

[amitmarty]

Classic Ajax Viewer. Have not tested against sheyboygan sample dataset. I am using a dynamic repository.

[zspitzer]

Sounds like a feature reader isn't being closed?

[amitmarty]

went through all of those and made sure I am closing it. In my case only one to check. Since the single layer is coming from the db.

[jbirch]

There were considerable changes to the connection handling code in 2.1. If you can test on that version, would be useful.

[jng]

Closed due to ticket inactivity and generally improved stability since 2.0.2