Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
WSM process is gone
 Login/Join
 
Platinum Member
posted
New to WebFocus--EDASERVE is on a Sun box.

Just wondering whether anyone has a suggestion about how to get out of this situation.

$ edastart -start
Shared memory remains but WSM process is gone
$ edastart -stop
Shared memory remains but WSM process is gone
Requesting to stop Workspace Manager in /opt/webfocus/ibi/srv52/wfs
'stop' request to Workspace Manager failed - (unknown)

Tried to find processes to kill, but nothing likely seemed to show up with ps -elf.

Thanks. Suzy
 
Posts: 124 | Location: Lebanon, New Hampshire | Registered: April 24, 2003Report This Post
Platinum Member
posted Hide Post
Earlier post didn't 'take', but I got this very quick reply from Customer Support after I opened up a case. Worked great.

------------------------
Hi Suzy,

This is because as the message mentions the shared memory remains and the
processes are gone. You can release the memory by using
$ edastart -clear or $./edastart -clear

To clear out the edatemp without bringing up the server you can use
$ edastart -cleardir or $./edastart -cleardir

Please let me know if there is anything else.

Regards
Paul
 
Posts: 124 | Location: Lebanon, New Hampshire | Registered: April 24, 2003Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders