Partial redeployment in exploded EAR gets blown away on restart

I have an exploded EAR with an (exploded) WAR and a JSP inside the WAR. On the filesystem it looks like this:
/.../foo.ear/blah.war/my.jsp
The EAR was initially deployed in stage mode, then I switched to nostage. my.jsp is still under development and continues to change. I wrote a simple script that has two steps: 1) copy my.jsp from /some/dir to /.../foo.ear/blah.war/ 2) do a partial deployment/update with weblogic.Deployer -targets <cluster> -name foo -redeploy blah.war/my.jsp .
The cluster is WL 10.3.3 in Production mode. I start the managed server, run the script that deploys changed JSPs and test the app. Everything is good. Then I restart the managed server...and my changed JSP is no longer there. I have to run the script again in order to make the managed server update the JSP.
I can't run the deploy script on every server restart. What am I missing here?

No one here is going to do anything about it. Send feedback to Apple.
http://www.apple.com/feedback/ipad.html
Basic troubleshooting steps. 
17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 

Similar Messages

  • Partial redeploy of an application ear fails intermittently

    Hi,
    I am trying to redeploy my application ear using deployment API provided by weblogic. The list of files which i try to redeploy are couple of jars and couple of wars one at a time. The problem is most of the times the deployment paritally goes through informing me that weblogic has transitioned application status from activated at last. But in some cases i see "<b>javax.management.InstanceAlreadyExistsException"</b> though the application is already present. Why does this happen where in the handle to ApplicationMBean tries to register the application as though it was new which is not the case. Check the exception below.
    javax.management.InstanceAlreadyExistsException: vgndomain:Location=VgnVCMServer,Name=VgnVCMServer_VgnContentSvcs,ServerRuntime=VgnVCMServer,Type=ApplicationRuntime
         at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
         at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
         at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
         at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
         at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
         at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
         at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
         at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:62)
         at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:74)
         at weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl.<init>(J2EEApplicationRuntimeMBeanImpl.java:42)
         at weblogic.j2ee.J2EEApplicationContainer.initRuntimeMBean(J2EEApplicationContainer.java:781)
         at weblogic.j2ee.J2EEApplicationContainer.<init>(J2EEApplicationContainer.java:448)
         at weblogic.j2ee.J2EEApplicationContainerFactory.createApplicationContainer(J2EEApplicationContainerFactory.java:131)
         at weblogic.j2ee.J2EEApplicationContainerFactory.getOrCreateApplicationContainer(J2EEApplicationContainerFactory.java:113)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.getContainer(SlaveDeployer.java:3011)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2550)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Any help on this would be appreciated.
    Thanks,
    Sandeep

    The info for the 149080 error is included below:
    Basically, you can only do a partial redeploy if you are using an exploded directory app.
    Error: A partial update of an archived application is not allowed. Application app cannot be redeployed.
    Description
         There was an attempt to partially redeploy an archived application. Partial redeployment of an archived application is not allowed.
    Cause
         There was an attempt to partially redeploy an archived application
    Action
         Try deploying entire application
    Refer to the deployment documentation for more info.
    http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/redeploy.html#wp1031505
    8.1.2.2 Partial Redeployment of J2EE Modules
    Partial redeployment also enables you to redeploy a single module or subset of
    modules in a deployed Enterprise Application. Again, partial deployment is
    supported only for applications that are deployed using an exploded archive directory.

  • Redeploying of exploded EJBs within an exploded EAR

    Hi all,
    I've an exploded EAR application which has an exploded EJB. Inside my exploded EJB, I've a META-INF folder with a REDEPLOY file, if I update my EJB & touches the REDEPLOY file inside the META-INF, the EJB doesn't get redeployed. I'd to touched the REDEPLOY inside the META-INF folder of the exploded EAR, is this behavior correct?
    Or am I missing something here?
    Thanks!

    Hi,
    If you are only attempting to read the file, you should read the file as a resource. If you are planning on writing to this file, then it is not a good idea that you depend on where this file is deployed, just place it anywhere else.
    Anyhow, if you have to do it, the best way is to obtain the resource URL, and from that the file name. BTW, there is no warranty that the war will get exploded, that you may be able to freely modify the file, nor that the file name be null :-S
    {the Classloader of your choice}.getResource(<Resource name>).getFile()
    should do the trick.
    Regards,
    LG

  • Exploded EAR in Weblogic 7.0.2

    I'm trying to deploy an exploded EAR file but I must be missing something since WLS doesn't deploy my application.
    I've read the documentation from http://e-docs.bea.com/wls/docs70/programming/deploying.html.
    Beneath the structure in my 'applications' directory as describes in http://e-docs.bea.com/wls/docs70/programming/deploying.html#1125125. I've put application.xml in the MyApp directory - is it the right place and is the file correct?
    MyApp\
    \MyApp.war
    WEB-INF\
    web.xml
    classes\
    dk\
    ...(JSP etc.)
    \MyApp-ejb.jar
    META-INF\
    application.xml
    ejb-jar.xml
    REDEPLOY
    weblogic-cmp-rdbms-jar.xml
    weblogic-ejb-jar.xml
    dk\
    ...(class files)
    application.xml looks like:
    <application>
    <display-name>MyApp</display-name>
    <module>
    <ejb>MyApp-ejb.jar</ejb>
    </module>
    <module>
         <web>
         <web-uri>MyApp.war</web-uri>
         <context-root>myapp</context-root>
         </web>
    </module>
    </application>
    Thanks
    Thomas Aagaard Jensen
    UNI-C, Uddannelse - IT-undervisningsmidler
    WWW : http://www.uni-c.dk/
    Tlf. : +45 8937 6673
    E-mail : [email protected]

    Hie,
              We are facing the same problem; i.e. we are getting the same error message when we are trying to run our struts application on Weblogic 7.0.5 using JDK 1.3.1. This problem occured particularly when we tried to do a load testing using approx 20 concurrent users (a lesser load was supported though). Can you please let us know how this problem was sorted out on your end?
              thanks,
              Debanjan

  • Partial redeployment problem for J2EE module update

    hi, all
    I have one application file (.ear) composed of three EJB modules. I tried to paritally redeploy one of them, but it didn't work.
    Here is the command-line for partial redeployment: java weblogic.Deployer -adminurl t3://XX.XX.XX.XX:XXXX -username XXXX -password XXXX -name XA_MOrderEAR -source XAMOrderEAR -targets MOrderBM.jar@SquadA_N1 -redeploy, where XAMOrderEAR is the name of the exploded archive, MOrderBM.jar is the EJB module to be partially redeployed, SquadA_N1 is a cluster.
    Here is the result:
    <2010/2/22 下午02時10分06秒 GMT+08:00> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for appl
    ication, XA_MOrderEAR [archive: null], to SquadA_N1 .>
    Task 29 initiated: [Deployer:149026]redeploy application XA_MOrderEAR on SquadA_N1.
    Task 29 failed: [Deployer:149026]redeploy application XA_MOrderEAR on SquadA_N1.
    Target state: redeploy failed on Cluster SquadA_N1
    weblogic.application.CannotRedeployException: Module 'MOrderBM.jar' has the same ClassLoader as the Application 'XA_MOrd
    erEAR'. Consider redeploying the entire application.
    Please tell me how to solve the problem. I tried to set enable-bean-class-redeploy to true in weblogic-ejb-jar.xml. It didn't work too.
    thanks
    Blithe Meng

    Hiya
    You can debug this quite easily yourself.
    Enable the SQL Trace for that session and see the Last SQL in the raw trace file.
    You can also run the trace with the option to view bind variables.
    This way you can find out why the SQL is returning no_data_found
    thanks
    anil passi

  • Partial Redeployment

    I'm using wls 8.1. I'm deploying an exploded EAR containing EJB modules and web
    apps. Can I redeploy only the classes loaded by the EJB classloader, or does
    the entire application have to be reloaded? If so, how? What partial redeployment
    options are available when the deployed module is an EAR? Thanks...
    ..Brian

    "Brian" <[email protected]> wrote:
    >
    Rob Woollen <[email protected]> wrote:
    You'll need to add the <enable-bean-class-redeploy> tag to your
    weblogic.ejb-jar.xml
    http://e-docs.bea.com/wls/docs81/ejb/reference.html#1431359
    Then you redeploy by specifying the class that was updated. Something
    like this:
    java weblogic.Deployer -username system -password gumby1234 -redeploy
    -name beanimpl ejb/com/acme/ejb/HelloWorldEJB.class
    This updates the application beanimpl with a new version of my
    HelloWorldEJB class. You just specify the path relative to the topof
    the EAR.
    -- Rob
    Brian wrote:
    I'm using wls 8.1. I'm deploying an exploded EAR containing EJB modulesand web
    apps. Can I redeploy only the classes loaded by the EJB classloader,or does
    the entire application have to be reloaded? If so, how? What partialredeployment
    options are available when the deployed module is an EAR? Thanks...
    ..Brian
    Thanks Rob. You've been a great help. One more question; If I use
    manifest
    classpath to cause a utility JAR to be loaded by the EJB classloader,
    will I need
    to reload the entire application to refresh it?
    Also, the EJB jar file has to be exploded in order to update the implementation
    class, right? I can't seem to update or replace an unexploded EJB JAR.

  • Trying unsuccessfully to redeploy an older ear on WLS9.2

    Hi All,
    I've spent a few days trying to get a redeploy of an ear working on WLS9.2 using the wldeploy ant task. It works where the ear file is newer that the one already deployed, but redeploy just doesn't take effect if the ear we want is older than the one that is already deployed. It doesn't give an error, the log says that it's redeployed, but the redeploy doesn't take effect. This wldeploy task worked fine with WLS8.1 no matter when the ear was built.
    It seems to be the same issue as
    http://forums.bea.com/bea/thread.jspa?forumID=2033&threadID=400002694&messageID=400007471#400007471
    I'm out of ideas, so any help would be gratefully received!
    The original deployment via the console was fine, specifying DDOnly. The ear was loaded from the location C:\EARS\app.ear on the machine "host1" We then specified that the location from which the ear would be available would be \\host1\ears\app.ear which is the same location simply specified as a network drive.
    An Ant task, not the wldeploy task, copies the ear we want from any development machine to the networked host1 location. This step works fine.
    Then we try to redeploy using the wldeploy task. This only seems to work if the ear file we're trying to deploy is newer than the one we already had running.
    The task was as follows, with all options valid and one target server specified in targets:
              <wldeploy action="redeploy"
                   source="${source}"
                   name="${appname}"
                   user="${user}"
                   password="${pass}"
                   verbose="true"
                   adminurl="${adminurl}"
                   debug="true"
                   targets="${targets}">
              </wldeploy>
    Source is specified as \\host1\ears\app.ear
    Since then, we've been changing all kinds of options in wldeploy trying to get it to work for older ears, but it won't.
    extract from one of many log files showing wldeploy logging for an older ear. In this case, we're trying to replace deployed version built at 10:30 with version built at 10:22. It shows successful but the version from 10:30 is still deployed on the managed server ManagedServer1 after the redeploy. The task is:
              <wldeploy action="redeploy"
                   retiretimeout="1"
                   source="${source}"
                   name="${appname}"
                   user="${user}"
                   password="${pass}"
                   verbose="true"
                   adminurl="${adminurl}"
                   debug="true"
                   graceful="false"
                   targets="${targets}">
              </wldeploy>
    copy_ear:
    [delete] Deleting 1 files from \\HOST1\EARS
    [copy] Copying 1 file to \\HOST1\EARS
    weblogic_redeploy:
    [echo] message="ant wldeploy classpath is: /bea/weblogic92/server/lib/weblogic.jar"
    [wldeploy] weblogic.Deployer -debug -verbose -noexit -name app1 -source \\host1\ears\app.ear -targets ManagedServer1 -adminurl t3://host1:5001 -user weblogic -password ******** -redeploy -retiretimeout 1
    [wldeploy] weblogic.Deployer invoked with options: -debug -verbose -noexit -name app1 -source \\host1\ears\app.ear -targets ManagedServer1 -adminurl t3://host1:5001 -user weblogic -redeploy -retiretimeout 1
    [wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at host1:5001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using t3://host1:5001
    [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://host1:5001/jndi/weblogic.management.mbeanservers.domainruntime
    [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://host1:5001/jndi/weblogic.management.mbeanservers.runtime
    [wldeploy] [DomainManager.resetDomain():36] : Getting new domain
    [wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@40ece0
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@40ece0
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1954f89
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1954f89
    [wldeploy] [ServerConnectionImpl.initialize():171] : Connected to WLS domain: OGPDomain
    [wldeploy] [ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]e9
    [wldeploy] [BasicOperation.dumpTmids():690] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():692] : {Target=ManagedServer1, WebLogicTargetType=server, Name=app1}, targeted=true
    [wldeploy] [RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: \\host1\ears\app.ear
    [wldeploy] [RedeployOperation.setupPaths():95] : redeploy src path: \\host1\ears\app.ear
    [wldeploy] [BasicOperation.deriveAppName():139] : appname established as: app1
    [wldeploy] <08-Aug-2007 10:18:00 o'clock IST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, app1 [archive: \\host1\ears\app.ear], to ManagedServer1 .>
    [wldeploy] [BasicOperation.dumpTmids():690] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():692] : {Target=ManagedServer1, WebLogicTargetType=server, Name=app1}, targeted=true
    [wldeploy] [BasicOperation.loadGeneralOptions():607] : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] ManagedServer1
    [wldeploy] ModuleTargets={}
    [wldeploy] SubModuleTargets={}
    [wldeploy] }
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy] Deployment Plan: null
    [wldeploy] App root: C:\dev\RELEASE\config\deployments\conord\app1
    [wldeploy] App config: C:\dev\RELEASE\config\deployments\conord\app1\plan
    [wldeploy] Deployment Options: {isRetireGracefully=false,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=app1,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0}
    [wldeploy] [BasicOperation.execute():424] : Initiating redeploy operation for app, app1, on targets:
    [wldeploy] [BasicOperation.execute():426] : ManagedServer1
    [wldeploy] [RedeployOperation.initializeTask():55] : Starting task with path: \\host1\ears\app.ear
    [wldeploy] Task 69 initiated: [Deployer:149026]deploy application app1 on ManagedServer1.
    [wldeploy] Task 69 completed: [Deployer:149026]deploy application app1 on ManagedServer1.
    [wldeploy] Target state: redeploy completed on Server ManagedServer1
    [wldeploy]
    [wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
    [wldeploy] [ServerConnectionImpl.closeJMX():374] : Closed JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection
    install_app:
    install_app:
    BUILD SUCCESSFUL
    Total time: 21 seconds
    Thanks for your time,
    ConorD

    Daniel Greeney wrote:
    So I just purchased an internal drive (separate from my system drive) to use as a Time Machine drive, for both of my computers (only one partition). Since they will be backing up every day, I will retain much more recent material in case of drive failure.
    Let Time Machine back up every hour, as it's designed. That will protect you best.
    My question is this - if I have a drive failure on my current internal system drive, and the internal Time Machine is intact, is it possible for me to take my external bootable backup (say 3 weeks older than Time Machine in how recently it was backed up), make a cone of that on a new internal system drive, and then use Time Machine to restore that drive to what is most current on Time Machine?
    Does this question make sense?
    The question makes sense until you realize that Time Machine backups contain everything you need (unless you do something silly, like exclude your system files).
    Once the new drive is installed and formatted, you can restore your entire system from the TM backups faster than you can copy the clone to the new internal HD. See #14 in the Frequently Asked Questions *User Tip,* also at the top of this forum. Note that you use the Snow Leopard Install disc only for the Installer on it; you don't install OSX from it.

  • How to identify the Exploded EAR name from the UI

    Hi,
    I need to do a customization in a page, "Manage Employment" (of 'Human Resources' product family)using Jdeveloper. Is there a way to find the corresponding EAR file from the UI.
    When I searched in the UNIX box (under /xx/oracle/fapp/products/fusionapps/applications/hcm/deploy) I can see Ext*.jar file in the following EAR directories.
    [ora@xxxxxxxxx deploy]$ find . -name Ext*.jar
    ./EarHcmCore.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmCoreExternal.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmTalent.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmCompensation.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmPayroll.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmBenefits.ear/APP-INF/lib/ExtHcmCustomization.jar
    ./EarHcmCoreSetup.ear/APP-INF/lib/ExtHcmCustomization.jar
    Which JAR file should I take to customize? Is the file same under different exploded EAR directories. Please let me know.
    Thanks,

    Hi Jani,
    I moved the entire EAR directory and the Ext*.jar to my local machine and created the "Customization Application Workspace". I was able to find out the View object to be customized
    using the Filter of 'Customizable Archive' as you suggested.
    But when I try to edit the page, the Jdeveloper seems to be hanged and I get the following error in the log.
    Apr 23, 2013 12:35:52 AM oracle.javatools.buffer.ReadWriteLock traceDeadlock
    SEVERE: lock deadlock; thread 'AWT-EventQueue-0' blocked on lock 'BenefitsServic
    eCenter.jsff' for more than 20,000ms:
    "AWT-EventQueue-0" id=15, blocked, no reads, no writes, no history collected:
    at oracle.javatools.buffer.ReadWriteLock.writeLock(ReadWriteLock.java:34
    6)
    at oracle.javatools.buffer.AbstractTextBuffer.writeLock(AbstractTextBuff
    er.java:1045)
    at oracle.ide.model.TextNode$FacadeTextBuffer.writeLock(TextNode.java:13
    88)
    at oracle.mds.internal.dt.dom.MDSDomModelPlugin.acquireWriteLockDirectly
    (MDSDomModelPlugin.java:1350)
    at oracle.bali.xml.dom.impl.DomModelImpl._acquireWriteLock(DomModelImpl.
    java:1632)
    at oracle.bali.xml.dom.impl.DomModelImpl.acquireWriteLock(DomModelImpl.j
    ava:486)
    I use the below memory setting in the Jdev start command script.
    set USER_MEM_ARGS=-Xms256m -Xmx1250m -XX:MaxPermSize=1024m -XX:CompileThreshold=8000
    Also I have done the appropriate memory settings in jdev.conf and ide.conf files as suggested in the Fusion Applications Developer guide.
    Can you please help?
    Thanks,

  • Partial redeployment of archived app

    Hello.
    So, as in subj:
    What I have: deployed war on weblogic, with a single jsp inside
    What I want: to redeploy only that jsp without redeploying entire war.
    When I try to use partial redeployment task with deltaFiles specified, I get DeploymentException: A partial update of an archived application is not allowed.
    It is fully described here
    http://download.oracle.com/docs/cd/E11035_01/wls100/messages/DeployerRuntime.html
    But
    I wonder if there is some walkaround of this situation, maybe somebody has done smth similar.
    Thanks in advance

    Hi Frf,
    You can partially deploy some part of your applications on the Server like following: http://jaysensharma.wordpress.com/2010/02/08/redeploying-a-single-jsp/
    In your ANT Task you can write then following to update new resources (Classes) in your WAR ...:
    <target name=”reBuildWAR”>
    <font color=maroon>
    <war destfile=”YourWarArchieve.war” update=”true”>
    <classes dir="dest/"/>
    </war>
    </font>
    </target>
    To Change the Library of your App:
    <target name=”reBuildWAR”>
    <font color=maroon>
    <war destfile=”YourWarArchieve.war” update=”true”>
    <lib dir="someLocation/jars">
    <exclude name="ojdbc14.jar"/>
    </lib>
    </war>
    </font>
    </target>
    To Change the JSPs of your App:
    <target name="reBuildWAR">
    <font color=maroon>
    <war destfile="${war.name}" update=”true”>
    <fileset dir="${jsps}"/>
    </war>
    </font>
    </target>
    .Thanks
    Jay SenSharma

  • Classpath problem in exploded ear

    I'm having problems deploying an application in a new environment. We deploy Mercury.ear as an exploded ear under
    Windows in a single-server domain without any problem.
    I am tasked with setting up a WL cluster as the first step in our cluster certification/testing (under Linux/RedHat ASE 3.0).
    We are using WL 8.1. SP2. This should be a relatively trivial task, but I must be missing something obvious,
    because I've been banging my head on it the last couple of days.
    Basically, I have two WL managed servers, ClusterMember1 and ClusterMember2 and an admin server AdminServer created in a WL domain.
    All servers start normally (when no applications are deployed to the managed servers).
    I have appended our entire config.xml to the end of this post, but here is the relevant <Application> section:
    <Application Name="Mercury"
    Path="/root/bea/user_projects/domains/clusterdomain/applications/Mercury"
    StagingMode="nostage" TwoPhase="true">
    <EJBComponent Name="MercuryEJB.jar" Targets="ClusterMember1" URI="MercuryEJB.jar"/>
    <WebAppComponent Name="Apollo" Targets="ClusterMember1" URI="MercuryWeb.war"/>
    <ConnectorComponent Name="SpectraConnector.rar"
    Targets="ClusterMember1" URI="SpectraConnector.rar"/>
    </Application>
    I am only attempting to deploy to managed server ClusterMember1 at this time.
    When I attempt to start ClusterMember1:
    ./startManagedWebLogic.sh ClusterMember1 http://localhost:9001 &
    It starts up, syncs with the admin server, and then attempts to deploy the Mercury application. I get the following exception when it attempts to start the Mercury application:
    <Feb 1, 2006 10:07:55 AM CST> <Error> <HTTP> <BEA-101216> <Servlet: "context" failed to preload on startup in Web application: "Apollo".
    javax.servlet.ServletException: Error registering bean with name 'ApolloSessionManager' defined in URL [file:/root/bea/user_projects/domains/clusterdomain/applications/Mercury/mercuryresources.jar/resources/xml/springconfig/Service-DAO-config.xml]: Class that bean class [com.sg.sims.mercury.apolloweb.service.processor.ApolloSessionManager] depends on not found; nested exception is java.lang.NoClassDefFoundError: com/sg/sims/mercury/apolloweb/service/processor/ApolloSessionManager
         at weblogic.servlet.internal.ServletStubImpl.createServlet()Ljavax/servlet/Servlet;(ServletStubImpl.java:985)
    {...snipped...}
    Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'ApolloSessionManager' defined in URL [file:/root/bea/user_projects/domains/clusterdomain/applications/Mercury/mercuryresources.jar/resources/xml/springconfig/Service-DAO-config.xml]: Class that bean class [com.sg.sims.mercury.apolloweb.service.processor.ApolloSessionManager] depends on not found; nested exception is java.lang.NoClassDefFoundError: com/sg/sims/mercury/apolloweb/service/processor/ApolloSessionManager
         at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinition(Lorg/w3c/dom/Element;Ljava/lang/String;)Lorg/springframework/beans/factory/config/BeanDefinition;(DefaultXmlBeanDefinitionParser.java:366)
    {...snipped...}
    Caused by: java.lang.NoClassDefFoundError: com/sg/sims/mercury/apolloweb/service/processor/ApolloSessionManager
         at java.lang.Class.forName(Ljava/lang/String;ZLjava/lang/ClassLoader;)Ljava/lang/Class;(Unknown Source)
         at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(Ljava/lang/String;Ljava/lang/String;Lorg/springframework/beans/factory/config/ConstructorArgumentValues;Lorg/springframework/beans/MutablePropertyValues;Ljava/lang/ClassLoader;)Lorg/springframework/beans/factory/support/AbstractBeanDefinition;(BeanDefinitionReaderUtils.java:50)
    {...snipped...}
    Clearly, Spring can't find the ApolloSessionManager class (or one of its dependent classes, the error message is somewhat unclear in places).
    However, the ApolloSessionManager.class file is there, under the mercurybusiness.jar directory (with package structure).
    // from ${DOMAIN_HOME}/applications/Mercury:
    ls -la mercurybusiness.jar/com/sg/sims/mercury/apolloweb/service/processor/ApolloSessionManager
    -rw-r--r-- 1 root root 7162 Jan 31 17:20 mercurybusiness.jar/com/sg/sims/mercury/apolloweb/service/processor/ApolloSessionManager.class
    mercurybusiness.jar (in turn) is present in the MercuryEJB.jar MANIFEST.MF file:
    // ${DOMAIN_HOME}/applications/Mercury/MercuryEJB.jar/META-INF/MANIFEST.MF:
    Manifest-Version: 1.0
    Ant-Version: Apache Ant 1.6.1
    Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
    Class-Path: mercurycommon.jar mercuryresources.jar mercurybusiness.jar mercuryserviceflow.jar mercuryutils.jar spectraconnector.rar {...snipped...}
    The same situation appears for the classes that ApolloSessonManager depends on: MercuryLogger (a log4j wrapper) and the HTTPClient.jar classes
    (e.g. Cookie, etc), except 3rd party jars are listed in the MANIFEST.MF of MercuryEJB.jar but are not exploded.
    There is no weblogic-application.xml file to override the default classloader hierarchy, so my understanding
    is that everything in the application should share a single classloader.
    So I am at a loss to understand why classes in MercuryWeb.war can not load classes in dependent jars of MercuryEJB.jar.
    As a note, if I add /root/bea/user_projects/domains/clusterdomain/applications/Mercury/mercurybusiness.jar to the CLASSPATH variable in startManagedWebLogic.sh,
    this error disappears of course, and it barfs on the next application class it can't find (in one of the other exploded jars that MercuryEJB.jar depends on.
    Can someone help point out what I may be missing?
    Chris Goodacre
    // config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <Domain ConfigurationVersion="8.1.5.0" Name="clusterdomain">
    <Server Cluster="SIMS_TEST_CLUSTER_1" ListenAddress=""
    ListenPort="9001" Name="AdminServer" NativeIOEnabled="true"
    ReliableDeliveryPolicy="RMDefaultPolicy" ServerVersion="8.1.5.0">
    <SSL Enabled="false" HostnameVerificationIgnored="false"
    IdentityAndTrustLocations="KeyStores" Name="AdminServer"/>
    </Server>
    <WSReliableDeliveryPolicy DefaultRetryCount="10"
    DefaultTimeToLive="60000" Name="RMDefaultPolicy" Store="FileStore"/>
    <Security Name="clusterdomain"
    PasswordPolicy="wl_default_password_policy"
    Realm="wl_default_realm" RealmSetup="true"/>
    <EmbeddedLDAP
    CredentialEncrypted="{3DES}dMeE/vNpCcbjzOMZGfNeShv5VFZuQ=" Name="clusterdomain"/>
    <SecurityConfiguration
    CredentialEncrypted="{3DES}jFRG5NzABP8IAJa5M/PNNRCtZYaqkc2zUTYjlysL+md+TAgZw6IfgCjzzre4e7p5gyJEt+0UkPXNleN0QtW7Ef"
    Name="clusterdomain" RealmBootStrapVersion="1"/>
    <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
    <FileRealm Name="wl_default_file_realm"/>
    <PasswordPolicy Name="wl_default_password_policy"/>
    <JMSConnectionFactory DefaultDeliveryMode="Non-Persistent"
    JNDIName="jms/ConnectionFactory" Name="ConnectionFactory" Targets="AdminServer"/>
    <JMSFileStore Directory="rmfilestore" Name="FileStore"/>
    <JMSServer Name="WSStoreForwardInternalJMSServerAdminServer"
    Store="FileStore" Targets="AdminServer">
    <JMSQueue CreationTime="1123128740234"
    JNDIName="jms.internal.queue.WSStoreForwardQueue"
    JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSStoreForwardQueueAdminServer"/>
    <JMSQueue CreationTime="1123128740390"
    JNDIName="jms.internal.queue.WSDupsEliminationHistoryQueue"
    JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSDupsEliminationHistoryQueueAdminServer"/>
    <JMSQueue CreationTime="1123128837453" JNDIName="jms/MenuQueue"
    Name="MenuQueue" StoreEnabled="false"/>
    <JMSQueue CreationTime="1123128864296"
    JNDIName="jms/MenuXMLQueue" Name="MenuXMLQueue" StoreEnabled="false"/>
    <JMSQueue CreationTime="1123128892343"
    JNDIName="jms/DataSyncQueue" Name="DataSyncQueue" StoreEnabled="false"/>
    <JMSQueue CreationTime="1123128915421"
    JNDIName="jms/LoginRefreshQueue" Name="LoginRefreshQueue" StoreEnabled="false"/>
    <JMSQueue CreationTime="1123128937046"
    JNDIName="jms/ProfileQueue" Name="ProfileQueue" StoreEnabled="false"/>
    <JMSQueue CreationTime="1123128957125"
    JNDIName="jms/ReportsQueue" Name="ReportsQueue" StoreEnabled="false"/>
    </JMSServer>
    <Cluster Name="SIMS_TEST_CLUSTER_1"/>
    <Server Cluster="SIMS_TEST_CLUSTER_1" ExpectedToRun="false"
    ListenPort="9999" Name="ClusterMember1" ServerVersion="8.1.5.0">
    <ServerDebug Name="ClusterMember1"/>
    <SSL IdentityAndTrustLocations="KeyStores" Name="ClusterMember1"/>
    <KernelDebug Name="ClusterMember1"/>
    <Log Name="ClusterMember1"/>
    <ServerStart Name="ClusterMember1"
    PasswordEncrypted="{3DES}TC7nfOvKF0xwJB/f+tyYwQ==" Username="toolbox"/>
    <WebServer Name="ClusterMember1"/>
    <COM Name="ClusterMember1"/>
    <IIOP Name="ClusterMember1"/>
    <JTAMigratableTarget Name="ClusterMember1" UserPreferredServer="ClusterMember1"/>
    <JTARecoveryService Name="ClusterMember1"/>
    </Server>
    <MigratableTarget Cluster="SIMS_TEST_CLUSTER_1"
    Name="ClusterMember1 (migratable)"
    Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="ClusterMember1"/>
    <Server Cluster="SIMS_TEST_CLUSTER_1" ExpectedToRun="false"
    ListenPort="9998" Name="ClusterMember2" ServerVersion="8.1.5.0">
    <ServerDebug Name="ClusterMember2"/>
    <SSL IdentityAndTrustLocations="KeyStores" Name="ClusterMember2"/>
    <KernelDebug Name="ClusterMember2"/>
    <Log Name="ClusterMember2"/>
    <ServerStart Name="ClusterMember2"
    PasswordEncrypted="{3DES}TC7nfOvKF0xwJB/f+tyYwQ==" Username="toolbox"/>
    <WebServer Name="ClusterMember2"/>
    <COM Name="ClusterMember2"/>
    <IIOP Name="ClusterMember2"/>
    <JTAMigratableTarget Name="ClusterMember2" UserPreferredServer="ClusterMember2"/>
    <JTARecoveryService Name="ClusterMember2"/>
    </Server>
    <MigratableTarget Cluster="SIMS_TEST_CLUSTER_1"
    Name="ClusterMember2 (migratable)"
    Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="ClusterMember2"/>
    <JDBCConnectionPool DriverName="com.sybase.jdbc2.jdbc.SybDriver"
    Name="MercuryJDBCConnPool"
    PasswordEncrypted="{3DES}Enwr7V6DdUk="
    Properties="user=dbuser;url=jdbc:sybase:Tds:10.15.3.66:4100/ENT_60_DEV;networkProtocol=Tds;portNumber=4100;userName=dbuser;databaseName=ENT_60_DEV;serverName=10.15.3.66"
    Targets="SIMS_TEST_CLUSTER_1" TestTableName="SQL SELECT 1" URL="jdbc:sybase:Tds:10.15.3.66:4100/ENT_60_DEV"/>
    <JDBCDataSource JNDIName="jdbc/MercuryDS" Name="MercuryDS"
    PoolName="MercuryJDBCConnPool" Targets="SIMS_TEST_CLUSTER_1"/>
    <MigratableTarget Cluster="SIMS_TEST_CLUSTER_1"
    Name="AdminServer (migratable)"
    Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="AdminServer"/>
    <Application Name="Mercury"
    Path="/root/bea/user_projects/domains/clusterdomain/applications/Mercury"
    StagingMode="nostage" TwoPhase="true">
    <EJBComponent Name="MercuryEJB.jar" Targets="ClusterMember1" URI="MercuryEJB.jar"/>
    <WebAppComponent Name="Apollo" Targets="ClusterMember1" URI="MercuryWeb.war"/>
    <ConnectorComponent Name="SpectraConnector.rar"
    Targets="ClusterMember1" URI="SpectraConnector.rar"/>
    </Application>
    </Domain>
    ////////////////////////////////////////////////////////////

    Sorry, I don't have the response to your question.
    But I'd like to know how youmake your servlet and your applet communicate.
    I'm building a web site using both applets and servlet. And I nned to make them communicate. I'm trying to use RMI but I get many problems.
    Can I know Which solution you have chosen for applet-servlet communication ?
    Thank's.

  • Deploying jars within a single (exploded) ear

    Our project currently uses 8.1 SP3 with split deployment structure.
    Currently the project is split into multiple ears deployed on a single (managed) server. It is my understanding that calls made across ear's even on the same server (jvm) need to be marshalled and unmarshalled using pass by value.
    We are trying to consolidate all our EJBs and Web apps into a single .ear so that we can take advantage of call-by-reference. We also have a requirement of being able to deploy "groups" of EJBs (within a single jar) and/or a web app. Deploying a single ear for the entire project would be one extreme, as it would be painful to deploy individual modules within the ear. On the other hand, using an exploded ear would be too "granular" a way of deploying our changes (we have many EJBs, etc.).
    Is it possible to deploy an exploded ear consisting of jar and war files ? I am in the process of trying this and was looking for feedback. The idea is of being able to deploy parts of the app, such as a .jar or a .war file. Can wlpackage create an exploded ear using .jar and .war files instead of modules consisting of .java/.jsp, etc. files? Thanks for your help!

    There is a classpath issue. Normally ejbs are loaded on top of the ears classpath, so whenever you redeploy them, you have to redeploy the webapps, too. In 8.1 you can build your custom class loader hierarchy. Take a look at http://e-docs.bea.com/wls/docs81/programming/classloading.html#1065667
    -Kai

  • Partial redeployment of a static jar file with weblogic.Deployer

    Hello,
    We are working on an application serving jar files to customers, via Java Web Start, hence that are considered from our point of view as static files, like our HTML and Javascript pages.
    Moreover, we have one jar that changes regularly, so every time it's loaded on the server we need to do a partial redeployment of this jar file, as documented here: http://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/redeploy.html#wp1025739
    However, it does not work, as I believe WebLogic doesn't consider my jar file as a static file.
    C:\>java -cp weblogic.jar weblogic.Deployer -adminurl http://mymachine:7001 -user weblogic -password mystrongpassword -name myapp -redeploy launcher/downloadme.jar
    weblogic.Deployer invoked with options: -adminurl http://mymachine:7001 -user weblogic -name myapp -redeploy launcher/downloadme.jar
    <Mar 8, 2013 7:09:36 PM CET> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, myapp [archive: null], to configured targets.>
    Task 24 initiated: [Deployer:149026]redeploy application myapp [Version=7] on WebServer.
    Task 24 failed: [Deployer:149026]redeploy application myapp [Version=7] on WebServer.
    Target state: redeploy failed on Server WebServer
    weblogic.management.DeploymentException:
    The application myapp#7 cannot have the resource launcher/downloadme.jar updated dynamically. Either:
    1.) The resource does not exist.
    or
    2) The resource cannot be changed dynamically.
    Please ensure the resource uri is correct, and redeploy the entire application for this change to take effect.
    As a side note, if I rename downloadme.jar to downloadme.jar.*html*, then WebLogic agrees to redeploy it!
    Is there any way to force the static redeployment of my jar file?
    Thanks and regards,
    Julien

    Hi,
    The feature you are trying to use works only when web application is deployed in exploded format. Is your app deployed in exploded format?
    Also jars are never considered static, so I doubt this will work here.
    As an alternative you can go for Oracle Weblogic Production redployment feature. Refer to - http://middlewaresupport.wordpress.com/2013/03/21/production-redeployment-feature-in-weblogic/
    Thanks,
    Ranjan
    Edited by: Ranjan K on Apr 12, 2013 5:45 AM

  • 10.1.3 bugs - redeployment of an EAR. Toplink and PermGen related

    This is very annoying! We're trying to use the OC4J 10.1.3 specific ant task to perform redeployment of our application. Basically we see, that redeployment of an EAR can't be performed successfully - (this can be reproduced from within OEM).
    By specifying orion-application.xml specific settings, we're forcing our application not to use the toplink shared library. All required libraries are part of our EAR file.
    There are two things noteworthy about this.
    1) Upon calling redeploy, the appserver is unable to remove the toplink.jar file which is stored in the libs directory of the respective EAR. I have no clue why this is happening, but it looks like the appserver is now holding on to our toplink.jar which is part of the application.
    2) Retrying this step, leads to a PermGen Out-of-Memory error.
    I'm hoping one of the Oracle gurus can comment on this (quickly ;-) )
    BTW; we're using OC4J standalone for development.

    To give some more info, here is the output I get upon redeploy:
    D:\oc4j10.1.3.0.0\j2ee\home\applications\NLSIS
    java.io.IOException:Unable to remove D:\oc4j10.1.3.0.0\j2ee\home\applications\NLSIS
      at oracle.oc4j.util.FileUtils.recursiveRemove(FileUtils.java:249)
      at oracle.oc4j.admin.internal.ApplicationUnDeployer.removeFiles(ApplicationUnDeployer.java:146)
      at oracle.oc4j.admin.internal.ApplicationUnDeployer.doUndeploy(ApplicationUnDeployer.java:117)
      at oracle.oc4j.admin.internal.UnDeployerBase.execute(UnDeployerBase.java:91)
      at oracle.oc4j.admin.internal.UnDeployerBase.execute(UnDeployerBase.java:72)
      at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JUnDeployerRunnable.doRun(OC4JUnDeployerRunnable.java:46)
      at oracle.oc4j.admin.jmx.server.mbeans.deploy.UnDeployerRunnable.run(UnDeployerRunnable.java:69)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
      at java.lang.Thread.run(Thread.java:595)
    2006-05-03 14:41:15.368 WARNING WARNING: Unable to remove appDir D:\oc4j10.1.3.0.0\j2ee\home\applications\NLSIS
      : Unable to remove D:\oc4j10.1.3.0.0\j2ee\home\applications\NLSIS
    2006-05-03 14:41:15.462 NOTIFICATION Application UnDeployer for NLSIS COMPLETES.

  • Deploying Portal App in exploded EAR format

    Hi all,
    We are using Portal BEA 8.1 SP2 and we also configured a cluster with
    production mode enabled.
    We want to deploy our portal app in exploded EAR format.
    http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
    But when we use workshop to "Build App" and when the application build is successful.
    And when we copy the App folder to the production server and deploy,
    We get the following error,
    [Deployer:149033]preparing application commApp on mgServer1
    [Deployer:149033]preparing application commApp on mgServer2
    [Deployer:149033]failed application commApp on mgServer1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
    Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
    [Deployer:149033]failed application commApp on mgServer2
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
    Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
    What is the problem ?
    Thanks,
    Karthi.
    [att1.html]

    To deploy the app as EAR (I am confused by the expression "exploed EAR", my understanding
    its either exploded or EAR format) build the app as EAR (there is an option in
    the workshop build drop down).
    Did this help?
    S
    "Karthi" <[email protected]> wrote:
    >
    >
    Hi all,
    We are using Portal BEA 8.1 SP2 and we also configured a cluster with
    production mode enabled.
    We want to deploy our portal app in exploded EAR format.
    http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
    But when we use workshop to "Build App" and when the application build
    =
    is successful.=20
    And when we copy the App folder to the production server and deploy,=20
    We get the following error,
    [Deployer:149033]preparing application commApp on mgServer1
    [Deployer:149033]preparing application commApp on mgServer2
    [Deployer:149033]failed application commApp on mgServer1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
    =
    application commApp on devCluster,bkarthiPS.:=20
    Exception:weblogic.management.ApplicationException: Application commApp
    =
    is packaged using the WebLogic Split Development Directory structure.
    =
    The Split Development Directory structure can only be used in =
    development environments with a single WebLogic Server. If you wish to
    =
    deploy this application to a separate managed server or cluster, use
    the =
    wlpackage ant task to create an exploded or archived EAR.
    [Deployer:149033]failed application commApp on mgServer2
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
    =
    application commApp on devCluster,bkarthiPS.:=20
    Exception:weblogic.management.ApplicationException: Application commApp
    =
    is packaged using the WebLogic Split Development Directory structure.
    =
    The Split Development Directory structure can only be used in =
    development environments with a single WebLogic Server. If you wish to
    =
    deploy this application to a separate managed server or cluster, use
    the =
    wlpackage ant task to create an exploded or archived EAR.
    What is the problem ?
    Thanks,
    Karthi.
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML><HEAD>
    <META http-equiv=3DContent-Type content=3D"text/html; =
    charset=3Diso-8859-1">
    <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
    <STYLE></STYLE>
    </HEAD>
    <BODY bgColor=3D#c0c0c0 background=3D"">
    <DIV><FONT face=3DArial size=3D2>Hi all,<BR><BR>We are using Portal BEA
    =
    8.1 SP2 and=20
    we also configured a cluster with<BR>production mode enabled.<BR><BR>We
    =
    want to=20
    deploy our portal app in exploded EAR=20
    format.<BR><BR>http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723=
    <BR><BR>But=20
    when we use workshop to "Build App" and when the application build is=20
    successful. <BR><BR>And when we copy the App folder to the production
    =
    server and=20
    deploy, <BR><BR>We get the following =
    error,<BR><BR>[Deployer:149033]preparing=20
    application commApp on mgServer1<BR>[Deployer:149033]preparing =
    application=20
    commApp on mgServer2<BR>[Deployer:149033]failed application commApp on=20
    mgServer1<BR>[Deployer:149034]An exception occurred for task=20
    [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
    <BR>Exception:weblogic.management.ApplicationException: Application =
    commApp is=20
    packaged using the WebLogic Split Development Directory structure. The
    =
    Split=20
    Development Directory structure can only be used in development =
    environments=20
    with a single WebLogic Server. If you wish to deploy this application
    to =
    a=20
    separate managed server or cluster, use the wlpackage ant task to create
    =
    an=20
    exploded or archived EAR.<BR>.<BR>[Deployer:149033]failed application
    =
    commApp on=20
    mgServer2<BR>[Deployer:149034]An exception occurred for task=20
    [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
    <BR>Exception:weblogic.management.ApplicationException: Application =
    commApp is=20
    packaged using the WebLogic Split Development Directory structure. The
    =
    Split=20
    Development Directory structure can only be used in development =
    environments=20
    with a single WebLogic Server. If you wish to deploy this application
    to =
    a=20
    separate managed server or cluster, use the wlpackage ant task to create
    =
    an=20
    exploded or archived EAR.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    <DIV><FONT face=3DArial size=3D2>What is the problem ?</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    <DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>Karthi.</FONT></DIV></BODY></HTML>

  • Infinity, what is it like, will I be blown away?

    I am expecting our cab to go live in the next week or two after waiting over two years.
    We will be going from the 1.75 / 0.3 mbit adsl slow lane, to the 62 / 20 mbit vdsl fastlane.
    Will I feel blown away, will life never be the same again?
    How will I feel once it is installed and how long does the good feeling last?

    rabbit wrote:
    Will I feel blown away, will life never be the same again?
    How will I feel once it is installed and how long does the good feeling last?
    From the speeds you were on, yes I think it will be a surge of interest... however as the others have said, it's does not last long... it's called human nature
    What you WILL find is that many (I daresay the majority) of hosts where you will download the big files from, are actually painfully slow anyway.. so you won't get the benefit.
    What you will also find is you can do new things enjoyably that were a pain before, streaming music, catchup TV and Youtube without the jitters. And uploads to Facebook and sending email are more fun... you will drink less tea and coffee that you would have had waiting for stuff to upload
    Enjoy it while it lasts... I suspect 3 weeks and then you'll be wanting faster!
    Be a first rate version of yourself, not a second rate version of someone else

Maybe you are looking for