Tibor,

 

Thanks for that.  You were right it failed to connect.

 

Here is the log file

 

2006-07-08 16:41:17,354 [3140] INFO  - Connecting....

2006-07-08 16:41:17,364 [3140] DEBUG - ExecutorContainer:Connect():0 - Created remote-end-point

2006-07-08 16:41:17,364 [3140] DEBUG - ExecutorContainer:Connect():0 - Created own-end-point

2006-07-08 16:41:17,774 [3140] DEBUG - GExecutor:.ctor():0 - datadir=I:\Program Files\Alchemi\Executor\dat

2006-07-08 16:41:17,784 [3140] DEBUG - GExecutor:.ctor():0 - Id is 550a7a4c-3e61-4fb6-bed4-2dd28d052de4

2006-07-08 16:41:17,795 [3140] DEBUG - GExecutor:ConnectToManager():0 - Connecting to Manager dedicated...

2006-07-08 16:41:22,311 [3140] WARN  - Exception starting Executor service...Reconnecting...

 

System.Runtime.Remoting.RemotingException: Server encountered an internal error. For more information, turn off customErrors in the server's .config file.

 

Server stack trace:

 

 

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Alchemi.Core.IManager.Executor_ConnectDedicatedExecutor(SecurityCredentials sc, String executorId, RemoteEndPoint executorEP)

   at Alchemi.Executor.GExecutor.ConnectToManager()

   at Alchemi.Executor.GExecutor..ctor(RemoteEndPoint managerEP, OwnEndPoint ownEP, String id, Boolean dedicated, SecurityCredentials sc, String baseDir)

   at Alchemi.Executor.ExecutorContainer.Connect()

   at Alchemi.Executor.ExecutorContainer.Start()

   at Alchemi.ExecutorService.ExecutorService.StartContainer()

2006-07-08 16:41:22,331 [3140] ERROR - Error trying to reconnect:

 

System.NullReferenceException: Object reference not set to an instance of an object.

   at Alchemi.Executor.ExecutorContainer.Reconnect(Int32 maxRetryCount, Int32 retryInterval)

   at Alchemi.Executor.ExecutorContainer.Reconnect()

   at Alchemi.ExecutorService.ExecutorService.StartContainer()

 

Also on the server the following was in the log file.

 

2006-07-08 16:41:21,890 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - GManager:PingManager():0 - Manager pinged successfully.

2006-07-08 16:41:22,031 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutor:VerifyExists():0 - Checking if executor :550a7a4c-3e61-4fb6-bed4-2dd28d052de4 exists in db

2006-07-08 16:41:22,031 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutor:VerifyExists():0 - Executor :550a7a4c-3e61-4fb6-bed4-2dd28d052de4 exists in db=False

2006-07-08 16:41:22,031 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutorCollection:RegisterNew():0 - Registered new executor id=550a7a4c-3e61-4fb6-bed4-2dd28d052de4

2006-07-08 16:41:22,046 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - GManager:Executor_ConnectDedicatedExecutor():0 - Executor called: ConnectDedicated: Authenticate,EnsurePermission,Connect,Set DedicatedScheduler

2006-07-08 16:41:22,046 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutor:ConnectDedicated():0 - Trying to connect Dedicated to executor: 550a7a4c-3e61-4fb6-bed4-2dd28d052de4

2006-07-08 16:41:22,046 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutor:VerifyExists():0 - Checking if executor :550a7a4c-3e61-4fb6-bed4-2dd28d052de4 exists in db

2006-07-08 16:41:22,046 [5124] DEBUG [(null)] [{log4net:HostName=EINSTEIN-01}] - MExecutor:VerifyExists():0 - Executor :550a7a4c-3e61-4fb6-bed4-2dd28d052de4 exists in db=True

2006-07-08 16:41:26,546 [5124] ERROR [(null)] [{log4net:HostName=EINSTEIN-01}] - Error connecting to exec: 550a7a4c-3e61-4fb6-bed4-2dd28d052de4

System.Runtime.Remoting.RemotingException: Server encountered an internal error. For more information, turn off customErrors in the server's .config file.

 

Server stack trace:

 

 

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Alchemi.Core.IExecutor.PingExecutor()

   at Alchemi.Manager.MExecutor.ConnectDedicated(RemoteEndPoint ep)

2006-07-08 16:41:26,546 [5124] ERROR [(null)] [{log4net:HostName=EINSTEIN-01}] - Couldnt connect back to the supplied executor

 

Alchemi.Manager.ExecutorCommException ---> System.Runtime.Remoting.RemotingException: Server encountered an internal error. For more information, turn off customErrors in the server's .config file.

 

Server stack trace:

 

 

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Alchemi.Core.IExecutor.PingExecutor()

   at Alchemi.Manager.MExecutor.ConnectDedicated(RemoteEndPoint ep)

   --- End of inner exception stack trace ---

   at Alchemi.Manager.MExecutor.ConnectDedicated(RemoteEndPoint ep)

   at Alchemi.Manager.GManager.Executor_ConnectDedicatedExecutor(SecurityCredentials sc, String executorId, RemoteEndPoint executorEP)

 

I see the msg that says switch off customErrors in the .config file. Where will I find that file?

 

Thanks for your help.

 

Jon Gould

 

 

 

-----Original Message-----
From: Tibor Biro [mailto:[EMAIL PROTECTED]
Sent: Sunday, 9 July 2006 4:37 AM
To: 'Jon Gould'; [email protected]
Subject: RE: [Alchemi-users] Alchemi - Initial Steup Problem

 

Hi Jon,

 

If the executor is grey it is not an active executor. You might see the other executor you tested with earlier. Executors are not removed automatically from the storage.

 

Verify on the remote executor if it connected successfully to the manager. My guess is that it failed to connect. You should see in the UI a successful connection message. There is also a log file in the executor’s dat folder that you can examine to see what the problem is.

 

Regards,

Tibor

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Gould
Sent: Saturday, July 08, 2006 4:53 AM
To: [email protected]
Subject: [Alchemi-users] Alchemi - Initial Steup Problem

 

Hi,

 

I’ve tried to set this up for the first time. 

 

I’ve been able to get the manager running using the “In Memory option” and setup an executor on the same computer. The samples ran fine.

I then tried adding an exector on a separate machine.

 

The console running on the manager box can see the other executor but it comes up grey rather than orange. If I look at the grey executor properties the connected and dedicated checkboxes are unchecked. The last time connected says 1054799568.71 mins. Ago and the ID has a value. However this value doesn’t seem to make it back to the other node.

 

What sort of things should I be looking at to get it going?

 

Thanks.

 

Jon

 

 

 

 

 

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
alchemi-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alchemi-users

Reply via email to