[Cosmo-dev] Cosmo not working?

[John Townsend]

On May 12, 2006, at 5:30 PM, Jared Rhine wrote:

> Sheila Mooney wrote:
>> It looks as though some people can't sync shares on Cosmo Demo today.
>
> No issue was being tracked.  There are error messages (SQL  
> Exception: No current connection) in the logs.  I've restarted the  
> server.
>

This could be a configuration issue with the connection pool on the  
database, couldn't it?

> It initially looks vaguely like another run-time error requiring a  
> restart.  The couple from a few weeks ago were similar, though  
> those messages were out of memory errors.
>
> The planned round-trip monitoring (create a real user and try to  
> get a resource from that user) will probably catch this case as  
> well as the OOM error otherwise found.
>
> I suspect a bug should still be opened.  Developers can examine the  
> run-time log for this period of time to determine if there's  
> something clear to fix.  Maybe try to create a connection of  
> there's "no current connection" or something like that.
>

I disagree with this. I would expect that the owner of any server in  
operation would do some of the legwork to spot what the possible  
issue might be. If there is something that is an honest software bug  
that requires a fix, then a bug should be opened.

There are many factors that go into maintaining operational servers.  
Everything from the network configuration to the amount of memory  
allocated to the server to how much free disk space you have. Many of  
those issues are things that can bring down a server and they have  
nothing to do with the actual software, they are part of the  
operating environment.

Bugs in bugzilla against Cosmo are bugs that require fixes in the  
software and that's very different from operational environment  
issues. I am not sure how we track those things, but they belong  
somewhere.. but not as a bug against Cosmo in Bugzilla.

--> John