| [ptp-user] Re: PTPLauncherFailswithJava.lang.reflect.InvocationTargetException |
|
Hi, I did not get any response to this. Perhaps
it was owing to the included screen dump’s causing it to exceed some size
restriction. Consequently, I am resending it without the image.
Thanks,
-Ken From:
ptp-user-bounces@xxxxxxxxxxx [mailto:ptp-user-bounces@xxxxxxxxxxx] On Behalf Of Kenneth Evans Hi, I am back at work where the response is much better. 1. I tried to run my launcher (which previously seemed to be working,
see below) again. It went back to the
java.lang.reflect.InvocationTargetException error. 2. I couldn't get around this, and deleted .metadata again, imported
the project, etc. 3. When I tried to remake the launcher, there were no machines in the
pull-down and it failed to save the launcher when I hit Close. The reason
was: null. (I think this also happened last week but I didn’t take
good notes then.) 4. I tried again, and there was Machine0 in the pull-down menu this
time. And it seemed to work from then on. Things in the PTP Runtime
perspective seem to work as expected (although the job I am using is too short
to test some of them). (I did find the stdout for each process in the
Jobs view.) 5. However, I can’t debug. (I made a Managed Make project
following the directions in the help and the following output is from
that. It also hung on my original, Standard Make, project the same
way.) I get the following dialog, which never goes away. <Screen dump that says
“Starting the debugger…”, “Connecting to proxy server…”,
with a progress bar about 2/3 full.> The terminal window where Eclipse was launched says: bind(0.0.0.0/0.0.0.0:0) port=32957 XXXXXXXXXXXX Waiting for Universe to Populate accept thread starting... MODEL MANAGER: newJob(17) ModelManager.run() - new JobID = 17 JAVA OMPI: run() with args: name:
Project1 path:
/clhome/EVANS/src/Eclipse/Work/Project1/Debug cwd:
/clhome/EVANS/src/Eclipse/Work/Project1 machineName: Machine0 #procs: 8 #proc/node: 1 firstNode#: 0 isDebug?
true <00000320 RUN 6:6a6f62494400 3:313700 9:657865634e616d6500
9:50726f6a6563743100 b:70617468546f4578656300
2e:2f636c686f6d652f4556414e532f7372632f45636c697073652f576f726b2f50726f6a656374312f446562756700
b:6e756d4f6650726f637300 2:3800 d:70726f63735065724e6f646500 2:3100
d:66697273744e6f64654e756d00 2:3000 b:776f726b696e6744697200
28:2f636c686f6d652f4556414e532f7372632f45636c697073652f576f726b2f50726f6a6563743100
d:64656275676765725061746800
58:2f636c686f6d652f4556414e532f65636c69707365506c7567696e732f65636c697073652f706c7567696e732f6f72672e65636c697073652e7074702e6c696e75782e7838365f36345f312e312e302f62696e2f73646d00
c:646562756767657241726700 11:2d2d686f73743d6c6f63616c686f737400
c:646562756767657241726700 12:2d2d64656275676765723d6764622d6d6900 c:646562756767657241726700
d:2d2d706f72743d333239353700> ++++++++++ ptp_orte_proxy: (debug ? 1) Spawning 8 processes of job
'/clhome/EVANS/src/Eclipse/Work/Project1/Debug/Project1' ++++++++++ ptp_orte_proxy: program name
'/clhome/EVANS/src/Eclipse/Work/Project1/Debug/Project1' ++++++++++ ptp_orte_proxy: SPAWNED [error code 0 = 'Success'], now
unlocking ++++++++++ ptp_orte_proxy: NEW JOBID = 22 ++++++++++ ptp_orte_proxy: registering IO forwarding - name = '' ++++++++++ ptp_orte_proxy: Returning from ORTERun OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=17)
state=1 *********** OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [0]:<ATTRIB_PROCESS_NODE_NAME=puppy1> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process0]=puppy1(0) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [4]:<ATTRIB_PROCESS_NODE_NAME=puppy1> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process4]=puppy1(0) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [1]:<ATTRIB_PROCESS_NODE_NAME=puppy2> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process1]=puppy2(1) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [5]:<ATTRIB_PROCESS_NODE_NAME=puppy2> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process5]=puppy2(1) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [2]:<ATTRIB_PROCESS_NODE_NAME=puppy3> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process2]=puppy3(2) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [6]:<ATTRIB_PROCESS_NODE_NAME=puppy3> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process6]=puppy3(2) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [3]:<ATTRIB_PROCESS_NODE_NAME=puppy4> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process3]=puppy4(3) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=17
{0}:<> [7]:<ATTRIB_PROCESS_NODE_NAME=puppy4> *********** PROC ATTRIBUTE CHANGE: (job = job17) setting node[job17_process7]=puppy4(3) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=17)
state=2 *********** OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=17)
state=3 *********** accept failed... :( accept thread exiting... XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true [I did not try the CVS patch for the Console (per Feiyi). I am
not yet set up to build the plug-ins myself. I am still using the version
from the update manager.) Thanks for any help. -Ken -----Original Message----- Beth, >> I think if I were you, I'd start over: Install a fresh eclipse
and put CDT and PTP on top of that. It's not likely the Eclipse. It's only about a week old, and I
keep the workspace and plug-ins like CDT and PTP apart from the Eclipse directory.
I completely cleaned out the plug-ins directory and have reinstalled both
CDT and PTP already, as described below. (It's also unlikely there
was anything wrong with them. I think I installed them correctly the first
time.) I also did a -clean on the workspace. What I didn't do is _completely_ clean the workspace by deleting
.metadata. That's where the configuration, which is likely where it is hosed,
would be stored. So I did that and started over. It does seem to be
working, now. At least it looks like it ran. I expected the output in the
console but it seems to be in the stdout where Eclipse was launched (see below).
Is that what it does? There is now only one machine, Machine0, in the pull-down menu. I
am still confused as to what this is. I did this at home. It is very painful to run Eclipse with a VPN,
SSH, and who knows what else in between, so I'll probably wait until I get back
to work. (I measure a one-way latency of about 150 ms which doesn't
mix well with X11's heavy use of round-trip protocols.) The SSH console
and even Emacs, which is also X11, are much faster. Thanks for the help and have a good holidays. -Ken ----------------------------------------------------------------------- 43 blacklab.aps.anl.gov:EVANS>[1] 9232 [2]
Done
eclipse 43 blacklab.aps.anl.gov:EVANS>In getResourceManagerFactories retrieved factory: Simulation, org.eclipse.ptp.simulation.core.resourcemanager leaving getResourceManagerFactories Your Control System Choice: '<UNDEFINED CS>' Your Monitoring System Choice: '<UNDEFINED MS>' No previous (or invalid) control or monitoring system selected. Default systems set to Open Runtime Environment (ORTE). To
change, use the Window->Preferences->PTP preferences page. Your Default Control System Choice: 'Open Runtime Environment (ORTE)' Your Default Monitoring System Choice: 'Open Runtime Environment
(ORTE)' In retrieveConfigurationWizardPageFactories wizard page factory: org.eclipse.ptp.simulation.ui.wizards.SimulationRMConfigurationWizardPageFac tory@618787c9 for class: class org.eclipse.ptp.rmsystem.SimulationResourceManagerFactory leaving retrieveConfigurationWizardPageFactories XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():false XXXXXXXXXXX refreshRuntimeSystems calling initialize(), force:false, isInitialized():false refreshRuntimeSystems SHUTTING DOWN CONTROL/MONITORING/PROXY systems where appropriate OMPIProxyRuntimeClient - firing up proxy, waiting for connecting.
Please wait! This can take a minute . . . ORTE_SERVER path = '' OS = 'linux', Architecture = 'x86_64', OS_ARCH combo = 'org.eclipse.ptp.linux.x86_64' PTP Version = 1.1.0 All Found Fragments: update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.x86_1.1.0/ [118] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.ppc_1.1.0/ [126] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_1.1.0/ [138] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1.1.0/ [145] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.ppc_1.1.0/ [151] Testing fragment 1 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.x86_1.1 .0/' Testing fragment 2 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.ppc_1.1. 0/' Testing fragment 3 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_1.1. 0/' Testing fragment 4 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1 .1.0/' Correct fragment for our OS
& arch Searching for file in '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1 .1.0/bin/ptp_orte_proxy'
**** FOUND IT! sessionCreate(0,0) bind(0.0.0.0/0.0.0.0:0) port=33676 accept thread starting... Waiting on accept. OMPIProxyRuntimeClient waiting on {201, 210} RUNNING PROXY SERVER COMMAND: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1 .1.0/bin/ptp_orte_proxy --port=33676' OMPIProxyRuntimeClient got event: EVENT_RUNTIME_CONNECTED OMPIProxyRuntimeClient notifying... OMPIProxyRuntimeClient awoke! <0000000b STARTDAEMON> accept thread exiting... event thread starting... OMPIProxyRuntimeClient waiting on {200, 201, 211} ++++++++++ ptp_orte_proxy: proxy_svr_connect returned. ++++++++++ ptp_orte_proxy: StartDaemon(orted orted --scope public
--seed --persistent --no-daemonize --universe PTP-ORTE-9383 --report-uri 5) ++++++++++ ptp_orte_proxy: CHILD: Starting execvp now! ++++++++++ ptp_orte_proxy: proxy_svr_connect returned. ++++++++++ ptp_orte_proxy: PARENT: orted_pid = 9383 ++++++++++ ptp_orte_proxy: PARENT: URI = 0.0.0;tcp://164.54.52.168:33678;tcp://172.16.1.254:33678;tcp://172.17.1.254: 33678 ++++++++++ ptp_orte_proxy: ORTEInit (PTP-ORTE-9383) OMPIProxyRuntimeClient got event: EVENT_RUNTIME_OK OMPIProxyRuntimeClient notifying... OMPIProxyRuntimeClient awoke! OMPIMonitoringSystem startup() OMPIMonitoringSystem: initiateDiscovery phase <00000008 DISCOVER> OS = 'linux', Architecture = 'x86_64', OS_ARCH combo = 'org.eclipse.ptp.linux.x86_64' PTP Version = 1.1.0 All Found Fragments: update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.x86_1.1.0/ [118] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.ppc_1.1.0/ [126] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_1.1.0/ [138] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1.1.0/ [145] update@../eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.ppc_1.1.0/ [151] Testing fragment 1 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.macosx.x86_1.1 .0/' Testing fragment 2 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.ppc_1.1. 0/' Testing fragment 3 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_1.1. 0/' Testing fragment 4 with this OS/arch - path: '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1 .1.0/' Correct fragment for our OS
& arch Searching for file in '/clhome/EVANS/eclipsePlugins/eclipse/plugins/org.eclipse.ptp.linux.x86_64_1 .1.0/bin/sdm'
**** FOUND IT! ++++++++++ ptp_orte_proxy: Start daemon returning OK. ++++++++++ ptp_orte_proxy: DISCOVERY PHASE: end OMPIProxyRuntimeClient got event: EVENT_RUNTIME_NODEATTR [Ljava.lang.String;@7f21c5df : [Ljava.lang.String;@245f4ae ModelManager.runtimeNodeGeneralName - #keys = 28, #values = 28
Unknown machine ID (0), adding to the model.
Unknown node number (0), adding to the model.
Unknown node number (1), adding to the model.
Unknown node number (2), adding to the model.
Unknown node number (3), adding to the model. XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true XXXXXXXXXXXX Waiting for Universe to Populate MODEL MANAGER: newJob(1) ModelManager.run() - new JobID = 1 JAVA OMPI: run() with args: name:
helloWorld path:
/clhome/EVANS/src/Eclipse/Work/OpenMPITest cwd:
/clhome/EVANS/src/Eclipse/Work/OpenMPITest machineName: Machine0 #procs: 5 #proc/node: 1 firstNode#: 0 isDebug?
false <00000195 RUN 6:6a6f62494400 2:3100 9:657865634e616d6500 b:68656c6c6f576f726c6400 b:70617468546f4578656300 2b:2f636c686f6d652f4556414e532f7372632f45636c697073652f576f726b2f4f70656e4d5 0495465737400 b:6e756d4f6650726f637300 2:3500
d:70726f63735065724e6f646500 2:3100 d:66697273744e6f64654e756d00 2:3000 b:776f726b696e6744697200 2b:2f636c686f6d652f4556414e532f7372632f45636c697073652f576f726b2f4f70656e4d5 0495465737400> ++++++++++ ptp_orte_proxy: (debug ? 0) Spawning 5 processes of job '/clhome/EVANS/src/Eclipse/Work/OpenMPITest/helloWorld' ++++++++++ ptp_orte_proxy: program name '/clhome/EVANS/src/Eclipse/Work/OpenMPITest/helloWorld' ++++++++++ ptp_orte_proxy: SPAWNED [error code 0 = 'Success'], now
unlocking OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=1)
state=1 *********** ++++++++++ ptp_orte_proxy: NEW JOBID = 2 ++++++++++ ptp_orte_proxy: registering IO forwarding - name = '' ++++++++++ ptp_orte_proxy: Returning from ORTERun ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 2 ++++++++++ ptp_orte_proxy: state callback returning state=2 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
{0}:<> [0]:<ATTRIB_PROCESS_NODE_NAME=puppy1>
[0]:<ATTRIB_PROCESS_PID=6003> *********** PROC ATTRIBUTE CHANGE: (job = job1) setting node[job1_process0]=puppy1(0) setting pid[job1_process0]=6003 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
{0}:<> [4]:<ATTRIB_PROCESS_NODE_NAME=puppy1>
[4]:<ATTRIB_PROCESS_PID=6004> *********** PROC ATTRIBUTE CHANGE: (job = job1) setting node[job1_process4]=puppy1(0) setting pid[job1_process4]=6004 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
{0}:<> [1]:<ATTRIB_PROCESS_NODE_NAME=puppy2>
[1]:<ATTRIB_PROCESS_PID=5540> *********** PROC ATTRIBUTE CHANGE: (job = job1) setting node[job1_process1]=puppy2(1) setting pid[job1_process1]=5540 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
{0}:<> [2]:<ATTRIB_PROCESS_NODE_NAME=puppy3>
[2]:<ATTRIB_PROCESS_PID=5490> *********** PROC ATTRIBUTE CHANGE: (job = job1) setting node[job1_process2]=puppy3(2) setting pid[job1_process2]=5490 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
{0}:<> [3]:<ATTRIB_PROCESS_NODE_NAME=puppy4>
[3]:<ATTRIB_PROCESS_PID=8177> *********** PROC ATTRIBUTE CHANGE: (job = job1) setting node[job1_process3]=puppy4(3) setting pid[job1_process3]=8177 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=1)
state=2 *********** ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 4 ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 8 ++++++++++ ptp_orte_proxy: state callback returning state=2 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=1)
state=2 *********** ++++++++++ ptp_orte_proxy: Hello World from process 1 of 5 on
puppy2.cluster OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCOUT 1 1 'Hello
World from process 1 of 5 on puppy2.cluster' ++++++++++ ptp_orte_proxy: Hello World from process 2 of 5 on
puppy3.cluster ++++++++++ ptp_orte_proxy: Hello World from process 3 of 5 on
puppy4.cluster ++++++++++ ptp_orte_proxy: Hello World from process 0 of 5 on
puppy1.cluster ++++++++++ ptp_orte_proxy: Hello World from process 4 of 5 on
puppy1.cluster ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 32 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCOUT 1 2 'Hello
World from process 2 of 5 on puppy3.cluster' ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 64 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCOUT 1 3 'Hello
World from process 3 of 5 on puppy4.cluster' OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCOUT 1 0 'Hello
World from process 0 of 5 on puppy1.cluster' OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCOUT 1 4 'Hello
World from process 4 of 5 on puppy1.cluster' ++++++++++ ptp_orte_proxy: JOB STATE CALLBACK: 128 ++++++++++ ptp_orte_proxy: unregistering IO forwarding - name = ++++++++++ ptp_orte_proxy: state callback returning state=3 OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=1)
state=3 *********** ----------------------------------------------------------------------- -Ken -----Original Message----- From: ptp-user-bounces@xxxxxxxxxxx
[mailto:ptp-user-bounces@xxxxxxxxxxx] On Behalf Of Beth Tibbitts Sent: Friday, December 21, 2007 7:54 PM To: Subject: RE: [ptp-user]PTPLauncherFailswithJava.lang.reflect.InvocationTargetException I think if I were you, I'd start over: Install a fresh eclipse and put
CDT and PTP on top of that. ...Beth Beth Tibbitts (859) 243-4981 (TL 545-4981) High Productivity Tools / Parallel Tools http://eclipse.org/ptp Mailing Address: IBM Corp., 745 West New Circle Road,
"Kenneth
Evans"
<evans@xxxxxxxxxx
v>
To
Sent by:
"'
ptp-user-bounces@
<ptp-user@xxxxxxxxxxx>
eclipse.org
cc
Subject
12/21/2007 05:49
RE:
PM
[ptp-user]PTPLauncherFailswithJava.
lang.reflect.InvocationTargetExcept
ion
Please respond
to
<ptp-user@eclipse
.org>
>> I will uninstall 1.1.0 and install 1.1.1. That wasn't very easy. When I disabled PTP in the Update manager,
it disappeared and could not be uninstalled. I then manually deleted
all the PTP plug-ins and features. Then I could not open the C / C++
Perspective. It was linked to a PTP view. Normally when this happens, a
perspective opens without that view. In this case it would not open, and
there was no way to get to the C / C++ perspective to reset it. Trying to do
so resulted in Eclipse's hanging and having to be kill -9'ed. So I deleted
all the C / C++ stuff as well, and started over. It turns out I already had 1.1.1 installed. Many of the plug-ins
are still 1.1.0 including where you do "sh BUILD". I have now reinstalled everything including running "sh
BUILD", using -clean regularly, and recreating the launcher. I still get the same
exception, and the same Machinemachine0 machine in the drop-down menu in the launch configuration. I'm not sure where to go from here. -Ken -----Original Message----- From: ptp-user-bounces@xxxxxxxxxxx
[mailto:ptp-user-bounces@xxxxxxxxxxx] On Behalf Of Kenneth Evans Sent: Friday, December 21, 2007 2:55 PM To: ' Subject: RE: [ptp-user]PTPLauncherFailswithJava.lang.reflect.InvocationTargetException Greg, Thanks. That fixed it. I didn't know that. I didn't
have the same problem with MPICH2, although there you start the daemon manually. Your TODO item looks good to me. In the meantime I've been
researching OpenMPI and see that are, in fact, _many_ options to mpiexec. Unfortunately, I still get the exception in Eclipse, even after
starting with -clean. I can't set a breakpoint on the exception,
apparently because it thinks it is running C/C++. I will uninstall 1.1.0 and install 1.1.1. -Ken _______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user _______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user _______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user _______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user |
_______________________________________________ ptp-user mailing list ptp-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-user