Hi guys,
It will be good to save the manager, executor, client application (if
any) logs whenever anyone experiences these kinds of problems with Alchemi.
This way, we will be able to try and find out what causes the error.
Sometimes, I think it gets quite hard to reproduce the errors, due to
the very nature of distributed computing.
I have noted down some things, looking at the messages, but havent been
able to reliably reproduce any of the errors all the time so far. So,
havent got around to considering them bugs as yet. Some of them may be
bugs, other's may be bad initial settings / corrupt database [ we'll
really need to try to avoid that one : seems to be causing lots of
problems... ]
So, Luis, do you have the logs for the manager,executor when this happened?
Also, do you have the logs, when you had 2 or 3 unfinished threads
remaining at the end of the application?
In some cases, it also helps to know what is in the database. This
especially applies to appearance of phantom Executors and connection
issues.
I have fixed the Manager start problems, which Jonathan mentioned, but
before releasing a bug-fix version, say 1.0.1 or something, I would like
to know about other problems so we can fix as many as possible quickly
and put out one that is much more stable.
I would also like suggestions from users/developers about how they would
like the initial setup/configuration improved? Apart from the Manager
connection issues which Jonathan mentioned, are there any other setup
problems people faced? How can the process be improved ... from the
user's perspective what is preferred?
Also, so far the "service" mode Executor, and Manager have required
manual editing of xml config files, before start up. It looks like not
many messages have appeared about these...but it does seem very
inconvenient. I have now made a Service Controller, for both the
Manager and Executor, which actually looks exactly like the normal GUI,
but controls the Manager / Executor service, so that it is easier to
configure and manage. The service installation will run the controller
app immediately after the setup, so that initial settings are
configured. Again, I would like to put these out only once the first set
of bugs / issues are resolved, hopefully within the next couple of weeks.
Then, we will probably start working on the next version, which is
mostly going to involve an upgrade to C# 2.0 (.Net 2.0 framework).
Cheers
Krishna.
Message: 4
From: "Tibor Biro" <[EMAIL PROTECTED]>
To: "'Luis Cota'" <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Date: Fri, 6 Jan 2006 10:26:43 -0500
Subject: [Alchemi-developers] RE: [Alchemi-users] Executor Doesn't Exit Cleanly
This is a multi-part message in MIME format.
------=_NextPart_000_04E6_01C612AB.B1596050
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi Luis,
This happened to me several times but not consistently. I'm pretty sure
there is a bug here but haven't had the time to work on reproducing it. It
would be great if we find something that always makes it happen, this way
we'll be able to fix it.
Regards,
Tibor
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luis Cota
Sent: Friday, January 06, 2006 9:29 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [Alchemi-users] Executor Doesn't Exit Cleanly
Sometimes, when exiting the Executor program, the application disappears
from the screen but remains an active process. When I attempt to re-open
the application, two copies show up in the process list and the new one is
unable to connect.
Has anyone else experienced this?
- Luis
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Alchemi-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alchemi-developers
