Deployment failure in Weblogic

Hi,
I am new to ADF development. I am using jdev11.1.1.0 and web logic server10.3. I downloaded 'rcf-dvt-demo.war' from the oracle site and deployed in the weblogic.
But i am getting the following issues.....
Unresolved WebApp library references defined in weblogic.xml, of module 'rcf-dvt-demo.war' [Extension-Name: jstl, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 1.2, exact-match: false].
There was a failure when processing annotations for application C:\Documents and Settings\u20658\My Documents\Downloads\rcf-dvt-demo.war. Please make sure that the annotations are valid. The error is javax.faces.webapp.FacesServlet
BEA-149265
BEA-149078
please advise the steps to resolve the issue.
Thanks,
Uma.

Hi,
I assume the demo WAR you downloaded is for a newer version of JDeveloper (11.1.1.3 is what I assume). To fix the issue, have a look at the weblogic.xml file in the WAR file, which defines the ADF library dependency. You can try removing the version number and see if this worked. If this fails, you still have the option to download JDeveloper 11g 11.1.1.3 (we don't maintain older versions of the ADF Faces component demo)
Frank

Similar Messages

  • Deployment Failures on WebLogic 9.2

    Hello,
    I have several deployments that are failing on WebLogic 9.2, including the JBoss Drools BRMS. Upon startup the following error is generated for each deployment:
    Deployment exception [Deployer:149233]....
    An unexpected error during deployment process....
    The security realm weblogicDefault does not support application versioning. Unable to deploy.....[Security:090772].
    A NullPointer Exception results when I try to start them. The BEA Enterprise Security product is installed on this server. I also have several security providers (Authentication, Authorization, etc) installed from Siteminder Netegrity.
    As related to the versioning error, research has shown that all the providers in the security realm must support application versioning but I can't find any information concerning this from Siteminder. Plus I'm not even sure if this is the problem....
    Help on this matter would be greatly appreciated!

    Hi,
    I am upgrading the application from weblogic 8.1 to WebLogic 9.2 version,
    There i am unable to deploy the application to the server.
    i am getting the error like :
    <Sep 24, 2007 4:22:11 PM IST> <Error> <J2EE> <BEA-160197> <Unable to load descri
    ptor C:\DOCUME~1\empID\LOCALS~1\Temp\appcgen_citOpPortalApp.ear\CITOperate.war/
    WEB-INF/web.xml of module XXXXX.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    Please suggest me, how this can be done,
    Appreciation could be Regrated.
    Regards,
    Bheemu

  • Oracle Identity Analytics (OIA 11g) Deployment failure in weblogic server

    Hi,
    While deploying OIA 11g (which is integrating with OIM 11g) in weblogic application server 10.3.3.0, i am getting the following deployment error...could you please advise on this.
    Appreciate your help!
    An error occurred during activation of changes, please see the log for details.
    weblogic.application.ModuleException:
    Could not initialize class org.springframework.aop.aspectj.AspectJExpressionPointcut
    Server log -
    er org.springframework.web.context.ContextLoaderListener failed: org.springframe
    work.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem
    : Failed to import bean definitions from relative location [security-acls-contex
    t.xml]
    Offending resource: ServletContext resource [/WEB-INF/security-context-server.xm
    l]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreExc
    eption: Unexpected exception parsing XML document from ServletContext resource [
    /WEB-INF/security-acls-context.xml]; nested exception is java.lang.NoClassDefFou
    ndError: Could not initialize class org.springframework.aop.aspectj.AspectJExpre
    ssionPointcut.
    org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Config
    uration problem: Failed to import bean definitions from relative location [secur
    ity-acls-context.xml]
    Offending resource: ServletContext resource [/WEB-INF/security-context-server.xm
    l]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreExc
    eption: Unexpected exception parsing XML document from ServletContext resource [
    /WEB-INF/security-acls-context.xml]; nested exception is java.lang.NoClassDefFou
    ndError: Could not initialize class org.springframework.aop.aspectj.AspectJExpre
    ssionPointcut
    at org.springframework.beans.factory.parsing.FailFastProblemReporter.err
    or(FailFastProblemReporter.java:68)
    Thanks,
    Sudhakar
    Edited by: Sudhakar on Mar 14, 2011 8:12 AM

    These logs are coming from my tomcat trial:
    14:58:48,749 INFO [Config] OSCache: Getting properties from URL file:/home/mw/Downloads/apache-tomcat-6.0.32/webapps/rbacx.war/WEB-INF/classes/oscache.properties for the default configuration
    14:58:48,749 INFO [Config] OSCache: Properties read {cache.blocking=true, cache.algorithm=com.opensymphony.oscache.base.algorithm.LRUCache, cache.cluster.multicast.ip=231.12.21.100, cache.capacity=10000, cache.memory=true}
    14:58:48,749 INFO [GeneralCacheAdministrator] Constructed GeneralCacheAdministrator()
    14:58:48,749 INFO [GeneralCacheAdministrator] Creating new cache
    14:59:07,794 ERROR [MultiCoreClusterAwareEmbeddedServer] I/O problem
    java.io.FileNotFoundException: /home/mw/mwh/oia/.indexes/solr.xml (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
    I tried creating a .indexes directory there and it worked fine. Then I deleted it.
    14:59:55,387 INFO [SearchIndexStartupRunner] Scheduler Started
    14:59:55,398 WARN [SearchIndexStartupRunner] Indexes are not consistent.
    14:59:55,398 WARN [SearchIndexStartupRunner] We will rebuild indexes now.
    14:59:55,398 INFO [SearchIndexStartupRunner] Starting Full Indexing
    14:59:59,396 ERROR [SolrSearchProvider] Could not start full search.
    java.lang.NullPointerException
         at com.vaau.commons.search.searchengine.solr.MultiCoreClusterAwareEmbeddedServer.initIndex(MultiCoreClusterAwareEmbeddedServer.java:547)
         at com.vaau.commons.search.searchengine.solr.AbstractSolrSearchEngine.initializeIndex(AbstractSolrSearchEngine.java:229)
         at com.vaau.commons.search.searchengine.solr.MultiCoreClusterAwareEmbeddedServer.initializeIndex(MultiCoreClusterAwareEmbeddedServer.java:541)
    No idea.
    5:00:00,474 DEBUG [CertificationReminderJob] [start] Executing certification reminder job...
    15:00:00,475 DEBUG [ReminderManagerImpl] [start] firing certification reminders
    15:00:00,506 ERROR [ReminderManagerImpl] Error: No System configuration found, please configure the system first
    15:00:00,506 DEBUG [CertificationReminderJob] [finished] Executing certification reminder job...
    15:00:00,506 DEBUG [CertificationReminderJob] [start] Executing certification expiry check job...
    15:00:00,508 DEBUG [CertificationReminderJob] [finished] Executing certification expiry check job...
    Now I found a reference to another post that mentioned ReminderManagerImpl (Re: OIA OIM Integration issue on weblogic 10.3 and OIA Installation & configuration and the instructions there were to download the latest version of the oscache jar. I seem to have the latest one already though.

  • Standalone WLS server instance deployment failure - missing ADFLogger

    I was hoping somebody could help me please with issues of installing ADF JDev 11g apps to separate WLS server instances (ie. not Admin Server) and the ADFLogger class.
    I've successfully configured a separate standalone WLS, installed the ADF Runtime Libraries and deployed/run an ADF JDev 11g app to the server under the default AdminServer.
    We encountered one issue with deployment regarding the ADFApplicationLifecycleListener class which is addessed in the following forum post with the documented workaround of removing ADFApplicationLifecycleListener from the weblogic-application.xml file: Standalone WLS deployment failure - incorrect weblogic-application.xml
    Next we want to deploy to a separate server instance/machine on the standalone WLS (we have the eventual requirement of deploying our apps to a WLS cluster, so we're experimenting with configuring separate WLS server instances+machines).
    I've created via the Admin Server a new separate server instance (say ADFServer) on a separate WLS machine (say ADFMachine) within my standalone WLS. I've configured the separate WLS server instance to run on a different port from the default Admin Server port. In addition for the 3 deployed libraries jsf, jstl and oracle.adf.domain, via selecting them in the Admin Console under Deployments, then the Target tab, I've also "targetted" (read: deployed) these 3 libraries to the new server instance so they reside both on the Admin Server and ADFServer.
    However when I redeploy my original application via JDeveloper's Application Menu -> Deploy option, on deployment to the ADFServer directly I receive the exception at the bottom of this post. The relevant error message:
    java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger
    This class is included in numerous ADF Runtime Libraries, and I would expect that once I targetted the oracle.adf.domain library for both Admin Server and ADFServer, the relevant ADFLogger class should be available (and given the fact I've run the application successfully on the standalone WLS under the Admin Server, it proves the library is available).
    The missing ADFLogger library seems to be a reoccuring theme for application server deployments, in particular OC4J. This is the first time I've seen it broached for WLS when using the ADF Runtime Libraries and haven't found much assistance via the OTN forums, Google searches etc.
    Does anybody know what I've configured incorrectly on my standalone WLS such that the ADFLogger is not configured for the separate WLS server instance? (I suspect I'll have to try the WLS forum too, but lets start here).
    Any help appreciated.
    Thanks & regards,
    CM.
    (Complete stack trace)
    Failure occurred in the execution of deployment request with ID '1229647798124' for task '2'. Error is: 'java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger' java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:965) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:958) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.processJ2eeAnnotations(BaseJ2eeAnnotationProcessor.java:97) at weblogic.j2ee.dd.xml.J2eeAnnotationProcessor.processJ2eeAnnotations(J2eeAnnotationProcessor.java:37) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processFilters(WebAnnotationProcessorImpl.java:241) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:212) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:388) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:44) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:616) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:198) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:725) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) 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:46) 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) java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:965) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:958) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.processJ2eeAnnotations(BaseJ2eeAnnotationProcessor.java:97) at weblogic.j2ee.dd.xml.J2eeAnnotationProcessor.processJ2eeAnnotations(J2eeAnnotationProcessor.java:37) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processFilters(WebAnnotationProcessorImpl.java:241) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:212) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:388) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:44) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:616) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:198) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:725) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) 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:46) 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 do start it by commandline since I only have the AdminServer, and no other nodes. Below is my startWeblogic.sh and setDomainEnv.sh scripts under medrec/bin directory. I don't see any modifications to them for ADF. Also, after extending the domain, the oracle.adf.domain library shows up in my deployments page and is pointing to "/ u01/ app/ oracle/ product/ wls/ jdeveloper/ modules/ oracle. adf. model_11. 1. 1/ adf. oracle. domain. ear". It seems like the extending step is missing a step to give access to all the libraries?
    STARTWEBLOGIC.SH:
    #!/bin/sh
    # WARNING: This file is created by the Configuration Wizard.
    # Any changes to this script may be lost when adding extensions to this configuration.
    # --- Start Functions ---
    stopAll()
         # We separate the stop commands into a function so we are able to use the trap command in Unix (calling a function) to stop these services
         if [ "X${ALREADY_STOPPED}" != "X" ] ; then
              exit
         fi
         # STOP POINTBASE (only if we started it)
         if [ "${POINTBASE_FLAG}" = "true" ] ; then
              echo "Stopping PointBase server..."
              ${WL_HOME}/common/bin/stopPointBase.sh -port=${POINTBASE_PORT} -name=${POINTBASE_DBNAME} >"${DOMAIN_HOME}/pointbaseShutdown.log" 2>&1
              echo "PointBase server stopped."
         fi
         ALREADY_STOPPED="true"
         # Restore IP configuration the node manager starts IP Migration
         if [ "${SERVER_IP}" != "" ] ; then
              ${WL_HOME}/common/bin/wlsifconfig.sh -removeif "${IFNAME}" "${SERVER_IP}"
         fi
    # --- End Functions ---
    # This script is used to start WebLogic Server for this domain.
    # To create your own start script for your domain, you can initialize the
    # environment by calling @USERDOMAINHOME/setDomainEnv.
    # setDomainEnv initializes or calls commEnv to initialize the following variables:
    # BEA_HOME - The BEA home directory of your WebLogic installation.
    # JAVA_HOME - Location of the version of Java used to start WebLogic
    # Server.
    # JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
    # PATH - JDK and WebLogic directories are added to system path.
    # WEBLOGIC_CLASSPATH
    # - Classpath needed to start WebLogic Server.
    # PATCH_CLASSPATH - Classpath used for patches
    # PATCH_LIBPATH - Library path used for patches
    # PATCH_PATH - Path used for patches
    # WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
    # JAVA_VM - The java arg specifying the VM to run. (i.e.
    # - server, -hotspot, etc.)
    # USER_MEM_ARGS - The variable to override the standard memory arguments
    # passed to java.
    # PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
    # POINTBASE_HOME - Point Base home directory.
    # POINTBASE_CLASSPATH
    # - Classpath needed to start PointBase.
    # Other variables used in this script include:
    # SERVER_NAME - Name of the weblogic server.
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and
    # MEM_ARGS)
    # For additional information, refer to the WebLogic Server Administration
    # Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
    # Call setDomainEnv here.
    DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
    . ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
    SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
    SAVE_CLASSPATH="${CLASSPATH}"
    # Start PointBase
    PB_DEBUG_LEVEL="3"
    if [ "${POINTBASE_FLAG}" = "true" ] ; then
         ${WL_HOME}/common/bin/startPointBase.sh -port=${POINTBASE_PORT} -debug=${PB_DEBUG_LEVEL} -console=false -background=true -ini=${DOMAIN_HOME}/pointbase.ini >"${DOMAIN_HOME}/pointbase.log" 2>&1
    fi
    JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
    SAVE_JAVA_OPTIONS=""
    CLASSPATH="${SAVE_CLASSPATH}"
    SAVE_CLASSPATH=""
    trap 'stopAll' 1 2 3 15
    if [ "${PRODUCTION_MODE}" = "true" ] ; then
         WLS_DISPLAY_MODE="Production"
    else
         WLS_DISPLAY_MODE="Development"
    fi
    if [ "${WLS_USER}" != "" ] ; then
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.username=${WLS_USER}"
    fi
    if [ "${WLS_PW}" != "" ] ; then
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.password=${WLS_PW}"
    fi
    CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${MEDREC_WEBLOGIC_CLASSPATH}"
    echo "."
    echo "."
    echo "JAVA Memory arguments: ${MEM_ARGS}"
    echo "."
    echo "WLS Start Mode=${WLS_DISPLAY_MODE}"
    echo "."
    echo "CLASSPATH=${CLASSPATH}"
    echo "."
    echo "PATH=${PATH}"
    echo "."
    echo "***************************************************"
    echo "* To start WebLogic Server, use a username and *"
    echo "* password assigned to an admin-level user. For *"
    echo "* server administration, use the WebLogic Server *"
    echo "* console at http://hostname:port/console *"
    echo "***************************************************"
    # Set up IP Migration related variables.
    # Set interface name.
    if [ "${Interface}" != "" ] ; then
         IFNAME="${Interface}"
    else
         IFNAME=""
    fi
    # Set IP Mask.
    if [ "${NetMask}" != "" ] ; then
         IPMASK="${NetMask}"
    else
         IPMASK=""
    fi
    # Perform IP Migration if SERVER_IP is set by node manager.
    if [ "${SERVER_IP}" != "" ] ; then
         ${WL_HOME}/common/bin/wlsifconfig.sh -addif "${IFNAME}" "${SERVER_IP}" "${IPMASK}"
    fi
    # START WEBLOGIC
    echo "starting weblogic with Java version:"
    ${JAVA_HOME}/bin/java ${JAVA_VM} -version
    if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
         echo "Starting WLS with line:"
         echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}"
         ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}
    else
         echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
         ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1
    fi
    stopAll
    popd
    # Exit this script only if we have been told to exit.
    if [ "${doExitFlag}" = "true" ] ; then
         exit
    fi
    SETDOMAINENV.SH:
    #!/bin/sh
    # WARNING: This file is created by the Configuration Wizard.
    # Any changes to this script may be lost when adding extensions to this configuration.
    # --- Start Functions ---
    BP=100
    SP=$BP
    pushd()
         if [ -z "$1" ]
         then
              return
         fi
         SP=`expr $SP - 1`
         eval _stack$SP=`pwd`
         cd $1
         return
    popd()
         if [ $SP -eq $BP ]
         then
              return
         fi
         eval cd \${_stack$SP}
         SP=`expr $SP + 1`
         return
    # --- End Functions ---
    # This script is used to setup the needed environment to be able to start Weblogic Server in this domain.
    # This script initializes the following variables before calling commEnv to set other variables:
    # WL_HOME - The BEA home directory of your WebLogic installation.
    # JAVA_VM - The desired Java VM to use. You can set this environment variable before calling
    # this script to switch between Sun or BEA or just have the default be set.
    # JAVA_HOME - Location of the version of Java used to start WebLogic
    # Server. Depends directly on which JAVA_VM value is set by default or by the environment.
    # USER_MEM_ARGS - The variable to override the standard memory arguments
    # passed to java.
    # PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
    # DOMAIN_PRODUCTION_MODE
    # - The variable that determines whether the workshop related settings like the debugger,
    # testconsole or iterativedev should be enabled. ONLY settable using the
    # command-line parameter named production
    # NOTE: Specifying the production command-line param will force
    # the server to start in production mode.
    # Other variables used in this script include:
    # SERVER_NAME - Name of the weblogic server.
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and
    # MEM_ARGS)
    # For additional information, refer to the WebLogic Server Administration
    # Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
    ORACLE_HOME="/u01/app/oracle/product/wls/jdeveloper"
    export ORACLE_HOME
    WL_HOME="/u01/app/oracle/product/wls/wlserver_10.3"
    export WL_HOME
    BEA_JAVA_HOME="/u01/app/oracle/product/wls/jrockit_160_05"
    export BEA_JAVA_HOME
    SUN_JAVA_HOME="/u01/app/oracle/product/wls/jdk160_05"
    export SUN_JAVA_HOME
    if [ "${JAVA_VENDOR}" = "BEA" ] ; then
         JAVA_HOME="${BEA_JAVA_HOME}"
         export JAVA_HOME
    else
         if [ "${JAVA_VENDOR}" = "Sun" ] ; then
              JAVA_HOME="${SUN_JAVA_HOME}"
              export JAVA_HOME
         else
              JAVA_VENDOR="BEA"
              export JAVA_VENDOR
              JAVA_HOME="/u01/app/oracle/product/wls/jrockit_160_05"
              export JAVA_HOME
         fi
    fi
    # We need to reset the value of JAVA_HOME to get it shortened AND
    # we can not shorten it above because immediate variable expansion will blank it
    JAVA_HOME="${JAVA_HOME}"
    export JAVA_HOME
    SAMPLES_HOME="${WL_HOME}/samples"
    export SAMPLES_HOME
    DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
    export DOMAIN_HOME
    LONG_DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
    export LONG_DOMAIN_HOME
    if [ "${DEBUG_PORT}" = "" ] ; then
         DEBUG_PORT="8453"
         export DEBUG_PORT
    fi
    if [ "${SERVER_NAME}" = "" ] ; then
         SERVER_NAME="MedRecServer"
         export SERVER_NAME
    fi
    POINTBASE_FLAG="true"
    export POINTBASE_FLAG
    POINTBASE_PORT="9082"
    export POINTBASE_PORT
    POINTBASE_DBNAME="medrec"
    export POINTBASE_DBNAME
    enableHotswapFlag=""
    export enableHotswapFlag
    PRODUCTION_MODE=""
    export PRODUCTION_MODE
    doExitFlag="false"
    export doExitFlag
    verboseLoggingFlag="false"
    export verboseLoggingFlag
    while [ $# -gt 0 ]
    do
         case $1 in
         nodebug)
              debugFlag="false"
              export debugFlag
         production)
              DOMAIN_PRODUCTION_MODE="true"
              export DOMAIN_PRODUCTION_MODE
         notestconsole)
              testConsoleFlag="false"
              export testConsoleFlag
         noiterativedev)
              iterativeDevFlag="false"
              export iterativeDevFlag
         noLogErrorsToConsole)
              logErrorsToConsoleFlag="false"
              export logErrorsToConsoleFlag
         nopointbase)
              POINTBASE_FLAG="false"
              export POINTBASE_FLAG
         doExit)
              doExitFlag="true"
              export doExitFlag
         noExit)
              doExitFlag="false"
              export doExitFlag
         verbose)
              verboseLoggingFlag="true"
              export verboseLoggingFlag
         enableHotswap)
              enableHotswapFlag="-javaagent:${WL_HOME}/server/lib/diagnostics-agent.jar"
              export enableHotswapFlag
              PROXY_SETTINGS="${PROXY_SETTINGS} $1"
              export PROXY_SETTINGS
         esac
         shift
    done
    MEM_DEV_ARGS=""
    export MEM_DEV_ARGS
    if [ "${DOMAIN_PRODUCTION_MODE}" = "true" ] ; then
         PRODUCTION_MODE="${DOMAIN_PRODUCTION_MODE}"
         export PRODUCTION_MODE
    fi
    if [ "${PRODUCTION_MODE}" = "true" ] ; then
         debugFlag="false"
         export debugFlag
         testConsoleFlag="false"
         export testConsoleFlag
         iterativeDevFlag="false"
         export iterativeDevFlag
    fi
    # If you want to override the default Patch Classpath, Library Path and Path for this domain,
    # Please uncomment the following lines and add a valid value for the environment variables
    # set PATCH_CLASSPATH=[myPatchClasspath] (windows)
    # set PATCH_LIBPATH=[myPatchLibpath] (windows)
    # set PATCH_PATH=[myPatchPath] (windows)
    # PATCH_CLASSPATH=[myPatchClasspath] (unix)
    # PATCH_LIBPATH=[myPatchLibpath] (unix)
    # PATCH_PATH=[myPatchPath] (unix)
    . ${WL_HOME}/common/bin/commEnv.sh
    WLS_HOME="${WL_HOME}/server"
    export WLS_HOME
    MEM_ARGS="-Xms256m -Xmx512m"
    export MEM_ARGS
    MEM_PERM_SIZE="-XX:PermSize=48m"
    export MEM_PERM_SIZE
    MEM_MAX_PERM_SIZE="-XX:MaxPermSize=128m"
    export MEM_MAX_PERM_SIZE
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
         if [ "${PRODUCTION_MODE}" = "" ] ; then
              MEM_DEV_ARGS="-XX:CompileThreshold=8000 ${MEM_PERM_SIZE} "
              export MEM_DEV_ARGS
         fi
    fi
    # Had to have a separate test here BECAUSE of immediate variable expansion on windows
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
         MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
         export MEM_ARGS
    fi
    if [ "${JAVA_VENDOR}" = "HP" ] ; then
         MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
         export MEM_ARGS
    fi
    # IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
    if [ "${USER_MEM_ARGS}" != "" ] ; then
         MEM_ARGS="${USER_MEM_ARGS}"
         export MEM_ARGS
    fi
    JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} "
    export JAVA_PROPERTIES
    # To use Java Authorization Contract for Containers (JACC) in this domain,
    # please uncomment the following section. If there are multiple machines in
    # your domain, be sure to edit the setDomainEnv in the associated domain on
    # each machine.
    # -Djava.security.manager
    # -Djava.security.policy=location of weblogic.policy
    # -Djavax.security.jacc.policy.provider=weblogic.security.jacc.simpleprovider.SimpleJACCPolicy
    # -Djavax.security.jacc.PolicyConfigurationFactory.provider=weblogic.security.jacc.simpleprovider.PolicyConfigurationFactoryImpl
    # -Dweblogic.security.jacc.RoleMapperFactory.provider=weblogic.security.jacc.simpleprovider.RoleMapperFactoryImpl
    EXTRA_JAVA_PROPERTIES="-Ddomain.home=${DOMAIN_HOME} -Doracle.home=${ORACLE_HOME} -Doracle.security.jps.config=${DOMAIN_HOME}/config/oracle/jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol ${EXTRA_JAVA_PROPERTIES}"
    export EXTRA_JAVA_PROPERTIES
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${EXTRA_JAVA_PROPERTIES}"
    export JAVA_PROPERTIES
    ARDIR="${WL_HOME}/server/lib"
    export ARDIR
    pushd ${LONG_DOMAIN_HOME}
    # Clustering support (edit for your cluster!)
    if [ "${ADMIN_URL}" = "" ] ; then
         # The then part of this block is telling us we are either starting an admin server OR we are non-clustered
         CLUSTER_PROPERTIES="-Dweblogic.management.discover=true"
         export CLUSTER_PROPERTIES
    else
         CLUSTER_PROPERTIES="-Dweblogic.management.discover=false -Dweblogic.management.server=${ADMIN_URL}"
         export CLUSTER_PROPERTIES
    fi
    LOG4J_CONFIG_FILE="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec/log4j.properties"
    export LOG4J_CONFIG_FILE
    if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
         JAVA_PROPERTIES="${JAVA_PROPERTIES} -Dlog4j.configuration=file:${LOG4J_CONFIG_FILE}"
         export JAVA_PROPERTIES
    fi
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${CLUSTER_PROPERTIES}"
    export JAVA_PROPERTIES
    # Clear the pre_classpath here in case an application template wants to set it before the larger pre_classpath is invoked below
    PRE_CLASSPATH=""
    export PRE_CLASSPATH
    PRE_CLASSPATH=""
    export PRE_CLASSPATH
    JAVA_DEBUG=""
    export JAVA_DEBUG
    if [ "${debugFlag}" = "true" ] ; then
         JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
         export JAVA_DEBUG
         JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
         export JAVA_OPTIONS
    else
         JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da"
         export JAVA_OPTIONS
    fi
    if [ ! -d ${JAVA_HOME}/lib ] ; then
         echo "The JRE was not found in directory ${JAVA_HOME}. (JAVA_HOME)"
         echo "Please edit your environment and set the JAVA_HOME"
         echo "variable to point to the root directory of your Java installation."
         popd
         read _val
         exit
    fi
    if [ "${POINTBASE_FLAG}" = "true" ] ; then
         DATABASE_CLASSPATH="${POINTBASE_CLASSPATH}"
         export DATABASE_CLASSPATH
    else
         DATABASE_CLASSPATH="${POINTBASE_CLIENT_CLASSPATH}"
         export DATABASE_CLASSPATH
    fi
    POST_CLASSPATH=""
    export POST_CLASSPATH
    POST_CLASSPATH="${ORACLE_HOME}/modules/features/adf.share_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"
    export POST_CLASSPATH
    POST_CLASSPATH=""
    export POST_CLASSPATH
    POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${DATABASE_CLASSPATH}${CLASSPATHSEP}${ARDIR}/xqrl.jar"
    export POST_CLASSPATH
    # PROFILING SUPPORT
    JAVA_PROFILE=""
    export JAVA_PROFILE
    SERVER_CLASS="weblogic.Server"
    export SERVER_CLASS
    JAVA_PROPERTIES="${JAVA_PROPERTIES} ${WLP_JAVA_PROPERTIES}"
    export JAVA_PROPERTIES
    JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag}"
    export JAVA_OPTIONS
    # -- Setup properties so that we can save stdout and stderr to files
    if [ "${WLS_STDOUT_LOG}" != "" ] ; then
         echo "Logging WLS stdout to ${WLS_STDOUT_LOG}"
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stdout=${WLS_STDOUT_LOG}"
         export JAVA_OPTIONS
    fi
    if [ "${WLS_STDERR_LOG}" != "" ] ; then
         echo "Logging WLS stderr to ${WLS_STDERR_LOG}"
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stderr=${WLS_STDERR_LOG}"
         export JAVA_OPTIONS
    fi
    # ADD EXTENSIONS TO CLASSPATHS
    if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
         PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
         export PRE_CLASSPATH
    fi
    if [ "${EXT_POST_CLASSPATH}" != "" ] ; then
         POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${EXT_POST_CLASSPATH}"
         export POST_CLASSPATH
    fi
    if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
         JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
         export JAVA_OPTIONS
    fi
    JAVA_OPTIONS="${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    # SET THE CLASSPATH
    CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
    export CLASSPATH
    JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE}"
    export JAVA_VM

  • OIA deployment error in weblogic

    Hi all,
    I am trying to deploy OIA in weblogic. But It is throwing the following exception.
    oracle.net.ns.NetException:Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor even in the jdbc.properties file under conf directory i have mentioned all the properties properly. using the same parameters able to connect to databse through sql developer.
    environment details:
    OS:windows2003 sp2
    db:oracle 11.2.0.1.0
    weblogic:10.3.5.0
    Please help me out.
    Thanks,
    power.

    Hi Pallavi,
    please find the jdbc file
    JDBC driver URL and driver name
    jdbc.url=jdbc:oracle:thin:@localhost:1521:saiDB
    jdbc.driverClassName=oracle.jdbc.OracleDriver
    # Database information
    # RBACx Database owner
    jdbc.username=rbacxservice
    jdbc.password=rbacxservice
    # RBACx Database password
    # Create a property jdbc.password assigned the clear-text value of the database
    # account password, then run the property encryptor utility available in
    # vaau-commons-crypt-2.x.x.jar to encrypt the password.
    # See the Oracle Identity Analytics Administration Guide for details.
    jdbc.defaultAutoCommit=false
    # Scheduler related properties
    jdbc.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
    jdbc.quartz.selectWithLockSQL=SELECT * FROM {0}LOCKS WHERE LOCK_NAME = ? FOR UPDATE
    jdbc.quartz.isClustered=false
    in iam.prop i have changed the loc of the files as mentioned below.
    com.vaau.rbacx.iam.file.import.completeLocation=C:\OIA_staging\import\complete
    com.vaau.rbacx.iam.file.import.schemaLocation=C:\OIA_staging\import\schema
    com.vaau.rbacx.iam.file.import.dropLocation=C:\OIA_staging\import\in
    I did not change any thing in iam-context.xml
    please find the admin server logs:
    <Error> <Deployer> <sai-8b5adc7dfb0> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345440861890> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'OIAin'.>
    ####<Aug 20, 2012 11:04:21 AM IST> <Warning> <Deployer> <sai-8b5adc7dfb0> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1345440861890> <BEA-149004> <Failures were detected while initiating start task for application 'OIAin'.>
    Caused By: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

  • Solaris Deployment Failure for cannot resolve symbol on PersistentContainer

    Hello, I'm having trouble diagnosing the following deployment failure.
    What are some common causes of this? My server was created using an
    Express Integration domain with some custom JMS destinations added
    afterwards via the console. I am deploying an application built with
    Workshop (straight from workshop). I copied over an application from
    Windows to Solaris, deleted the .workshop directory and .beabuild.txt
    and rebuilt the application to deploy.
    I get this error a few times.
    ####<Aug 21, 2003 10:48:19 AM EDT> <Info> <EJB> <rhino> <cgServer>
    <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
    <> <BEA-012033> <Compiling generated EJB classes produced the following
    Java compiler output:
    /export/data/ident/bea/user_projects/domains/ident1Server.conf/./cgServer/.wlnotdelete/EJBCompilerCache/-7dxi2hv35mro/com/bea/wlwgen/PersistentContainer_3fq3ar_Impl.java:143:
    cannot resolve symbol
    symbol : class BMPContainerBean$DuplicateKeyRemoteException
    location: package bean
    perchance you meant 'BMPContainerBean.DuplicateKeyRemoteException'
    throws
    com.bea.wlw.runtime.core.bean.BMPContainerBean$DuplicateKeyRemoteException
    ^
    1 error
    This then causes other errors repeating that the deployment failed (let
    me know if you need more to diagnose this):
    Exception:weblogic.management.ApplicationException: prepare failed for
    .workshop/myApp/EJB/myProc_1trtqtoxcz4uv
    Module: .workshop/myApp/EJB/myProc_1trtqtoxcz4uv Error:
    Exception preparing module:
    EJBModule(.workshop/myApp/EJB/myProc_1trtqtoxcz4uv,status=NEW)
    Unable to deploy EJB: .workshop/myApp/EJB/myProc_1trtqtoxcz4uv from
    .workshop/myApp/EJB/myProc_1trtqtoxcz4uv:
    Compiler failed executable.exec

    But by default WLS8.1 comes with jdk141_02 ...correct ?
    AND what i understand is that...the bug you posted is related to a bug in jdk1.4.2
    ....correct ??
    correct me if i wrong.
    -sangita
    Steven Ostrowski <[email protected]> wrote:
    It looks like this is a bug in the BEA-generated code that is then
    compiled by WLS. The generated code was using the Class1$Class2 notation
    to reference the class, but since $ is a valid character in the class
    name, this does not behave as intended. This used to be a bug in
    pre-1.4.2 but is now fixed in 1.4.2 (look at bug 4635044, and this is
    also mentioned in the 1.4.2 release notes and the Java Developer forums).
    The generated code should be:
    com.bea.wlw.runtime.core.bean.BMPContainerBean.DuplicateKeyRemoteException
    not
    com.bea.wlw.runtime.core.bean.BMPContainerBean$DuplicateKeyRemoteException
    Thanks again for the good response. I'll send this in to BEA support.
    Steven Ostrowski wrote:
    One other thing to add, this was fixed by changing the JAVA_HOME
    variable inside of the startWeblogic.sh script. Setting it in workshop
    did not change anything.
    Steven Ostrowski wrote:
    Wow, you hit it right on target! I was using 1.4.2 then tried it on
    1.4.1_03 and it deployed fine.
    Is this a bug in BEA or in the JDK? In either case, where should I
    report this bug?
    Thanks again
    Rob Woollen wrote:
    What version of the JDK are you using? I believe they changed the
    inner class naming conventions in 1.4.2, and it's breaking lots of
    people.
    -- Rob
    Steven Ostrowski wrote:
    Hello, I'm having trouble diagnosing the following deployment
    failure. What are some common causes of this? My server was created
    using an Express Integration domain with some custom JMS
    destinations added afterwards via the console. I am deploying an
    application built with Workshop (straight from workshop). I copied
    over an application from Windows to Solaris, deleted the .workshop
    directory and .beabuild.txt and rebuilt the application to deploy.
    I get this error a few times.
    ####<Aug 21, 2003 10:48:19 AM EDT> <Info> <EJB> <rhino> <cgServer>
    <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS
    Kernel>> <> <BEA-012033> <Compiling generated EJB classes produced
    the following Java compiler output:
    /export/data/ident/bea/user_projects/domains/ident1Server.conf/./cgServer/.wlnotdelete/EJBCompilerCache/-7dxi2hv35mro/com/bea/wlwgen/PersistentContainer_3fq3ar_Impl.java:143:
    cannot resolve symbol
    symbol : class BMPContainerBean$DuplicateKeyRemoteException
    location: package bean
    perchance you meant 'BMPContainerBean.DuplicateKeyRemoteException'
    throws
    com.bea.wlw.runtime.core.bean.BMPContainerBean$DuplicateKeyRemoteException
    ^
    1 error
    This then causes other errors repeating that the deployment failed
    (let me know if you need more to diagnose this):
    Exception:weblogic.management.ApplicationException: prepare failed
    for .workshop/myApp/EJB/myProc_1trtqtoxcz4uv
    Module: .workshop/myApp/EJB/myProc_1trtqtoxcz4uv Error:
    Exception preparing module:
    EJBModule(.workshop/myApp/EJB/myProc_1trtqtoxcz4uv,status=NEW)
    Unable to deploy EJB: .workshop/myApp/EJB/myProc_1trtqtoxcz4uv from
    .workshop/myApp/EJB/myProc_1trtqtoxcz4uv:
    Compiler failed executable.exec

  • Maven Auto deployment problems in Weblogic 10.0

    Hi All,
    Past two day's i am facing a exception in maven auto deployment process. I have given properly the configuration Tags(Shown below). I am able to send the deployment commands to weblogic but i am getting some run time exceptions. Please find below details.
    mvn -e org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy -Dsource=target/test-war-SNAPSHOT.war
    [INFO] Error stacktraces are turned on.
    [INFO] Scanning for projects...
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Building maven-test-war -SNAPSHOT
    [INFO] ------------------------------------------------------------------------
    [INFO]
    [INFO] --- weblogic-maven-plugin:2.9.1:deploy (default-cli) @ test-war ---
    [INFO] Weblogic Deployment beginning with parameters DeployMojoBase[adminServerH
    ostName = localhost, adminServerProtocol = t3, adminServerPort = 8001, userId =
    weblogic, password = weblogic, artifactPath = C:\test\test\test-war\target/test-war--SNAPSHOT, projectPackaging = war, name = test-war, targetNames = AdminServer, remote = false]
    [INFO] Weblogic Deployment parameters [-adminurl, t3://localhost:8001, -username
    , weblogic, -password, weblogic, -name, test-war, -targets, AdminServer, -s
    ource,
    weblogic.Deployer invoked with options: -adminurl t3://localhost:8001 -username
    weblogic -name test-war -targets AdminServer -source C:\test\test-war\target/test-war--SNAPSHOT.war -deploy
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 2.155s
    [INFO] Finished at: Wed Jul 13 18:06:20 IST 2011
    [INFO] Final Memory: 3M/12M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:dep
    loy (default-cli) on project test-war: Execution default-cli of goal org.co
    dehaus.mojo:weblogic-maven-plugin:2.9.1:deploy failed: A required class was miss
    ing while executing org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy: weblog
    ic/rmi/extensions/RemoteRuntimeException
    [ERROR] -----------------------------------------------------
    Number of foreign imports: 1
    import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:225)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
    ct(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
    ct(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
    ild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
    eStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
    cher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
    a:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
    uncher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
    352)
    Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-c
    li of goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy failed: A requir
    ed class was missing while executing org.codehaus.mojo:weblogic-maven-plugin:2.9
    .1:deploy: weblogic/rmi/extensions/RemoteRuntimeException
    r
    import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
    BuildPluginManager.java:125)
    ... 20 more
    Caused by: java.lang.NoClassDefFoundError: weblogic/rmi/extensions/RemoteRuntime
    Exception
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:90)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.Deployer.run(Deployer.java:70)
    at org.codehaus.mojo.weblogic.DeployMojoBase.executeDeployer(DeployMojoB
    ase.java:510)
    at org.codehaus.mojo.weblogic.DeployMojo.execute(DeployMojo.java:49)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
    BuildPluginManager.java:101)
    ... 20 more
    [ERROR]
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please rea
    d the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContaine
    rException
    I checked the weblogc.jar, i am unable to find the RemoteRuntimeException class in that jar.
    Configuration Tags
    ================
    <configuration>
    <name>web</name>
    <adminServerHostName>localhost</adminServerHostName>
    <adminServerPort>7001</adminServerPort>
    <adminServerProtocol>t3</adminServerProtocol>
    <artifactPath></artifactPath>
    <exploded>true</exploded>
    <userId>weblogic</userId>
    <password>weblogic</password>
    <upload>true</upload>
    <remote>false</remote>
    <verbose>true</verbose>
    <debug>false</debug>
    <targetNames>AdminServer</targetNames>
    </configuration>
    Please help me on the same.
    Regards,
    Jerald.
    Edited by: user1173449 on Jul 14, 2011 6:09 AM

    Jerald, Oracle doesn't own this particular piece of code so I can't help too much since I have no real knowledge of it's working. It was built and used with earlier versions of WLS (8.1, 9.2) so it may not have tracked any changes made to libraries/packaging in WLS 10.0.
    Caused by: java.lang.NoClassDefFoundError: weblogic/rmi/extensions/RemoteRuntimeException
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:90)I see in WLS 10.3.x, that the class identified as missing is located in client JAR files:
    sbutton:~/Oracle/Middleware/wlserver_10.3 $ jwhich RemoteRuntimeException .
    Adding . to search path
    ./server/lib/wljmsclient.jar: weblogic.rmi.extensions.RemoteRuntimeException
    ./server/lib/wlthint3client.jar: weblogic.rmi.extensions.RemoteRuntimeException
    I don't have a 10.0 install so am not sure where it resides in that release.
    We have introduced a WebLogic Server Maven Plugin in our WLS 10.3.3 release which supports deployment operations. This is not supported/certified for working against a WLS 10.0 environment, but if you are using Maven and have an opportunity to update to a more recent release, then we have something which may be of use to you.
    http://download.oracle.com/docs/cd/E17904_01/web.1111/e13702/maven_deployer.htm#BABBBEGG
    -steve-

  • How to delete the deployed composite in weblogic server 11g

    Can someone tell me how to delete the deployed composite in weblogic server 11g ?I'm facing an issue where the weblogic server is getting started and immediately after sometime the server changes to "Force shutdown"..When i checked the logs,there is an error in one of the composite i deployed..So now i wanted to delete the deployed composite?Please help ....
    Thanks

    Hi
    1. Deleting a domain will not hold any references. But make sure that under your user_projects/applications also remove the folder that matches with your domain. Basically under user_projects folder you will see 2 folders named applications and domains. When you create a domain say mySoaDomain, it will crate a folder with the same name under applications folder also with few files like em.ear. If you do this, then you can crate a new soa domain and use the same old name.
    2. NOW comes the most important thing. If you create a new SOADomain, at one point, you had to give details for soainfra and mds schemas. If you give your current existing db details (that was used for your old deleted domain), then you may still have the issues. Because the soainfra db may still have the instances for your old process.
    3. If you really want to have a full clean soa domain, here is what you do:
    a) Run rcu and drop the existing schemas for soainfra and mds.
    b) Run rcu again and create above schemas again.
    c) Now create SOADomain using config wizard and refer above clean rcu db and you are all set.
    3. Under your domain root folder, just searh for files named with your workflow and you should see the .jar location.
    Thanks
    Ravi Jegga

  • Pagelets not rendering in Fusion ADF application pages deployed on standalone weblogic server

    HI All,
    I am creating a Pagelet Producer connection, and dragging a pagelet on the page as iframe, with height auto. When I run the application in the integrated weblogic server, I am able to see the pagelet. However when I deploy the application on the standalone weblogic server, then the pagelet isn't rendered.
    I am using fusion ADF application 11.1.1.7  and standalone weblogic server v 10.3.6.
    Thanks in advance for yours assistance. Please I need a solution for this uregently. DO let me know, if you need any additonal information.
    Regards,
    Nikhil Mahto

    Sorry for the wrong infromation. The correct scenario is:
    I have an ADF application, in which I have a Pagelet producer connection, pages and taskflows. This ADF application is inlcuded in a Webcenter Portal Framework application, as a shared library. When the WCF application is deployed on the Weblogic server, the pagelets don't appear on the pages.
    I tried the FRAMEBUSTING context parameter to never but it didn't help.
    Regards,
    Nikhil Mahto

  • Deployment Application To Weblogic Server Failed

    Hello every body
    I need your help in this problem please :
    I'm using Oracle JDeveloper 11.1 in my local machine, I Installed Weblogic Server 10.3 on the server and it's works well, I made new JDBC connection in Weblogic Server and it's works well too.
    I made new ADF Fusion web Application and I used the same connection that I used in Weblogic server and it's works well.
    I made new Application Server Connection from my local machine and It's works well with my user account.
    In my project I made new WAR deployment, Also I configured my Application properties to Bind Application to the Weblogic server Instance.
    1-when I try to deploy my project to Weblogic server I get this error message :
    Deploying Application...
    [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application test_webapp on AdminServer.: Failed to load webapp: 'test_webapp.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'test_webapp.war'
    #### Deployment incomplete. #### Feb 15, 2009 12:18:01 PM
    Deployment Failed
    2-Another application was deployed before to Weblogic server, it seems running well, whereas Weblogic Server marks my deployment health as OK, but when I try to run it for test using this URL : http://serverIP:Port/Deployment Name, I get this Error : Error 403--Forbidden
    What Should I do for both cases ?
    Thanks a lot ...

    Thanks Timo
    But first I don't use any library at my project , this is last log in Weblogic Server logfile :
    ####<Feb 16, 2009 1:56:58 PM EET> <Warning> <DeploymentService> <D2KR2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <Osama> <> <> <1234785418343> <BEA-290008> <Deployment service servlet encountered while extracting uploaded file to directory ".\servers\AdminServer\upload\test_webapp". Exception is: "invalid distance code".>
    Where D2KR2 is my Server Name
    Osama is my user in Weblogic Server
    test_webapp is the Application name
    My problem didn't solved yet, and I'm new at JDeveloper ADF.
    Where I can find clear information about deploying projects to Weblogic server.
    Thank's Agin ...
    Edited by: user8330337 on 15/02/2009 04:09 ص

  • Report to Show All Machines with ANY Deployment Failures

    I need to generate a report, daily, that displays all machines that have
    any kind of an deployment failure. This list will then be used to generate tickets for consultants in that area to check on them.
    I know I can look at specific deployments and see which machines show up as failed, but I am not seeing a report that shows all machines that have
    any kind of a failed deployment. Does one exist, or will I need to create it?

    you can try this report to list all failed deployments(only for applications but not packages).
     select
    all
    SMS_AppDeploymentAssetDetails.AppName as 'App Name',
    CASE WHEN SMS_AppDeploymentAssetDetails.AppStatusType = '1' Then 'Success'
    when SMS_AppDeploymentAssetDetails.AppStatusType = '2' Then 'In Progress'
    when SMS_AppDeploymentAssetDetails.AppStatusType = '3' Then 'Requirements Not Met'
    when SMS_AppDeploymentAssetDetails.AppStatusType = '4' Then 'Unknown'
    when SMS_AppDeploymentAssetDetails.AppStatusType = '5' Then 'Error'
    else 'Unknown'
    End as 'App Status Type',
    CASE WHEN SMS_AppDeploymentAssetDetails.ComplianceState = '1' Then 'Compliant'
    WHEN SMS_AppDeploymentAssetDetails.ComplianceState = '2' Then 'Non-Compliant'
    WHEN SMS_AppDeploymentAssetDetails.ComplianceState = '4' Then 'Error'
    WHEN SMS_AppDeploymentAssetDetails.ComplianceState = '6' Then 'Partial Compliance'
    else 'Unknown'
    End as 'Compliance State',
    CASE WHEN SMS_AppDeploymentAssetDetails.DeploymentIntent  = '1' Then 'Install'
    WHEN SMS_AppDeploymentAssetDetails.DeploymentIntent  = '2' Then 'Uninstall'
    WHEN SMS_AppDeploymentAssetDetails.DeploymentIntent  = '3' Then 'Preflight'
    else 'Unknown'
    End as 'Deployment Intent',
    SMS_AppDeploymentAssetDetails.DTName as 'Deplyoment Type Name',
    CASE WHEN SMS_AppDeploymentAssetDetails.InstalledState  = '1' Then 'Uninstall'
    WHEN SMS_AppDeploymentAssetDetails.InstalledState  = '2' Then 'Install'
    WHEN SMS_AppDeploymentAssetDetails.InstalledState  = '3' Then 'Unknown'
    else 'Unknown'
    End as 'Installed State',
    CASE WHEN SMS_AppDeploymentAssetDetails.IsMachineAssignedToUser = '1' Then 'Yes'
    Else 'No'
    End as 'Device Assigned to User?',
    SMS_AppDeploymentAssetDetails.MachineName as 'Device Name',
    CASE WHEN CHARINDEX('\',SMS_AppDeploymentAssetDetails.UserName)>0 THEN SUBSTRING
    (SMS_AppDeploymentAssetDetails.UserName,CHARINDEX('\',SMS_AppDeploymentAssetDetails.UserName)+1,255)
    ELSE SMS_AppDeploymentAssetDetails.UserName END 'User Name'
    from fn_AppDeploymentAssetDetails(1033) AS SMS_AppDeploymentAssetDetails
    where SMS_AppDeploymentAssetDetails.AppStatusType = '5'
    ORDER BY 1
    Original query posted on http://systemcenteradmin.com/?p=67
    Eswar Koneti | Configmgr blog:
    www.eskonr.com | Linkedin: Eswar Koneti
    | Twitter: Eskonr

  • Plsql webservices deploy error in weblogic.... Can anybody help me.. Urgent

    Could any body look into this exception....
    I am stuggling with this for the last one week........
    I have generated the webservices from PLSql procedure, deployed and tested in oc4j which is successfull running and I can access the webservice too.....
    The same ear file, when i deploy in to weblogic I am getting the follwing error, can anybody look in to this and help me....
    <May 20, 2006 2:09:14 PM GMT+05:30> <Error> <Deployer> <BEA-149231> <Unable to s
    et the activation state to true for the application 'gtry-gtry-WS'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "gwsSoapHttpPort" fa
    iled to preload on startup in Web application: "gtry-gtry-context-root".
    java.lang.IllegalStateException: could not find schema type named {{http}//orass
    pcon/Gws.wsdl/types/}EmpRecUser
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalTypeNod
    e.getSchemaType(AnonymousTypeFinder.java:181)
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getTypeNamed(
    AnonymousTypeFinder.java:86)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.create
    BindingTypeFrom(Deploytime109MappingHelper.java:888)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.proces
    sTypeMappings(Deploytime109MappingHelper.java:466)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBi
    ndingFileFrom109dd(Deploytime109MappingHelper.java:246)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>
    (Deploytime109MappingHelper.java:162)
    at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.create
    RuntimeBindings(RuntimeBindingsBuilderImpl.java:80)
    at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.jav
    a:272)
    at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:94)
    at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:58)
    at weblogic.wsee.server.servlet.WebappWSServlet.initRuntime(WebappWSServ
    let.java:70)
    at weblogic.wsee.server.servlet.WebappWSServlet.initImpl(WebappWSServlet
    .java:32)
    at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:40
    at javax.servlet.GenericServlet.init(GenericServlet.java:256)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
    ubSecurityHelper.java:276)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
    tyHelper.java:68)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
    ifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
    per.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
    mpl.java:493)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
    ervletContext.java:1688)
    Thanks in Advance
    Jayanthy.

    Hi Supriya,
    Check the following:
    * Whether the Report is locked in the server.
    * Are the parameters you pass from the form to report have the similar data types.
    Hope your problem is fixed.
    Regards.

  • Error while deploying composite to weblogic

    Getting following error while deploying composite to weblogic; As I got some reason from google that, its because of jdk8. If it is a known issue, does oracle released any patch for this?
    8:16:43 AM] Server is most likely down. Please check the server status and make sure it is up.
    [08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
    [08:16:43 AM] HTTP error code returned [-1]
    [08:16:43 AM] Error message from server:
    Server is most likely down. Please check the server status and make sure it is up.
    [08:16:43 AM] Check server log for more details.
    [08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
    [08:16:43 AM] Deployment cancelled.
    [08:16:43 AM] ----  Deployment incomplete  ----.
    [08:16:43 AM] Error deploying archive file:/C:/JDeveloper/mywork/e2e-1201-composites/ValidatePayment/deploy/sca_ValidatePayment_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

    Hi Priya,
    Can you check the server status.It clearly says that the server is down.Check the status of the server and also the disk space .
    [08:16:43 AM] Error message from server:
    Server is most likely down. Please check the server status and make sure it is up.

  • 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

  • While deploying application in weblogic 10.3 getting following eror

    while deploying app into weblogic 10.3 getting following taglib errors please any one cane ensure this....
    An error occurred during activation of changes, please see the log for details.
    weblogic.application.ModuleException:
    Substituted for the exception weblogic.servlet.jsp.CompilationException which lacks a String contructor, original message - footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:5:5: Invalid tag library. <%@ taglib uri="/WEB-INF/tb-tags.tld" prefix="tb"%> ^----^ connection.jsp:5:5

    Hi Pratik,
    Would suggest you to create a "*wlfullclient.jar*" by going through the below link and add it in your weblogic workshop and then try to deploy your application. Also it is always recommended that you should compile the old application again with the new JDK version your new weblogic sever is using.
    Tpoic:*Creating a wlfullclient.jar for JDK 1.6 client applications*
    http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html#wp1078098
    Hope this would help you.
    Regards,
    Ravish Mody

Maybe you are looking for