APAR status |
Closed as program error.
| Error description
When you telnet into a unix environment machine which is running
Websphere there are problem with wscp commands. When you try
to do the EnterpriseBean show <name> command in wscp an X11
error will appear. This is because the wscp command uses AWT
components which cause problem with telnet. Local fix
Workaround is to simply make sure the DISPLAY var is set
properly to a xserver prior to calling WSCP. Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of WSCP *
****************************************************************
* PROBLEM DESCRIPTION: Telnet to WebSphere on a UNIX *
* environment to run WSCP command fails *
* to work. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In WAS 3.5 running on UNIX, if user runs WSCP on a
non-graphical interface (such as telnet into the UNIX host, or
without starting X), when user execute commands such as
"EnterpriseBean show", the WSCP fails with exception as
follows:
Can't connect to X11 window server using
':0.0' as the value of the DISPLAY variable" follows:Can't connect to X11 window server using':0.0' as the value of the DISPLAY variable" Problem conclusion
The cause of exception:
"Can't connect to X11 window server using
':0.0' as the value of the DISPLAY variable" when running WSCP
on non-graphical interface is due to sharing of certain classes
between WSCP and the GUI. This fix created new independent
classes for WSCP and removed the swing component dependencies. The cause of exception:"Can't connect to X11 window server using':0.0' as the value of the DISPLAY variable" when running WSCPon non-graphical interface is due to sharing of certain classesbetween WSCP and the GUI. This fix created new independentclasses for WSCP and removed the swing component dependencies. Temporary fix
posted test eFix on wasdoc0 for customer. Comments
APAR information | APAR number | PQ66579 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-09-25 | Closed date | 2002-10-28 | Last modified date | 2002-10-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|