aspose file tools
The moose likes Portals and Portlets and the fly likes Portal Server 5.1 Problem Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » Portals and Portlets
Reply Bookmark "Portal Server 5.1 Problem" Watch "Portal Server 5.1 Problem" New topic
Author

Portal Server 5.1 Problem

Gaurav Sharma
Greenhorn

Joined: Jan 30, 2007
Posts: 28
Hi,

I am having some queries regarding WPS5.1 :-

1. If i made some changes in shared/app, I need to restat the server. So is there any way (Server Settings) through which if I made some changes I need not to re-start the server.

2. I am using WPS5.1 with RAD6.0. For running my application I have to add five EARs which makes the server bit heavy. I usually get an exception :

[12/10/07 8:32:26:059 GMT] 6ab0fd6c ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 0" (523ffd65) has been active for 727,096 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.


To make the server in Started mode I have to stop the server and again restart it.
So is there any server setting through which I dont get such exception.?

Anyone please help me out of this problem as it waste a lot of time to restart & load five application.

Regards,
Gaurav
Sanjay Kannan
Greenhorn

Joined: Nov 25, 2007
Posts: 16
If you add any libraries, you'll have to restart the portal server. There is no round about way. But for your jsp's you can enable the re-load property in the server so that it compiles again if you make any changes to the jsp in your portlet app. There is another way for development purpose only, by keeping all the dependent jar files in your portlet lib folder and through the WAS admin console, restart the portlet application. But the question is in case of standalone install of portal 5.1, whether you can access the WAS admin console of portal server instance. In wps6.0 you can access the WAS admin console of server1 and WebSphere_Portal instance separately.
Dharmesh Chheda
Ranch Hand

Joined: May 08, 2001
Posts: 204
Hi
Since you already got your reply to point 1>

My inputs to point 2 are ... in case you want to remove the portlets, right click on the server and select the Add/Remove projects and just keep the one which you want and remove the rest. By doing that only the required portlet will load

Dharmesh


regards,<br />Dharmesh Chheda
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Portal Server 5.1 Problem
 
Similar Threads
HELP! Websphere ThreadMonitor Exception
Problem with RAD
Loading .properties file.
Problem when code changes!!!
debugging web application on weblogic from eclipse