Ear deploy failure with webservice in weblogic 9.2 build from weblogic 8.1

I get the below exception when I try to deploy the ear file that contains the webservice modules in weblogic 9.2. The ear was working fine in weblogic 8.1 which is build from this version. As part of migrating to the 9.2 I tried to deploy the ear that is build from 8.1. I am struct at this point. Pls help.
####<17-Dec-2008 21:03:35 o'clock GMT> <Error> <Deployer> <LDNCTIWA046436> <BatchServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1229547815831> <BEA-149205> <Failed to initialize the application 'exwebservices' due to error java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean.
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:355)
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:294)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:262)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:161)
     at weblogic.ejb.container.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1415)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:326)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Thanks David and weblogicRocks..
David,
I have installed the workshop also during installation. Actually I have searched for the class which is missing from the weblogic 9.2 installation folder. The missing class is is in different package path in weblogic 9.2 (knex81.jar) as shown below. Also, this class is generated by workshop while building in 8.1. So, I think I have to rebuild the work file in 9.2 to avoid referring to this class.
Missing Class location (weblogic 8.1) (knex.jar): com/bea/wlw/runtime/core/bean/SLSBContainerBean
Missing Class location (weblogic 9.2) (knex81.jar): com/bea/wlw/knex/runtime/core/bean/SLSBContainerBean
weblogicRocks,
I saw in the weblogic site that the webservices built from 8.1 will still work in 9.2 with out the need for changing the code. Pls, let me know whether I need to rebuild them on 9.2. If yes, I have used .jws files(sample class definition below) for my webservices and I came to know that in 9.2 new jws annotations are added, do I need to change my source code to add any new annotations so as to work in 9.2? Also, I have used wlwBuildTask using Ant to build the code in 8.1 and this task is not available in 9.2. Let me know what all I need to change for webservices created from workshop to migrate to 9.2. I am really struggling in resolving the issues as it is very urgent for me. Appreciate you quick response.
Below is my .jws webserice class definition.
public class MyWebService implements com.bea.jws.WebService
private String reqImpl;
* @common:operation
* @jws:conversation phase="none"
public String submitRequest(String var)
<Method Logic>
}

Similar Messages

  • EAR Deployment Problem with weblogic 10.2. Need help.

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

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

  • Problem to deploy to a WebService interface for ADF Business Components to Weblogic Server

    Hi,
      I'm trying to deploy a custom application ,in which i have exposed ADF Business Components through a WebService interface, to a standalone weblogic server.
    Application Module is configured with a Service Interface for ordinary ViewObjects.
    Now I want to create a EAR file of this application to deploy it on the weblogic server.
    But I got an error while deploying it.The error i am getting is shown below.
    ERROR: No Java EE modules detected in EAR archive. Deployment aborted. == (oracle.jdevimpl.deploy.ear.WeblogicAssembler)
    I have followed the steps mention in the below link :
    http://technology.amis.nl/2010/12/29/quickly-creating-reploying-and-testing-a-webservice-interface-for-adf-business-components/
    I'm using Jdeveloper 11.1.2.4 on windows.
    Please suggest what i could be doing wrong.
    Regards,
    Himanshu

    Does the deployment profile include Java EE modules?
    Refer
    Java EE Developer: ERROR: No j2ee modules detected in EAR archive. Deployment aborted. == (oracle.jdeveloper.deploy.Veto…

  • Portlet ear deployment fails with 9iAS/JDeveloper

    Hi.
    My portlet deployment fails, when I deploy
    the portlet-ear (generated with java portlet wizard).
    The connection to 9iAS works fine with the test.
    I just get this error:
    Executing command redeploy /oradata/oracle portlets_ear.ear portlets_ear OC4J_Portal
    ... <snip>
    Command was successfully sent to Oc4jDcmServlet
    ... <snip>
    Command has finished
    Receiving command exit value
    Receiving command output
    **** No output was received from command
    Closing connection to Oc4jDcmServlet
    #### DCM command did not complete successfully (-1)
    #### HTTP return code was -1
    The deployment also fails, when i try to do it trough oem. It just shows empty page after step 2 (select application).
    em-application.log shows this:
    7/23/03 5:57 PM emd: java.lang.NullPointerException
    at java.util.Hashtable.put(Hashtable.java:380)
    at oracle.cabo.ui.data.DictionaryData.put(Unknown Source)
    at oracle.sysman.eml.ias.oc4j.DeployWiz.displayDataBindingException(DeployWiz.java:2249)
    at oracle.sysman.eml.ias.oc4j.DeployWiz.getWebModulesURLMapping(DeployWiz.java:645)
    at java.lang.reflect.Method.invoke(Native Method)
    at oracle.cabo.ui.data.provider.MethodDataProvider.getDataObject(Unknown Source)
    If anyone has experienced something similar and fixed it, could you please give me some advice.
    Thanks in advance,
    Toni

    Hi again.
    Yes, the properties files and provider.xml files exist,
    and they are not corrupted (atleast I don't see any relevant differences).
    I installed the OC4J with the help of these files:
    * http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-install-note.html
    * http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/jpdk/v2/installing.pdkjava.v2.html
    * http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/SOLUTIONS/installing.integration.v2.html#deployingUsingOc4j
    If there's a known bugs with these, could you let me know?
    Here are the contents:
    _default.properties:
    serviceClass=oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter
    loaderClass=oracle.portal.provider.v2.http.DefaultProviderLoader
    showTestPage=true
    definition=providers/jsp_test_provider/provider.xml
    autoReload=true
    jsp_test_provider.properties: (My main provider)
    serviceClass=oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter
    loaderClass=oracle.portal.provider.v2.http.DefaultProviderLoader
    showTestPage=true
    definition=providers/jsp_test_provider/provider.xml
    autoReload=true
    provider.xml:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <?providerDefinition version="3.1"?>
    <provider class="oracle.portal.provider.v2.DefaultProviderDefinition">
    <session>true</session>
    <passAllUrlParams>false</passAllUrlParams>
    <portlet class="oracle.portal.provider.v2.DefaultPortletDefinition">
    <id>1</id>
    <name>MyPortlet</name>
    <title>My Portlet</title>
    <description>My Portlet Description</description>
    <timeout>40</timeout>
    <showEditToPublic>false</showEditToPublic>
    <hasAbout>false</hasAbout>
    <showEdit>false</showEdit>
    <hasHelp>false</hasHelp>
    <showEditDefault>false</showEditDefault>
    <showDetails>false</showDetails>
    <renderer class="oracle.portal.provider.v2.render.RenderManager">
    <renderContainer>true</renderContainer>
    <renderCustomize>true</renderCustomize>
    <autoRedirect>true</autoRedirect>
    <contentType>text/html</contentType>
    <showPage>/htdocs/myportlet/MyPortletShowPage.jsp</showPage>
    </renderer>
    </portlet>
    </provider>

  • Deploying ejb with webservice annotation problem

    I have the following code:
    HelloInf.java:
    package com.bekijkhet;
    import java.rmi.Remote;
    import java.rmi.RemoteException;
    import javax.jws.WebService;
    @WebService
    public interface HelloInf extends java.rmi.Remote {
    java.lang.String sayHello()
    throws java.rmi.RemoteException;
    Hello.java:
    package com.bekijkhet;
    import javax.ejb.Remote;
    @Remote
    public interface Hello {
    public String sayHello();
    public String sayHelloRemote();
    HelloLocal.java:
    package com.bekijkhet;
    import javax.ejb.Local;
    @Local
    public interface HelloLocal {
    public String sayHello();
    public String sayHelloLocal();
    HelloBean.java:
    package com.bekijkhet;
    import javax.ejb.Stateless;
    @Stateless
    public class HelloBean implements Hello,HelloLocal,HelloInf {
    public String sayHello() {
    return "Hello World!!!!";
    public String sayHelloLocal() {
    return "Hello Local World!!!!";
    public String sayHelloRemote() {
    return "Hello Remote World!!!!";
    When I compile these, add them to a jar and try to deploy them to a standalone oc4j 11g container I don't see the Webservice. I do see the EJB. Why isn't the webservice annotation picked up?
    BTW: I use jdk 6 u03.
    Mvg Andre Broers

    Hi,
    since there is no enterpise manager in OC4J 11 I am wondering how you verifying the non existence of the WebService. Just asking because I need a clue how to verify this issue.
    Frank

  • MDT 2012 UNC Deployment Failure with static IP.

    I am having trouble getting my UNC deployment to run the State Restore phase. I am operating on a network without DHCP and have successfully connected to the network share and ran the Task Sequence. After the reboot, however, the static ip doesn't get set
    and the deployment can't continue.
    Upon inspection of the BDD.log I ran across the entry in the State Restore section that pertains to setting the static ip.
    WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147217405 Unknown Error: -2147217405
    If I log in and run the LiteTouch.wsf file as an administrator, the task sequence starts running again and the static ip gets applied.
    Why is this not happening automatically?

    The account I'm using does have permissions. I use the same account to join manually after the process is complete. I'm not sure what the purpose of the Temp Account is. I only see it if the process fails. Otherwise, if the process completes, it is not there
    when I log in. The Administrator account is disabled by Group Policy but since it never joins the Domain, the Administrator account doesn't get disabled.
    There is no ZTIDomainJoin.log
    NetSetup.log is as follows:
    NetpDomainJoin
    NetpMachineValidToJoin
        OS Version: 6.1
        Build Number: 7601 (7601.win7sp1_ldr.130828-1532)
        ServicePack: Service Pack 1
        SKU: Windows 7 Enterprise
    NetpGetLsaPrimaryDomain: status: 0x0
    NetpMachineValidToJoin: status: 0x0
    NetpJoinWorkgroup: joining computer 'MININT-TBQSA02' to workgroup 'WORKGROUP'
    NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
    NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE ] returned 0x0
    NetpValidateName: name 'WORKGROUP' is valid for type 2
    NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
    NetpJoinWorkgroup: status: 0x0
    NetpDoDomainJoin: status: 0x0
    Now I realize that it appears to be joining the "Workgroup" Workgroup, but in my customsettings.ini I have the JoinDomain variable set to the proper domain.

  • Failure with cloning database structure and then restore from source db

    Hello, dear experts!
    I am trying to duplicate a database.
    First step was to use the DBCA to create a template. Because there is no downtime possible, I only created a template of the structure without user schema and without objects.
    At another destination I used this template to create a new database "CLON".
    This worked successful. The database is up and running. (But quite empty).
    Then I transferred the latest full backup of my source database to the new database. I have the same structure at the destiantion as at the
    source.
    Now I want to use rman restore to build up the clone with this backup. Therefore I start RMAN and connect to the target without catalog.
    "RMAN> restore database;"
    leads to:
    Starten restore um 27.09.07
    Kanal ORA_DISK_1 wird benutzt
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 09/27/2007 16:26:16
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 709 found to restore
    RMAN-06023: no backup or copy of datafile 708 found to restore
    RMAN-06023: no backup or copy of datafile 707 found to restore
    "RMAN> list backup;"
    does not show any results.
    "RMAN> crosscheck backup;"
    Zugewiesener Kanal: ORA_DISK_1
    Kanal ORA_DISK_1: SID=17 Gerõtetyp=DISK
    "RMAN> list backup;"
    does not show any results.
    To me this looks as if RMAN does not identify the/any backup.
    What has to be done to solve the problem?
    Thank you in advance,
    Hergen.

    Hi, I assume that by clone you mean a duplicate of the DB including ALL tablespaces and not just a few right? YOu want to also rename the DB according to what I read.
    As a note, your new database does not see the backups because you do not connect to the catalog, and you have no backup info as a result.
    Correct me if I am wrong if I misundestand your situation:
    First if you want to duplicate, you do not need to create an empty DB. Just create an new instance without any controlfiles or datafiles. Then you restore your rman backup
    You could perhaps adapt this procedure I have used recently to clone databases with RMAN backups: You just need RMAN backups, taken as hot backups is fine. You also need the controlfile autobackup from RMAN. If you do not want to use the catalog, you can use the controlfile as catalog, and register the backup info to the controlfile, then restore.
    Here is the procedure:
    RMAN RESTORE DB FROM COMPLETE LOSS (without use of catalog)
    1-     Install oracle db home and patch.
    Note: As much as possible, patch to the same version of the DB to be restored. If you do not, you should patch to a later release (do not do this if at all possible, as problems may occur). After opening with reset logs, you will have to startup with the upgrade option and run the cat upgrade script to update the DB to the current patchset.
    2-     Install or configure an instance on the desired node. It is not necessary to create a database.
    a.     Run oradim to create the instance.
    Oradim –new –SID sid –SYSPWD sysdbapass –STARTMODE manual|automatic –PFILE ‘….path to pfile….\initsid.ora’
    NOTE: The pfile is optional, required if you do not use a spfile
    b.     Create and configure a listener, as rman requires oracle net connectivity.
    i.     Use oracle utilities to create listener.
    ii.     Use oracle utilities to configure listener to register the instance just created. (or manually edit the listener.ora file).
    c.     Configure a tnsnames.ora file so that rman can reach the database through the listener.
    d.     Create all directories for datafiles, admin, redologs, archive, flash_recovery_area etc if required.
    3-     Create a pfile or get one (ideally the backups should include it).
    a.     Change paths in the pfile to reflect new file structure. Also change any settings that are relevant.
    Note: if using an spfile, then the rman controlfile autobackup will have it. In that case startup in nomount, start RMAN after setting ORACLE_SID=sid, with ‘RMAN target / NOCATALOG.
    Run this in rman
    RUN {
    SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘………………..\CONTROL_%F’;
    RESTORE SPFILE TO PFILE ‘………\initsid.ora’ FROM AUTOBACKUP;
    SHUTDOWN ABORT;
    NOTE:
    -     If you do not have a specific archive file location (archivelog mode only) the flash recovery area size may need to be increased, depending on the number of archive files to recover.
    -     If restoring to a different instance (want to restore an old backup to a different db name, set the db_name in the pfile the same as the db name in the backups. You can rename the db later.
    4-     Get the backups desired to restore the DB, and make them available to the node where the restore is to be done.
    5-     Startup the database in nomount mode. Startup the service is necessary, then startup the database in nomount mode: specify the pfile location if not in a standard location.
    ‘STARTUP NOMOUNT PFILE=’……\initsid.ora’’;
    6-     Get DB id from controlfile autobackup. Get the most recent controlfile autobackups from the backup files, and find the database id. Below is an example
    # CONTROL_c-XXXXXXXXXX-YYYYMMDD-ZZ
    # XXXXXXXXXX IS THE DBID
    7-     START RMAN after setting ORACLE_SID=sid, with ‘RMAN target / NOCATALOG’.
    8-     SET DBID. Get the dbid from above. Run ‘SET DBID XXXXXXXXXXXX;’
    9-     Restore controlfile
    RUN {
    SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '… \CONTROL_%F';
    RESTORE CONTROLFILE FROM AUTOBACKUP;
    ALTER DATABASE MOUNT;
    NOTE: If restoring old files, then you must add MAXDAYS=xxx to the restore controlfile command, so that it will find the desired file. Default is 7 days. (explaining why it can’t find older then 7 days).
    10-     Catalog backup files. It is probable that the backup files restored will be in a different location once restored (applicable to disk backups). You need to catalog them in RMAN so that RMAN knows about them. List all backup files and run these commands for each backup and controlfile autobackup:
    ‘CATALOG BACKUPPIECE ….\CONTROL_C-310452700-20070918-01';’
    ‘CATALOG BACKUPPIECE …\BACKUP_HEIS8FIK_1_1';
    NOTES: If the backups are in the same location as they have always been, then a recatalog is not necessary, as the control file has the right backup files information.
    If the backups were restored to a different location, then a recatalog must be done so that RMAN can find them. If the regular location of backups is not available, then rman needs to be updated to reflect that. In that case run these commands:
         CROSSCHECK BACKUPS;
         DELETE EXPIRED BACKUP;
         CROSSCHECK ARCHIVELOG ALL;
         DELETE EXPIRED ARCHIVELOG ALL;
    If this is test restore (to test disaster recovery for example), likely all the backups are still there, but it is desired to use the restored backup files only. RMAN needs to be updated to reflect that the regular backups do not exist. Make the regular backup files unavailable to RMAN (such are renaming a directory, or preventing access through security), and then run the above commands.
    11-     Find the datafile names and numbers. This is only required if datafiles are in a different location on the database to be restored.
    Using SQLPlus, set the oracle_sid, then run sqlplus / ;
    Run the following command
         Select file# as “file/grp#’, name from v$datafile; (for datafiles).
         Select group#, member from v$logfile. (for redologs)
    12-     Restore the database
    (use only if all datafile locations are the same!)
    RUN
    # allocate a channel to disk
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK MAXPIECESIZE 2 G FORMAT '…path…\BACKUP_%U';
    RESTORE DATABASE;
    RECOVER DATABASE;
    (use if datafiles are not in the same location)
    RUN
    ALLOCATE CHANNEL C1 DEVICE TYPE DISK FORMAT ‘…\BACKUP_%U';
    SET NEWNAME FOR DATAFILE 1 TO ‘….\SYSTEM01.DBF';
    SET NEWNAME FOR DATAFILE 2 TO '…\UNDOTBS01.DBF';
    SET NEWNAME FOR DATAFILE 3 TO '…\SYSAUX01.DBF';
    SET NEWNAME FOR DATAFILE 4 TO '…\USERS01.DBF';
    SET NEWNAME FOR DATAFILE 5 TO '…\TOOLS_01.DBF ';
    # add other tablespace locations here.
    # We need to tell the controlfile the new location for the redologs
    SQL "ALTER DATABASE RENAME FILE ''…\REDO01.LOG'' TO      ''…\REDO01.LOG''";
    SQL "ALTER DATABASE RENAME FILE ''…\REDO02.LOG'' TO      ''…\REDO02.LOG''";
    SQL "ALTER DATABASE RENAME FILE ''…\REDO03.LOG'' TO      ''…\REDO03.LOG''";
    RESTORE DATABASE;
    # we need to tell the controlfile the location of the new datafiles.
    SWITCH DATAFILE ALL;
    RECOVER DATABASE;
    13-     Reset the logs. ALTER DATABASE OPEN RESETLOGS;
    NOTE: If the oracle home is of a newer revision then the database, the open resetlogs will generate an error. In that case open the database with the upgrade option and then run the catalog upgrade as per patch instructions.
    14-     Create a temporary tablespace. The system thinks it has a temp tablespace, but it needs to be recreated
    a.     Create another temp tablespace (modify as needed).
         CREATE TEMPORARY TABLESPACE temp2
              TEMPFILE '......\temp02.dbf' SIZE 128M REUSE
              AUTOEXTEND ON NEXT 16M MAXSIZE unlimited
              EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
    b.     Point the server to the new file
    ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;
    c.     Delete the missing one:
              DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;
    d.     RECREATE THE temp tablespace;
              CREATE TEMPORARY TABLESPACE temp
                   TEMPFILE 'd:\......\temp_01.dbf' SIZE 128M REUSE
              AUTOEXTEND ON NEXT 16M MAXSIZE unlimited
              EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
    e.     Change system default tablespace again to temp:
              ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
    f.     Delete the transition temp tablespace temp2:
    DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;
    15-     Rename the database if the restored database name needs to change.
    Use the nid utility to rename the db. IMPORTANT: the temporary tablespace needs to exist for this to work, or the db rename will fail and a restore will have to be done.
    Use :
    -     Shutdown database in immediate mode.
    -     Startup in nomount.
    -     Open command prompt.
    -     set oracle_sid = sid
    -     nid sys/pass dbname=newname logfile=….\logfile.txt
    -     shutdown the db (if required)
    -     Change the dbname in the pfile or spfile to the new dbname
    -     Create a new password file:
    o     Orapwd file=….. password=…
    IMPORTANT NOTE: if you rename a DB, your existing backups will not be valid, do backups of the newly renamed db!!!
    16-     Open the database and test.
    NOTE: Whenever you open with resetlogs, YOU MUST BACKUP YOUR DATABASE. Your old backups can only be used to restore the old DB.
    I hope this helps.

  • Migrating  to Weblogic 8.1 from Weblogic 7.0

    We are using Weblogic 7.0 with SP2. The application is build on weblogic portal.
    Can we have some docs on migrating from 7.0 to 8.1.
    thanks in advance.
    Selva

    Selva -
    See the upgrade guide at -
    http://e-docs.bea.com/wlp/docs81/upgrade/index.html
    Regards,
    Kunal
    "Selva" <[email protected]> wrote:
    >
    We are using Weblogic 7.0 with SP2. The application is build on weblogic
    portal.
    Can we have some docs on migrating from 7.0 to 8.1.
    thanks in advance.
    Selva

  • EJB EAR deployment for weblogic 9.2

    Hello!
    I already have the EJB3.0 application which I would like to deploy. After preparing the .ear file I tried to deploy it with the Administration console. I received the error message, and I found a workaround : [url http://forums.bea.com/bea/thread.jspa?threadID=600016992&tstart=0]here (@dev2dev). When I tried the console deployment, I received the following error message:
    <11.12.2006 14.49 Uhr CET> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1165844945693' f
    or task '3'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
    weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
            Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
    ate is [END_DOCUMENT]
            at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
            at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
            Truncated. see log file for complete stacktrace
    >
    <11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'app5'.
    >
    <11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
            Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
    ate is [END_DOCUMENT]
            at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
            at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
            Truncated. see log file for complete stacktrace
    >I would just like to mention, that it is not really self-explaining. Can somebody help me and explain me what does this error mean?
    Also, is there a document describing the complete deployment process for wl9.2?
    Thank you.
    Konstantin

    MIK wrote:
    I have a question about weblogic-ejb-jar.xml file entries.
    weblogic 9.1 server says it is invalid while deploying my file
    my file is as under,
    <?xml version="1.0"?><!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems,
    Inc.//DTD WebLogic 8.1.0 EJB//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/910"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/910
    http://www.bea.com/ns/weblogic/910/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
              <ejb-name>MessageAccess</ejb-name>
              <message-driven-descriptor>
    <resource-adapter-jndi-name>SystemModule-test</resource-adapter-jndi-name>
              </message-driven-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    can anybody help what is wrong with it?the error I get is this,
    [EJB:011023]An error occurred while reading the deployment descriptor.
    The error was:
    Unmarshaller failed.
    at
    weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:957)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:317)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    and XMLSPY also says that weblogic-ejb-jar.xml is invalid and the error
    there is,
    Root element '<weblogic-ejb-jar' not defined in DTD/Schema.

  • Problems deploying ear file created with ant build script

    Hi All,
    I'm using Jdeveloper 11G and Weblogic 10.3. When I build my application and run it within Jdeveloper, it works fine. However, we have a requirement to run ANT build script and create a deployable .ear file that can be manually deployed to any Weblogic Server.
    I created my ant build script and it compiles/builds fine - the .ear file looks good. However, when I attempt to deploy it, it fails with
    javax.faces.webapp.FacesServlet for servlet Faces Servlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         Truncated. see log file for complete stacktrace
    >
    <Nov 2, 2011 2:43:43 PM MDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1320266599219' for task '3'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "Faces Servlet" failed to preload on startup in Web application: "###"
    I am not sure how to tell weblogic where to find the classes needed. I have a pretty huge classpath used when compiling - should I be putting the classpath in the manifest (?) - I don't think I should need to include the .jar files manually in the .ear file - since all the libraries should already be available in weblogic - or is that a misconception?
    Please help!!

    I answered my own question -
    I had to manually add the following to the WEB-INF/lib to get the error to go away:
    ${ORACLE_HOME}/modules/javax.jsf_1.1.0.0_1-2.jar and
    ${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jsf_1.0.0.0_1-2-15.jar and
    ${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jstl_1.2.0.1.jar
    that solved my problem. However, I think it'd be great if I could somehow just specify (in the weblogic-application.xml maybe?) that my application is using the above modules without having to copy the jar files into my WEB-INF/lib - any suggestions?
    Thanks

  • WLS 8.1 issue with .ear deployment ....

    I think the weblogic8.1 seems to have some NEW bug now. We have a .ear file that
    works just PERFECT in WLS6.1. But now when we try to DEPLOY this .ear file our
    WLS8.1 server(via the new look and feel of WLS8.1' console)....we are getting
    the Exception like ...."pl read inline below":
    ...All i know is that WLS 8.1 has introduced something like : "single J2EEC -
    EAR compiler, replacing the separate compilers in previous releases" ........is
    it may be because of this ????
    If somebody has any idea ....please let me know asap ...and just above the EXCEPTION
    we are also getting something like ...."Deployment descriptor "/WEB-INF/ups-html.tld"
    is malformed" ....what is going wrong now ?
    Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
    Read inline for the Exception:
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
    DTD: Element type "info" must be declared. (line 334, column 9).>
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
    DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
    (line 335, column 8).>
    MessageResourcesFactory.createFactory
    java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
    service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    java.lang.NullPointerException
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    >
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "service"
    failed to preload on startup in Web application: "ABL".
    javax.servlet.UnavailableException: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1043)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    thx, sangita

    Rob,
    These are the 3 files that you need:
    1) wlstart_cap (this is the start up script that we use to start the Managed server
    while on WLS6.1) ....please read inline:
    -----------Inline 1-----------------
    #!/bin/ksh
    # BEA WebLogic Start Script - Version 1.1
    # Add support for STARTMODE MKG 03/08/2002
    # Set user specified variables
    JAVA_HOME=/usr/j2sdk1_3_1_01
    JAVA_OPTIONS="-D$1 -ms128m -mx128m -noclassgc"
    BEA_HOME=/opt/bea
    WL_HOME=$BEA_HOME/wlserver6.1
    WL_SCRIPT=$WL_HOME/config/Subsidiary
    export WL_SCRIPT
    EXPORT_LIB=$WL_HOME/lib
    #### Set locale to US English MKG 2003/01/16
    LC_MESSAGES=C
    LC_TIME=en_US.ISO8859-1
    LC_NUMERIC=en_US.ISO8859-1
    LC_MONETARY=en_US.ISO8859-1
    LC_COLLATE=en_US.ISO8859-1
    LC_CTYPE=en_US.ISO8859-1
    export LC_MESSAGES LC_TIME LC_NUMERIC LC_MONETARY LC_COLLATE LC_CTYPE
    #### End locale settings
    #### UPSCAP-clientmanger App settings --- Begin
    # workaround for strange bug in code that requires an x-server
    # to be present when graph code is initialized.
    # Note that this is my sun workstation. MKG 05/16/2002
    DISPLAY=bluewolf.telecom.ups.com:0.0
    export DISPLAY
    #### UPSCAP-clientmanger App settings --- End
    #### EUP App settings --- Begin
    VANAPI_HOME=/opt/vanapi
    VANPATH=$VANPATH:$VANAPI_HOME/vanapi/share
    LD_LIBRARY_PATH=$VANAPI_HOME/vanapi:$VANAPI_HOME/vanapi/vanjavi:$LD_LIBRARY_PATH
    PATH=$VANAPI_HOME/perl_dir/bin:$PATH
    EUP_CLASSPATH=$WL_HOME/config/Subsidiary/serverclasses
    export VANPATH LD_LIBRARY_PATH VANAPI_HOME PATH EUP_CLASSPATH
    #### EUP App settings --- End
    CLASSPATH=$WL_HOME/lib/CR061106_61sp2.jar:$WL_HOME/lib/CR072612_61sp2.jar:$WL_HOME/lib/CR071109_610sp2.jar:$WL_
    HOME/lib/CR058352_61sp2.jar:$WL_HOME/lib/weblogic.jar:$BEA_HOME:$EUP_CLASSPATH
    if [ -n "$LD_LIBRARY_PATH" ]; then
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/lib/solaris:
    else
    LD_LIBRARY_PATH=$WL_HOME/lib/solaris:
    fi
    export LD_LIBRARY_PATH
    ADMIN_URL=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerURL|awk '{print  $2}')
    ADMIN_SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerName|awk '{print
    $2}')
    DOMAIN_NAME=$(cat $WL_SCRIPT/config.weblogic|grep Domain|awk '{print  $2}')
    PATH=$WL_HOME/bin:$JAVA_HOME/bin:$PATH
    export PATH
    WLS_PW=$(cat $WL_SCRIPT/bea.check | awk '{print $1}')
    export $WLS_PW
    #################################export LOG_HOME=/export/bea/netsite/ext-admin/logs/bea
    export LOG_HOME=/export/bea/logs
    # echo all of the variable settings
    #echo
    #echo "BEA_HOME=$BEA_HOME"
    #echo "WL_HOME=$WL_HOME"
    echo "EXPORT_HOME=$EXPORT_HOME"
    echo "CLASSPATH=$CLASSPATH"
    #echo "LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
    #echo "PATH=$PATH"
    #echo "JAVA_OPTIONS=$JAVA_OPTIONS"
    #echo "DOMAIN_NAME=$DOMAIN_NAME"
    #echo "ADMIN_URL=$ADMIN_URL"
    #echo "ADMIN_SERVER_NAME=$ADMIN_SERVER_NAME"
    #java -fullversion
    #echo
    #echo
    # Grab some file descriptors.
    maxfiles='ulimit -H -n'
    if [ ! $? -a "$maxfiles" != 1024 ]; then
    if [ "$maxfiles" = "unlimited" ]; then
    maxfiles=1025
    fi
    if [ "$maxfiles" -lt 1024 ]; then
    ulimit -n $maxfiles
    else
    ulimit -n 1024
    fi
    fi
    # Set Production Mode. When set to true, the server starts up
    # in production mode. When set to false, the server starts up
    # in development mode. The default is false.
    STARTMODE=true
    if [[ -n $1 ]]; then
    if [[ $1 = "admin" ]]; then
    echo "Starting admin server...."
    ###### echo "See /export/netsite/ext-admin/logs/bea/admin.start for more info"
    # Change to the WebLogic directory
    cd $WL_HOME
    echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$ADM
    IN_SERVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblogic.Production
    ModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
    -Dweblogic.ma
    nagement.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
    nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$ADMIN_SE
    RVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblogic.ProductionModeE
    nabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
    -Dweblogic.managem
    ent.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
    $LOG_HOME/admin.start 2>&1&
    echo
    shift
    # Change back to the domain directory
    cd config/$DOMAIN_NAME
    echo $! > admin.pid
    else
    while [[ $# -gt 0 ]];do
    SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep $1|awk '{print $2}')
    if [[ $SERVER_NAME = "" ]]; then
    echo "ERROR: unable to locate an entry for "$1" in config file"
    shift
    else
    echo "Starting server: "$SERVER_NAME
    ######### echo "See /export/netsite/ext-admin/logs/bea/$SERVER_NAME.start
    for more info"
    # Change to the WebLogic directory
    cd $WL_HOME
    echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Nam
    e=$SERVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dw
    eblogic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW
    weblogic.Server
    nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$SE
    RVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblog
    ic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW weblogic.Server
    $LOG_HOME/$SERVER_NAME.start 2>&1 &
    shift
    # Change back to the domain directory
    cd config/$DOMAIN_NAME
    echo $! > $SERVER_NAME".pid"
    fi
    done
    fi
    else
    echo ""
    echo ""
    echo "FATAL ERROR: You must specify the server to start. Either 'admin' or
    the server token"
    echo ""
    fi
    -----------Inline 1 ends-----------------
    2) startManagedWebLogic.sh(this is the Managed server start up script at wls8.1)
    ---------Inline 2 starts---------
    #!/bin/sh
    # This script is used to start a managed WebLogic Server for the domain in the
    # current working directory. This script reads in the SERVER_NAME and
    # ADMIN_URL as positional parameters, sets the SERVER_NAME variable, then
    # starts the server.
    # Other variables that startWLS takes are:
    # WLS_USER - cleartext user for server startup
    # WLS_PW - cleartext password for server startup
    # PRODUCTION_MODE - Set to true for production mode servers, false for
    # development mode
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    # JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    # -hotspot, etc.)
    # MEM_ARGS - The variable to override the standard memory arguments
    # passed to java
    # For additional information, refer to the WebLogic Server Administration Guide
    # (http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html).
    #Set the New Java Path
    PATH=/opt/bea/jdk141_02/bin:$PATH
    # set up WL_HOME, the root directory of your WebLogic installation
    WL_HOME="/opt/bea/weblogic81"
    # set up common environment
    # Set Production Mode. When this is set to true, the server starts up in
    # production mode. When set to false, the server starts up in development
    # mode. If it is not set, it will default to false.
    PRODUCTION_MODE="true"
    # Set JAVA_VENDOR to java virtual machine you want to run on server side.
    JAVA_VENDOR="Sun"
    # Set JAVA_HOME to java virtual machine you want to run on server side.
    JAVA_HOME="/opt/bea/jdk141_02"
    set USE_CURRENT_JAVA_HOME "$@"
    . "${WL_HOME}/common/bin/commEnv.sh"
    shift 1
    # Set SERVER_NAME to the name of the server you wish to start up.
    ADMIN_URL=http://153.2.255.51:8001
    SERVER_NAME=
    # Set WLS_USER equal to your system username and WLS_PW equal
    # to your system password for no username and password prompt
    # during server startup. Both are required to bypass the startup
    # prompt.
    WLS_USER=
    WLS_PW=
    # Set JAVA_VM to java virtual machine you want to run on server side.
    # JAVA_VM="-server"
    # Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
    # are more than one, include quotes around them. For instance:
    # JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
    usage()
    echo "Need to set SERVER_NAME and ADMIN_URL environment variables or specify"
    echo "them in command line:"
    echo 'Usage: ./startManagedWebLogic.sh [SERVER_NAME] [ADMIN_URL]'
    echo "for example:"
    echo './startManagedWebLogic.sh managedserver1 http://localhost:7001'
    exit 1
    # Check for variables SERVER_NAME and ADMIN_URL
    # SERVER_NAME and ADMIN_URL must by specified before starting a managed server,
    # detailed information can be found at http://e-docs.bea.com/wls/docs81/adminguide/startstop.html.
    if [ ${#} = 0 ]; then
    if [ "x${SERVER_NAME}" = "x" -o "x${ADMIN_URL}" = "x" ]; then
    usage
    fi
    elif [ ${#} = 1 ]; then
    SERVER_NAME=${1}
    if [ "x${ADMIN_URL}" = "x" ]; then
    usage
    fi
    elif [ ${#} = 2 ]; then
    SERVER_NAME=${1}
    ADMIN_URL=${2}
    else
    usage
    fi
    # Start WebLogic server
    # Reset number of open file descriptors in the current process
    # This function is defined in commEnv.sh
    resetFd
    CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
    export CLASSPATH
    # Start WebLogic server
    echo CLASSPATH="${CLASSPATH}"
    echo
    echo PATH="${PATH}"
    echo
    echo "***************************************************"
    echo "* To start WebLogic Server, use a username and *"
    echo "* password assigned to an admin-level user. For *"
    echo "* server administration, use the WebLogic Server *"
    echo "* console at http://<hostname>:<port>/console *"
    echo "***************************************************"
    "$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} \
    -Dweblogic.Name=${SERVER_NAME} \
    -Dweblogic.management.username=${WLS_USER} \
    -Dweblogic.management.password=${WLS_PW} \
    -Dweblogic.management.server=${ADMIN_URL} \
    -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" \
    weblogic.Server
    -------Inline 2 ends----------
    3) startWebLogic.sh(this is the Admin start up script at wls8.1)
    ---------Inline 3 starts-------
    #!/bin/sh
    # This script is used to start WebLogic Server for the domain in the current
    # working directory. This script simply sets the SERVER_NAME variable
    # and calls the startWLS.sh script under ${WL_HOME}/server/bin.
    # To create your own start script for your domain, all you need to set is
    # SERVER_NAME, then starts server.
    # Other variables that startWLS takes are:
    # WLS_USER - cleartext user for server startup
    # WLS_PW - cleartext password for server startup
    # PRODUCTION_MODE - Set to true for production mode servers, false for
    # development mode
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    # JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    # -hotspot, etc.)
    # MEM_ARGS - The variable to override the standard memory arguments
    # passed to java
    # For additional information, refer to the WebLogic Server Administration
    # Console Online Help(http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html)
    #Set the New Java Path
    PATH=/opt/bea/jdk141_02/bin:$PATH
    # set up WL_HOME, the root directory of your WebLogic installation
    WL_HOME="/opt/bea/weblogic81"
    # set up common environment
    # Set Production Mode. When this is set to true, the server starts up in
    # production mode. When set to false, the server starts up in development
    # mode. If it is not set, it will default to false.
    PRODUCTION_MODE="true"
    # Set JAVA_VENDOR to java virtual machine you want to run on server side.
    JAVA_VENDOR="Sun"
    # Set JAVA_HOME to java virtual machine you want to run on server side.
    JAVA_HOME="/opt/bea/jdk141_02"
    set USE_CURRENT_JAVA_HOME "$@"
    . "${WL_HOME}/common/bin/commEnv.sh"
    shift 1
    # Set SERVER_NAME to the name of the server you wish to start up.
    SERVER_NAME=Admin
    # Set WLS_USER equal to your system username and WLS_PW equal
    # to your system password for no username and password prompt
    # during server startup. Both are required to bypass the startup
    # prompt.
    WLS_USER=
    WLS_PW=
    # Set JAVA_VM to java virtual machine you want to run on server side.
    # JAVA_VM="-server"
    # Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
    # are more than one, include quotes around them. For instance:
    # JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
    # Reset number of open file descriptors in the current process
    # This function is defined in commEnv.sh
    resetFd
    # Start WebLogic server
    CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
    export CLASSPATH
    "$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
    -Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW}
    -Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
    weblogic.Server
    --------Inline 3 ends---------
    I think we are getting closer to a solution !
    thanks rob,
    Rob Woollen <[email protected]> wrote:
    Yes, your $CLASSPATH could be the issue. Can you show me the $CLASSPATH
    used in each version of the server?
    -- Rob
    sangita wrote:
    Thanks Rob, I understood changing the DOCTYPE ...and i will give ita try.
    And iam assuming you might have read my previous response in this chain,Iam using
    WLS6.1 & WLS8.1 BOTH on the same hardware unix server....iam just wonderingif
    there is any CLASSPATH issue that might have been causing this NoClassDefFoundError......?
    just wanted to let you know that iam running WLS6.1 + WLS8.1 on thesame BOX.
    I will try other options that you have suggested ....thanks again !
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    Rob,
    Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
    to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
    definition to the Taglib 1.1 DTD or change the tld file to conformto
    the 1.2 DTD. how do i do either of the 2 options ?To change your taglib to be the 1.1 DTD you just need to change the
    DOCTYPE header to be
    <!DOCTYPE taglib
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
    "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
    Otherwise, you'll need to change the tld file to be JSP 1.2 compliant.
    If you post your tld file here, then I can help.
    Iam just guessing here, is it may be due to this DTD/.tld issue thatiam not been
    able to DEPLOY the .ear file(now that wls8.1 checks the validity beforedeloying
    the app)....are the 2 errors that iam getting, in any ways inter-related?
    I'm not sure they're related. It is possible.
    i.e is it possible that due to DTD/.tld ....am i getting this NoClassDefFoundError
    JUST CURIOUS ???
    WELL THANKS FOR YOUR TIME ON THIS ...REALLY APPRECIATE IT !
    No problem.
    -- Rob
    Regards, sangita
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    1) This is how my .tld looks like:
    <?xml version="1.0" encoding="UTF-8" ?>^M
    <!DOCTYPE taglib^M
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"^M
    "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">^M
    Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
    to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
    definition to the Taglib 1.1 DTD or change the tld file to conformto
    the 1.2 DTD. Unfortunately WLS 6.1 didn't validate the tld file
    against
    the DTD, but it should have, and you'll need to correct your application.
    <taglib>^M
    <tlib-version>1.0</tlib-version>^M
    <jsp-version>1.2</jsp-version>^M
    <short-name>html</short-name>^M
    2) the MANIFEST.MF file is located within the ABL.war.
    3) I will try placing the struts-util.jar in the WEB-INF/lib directoryof the
    ABL.war file. And I will let you if it works or not ?Right. My guess is this is a bug in WLS 8.1. I can see no reasonwhy
    the manifest class-path isn't working for you. That's why I askedif
    you could send the EAR file so I could investigate, but I understand
    that's not always possible.
    I suspect the WEB-INF/lib will work, but it's just a workaround.
    I'm
    not sure if you're using 8.1 or 8.1SP1, but if you're not using SP1,
    then you might consider trying that. (java weblogic.version willtell
    you.)
    Otherwise, I think you should open a case with [email protected]
    -- Rob
    thx, sangita
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    Rob, here is the information that you need: Please read inline:
    ---------------------------iam doing cut&paste
    <attribute>^M
    <name>styleClass</name>^M
    <required>false</required>^M
    </attribute>^M
    (this is the 334 line)<info>applys the style of
    the
    number text
    if it passes the conditional given</info>^M
    </tag>^M
    </taglib>^MWell, it looks like you have a JSP 1.1 tld, but it's being validated
    against the JSP 1.2 tld. I suspect that you have not declareda
    DOCTYPE
    and 6.1 defaulted to the older JSP spec.
    Anyway, check the first line of your tld file. It should look
    something
    like this:
    <!DOCTYPE taglib
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
         "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
    I have an ABL.ear file and this is what it looks like:
    ABL.ear
    META-INF/
    META-INF/MANIFEST.MF
    ABL.jar
    ABL.war
    lib/
    lib/struts-util.jar
    META-INF/application.xml
    and in the ABL.war ...there is a META-INF/MANIFEST.MF file ...and
    when
    i open
    this file ...this is what it contains:Just to double-check, the MANIFEST.MF file is located within the
    ABL.war, right?
    Manifest-Version: 1.0
    Created-By: Ant 1.4.1
    Class-Path: lib/struts-util.jar
    there is nothing in the CLASSPATH that contains this application'sspecific .jar/.war
    ...or any classes specific to this application ........BOTH IN
    WLS6.1(and
    now
    in WLS8.1)Hmm, I'm not sure yet what the problem is here. Does it work ifyou
    place the struts-util.jar in the WEB-INF/lib directory of the ABL.war
    file? (I suspect it will.)
    This might be a WLS bug. If you can post your ear file here (oremail
    it to me rwoollen at bea dot com), then I can dig into it more.
    -- Rob
    thx, sangita
    Rob Woollen <[email protected]> wrote:
    It looks like there are 2 errors.
    The first error /WEB-INF/ups-html.tld is most likely the result
    of
    WLS
    8.1 doing more validation on your tld file. If you'd show us
    either
    the
    entire ups-html.tld or just the part around line 334, then wecan
    help.
    As for the NoClassDefFoundError, you'll have to provide some
    more
    details about your ear file and environment. Do you have anythingin
    the $CLASSPATH on either the 6.1 or 8.1 environments?
    -- Rob
    Sangita wrote:
    I think the weblogic8.1 seems to have some NEW bug now. We have
    a
    .ear
    file that
    works just PERFECT in WLS6.1. But now when we try to DEPLOY
    this
    .ear
    file our
    WLS8.1 server(via the new look and feel of WLS8.1' console)....we
    are
    getting
    the Exception like ...."pl read inline below":
    ...All i know is that WLS 8.1 has introduced something like
    "single
    J2EEC -
    EAR compiler, replacing the separate compilers in previous releases"........is
    it may be because of this ????
    If somebody has any idea ....please let me know asap ...and
    just
    above
    the EXCEPTION
    we are also getting something like ...."Deployment descriptor
    "/WEB-INF/ups-html.tld"
    is malformed" ....what is going wrong now ?
    Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
    Read inline for the Exception:
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248>
    <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
    against
    the
    DTD: Element type "info" must be declared. (line 334, column
    9).>
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248><[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
    against
    the
    DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
    (line 335, column 8).>
    MessageResourcesFactory.createFactory
    java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
    service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    java.lang.NullPointerException
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.

  • Weblogic EAR deployment - "error in opening zip file"

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

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

  • Ear Deployment failed in weblogic server 9.2

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

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

  • WebLogic Server EAR Deployment Queries!

    Hi All,
    I have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Any pointers to info source will be REALLY appreciated.
    Wiating for your reply.
    Many Thanks in Advance,
    C R Baradwaj

    Hi,
    Can anyone from BEA team help me in these queries?
    This is very urgent!
    have few queries with respect to EAR deployment in BEA WebLogic Server
    a) we have a requirement wherein we need to deploy the modified EAR file to one node in a cluster, whereas the other node will still continue to use the old EAR file. Is that possible in a production environment?
    b) we also have a requirement wherein we need to bring down the cluster and start the servers as independent servers instead of a clustered servers from command line without logging into the weblogic server console
    c) we have one more requirement wherein we have all the configuration xml files for each web application in a EAR File. We need a way to deploy the configuration xml file separately if there is a change only to the configuration xml file. Is that possible?
    Also, we need to deploy a specific web application in a EAR file instead of re-creating the EAR again. Like an emergency release of one or more web application in a EAR.
    d) Is that possible to update the JAR file and WAR file dynamically which are deployed as part of the EAR file.
    Thanks and Regards,
    C R Baradwaj

  • Failure occurred in the execution of deployment request with ID '1219300288

    I deployed my JSF application from workspacestudio 1.1 (workshop for weblogic 10) to weblogic 10 server. It works fine for me.
    All other teammates are facing problem with their deployment. They get an error as
    <Failure occurred in the execution of deployment request with ID '1219300288452' for task '0'. Error is: 'weblogic.application.ModuleException: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;'
    Please can someone tell me the reason for this behaviour?
    Here's the stack trace:
    <Aug 20, 2008 11:31:15 PM PDT> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 10.1.243.73, 127.0.0.1> <Aug 20, 2008 11:31:15 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> <Aug 20, 2008 11:31:15 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
    log4j:WARN Please initialize the log4j system properly.
    <Aug 20, 2008 11:31:29 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1219300288452' for task '0'. Error is: 'weblogic.application.ModuleException: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;'
    weblogic.application.ModuleException: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:977)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         Truncated. see log file for complete stacktrace
    java.lang.NoSuchMethodError: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;
         at com.sun.faces.application.WebappLifecycleListener.<clinit>(WebappLifecycleListener.java:67)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         Truncated. see log file for complete stacktrace
    >
    <Aug 20, 2008 11:31:30 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'ipro'.> <Aug 20, 2008 11:31:30 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'ipro'.> <Aug 20, 2008 11:31:30 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:977)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         Truncated. see log file for complete stacktrace
    java.lang.NoSuchMethodError: com.sun.faces.util.Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;
         at com.sun.faces.application.WebappLifecycleListener.<clinit>(WebappLifecycleListener.java:67)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         Truncated. see log file for complete stacktrace
    >
    <Aug 20, 2008 11:31:30 PM PDT> <Warning> <Deployer> <BEA-149252> <No deployment 'ipro' found for Operation stop.>

    I created JSF app in the workshop for weblogic 10 and submitted the code to source control.
    Team mates took the latest revision and build the project on their machine, which has same installation workshop for weblogic 10 as mine( we use same installler)
    Thus the project have same code no difference at all.

Maybe you are looking for