-
1. Re: portletbridge deployment exception (Jboss-4.0.3SP1 and P
chris1906 Apr 26, 2006 4:58 AM (in response to dibell)I am having the same issue on Jboss-4.0.3SP1 and Portal 2.2.1RC3.
I can't see that it is anything I have done. If I remove the portletbridge-portlet-1.0.war, I get18:39:02,537 INFO [TomcatDeployer] undeploy, ctxPath=/portletbridge-portlet-1.0, warUrl=.../deploy/portletbridge-portlet-1.0.war/
and the jmx console says portletbridge is not deployed but jmx MainDeployer.listDeployedAsString() reports:org.jboss.portal.server.deployment.jboss.PortalDeploymentInfo@85195958 { url=file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/ } deployer: org.jboss.portal.server.deployment.jboss.ServerDeployer@360e46 status: Deployment FAILED reason: Cannot deploy portlet application; - nested throwable: (javax.management.InstanceAlreadyExistsException: portal:container=WebApp,id=portletbridge already registered.) state: FAILED watch: file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/ altDD: null lastDeployed: 1146039041321 lastModified: 1146038342819 mbeans:
When I redeploy (hot deploy the war via copy to deploy directory) I get:18:48:46,911 INFO [TomcatDeployer] deploy, ctxPath=/portletbridge-portlet-1.0, warUrl=.../deploy/portletbridge-portlet-1.0.war/ 18:48:47,396 INFO [PortletWebApp] Registration is not done -> stop 18:48:47,396 ERROR [MainDeployer] Could not create deployment: file:/C:/Programs /jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/ org.jboss.deployment.DeploymentException: Cannot deploy portlet application; - n ested throwable: (javax.management.InstanceAlreadyExistsException: portal:contai ner=WebApp,id=portletbridge already registered.) at org.jboss.portal.portlet.deployment.jboss.PortletAppDeployment.create (PortletAppDeployment.java:146) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfo$Deploym entContext.create(PortalDeploymentInfo.java:196) at org.jboss.portal.server.deployment.jboss.ServerDeployer.create(Server Deployer.java:229) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
and the jmx listDeployedAsString reports
, org.jboss.portal.server.deployment.jboss.PortalDeploymentInfo@85195958 { url=file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/ } deployer: org.jboss.portal.server.deployment.jboss.ServerDeployer@360e46 status: Deployment FAILED reason: Cannot deploy portlet application; - nested throwable: (javax.management.InstanceAlreadyExistsException: portal:container=WebApp,id=portletbridge already registered.) state: FAILED watch: file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/ altDD: null lastDeployed: 1146039041321 lastModified: 1146038342819 mbeans: , org.jboss.deployment.DeploymentInfo@e4757fd1 { url=file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/ } deployer: MBeanProxyExt[jboss.web:service=WebServer] status: Deployed state: STARTED watch: file:/C:/Programs/jboss-4.0.3SP1/server/default/deploy/portletbridge-portlet-1.0.war/WEB-INF/web.xml altDD: null lastDeployed: 1146041326911 lastModified: 1146038341147 mbeans: jboss.web:j2eeType=Servlet,name=jsp,WebModule=//localhost/portletbridge-portlet-1.0,J2EEApplication=none,J2EEServer=none (state not available) jboss.web:j2eeType=Servlet,name=pbhs,WebModule=//localhost/portletbridge-portlet-1.0,J2EEApplication=none,J2EEServer=none (state not available) jboss.web:j2eeType=Servlet,name=default,WebModule=//localhost/portletbridge-portlet-1.0,J2EEApplication=none,J2EEServer=none (state not available)
but the portletInstance is not available in the portal management portlet.
How can I get around this please? -
2. Re: portletbridge deployment exception - duplicate xml files
chris1906 Apr 26, 2006 6:22 AM (in response to dibell)Hey dibell - I just thought that likely the duplication of .xml files in the portletbridge.war may be the issue. I'll try removing the duplicated files (eg portlet.xml) tomorrow (12 hours away) - chris
-
3. Re: portletbridge deployment exception
dibell Apr 26, 2006 10:05 AM (in response to dibell)Your thoughts were correct chris1906.
This error is caused because the portlet-bridge war has the src tree under the WEB-INF directory which contains the portlet.xml again!
JBossPortal finds both and therefore tries to register the app twice which then fails.
Rebuilding the war without the src directory deploys straight away. -
4. Re: portletbridge deployment exception
chris1906 Apr 26, 2006 5:27 PM (in response to dibell)Dibell - thanks for checking this out. On to the next challenge!
Chris -
5. Re: portletbridge deployment exception
dibell Apr 27, 2006 4:38 AM (in response to dibell)That fixed the deployment but the HTML rewriting doesn't seem to work. The initial URL appears in the portlet but any links clicked come straight back out to the original site.
Are you seeing that too chris1906? -
6. Re: portletbridge deployment exception
chris1906 Apr 27, 2006 4:59 AM (in response to dibell)Yes, I am not seeing very good behaviour. I'll probably have to put further portletbridge work on hold until Tuesday, but advice on any experience/solutions you have/find would be appreciated.
Chris