StartUp Class in WLS 6.0

Hi,
I am beggining to upgrade our app from Weblogic 5.1 to 6.0. So far it
has been progressing nicely and everything works with one exception. I
can not get the start up classes to run. I get the following exception:
<Failed to invoke startup class "MyStartup Class",
java.lang.ClassNotFoundException:
followed by my fully qualified class name. The class is reference
elsewhere in the code and works fine. Is a seperate classpath used for
startup classes? If not why might Weblogic have a hard time finding my
class?
Thanks,
Steve

I should be more specific and have a bit more to add....
We have our app in an .ear file. I find that when I put the startup
classes in a seperate directory which is in the classpath specified in the
startWeblogic.cmd file they will be run on startup. I don't think I should
have to do this since these files exist in the ear file. I think this is
causing other problems too such as an illegalAccessError I get when an EJB
tries to load a class which was previously accessed by the startup classes.
Thanks,
Steve
Steve Snodgrass wrote:
Hi,
I am beggining to upgrade our app from Weblogic 5.1 to 6.0. So far it
has been progressing nicely and everything works with one exception. I
can not get the start up classes to run. I get the following exception:
<Failed to invoke startup class "MyStartup Class",
java.lang.ClassNotFoundException:
followed by my fully qualified class name. The class is reference
elsewhere in the code and works fine. Is a seperate classpath used for
startup classes? If not why might Weblogic have a hard time finding my
class?
Thanks,
Steve

Similar Messages

Servlets as Startup classes in WLS 5.1

Hi,
I would like to know if:
1) a servlet can be used as a startup class in WLS 5.1. If so,
are there any restriction on what can be done inside this servlet?
Or
2) can we load a servlet from a startup class? if so? how?
any ideas?
regards,
Modou.

Not sure if this is what you are looking for, but you can mark a servlet to
be pre-loaded when the servlet runner starts.
"Modou" <[email protected]> wrote in message
news:3ac14139$[email protected]..
>
Hi,
I would like to know if:
1) a servlet can be used as a startup class in WLS 5.1. If so,
are there any restriction on what can be done inside this servlet?
Or
2) can we load a servlet from a startup class? if so? how?
any ideas?
regards,
Modou.

Order of startup servlets in WLS 5.1

          Is there any way to set the order in which servlets are started up using ServletStartup.
          I have something similar to this in my weblogic.properties file -
          weblogic.system.startupClass.StartServletA=weblogic.servlet.utils.ServletStartup
          weblogic.system.startupArgs.StartServletA=servlet=ServletA weblogic.system.startupClass.StartServletB=weblogic.servlet.utils.ServletStartup
          weblogic.system.startupArgs.StartServletB=servlet=ServletB
          I'd like ServletA to load first and then ServletB, but ServletB always seems to
          load first.
          Any ideas?
          Thanks...
          ps - using WLS 5.1, SP6


If, for some reason, you do not deploy your application as a webapp,
          you can use ServletStartup:
          http://www.weblogic.com/docs51/classdocs/API_servlet.html#128566
          > Dimitri,
          > Thanks for the response. But wouldn't this restrict me to only
          > servlets that are deployed within a WebApp? would the servlet
          > run even when the webApp is not deployed?
          > Modou.
          > Dimitri Rakitine <[email protected]> wrote:
          >>The portable way is to specify load-on-startup in the
          >>web.xml - 5.1sp7 or 8
          >>supports this (but not before).
          >>
          >>Modou <[email protected]> wrote:
          >>
          >>> Hi,
          >>> I would like to know if:
          >>> 1) a servlet can be used as a startup class in WLS 5.1.
          >>If so,
          >>> are there any restriction on what can be done inside
          >>this servlet?
          >>> Or
          >>
          >>> 2) can we load a servlet from a startup class? if so?
          >>how?
          >>
          >>> any ideas?
          >>
          >>> regards,
          >>> Modou.
          >>
          >>--
          >>Dimitri
          Dimitri

Clustering of startup classes in WebLogic

          Hi
          WE have an application running as startup class in WLS 6.1 . I want to know
          how this class can be deployed in clustered environment. Iam pretty ne to clustering
          . Can some body help me out ?.
          Thanks in advance,
          S Gopikrishna


I don't know what you mean.
          If you want each instance of your app to be running something, you should
          use a load-on-startup Servlet with its init() method instead of a startup
          class.
          If you want each instance of a server (not each instance of your app, since
          an app can be loaded multiple times on a server) to be running something,
          you should use a startup class.
          If you want exactly one instance in a cluster to be running something ...
          well, good luck. There's no guarantees in this regard, but the easiest way
          is to pin it to one server and make sure that that server never goes down
          because it is a single point of failure.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "S Gopikrishna" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi
          >
          > Thanks a lot for the reply. My startup class listens continously on a
          queue.
          > I need to know whether my startup class will also be clustered just like
          EJB.
          > If not what is the altrnative.
          >
          > Regards,
          > S Gopikrishna
          >
          >
          >
          >
          > "Cameron Purdy" <[email protected]> wrote:
          > >When you have a startup class in a cluster, each server will run that
          > >startup class one time. In other words, it always runs once per server.
          > >
          > >Peace,
          > >
          > >--
          > >Cameron Purdy
          > >Tangosol, Inc.
          > >Clustering Weblogic? You're either using Coherence, or you should be!
          > >Download a Tangosol Coherence eval today at http://www.tangosol.com/
          > >
          > >
          > >
          > >"S Gopikrishna" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> Hi
          > >> WE have an application running as startup class in WLS 6.1 . I
          > >want
          > >to know
          > >> how this class can be deployed in clustered environment. Iam pretty
          > >ne to
          > >clustering
          > >> Can some body help me out ?.
          > >>
          > >> Thanks in advance,
          > >> S Gopikrishna
          > >
          > >
          >

A startup class to enable MQ Queues to trigger MDBs in WLS 6.1(sp4)

          Hi,
          I am hoping for references to documentation or opinions on the following method
          allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          with MQs connection factory.
          I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          in a startup class will not allow MDBs to be linked to an MQ queue because startup
          classes are run after MDB deployment during startup. However I found some unused
          in-house code which appeared to do just that and it works.
          Here is the code in abbreviated form:
          public String startup(String str, Hashtable args) throws Exception
               bindMQFactory();
               bindMQQueues();
               return "";
          private void bindMQFactory() throws Exception
               // Create MQ Factory and configure it
               MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
               factory.setChannel(channel );
               factory.setHostName(host);
               factory.setPort(Integer.parseInt(port));
               factory.setQueueManager(qmanager);
               factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
               // bind connection factory into WLS JNDI for later use by clients
               _wlsContext.bind( connectionFactoryJndi, factory );
               // Force mq connection factory to be the one used for mdb's
               _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          private void bindMQQueue() throws Exception
               // create queue and configure it
               MQQueue queue = new MQQueue();
               queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
               queue.setBaseQueueName( mqQueueName );
               // bind queue in WLS JNDI
               _wlsContext.bind( wlsJndi, queue );
          Thanks in advance for any comments or opinions on the above.
          regards
          Martin


Start with the white-paper:
          "Using Foreign JMS Providers with WebLogic Server"
          Note that to get transactional behavior you
          will need to use the WebLogic Messaging Bridge feature.
          Note that integrating MQ is easier in 8.1 - consider
          using WL 8.1 if you can.
          One more comment in-line.
          Martin wrote:
          > Hi,
          >
          > I am hoping for references to documentation or opinions on the following method
          > allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          > the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          > with MQs connection factory.
          Not recommended. Highly not recommended. Do not use the same name
          as the internal factory. Create your own name for a CF, and change the
          weblogic ejb jar to reference your name. The above white-paper
          states how to do this.
          >
          > I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          > in a startup class will not allow MDBs to be linked to an MQ queue because startup
          > classes are run after MDB deployment during startup. However I found some unused
          > in-house code which appeared to do just that and it works.
          >
          > Here is the code in abbreviated form:
          > public String startup(String str, Hashtable args) throws Exception
          > {
          >      bindMQFactory();
          >      bindMQQueues();
          >
          >      return "";
          > }
          >
          > private void bindMQFactory() throws Exception
          > {
          >
          >      // Create MQ Factory and configure it
          >      MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          >      factory.setChannel(channel );
          >      factory.setHostName(host);
          >      factory.setPort(Integer.parseInt(port));
          >      factory.setQueueManager(qmanager);
          >      factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
          >
          >      // bind connection factory into WLS JNDI for later use by clients
          >      _wlsContext.bind( connectionFactoryJndi, factory );
          >
          >      // Force mq connection factory to be the one used for mdb's
          >      _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          > }
          >
          > private void bindMQQueue() throws Exception
          > {
          >      // create queue and configure it
          >      MQQueue queue = new MQQueue();
          >      queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
          >      queue.setBaseQueueName( mqQueueName );
          >
          >      // bind queue in WLS JNDI
          >      _wlsContext.bind( wlsJndi, queue );
          > }
          >
          > Thanks in advance for any comments or opinions on the above.
          >
          > regards
          >
          > Martin

WLS 10.0 Mp1 - Weblogic startup class to initialize client's SSL channels

Hi,
Is it possible to use Weblogic startup class to initialize client's SSL channels?
Any pointers are appreciated.
Thanks in advance.

Hey
If possible can you explain the issue in detail.
What do you mean by “initialize client's SSL channels”
Regards,
Hussain

Problems with Deployment, Startup classes and MBeanHome

Hello,
we have the following problem: How to initialize our application
correctly???
We are using MDBs as message consumers but have to guarantee the order of
incoming
messages. Due to a shortcoming in the JMS implementation (Order of
redelivered messages
is not guaranteed before WLS 8.1!!!) we are using a singleton class to keep
the health state
of the different message queues within the application (controlling whether
the MDBs are
supposed to proceed with processing or to discard any incoming messages).
Thus the MDBs
have to access this singleton, what implies latter has to be initialized
prior to the application
deployment. That's what we are using a startup class for, which is marked to
be loaded before
appplication deployment...
Fortunately the according bug is fixed with WLS 7.0.2.0, so the class is
loaded, but we are
not able to access the MBeanHome interface (We like to register MBean to
provide
adminstrative access to the health state)!!!
javax.naming.NameNotFoundException: Unable to resolve
'weblogic.management.home.localhome' Resolved: 'weblogic.management'
Unresolved:'home' ; remaining name 'home.localhome'
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
So when is the MBeanServer started???
Before application deployment??? After??? Is there any way to tell WLS not
to load the startup
class before the MBeanServer is available respectively the MBeanHome is
accessible via JNDI
but before application deployment???
Any hints are welcome!!!
Regards,
CK

this seems like a bug. the mbeanhome should be available for lookup in
startup classes. also posting to system management newsgroup.
"Carsten Kaiser" <[email protected]> wrote in message
news:[email protected]..
Hello,
we have the following problem: How to initialize our application
correctly???
We are using MDBs as message consumers but have to guarantee the order of
incoming
messages. Due to a shortcoming in the JMS implementation (Order of
redelivered messages
is not guaranteed before WLS 8.1!!!) we are using a singleton class tokeep
the health state
of the different message queues within the application (controllingwhether
the MDBs are
supposed to proceed with processing or to discard any incoming messages).
Thus the MDBs
have to access this singleton, what implies latter has to be initialized
prior to the application
deployment. That's what we are using a startup class for, which is markedto
be loaded before
appplication deployment...
Fortunately the according bug is fixed with WLS 7.0.2.0, so the class is
loaded, but we are
not able to access the MBeanHome interface (We like to register MBean to
provide
adminstrative access to the health state)!!!
javax.naming.NameNotFoundException: Unable to resolve
'weblogic.management.home.localhome' Resolved: 'weblogic.management'
Unresolved:'home' ; remaining name 'home.localhome'
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
So when is the MBeanServer started???
Before application deployment??? After??? Is there any way to tell WLS not
to load the startup
class before the MBeanServer is available respectively the MBeanHome is
accessible via JNDI
but before application deployment???
Any hints are welcome!!!
Regards,
CK

Startup Class in WebLogic server 6.1

I Have a Java application as startup class in Weblogic server 6.1 . I need to stop
the application without restarting the Weblogi server (The startup class should
be removed and the change should be reflected in WebLogic server). Is it possible
to achieve this. I Know that we can remove the startup class from the console
but the change is getting reflected only if i restart the WebLogic Server. Can
some one help me out ?.
Thanks,
S Gopikrishna

Even if it is EJB-only, adding .war with startup logic will be more convinient
than startup classes.
S Gopikrishna <[email protected]> wrote:
Hi
Thanks a lot for the info. My application is not servlet based rather not
web based. In this case how to solve my startupclass problem.
Regards,
S Gopikrishna
Dimitri Rakitine <[email protected]> wrote:
You can deploy web-app(stand-alone, or as a part of an EAR), which has
servlets marked as
load-on-startup (in that case you can use servlet's init() method to
perform your startup
logic), or has servlet context listeners registered
(http://e-docs.bea.com/wls/docs61/webapp/app_events.html#177041) - contextInitialized()
callback will be called when application is deployed, and contextDestroyed()
will be called when application is undeployed.
S Gopikrishna <[email protected]> wrote:
Thanks a lot for the info. Iam pretty new to WeblogicServer. Can utell me about
how to use load-on-startup servlets or application listeners ?.
Thanks in Advance
S Gopikrishna
Dimitri Rakitine <[email protected]> wrote:
You can look into using load-on-startup servlets or application listeners
instead
of startup classes in 6.1 - that way you can redeploy your application
and re-execute
it's startup logic without placing any classes in the system classpath
or restarting
WebLogic.
S Gopikrishna <[email protected]> wrote:
I Have a Java application as startup class in Weblogic server 6.1
I need to stop
the application without restarting the Weblogi server (The startupclass should
be removed and the change should be reflected in WebLogic server).Is it possible
to achieve this. I Know that we can remove the startup class from
the
console
but the change is getting reflected only if i restart the WebLogicServer. Can
some one help me out ?.
Thanks,
S Gopikrishna--
Dimitri--
Dimitri
Dimitri

Weblogic Startup Class

Hello,
I need to set up a start up class for quartz jobs in my weblogic server.
I have created the startup class from the weblogic console but i dont know where to put the class or java file.
Where is it read from?

follow this :
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/startup_shutdown.html#1108355

Sequence of startup classes and EJB deployment

The default sequence when WLS is starting is deploying EJB first and then startUpClasses. Could someone tell me if it's possible to change the sequence.
Thanks a lot in advance.

Sure have your startup class do its work and then hot-deploy the EJB.
-- Rob
Jack wrote:
>
The default sequence when WLS is starting is deploying EJB first and then startUpClasses. Could someone tell me if it's possible to change the sequence.
Thanks a lot in advance.

Order of starting startup classes

I am using WLS 4.5. Is there a way to tell the server in which order to
start the startup classes?
I have tried putting them in certain order in the properties file, but that
certainly does not
do it. Any other tricks?

per the WLS 4.5.1 documentation you can start the classes in a specific
order by putting them in the same line in the properties file separated by
commas.
e.g.
virtual class name= class A, class B, class C
Read the part on start up classes in the doc on the WebLogic properties
file.
farnaz <[email protected]> wrote in message
news:8i5nph$ifu$[email protected]..
I am using WLS 4.5. Is there a way to tell the server in which order to
start the startup classes?
I have tried putting them in certain order in the properties file, butthat
certainly does not
do it. Any other tricks?

Failed to invoke startup class "SOAStartupClass"

Hi all,
1. WLS domain (wls 10.3.5 on Linux, Middleware 11.1.1.5.0) is extended with OIM and SOA Suite.
2. AdminServer is started by wlst.sh script, node manager runs with StartScriptEnabled=true
wls_soa1 is up and running, but soa-infra fails to start with following error:
####<Feb 14, 2012 3:30:28 PM CET> <Critical> <WebLogicServer> <vfusion01.fss-group.com> <wls_soa1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329229828020> <BEA-000286> <Failed to invoke startup
class "SOAStartupClass", java.lang.ClassNotFoundException: oracle.bpel.services.common.util.GenerateBPMCryptoKey
java.lang.ClassNotFoundException: oracle.bpel.services.common.util.GenerateBPMCryptoKey
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:262)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:246)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149)
at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:21)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
I have re-installed twice both SOA Suite and domain, but I always end up with this error.
The same problem has been already reported e.g. here: Fusion MIddleware 11g , but I haven't found any final solution yet.
I've tried to play also with permissions of ../Oracle_SOA1/soa/modules/oracle.rules_11.1.1/rules.jar, but without success.
Any idea how to solve this?
Thanks for support
DanielF

Check Can not start managed servers using Node Manager
hth,
Peter Paul

BEA-000286 Failed to invoke startup class

Have created a class which implements T3StartupDef has a setServices and startup methods. Put inside a JAR which is the WLS 8.1 sp3 Classpath.
Have deployed the startup class from the WL Console;
Deployments | Startup & Shutdown. Given the class the full package name.
However when WLS starts I get;
<30-Sep-2004 17:57:46 o'clock BST> <Critical> <WebLogicServer> <BEA-000286> <Fai
led to invoke startup class "NOTiFYMonitorListener", java.lang.ClassNotFoundException: uk.co.notify.agent.NOTiFYMonitorListener
java.lang.ClassNotFoundException: uk.co.notify.agent.NOTiFYMonitorListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
java:156)
at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:1
21)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassS
ervice.java:116)
at weblogic.t3.srvr.PostDeploymentStartupService.resume(PostDeploymentSt
artupService.java:63)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Any pointers? Thanks

Thanks for that. Followed your instructions now get;
Your environment has been set.
C:\bea\weblogic81\server\bin>
C:\bea\weblogic81\server\bin>
C:\bea\weblogic81\server\bin>javap uk.co.notify.agent.NOTiFYMonitorListener
Compiled from "NOTiFYMonitorListener.java"
public class uk.co.notify.agent.NOTiFYMonitorListener extends java.lang.Object i
mplements uk.co.notify.ejb.utilities.NOTiFYConstants,weblogic.common.T3StartupDe
f{
static java.lang.Class class$uk$co$notify$agent$NOTiFYMonitorListener;
weblogic.management.runtime.LogBroadcasterRuntimeMBean logBroadcaster;
weblogic.management.MBeanHome mBeanHome;
static uk.co.notify.valueobjects.NotificationVO notificationVO;
static java.lang.String password;
weblogic.management.RemoteMBeanServer rmbs;
java.lang.String sDomainName;
static java.lang.String serverName;
static java.lang.String url;
static java.lang.String userName;
public uk.co.notify.agent.NOTiFYMonitorListener();
static java.lang.Class class$(java.lang.String);
public static void main(java.lang.String[]);
public void setServices(weblogic.common.T3ServicesDef);
public void startListening();
public java.lang.String startup(java.lang.String,java.util.Hashtable);
throws java/lang/Exception
Still get ClassNotFoundException. Is the JAR containing my NOTiFYListener class being loaded or not?

Failed to invoke startup class "ClusteredMQJMSStartup", java.lang.ClassNotFoundException

          Windows 2000
          BEA WLS 8.1 SP1
          Created a config based on the template for a WLS with Workshop - "cgServer".
          Changed <configdir>/startWeblogic.cmd to include the extra classes I need to execute
          my startup class.
          Added 2 new servers via the Admin console (http://localhost:7001/) entitled "cgServer2"
          and "cgServer3"
          Added a cluster and added cgServer2 and cgServer3 to the cluster.
          Targetted startup class to the cluster.
          Stop everything.
          Start cgServer via the startWeblogic.cmd script - OK.
          Start cgServer2 via the startManagedWeblogic.cmd script - OK.
          Start cgServer3 via the startManagedWeblogic.cmd script - OK.
          BUT
          if I try and start the managed servers via the admin console, each server reports
          that it cannot find the startup class:
          <11-Feb-2004 11:00:34 o'clock CET> <Critical> <WebLogicServer> <BEA-000286> <Failed
          to invoke startup class "ClusteredMQJMSStartup", java.lang.ClassNotFoundException:
          demo.MQJMSStartup
          Failed to invoke startup class "ClusteredMQJMSStartup", java.lang.ClassNotFoundException.
          What have I missed in the configuration of the Node Manager (I assume it is that)?
          I want cgServer to be the admin server and cgServers 2 and 3 to be my application
          servers, and I will not have everything on the same machine, so I need to use
          the Admin console to manage the cluster and ind its managed-servers.
          FYI - the same code with the same configuration for a single server (no cluster)
          works fine.
          Thanks in advance ... KSS


Check your Startup class code...Are u trying to read any "*.properties" file ?
It is possible that that particular properties file is present only in ManagedServer1 Box and Not in the ManagedServer2 & 3 boxes.

Startup tasks won't work in startup class

Hi,
I need to do some work at system startup and shutdown that
doesn't quite fit the WLS startup/shutdown model. In both cases,
I need to talk to the WLS web server but it's not listening until
after the startup classes are run and stops listening before the
shutdown classes are run.
I'm thinking about using a servlet init() for my one-shot startup
but don't know how robust a solution that is. And I don't know
what to do about shutdown. Is there a startup/shutdown hook
associated with container loading/unloading? Some other solution?
I'm using WLS 6.1 SP2.
Thanks, Garry

Garry <[email protected]> wrote:
Hi,
I need to do some work at system startup and shutdown that
doesn't quite fit the WLS startup/shutdown model. In both cases,
I need to talk to the WLS web server but it's not listening until
after the startup classes are run and stops listening before the
shutdown classes are run.
I'm thinking about using a servlet init() for my one-shot startup
but don't know how robust a solution that is. And I don't know
what to do about shutdown. Is there a startup/shutdown hook
associated with container loading/unloading? Some other solution?If you do not like the fact that you are using servlet to perform
startup/shutdown tasks, you can use ServletContextListener instead.
Using one of those is definitely better than startup classes.
I'm using WLS 6.1 SP2.
Thanks, Garry--
Dimitri

StartUp Class in WLS 6.0

Similar Messages

Maybe you are looking for