CLASSPATH not taken during deployment

I created an ejb and while deploying I get error.
Following are the steps done
- did "ejbc" of the class files and created a jar(jar A) file.
(for an jb).
- The utility classes are wrapped into another (jarB).
- The jarA is deployed in "C:\iPlanet\ias6\ias\JAR"
while jarB is in a different directory.
When the jarA is opened using the deployment tool, i get an error
"The following entries are incorrectly packaged or have external
dependencies".
When I try to deploy it the tool spits out errors saying that the
utility files in jarB could not be found.
I updated the CLASSPATH in the registry under SOFTWARE\iPlanet\6.0\Java.
and also SOFTWARE\iPlanet\6.0\CCS0\SYSTEM_JAVA\GX_CLASSPATH.
Later I restarted the server and also the machine but with no
success.
Environment
===========
ias6.0SP3
Windows2000
Am I missing something here.!!!!
Thanks in advance
Chandu

Hi,
On the Windows platform you will have to add the JAR files to the
IAS_CLASSPATH in deploytool.bat. This is one way. Another way is to open up
deploytool and go to Edit>Preferences and set the complete path for your Jar
file. Click on apply and it will include the classes in the Jar file into
its classpath.
Rgds,
Irfan.
Chandu wrote:
I created an ejb and while deploying I get error.
Following are the steps done
- did "ejbc" of the class files and created a jar(jar A) file.
(for an jb).
- The utility classes are wrapped into another (jarB).
- The jarA is deployed in "C:\iPlanet\ias6\ias\JAR"
while jarB is in a different directory.
When the jarA is opened using the deployment tool, i get an error
"The following entries are incorrectly packaged or have external
dependencies".
When I try to deploy it the tool spits out errors saying that the
utility files in jarB could not be found.
I updated the CLASSPATH in the registry under SOFTWARE\iPlanet\6.0\Java.
and also SOFTWARE\iPlanet\6.0\CCS0\SYSTEM_JAVA\GX_CLASSPATH.
Later I restarted the server and also the machine but with no
success.
Environment
===========
ias6.0SP3
Windows2000
Am I missing something here.!!!!
Thanks in advance
Chandu

Similar Messages

  • Content Selector is not loading during deployment

    Hi Alll,
    I am using weblogic portal 10.2 and MySQL 5.0.
    I have created content selector during developement using workshop.
    and deployed the same EAR in Staging server.
    But content selector is not loaded after deployment.
    I got confirmation after checking adminconsole ->> Content Selectors(Which will be displayed in home page of admin console after login)
    And i can see that , other changes ,,JSP Changes...are reflected as part of deployment.
    Please let me know what might be the poblem,for not loading content selector??
    Is there any number of restrictions on number of content selectors for an environment??
    Srinivas

    hi
    production mode does have the behavior you see, and there are good reasons why this must be so.
    You mean to say, we need to propagate Content selectors from STAGING to PRODUCTION??Yes you need to propagate from an environment which has all the data you want correctly to your production environment. You can scope the propagation to only Content Selectors (if you want, the documentation has data how you can do this) and you can run this via GUI or via ANT.
    regards
    deepak

  • DTD not available during deployment

    Hello
    We had a problem that during the deployment of our ear, some dtd's of struts where not accessible on the internet. It seems that xml files are validated, during deployment, so the application was not deployed properly.
    Is there a way to either :
    - configure the container that no validatio should be done when deploying the ear
    - put the dtd in the application itself, so we don't depend on the struts site wether we can deploy or not
    grtz
    Chris.

    The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.

  • Class not found during deployment

    I'm getting "class not found during deserialization of descriptor" during deployment of an EJB. What does this mean?

    The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.

  • ResourceAdapter not found during deployment using WL 7.0 SP2

    Hi,
              Am using WL 7.0 SP2 on Win2k w/ JDK 1.4.
              Am using the non-managed mode (wherein the admin server is also the managed-server).
              Am trying to deploy my RA. On uploading the RAR using
              the admin console, I get the following error (from the server.log):
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer Initiating a deployment task with id 8 for application bs-ra
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer preparing application bs-ra on vspl-dev-server
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer prepared application bs-ra on vspl-dev-server
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Management Configuration changes for domain saved to the repository.
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Deployer activating application bs-ra on vspl-dev-server
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info Connector Initializing connection pool for resource adapter BookStore-
              Resource Adapter_eis/BSResourceAdapter.
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error Deployer Unexpected error was encountered during the deployment proce
              ss.
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error Deployer The Slave Deployer failed to complete the deployment task wi
              th id 8 for the application bs-ra.
              java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter
                   at java.lang.Class.getMethods0(Native Method)
                   at java.lang.Class.getDeclaredMethods(Class.java:1034)
                   at java.beans.Introspector$1.run(Introspector.java:847)
                   at java.security.AccessController.doPrivileged(Native Method)
                   at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:845)
                   at java.beans.Introspector.getTargetEventInfo(Introspector.java:551)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:289)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:76)
                   at weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java:402)
                   at weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectionFactory(ConnectionPoolManager.java:64)
                   at weblogic.connector.deploy.ConnectorDeployer.activate(ConnectorDeployer.java:315)
                   at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:221)
                   at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1662)
                   at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1087)
                   at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1074)
                   at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1110)
                   at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
                   at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              --------------- nested within: ------------------
              weblogic.management.ManagementException: 149233 - with nested exception:
              [java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter]
                   at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:834)
                   at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1180)
                   at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
                   at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Warning Deployer Failures detected initiating weblogic.management.ManagementE
              xception: 149233 - with nested exception:
              [java.lang.NoClassDefFoundError: javax/resource/spi/Resource
                                                                                                  Adapter] task for application Activate application bs-ra on
              vspl-dev-server
              Jun 9, 2003 5:32:32 PM EDT vspl-dev-server Info Management Configuration changes for domain saved to the repository.
              Jun 9, 2003 5:32:36 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
              ceAdapter.
              Jun 9, 2003 5:32:39 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
              ceAdapter.
              Jun 9, 2003 5:32:47 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
              ceAdapter.
              Jun 9, 2003 5:32:48 PM EDT vspl-dev-server Error Connector ManagedConnectionFactory not found for jndiName eis/BSResour
              ceAdapter.
              There are two things I observer here.
              1. The ResourceAdapter class does not seem to be found by Weblogic. It's part of the javax.resource.spi package.
              I checked the weblogic.jar archive in the WL-HOME/server/lib folder. It does not seem to have the class. Why ?
              2. It complains about the ManagedConnectionFactory not being found. Am assuming that if the RA was deployed
              in the first place, I would not have seen this error (coz, the ManagedConnectionFactory would have been
              deployed in the previous step). Right ?
              I did observe that WL 7.0 supports only JCA 1.0. In JCA 1.0's (public) API, there is no mention of the
              javax.resource.spi.ResourceAdapter class, though the spec talks about it. ??
              Note: I had designed and implemented my RA as per JCA 1.5 (but nothing 1.5-specific, I guess).
              Any ideas ?
              thanks,
              raghu
              

    I figured it out. Darn simple.
              My ManagedConnectionFactory implementation referenced ResourceAdapter as
              it has to implement the ManagedConnnectionFactory interface of JCA 1.5.
              In JCA 1.0 (which is supported by WL 7.0 & 8.1), the ResourceAdapater
              is undefined. Hence, the classloading problem.
              Sorry for any confusion.
              raghu
              raghu h wrote:
              > Hi,
              >
              > Am using WL 7.0 SP2 on Win2k w/ JDK 1.4. Am using the non-managed mode
              > (wherein the admin server is also the managed-server).
              >
              > Am trying to deploy my RA. On uploading the RAR using
              > the admin console, I get the following error (from the server.log):
              >
              >
              >
              > -----------------------------------------------------------------------------------------------------------------
              >
              >
              > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info
              > Deployer Initiating a deployment task with id 8 for
              > application bs-ra
              > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Info
              > Deployer preparing application bs-ra on
              > vspl-dev-server Jun 9, 2003 5:32:31 PM EDT
              > vspl-dev-server Info Deployer prepared application
              > bs-ra on vspl-dev-server Jun 9, 2003 5:32:31 PM EDT
              > vspl-dev-server Info Management Configuration
              > changes for domain saved to the repository. Jun 9, 2003 5:32:31 PM
              > EDT vspl-dev-server Info Deployer activating
              > application bs-ra on vspl-dev-server Jun 9, 2003 5:32:31 PM
              > EDT vspl-dev-server Info Connector
              > Initializing connection pool for resource adapter BookStore-
              >
              > Resource Adapter_eis/BSResourceAdapter.
              >
              > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error
              > Deployer Unexpected error was encountered during the
              > deployment proce
              >
              > ss.
              >
              > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Error
              > Deployer The Slave Deployer failed to complete the deployment
              > task wi
              >
              > th id 8 for the application bs-ra.
              >
              > java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter
              > at java.lang.Class.getMethods0(Native Method)
              > at java.lang.Class.getDeclaredMethods(Class.java:1034)
              > at java.beans.Introspector$1.run(Introspector.java:847)
              > at java.security.AccessController.doPrivileged(Native Method)
              > at
              > java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:845)
              > at java.beans.Introspector.getTargetEventInfo(Introspector.java:551)
              > at java.beans.Introspector.getBeanInfo(Introspector.java:289)
              > at java.beans.Introspector.getBeanInfo(Introspector.java:76)
              > at
              > weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java:402)
              >
              > at
              > weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectionFactory(ConnectionPoolManager.java:64)
              >
              > at
              > weblogic.connector.deploy.ConnectorDeployer.activate(ConnectorDeployer.java:315)
              >
              > at
              > weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:221)
              >
              > at
              > weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1662)
              >
              > at
              > weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1087)
              >
              > at
              > weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1074)
              >
              > at
              > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1110)
              >
              > at
              > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
              >
              > at
              > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
              >
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              > --------------- nested within: ------------------
              > weblogic.management.ManagementException: 149233 - with nested exception:
              > [java.lang.NoClassDefFoundError: javax/resource/spi/ResourceAdapter]
              > at
              > weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:834)
              >
              > at
              > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1180)
              >
              > at
              > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
              >
              > at
              > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
              >
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              > Jun 9, 2003 5:32:31 PM EDT vspl-dev-server Warning
              > Deployer Failures detected initiating
              > weblogic.management.ManagementE
              >
              > xception: 149233 - with nested exception:
              >
              > [java.lang.NoClassDefFoundError: javax/resource/spi/Resource
              >                                                                                   
              > Adapter] task for application Activate application bs-ra on
              >
              > vspl-dev-server
              >
              > Jun 9, 2003 5:32:32 PM EDT vspl-dev-server Info
              > Management Configuration changes for domain saved to the
              > repository. Jun 9, 2003 5:32:36 PM EDT vspl-dev-server
              > Error Connector ManagedConnectionFactory not found for
              > jndiName eis/BSResour
              >
              > ceAdapter.
              >
              > Jun 9, 2003 5:32:39 PM EDT vspl-dev-server Error
              > Connector ManagedConnectionFactory not found for jndiName
              > eis/BSResour
              >
              > ceAdapter.
              >
              > Jun 9, 2003 5:32:47 PM EDT vspl-dev-server Error
              > Connector ManagedConnectionFactory not found for jndiName
              > eis/BSResour
              >
              > ceAdapter.
              >
              > Jun 9, 2003 5:32:48 PM EDT vspl-dev-server Error
              > Connector ManagedConnectionFactory not found for jndiName
              > eis/BSResour
              >
              > ceAdapter.
              >
              > -------------------------------------------------------------------------------------------------------------
              >
              >
              >
              > There are two things I observer here. 1. The ResourceAdapter class does
              > not seem to be found by Weblogic. It's part of the javax.resource.spi
              > package.
              > I checked the weblogic.jar archive in the WL-HOME/server/lib folder. It
              > does not seem to have the class. Why ?
              > 2. It complains about the ManagedConnectionFactory not being found. Am
              > assuming that if the RA was deployed
              > in the first place, I would not have seen this error (coz, the
              > ManagedConnectionFactory would have been
              > deployed in the previous step). Right ?
              >
              > I did observe that WL 7.0 supports only JCA 1.0. In JCA 1.0's (public)
              > API, there is no mention of the
              > javax.resource.spi.ResourceAdapter class, though the spec talks about
              > it. ??
              >
              >
              > Note: I had designed and implemented my RA as per JCA 1.5 (but nothing
              > 1.5-specific, I guess).
              >
              > Any ideas ?
              >
              > thanks,
              > raghu
              >
              >
              >
              >
              

  • Dependencies not included during deployment in JDev3.0

    At the Advanced configuration I have included
    the package name or the classes name to be included into the archive file but this
    does not seem to work.
    There is no problem when using JDev2.0.
    Is there anyone else facing this problem?

    At the Advanced configuration I have included
    the package name or the classes name to be included into the archive file but this
    does not seem to work.
    There is no problem when using JDev2.0.
    Is there anyone else facing this problem?

  • Management Point did not install during deployment

    I found the 2007 client installed on this server prior to the install. I removed the client with /uninstall... however after the installation of CM 2012 the managment point did not install. It pointed me to the mpmsi.log. Below is that log. Has anyone run
    into this issue before?
    === Verbose logging started: 2/25/2014  15:58:05  Build type: SHIP UNICODE 5.00.9600.00  Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
    MSI (c) (C4:40) [15:58:05:347]: Resetting cached policy values
    MSI (c) (C4:40) [15:58:05:347]: Machine policy value 'Debug' is 0
    MSI (c) (C4:40) [15:58:05:347]: ******* RunEngine:
               ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (C4:40) [15:58:05:348]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (C4:40) [15:58:08:348]: Failed to grab execution mutex. System error 258.
    MSI (c) (C4:40) [15:58:08:350]: Cloaking enabled.
    MSI (c) (C4:40) [15:58:08:350]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (C4:40) [15:58:08:350]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (c) (C4:40) [15:58:08:351]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (C4:40) [15:58:08:351]: MainEngineThread is returning 1618
    === Verbose logging stopped: 2/25/2014  15:58:08 ===
    MSI (s) (80:58) [15:58:11:836]: User policy value 'DisableRollback' is 0
    MSI (s) (80:58) [15:58:11:836]: Machine policy value 'DisableRollback' is 0
    MSI (s) (80:58) [15:58:11:837]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (80:58) [15:58:11:837]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (80:58) [15:58:11:844]: Note: 1: 2265 2:  3: -2147287035
    MSI (s) (80:58) [15:58:11:860]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (80:58) [15:58:11:867]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (80:58) [15:58:11:881]: Destroying RemoteAPI object.
    MSI (s) (80:60) [15:58:11:889]: Custom Action Manager thread ending.

    MSI (c) (C4:40) [15:58:08:348]: Failed to grab execution mutex. System error 258.
    This normally means there is another install process in progress. So please restart the computer and try again. If no avail, check whether there is a process name msiexec running.
    Juke Chou
    TechNet Community Support

  • Zero values not taken into account during retraction

    Hello,
    we are having an issue with data retraction.
    When we reset a value to zero, the change in the value is not taken into account and the corresponding value in R/3 remains unchanged.
    There are some posts that say that the function modules UPR_COST_PLAN_EXEC and UPR_COST_PLAN_INIT should be modified in order to populate <xth_data> with zero values, but debug mode shows that the data are read before calling these functions, and the zero values are
    already ignored at this stage.
    Could anyone help me, please?
    Thank you in advance!

    Here is the second method  -
    Regarding your issue:
    Retraction is based on the records of the SEM buffer. Zero records are
    in general filtered in the buffer, so that they cannot be considered forplanning functions that execute the retraction. I regret but this is
    the normal system behaviour in the standard. As workaround, please use adummy key figure that is set to a value <> 0.
    The only way is a work around. If you fill a dummy key figure with an
    arbitrary value, the frame work recognizes this as not 0, even if the
    proper key figure is 0. In that case the 0 retraction would work. So if
    not existing, create an additional dummy key figure to the cube and workon as described.
    For all the of retractions (CO-OM, IM, PS) BPS planning functions are
    used and they run in the general BPS framework. This framework is
    designed to explicitly not process zero records because of performance
    reasons.
    If zero records would be processed, planning functions would run longer
    but they can't deal with those records anyway. Therefore the developmentdecided on the current design, to delete all zero records first, before
    processing them with a planning function. This decision has been
    discussed several times before and it not likely to be changed.
    Regarding SAP note you can check the work aroud I explained can be foundin the oss note 768822 SEM-BPS: Retraction of WBS element w/ Pushback.
    I hope this explains the reason.
    Please kindly confirm the message if your issue is answered.
    Thanks for your support and cooperation.

  • WebLogic 11g: Weblogic-Application-Version not taken into account

    Hello,
    I'm trying to set up Production Redeployment on my EAR, under WebLogic 10.3.6.
    However, I can't figure out how to make Weblogic-Application-Version work in MANIFEST.MF
    Here is my EAR structure:
    MyApplication
    --- APP-INF
    --- --- lib
    --- --- classes
    --- META-INF
    --- --- application.xml
    --- --- weblogic-application.xml
    --- --- MANIFEST.MF <- file I update
    --- WebApp1
    --- --- META-INF
    --- --- --- MANIFEST.MF
    --- --- WEB-INF
    --- --- --- classes
    --- --- --- lib
    --- --- --- web.xml
    --- --- --- weblogic.xml
    --- WebApp2
    --- --- same as WebApp1
    MANIFEST.MF content is the following:
    Manifest-Version: 1.0
    Weblogic-Application-Version: VERSION_1
    The problem is that it's not taken into account when I deploy the application in the WebLogic console.
    When I use staged mode, the line Weblogic-Application-Version: VERSION_1 is removed from the staged MANIFEST.MF file.
    The only way to manage to version my application is to add the flag -appversion to weblogic.Deployer, but I don't want to use that on a Production environment (and it's not recommended in the documentation!).
    Any idea why Weblogic-Application-Version not taken into account? I tried to add debug mode to node weblogic/debug but with no success.
    Thanks by advance,
    Julien

    I tested it at my end and was able to redeploy it successfully with the application versions.
    Are you saying that by deploying through weblogic console,the archive version is not honoring/getting picked up .is that correct?
    if yes, what does your weblogic console shows for archive version,when you first try to deploy your application with the VERSION_1.
    I mean,when you are on the "Optional Settings" Page.Do you see the Archive Version as VERSION_1?
    Deployments >> Click on the Install >> select your application ( MyAPP)>> Install this deployment as an application >> Select deployment targets >> Optional Settngs
    Example from the Optional settings Page for My application
    What do you want to name this deployment?
    Name: MyAPP     
    Archive Version:     
    VERSION_1
    This can confirm that the application being deployed is versioned one and if it doesn't shows up,then you need to check why its not getting picked up.?
    Moreover,You can enable the "deploy" debug flag to see whats going wrong in your case during the deployment process
    Server > Debug > Weblogic > Deploy
    Do refer the below viewlet on the Production Redeployment
    http://download.oracle.com/otn_hosted_doc/wls/redeployment/wls-side-by-side-non-annotation_viewlet_swf.html

  • ConfigureListener contextInitialized Critical error during deployment:  com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver

    Hi Techies,
    I am facing small problem with deployment thru cosole deployment.. details below.I am using Jdeveloper 11.1.2.1.0 ver.
    I am able to deploy the application thru Jdeveloper Run/Debug Option. But If i create an EAR file and deploying thru server console , then i am getting below error. hence its not deploed.
    .Till yesterday it was working ..Just to day i am facing this issue.What can be the reasons for this ?
    Can anyone help me plz..
    ---------------------- Error Message on log---------------------------------------------------------------------------------
    <ConfigureListener> <contextInitialized> Critical error during deployment:
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
      at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
      at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
      at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
      at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
      at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
      at com.sun.faces.util.Util.loadClass(Util.java:291)
      at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
      at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
      at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
      at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
      at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
      at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
      at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
      at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
      at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
      ... 38 more
    <Jul 25, 2013 8:50:54 PM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver.
    java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
      at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:294)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
      Truncated. see log file for complete stacktrace
    Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
      at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
      at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      Truncated. see log file for complete stacktrace
    >
    <ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
    java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
      at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
      at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
      at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:108)
      at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:327)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
      at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
      at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
      at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
      at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
      at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
      at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
      at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
      at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
      at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
      at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
      at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
      at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
      at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
      at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
      at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
      at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1374785326461' for task '2'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      Truncated. see log file for complete stacktrace
    >
    <Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'EmersonMMI_QACerts'.>
    <Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'EmersonMMI_QACerts'.>
    <Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      Truncated. see log file for complete stacktrace
    >
    <Jul 25, 2013 8:50:55 PM GMT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
      at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
      at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
      at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
      at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
      at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
      at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
      at com.sun.faces.util.Util.loadClass(Util.java:291)
      at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
      at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
      at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
      at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
      at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
      at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
      at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
      at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
      at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
      at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)..
    [03:58:26 AM] Deployment cancelled.
    [03:58:26 AM] ----  Deployment incomplete  ----.
    [03:58:26 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Thanks,
    Rajesh

    java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
    Add the jsf-api.jar to the runtime classpath of the server.

  • Fatal error during deployment!

    I'm getting the following error message whenever I try to deploy my (server-side)
    app:
    Internal VM (14:41:29): Fatal error during deployment! Deployment failed
    Any ideas on how to resolve this?

    Seems like problem in setup in Visual Cafe. See the message
    Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
    does not exist
    Can you try other tools for deployment like ant task wldeploy or directly using
    command line Weblogic.Deployer?
    "Fred Bloggs" <[email protected]> wrote:
    >
    I click the "Project" menu item, then "Build Application". No problem
    doing that,
    then I click "Project" again, then "Deploy". The attempt to deploy fails:
    VisualCafe (09:45:40): wjc -sysclasspath C:\WebGain\VCafe\bin\..\JDK13\JRE\LIB\RT.JAR;C:\WebGain\VCafe\bin\..\JDK13\LIB\TOOLS.JAR
    -g -O -d C:\WebGain\VCafe\Projects\ -classpath
    VisualCafe (09:45:40): S:\general\superjar\superjar.jar;C:\WebGain\VCafe\Projects\;C:\WebGain\VCafe\jdk13\jre\lib\rt.jar;C:\WebGain\VCafe\jdk13\lib\tools.jar;C:\WebGain\VCafe\jdk13\lib\dt.jar;C:\WebGain\VCafe\jdk13\jre\lib\i
    VisualCafe (09:45:40): 18n.jar;C:\WebGain\VCafe\JAVA\LIB\;C:\WebGain\VCafe\JAVA\LIB\SYMCLASS.ZIP;C:\WebGain\VCafe\JAVA\LIB\CLASSES.ZIP;C:\WebGain\VCafe\swing-1.1\SWINGALL.JAR;C:\WebGain\VCafe\bin\xutil.ZIP;C:\WebGain\VCafe\b
    VisualCafe (09:45:40): in\components\sfc.jar;C:\WebGain\VCafe\bin\components\symbeans.jar;C:\WebGain\VCafe\java\lib\eradtools.jar;C:\WebGain\VCafe\java\lib\eradpublic.jar;C:\WebGain\VCafe\java\lib\dbaw.zip;C:\WebGain\VCafe\b
    VisualCafe (09:45:40): in\components\dbaw_awt.jar;C:\WebGain\VCafe\bin\components\databind.jar;C:\WebGain\VCafe\java\lib\collections.zip;C:\WebGain\VCafe\java\lib\icebrowserbean.jar;C:\WebGain\VCafe\java\lib\servlet.jar;C:\W
    VisualCafe (09:45:40): ebGain\VCafe\java\lib\webserver.jar;C:\WebGain\VCafe\java\lib\jspengine.jar;C:\WebGain\VCafe\java\lib\symtools.jar;C:\WebGain\VCafe\bin\components\deploy.jar;C:\WebGain\VCafe\bin\components\templates.j
    VisualCafe (09:45:40): ar;C:\WebGain\VCafe\bin\components\vcservlet.jar;C:\WebGain\VCafe\bin\components\vcjsp.jar;C:\WebGain\VCafe\bin\components\flexlm.zip;C:\WebGain\VCafe\bin\components\vcejbwl.jar;C:\WebGain\VCafe\java\l
    VisualCafe (09:45:40): ib\javax_ejb.zip;C:\WebGain\VCafe\java\lib\jndi.jar;C:\WebGain\VCafe\java\lib\jts.zip;C:\WebGain\VCafe\java\lib\jdbc2_0-stdext.jar;C:\WebGain\VCafe\bin\sb\;C:\WebGain\VCafe\bin\sb\classes\sb.jar;C:\Web
    VisualCafe (09:45:40): Gain\VCafe\bin\components\wqaplugin.jar;C:\WebGain\QAnalyzer\lib\mrt.jar;C:\WebGain\QAnalyzer\lib\metamata.jar;C:\WebGain\VCafe\bin\components\TurboXMLPlugin.jar;C:\WebGain\VCafe\bin\components\Dreamwe
    VisualCafe (09:45:40): averPlugin.jar;c:\jaxp-1.2_01\dom.jar;c:\jaxp-1.2_01\jaxp-api.jar;c:\jaxp-1.2_01\sax.jar;c:\jaxp-1.2_01\xalan.jar;c:\jaxp-1.2_01\xercesImpl.jar;c:\jaxp-1.2_01\xsltc.jar;c:\WebGain\bea\wlserver6.1sp1\sa
    VisualCafe (09:45:40): mples\eval\cloudscape\lib\cloudscape.jar -make
    -cdb incidentAlertPrj.cdb
    C:\WebGain\VCafe\Projects\incidentAlert.java C:\WebGain\VCafe\Projects\appRoles.java
    VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\abstractAlertSDFBean.java
    C:\WebGain\VCafe\Projects\sdfTextBean.java
    C:\WebGain\VCafe\Projects\alertXMLBean.java C:\WebGain\VCafe\Projects\alertSDFBeanFactory.java
    VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\nullAlertSDFBean.java
    VisualCafe (09:45:40): Warning 61: Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
    does not exist
    VisualCafe (09:45:40): Build Successful
    Internal VM (09:45:46): Starting deployment to WebLogic Server 6.1 ...
    Internal VM (09:46:07): Building deployment descriptor...Building generic
    WAR
    file...
    Internal VM (09:46:07): Fatal error during deployment! Deployment failed
    Rob Woollen <[email protected]> wrote:
    I think we'll need some more info. That doesn't look like a WLS error
    message.
    Can you show us your logs, stdout etc?
    How are you deploying the app?
    -- Rob

  • ClassCastException during deployment with more than one used entity

    Hi,
    i am still trying to get into NW development and got one more time stuck. I have a CE 7.1 SR5 project containing a dictionary, a bean module, an EAR project and a web dynpro project.
    With the following two classes everything runs fine:
    [AT]Entity
    [AT]Table(name="TMP_USER")
    [AT]NamedQueries(value={[AT]NamedQuery(name="doLogin", query="SELECT u FROM User u WHERE u.login = :login AND u.password = :password")})
    public class User implements Serializable {
         [AT]Id
         private int id;
         private String login;
         private String password;
         private static final long serialVersionUID = 1L;
         public User() {
              super();
    // Omitted Accessors
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
    build, deploy, run in webservice navigator -> ok
    Then i created a new entity:
    [AT]Entity
    [AT]Table(name="TMP_PROJECT")
    [AT]NamedQueries(value={[AT]NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         [AT]Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
      Omitted Accessors
    build, deploy, run in webservice navigator -> no problem.
    Then i changed  the UserSessionBean to:
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
         public Projecet testfunc()
              return null;
    And now during deployment there is an warning (in reality it´s an exception) and the bean does not work any more.
    The exception is
              1. Exception has been returned while the 'testproject.testcorp.de/testprojectear' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7707450:com.sap.engine.services.deploy.container.DeploymentException:
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:693)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to generate serialization framework for web service UserSessionBeanService, application testproject.testcorp.de/testprojectear.
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:360)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:688)
         ... 37 more
    Caused by: java.lang.ClassCastException: class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive
         at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:58)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
         at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
         at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsSchemaGenerator.genJaxbMappings(JaxWsSchemaGenerator.java:274)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsIMappingGenerator.generateWSDL(JaxWsIMappingGenerator.java:103)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:286)
         ... 41 more
    I already downgraded my Java JRE/JDK to 1.5.0_15 as it was hinted here in the forum, but the problem persists. Any idea what is wrong?

    Thanks for the answer, but i am not using this wizard. Some how this project class must be flawed.
    public User testfunc()
    return null;
    works, but changing to
    public Project testfunc()
    return null;
    immediately leads to the above deployment error.
    This is the offending class, it compiles without warning
    package de.testcorp.testproject.beans;
    import java.io.Serializable;
    import java.sql.Timestamp;
    import javax.persistence.*;
    @Entity
    @Table(name="TMP_PROJECT")
    @NamedQueries(value={@NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         @Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
         public int getId() {
              return this.id;
         public void setId(int id) {
              this.id = id;
         public int getOwnerid() {
              return this.ownerid;
         public void setOwnerid(int ownerid) {
              this.ownerid = ownerid;
         public String getName() {
              return this.name;
         public void setName(String name) {
              this.name = name;
         public Timestamp getCreationtime() {
              return this.creationtime;
         public void setCreationtime(Timestamp creationtime) {
              this.creationtime = creationtime;
         public String getDescription() {
              return this.description;
         public void setDescription(String description) {
              this.description = description;
         public int getNumber() {
              return this.number;
         public void setNumber(int number) {
              this.number = number;
         public short getSubnumber() {
              return this.subnumber;
         public void setSubnumber(short subnumber) {
              this.subnumber = subnumber;

  • Error during deployment of Message Driven Bean

    Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              I am getting some error (or perhaps warning) during deployment of Message
              Driven Bean. Any one seen this before?
              This error only comes on a machine with Dual Network card.
              Thanks.
              ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
              <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
              enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
              Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
              is of a non-final version of the appropriate specification. It is subject to
              change in future releases once the specification becomes finalized. This may
              cause application code developed for BEA WebLogic Server 6.1 that uses the
              new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              supported in future releases of BEA WebLogic Server.>
              ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              container will automatically attempt to re-establish the connection with the
              JMS server. This warning may occur during WebLogic Cluster start-up if the
              JMS destination is located on another server. When the JMS server connection
              is re-established, the Message-Driven EJB will again receive JMS messages.
              The Error was:
              Unable to create a JNDI InitialContext to lookup the JMS destination. The
              error was:
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router
              to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:307)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:211)
              at
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              ory.java:149)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              rivenBeanInfoImpl.java:641)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              nPoller.java:474)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              .java:418)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              nectionPoller.java:286)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              foImpl.java:511)
              at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              at weblogic.j2ee.Application.addComponent(Application.java:170)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:360)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:285)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:239)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy34.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2977)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:372)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy49.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010009> <EJB Deployed EJB with JNDI name
              ASYNCMessageDrivenBean.>
              

    Hi Tom
              Yes we do have an URL provided in the descriptor. It's
              t3://jms.server.net:7001.
              and the jms.server.net is resolved via a hosts file in Win2K
              eg,
              192.168.100.200 jms.server.net
              You are right in saying that the loopback in a dual-net card is a problem.
              But our solution
              above solves the issue as long as your host file does not use 127.0.0.1 as
              the IP.
              We need the URL b/c depending on our client's deployment , the JMS Server
              may be remote or may be local.
              "Tom Barnes" <[email protected]> wrote in message
              news:[email protected]...
              > Hi x,
              >
              > Something to do with the loopback and dual-network cards is
              > messin' with WLS' mind. I do not know what the problem is,
              > but I can guess:
              >
              > You have specified an URL in the MDB descriptor when there
              > is no need for one. If t3://127.0.0.1:7001 is in the same
              > cluster the MDB is running in (I suspect this URL is
              > actually the same WL server), then don't specify the URL.
              > This URL is only useful for connecting an MDB to a JMS
              > server that is outside local server and outside the cluster.
              > The URL may be working on single-network card systems
              > as perhaps then WL has enough info to guess that you
              > actually mean the local WL server, and simply converts
              > the context to a local context.
              >
              > Note that the URL option in the MDB descriptor is actually
              > a WebLogic extension of J2EE.
              >
              > Tom
              >
              >
              >
              > x wrote:
              > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              > >
              > > I am getting some error (or perhaps warning) during deployment of
              Message
              > > Driven Bean. Any one seen this before?
              > > This error only comes on a machine with Dual Network card.
              > >
              > > Thanks.
              > >
              > >
              > >
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
              features
              > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
              1.2,
              > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
              6.1
              > > is of a non-final version of the appropriate specification. It is
              subject to
              > > change in future releases once the specification becomes finalized. This
              may
              > > cause application code developed for BEA WebLogic Server 6.1 that uses
              the
              > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              > > supported in future releases of BEA WebLogic Server.>
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              > > container will automatically attempt to re-establish the connection with
              the
              > > JMS server. This warning may occur during WebLogic Cluster start-up if
              the
              > > JMS destination is located on another server. When the JMS server
              connection
              > > is re-established, the Message-Driven EJB will again receive JMS
              messages.
              > > The Error was:
              > > Unable to create a JNDI InitialContext to lookup the JMS destination.
              The
              > > error was:
              > > javax.naming.CommunicationException. Root exception is
              > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              > > nested exception is:
              > > java.net.ConnectException: Connection refused: connect; No available
              router
              > > to destination
              > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > at
              javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              > > at
              javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > > at javax.naming.InitialContext.init(InitialContext.java:217)
              > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              > > rivenBeanInfoImpl.java:641)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              > > nPoller.java:474)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              > > .java:418)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              > > nectionPoller.java:286)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              > > foImpl.java:511)
              > > at
              weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              > > at weblogic.j2ee.Application.addComponent(Application.java:170)
              > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              > > arget.java:360)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              > > Target.java:285)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              > > eploymentTarget.java:239)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              > > entTarget.java:199)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy34.updateDeployments(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              > > ServerMBean_CachingStub.java:2977)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              > > icationManager.java:372)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              > > r.java:160)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy49.start(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              > > ApplicationManagerMBean_CachingStub.java:480)
              > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > > at weblogic.management.Admin.finish(Admin.java:644)
              > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > > at weblogic.Server.main(Server.java:35)
              > >
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010009> <EJB Deployed EJB with JNDI name
              > > ASYNCMessageDrivenBean.>
              > >
              > >
              >
              

  • Precompiled JSP not taken in account by Weblogic 10.3.1

    Hi
    My JSPs are properly precompiled in my ear, and well taken in account by weblogic when I work with my local environment. But if I upload my ear on the Unix server, they're not taken in account anymore. Weblogic compiles them in real time, that causes a display time really long for each page.
    The precompiled JSP are present in the folder WEB-INF/classes/jsp_servlet/_jsp , inside the file app-web.war, itself included in the ear.
    Once the ear is deployed on the server, I find my precompiled JSP at 2 places :
    - <domain>/servers/<server>/tmp/_WL_user/<ear_name>/rdi76c/war/WEB-INF/lib/_wl_cls_gen.jar
    then in jsp_servlet/_jsp
    - <domain>/servers/<server>/tmp/_WL_user/<ear_name>/m8l8j8/app-web.war
    then in WEB-INF\classes\jsp_servlet\_jsp\
    At the execution time, Weblogic should be able to find the precompiled JSP at that 2 places. However, it recompiles the JSPs and places them here :
    - <domain>/servers/<server>/tmp/_WL_user/<ear_name>/rdi76c/jsp_servlet/_jsp
    I have already checked the dates. The dates written in the generated .java files match the system dates of the corresponding JSP files. It could have been an explanation, but it's not.
    Do you have any idea ?

    but encounter version mismatching error... It indicated that it only support 10.3.0... It's hard to tell based on your description, but I am going to guess that you are not selecting the right version of WLS runtime in the new runtime wizard. WLS 10.3.1 is also known as WLS 11gR1. Make sure that you look for it in Oracle rather than BEA category.
    - Konstantin

  • Not able to deploy application on NWDS 7.20

    Hi All,
    I am trying to deploy one simple application in NWDS 7.20 but getting below error.
    Note - i am on the same patch level in NWDS and Server.
    Status ERROR
    Plugin : com.sap.ide.tools.services
    code=0
    Deployment problems
    children=[
    Status ERROR
    Plugin : com.sap.ide.tools.services
    code=0
    Deploy Exception.
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [demo.sap.com_dc_my_name_age].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
    at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:178)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:92)
    at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:236)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Nested exceptions :com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [demo.sap.com_dc_my_name_age].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:244)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:134)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Error while deploying ear file /usr/sap/BPD/J03/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/135/demo.sap.com~dc_my_name_age.sda; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: TxException
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4443)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:353)
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.deploy.container.DeploymentException: TxException
    atcom.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
    atcom.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
    atcom.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
    atcom.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
    atcom.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:297)
    atcom.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
    atcom.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
    atcom.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2238)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:401)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:351)
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
         at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:587)
         at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
         at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
         at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:297)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2238)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:401)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:351)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
         at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:116)
         at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
         at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:518)
         at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1026)
         at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:317)
         at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:576)
         ... 24 more
    Posting in 2 chunks as only allowed till 15000..
    Please help i am stuck up here.
    Thanks
    Vidhi

    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
         at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:742)
         at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:192)
         at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:79)
         at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:114)
         ... 29 more
    Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
         at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:693)
         at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:492)
         at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:1137)
         at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.runStdDeploy(DeployControllerImpl.java:715)
         at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.run(DeployControllerImpl.java:528)
         at com.sap.glx.core.kernel.RuntimeManager.requestRuntimeMode(RuntimeManager.java:980)
         at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.execute(DeployControllerImpl.java:475)
         at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:442)
         at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:78)
         at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2548)
         at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1522)
         at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:335)
         at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:257)
         at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:247)
         at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
         ... 22 more
    Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 168d02d395f1e53d53fdae504c728a34 using configuration mode DEPLOYMENT
         at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:671)
         ... 36 more
    Caused by: java.lang.IllegalArgumentException: No enum const class com.sap.glx.mapping.definition.api.rule.Literal$Type.EMPTY
         at java.lang.Enum.valueOf(Enum.java:196)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackStepLiteral(Transporter.java:1512)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackStep(Transporter.java:1452)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackExpression(Transporter.java:1100)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackPart(Transporter.java:1329)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackPart(Transporter.java:1351)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker.unpackMapping(Transporter.java:1303)
         at com.sap.glx.mapping.definition.implementation.Transporter$BaseConverter$BaseUnpacker$MappingUnpacker.<init>(Transporter.java:610)
         at com.sap.glx.mapping.definition.implementation.Transporter.unpackMapping(Transporter.java:1859)
         at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$MapperTemplate$ImplementedConfigurationHandler.configure(Transformer.java:3041)
         at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$MapperTemplateHandler.configure(Transformer.java:3264)
         at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3408)
         at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:668)
         ... 36 more
    atcom.sap.engine.services.ts.transaction.TxRollbackException.writeReplace(TxRollbackException.java:163)
    atsun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    atjava.lang.reflect.Method.invoke(Method.java:597)
    atjava.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1032)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1107)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
    atcom.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
    atsun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    atjava.lang.reflect.Method.invoke(Method.java:597)
    atjava.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
    atcom.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
    atsun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    atjava.lang.reflect.Method.invoke(Method.java:597)
    atjava.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
    atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
    atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
    atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
    atjava.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
    atcom.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:138)
    atcom.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:460)
    atcom.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
    atcom.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
    atcom.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
    atcom.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
    atcom.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
    atcom.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Maybe you are looking for

  • J2ee tutorial bookstore2 example

    Hi, I'm having difficulty getting the bookstore2 example to run. In my web browser I get the following message The requested resource (/bookstore2/bookstore) is not available. The server.log file contains this message Couldn't create bookstore databa

  • Can"t get my system to work with smart board notebook.  What's wrong?  it worked before I upgraded.

    Before I upgraded my system worked with smart board notebook.  Now it does not.  Can someone tell me how to get the two working together/

  • MBP takes up to 2 minutes to sleep

    My MBP usually only needs 5 seconds to go to sleep mode when I choose the "Sleep" option, but all of a sudden it's been taking up to 2 minutes for it to go to sleep. Why could this be? Thanks

  • Service Accounts in Sharepoint 2013

    Ok in SharePoint 2013, we have an intranet set up. Ok so on the central administration page, under Security, and configure service accounts, I selected Farm Account for the drop down menu at the top. We have 3 managed accounts for the intranet, which

  • Compiling errors under LabVIEW FPGA v1.1

    Problems compiling any designs to target PXI-7831R. Compile Server v1.1 starts but fails after 5 seconds. Details window reports "#SERVER ERROR:  Error while Compiling #" I have checked the configuration and it points to the correct directories. I ha