Quirk of wls 4.5.1 startup..

<HELP ME>
I have no understanding as to why, but it seems that the dynamic classloader
thingy will not function unless you begin the process from <installDir>.
Because of this the batch file to start the hotDeploy version must be in
your <installDir> and all references to classes found stemming from the
<installDir> must be indicated using .\theClass
I would love somebody to explain why this is so.
In other words:
if you do this:
set WLS_INSTALL_DIR=d:\weblogic
set JAVACLASSPATH=%WLS_INSTALL_DIR%\classes\boot;.....etc etc
you throw an Exception in Thread Main class not found Exception
javax.naming.blah blah
if instead you start your .bat file from d:\weblogic and do this:
set JAVACLASSPATH=.\classes\boot;...etc etc
everything works great.
</HELP ME>

Great. I'm glad that worked out for you.
The will ask the documentation team to place a note regarding this.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Owen Taylor <[email protected]> wrote in message
news:8g2odh$hg7$[email protected]..
You are so right! - kind of. It turns out you must start your .bat file
from a directory which contains a global weblogic.properties file and you
must specify the path to the weblogic.policy file. If you do these things
you can use any arbitrary %VARIABLES% that you like with full success.
Thankyou.
Michael Girdley <[email protected]> wrote in message
news:8fflt5$36n$[email protected]..
I believe that you were simply witnessing an artifact of the relativepaths
that we used in the start script. If you were to give full paths there,
I
think that you would be fine.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Owen Taylor <[email protected]> wrote in message
news:8fd6go$oe9$[email protected]..
<HELP ME>
I have no understanding as to why, but it seems that the dynamicclassloader
thingy will not function unless you begin the process from
<installDir>.
Because of this the batch file to start the hotDeploy version must bein
your <installDir> and all references to classes found stemming fromthe
<installDir> must be indicated using .\theClass
I would love somebody to explain why this is so.
In other words:
if you do this:
set WLS_INSTALL_DIR=d:\weblogic
set JAVACLASSPATH=%WLS_INSTALL_DIR%\classes\boot;.....etc etc
you throw an Exception in Thread Main class not found Exception
javax.naming.blah blah
if instead you start your .bat file from d:\weblogic and do this:
set JAVACLASSPATH=.\classes\boot;...etc etc
everything works great.
</HELP ME>

Similar Messages

  • WLS 8.1 cluster startup scripts

    Hi all,
    I'm new to WebLogic and so am stumped by a configuration issue that should be normally be simple. I'm running WebLogic Server 8.1 SP6 on a Linux server and the Sun 1.4.2 JVM. A single cluster with 3 managed servers is set up, all servers being on the same machine.
    I'm trying to get the JProfiler 4.3 agent running on one of these servers to investigate a memory leak issue. Using the WLS administration console (TestDomain > Clusters > TestCluster > TestServer1 > Configuration > RemoteStart), I have changed the server's startup arguments to add "-Xrunjprofiler" and "-Xbootclasspath".
    For now I'm getting a "Error occurred during initialization of VM Could not find -Xrun library: libjprofiler.so" message when I start the server using the admin console. To solve this I need to modify the LD_LIBRARY_PATH for this particular server to include this library's dynamic dependencies.
    The current question is: where should I be making these changes? I thought that the setEnv.sh, startManagedWebLogic.sh and startWebLogic.sh scripts in ~/domains/TestDomain/TestServer would be executed when starting this individual server, but changing them doesn't seem to have any impact. This means that other scripts are invoked, but which ones?
    Thanks a bunch for your help.
    Cheers,
    GB
    Edited by gbilodeau at 08/13/2007 10:59 AM
    Edited by gbilodeau at 08/13/2007 10:59 AM

    Hi,
    Go through the following link and check whether you configured load balancing settings correctly or not.
    http://e-docs.bea.com/wls/docs81/cluster/load_balancing.html
    Regards
    Anilkumar kari

  • WLS 10.1 server startup credentials cause server to fail

    Hello all,
    Any guidance or assistance given towards configuring WLS to meet the stated requirements and correct the isssues listed would be greatly appreciated.
    The requirements:
    1. a domain configured with two managed servers in a cluster on a single linux host
    2. admin and managed servers should startup as the "bea" user instead of root
    3. servers should automatically start at boot for run states 3,4,5
    4. node manager should control the servers and restart them if they crash
    5. node manager and admin servers are started at boot in rc script.
    6. node manager is started as root.
    Current Issue:
    servers will not stay running with user/pass set on "server start" page. Credentials used were the admin user for the domain. Why is this breaking?
    Exception: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    The domain was installed using the admin credentials of "bea" and a password of "abcd1234". These are the correct parameters to put into the "server start" page parameters for each server?

    Admin credentials issue has been resolved. (recreated the domain)
    Any best-practices on how to implement the requirements listed in my previous e-mail would still be really appreciated.
    All of the servers seem to start as the "bea" user now, but one of the two managed servers crashes within 2 minutes of being started. No cause seems evident from the logs with the default logging levels. I have not tracked down the error yet. There are no applications deployed... It seems as if the two managed servers are conflicting somehow.

  • WLS 9.2.03 Startup errors

    Hi,
    can anyone explain what may be causing these two errors on startup. Both seem related to Web Services; all of which use SOAP/HTTP bindings so mention of JMS seems spurious.
    1. Data Binding Error
    <WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
    <WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.
    2. JMS queue warning
    <WSEE>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.c
    onnect:227>
    Thanks.

    The first error might be thrown by WLS JAX-RPC client. Which API did you use to create javax.xml.rpc.Service? If your client can't invoke your service, you can try ServiceFactory.loadService(Class serviceInterface), or Service loadService(URL wsdl, Class serviceInterface, Properties p) to create the Service instance.
    'weblogic.wsee.DefaultQueue' is used by the internal async webservice to receiving async response message over JMS transport.The second warning just tries to remind that async request-reply webservice and callback webservice over JMS transport doesn't work if no JMS queue is configured to receiving async messages. You can ignore this warning message if all your services use SOAP/HTTP bindings.

  • WLS and TUX domain startup/Shutdown

    Hi All,
    1. I start my TUX domain first.
    2. Then Start my WLS configured with startup class for Tuxedo connection.
    3. I invoke a method that requests a service on Tuxedo. I get the tuxedo connection
    and the request is successful.
    4. I restart my Tuxedo domain.
    5. I invoke the same request again as in Step 3.
    4. I get a Tuxedo connection failure.
    When I restart my WLS again then it works fine.
    My understanding is when Tuxedo domain is restarted the handle of Tuxedo factory
    connection which was establised at the time of startup is invalid as the Tux domain
    was restarted.
    Could any one tell me how could I resolve this. Is there any configration in
    the bdmconfig.xml or an alternate way to look up Tuxedo factory connection handle
    only when there is a request from the client.
    regards,
    Riaz

    Thanx Bob.
    I shall look into the areas you mentioned and try out the same.
    Will get back to you in case I need further help.
    regards,
    Riaz
    Bob Finan <[email protected]> wrote:
    Riaz,
    The Tuxedo connection factory handle is not invalidated by the Tuxedo
    side rebooting. The session connection is invalidated but that should
    not
    be visible to the app. For example, if in the simpapp sample a tpcall()
    to the
    TOUPPER Tuxedo service is done twice the second call will occur but then
    fail if it can not create a connection to the remote Tuxedo domain. Your
    problem
    may be because the remote domain has not had sufficient time to create
    a
    connection
    OR the configuration does not permit WTC side from retrying the
    connection OR.......
    Try turning on the WTC tracing and see if the connection has been
    re-established
    prior to the repeated call to the Tuxedo service.(Also look at Tuxedo
    side ulog). Check
    the configuration ConnectionPolicy and MaxRetries attributes.
    Bob Finan
    Riaz wrote:
    Hi All,
    1. I start my TUX domain first.
    2. Then Start my WLS configured with startup class for Tuxedo connection.
    3. I invoke a method that requests a service on Tuxedo. I get the tuxedoconnection
    and the request is successful.
    4. I restart my Tuxedo domain.
    5. I invoke the same request again as in Step 3.
    4. I get a Tuxedo connection failure.
    When I restart my WLS again then it works fine.
    My understanding is when Tuxedo domain is restarted the handle of Tuxedofactory
    connection which was establised at the time of startup is invalid asthe Tux domain
    was restarted.
    Could any one tell me how could I resolve this. Is there any configrationin
    the bdmconfig.xml or an alternate way to look up Tuxedo factory connectionhandle
    only when there is a request from the client.
    regards,
    Riaz

  • Unable to find information on WS data binding error on WLS 9.2.03 startup

    Frustratingly, when I Google for "WS data binding error" I get 'old' links to BEA forum issues which may help but these are nowhere to be seen on the read-only copies now on Oracle forums here :- http://forums.oracle.com/forums/category.jspa?categoryID=202.
    The link I'm looking for is:-
    forums.bea.com/thread.jspa?threadID=600017135
    Is there anywhere I can get access to this information or should I just post new items on the new WLS forum?
    Many thanks.
    p.s. the errors I am trying to research are as follows:-
    <WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
    <WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.

    Check this..
    http://docs.oracle.com/cd/E10291_01/doc.1013/e10538/weblogic.htm
    you can ignore those warnings
    The following data type binding warnings and errors are displayed during deployment and start of Decision Service (Business Rules) Applications. These errors and warnings can be ignored.
    <WS data binding error>could not find schema type '{http://www.w3.org/2001/XMLSchema}NCName
    <WS data binding error>could not find schema type
    '{http://websphere.ibm.com/webservices/}SOAPElement
    java.lang.IllegalStateException
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.
    getSchemaProperty(AnonymousTypeFinder.java:253)

  • WLS extension classpath during startup

    I have a WLS 9.2 domain which hosts an application which uses JSF & EJBs. When starting WLS, the JVM adds an extension directory to the end of its classpath as is reported here:
    <Feb 13, 2007 6:22:46 PM PST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /u1/toro/toro/toro/tools/bea-wl9.2/user_projects/domains/rh/lib/mysql-connector-java-3.1.11-bin.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/p13n/p13n_common.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/p13n/p13n_system.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/wlp/netuix_common.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/wlp/netuix_schemas.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/wlp/netuix_system.jar:
    /u1/toro/toro/toro/tools/bea-wl9.2/weblogic92/platform/lib/wlp/wsrp-common.jar
    I realize that some of these are picked up from the <domain_home>/lib directory, but i am not sure about the others which are not part of this lib folder. Why does WLS add these to the extensions classpath?
    Thanks
    Ramdas

    We have realized the same phenomenon which lead to undesired behaviour: any .jar file in a directory "lib" of the domain directory is automatically added to the boot classpath.
    Does anyone know if there is a way to disable or configure this (undocumented?) feature?

  • Multiple Web Applications WLS 7.0

    Hi,
    I am trying to configure multiple web applications on the same WL 7.0 server and
    am having trouble doing the following.
    I would like to be able to use the following URLS:
    Application #1:
    http://myserver/st/aems - where st/aems maps to the path X:\SimpleTrade2\AEMS\ui\source\htdocs
    Application #2:
    http://myserver/st/acms - where st/aems maps to the path X:\SimpleTrade2\ACMS\ui\source\htdocs
    Root - Default web application - This would be left empty with the idea that our
    company could sell our web applications and we would deploy them on someone elses
    WLS and we would not conflict in any way.
    The problem with the above is that when I look at the DTD and try and configure
    config.xml in the following way:
    <Application Deployed="true" Name="AEMS"
    Path="X:\SimpleTrade2\AEMS\ui\source\htdocs" TwoPhase="true">
    <WebAppComponent DeploymentOrder="2000" Name="aems"
    Targets="simpletradeserver" URI="st/aems"/>
    WLS blows up on startup because it tries to POST-Pend the URI to the path... If
    I change it to:
    <Application Deployed="true" Name="AEMS"
    Path="X:\SimpleTrade2\AEMS\ui\source" TwoPhase="true">
    <WebAppComponent DeploymentOrder="2000" Name="aems"
    Targets="simpletradeserver" URI="htdocs"/>
    This will work but then my URL is not what I want it becomes http://myserver/htdocs
    Is there anyway around this or a way to get what I want?
    Another piece of information, I am developing in Exploded directory format when
    we deploy it will be as an ear.
    Thanks in advance for any ideas!!!
    -Jerry Rodgers

    Thanks for the info Christian.
    I thought I would pass along a bit more inforation for others who might be trying
    to do something similar. In case they run across this message.
    I did determine that if you are using a .WAR file the name attribute of the xml
    node WebAppComponent will allow you to create a different context path than the
    URI. I did not test to see if it allowed you to use a name like "st/aems" I am
    sure "st.aems" would work or any name that may be different than the URI. The
    weird thinhg is that when using the EXPLODED DIRECTORY format the URI is the name
    of the folder under the path and the name property appears to be ignored no matter
    what you change it to you can only get to your web app using the URI.
    Hope this helps someone who comes after me and is looking for the same thing,
    maybe they won't spend 6 hours on it like I did ;>
    -Jerry
    "Christian Plenagl" <[email protected]> wrote:
    >
    Hi,
    this is not possible.
    The URI field contains the directory name of the WebApplication, which
    normally
    is the same name as the directory where you put the webapplication in.
    Christian Plenagl
    Developer Relations Engineer
    BEA Support
    "Jerry Rodgers" <[email protected]> wrote:
    Hi,
    I am trying to configure multiple web applications on the same WL 7.0
    server and
    am having trouble doing the following.
    I would like to be able to use the following URLS:
    Application #1:
    http://myserver/st/aems - where st/aems maps to the path X:\SimpleTrade2\AEMS\ui\source\htdocs
    Application #2:
    http://myserver/st/acms - where st/aems maps to the path X:\SimpleTrade2\ACMS\ui\source\htdocs
    Root - Default web application - This would be left empty with the idea
    that our
    company could sell our web applications and we would deploy them onsomeone
    elses
    WLS and we would not conflict in any way.
    The problem with the above is that when I look at the DTD and try and
    configure
    config.xml in the following way:
    <Application Deployed="true" Name="AEMS"
    Path="X:\SimpleTrade2\AEMS\ui\source\htdocs" TwoPhase="true">
    <WebAppComponent DeploymentOrder="2000" Name="aems"
    Targets="simpletradeserver" URI="st/aems"/>
    WLS blows up on startup because it tries to POST-Pend the URI to the
    path... If
    I change it to:
    <Application Deployed="true" Name="AEMS"
    Path="X:\SimpleTrade2\AEMS\ui\source" TwoPhase="true">
    <WebAppComponent DeploymentOrder="2000" Name="aems"
    Targets="simpletradeserver" URI="htdocs"/>
    This will work but then my URL is not what I want it becomes http://myserver/htdocs
    Is there anyway around this or a way to get what I want?
    Another piece of information, I am developing in Exploded directoryformat
    when
    we deploy it will be as an ear.
    Thanks in advance for any ideas!!!
    -Jerry Rodgers

  • T61, battery and Trackpoint/touchpad quirks.

    Hi all,
    I purchased a T61 back in the early part of 2008, I suppose it's been 7-8 months.  Overall I've been very pleased with the unit, but I currently have a couple of quirks:
    Since the very beginning, upon startup my T61 will intermittantly not recognize the Trackpoint, touchpad, sometimes both, and very very occaisionally the keyboard.   For the most part it's fine, but when it acts up I have to reboot 1-3 times for everything to work. 
    My other problem is recent, within the last month.  Battery life has always been good until this point.  I was fiddling with the power management settings and came across the Battery Maintenance feature and performed a battery reset - ever since battery information claims my battery can store 11% of it's full charge capacity and it will last at most 15 minutes.  I don't mind having to replace a battery every so often, it's the nature of anything battery powered, but it seems from my perspective that the battery reset *caused* my battery life problem./
    Any comments, constructive criticism, or encouraging words are appreciated.  Thanks,
    Joseph
    There is no mechanical problem so difficult that it cannot be solved by brute strength and ignorance.

    Just got the laptop back, so far it looks like everything's gone off without a hitch.  Total down time on my end: 3 days for basic depot warranty service.  I have friends who send off their HPs for weeks at a time, the laptop returns unfixed, and any time they speak to a customer service rep they are told their one year old laptop is outdated and the sales pitch on a new machine begins.
    Thanks, guys.  I hope I can singlehanded sell fifty T-series for you, they are worth every penny.
    There is no mechanical problem so difficult that it cannot be solved by brute strength and ignorance.

  • Itunes can't find network drive on boot, but fine after

    I have a MacMini server for my house providing light control, emal, websites and other fun stuff.   As it is on 24x7 it made sense to put the iTunes library here as well and have my primary workstation simply connect to it.  As the MacMini is in a closet I really need the primary workstation as the point of connection for all iPads and iPhones.
    This seemed simple enough in theory but it's got a quirk in it somewhere. 
    On startup, the primary workstation always comes up with an error that it can't find the iTunes library.   But when I click the option button to choose the library, it opens to the proper place - the directory locatino on the MacMini.
    After I have done this, iTunes works just as expected.   I can even close iTunes on the workstation and open it again - poof, there it is as expected and no problem.   If I shut down the workstation and start it up again then once again I get this same error from iTunes regarding it being unable to find the library.
    I wrote an apple script in an effort to establish connection to the network drive (i.e., the MacMini) and it works just fine - it even has a delay to make sure the connection is established (I can disable this but it makes no difference).  The problem is that it seems to run AFTER the iTunes Helper has tried and fialed.  
    Under my Login Items, the iTuens Helper is always the First application listed.  I can't seem to reorder them at all.  I can delete the iTunes Helper, but then of coruse iTunes doesn't launch.   Once I set the preferences again to start iTunes at Startup, it reasserts itself to be first in line.
    I am using a Mac Airport Extreme (had the original and now have the 802.11ac) as the central network controller - but this issue was there before.  Although there is a Netgear Gigbabit router in the house too, the workstation and the MacMini are both on diret lines to the Airport Extreme and are not using wireless.
    The sharing of the media files works just fine, and from the Apple TVs in the house I can select and play either from the MacMini or the workstation as long as the workstation is on.   Of course the media is all coming from the MacMini drive as the original source, but there are no latency issues perceptable.
    It's only the initial startup boot of the workstation that seems to trigger this error.  
    I have tried removing the network connection script, and simply reidetifying the library location using the option key when starting iTunes - but the behavior remains.
    Searching for how others have recommended doing this, most articles don't have the login script but others do - but none of them have any sort of a bi-line warning that for the initial startup there may be this lost library error. 
    The MacMini is new as of February and the workstation is an older Mac Pro - both are running the latest versions of OS X 10.8.4 with all updates in place.
    I don't have any other startup applications that require info from the MacMini.  However, since I adminster it via screen share, and usually have no exited that - screen share is happily there and fully connected after startup.   Leaving this open or shutting it down doesn't have any affect on the iTunes issue.
    This seems to simple an issue for it to have a complex cause - but I am clearly missing something.
    Hoping someone here has some fresh thoughts and ideas.
    Cheers -
    Dan

    On a whim, I tested the remote library with my MacBook Pro.
    I shut down iTunes on the MacPro Workstation and then used the Option key to startup iTunes on the MacBook Pro - and selected the remote library on the MacMini.   Worked jsut fine (of coure the size of the open window was too big) but no issues at all.  
    And once selected, I can close and start iTunes repeatedly with no issues on the MacBook Pro.
    Then I did a Shutdown and Restart.   Following the login I get the very same popup window telling me that the iTunes library can not be found.  AND just like on the Workstation, I hit the option for Choose and it takes me right to the correct location on the MacMini - all I need to do is accept and poof it launches just as it should.
    The MacBook is on wireless.
    Indications here are that this is an issue with iTunes starting up before the netowrk handshakes have completed.
    Anyone have any thoughts??

  • BPM 10.3 Process Admin Engine Settings

    Hi
    In BPM 10.3 in the Process Admin console there are a series of engine settings that users can modify, inparticular under the Execution tab there's a section called Automatic Execution where an 'Interruption Retry Internal ' value can be set.
    So I'm just trying to understand the impact that will this have on the on process behaviour?
    Documentation is limited, but I can only assume that this value relates to the retry internal when you attempt to interrupt a process instance.
    Does anyone have any experience / knowledge good or bad with relating to this setting?
    Thanks

    Hello -
    >
    Please note that the information below is specific to BPM engine running on WLS.
    1) At startup, BPM engine tries to connect to the JMS server.
    1a) If the service is not available, it fails and stops the Global Automatic JMS Poller. A restart of BPM engine is required.
    1b) If the service is available, it starts consuming messages.
    2) When BPM engine is running if at some time the JMS connection goes down, BPM engine tries to reconnect to the JMS server every minute up to 50 times.
    2a) If the connection can be reestablished, JMS Poller starts processing messages
    again.
    2b) If after the 50 retries the connection can not be reestablished, BPM engine logs
    a severe message and stops the Global Automatic JMS Poller.
    >
    BR,
    Justin.

  • JMS MessageBridge Problem ??

              Hello,
              We are using WLS 7.0. We 've set up the WLS Message Bridge to communicate between
              MQ and WLS JMS queues. The MQSeries JNDI objects are created in WLS JNDI using
              a startup class. There are 2 Queues on the MQseries[TO_JMS and FROM_JMS] and 2
              Queues on the WLS JMS[FROM_MQ and TO_MQ]. I put a message on TO_JMS of MQ which
              is transferred to FROM_MQ of WLS JMS using the WLS Message Bridge. After processing
              the message on the WLS side, I put a message on TO_MQ of WLS JMS which is transferred
              to FROM_JMS of MQ. The whole messaging transfer works very well. The problem is
              with the Corelation Id I set when putting the message on TO_JMS. I expected the
              same Correlation Id will be transferred to FROM_MQ. And while sending the message
              back from WLS to MQ, I set this corelation Id to whatever was first set. I do
              this to filter out a specific message. But as the correlation ids are not copied
              by the message bridge, when I filter the message using the correlation Id from
              the FROM_JMS, I get nothing. Without the filter, I can get the message. Is this
              a Bug? Are there any work arounds ?
              Thanks
              Swamy
              

    Hi Swamy,
              The bridge does copy all the JMS header fields (except for
              the MessageID, Destination and ReplyTo) and user properties when
              transferring messages over.
              I would suggest that you double check your filter expression and make sure
              it does what you want. It would be a good idea to test your filter without the bridge
              involved.
              If that still does not work, try to use a user property and see if that gets you
              anywhere.
              If neither of those works, contact BEA support. But I think both approaches should just
              work.
              Thanks,
              Dongbo
              Swamy Vasudevan wrote:
              > Hello,
              > We are using WLS 7.0. We 've set up the WLS Message Bridge to communicate between
              > MQ and WLS JMS queues. The MQSeries JNDI objects are created in WLS JNDI using
              > a startup class. There are 2 Queues on the MQseries[TO_JMS and FROM_JMS] and 2
              > Queues on the WLS JMS[FROM_MQ and TO_MQ]. I put a message on TO_JMS of MQ which
              > is transferred to FROM_MQ of WLS JMS using the WLS Message Bridge. After processing
              > the message on the WLS side, I put a message on TO_MQ of WLS JMS which is transferred
              > to FROM_JMS of MQ. The whole messaging transfer works very well. The problem is
              > with the Corelation Id I set when putting the message on TO_JMS. I expected the
              > same Correlation Id will be transferred to FROM_MQ. And while sending the message
              > back from WLS to MQ, I set this corelation Id to whatever was first set. I do
              > this to filter out a specific message. But as the correlation ids are not copied
              > by the message bridge, when I filter the message using the correlation Id from
              > the FROM_JMS, I get nothing. Without the filter, I can get the message. Is this
              > a Bug? Are there any work arounds ?
              >
              > Thanks
              > Swamy
              

  • System properties

    Hi,
    Is there any way to define custom properties in the weblogic.properties file
    and access them from WLS, say from a startup class, a session bean etc?
    Thanks
    Chulaka

    Here it is:
    T3Services.getT3Services().config().getProperty("weblogic.system.name"));
    This is for weblogic defined properties only.
    Cheers - Wei
    Cameron Purdy <[email protected]> wrote in message
    news:395a9e77$[email protected]..
    In addition to Wei's comments, there is a T3 class that lets you accessthe
    contents of weblogic.properties very easily, but I cannot remember thecall.
    >
    Cameron Purdy, LiveWater
    "Chulaka Ailapperuma" <[email protected]> wrote in message
    news:8j7qgt$gt2$[email protected]..
    Hi,
    Is there any way to define custom properties in the weblogic.propertiesfile
    and access them from WLS, say from a startup class, a session bean etc?
    Thanks
    Chulaka

  • 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
              

  • 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
              

Maybe you are looking for