I just experienced a strange problem with WebSphere Process Server. When I started WPS server from WebSphere Integration Developer, its status was starting… starting… and starting… only. The server’s status remains unchanged for ever. I tried all the ways I could think to make the status as started. I stopped the server, restarted the server, killed the server, restarted WID, killed WID, and even restarted my machine (Unfortunately I did not know how to kill my machine. Moreover my laptop was given by my company and any developments on my laptop’s physical and mental state has a direct impact on my pas slip. So I did not invest too much time for reading articles on how to kill my machine :-) ).

The strange part was, according to the log files the server was open for e-business and when I tried I was able to access the BPC Explorer and admin console. But some how WID didn’t know about the server’s status change.

Finally I got a solution to fix the problem. Just double click on the server and open the server properties window. Change the ‘Server connection type’ to SOAP. I don’t know how it solved the problem, but it worked and it is working.

Share/Save/Bookmark

If you enjoyed this post, make sure you subscribe to my RSS feed!



Related Posts:
  • Creating a Business Calendar in WebSphere Integration Developer 6.1.2
  • Querying human task based on custom property using EJB API
  • WebSphere Process Server Human task custom properties
  • Business calendars in WID 6.1.2
  • Running a correlation set


  • 3 Responses to “WPS server’s status is starting… starting… and starting…”  

    1. 1 Zain

      Thanks dude; just started with WID/WPS and ran into exactly the same thing.

    2. 2 Anthony

      Dude, thanks a lot :mrgreen: !!!! I’ve been facing this annoying problem for such a long time… just can’t believe someone has finally found a solution…

      Thank you very, very much!!!!! :grin:

    3. 3 Varun Sharma

      Thank for the solution this problem was annoying me for last 2 weeks.

    Leave a Reply