On a very long, large project where there are multiple portals I will create separate worskpaces for the different portals. Especially when developing shared libraries, to save time in unit testing and debugging. Once in a while, I would get this annoying message about the WebLogic Server not starting within the timeout period. The server does eventually start, but you can’t debug without restarting.
Later in the project I had to run all of the portals in Workshop at once. Being able to debug become the norm, which is really annoying when trying to find bugs in code you have never seen before. I did some digging and found that the timout period was made configurable in an older version of Workshop. Originally, there were several versions of Workshop. Some were versions for specific products, like WebLogic Portal. Then they combined them in all into one. Unfortunately, the ability to configure the timeout was only in the WLP version and did not make it into Workspace Studio (the actual new name for Workshop that no one seems to use).
Long story short (yeah, I know, too late), I got the feature ported forward to 10.2. It is patch WW5U | F21UMQIN. Once the patch is installed, edit workshop.ini and add the following:
-Dweblogic.deployment.timeout=3600000
-Dweblogic.startserver.timeout=3600000
-Dweblogic.stopserver.timeout=3600000
3600000 is number of milliseconds, and is the maximum setting. You can set it for whatever you want less than that, but why would you?
© Scott S. Nelson
Glad I blogged this, as I ran into today at a new client.
Note that in Oracle Enterprise Pack for Eclipse (OEPE), the settings are done in the (normal) eclipse.ini file instead of workshop.ini. However, they are ignored from there. It is now controlled in the Server configuration screen AFTER the server has been added.
Screen shot to come, when I am not trapped behind two firewalls for FTP access.