Return-Path: list-help: list-unsubscribe: List-Post: List-Id: Mailing-List: contact cactus-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list cactus-user@jakarta.apache.org Received: (qmail 31808 invoked from network); 31 Mar 2004 08:56:47 -0000 Received: from unknown (HELO if113.bacs.co.uk) (81.144.234.222) by daedalus.apache.org with SMTP; 31 Mar 2004 08:56:47 -0000 Received: from SPR304.office.local (msw.office.local [10.96.50.18]) by if113.bacs.co.uk (8.12.10+Sun/8.12.10) with ESMTP id i2V8uvTO028776 for ; Wed, 31 Mar 2004 09:56:58 +0100 (BST) Received: from SOW2K301.office.local (unverified) by SPR304.office.local (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Wed, 31 Mar 2004 09:56:52 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Weblogic 8.1 deploy issue X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Date: Wed, 31 Mar 2004 09:56:52 +0100 Message-ID: <05F265D990C8C141A719D1FB3ED8CA4A6E112A@SOW2K301.office.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Weblogic 8.1 deploy issue Thread-Index: AcQSZtU7W7iG5tlFQmyLbyGNsuQ5KgAAH6GQAAE5MxAAA8UE8AAEbU4AAP5SCyAAHZ008A== From: "Darren Witham" To: "Cactus Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thx - Mark yes I ran into that one. I took a bit more of a sledgehammer = solution and added the relevant jar file to the Cactus libs. Will look = at this suggestion. FYI - the reason I was unable to deploy even a bulk standard cactified = WAR was something to do with using the J2EE 1.3 version against WLS 8.1. = I reverted back to 1.2 and it deployed fine. I have not had time to = investigate why that might be the case, for the time being I am just = happy to be able to run Cactus tests..... -----Original Message----- From: Mark Lybarger [mailto:Mark.Lybarger@CBC-Companies.com] Sent: 30 March 2004 19:46 To: Cactus Users List Subject: RE: Weblogic 8.1 deploy issue Darren, I just ran into some snags with wls 8.1. It seems they (by default) = override the LogFactory setting for the commons-logging, but fail to = make available (by default) the implementation that they require. See = the following: http://dev2dev.bea.com/products/wlworkshop81/articles/workshopfaqs.jsp IIRC, cactus is also using commons-logging. You might want to try the = suggestion of bea (if you're not on sp2) and put a blank = commons-logging.properties on your server classpath. Let me know if = this helps. ~mark > -----Original Message----- > From: Darren Witham [mailto:Darren.Witham@bacs.co.uk] > Sent: Thursday, March 25, 2004 12:31 PM > To: Cactus Users List > Subject: RE: Weblogic 8.1 deploy issue >=20 >=20 >=20 > Regardless of the Ant task etc if I drop a cactified WAR into=20 > the apps dir of Weblogic it attempts to hot deploy and fails.=20 > The WAR itself only contains the following : >=20 > META-INF/ > META-INF/MANIFEST.MF > jspRedirector.jsp > WEB-INF/ > WEB-INF/web.xml > WEB-INF/lib/ > WEB-INF/lib/aspectjrt-1.1.1.jar > WEB-INF/lib/cactus-1.5.jar > WEB-INF/lib/commons-logging-1.0.3.jar > WEB-INF/lib/commons-httpclient-2.0-rc2.jar > WEB-INF/lib/junit.jar >=20 > I might be missing the point but I assumed that at least this=20 > should deploy ??? >=20 >=20 >=20 > -----Original Message----- > From: Mark Lybarger [mailto:Mark.Lybarger@CBC-Companies.com] > Sent: 25 March 2004 15:17 > To: Cactus Users List > Subject: RE: Weblogic 8.1 deploy issue >=20 >=20 > I'm not familiar with what needs done to properly initialize=20 > the cactified war. Maybe someone else can elaborate. =20 > Perhaps it's just a classpath type of thing. >=20 > Are you using weblogic provided ant tasks to deploy your=20 > application? Can you run your server in development mode=20 > (non-production) to let the cactified war auto deploy when=20 > it's placed into the applications folder? Only thing i can=20 > think of is that things are getting put into the classpath=20 > when running the ant task that cactus doesn't like. IIRC,=20 > wls includes their own older version of ant (1.5.3) which may=20 > or may not impact things. Personally, I stay clear of=20 > weblogic's ant tasks since they lock you into that ant version. >=20 >=20 > > -----Original Message----- > > From: Darren Witham [mailto:Darren.Witham@bacs.co.uk] > > Sent: Thursday, March 25, 2004 8:27 AM > > To: Cactus Users List > > Subject: RE: Weblogic 8.1 deploy issue > >=20 > >=20 > > Hi Mark, > >=20 > > Thanks for reply. I attempted to deploy just a plain test=20 > > war that I created as you suggest : > >=20 > > . > >=20 > > This still fails so it is something silly ??????? Outside=20 > > of the logs the deployer churns out the following : > >=20 > > Deploying: coreservices-cactus-test.ear > > [java] Initiated Task: [9] [Deployer:149026]Deploy=20 > > application coreservices-cactus-test on cgServer. > > [java] Application coreservices-cactus-test preparing on=20 > > server cgServer. > > [java] Module testcact: unprepared to prepared on server=20 > > cgServer. > > [java] Application coreservices-cactus-test prepared on=20 > > server cgServer. > > [java] Application coreservices-cactus-test activating=20 > > on server cgServer. > > [java] Module testcact: prepared to active on server cgServer. > > [java] Application coreservices-cactus-test failed on=20 > > server cgServer. > > [java] Module testcact: active to prepared on server cgServer. > > [java] Module testcact: prepared to unprepared on server=20 > > cgServer. > > [java] Task 9 failed: [Deployer:149026]Deploy=20 > > application coreservices-cactus-test on cgServer. > > [java] Deployment failed on Server cgServer > > [java] weblogic.management.DeploymentException: > > [java]=20 > > Exception:weblogic.management.ApplicationException: start() failed. > > [java] Module: testcact Error:=20 > > java.lang.ExceptionInInitializerError > >=20 > > Thx > >=20 > > -----Original Message----- > > From: Mark Lybarger [mailto:Mark.Lybarger@CBC-Companies.com] > > Sent: 25 March 2004 13:01 > > To: Cactus Users List > > Subject: RE: Weblogic 8.1 deploy issue > >=20 > >=20 > > Darren, > >=20 > > Are you able to deploy a plain jane cactified war? Using=20 > > something like this: > > > > I'm only using cactus to test ejbs with wls 8.1 right now. =20 > > We don't have any client items that we can easily test using=20 > > cactus (turbine/velocity framework). Someone correct me if=20 > > i'm wrong, but all cactus needs on the cactified war side is=20 > > to have the .class files of the tests and all classes needed=20 > > to invoke the tests classes. maybe some supporting jars as=20 > > well (web-inf/lib). For ejbs this means having remote=20 > > interfaces available. Then cactus will proxy off to the=20 > > actual running component. So for me, I deploy a=20 > > cactifiedwar, and our ear which contains only ejbs and=20 > > supporting jar files. The cactified war contains (as a=20 > > convenience) all our class files, but not deployment=20 > > descriptors or anything like that. the beans the war uses are=20 > > the beans deployed as part of our ear. > >=20 > > I've found Weblogic's error messages to be cryptic and hard=20 > > to track down. A rough guess would be that something in your=20 > > app (within the cactified war) wasn't able to initialize so=20 > > it bailed out. that's probably way off, probably would need=20 > > more info from the log file to help better determine the cause. =20 > >=20 > > Maybe you can try to deploy your war, as well as a cactified=20 > > war that contains just your class files and web-inf/lib=20 > > folder to the same server (maybe you just have one in=20 > > development), and see how that goes? > >=20 > > > -----Original Message----- > > > From: Darren Witham [mailto:Darren.Witham@bacs.co.uk] > > > Sent: Thursday, March 25, 2004 7:44 AM > > > To: cactus-user@jakarta.apache.org > > > Subject: Weblogic 8.1 deploy issue > > >=20 > > >=20 > > > Hi, > > >=20 > > > I am having some issues deploying a cactified WAR onto Weblogic. > > >=20 > > > I am simply creating a WAR file using ANT and then applying=20 > > > the task. When I examine what this task has done=20 > > > I see that the web.xml file has been modified and a few=20 > > > libraries added to WEB-INF/lib as expected. However when I=20 > > > attempt to deploy this WAR either via ANT (using=20 > > > Weblogic.deploy) or simply attempting to hot deploy it,=20 > > > Weblogic complains with the following : > > >=20 > > > [java]=20 > > > Exception:weblogic.management.ApplicationException:=20 > start() failed. > > > [java] Module: coreservices Error:=20 > > > java.lang.ExceptionInInitializerError > > >=20 > > > A further look in the logs shows : > > >=20 > > > weblogic.management.DeploymentException:=20 > > > Exception:weblogic.management.ApplicationException: start()=20 > > > failed Module: coreservices Error:=20 > > > java.lang.ExceptionInInitializerError at=20 > > > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.do > > > Commit(SlaveDeployer.java:2549 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer$Task.commit(Sla > > > veDeployer.java:2349 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoC > > > ommit(SlaveDeployer.java:2431 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(Sl > > > aveDeployer.java:2343 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.pr > > > epare(SlaveDeployer.java:2511 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer.processPrepareT > > > ask(SlaveDeployer.java:833 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Sl > > > aveDeployer.java:542 at=20 > > > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(S > > > laveDeployer.java:500 at=20 > > > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCall > > > backHandler.java:25 at=20 > > > weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197=20 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170=20 > > > The WAR file itself deploys fine prior to cactifying it.=20 > > > There is no obvious message telling me that the WAR file=20 > > > maybe be missing something it requires. > > > Any pointers appreciated........ > > > Thx > > >=20 > > >=20 > > >=20 > > > =20 > > >=20 > > >=20 > > >=20 > > >=20 > > > ----------------------------------------------------- > > >=20 > > > You can find us at www.bacs.co.uk=20 > > >=20 > > > ***************************************************** > > > This communication is confidential and intended for=20 > > > the exclusive use of the addressee only. You should=20 > > > not disclose its contents to any other person. > > > If you are not the intended recipient please notify=20 > > > the sender named above immediately. > > >=20 > > > BACS Limited, registered in England, No 1023742,=20 > > > 3 De Havilland Road, Edgware, Middlesex, HA8 5QA > > > ***************************************************** > > >=20 > > >=20 > >=20 > >=20 > >=20 > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: cactus-user-help@jakarta.apache.org > >=20 > >=20 > >=20 > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: cactus-user-help@jakarta.apache.org > >=20 > >=20 > >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: cactus-user-help@jakarta.apache.org >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: cactus-user-help@jakarta.apache.org >=20 >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: cactus-user-help@jakarta.apache.org