Adobe-livecycle-weblogic.ear deployment issue on weblogic 12c

Hi All,
I am trying to install livecycle 3 on weblogic 12c. but in configuration manager adobe-livecycle-weblogic.ear is not getting deployed when packaged JDBC is selected
has anyone faced this isse before...

Hi Ravi,
WebLogic 12c is not a supported Application Server for LiveCycle ES3.
You can visit http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.html for a list of supported Application Servers for LiveCycle ES3.
Thanks and Regards,
Hina Rastogi

Similar Messages

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

Deployment issue in weblogic 10.3

Hi,
I am facing the below error when am trying to deploy the ear on my weblogic server in Linux Env. I have gone through the posts here for similar problem and tried all the suggestions with no results. Tries changing the permissions on _WL_TEMP_APP_DOWNLOADS folder on admin server too. Please inform if you people have any idea on this.
java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "1,374,489,582,513". Underlying error is: "null"
        at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
        at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
        at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
        at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
        at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
        at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepareDataUpdate(AbstractOperation.java:890)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.stageFilesFromAdminServer(AbstractOperation.java:264)
        at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1375)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:155)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:133)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:27)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:112)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
        at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
        at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:410)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I am deploying the application with Deployer utility as below:
java weblogic.Deployer -adminurl t3://localhost:8001 -username weblogic1 -password weblogic1 -targets my_Server -verbose -debug -deploy /var/app/weblogic/user_projects/domains/myDomain/myapp.ear
All advices and pointer are hearty welcome..
Thanks in advance...

We are working on Solaris server and i checked , it looks like we do not have any HIPS services running there.. i got the below output:
bash-3.00$ svcs HIPS
svcs: Pattern 'HIPS' doesn't match any instances
STATE          STIME    FMRI
bash-3.00$ svcs hips
svcs: Pattern 'hips' doesn't match any instances
STATE          STIME    FMRI
Thanks..

Ear deployment issue.

Hi,
i am using jdev Studio Edition Version 11.1.1.4.0
I have created EAR of my application and trying to depoly it on Weblogic server.
I have following entry in weblogic-application.xml
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
[03:12:39 PM] ---- Deployment started. ----
[03:12:39 PM] Target platform is (Weblogic 10.3).
[03:13:07 PM] Retrieving existing application information
[03:13:07 PM] Running dependency analysis...
[03:13:07 PM] Building...
[03:13:28 PM] Deploying 3 profiles...
[03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
[03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
[03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
[03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
[03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
[03:13:55 PM] Entering Oracle Deployment Plan Editor
[03:15:53 PM] Deploying Application...
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
[03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
[03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
*[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
[03:16:41 PM] See server logs or server console for more details.
[03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
[03:16:41 PM] #### Deployment incomplete. ####
[03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am getting above exception while i am trying to depoly the my ear. please see bold lines.
Please give me some guide line .
Regards,
Kiran.

Hi John,
Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
For my installations:
On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
Thank you,
Gavin
Edited by: GavinWoods on Feb 14, 2012 6:25 AM

Adobe Acrobat 9 Pro deployment issue

Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?

SOLUTION:
The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window.

EAR Deployment Problem with weblogic 10.2. Need help.

Hi,
I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
Thank you,
Vijay M

I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

Weblogic EAR deployment - "error in opening zip file"

Dear All,
we build EAR using MAVEN 3.0.4 on Unix and are trying to deploy the application. The weblogic version is 10.3.4.
We get the following error.
<Mar 12, 2012 5:31:41 PM CET> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "ServletContext@1306153[app:sma-1 module:afis/sma path:/afis/sma spec-version:2.5]" to "/AFIS_DOMAIN/AFIS/servers/production/tmp/_WL_user/sma-1/bmzpi3/sma.web-1.1.0.war".>
<Mar 12, 2012 5:31:42 PM CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1331569832008' for task '13'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'afis/sma''
weblogic.application.ModuleException: Failed to load webapp: 'afis/sma'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.zip.ZipFile.<init>(ZipFile.java:131)
at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
at weblogic.servlet.internal.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:298)
Truncated. see log file for complete stacktrace
>
Obviously, the WAR file cannot be opened by Weblogic, but why and how to solve it ... have no clue. We went through almost everything in Internet, regarding this issue, but we couldn't find a solution.
Every idea or suggestion is more than welcome because I'm running out of ideas :(

Did you perhaps do something like FTP the EAR file to the RedHat box in text mode or something? Can you check that the file size of the file on RedHat is the same as it was on Windows?

BPM engine deployment issue on Weblogic server

Hello,
I read all threads related to this issue, but I am getting mad.
Yesterday:
I have successfully deployed BPM 10.3.1 + certified WLS 10.3.0 on Linux Redhat + Oracle
I have successfully created a BPM configuration with the BPM Admin configuration wizard.
I could successfully access to BPM workspace admin and BPM workskape.
Today:
I have restarted weblogic server and BPM, the engine is not starting, with an error raised in another thread. Below is the most detailed message:
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'..
weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-soapocengine.jar)
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
My server is not connected to the Internet, and will probably not. But it could not access the internet yesterday (before restart) neither...
a reply to another thread says that a patch coprrects this issue. which one is it? please note I cannot download it from the server... I have downloaded all public patches for WLS 10.3 for Linux (ZIP files), but the BSU tool refused to detect them... how should I proceed?
Thank you for your help
Hervé

Hi,
I have downloaded weblogic from oracle downloads 2 weeks back. i thought all the patches would be installed?? But am facing the same issue when deploying engine ear..
Do you think I need to install the above patch ???
A month back I downloaded ( might be by March) Weblogic. I was not facing any issue. But with the new download am facing the issue.
Kindly suggest.
Thanks,
Charan

Ear Deployment failed in weblogic server 9.2

Hi
I have ear which was generated by using weblogic workshop.
I Successfully deployed this ear in weblogic server 8.1 ,but when i am deploying the same ear in weblogic server 9.2(after clicking the activate changes on admin console) the deployment was failed.
any one can plz provide the solution how to deploy in WLS 9.2.or what i need to change.
thanks in advance
I got below messages on admin console
Messages
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
com.bea.wlw.runtime.core.servlet.WebappContextListener
The stack trace which i got from admin server log
<Warning> <Deployer> <g1u0752c.austin.hp.com> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1184166448347> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:292)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassNotFoundException: com.bea.wlw.runtime.core.servlet.WebappContextListener
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:286)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:259)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:158)
     at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:272)
     at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:258)
     at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1591)
     at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1036)
     at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:432)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:407)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:549)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:284)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>

I experienced similar (identical?) problem after upgrading WLS 9.2 with MP2.
In my case simple setting the following fields from the tab 'Server Start': Java Home and Classpath resolved problem.
Greetings
GT

Weblogic EAR deployment before resource initialization

Hi All,
Our application deployment is failing while "starting all services". One of our bean is trying to obtain & initializing a queue in the ejbCreate method (bcos this is a migration project so we are not using the annotations) and it is unable to locate that name in the JNDI tree. After enabling the weblogic jms logs from the console, I could see that the queue's JNDI name is getting binded only at the end of the intiialization, hence the the progrme is unable to obtain the queue instance and failing with NameNotFoundException. I have tried keeping the resource-ref in the ejb-jar to defining the dependency, however it doesn't seems to be working.
Is there anyway, we can specify the deployment priority ?
Thanks in Advance.
Saji

Hi Jay & James,
Thanks for your response. Let me try answer your questions in a single reply.
James,
"Are you using an application module instead of a system module to define your JMS queue?"
No, we are using the system module only, but after seeing your question, I have read thru the application module which looks to be bit complex to adopt at this stage as this is a migration project. Moreover I am not able understand how the the application become active before the resourse initialization.
Jay,
As you correctly pointed in your response, the application become active before the JMS module initialization. I am facing multiple issues due to this.
1. MDB's are failing initially but once the server is fully started then it becomes connected state.
2. Even I face the same issue for my jms-xa-adp.rar and jms-notran-adp.rar deployment.
javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDINoTX'
3. Some of my EJB beans are trying to obtain a queue instances (in ejbCreate Method as the initial-bean-in-free-pool =1 ) which are also failing with NameNotFoundException.
I have tried defining the resource-ref in the ejb-jar and weblogic-ejb-jar.xml but still no luck. These issues were not faced when our application was running on weblogic 8. The setup was exactly same.
How do I make my application active active after all my resource is initialized.
Please help.
Edited by: Saji on 26-Jul-2010 21:24

Deployment issue in Weblogic 9.2

Hi,
I get the below error while deploying my application in Weblogic 9.2.Guess, it has something to do with class path but am unable to fix it.Any help on this, would be great.
Regards,
Rahul
###<Oct 3, 2006 8:16:40 PM IST> <Error> <HTTP> <hpuxdhl> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1159886800944> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "/fcm".
javax.servlet.UnavailableException: Parsing error processing resource path
at org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1014)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:68)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1698)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1675)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1595)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2734)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:892)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:336)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:565)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:128)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)

hi,
I'm facing the same problem.
Did you find the solution ?
Thank you

Weblogic 10 Deployment issues

Hi,
I am trying to use weblogic ant task - Wldeploy to automate the deployment. Unfortuantely deployment fails, I did some research and discovered that WLdeploy class is not present in weblogic.jar(..Bea\wlserver_10.0\server\lib). I also have version 9.2 installed on my box and it has this calss. Just wondering where can I find WLDeploy class in version 10 ?. Also, is there any maven support for version 10 ?
Thanks & Regards !

Hi,
Wldeploy "weblogic.ant.taskdefs.management.WLDeploy" is present in weblogic.jar I have double check it and maven is a build tool and in the docs there is no way written its supported or not, however as its a build tool you can use it but make sure you are using the correct class as above.
Also you can try using the ANT script given in the below link:
Topic: Ant to Deploy Applications
http://middlewaremagic.com/weblogic/?p=373
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic…

EPMA 11.1.1.3 manual deployment issues with WEBLOGIC in EAS and WEBANALYSIS

Hi all,
As we are working on 64 bit machines, we have to deploy hyperion products manually with WEBLOGIC. other than EAS and WEBANALYSIS, all the products are working fine.
we have followed all the steps related to manual deployment. but still we r getting JAVA related error. so if anything else that we need to perform other than normal manual deployment steps, please let me know.
NOTE: EASDOCS, HBRLAUNCHER, are working but EAS is not been deployed.
Regards

Is your WebLogic 32-bit or 64-bit WebLogic? What specific O/S and version are you using? Some of the products make use of 32-bit native libraries's for JNDI and there are not 64-bit native libraries available unless you are using the AIX or Solaris Platform and even then not all products are supported for 64-bit.
If you were to use 11.1.2 it supports most of the product suite in 64-bit on most platforms.
Refer to support matrices at: http://www.oracle.com/technetwork/middleware/bi-foundation/hyperion-supported-platforms-085957.html
Regards,
John A. Booth
http://www.metavero.com

WebSphere deploy adobe-livecycle-websphere.ear error

Starting workbench.
framework search path: d:\Program Files\IBM\WebSphere\AppServer\deploytool\itp\plugins
Creating the project.
IOException: null
IOException: null
IOException: null
IOException: null

To receive this patch you will need to contact Adobe Enterprise Support. Please reference defect id#2695467 and they will evaluate further confirming you have the same problem and deliver you the fix.

Adobe Creative Cloud Enterprise Deployment Issues using SCCM 2012 R2

Hi,
I have been trying to deploy Adobe Creative Cloud Enterprise to Windows 8.1 machines that are identical, using SCCM 2012 R2.
The Adobe package seems fine, because it seems to deploy successfully to some machines. And SCCM 2012 R2 has been configured correctly, as I can deploy other software using it, and again, it deploys Adobe CC successfully to some of the machines.
I have tried comparing the package that is downloaded on the test machine/client machine, with the original package on the distribution point, using Beyond Compare, and there are no differences.
I have contacted Adobe Enterprise Support, and they asked me to send to them log files from Event Viewer, the msi installer, and other Adobe logs, from the machine that failed the deployment. However, after Adobe studying them, they told me that they could not identify any problems... Strange, because I could have sworn that I saw error 1603 pop up over 20 times on different machines indicating that the 'Set-up.dat' file had a problem with it.
After all the testing on over 20 identical machines (same hardware/same software), using different configurations on SCCM 2012 R2 and the client machines, I still can't seem to have a reliable solution to deploying Adobe CC.
The fact that it deploys successfully on one machine and fails on another, or sometimes deploy to two machines and fail on another (simultaneously), is something that I don't understand.
Another thing is that, if I retry the deployment 10-15 times after it failed the first time, it might go through...
Adobe Enterprise Support asked me if they could remote into a machine that failed the deployment to have a look at it and I agreed to that option, but it seems like my issue has been ignored because they never got back to me.
Has anyone had this kind of problem or anything similar before?
I need to be able to deploy this remotely to 100+ machines. So installing manually is not an option.
Any help is appreciated.
This was posted in the wrong section a few days ago. I'm hoping I can get some help here.
Case Number: 1862659812
UPDATE: I spoke to Adobe Customer Support and after 1.5 hours on the phone with a remote session going on, problem was still not solved or identified. Additional log files have been sent and now I'm waiting for a call back.

Hi Robert,
We seem to be having a very similar issue. Our installs would randomly fail with error code 1603 and an error message about a fault in Set-up.dat. Failure rate was near 95% on our 900 machines. Adobe Support and Karl having been looking into our issues but so far no solution has been found.
Having done a lot of investigating we've managed to deploy our package using a schedule task running as a domain admin. This is a nasty solution and we don't intend on using this permanently, but we needed to get the package out.
Are you seeing any of the following:
Entries in PDApp.log:
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The Bootstrapper Process is (5).Stopping the installation process.
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to find the pdb database.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to get the local payload database handle.
Event Log:
Faulting application name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Faulting module name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Exception code: 0xc0000005
Fault offset: 0x000d7c52
Faulting process id: 0xb40
Faulting application start time: 0x01d072a073861622
Faulting application path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Faulting module path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Report Id: c86d9216-de93-11e4-8284-782bcb99e284
Faulting package full name:
Faulting package-relative application ID:
Installer Log
Indicates it can't find the Media_db. We noticed that the folder C:\Program Files (x86)\Common Files\Adobe\caps doesn't get created on the machines were the install fails, so error message is correct in that there isn't a Media_db.db. Sysinterals Process Monitor seems to show that the setup tried to create the folder/files but they don't actually get created. Copying a Media_db into the folder from another machine seems to allow the installation to almost finish, but unsurprisingly you end up with problems later on.

Adobe-livecycle-weblogic.ear deployment issue on weblogic 12c

Similar Messages

Maybe you are looking for