ow2-proactive / agent-windows Goto Github PK

Original issue created by Cédric Dalmasso on 27, Jul 2009 at 12:22 PM - AGENT-33

---

I don't know if there is a way to install the shortcuts only for admin users, probably not easily. It's not a major issue but it would be nicer at least to warn a non admin user trying to launch the ProActive Agent Control that he have to have the admin rights.
The current behaviour lead to a non friendly error message, actually the same one attached to issue AGENT-31.

Original issue created by Vladimir Bodnartchouk on 23, Sep 2009 at 10:32 AM - AGENT-46

---

Both username/password and credentials mechanisms must be supported.

Original issue created by Cédric Dalmasso on 27, Jul 2009 at 11:24 AM - AGENT-30

---

use ProActive Parallel Suite instead

Original issue created by Jean-Luc Scheefer on 05, Aug 2009 at 15:21 PM - AGENT-40

---

The message displayed when leaving GUI without having the modification saved should be :

"Save before exit" YES/NO
YES -> save and leave the GUI edit
NO -> just close the panel

Original issue created by Salageanu Emil on 08, Aug 2008 at 14:52 PM – AGENT-15

---

08/08/2008 14:36:55 ::Full path of the script: C:\Program Files..\ProActive\ProActiveAgent\agentservice.bat
08/08/2008 14:36:55 ::Arguments: “C:\Documents and Settings\ohelin\Bureau\plop\pa” “C:\Program Files\Java\jdk1.6.0_04” "" “ADVERT” " olivier"

‘C:\Program’ n’est pas reconnu en tant que commande interne
ou externe, un programme executable ou un fichier de commandes.

Original issue created by Salageanu Emil on 13, Aug 2008 at 14:27 PM – AGENT-18

---

No description

Original issue created by Salageanu Emil on 24, Jul 2008 at 16:21 PM – AGENT-13

---

reset the delay after each new event

Original issue created by Salageanu Emil on 17, Jul 2008 at 16:00 PM – AGENT-4

---

now, the user needs to press save button and then cancel in order to the changes to take effect.
Save button should save data and close the window.

Original issue created by Salageanu Emil on 24, Jul 2008 at 16:19 PM – AGENT-12

---

like “allways on”, “during off time” etc

Original issue created by Salageanu Emil on 17, Jul 2008 at 15:22 PM – AGENT-1

---

Create a schema for the agent configuratyion file PAAgent-config.xml.
The config file should be checked before parsing and, if it doesn’t respect the schema, a message should be shown to the user.

See AgentForAgent public partial class ConfigEditor contructor. Note: use xsd tool to generate the schema

Original issue created by Salageanu Emil on 17, Jul 2008 at 15:24 PM – AGENT-3

---

See AgentWindow.cs file

Original issue created by Cédric Dalmasso on 03, Aug 2009 at 18:57 PM - AGENT-37

---

I have tried (just for fun :-D ) to put something in the Node Source Name field, in the "Resource Manager Registration" configuration part. The registration failed with the following logs in the executor log file.

2009-08-03 18:52:32,652 - Usage: java PAAgentServiceRMStarter username password rmUrl nodename
2009-08-03 18:52:33,822 - Usage: java PAAgentServiceRMStarter username password rmUrl nodename

There is nothing in the documentation about this configuration field, so I suspect that this behavior is a bug.

Original issue created by Salageanu Emil on 01, Sep 2008 at 11:21 AM – AGENT-20

---

first event: monday 10:50 for 10 minutes
second event: monday 10:58 for 1 minute
agent started mondat at 10:57

the runtime is not stop at 11:00 as it should be. We see in the logs:

01/09/2008 10:57:02 ::OUTPUT: —> This ClassFileServer is listening on port 2026
01/09/2008 10:57:03 ::OUTPUT: Created a new registry on port 1099
01/09/2008 10:57:03 ::OUTPUT: The node was registered at rmi://127.0.0.1:1099/PA-AGENT_NODE
01/09/2008 10:58:00 ::mySendStartAction
01/09/2008 10:58:00 ::Received start action request from AgentScheduler
01/09/2008 10:59:00 ::Received stop action request from AgentScheduler
01/09/2008 11:00:00 ::Received stop action request from AgentScheduler

First thing to do is to log the operation that leeds to the decision to start/stop the runtime.

Original issue created by Salageanu Emil on 18, Jul 2008 at 15:01 PM – AGENT-7

---

the installer should:
1. check for prerequisites: – visual c++ 2008 redustributable package (if not, install it)
– .net framework (if not, give a link to the user to download and install)
2. dialog with user

``` - confirm the location of ProActive /Scheduler (the default location will be read from the config file. if chanded by the user, the config file will be updated. ) → check if location ok. (???) ``` - ask for Agent Home Directory (propose for c:\ProActiveSoftware\WindowsAgent) - ask for the JAVA_HOME directory (look for an installed JAVA_HOME and propose it to the user: JAVA_HOME sys var or c:\P F\JAVA\jdk ….)

- ask user if the screen saver will be installed (or choose between components)
1. Functional (what it does)

→ copy the Agent files in the Agent home dir → update the config file if needed → write in the registries the values for : - Agent home directory - configuration file location → running the agent/install.bat program → copy the screen saver files in .. Windows/ system32 → run the Administration console program (actually Agent4Agent)

Original issue created by Christian Delbé on 11, Jun 2009 at 16:44 PM - AGENT-23

---

The node started by the agent are always added in the default node source (with RM config). The user must be able to define another node source.

Original issue created by Salageanu Emil on 18, Jul 2008 at 14:33 PM – AGENT-5

---

if the file do not comply to the schema, show a message to the user advising him to edit the file and fix the problem.

Original issue created by Cédric Dalmasso on 27, Jul 2009 at 12:09 PM - AGENT-32

---

The documentation is distributed within the documentation.pdf file. A more precise name would be better.
What about ProActiveAgent_documentaton.pdf or something like that

Original issue created by Cédric Dalmasso on 21, Jul 2009 at 13:17 PM - AGENT-26

---

as shown in the agent's logs below the windows directory does not exist in the bin directory of ProActive programming

2009-07-21 12:18:27,906 INFO ProActiveAgent.WindowsService - Starting ProActive Agent service
2009-07-21 12:18:28,483 ERROR ProActiveAgent.WindowsService - An exception occured when reading the classpath
System.ApplicationException: Unable to read the classpath, cannot find the initialization script C:\Users\sucdalmass\Documents\PPS\ProActive-4.0.2\bin\windows\init.bat
at ProActiveAgent.Utils.readClasspath(AgentConfig config)
at ProActiveAgent.WindowsService.OnStart(String(link: ) args)

Original issue created by Salageanu Emil on 18, Jul 2008 at 15:02 PM – AGENT-9

---

should be launched minimised

Original issue created by Vladimir Bodnartchouk on 10, Aug 2009 at 17:30 PM - AGENT-45

---

No description

Original issue created by Cédric Dalmasso on 21, Jul 2009 at 13:10 PM - AGENT-25

---

In the configuration editor for the ProActive windows agent the ProActive location field is misleading. I understood that I have to fill in it with the ProActive path whereas it is the ProActive Scheduling path...

So, it would be nice to change the name of this field or even better/easier add a help or infobulle

Original issue created by Vladimir Bodnartchouk on 10, Aug 2009 at 12:08 PM - AGENT-43

---

Some situations require additional native cleaning operation after a runtime is finished (jvm terminated) for example in case of severe error. The .bat/.cmd should be executed each time a runtime exits. In case of Multi-Runtime there should be as many scripts execution as runtimes. The pid of the runtime should be passed as parameter of the script.

Original issue created by Cédric Dalmasso on 21, Jul 2009 at 10:19 AM - AGENT-24

---

I didn' t succeed to install the Windows agent on Windows Vista.
Two successive errors raised:

• First, the message described in attached image install_ProActiveAgent error.png
  As requested I have disabled the UAC feature in the user account panel.
• After a reboot a second message described in attached image install_ProActiveAgent error_2.png

Original issue created by Salageanu Emil on 18, Jul 2008 at 14:39 PM – AGENT-6

---

if the file does not meet the schema requirements when trying to GUI edit it we have an error message. The system should propose the user to clean the conf file (delete) and recreate it with the GUI.

Original issue created by Vladimir Bodnartchouk on 28, Jul 2009 at 14:12 PM - AGENT-35

---

This can solve different kind of problems in case of Multi-Runtime such as specifying different ports for each Runtime.

Original issue created by Salageanu Emil on 08, Aug 2008 at 15:04 PM – AGENT-16

---

No description

Original issue created by Vladimir Bodnartchouk on 15, Oct 2009 at 20:11 PM - AGENT-48

---

License headers.

Original issue created by Vladimir Bodnartchouk on 04, Aug 2009 at 16:17 PM - AGENT-38

---

No backward compatibility from 1.1

Original issue created by Salageanu Emil on 24, Jul 2008 at 14:19 PM – AGENT-11

---

No description

Original issue created by Salageanu Emil on 18, Jul 2008 at 15:01 PM – AGENT-8

---

No description

Original issue created by Cédric Dalmasso on 03, Aug 2009 at 18:41 PM - AGENT-36

---

If I only put pataud.activeeon.com in the field "Resource Manager URL" I have the two following errors dependdin the protocol selected

whit the "rmi" protocol selected

2009-08-03 18:31:08,321 - Could not join the Resource Manager at pataud.activeeon.com
2009-08-03 18:31:08,337 - org.ow2.proactive.resourcemanager.exception.RMException: The url rmi:/pataud.activeeon.com/RMAUTHENTICATION is not bound to any known object
2009-08-03 18:31:08,337 - The Resource Manager at pataud.activeeon.com is unreachable ! The application will exit.
2009-08-03 18:31:08,337 - at org.ow2.proactive.resourcemanager.frontend.RMConnection.waitAndJoin(RMConnection.java:111)
2009-08-03 18:31:08,337 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.registerInRM(PAAgentServiceRMStarter.java:117)
2009-08-03 18:31:08,337 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.main(PAAgentServiceRMStarter.java:82)
2009-08-03 18:32:32,290 - Could not join the Resource Manager at pataud.activeeon.com
2009-08-03 18:32:32,290 - The Resource Manager at pataud.activeeon.com is unreachable ! The application will exit.
2009-08-03 18:32:32,290 - org.ow2.proactive.resourcemanager.exception.RMException: The url rmi:/pataud.activeeon.com/RMAUTHENTICATION is not bound to any known object
2009-08-03 18:32:32,290 - at org.ow2.proactive.resourcemanager.frontend.RMConnection.waitAndJoin(RMConnection.java:111)
2009-08-03 18:32:32,290 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.registerInRM(PAAgentServiceRMStarter.java:117)
2009-08-03 18:32:32,290 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.main(PAAgentServiceRMStarter.java:82)

with the "http" protocol selected

2009-08-03 18:37:00,805 - org.ow2.proactive.resourcemanager.exception.RMException: org.objectweb.proactive.core.remoteobject.http.util.exceptions.HTTPRemoteException: Unknown remote host: http://null:-1
2009-08-03 18:37:00,805 - at org.ow2.proactive.resourcemanager.frontend.RMConnection.waitAndJoin(RMConnection.java:111)
2009-08-03 18:37:00,805 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.registerInRM(PAAgentServiceRMStarter.java:117)
2009-08-03 18:37:00,805 - at org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter.main(PAAgentServiceRMStarter.java:82)
2009-08-03 18:37:00,805 - The Resource Manager at pataud.activeeon.com is unreachable ! The application will exit.

Original issue created by Salageanu Emil on 22, Jul 2008 at 15:31 PM – AGENT-10

---

show to the user the first 3 lines of the command:

java -jar PROACTIVE_HOME/dist/lib/ProActive.jar

Original issue created by Olivier Helin on 07, Aug 2009 at 15:47 PM - AGENT-42

---

It will be interesting to create a subfolder "config" in the Agent installation path.

Original issue created by Olivier Helin on 13, Oct 2009 at 14:19 PM - AGENT-47

---

When we click on "Save" in GUI Configuration Editor, a information message appear :
"The ProActive Agent must be restarted to apply changes. Display this message again ? Yes/No"

It would be well to ask to the user if he wants to restart automatically. (Application.Restart() )

Original issue created by Vladimir Bodnartchouk on 10, Aug 2009 at 15:29 PM - AGENT-44

---

Add a tooltip for each ui element that briefly explains the purpose of the element.

Original issue created by Christian Delbé on 23, Oct 2009 at 18:14 PM - AGENT-49

---

Even if Use Default Credential is not checked, the started runtime try to access to cred,enc in home dir.

Original issue created by Vladimir Bodnartchouk on 24, Jul 2009 at 16:39 PM - AGENT-28

---

In the configuration when the user specifies the node name, the ProActive Agent will automatically add the runtime rank to the node name in case of multi runtime, since each runtime is started with a unique proactive rmi port, the rank additivity is no more required.

Original issue created by Jean-Luc Scheefer on 05, Aug 2009 at 15:52 PM - AGENT-41

---

There is a panel asking to keep displaying the "restart to perform changes" message.

The way to ask if user want to keep this message or not should be the "common" way : check box

Original issue created by Christian Delbé on 23, Oct 2009 at 18:23 PM - AGENT-51

---

After the first install, the AgentForAgent service failed (windows popup "send a report").
With one particular JDK, a "Java : no such process " occurs when starting a new runtime.

Original issue created by Salageanu Emil on 08, Aug 2008 at 15:31 PM – AGENT-17

---

The problem is that we need to obtain, in the GUI program, the information about the PA Runtime (the service has this information)
As we cannot call a method (with no void return) on the service we need to :
1. implement RM com between GUI and service
OR
2. use a .lock file on disk

OR

1. use a windows registry

For the solution 3: LET the registry be called PARTRunning with values 0 (not running) or 1 (running) when the service starts, it sets the value of the registry to 0 (not running) then, it will update the the value each tilme it starts/stops the RT The GUi will read once in a while the registry in order to update its state.

Original issue created by Salageanu Emil on 12, Feb 2009 at 11:47 AM – AGENT-21

---

In mode allaways when an error occurs, the system does not restart beacuse the limit barrier is set (why? this is the bug) at 01/01/0001
See the agent logs and the agent configuration bellow.

-———————————— the agent logs -—————————————-

2009-02-11 17:13:23,992 DEBUG ProActiveAgent.WindowsService – ProActive Agent application loaded successfully.
2009-02-11 17:13:24,044 DEBUG ProActiveAgent.WindowsService – Starting ProActive Agent service.
2009-02-11 17:13:24,278 DEBUG ProActiveAgent.WindowsService – Starting action RMAction
2009-02-11 17:13:24,386 INFO ProActiveAgent.ProActiveExec – The initial java heap size is Xms64M and maximum java heap size is -Xmx64M
2009-02-11 17:13:24,389 DEBUG ProActiveAgent.TimerManager – Loading events in the Time Manager.
2009-02-11 17:13:24,391 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 11/02/2009 17:15:00 → 11/02/2009 19:26:00
2009-02-11 17:13:24,392 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 09/02/2009 00:00:00 → 15/02/2009 23:59:59
2009-02-11 17:13:24,394 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:13:24,399 DEBUG ProActiveAgent.ProActiveExec – Preparing to start new ProActive Runtime process with cmd : org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter args : System.String(link: )
2009-02-11 17:13:24,411 INFO ProActiveAgent.ProActiveExec – Started ProActive Runtime process (link: pid:3808)
Command-line: C:\Program Files\Java\jdk1.6.0_10\bin\java.exe -Dproactive.home=“C:\emil\Scheduling” -Dproactive.configuration=“C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml” -Djava.security.manager -Dpa.scheduler.home=“C:\emil\Scheduling” -Dpa.rm.home=“C:\emil\Scheduling” -Djava.security.policy=“C:\emil\Scheduling\config\scheduler.java.policy” -Dlog4j.configuration=“file:///C:\emil\Scheduling\config\scheduler-log4j” -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter rmi://192.168.1.10:1605 emil
2009-02-11 17:13:24,413 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 100%
2009-02-11 17:13:24,415 INFO ProActiveAgent.ProActiveExec – Adding new process java (link: pid:3808) to the cpu limiter.
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: TOTO
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.linux
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.windows
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.linux
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.windows
2009-02-11 17:13:24,987 INFO ProActiveRuntimeProcessLogger – All supported ProActive Java properties are declared inside org.objectweb.proactive.core.config.PAProperties. Please check your ProActive Configuration file: C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml
2009-02-11 17:13:25,383 INFO ProActiveRuntimeProcessLogger – —> This ClassFileServer is listening on port 2026
2009-02-11 17:13:26,420 INFO ProActiveRuntimeProcessLogger – Created a new registry on port 1605
2009-02-11 17:13:27,134 INFO ProActiveRuntimeProcessLogger – Connected to the Resource Manager at rmi://192.168.1.10:1605/RMADMIN
2009-02-11 17:14:00,689 INFO ProActiveRuntimeProcessLogger – Using “C:\Users\esalagea\AppData\Local\Temp\vfs_cache” as temporary files store.
2009-02-11 17:14:04,926 INFO ProActiveAgent.ProActiveExec – A new process cmd (link: pid:3268) has been detected.
2009-02-11 17:14:04,927 INFO ProActiveAgent.ProActiveExec – Adding new process cmd (link: pid:3268) to the cpu limiter.
2009-02-11 17:14:04,999 INFO ProActiveAgent.ProActiveExec – A new process mapreads (link: pid:816) has been detected.
2009-02-11 17:14:05,000 INFO ProActiveAgent.ProActiveExec – Adding new process mapreads (link: pid:816) to the cpu limiter.
2009-02-11 17:14:59,994 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:14:59,995 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 20%
2009-02-11 17:15:40,173 DEBUG ProActiveAgent.WindowsService – Stopping ProActive Agent service.
2009-02-11 17:15:40,176 DEBUG ProActiveAgent.ProActiveExec – Stopping the ProActive Runtime process.
2009-02-11 17:16:15,233 DEBUG ProActiveAgent.WindowsService – ProActive Agent application loaded successfully.
2009-02-11 17:16:15,287 DEBUG ProActiveAgent.WindowsService – Starting ProActive Agent service.
2009-02-11 17:16:15,523 DEBUG ProActiveAgent.WindowsService – Starting action RMAction
2009-02-11 17:16:15,631 INFO ProActiveAgent.ProActiveExec – The initial java heap size is -Xms64M and maximum java heap size is -Xmx64M
2009-02-11 17:16:15,634 DEBUG ProActiveAgent.TimerManager – Loading events in the Time Manager.
2009-02-11 17:16:15,636 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 11/02/2009 17:17:00 → 11/02/2009 19:28:00
2009-02-11 17:16:15,637 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 09/02/2009 00:00:00 → 15/02/2009 23:59:59
2009-02-11 17:16:15,639 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:16:15,643 DEBUG ProActiveAgent.ProActiveExec – Preparing to start new ProActive Runtime process with cmd : org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter args : System.String(link: )
2009-02-11 17:16:15,655 INFO ProActiveAgent.ProActiveExec – Started ProActive Runtime process (link: pid:3480)
Command-line: C:\Program Files\Java\jdk1.6.0_10\bin\java.exe -Dproactive.home=“C:\emil\Scheduling” -Dproactive.configuration=“C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml” -Djava.security.manager -Dpa.scheduler.home=“C:\emil\Scheduling” -Dpa.rm.home=“C:\emil\Scheduling” -Djava.security.policy=“C:\emil\Scheduling\config\scheduler.java.policy” -Dlog4j.configuration=“file:///C:\emil\Scheduling\config\scheduler-log4j” -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter rmi://192.168.1.10:1605 emil
2009-02-11 17:16:15,660 INFO ProActiveAgent.ProActiveExec – Adding new process java (link: pid:3480) to the cpu limiter.
2009-02-11 17:16:15,661 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 100%
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: TOTO
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.linux
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.windows
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.linux
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.windows
2009-02-11 17:16:16,253 INFO ProActiveRuntimeProcessLogger – All supported ProActive Java properties are declared inside org.objectweb.proactive.core.config.PAProperties. Please check your ProActive Configuration file: C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml
2009-02-11 17:16:16,638 INFO ProActiveRuntimeProcessLogger – —> This ClassFileServer is listening on port 2026
2009-02-11 17:16:17,669 INFO ProActiveRuntimeProcessLogger – Created a new registry on port 1605
2009-02-11 17:16:18,354 INFO ProActiveRuntimeProcessLogger – Connected to the Resource Manager at rmi://192.168.1.10:1605/RMADMIN
2009-02-11 17:16:22,058 INFO ProActiveRuntimeProcessLogger – Using “C:\Users\esalagea\AppData\Local\Temp\vfs_cache” as temporary files store.
2009-02-11 17:16:25,830 INFO ProActiveAgent.ProActiveExec – A new process cmd (link: pid:4140) has been detected.
2009-02-11 17:16:25,831 INFO ProActiveAgent.ProActiveExec – Adding new process cmd (link: pid:4140) to the cpu limiter.
2009-02-11 17:16:25,946 INFO ProActiveAgent.ProActiveExec – A new process mapreads (link: pid:4460) has been detected.
2009-02-11 17:16:25,947 INFO ProActiveAgent.ProActiveExec – Adding new process mapreads (link: pid:4460) to the cpu limiter.
2009-02-11 17:16:59,996 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:16:59,997 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 20%
2009-02-11 17:18:15,458 DEBUG ProActiveAgent.WindowsService – Stopping ProActive Agent service.
2009-02-11 17:18:15,462 DEBUG ProActiveAgent.ProActiveExec – Stopping the ProActive Runtime process.
2009-02-11 17:19:07,912 DEBUG ProActiveAgent.WindowsService – ProActive Agent application loaded successfully.
2009-02-11 17:19:07,965 DEBUG ProActiveAgent.WindowsService – Starting ProActive Agent service.
2009-02-11 17:19:08,206 DEBUG ProActiveAgent.WindowsService – Starting action RMAction
2009-02-11 17:19:08,314 INFO ProActiveAgent.ProActiveExec – The initial java heap size is -Xms64M and maximum java heap size is -Xmx64M
2009-02-11 17:19:08,317 DEBUG ProActiveAgent.TimerManager – Loading events in the Time Manager.
2009-02-11 17:19:08,319 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 11/02/2009 16:17:00 → 11/02/2009 19:28:00
2009-02-11 17:19:08,321 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:19:08,326 DEBUG ProActiveAgent.ProActiveExec – Preparing to start new ProActive Runtime process with cmd : org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter args : System.String(link: )
2009-02-11 17:19:08,337 INFO ProActiveAgent.ProActiveExec – Started ProActive Runtime process (link: pid:5420)
Command-line: C:\Program Files\Java\jdk1.6.0_10\bin\java.exe -Dproactive.home=“C:\emil\Scheduling” -Dproactive.configuration=“C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml” -Djava.security.manager -Dpa.scheduler.home=“C:\emil\Scheduling” -Dpa.rm.home=“C:\emil\Scheduling” -Djava.security.policy=“C:\emil\Scheduling\config\scheduler.java.policy” -Dlog4j.configuration=“file:///C:\emil\Scheduling\config\scheduler-log4j” -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter rmi://192.168.1.10:1605 emil
2009-02-11 17:19:08,342 INFO ProActiveAgent.ProActiveExec – Adding new process java (link: pid:5420) to the cpu limiter.
2009-02-11 17:19:08,343 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 20%
2009-02-11 17:19:08,375 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 09/02/2009 00:00:00 → 15/02/2009 23:59:59
2009-02-11 17:19:08,378 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:19:08,379 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 100%
2009-02-11 17:19:08,900 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: TOTO
2009-02-11 17:19:08,900 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.linux
2009-02-11 17:19:08,900 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.windows
2009-02-11 17:19:08,900 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.linux
2009-02-11 17:19:08,900 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.windows
2009-02-11 17:19:08,901 INFO ProActiveRuntimeProcessLogger – All supported ProActive Java properties are declared inside org.objectweb.proactive.core.config.PAProperties. Please check your ProActive Configuration file: C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml
2009-02-11 17:19:09,298 INFO ProActiveRuntimeProcessLogger – —> This ClassFileServer is listening on port 2026
2009-02-11 17:19:10,334 INFO ProActiveRuntimeProcessLogger – Created a new registry on port 1605
2009-02-11 17:19:11,012 INFO ProActiveRuntimeProcessLogger – Connected to the Resource Manager at rmi://192.168.1.10:1605/RMADMIN
2009-02-11 17:19:12,925 INFO ProActiveRuntimeProcessLogger – Using “C:\Users\esalagea\AppData\Local\Temp\vfs_cache” as temporary files store.
2009-02-11 17:19:16,731 INFO ProActiveAgent.ProActiveExec – A new process cmd (link: pid:5120) has been detected.
2009-02-11 17:19:16,733 INFO ProActiveAgent.ProActiveExec – Adding new process cmd (link: pid:5120) to the cpu limiter.
2009-02-11 17:19:16,834 INFO ProActiveAgent.ProActiveExec – A new process mapreads (link: pid:5196) has been detected.
2009-02-11 17:19:16,835 INFO ProActiveAgent.ProActiveExec – Adding new process mapreads (link: pid:5196) to the cpu limiter.
2009-02-11 17:23:20,312 DEBUG ProActiveAgent.WindowsService – Stopping ProActive Agent service.
2009-02-11 17:23:20,314 DEBUG ProActiveAgent.ProActiveExec – Stopping the ProActive Runtime process.
2009-02-11 17:23:21,362 DEBUG ProActiveAgent.WindowsService – ProActive Agent application loaded successfully.
2009-02-11 17:23:21,414 DEBUG ProActiveAgent.WindowsService – Starting ProActive Agent service.
2009-02-11 17:23:21,647 DEBUG ProActiveAgent.WindowsService – Starting action RMAction
2009-02-11 17:23:21,755 INFO ProActiveAgent.ProActiveExec – The initial java heap size is -Xms64M and maximum java heap size is -Xmx64M
2009-02-11 17:23:21,758 DEBUG ProActiveAgent.TimerManager – Loading events in the Time Manager.
2009-02-11 17:23:21,760 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 11/02/2009 16:17:00 → 11/02/2009 19:28:00
2009-02-11 17:23:21,762 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:23:21,767 DEBUG ProActiveAgent.ProActiveExec – Preparing to start new ProActive Runtime process with cmd : org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter args : System.String(link: )
2009-02-11 17:23:21,779 INFO ProActiveAgent.ProActiveExec – Started ProActive Runtime process (link: pid:4876)
Command-line: C:\Program Files\Java\jdk1.6.0_10\bin\java.exe -Dproactive.home=“C:\emil\Scheduling” -Dproactive.configuration=“C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml” -Djava.security.manager -Dpa.scheduler.home=“C:\emil\Scheduling” -Dpa.rm.home=“C:\emil\Scheduling” -Djava.security.policy=“C:\emil\Scheduling\config\scheduler.java.policy” -Dlog4j.configuration=“file:///C:\emil\Scheduling\config\scheduler-log4j” -Xms64M -Xmx64M org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter rmi://192.168.1.10:1605 emil
2009-02-11 17:23:21,791 INFO ProActiveAgent.ProActiveExec – Adding new process java (link: pid:4876) to the cpu limiter.
2009-02-11 17:23:21,792 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 20%
2009-02-11 17:23:21,834 DEBUG ProActiveAgent.TimerManager – Loading CalendardEvent 09/02/2009 00:00:00 → 15/02/2009 23:59:59
2009-02-11 17:23:21,837 DEBUG ProActiveAgent.ProActiveExec – Received start action request from AgentScheduler
2009-02-11 17:23:21,839 DEBUG ProActiveAgent.ProActiveExec – Setting process priority to Normal and max cpu usage to 100%
2009-02-11 17:23:22,378 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: TOTO
2009-02-11 17:23:22,379 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.linux
2009-02-11 17:23:22,379 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.matlab.script.windows
2009-02-11 17:23:22,379 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.linux
2009-02-11 17:23:22,379 INFO ProActiveRuntimeProcessLogger – Skiped unknown ProActive Java property: proactive.scheduler.ext.scilab.script.windows
2009-02-11 17:23:22,379 INFO ProActiveRuntimeProcessLogger – All supported ProActive Java properties are declared inside org.objectweb.proactive.core.config.PAProperties. Please check your ProActive Configuration file: C:\emil\Scheduling\config\proactive\ProActiveConfiguration.xml
2009-02-11 17:23:22,766 INFO ProActiveRuntimeProcessLogger – —> This ClassFileServer is listening on port 2026
2009-02-11 17:23:23,799 INFO ProActiveRuntimeProcessLogger – Created a new registry on port 1605
2009-02-11 17:23:24,517 INFO ProActiveRuntimeProcessLogger – Connected to the Resource Manager at rmi://192.168.1.10:1605/RMADMIN
2009-02-11 17:23:26,192 INFO ProActiveRuntimeProcessLogger – Using “C:\Users\esalagea\AppData\Local\Temp\vfs_cache” as temporary files store.
2009-02-11 17:23:30,046 INFO ProActiveAgent.ProActiveExec – A new process cmd (link: pid:6036) has been detected.
2009-02-11 17:23:30,047 INFO ProActiveAgent.ProActiveExec – Adding new process cmd (link: pid:6036) to the cpu limiter.
2009-02-11 17:23:30,155 INFO ProActiveAgent.ProActiveExec – A new process mapreads (link: pid:4260) has been detected.
2009-02-11 17:23:30,156 INFO ProActiveAgent.ProActiveExec – Adding new process mapreads (link: pid:4260) to the cpu limiter.
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – org.objectweb.proactive.core.body.exceptions.InactiveBodyException: Cannot perform this call because body 62b48dd9-11f66265674-7fd0—f099e3b3a6087726-62b48dd9-11f66265674—8000is inactive
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – org.objectweb.proactive.core.body.exceptions.InactiveBodyException: Cannot perform this call because body 62b48dd9-11f66265674—7fd0—f099e3b3a6087726-62b48dd9-11f66265674—8000is inactive
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.BodyImpl$InactiveLocalBodyStrategy.getReifiedObject(BodyImpl.java:751)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.AbstractBody.getReifiedObject(AbstractBody.java:889)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.api.PAActiveObject.getStubForBody(PAActiveObject.java:1348)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.api.PAActiveObject.getStubOnThis(PAActiveObject.java:1174)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.api.PAActiveObject.terminateActiveObject(PAActiveObject.java:983)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.ow2.proactive.scheduler.task.TaskLauncher.terminate(TaskLauncher.java:354)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at java.lang.reflect.Method.invoke(Method.java:597)
2009-02-11 17:23:33,729 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.mop.MethodCall.execute(MethodCall.java:394)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.request.RequestImpl.serveInternal(RequestImpl.java:230)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.request.RequestImpl.serve(RequestImpl.java:174)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serveInternal(BodyImpl.java:549)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serve(BodyImpl.java:520)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.AbstractBody.serve(AbstractBody.java:914)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.request.RequestReceiverImpl.receiveRequest(RequestReceiverImpl.java:101)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.BodyImpl.internalReceiveRequest(BodyImpl.java:281)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.body.AbstractBody.receiveRequest(AbstractBody.java:343)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.lang.reflect.Method.invoke(Method.java:597)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.mop.MethodCall.execute(MethodCall.java:394)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.remoteobject.RemoteObjectImpl.receiveMessage(RemoteObjectImpl.java:110)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.remoteobject.InternalRemoteRemoteObjectImpl.receiveMessage(InternalRemoteRemoteObjectImpl.java:150)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at org.objectweb.proactive.core.remoteobject.rmi.RmiRemoteObjectImpl.receiveMessage(RmiRemoteObjectImpl.java:79)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.lang.reflect.Method.invoke(Method.java:597)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.transport.Transport$1.run(Transport.java:159)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.security.AccessController.doPrivileged(Native Method)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
2009-02-11 17:23:33,730 INFO ProActiveRuntimeProcessLogger – at java.lang.Thread.run(Thread.java:619)
2009-02-12 10:18:46,565 DEBUG ProActiveAgent.ProActiveExec – Received stop action request from AgentScheduler
2009-02-12 10:18:46,711 INFO ProActiveRuntimeProcessLogger – unable to contact remote object at rmi://abulafia.activeeon.com:1605/RMADMIN when calling receiveFTMessage
2009-02-12 10:18:46,727 DEBUG ProActiveAgent.ProActiveExec – callersState — AgentScheduler
2009-02-12 10:19:17,160 INFO ProActiveAgent.ProActiveExec – The ProActive Runtime process has exited for unknown reason.
2009-02-12 10:35:07,591 DEBUG ProActiveAgent.ProActiveExec – Preparing to restart the ProActive Runtime process.
2009-02-12 10:35:07,592 DEBUG ProActiveAgent.ProActiveExec – Restarting the ProActive Runtime process in 3000 ms.
2009-02-12 10:35:07,594 DEBUG ProActiveAgent.TimerManager – Trying to schedule restart at 12/02/2009 10:35:10 Limit time barrier is 01/01/0001 00:00:00 (we cannot restart after this time point).
2009-02-12 10:35:07,595 DEBUG ProActiveAgent.TimerManager – Discarding restarting of 12/02/2009 10:35:10 because it would happen outside the job allocated time.
2009-02-12 11:37:47,570 DEBUG ProActiveAgent.WindowsService – Stopping ProActive Agent service.

---

agent configuration xml file -———————————————

<?xml version=“1.0” encoding=“utf-8”?>


C:\emil\Scheduling
C:\Program Files\Java\jdk1.6.0_10

false
0
0

wednesday 16 17 0 0 3 11 0 Normal 20 monday 0 0 0 6 23 59 59 Normal 100 0 org.objectweb.proactive.core.util.winagent.PAAgentServiceRMIStarter false 0 org.ow2.proactive.resourcemanager.utils.PAAgentServiceRMStarter true rmi://192.168.1.10:1605 emil 0 user.Starter false

Original issue created by Christian Delbé on 23, Oct 2009 at 18:21 PM - AGENT-50

---

No description

Original issue created by Salageanu Emil on 24, Jul 2008 at 16:32 PM – AGENT-14

---

just create an event on the day “Toto”

Original issue created by Cédric Dalmasso on 21, Jul 2009 at 13:19 PM - AGENT-27

---

It would be nice to have by default the Always available checkbox in the Planning tab of the configuration editor checked by default.

Original issue created by Cédric Dalmasso on 27, Jul 2009 at 11:53 AM - AGENT-31

---

If I checked "Automatic Launch" in the ProActive agent tray icon menu. I have an error when I log on as a standard user on my laptop. See attached screenshot.

AgentForAgent has stopped working
with
Window is looking for a solution and then
and then
Windows is collecting more information about the problem.
This might take several minutes ...

Original issue created by Cédric Dalmasso on 04, Aug 2009 at 16:57 PM - AGENT-39

---

The user account used to start the ProActive agent service should have administrator right and require Log on as a service right assignment.
If not, I got a not helping at all message (see image in attachment).

Two actions should be take:

• inform user at installation time of this strong requirement and even better check if the provided account is fine
• print a better message in case of error instead an exception, this message is useful both if the log on as a service is not set and if the given password is wrong

Original issue created by Christian Delbé on 24, Jul 2009 at 17:59 PM - AGENT-29

---

The user can specifcy the protocol used (rmi/ http / rmissh (credential ??) / pamr (??) ) and the ports that should be used.
In a more general way, the user must be able to specifiy in a dedicated GUI (i.e. not through -Dproperty...) everything that is not common to all the runtimes started on the same machine.

Original issue created by Vladimir Bodnartchouk on 27, Jul 2009 at 16:36 PM - AGENT-34

---

The current behavior can lead to a lot of down nodes in the RM.

Original issue created by Salageanu Emil on 17, Jul 2008 at 15:23 PM – AGENT-2

---

No description

Original issue created by Christian Delbé on 11, Jun 2009 at 15:01 PM - AGENT-22

---

When JAVA_HOME is not set, the runtime's CLASSPATH is set to "JAVA_HOME is not set. Please..."