Forum Stats

  • 3,851,945 Users
  • 2,264,053 Discussions


Application Deployment works from Admin Console but fails from Workshop?

664622 Member Posts: 1
edited Oct 10, 2008 4:05PM in WebLogic Portal
Hi all,
I am working on a standard Enterprise portal appliication and i am running into a peculiar problem. My application is made of an EAR let's call it my-portal-ear that contains a web app, my-portal-web. I created a Server in Workshop (9.2 like my Weblogic Server version) based on myDomain and added my EAR and it used to deploy and run fine until i decided to change my web app's name in my web.xml and rebuild and redeploy. I made a change to my weblogic.xml as well. I've tried republishing my application through my server view and that's when the trouble started. Ever since then i get either a deployment time out error, or another kind of error but i narrowed it down to the following lines in my server log.

To make a long story short, it seems that instead of calling the
*000000 TailEJBCacheFlow starting cache scrubbers for*
app: my-portal-ear
{color:#000000}like in the correct deployment (from the console), Workshop's deployment calls
*000000 destroyServlet: Destroying all servlets named:*

{color:#000000}All my servlets are destroyed, my Spring session is closed, my beans are destroyed, my ear is removed and deployment fails with the following error:
java.lang.NoClassDefFoundError: com/bea/p13n/entitlements/management/persistence/internal/PolicyRef
at com.bea.content.manager.internal.ContentUpgradeListener.hasUpgradeBeenDone(
at com.bea.content.manager.internal.ContentUpgradeListener.postStart(
at weblogic.application.internal.flow.BaseLifecycleFlow$
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(
at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(
at weblogic.application.internal.flow.TailLifecycleFlow.activate(
at weblogic.application.internal.BaseDeployment$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.BaseDeployment.activate(
at weblogic.application.internal.DeploymentStateChecker.activate(
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$


{color}{color:#3366ff}{color:#000000}Anybody has some insight on why the p13n stuff would work in the console and not in Workshop?
I've tried changing my workspace, deleting and creating a new Workshop server, the only thing i haven't tried yet is deploying on a new domain because setting up the domain for my app is a PITA and i don't want to go through it if i don't have to.

Thanks in advance!

Edited by: user2977465 on Oct 10, 2008 1:04 PM
This discussion has been closed.