Bugzilla – Full Text Bug Listing
| Summary: | [dstore] Processes do not work on Dstore-UNIX connection to Solaris | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Martin Oberhuber <mober.at+eclipse> | ||||||
| Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | Keywords: | helpwanted | ||||||
| Version: | 2.0 | ||||||||
| Target Milestone: | 3.1.1 | ||||||||
| Hardware: | Sun | ||||||||
| OS: | Solaris-Motif | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Not for 2.0 - if anybody wants to contribute a dstore processes miner for Solaris, this would be welcome. This should not be very hard to get done -- just create a new
UniversalSolarisProcessHandler.java
in
org.eclipse.rse.services/
clientserver/
org/eclipse/rse/services/clientserver/processes/handlers
based on the existing code in
UniversalLinuxProcessHandler.java
and then register the implementation in
ProcessHandlerManager.getNewProcessHandler()
in the same package.
Created attachment 139901 [details]
server jar to try on solaris
I'm not sure whether this will work or not (since I don't have access to a solaris box) but this is a jar that was built using a modified version of the RSE 3.1 code. At the moment, the process handling for solaris is assuming the same form as AIX does. If someone can try this on a solaris box to see whether the process subsystem works, then maybe we can get this resolved.
Created attachment 140035 [details]
patch to support solaris ps commands
I've committed the change to cvs. |
Connect to remote dstore-unix server running on Solaris 5.9, Sun Java 1.5.0_08 Expand the My Processes filter. An empty List is shown. The dstore server prints an exception: java.lang.Exception: "No handler for this system type". I think we should either implement a handler, or handle this more gracefully: - Detect dynamically that no handler is there and disable the subsystem as soon as a connect is tried - At least return the "No handler" message to the user, instead of just "Empty list" -----------Enter bugs above this line----------- TM 2.0M5 Testing installation : WR wb05.07fa, based on eclipse-SDK-3.3M4 RSE install : Link to existing download from update-site: runtime-all + tests + remotecdt + efs + discovery + terminal java.runtime : Sun 1.5.0_08-b03 os.name : solaris-motif: Solaris 9 9/04 s9s_u7wos_09 SPARC os.uname : SunOS szg-anar 5.9 Generic_118558-06 sun4u SUNW,Sun-Blade-1500 ------------------------------------------------ systemtype : Solaris-local, Dstore-unix, Ssh-Linux targetos : Windows XP SP1, and others targetvm : Sun 1.5.0_08-b03 ------------------------------------------------