You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Bryan Noll <bn...@virtuas.com> on 2006/04/11 00:24:19 UTC
WebLogic 9.1 - no worko
Hello all... Mr. Watler told me that two gentlemen that frequent this
list, Ate Douma & David Taylor, may be able to provide some insight on
getting Jetspeed 2 up and going on Weblogic 9.1. I'm about 3 hours into
it, and still haven't made it happen. We seem to have gotten as far as
getting jetspeed itself deployed OK... but when attempting to deploy any
portlet war's to the jetspeed.war/WEB-INF/deploy, we continually see the
following:
War C:\bea\weblogic91\samples\domains\wl_server\autodeploy\j2-admin.war
created
INFO: File:
C:\bea\weblogic91\samples\domains\wl_server\autodeploy\jetspeed.ear\WEB-INF\deploy\j2-admin.war
deployed
<Apr 10, 2006 4:20:50 PM MDT> <Warning> <Deployer> <BEA-149004>
<Failures were detected while initiating deploy task for application
'_appsdir_j2-admin_war'.>
<Apr 10, 2006 4:20:50 PM MDT> <Warning> <Deployer> <BEA-149078> <Stack
trace for message 149004
weblogic.management.DeploymentException: Attempt to operate 'deploy' on
null BasicDeploymentMBean : _appsdir_j2-admin_war
at
weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1314)
at
weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1358)
at
weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1059)
at
weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1404)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:158)
Truncated. see log file for complete stacktrace
>
Any ideas or thoughts from folks who have been there/done that would be
much appreciated.
Thanks...
--
+-------------------------------
| Bryan Noll
| Practice Consultant
| Virtuas Open Source Solutions
| o: 303.260.7300 x713
| c: 720.201.9659
+-------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: WebLogic 9.1 - no worko
Posted by Ate Douma <at...@douma.nu>.
Bryan,
I'd love to help you out with this, but actually I haven't used WebLogic before.
I haven't seen much reports of others deploying Jetspeed-2 on WebLogic so you might be
an early-adopter here :)
Looking at the stacktrace you provided this seems to be a WebLogic specific "autodeploy"
type of problem...
Maybe someone else on the list has experience with WebLogic autodeployment, but other
than that I can only advise you to ask again on WebLogic specific lists or forums.
Sorry for not being able to provide more help right now.
But if it turns out to be related how Portlet Application registration is implemented in
Jetspeed please let me know. Than I surely will try to help you out.
Regards, Ate
Bryan Noll wrote:
> Hello all... Mr. Watler told me that two gentlemen that frequent this
> list, Ate Douma & David Taylor, may be able to provide some insight on
> getting Jetspeed 2 up and going on Weblogic 9.1. I'm about 3 hours into
> it, and still haven't made it happen. We seem to have gotten as far as
> getting jetspeed itself deployed OK... but when attempting to deploy any
> portlet war's to the jetspeed.war/WEB-INF/deploy, we continually see the
> following:
>
> War C:\bea\weblogic91\samples\domains\wl_server\autodeploy\j2-admin.war
> created
> INFO: File:
> C:\bea\weblogic91\samples\domains\wl_server\autodeploy\jetspeed.ear\WEB-INF\deploy\j2-admin.war
> deployed
> <Apr 10, 2006 4:20:50 PM MDT> <Warning> <Deployer> <BEA-149004>
> <Failures were detected while initiating deploy task for application
> '_appsdir_j2-admin_war'.>
> <Apr 10, 2006 4:20:50 PM MDT> <Warning> <Deployer> <BEA-149078> <Stack
> trace for message 149004
> weblogic.management.DeploymentException: Attempt to operate 'deploy' on
> null BasicDeploymentMBean : _appsdir_j2-admin_war
> at
> weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1314)
>
> at
> weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1358)
>
> at
> weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1059)
>
> at
> weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1404)
>
> at
> weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:158)
>
> Truncated. see log file for complete stacktrace
> >
>
> Any ideas or thoughts from folks who have been there/done that would be
> much appreciated.
>
> Thanks...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: WebLogic 9.1 - no worko
Posted by David Sean Taylor <da...@bluesunrise.com>.
Bryan Noll wrote:
> Hello all... Mr. Watler told me that two gentlemen that frequent this
> list, Ate Douma & David Taylor, may be able to provide some insight on
> getting Jetspeed 2 up and going on Weblogic 9.1. I'm about 3 hours into
> it, and still haven't made it happen. We seem to have gotten as far as
> getting jetspeed itself deployed OK... but when attempting to deploy any
> portlet war's to the jetspeed.war/WEB-INF/deploy, we continually see the
> following:
>
I don't recommend Jetspeed's live deployment mechanism on Weblogic,
although it might work, I've never tried it recently.
Instead use our command line deploy tool to infuse the necessary startup
registration code into your webapp, and then package your portlet
applications specifically for Weblogic as you would any other webapp,
and deploy the app the same way you would deploy any other webapp.
With this approach, the portlet application will register with Jetspeed
at runtime, during servlet init. Thus, you need to have Jetspeed
installed on Websphere prior to installing any other portlet apps.
To Run the command line tool to infuse automatic registration of portlet
app at app server startup:
java -jar target/jetspeed-deploy-tools-2.0-M4-SNAPSHOT-uber.jar [-s]
source.war destination.war
-s: stripLoggers - remove commons-logging[version].jar and/or
log4j[version].jar from war
required when targetting application servers like JBoss
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org