[Progress Communities] [Progress OpenEdge ABL] Windows processes: put identifying features FIRST

Status
Not open for further replies.
S

Stefan Drissen

Guest
When the whole java / ABL stack has become unusable due to networking changes, it can help to kill WebSpeed agents (_progres.exe) and WebSpeed brokers (java.exe). But... the identifying features are so far back along the command line that the command line (task manager) cannot be used to identify the broker / agent. example webspeed broker: c:\progress\oe11.7\jre\bin\java -classpath c:\progress\oe11.7\jdk\lib\tools.jar;c:\progress\oe11.7\java\progress.jar -DInstall.Dir=c:\progress\oe11.7 -Djava.secruity.policy=c:\progress\oe11.7\java\java.policy -DCanonicalName=fathom1. :ID=WebSpeed com Just when it was starting to get interesting the 256 character limit kicks in...

Continue reading...
 
Status
Not open for further replies.

Similar threads

J
  • Locked
[Progress News] [Progress OpenEdge ABL] What’s New in OpenEdge 12.8: Supercharge Developer Efficiency, Enhance Database Management and Improve Applica
Replies
0
Views
455
Jessica Malakian
J
C
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: FW: Progress Alert and Notification Service Article Alert OpenEdge
Replies
0
Views
579
Community Admin
C
A
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: 2020.2 Progress DataDirect for JDBC for HubSpot Driver: Initial Preview Release
Replies
0
Views
821
Avadhoot Kulkarni
A
T
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: 2020.1 Progress DataDirect for JDBC for Aha! driver: Initial Preview Release
Replies
0
Views
973
Thomas Dixon
T
T
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: 2020.1 Progress DataDirect for JDBC for Microsoft Dynamics 365 driver: Initial Preview Rele
Replies
0
Views
845
Thomas Dixon
T
Top