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

Similar Messages

  • Weblogic Startup Class does not run as Windows Service

    If you know the answer, plase send me an email at [email protected]
    I'm running a weblogic startup class that starts a Thread. I need to
    run a batch program that should be running as long as WebLogic is
    running (to process new orders).
    It works fine when I run WebLogic (5.1 SP8) from a script, but causes
    problem when I'm running it as a Windows Service. It calls the
    startup class, however, the startup class never spawns the Thread
    class.
    Following is excerpts from different components:
    =============================================================
    *** weblogic.properties ***
    weblogic.system.startupClass.pdfCreatorStart=WebLogicStartupPdfCreator
    *** WebLogicStartupPdfCreator.java ***
    public class WebLogicStartupPdfCreator implements T3StartupDef {
    public String startup(String name, Hashtable args) throws
    Exception {
    Thread t = new ProductionPdfBatchRunner();
    t.start();
    return "success";
    *** ProductionPdfBatchRunner.java ***
    public class ProductionPdfBatchRunner extends Thread {
    public void run() {
    try {
    //work being done here
    this.sleep(30000);
    catch (InterruptedException ie) {               
    catch(Exception e) {
    e.printStackTrace();
    =============================================================
    Thanks for any help

    Hi,
    Ok. Few suggestions.
    1. Can you review the SAP note:
    552286  Troubleshooting for the SAP Web Dispatcher
    2. When you said: "web dispatcher does not get started ", what error you got ? Can you be more details here ?
    3. Please check the trace file dev_webdisp" that generated in the work directory. If the log entries is not abvious, increase the trace level to 2 or 3, and reproduce and re-check the trace file.
    4. What is the output of the command "sapwebdisp -v"
    5. How about sapwebdisp.pfl ? Are those settings correct ?
    Hope this helps.
    Regards,
    Vincent

  • Weblogic startup class (urgent)

    Hi All,
    I need a java program (weblogic startup class) which should fetch data from the database and instantiate another one class (it will be the data holder) and store that object into a webapplication context. Anyone tried this? Since its urgent any help will be appreciated.
    Thanks in advance
    Cheers,
    Pandiaraj

    Do this in the init() method of a servlet and start
    the servlet when you start your weblogic server
    second that. just give a value of 1 for <load-on-startup> in web.xml

  • 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

  • Weblogic startup class and EAR file

    Hi,
    I am using WL 8.1.5.
    I have a weblogic starup class MyStartup that implements T3StartupDef. (it does not specify package).
    I jar-ed it. And I placed MyStartup.jar file into the MyEA.ear file. And I placed that into applications dir.
    With WL Console I defined the startup class and for the ClassName specified MyStartup.
    Yet I get the java.lang.ClassNotFoundException.
    I also have a Manifest.mf file with
    Class-Path: MyStartup.jar
    Please help me solve this problem, I literally don't know what to do next.
    MB

    Hi,
    thanks.
    This seems like a completely opposite method of the depplying startup class with weblogic console.
    Does my class still need to implement T3StartupDef?
    I get this exception. And my classnotfound is still there.
    Exception:weblogic.management.ApplicationException: startup.MyStartup
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Regards,
    MB

  • Weblogic startup class: problem calling EJB's

    Has anyone ever experienced a problem in using a startup class (registered in weblogic.properties)
    and tried to lookup and use an EJB in the same application?
    Basically, I have a startup class which registers to receive messages from an
    MQ queue, and when it receives a message, it tries to do a lookup of a bean and
    use it, but I receive a 'NullPointerException'.
    I'm running Weblogic 5.1
    (I know that Weblogic 6.0 makes use of MessageDrivenBeans, but my app isn't using
    6 or EJB 2.0)
    Thanks...

    Can you post weblogic.log? Are you sure that EJB was deployed successfully.
    Also comment the PROVIDER_URL in initial context and see if that solves the problem
    Viresh Garg
    BEA Systems
    shaun wrote:
    The exception is simply a 'NullPointerException' coming from the startup class
    (I don't have the old log file or I would include the trace here.). Basically,
    when my startup class receives a call to the onMessage(...) method (from listening
    for messages), it looks up an EJB on the server, through the InitialContect class
    and gets a 'null' returned back, thereby throwing the NullPointerException.
    If anyone else is successful in having a startup class which can lookup and call
    an EJB within the same Weblogic server, please help.
    Thanks again....
    Viresh Garg <[email protected]> wrote:
    Can you post the exception stack trace? Also what exactly are you doing
    in startup class.
    Viresh Garg
    Principal Developer Relations Engineer
    BEA Systems
    Shaun wrote:
    Has anyone ever experienced a problem in using a startup class (registeredin weblogic.properties)
    and tried to lookup and use an EJB in the same application?
    Basically, I have a startup class which registers to receive messagesfrom an
    MQ queue, and when it receives a message, it tries to do a lookup ofa bean and
    use it, but I receive a 'NullPointerException'.
    I'm running Weblogic 5.1
    (I know that Weblogic 6.0 makes use of MessageDrivenBeans, but my appisn't using
    6 or EJB 2.0)
    Thanks...

  • Configure weblogic startup class in deployment jar

    We need to invoke a class during weblogic startup that is part of application deployment jar...
    It works if startup class is added to server classpath ( Weblogic documentation also insists that). But our startup class uses application logic and needs to be part of application jar..
    We are getting java.lang.ClassNotFoundException for the class during start up. setting LoadBeforeAppDeployments to false also does not help...
    Is there any other way to invoke a application class during weblogic startup...?
    Any help would be appreciated.
    Thanks,
    Rajasekar.

    here is the solution to this:
    in the conventional method of implementing a startup class, one needs to impletent the T3STartupDef interface and register the class as a startup class in the console / config.xml
    in this method, the startup class need not implement the T3STartupDef interface, it just needs to have a "main" method that will be called. the process of registeration is also simple, if you have an application ear.
    while making the application ear, add a weblogic-application.xml along with the application.xml. the weblogic-application.xml should contain :
    <startup>
    <startup-class>myStartup</startup-class>
    <startup-uri>myStartupArchive.jar</startup-uri>
    </startup>
    the myStartupArchive.jar should contain the startup class and all classes used by it
    also, use a "manifest" file to point to other library jars within the ear
    hope this helps someone !
    going, going, ... gone.

  • 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

  • How to define my startup class in an .ear package?

    I am using WL6.0SP2 on solaris.
    I plan to package my application as an .ear file and to put all necesarry class
    files in there (it will has one .war file for the web tier and one .jar file for
    the EJBs).
    I want, when Weblogic loads my .ear file (i.e. my application), to execute my
    special startup class, which initializes some caches, etc.
    I do not want to define a startup/shutdown class in the console, because it is
    only specific to my application and this startup class is not present in the weblogic
    classpath during weblogic startup.
    The correct place should be in application.xml, but I don't see such thing in
    the DTD.
    Thank you,
    Ivaylo Zlatev

    There is no way to do this on the EAR level - you can use load-on-startup
    servlet(s) in your web component, or initial-beans-in-free-pool=1 EJB.
    Ivaylo Zlatev <[email protected]> wrote:
    I am using WL6.0SP2 on solaris.
    I plan to package my application as an .ear file and to put all necesarry class
    files in there (it will has one .war file for the web tier and one .jar file for
    the EJBs).
    I want, when Weblogic loads my .ear file (i.e. my application), to execute my
    special startup class, which initializes some caches, etc.
    I do not want to define a startup/shutdown class in the console, because it is
    only specific to my application and this startup class is not present in the weblogic
    classpath during weblogic startup.
    The correct place should be in application.xml, but I don't see such thing in
    the DTD.
    Thank you,
    Ivaylo Zlatev--
    Dimitri

  • Startup class : Context lookup for a Home fails in a new thread

    Hi All,
    I am having a funny problem with Weblogic Startup class.In the startup method,
    I am creating an instance of InitialContext. I called look up in this context
    for a bean's home. It works and it retuns the proper Home interface.
    But, when I use the same InitialContext instance in a new thread, and again if
    I call look up for the same bean's home, the server fails with a SecurityException.
    I don't have any Role based Security for this bean.
    Btw, I am using Weblogic 5.1 & SP7.
    Any ideas or help, appreciated..
    Thanks in Advance
    Srikanth Goli
    Here is the code.
    public String startup(String name, Hashtable args) throws Exception {
    InitialContext initialContext = null;
    try {
    initialContext = new InitialContext();
    UserPreferencesHome userPreferencesHome =
         (UserPreferencesHome)initialContext.lookup
         (UserPreferencesHome.DEFAULT_URL);
    //This prints Properly
    System.err.println("StartupTest: userPrefsHome is " + userPreferencesHome);
    } catch(Exception e) {
    e.printStackTrace();
    Thread th = new Thread(new TestThread(initialContext));
    th.start();
    return "ok";
    class TestThread implements Runnable {
    Context context;
    public TestThread(InitialContext ctx) {
    context = ctx;
    public void run() {
    try {
    //This is failing
    UserPreferencesHome userPreferencesHome1 =
         (UserPreferencesHome)context.lookup
         (UserPreferencesHome.DEFAULT_URL);
    System.err.println("UserPreferencesHome1 in the thread is " + userPreferencesHome1);
    } catch(Exception e) {
    e.printStackTrace();
    Here is the exception, I am getting
    java.lang.SecurityException: User "guest" does not have Permission "lookup" base
    d on ACL "weblogic.jndi.com.capgroup.btps".
    at weblogic.security.acl.Security.logAndThrow(Security.java:372)
    at weblogic.security.acl.Security.checkPermission(Security.java:254)
    at weblogic.jndi.internal.NamingSecurityManagerImpl.checkPermission(Nami
    ngSecurityManagerImpl.java:98)
    at weblogic.jndi.internal.NamingSecurityManagerImpl.checkLookup(NamingSe
    curityManagerImpl.java:45)
    at weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:
    737)
    at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
    at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at com.capgroup.btps.server.TestThread.run(StartupTest.java:49)
    at java.lang.Thread.run(Thread.java:484)

    Hi All,
    I am having a funny problem with Weblogic Startup class.In the startup method,
    I am creating an instance of InitialContext. I called look up in this context
    for a bean's home. It works and it retuns the proper Home interface.
    But, when I use the same InitialContext instance in a new thread, and again if
    I call look up for the same bean's home, the server fails with a SecurityException.
    I don't have any Role based Security for this bean.
    Btw, I am using Weblogic 5.1 & SP7.
    Any ideas or help, appreciated..
    Thanks in Advance
    Srikanth Goli
    Here is the code.
    public String startup(String name, Hashtable args) throws Exception {
    InitialContext initialContext = null;
    try {
    initialContext = new InitialContext();
    UserPreferencesHome userPreferencesHome =
         (UserPreferencesHome)initialContext.lookup
         (UserPreferencesHome.DEFAULT_URL);
    //This prints Properly
    System.err.println("StartupTest: userPrefsHome is " + userPreferencesHome);
    } catch(Exception e) {
    e.printStackTrace();
    Thread th = new Thread(new TestThread(initialContext));
    th.start();
    return "ok";
    class TestThread implements Runnable {
    Context context;
    public TestThread(InitialContext ctx) {
    context = ctx;
    public void run() {
    try {
    //This is failing
    UserPreferencesHome userPreferencesHome1 =
         (UserPreferencesHome)context.lookup
         (UserPreferencesHome.DEFAULT_URL);
    System.err.println("UserPreferencesHome1 in the thread is " + userPreferencesHome1);
    } catch(Exception e) {
    e.printStackTrace();
    Here is the exception, I am getting
    java.lang.SecurityException: User "guest" does not have Permission "lookup" base
    d on ACL "weblogic.jndi.com.capgroup.btps".
    at weblogic.security.acl.Security.logAndThrow(Security.java:372)
    at weblogic.security.acl.Security.checkPermission(Security.java:254)
    at weblogic.jndi.internal.NamingSecurityManagerImpl.checkPermission(Nami
    ngSecurityManagerImpl.java:98)
    at weblogic.jndi.internal.NamingSecurityManagerImpl.checkLookup(NamingSe
    curityManagerImpl.java:45)
    at weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:
    737)
    at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
    at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at com.capgroup.btps.server.TestThread.run(StartupTest.java:49)
    at java.lang.Thread.run(Thread.java:484)

  • "problem about weblogic startUp feature"

    I write one classe "A" in weblogic5.1.0 that startup via weblogic.system.startupClass, in the "startup" method of class "A", i initalize a singtlon class "B", after weblogic started, how can i invoke the object of class "B" in other class. thanks.

    Hi jim.
    If you have create a Singleton you can refer to insyance by "getInstance()"
    method;
    but I image that you lost object because GC collect the garbage and your
    singleton is not referred by anyone.
    Then, in startup class, after initialization, you can put your Singleton in
    system properties
    (System.getProperties()) or in a WL workspace.
    Have a nice day.
    Giuseppe Villanova
    Software Engineer
    IT Staff s.p.a.
    081/7877028
    [email protected]
    "jim" <[email protected]> wrote in message
    news:3a6604d6$[email protected]..
    >
    I write one classe "A" in weblogic5.1.0 that startup viaweblogic.system.startupClass, in the "startup" method of class "A", i
    initalize a singtlon class "B", after weblogic started, how can i invoke the
    object of class "B" in other class. thanks.

  • Startup Classes and JMS - Suggestions Please!

    I'm in serious need of having several resources initialized before beans
    start handling requests.
    I tried implementing a Weblogic Startup Class, and it works fine - as long
    as it's the first thing
    to run! -- the problem is, when my Message Driven Beans deploy, if there are
    messages waiting
    for them in their durable subscriptions, they immediately start
    processing... then about 30 seconds
    later Weblogic (6.0sp1) gets around to starting my startup class. If I put
    code in each MDB that
    kicks off the initialization when they are invoked I still run into
    problems, because my initialization
    takes a LONG time (more than 2 minutes) - so I end up with lots of
    transaction rollbacks... which
    are very annoying and clutter up the log files, and scare customers of the
    product.
    Is there anyway to make a startup class/servlet/something that runs and
    completes before any
    other processing occurs?
    Thanks,
    James

    Yes, Startup servlet has the same problem - it doesn't 'startup' until after
    jms messages are already being delivered. :( aside from this, there are
    class loader issues -servlet space and ejb space are not the same...
    Thanks though,
    James
    "minjiang" <[email protected]> wrote in message
    news:[email protected]...
    Hi, did you ever try startup servlet? not startup class?
    mj
    James House wrote:
    The only problem with creating a base class to extend is the fact that
    Java only supports single inheritance, -- and I'm already inheriting...
    >>
    I've been involved with many projects that use WLServer, and in
    almost every one of them, there has been a need for a startup class
    that fires before the server starts handling requests.... strange that
    I'd be the only one to need this, when the need has recurred so often.
    James
    "Raja Mukherjee" <[email protected]> wrote in message
    news:[email protected]...
    James,
    If you have common initialization tasks to be shared by multiple MDBs,
    I
    would create an abstract class (a.k.a BeanAdapter class) where you canhave
    all your initialization logics and have your MDB extend from it.
    I am not convinced that the Startup class needs to run first. In fact,
    I
    have the same view that Startup class should run last. My only wishlist
    for
    startup class was that I should be able to specify order, which isaddressed
    in 6.1.
    I am also getting the feeling from different posts that MDB deploymentwould
    have a re-try logic in 6.1, which I am beginning to look into. Check
    (or
    post) in JMS news group.
    .raja
    "James House" <[email protected]> wrote in message
    news:[email protected]...
    Thanks for the help... I like the pattern you pointed me to better
    than
    anything else... ... but in all cases (your method, Gene's, and whatI'm
    currently doing) I still have to put some code in every MDB that
    I deploy... : (
    Put in a good word for me there at BEA and convince the appropriate
    developer that startup classes should run first!
    James
    "Raja Mukherjee" <[email protected]> wrote in message
    news:[email protected]...
    James,
    There are several ways to solve your problem. I normally use
    setMessageDrivenContext to do all my initialization. There are two
    types
    of
    initialization that I have performed here, first, reading theconfiguration
    file and then load some utility classes in specific order. The
    problem
    with
    the second was that you will have to use synchronized block
    w/HotSpot
    2.0
    to
    keep the order, which is ok. I don't use static block to do the
    initialization, instead use an init() metod. Hopefully you got the
    idea.
    Recently, Gene Chuang created a pattern which esentially does the
    same
    and
    I
    liked the pattern because it was a nicer way of doing what I
    needed to
    do.
    I
    have changed all my examples to customer to use the new pattern.
    You
    can
    find it in
    http://theserverside.com/patterns/thread.jsp?thread_id=7270.
    The
    only think I do not use of this pattern is
    initializeEveryContextSwap()
    method. I am not convinced yet that I would need it (of course
    that
    might
    change over the time).
    Hope this helps, and thanks Gene.
    .raja
    "James House" <[email protected]> wrote in message
    news:[email protected]...
    Ok... here's some more detail:
    The application is largely JMS based, and most of my Session
    EJBs
    are
    invoked only my Message Driven Beans.
    I have a large set of properties that need to be read from a
    config
    file,
    and stored somewhere "globally". I also have a number of
    utilities
    that
    need to get "warmed up" before I start doing any real processing(before
    I start receiving messages from the JMS Topics). These
    utilities
    take
    a
    long time to warm up (a long time being about 45-60 seconds) -
    because
    they are loading hundereds of classes, and creating variousconnections
    to external resources.
    Currently I'm creating a Singleton object that reads the
    configuration
    file
    name from an environment property, and it then parses the file,
    and
    starts
    configuring all of these utilities. Since the "Startup Class"
    didn't
    work
    (weblogic invokes it after I'm already receiving messages), I
    put
    code
    at
    the beginning of all of my MDB's onMessage() methods that calls
    the
    singleton's "getInstance()" method - which synchronizes on alock
    object,
    and does all of it's work.
    I don't like this solution because:
    1- I have to put code in EVERY message-driven bean that I
    create -
    if
    I
    forget one, everything is broken.
    2- I have to increase the transaction time out of the entire
    server
    to
    be over 60 seconds since the beans hang that long while theconfiguration
    is
    happening.
    It seems very obvious that a "Startup Class" should be invoked
    after
    the
    server has come completely up, but before it starts listening
    for
    requests -- isn't the whole point of a "startup class" to getthings
    ready
    that need to be done as soon as the server comes up? but alas,
    the
    person
    who designed this at BEA apparently didn't agree with me on this
    point!
    Any suggestion on better solutions would be greatly appreciated.
    James
    "Raja Mukherjee" <[email protected]> wrote in message
    news:[email protected]...
    You can do it this way, but I would not recommend it, unless
    that's
    the
    only
    way to attack the problem at hand. But that's just me.
    I have seen this problem with multiple clients and in most
    cases
    there
    is
    a
    better way to handle it. If James give us a little more
    information
    on
    what
    type of configuration is he talking about and some background
    of
    his
    application, we as a group can think and may be able to come
    up
    with
    some
    idea.
    .raja
    "Joel Nylund" <[email protected]> wrote in message
    news:[email protected]...
    you could wrap the starting of weblogic in your own class
    and do
    initialization
    there. You have to be careful because of the way weblogic
    classloaders
    work, but
    you may be able to do what you want. Weblogic is just a java
    class,
    so
    you
    can
    start your class, then once your done initializing, just
    call
    weblogic.Server.main
    -Joel
    James House wrote:
    I'm in serious need of having several resources
    initialized
    before
    beans
    start handling requests.
    I tried implementing a Weblogic Startup Class, and it
    works
    fine -
    as
    long
    as it's the first thing
    to run! -- the problem is, when my Message Driven Beans
    deploy,
    if
    there
    are
    messages waiting
    for them in their durable subscriptions, they immediately
    start
    processing... then about 30 seconds
    later Weblogic (6.0sp1) gets around to starting my startupclass.
    If
    I
    put
    code in each MDB that
    kicks off the initialization when they are invoked I still
    run
    into
    problems, because my initialization
    takes a LONG time (more than 2 minutes) - so I end up with
    lots
    of
    transaction rollbacks... which
    are very annoying and clutter up the log files, and scarecustomers
    of
    the
    product.
    Is there anyway to make a startup class/servlet/something
    that
    runs
    and
    completes before any
    other processing occurs?
    Thanks,
    James

  • Startup classes in WL6.0

    Hi everybody,
    Is the use of T3StartupDef interface deprecated in
    weblogic 6.0 for writing startup classes? If yes how do I write startup classes?
    Thanx,
    Sunil

    One feature of WebLogic startup classes is that you do not have to implement
    T3StartupDef - if you class has static void main(String[] args) it will be
    invoked.
    Also, note that startup classes have to be in the system classpath, which
    creates problems when they need to use application classes.
    Sunil Naik <[email protected]> wrote:
    Hi William,
    Thanx for the explanation.I assume that use of T3StartupDef is not
    deprecated and I'll go ahead with it.
    thanx,
    Sunil
    "William Stewart" <[email protected]> wrote:
    Startup classes using the T3StartupDef interface do work in WebLogic
    6.0 - I am
    just now porting a project from WL 4.5 to WL 6.0 and got it to work okay,
    but
    with these caveats:
    (1) BEA's Javadoc documentation on the T3StartupDef interface is outdated
    - it
    mentions 'weblogic.properties', which no longer exists in WL 6.0 (replaced
    by
    config.xml and the Web-based Admin console).
    (2) BEA's documentation for configuring startup classes in the Admin
    console is
    poor - for the 'Arguments' attribute, it doesn't specify how to format
    arguments
    for the startup class - you separate them with a comma like this:
    ARG1=value1,ARG2=value2
    (3) There is no documentation on how to write a Startup class in the
    programming
    section of BEA's documentation. It's very simple though; here is what
    you do:
    (a) Write a class that implements T3StartupDef.
    (b) Give it a default, do-nothing constructor.
    (c) Provide the interface's #setServices(T3ServicesDef) method - just
    save the
    parm in a field or something.
    (d) Provide the interface's #startup(String, Hashtable) method - the
    Hashtable
    contains your arguments (set in the Admin console) and this is where
    you put your
    desired startup code.
    "Sunil Naik" <[email protected]> wrote:
    Hi everybody,
    Is the use of T3StartupDef interface deprecated in
    weblogic 6.0 for writing startup classes? If yes how do I write startup
    classes?
    Thanx,
    Sunil
    Dimitri

  • Startup class is run before web services are deployed

    Hello, I need to run a class at server start-up which uses web services deployed on the same Weblogic server.
    I'm using Weblogic startup class, which fires after the server is up and all modules have been deployed.
    However, it is fired before web services are deployed, so this solution doesn't work.
    Is there a way to have a class that is run by Weblogic after web services are deployed?
    Right now I'm using a timer that polls the server till the services are up and running, but I hope there's a cleaner way.
    thanx,
    Mike

    Thanx for response.
    Looking at the logs, the following came to light.
    1. My app does get deployed last, but the ServletContextListener in my app is fired after all modules "...transitioned from STATE_PREPARED to STATE_ADMIN".
    It took a few more seconds for all modules to transition "from STATE_ADMIN to STATE_ACTIVE".
    2. After all modules transitioned to STATE_ACTIVE, the log shows this:
    <Channel "DefaultSecure" is now listening on xxx.xxx.xxx.xxx:443 for protocols iiops, t3s, ldaps, https.>
    I assume that only at this point are web services accessible. The error that I get when trying to invoke a web service from ServletContextListener is:
    java.net.ConnectException: Tried all: 1 addresses, but could not connect over HTTPS to server: RLOCVGVY91 port: 443
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:289)
    So I dunno... If my ServletContextListener waits for 10 seconds, everything works.
    Mike

  • Loading startup class before Applications

    I need to load a startup class before my EJBs are deployed. The "deployment order"
    field from the console works for components of the same type only. Looks like WLS
    always loads Applications before startup classes. Does anyone know how to change
    this configuration?
    Thanks,
    Stefano

    Hi Stefano
    I think the relevant CR for this problem is CR061426.
    This CR is included in sp3 of WLS6.1
    Hope this help
    J-F
    Stefano wrote:
    I need to load a startup class before my EJBs are deployed. The "deployment order"
    field from the console works for components of the same type only. Looks like WLS
    always loads Applications before startup classes. Does anyone know how to change
    this configuration?
    Thanks,
    Stefano

Maybe you are looking for