Jetspeed-2 is not designed/implemented to run multiple portal instances in a 
servlet container instance. It's using a static singleton for service 
components, so accessing those portal service components will conflict each 
other.
Do you have any strong reason to run multiple portal instances in single tomcat 
instance, instead of running multiple tomcat instances?

-Woonsan


--- On Mon, 1/3/11, chocba <[email protected]> wrote:

> From: chocba <[email protected]>
> Subject: JetSpeed Portal 2.2.1 Multiple Instance Issue
> To: [email protected]
> Date: Monday, January 3, 2011, 10:49 PM
> 
> Hello,
> I used maven and successfully built and deployed Jetspeed
> portal in Tomcat
> instance. When I hit the url http://localhost:8080/jetspeed, everything
> works fine, I get the home page. Then I created a copy of
> portal webapp
> jetspeed, named as jetspeed2, in the same Tomcat instance.
> The objective is
> to have two jetspeed portals in same tomcat instance. After
> restarting, when
> I hit the url http://localhost:8080/jetspeed2, I get
> the home page, no
> problem. But when I hit the url http://localhost:8080/jetspeed, I get the
> error below::
> 
> "Failed to load portlet
> org.apache.jetspeed.portlets.layout.MultiColumnPortlet:
> java.lang.ClassCastException:
> org.apache.jetspeed.velocity.JetspeedPowerToolFactory
> cannot be cast to
> org.apache.jetspeed.velocity.JetspeedPowerToolFactory"
> 
> Any idea what is the issue? Appreciate your help.
> 
> 
> Jetspeed portal - 2.2.1
> Tomcat - 6.0.16
> 
> -- 
> View this message in context: 
> http://old.nabble.com/JetSpeed-Portal-2.2.1-Multiple-Instance-Issue-tp30581946p30581946.html
> Sent from the Jetspeed - User mailing list archive at
> Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to