BEA Responses to Newsgroup

Does BEA staff look at this newsgroup at all? If not how can I get my
question answered:
"Any information on the purpose of the GC threshold setting? There seems to
be universal agreement that setting the GC threshold is at best pointless.
Looking for any clarification on this issue.
TIA"
I am curious to know as much about BEA specific issues (very familiar with
how the GC works so not looking for boiler plate information) regarding
memory since it seems to be extremely unreliable versus other platforms.
Anybody have any helpful hints in that regard?
TIA, again

I don't quite understand. Do you want to view the responses in more of a record view? Go to the View Responses tab, select the View menu and click Detail View. Is this what you are looking for?
Randy

Similar Messages

  • Installing another WLS 6.0 instance in same root /bea directory

    I have a running WLS 6x instance in /bea/wls6***. I want to put another
    instance in /bea directory as a totally separate instance (/bea/wls6trn
    e.g.) Is this a valid way to do this or do I need to go ahead and install to
    another separate filesystem.
    daryl

    Daryl,
    What is it you are trying to accomplish? You do not need to install the software
    multiple times to have multiple instances running on the same machine. In fact, I
    always recommend to our customers that they never use the BEA-HOME directory
    structure to store ther application-specific data. If all you want to do is create
    two separate domains on the same machine, do the following:
    1.) Install the WebLogic Server 6.1 (or 6.0) software (it will go under
    $BEA_HOME/wlserver6.1).
    2.) Create some other directory somewhere outside of the $BEA_HOME directory
    structure (e.g., /usr/myApp1).
    3.) Copy the $BEA_HOME/wlserver6.1/config directory to /usr/myApp1 (you can delete
    the examples and PetStore directories under /usr/myApp1/config directory).
    4.) Edit the /usr/myApp1/config/mydomain/startWebLogic.sh script to reflect the
    fact that the WebLogic software is installed elsewhere.
    5.) Repeat steps 2 through 4 as many times as you want to create as many instances
    as you want...
    Hope this helps,
    Robert
    BEA Weblogic Support wrote:
    Hi Daryl
    That is a weblogic 6.x design constraint. Weblogic 6.x keeps the history of
    versions under BEA-HOME, in the registry.xml file. So, if you have already
    installed same weblogic version with same service pack level then the installer
    won't allow you to install it second time. You should have different bea-homes.
    I hope this clarifies your query.
    Thanks & Regards
    BEA Customer Support
    Daryl Davis wrote:
    I believe you. But I do have a question. If two different versions work,
    why won't two of the same?
    daryl
    "BEA Weblogic Support" <[email protected]> wrote in message
    news:[email protected]...
    Hi Daryl
    Greetings...!
    How are you doing?.
    You can have different versions under same BEA-HOME. For example
    BEA-HOME is /bea
    ----/wlserver6.1(weblogic6.1 build)
    ----/wlserver6.1sp1 (weblogic 6.1 with sp1build)
    ----/wlserver6.0sp2 (weblogic6.0 with sp2 build)
    But you can't have more than one wls instance of same version under one
    BEA-HOME. You have to choose different BEA-HOME, /beatrans
    Thanks & Regards
    BEA Customer Suppot
    Daryl Davis wrote:
    I have a running WLS 6x instance in /bea/wls6***. I want to put
    another
    instance in /bea directory as a totally separate instance (/bea/wls6trn
    e.g.) Is this a valid way to do this or do I need to go ahead andinstall to
    another separate filesystem.
    daryl

  • Ejb security role & bea implementation

    A role has been defined in ejb-jar as following:
    <security-role>
    <description><![CDATA[Deployer User]]></description>
    <role-name>deployer</role-name>
    </security-role>
    <method-permission>
    <description><![CDATA[Deployer Method Permission]]></description>
    <role-name>deployer</role-name>
    <method>
    <description><![CDATA[All method for CCPStateBean]]></description>
    <ejb-name>CCPStateBean</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    If the principal is included in the weblogic-ejb-jar as below, and the jndi lookup
    includes the SECURITY_PRINCIPAL (e.g., jzhu), the code works fine.
    <security-role-assignment>
    <role-name>deployer</role-name>
    <principal-name>jzhu</principal-name>
    </security-role-assignment>
    The problem comes when the principal is not included as above weblogic-ejb-jar
    instead a role "deployer" is defined in WLS's, The user ("jzhu") is defined in
    the deployer group. And the deployer group belongs to deployer role. The defaultRoleMapper
    is enabled. In this scenario, the access failed due to insufficient permission.
    Can ejb-jar's role relates to WLS's role. Please advise. THX.
    -John

    Thanks for the information. It works. I wish bea monitor this newsgroup since this
    is not in their document. By the way, the following links clarifies the relationship
    between DD and admin console security configuration.
    http://edocs.bea.com/wls/docs70/security/cli_apps.html#1090734
    -John
    "Arjuna Chala" <[email protected]> wrote:
    I don't know about "defaultRoleMapper", but this works
    <security-role-assignment>
    <role-name>deployer</role-name>
    <principal-name>deployer</principal-name>
    </security-role-assignment>
    where <role-name> maps to a ejb-jar role and <principal-name> maps to
    a
    weblogic group (in this case).
    "john" <[email protected]> wrote in message
    news:[email protected]..
    A role has been defined in ejb-jar as following:
    <security-role>
    <description><![CDATA[Deployer User]]></description>
    <role-name>deployer</role-name>
    </security-role>
    <method-permission>
    <description><![CDATA[Deployer Method Permission]]></description>
    <role-name>deployer</role-name>
    <method>
    <description><![CDATA[All method for CCPStateBean]]></description>
    <ejb-name>CCPStateBean</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    If the principal is included in the weblogic-ejb-jar as below, andthe
    jndi lookup
    includes the SECURITY_PRINCIPAL (e.g., jzhu), the code works fine.
    <security-role-assignment>
    <role-name>deployer</role-name>
    <principal-name>jzhu</principal-name>
    </security-role-assignment>
    The problem comes when the principal is not included as aboveweblogic-ejb-jar
    instead a role "deployer" is defined in WLS's, The user ("jzhu") isdefined in
    the deployer group. And the deployer group belongs to deployer role.The
    defaultRoleMapper
    is enabled. In this scenario, the access failed due to insufficientpermission.
    Can ejb-jar's role relates to WLS's role. Please advise. THX.
    -John

  • WLS with Cocoon

    Has anyone tried using Apache's Cocoon for managing web publishing? I've
    has a go with Xalan and Xerces, and been pleased with these to date. I've
    now come across Apache's Cocoon, and would be interested to here the
    opinions of anyone who has used it already.
    Mark.

    I also managed to get cocoon and weblogic 451 working without too much
    difficulty.
    However I have't been able to suss out the mechanism for passing a default
    file to the cocoon servlet.
    Anybody know what to do?
    Humphrey Sheil <[email protected]> wrote in message
    news:[email protected]...
    I got Cocoon 1.7.4 working with weblogic 5.1 very easily (apart from one
    major issue which I'll detail and gripe about below ;-)).
    I used the instructions posted on the Cocoon list by Philip Aston (which
    I've included below) which worked but one change was required.
    I got a problem (about 50% of the time) where weblogic would fail todeploy
    my cocoon war and also complain about another process listening on ports
    7001 / 7002 which simply wasn't true. Turns out that if weblogic isunable
    to parse the web.xml that comes with cocoon, I had to replace it with an
    example taken from the weblogic examples directory (with the relevant
    information included). The way weblogic deals with this - cascading the
    error in deploying to affect the port listening is not good.
    Once I got this working, I hooked up security etc. in about 10 minutesusing
    the servlet 2.2 form-based authentication and am generally very happy with
    the weblogic-cocoon integration.
    Here are the posted instructions and I'm also attaching my web.xml file asa
    reference. I didn't have any problems getting XSP to work (although I'mnot
    using it at all - just hitting the samples provided). Even given thepoints
    Philip makes below about losing hot deploy abilities, your EJBs should
    deploy fine with this turned off.
    Regards,
    Humphrey
    Philip Aston wrote:
    I've been playing with using Cocoon 1.7.4 in conjunction with BEA
    WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
    of this to the installation guide. You might also like to add a
    success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
    1.2.2.)
    WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
    recipe:
    - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
    distribution) to your CLASSPATH. (See below). If you're using Java
    2, you should also add the tools.jar file from the JDK distribution
    to your CLASSPATH.
    - Create a new subdirectory tree of your WLS run time directory
    "cocoonwar/WEB-INF" and copy the default web.xml file (from the
    src directory of the distribution) there.
    - Copy the cocoon.properties from the conf directory of the
    distribution to cocoonwar/WEB-INF and updated the web.xml file to
    refer to it.
    - Copy the samples directory from the distribution to cocoonwar
    - Map the web application into the WLS URI name space by adding the
    following line to your weblogic.properties file:
    weblogic.httpd.webApp.cocoon=cocoonwar
    Start WLS, point your browser at
    "http://localhost:7001/cocoon/samples/index.xml" and away you go.
    Classpaths and XSP:
    To support hot deployment of EJB's and Servlets, WebLogic Server
    uses its own class loader with its own classpath (the "WebLogic
    classpath"). Normally you'd put all the WebLogic Server container
    code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
    Server can start up) and add all your application code (stuff that
    needs to be able to be redeployable) to the WebLogic classpath.
    Cocoon is effectively "container" code, and the XSP processor uses
    dynamic classloading which only understands the Java CLASSPATH, so
    you should put all of the Cocoon jars in CLASSPATH.
    The big problem with this is that you can't use any code that loads
    from the WebLogic classpath within XSP's. This includes all of the
    WebLogic API, so is a PITA. To overcome this, either the way Cocoon
    loads classes needs to be modified (Stefano, is this easy?), or the
    WebLogic Server class loader needs to be disabled (in which case you
    have to be willing to live without hot redeployment).
    To disable the WebLogic class loader, put your application classes,
    the Cocoon jars and all of the WebLogic Server stuff into the Java
    CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
    Java command at the end of you WebLogic start script.
    - Phil
    This is not an official BEA response. Please do not send me unrelated
    WebLogic support questions - I am unable to answer them. Instead
    please use the BEA developer newsgroups - see
    http://developer.bea.com, or contact BEA support.
    Philip Aston - Senior Consultant
    BEA Professional Services (Northern Europe)
    "Bob" <[email protected]> wrote in message
    news:[email protected]...
    I have been trying to get Cocoon working with WL. So far it has been a
    lot
    of trouble. I am mostly interested in getting XSP to work. The firstthing
    you need to do is usethe -Dweblogic.system.disableWeblogicClassPath=true
    command to turn off dynamic class loading. The problem I am now havingis
    that some of my EJBs won't deploy.
    If you don't want XSP Cocoon works well.
    -Bob
    Mark Bower <[email protected]> wrote in message
    news:[email protected]...
    Has anyone tried using Apache's Cocoon for managing web publishing?
    I've
    has a go with Xalan and Xerces, and been pleased with these to date.I've
    now come across Apache's Cocoon, and would be interested to here the
    opinions of anyone who has used it already.
    Mark.

  • Weblogic apache plugin and webservices

    Can I use the weblogic plugin on a DMZ based Apache server and use a 3 tier architecture
    to implement webservices.
    Using this model can a external application contact my webservices running in
    my internal network and can my weblogic/webservices server contact an external
    application/webservices using the same route i.e through the apache webserver
    and weblogic plugin.
    Any documentation regarding the architecture?

    Hi Anil,
    Not sure this is possible, unless you are using it as a proxy and setup
    the proper host/port mappings, see:
    http://edocs.bea.com/wls/docs81/webserv/client.html#1072224
    We have a very responsive security newsgroup, you might ask your
    configuration question there:
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.security&utag=
    Sorry, not much help (SNMH)
    Bruce
    Anil Jacob wrote:
    >
    Can I use the weblogic plugin on a DMZ based Apache server and use a 3 tier architecture
    to implement webservices.
    Using this model can a external application contact my webservices running in
    my internal network and can my weblogic/webservices server contact an external
    application/webservices using the same route i.e through the apache webserver
    and weblogic plugin.
    Any documentation regarding the architecture?

  • MaxMessageSizeExceededException in weblogic how to solve

    How to solve this Exception. When is sent more than 8000 bytes of data
    in the request weblogic 5.1 in solaris server gives me this error. But
    the same server and same configuration in Window NT with same
    SSLClient program does not give any expection even if i send 60000
    bytes in the request.
    Exception got in the weblogic server 5.1 in solaris server
    weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
    request headers of size 8320 bytes exceeds the configured maximum of
    8192 bytes]
    at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
    at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    SSLClient Program used: JSSE 1.0.2 package is used for SSL
    import java.io.*;
    import javax.net.ssl.*;
    import java.net.*;
    import com.sun.net.ssl.*;
    import java.security.KeyStore;
    public class SSLClient {
         public SSLClientCheck()
              System.out.println(" SSLClient is instantiated ...");     
         public String getSSLConnection(String host,String port,String
    keystorepwd,String truststorepwd,
                                            String keystorepath,String truststorepath,String
    filepath,String parName,String message)throws Exception
              String output = "";
              int iport = Integer.parseInt(port);
                             SSLSocketFactory factory = null;          
                             SSLContext ctx;
                             KeyManagerFactory kmf;                         
                             KeyStore ks;                         
                             KeyStore ks2;
                             TrustManagerFactory tmf;
                             char[] storepass = keystorepwd.toCharArray();
                             char[] truststorepass = truststorepwd.toCharArray();
                             ctx = SSLContext.getInstance("SSLv3");                    
                             kmf = KeyManagerFactory.getInstance("SunX509");
                             ks = KeyStore.getInstance("JKS");                         
                             ks.load(new FileInputStream(keystorepath), storepass);
                             kmf.init(ks, storepass);                         
                             tmf = TrustManagerFactory.getInstance("SunX509");                         
                             ks2 = KeyStore.getInstance("JKS");
                             ks2.load(new FileInputStream(truststorepath), truststorepass);
                             tmf.init(ks2);
                             ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);     
                             factory = ctx.getSocketFactory();
                   SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
                   socket.startHandshake();
                   PrintWriter out = new PrintWriter(
                                  new BufferedWriter(
                                  new OutputStreamWriter(
                                       socket.getOutputStream())));
                   out.println("GET " +
    filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
                   out.println();
                   out.flush();
                   if (out.checkError())
                        System.out.println("SSLSocketClient: java.io.PrintWriter error");
                   /* read response */
                   BufferedReader in = new BufferedReader(
                                  new InputStreamReader(
                                  socket.getInputStream()));
                        String inputLine ;                    
                        while ((inputLine = in.readLine()) != null){                         
                        output = output+inputLine;
                             //System.out.println(inputLine);                    
                   in.close();
                   out.close();
                   socket.close();                    
              return output;
         public static void main(String args[])
                   String host = "host name";
                   String port="7001";
                   String keystorepwd="cqrcqr";
                   String keystorepwd="changeit";
                   String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
                   String truststorepath="d:/jdk1.3/jre/security/cacerts";
                   String filepath="/servlets/SSLDemo";
                   String parName="xml_message";
                   String message="xml message";// of size more than 9000 bytes
              try{
              SSLClient ssl = new SSLClient();
              String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
              System.out.println(output);
              catch(Exception e)
                   e.printStackTrace();

    Hello
    I had taken a crack at this before but never got a response --
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.security&item=6948&utag=
    Can you look at my old post and see if that helps at all? Please let me know
    Joe Jerry
    "[email protected]" wrote:
    How to solve this Exception. When is sent more than 8000 bytes of data
    in the request weblogic 5.1 in solaris server gives me this error. But
    the same server and same configuration in Window NT with same
    SSLClient program does not give any expection even if i send 60000
    bytes in the request.
    Exception got in the weblogic server 5.1 in solaris server
    weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
    request headers of size 8320 bytes exceeds the configured maximum of
    8192 bytes]
    at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
    at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    SSLClient Program used: JSSE 1.0.2 package is used for SSL
    import java.io.*;
    import javax.net.ssl.*;
    import java.net.*;
    import com.sun.net.ssl.*;
    import java.security.KeyStore;
    public class SSLClient {
    public SSLClientCheck()
    System.out.println(" SSLClient is instantiated ...");
    public String getSSLConnection(String host,String port,String
    keystorepwd,String truststorepwd,
    String keystorepath,String truststorepath,String
    filepath,String parName,String message)throws Exception
    String output = "";
    int iport = Integer.parseInt(port);
    SSLSocketFactory factory = null;
    SSLContext ctx;
    KeyManagerFactory kmf;
    KeyStore ks;
    KeyStore ks2;
    TrustManagerFactory tmf;
    char[] storepass = keystorepwd.toCharArray();
    char[] truststorepass = truststorepwd.toCharArray();
    ctx = SSLContext.getInstance("SSLv3");
    kmf = KeyManagerFactory.getInstance("SunX509");
    ks = KeyStore.getInstance("JKS");
    ks.load(new FileInputStream(keystorepath), storepass);
    kmf.init(ks, storepass);
    tmf = TrustManagerFactory.getInstance("SunX509");
    ks2 = KeyStore.getInstance("JKS");
    ks2.load(new FileInputStream(truststorepath), truststorepass);
    tmf.init(ks2);
    ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
    factory = ctx.getSocketFactory();
    SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
    socket.startHandshake();
    PrintWriter out = new PrintWriter(
    new BufferedWriter(
    new OutputStreamWriter(
    socket.getOutputStream())));
    out.println("GET " +
    filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
    out.println();
    out.flush();
    if (out.checkError())
    System.out.println("SSLSocketClient: java.io.PrintWriter error");
    /* read response */
    BufferedReader in = new BufferedReader(
    new InputStreamReader(
    socket.getInputStream()));
    String inputLine ;
    while ((inputLine = in.readLine()) != null){
    output = output+inputLine;
    //System.out.println(inputLine);
    in.close();
    out.close();
    socket.close();
    return output;
    public static void main(String args[])
    String host = "host name";
    String port="7001";
    String keystorepwd="cqrcqr";
    String keystorepwd="changeit";
    String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
    String truststorepath="d:/jdk1.3/jre/security/cacerts";
    String filepath="/servlets/SSLDemo";
    String parName="xml_message";
    String message="xml message";// of size more than 9000 bytes
    try{
    SSLClient ssl = new SSLClient();
    String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
    System.out.println(output);
    catch(Exception e)
    e.printStackTrace();

  • Strange Cluster Startup Timing Issues (Solaris 2.7)

              When we start up our admin server for our WLS 6.0sp1 cluster (running on Solaris
              2.7), then try to start all the managed servers approximately simultaneously,
              the managed servers come up apparently normally (no errors in the logs) but no
              EJBs ever deploy.
              If we follow the same steps, but wait until each server is all the way up before
              starting the next, everything is fine.
              Has anyone else run into this?
              -daniel
              

    Hmm, I wonder if they "cannot" or "will not" supply you the patch...
              Oh well, hopefully this won't get me in trouble! Here's the patch, stick it in your weblogic /lib
              directory or in CLASSPATH, and add the following to your startup command:
              -Dweblogic.rmi.queuesize=n
              And if you are having problems, don't tell BEA who gave this to you! :-)
              Gene
              "Aaron Oas" <[email protected]> wrote in message
              news:[email protected]...
              > Thanks for the information.
              >
              > We wrote to BEA support; here's the response (i.e. no patch is forthcoming):
              >
              > ----------------------------- begin BEA
              > response -----------------------------
              > FR: tommy
              >
              > CASE_ID_NUM: 248170
              >
              > MESSAGE:
              >
              > Daniel,
              >
              > My name is Tommy, and I'm a Developer Relations Engineer with
              > BEA Technical Support. I wanted to drop you a quick note to tell you
              > that I've picked up your support case.
              >
              > At this time engineering does not have a patch for this CR. This issue is
              > slated to be fixed in WLS 6.1 release which is scheduled for end of July.
              > At this time engineering is pushing to have 6.1 released on schedule, and
              > since
              > there is a valid work around for this issue, they will not provide a patch.
              >
              > The work around is to simply boot your servers in increments of about 30
              > seconds.
              >
              > Thanks in Advance,
              >
              > Tommy Butcher
              >
              > ----------------------------- end BEA response -----------------------------
              >
              > I guess it could be worse.
              >
              > - Aaron
              >
              >
              > "Gene Chuang" <[email protected]> wrote in message
              > news:[email protected]...
              > > Currently, weblogic_admin_rmi_queue native thread count is fixed at 3 (or
              > was it 4?). I did get a
              > > patch which allows me to set the count as a flag at startup, although it
              > would seem the longterm
              > > solution is for WL to self-manage the thread count dynamically. For
              > anyone who needs this interim
              > > solution, write to support and mention the CR.
              > >
              > > Gene
              > >
              > > "Aaron Oas" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > Gene (and clusterers in general) -
              > > >
              > > > It seems odd that so few people have reported problems with concurrently
              > > > starting servers in a cluster if it is a limitation of
              > > > weblogic_admin_rmi_queue native thread count. Is it a limitation
              > imposed by
              > > > the Solaris kernel on weblogic (i.e. Solaris max threads per process or
              > per
              > > > user can't be set high enough in /etc/system)?
              > > >
              > > > I would think that for a mission-critical environment, starting managed
              > > > servers in a weblogic cluster would ideally be automated and
              > simultaneous;
              > > > rather than serial, and certainly rather than manual (log into each
              > solaris
              > > > box in turn and run the startup script by hand).
              > > >
              > > > Does anyone out there running weblogic clusters automate the startup of
              > > > their weblogic cluster as a whole (e.g. a startup script on the admin
              > server
              > > > box that cranks up all the remote managed servers as well)?
              > > >
              > > > I have ideas about how to do this without using rexec and .rhosts files,
              > but
              > > > it's not trivial (create a listener on each box wait for startup
              > command,
              > > > check for managed server process, run startup script...), and I'm
              > wondering
              > > > if:
              > > > 1) there is a well-known approach to starting up all the managed servers
              > on
              > > > remote boxes, and
              > > > 2) there is a solution to the apparent requirement that clustered
              > managed
              > > > servers can't start at the same time, even on separate boxes
              > > >
              > > > Hope there are some thoughts on this out there,
              > > >
              > > >
              > > > - Aaron
              > > > "Gene Chuang" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > I've filed a issue, CR042545, where I cannot concurrently start more
              > than
              > > > 2 managed servers in
              > > > > Solaris 2.7 due to weblogic_admin_rmi_queue native thread count
              > > > limitations... hopefully it has
              > > > > been fixed in 6.1?
              > > > >
              > > > > Gene
              > > > >
              > > > > "Fred Bloggs" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > >
              > > > > > When we start up our admin server for our WLS 6.0sp1 cluster
              > (running on
              > > > Solaris
              > > > > > 2.7), then try to start all the managed servers approximately
              > > > simultaneously,
              > > > > > the managed servers come up apparently normally (no errors in the
              > logs)
              > > > but no
              > > > > > EJBs ever deploy.
              > > > > >
              > > > > > If we follow the same steps, but wait until each server is all the
              > way
              > > > up before
              > > > > > starting the next, everything is fine.
              > > > > >
              > > > > > Has anyone else run into this?
              > > > > >
              > > > > > -daniel
              > > > >
              > > > >
              > > >
              > > >
              > >
              > >
              >
              >
              [cr042545.jar]
              

  • Error 403--Forbidden

    Hi all ,
    I create a simple stateless ejb named LoginSession to manage the login task
    , package it to a ejb jar file named login.jar , and then I want to explode
    it as a wls7.0 webservice , the build.xml like this :
    <project name="buildWebservice" default="ear">
    <target name="ear">
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    </servicegen>
    </target>
    </project>
    When after ant running successfully , ant generated login.ear file for me ,
    but I find some ploblems :
    1 , the ear file contains login jar and web-service.war file , similar with
    wls6.1 webservice , but the web.xml file in web-service.war is different
    from wls6.1 , the 7.0 file is black ! only the following 3 lines :
    #1 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
    2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    #2 <web-app>
    #3 </web-app>
    2 , I can not file the wsdl.jsp file in the ear file , whick will contained
    in 6.1 webservice .
    3 , when I want to request http://localhost:7001/login/ , error message
    list in my browser :
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it.
    Authorization will not help and the request SHOULD NOT be repeated. If the
    request method was not HEAD and the server wishes to make public why the
    request has not been fulfilled, it SHOULD describe the reason for the
    refusal in the entity. This status code is commonly used when the server
    does not wish to reveal exactly why the request has been refused, or when no
    other response is applicable.
    ps , I do need client jar , so in build.xml , does not include client
    element , and when I insert it to the xml file , result is the same.
    Any response will be appreciated .
    Thank you.
    lcl

    Thank you ,Manoj
    "manoj cheenath" <[email protected]> :[email protected]...
    see comments inline:
    regards,
    -manoj
    "lcl" <[email protected]> wrote in message news:[email protected]...
    Hi all ,
    I create a simple stateless ejb named LoginSession to manage the login task
    , package it to a ejb jar file named login.jar , and then I want to explode
    it as a wls7.0 webservice , the build.xml like this :
    <project name="buildWebservice" default="ear">
    <target name="ear">
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    </servicegen>
    </target>
    </project>
    When after ant running successfully , ant generated login.ear file for me ,
    but I find some ploblems :
    1 , the ear file contains login jar and web-service.war file , similar with
    wls6.1 webservice , but the web.xml file in web-service.war is different
    from wls6.1 , the 7.0 file is black ! only the following 3 lines :
    #1 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
    2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    #2 <web-app>
    #3 </web-app>
    In WLS 7.0 there is a new DD file for Web Service. Look for
    web-services.xml file inside the WEB-INF dir. There is no
    change needed to the web.xml file.
    2 , I can not file the wsdl.jsp file in the ear file , whick will contained
    in 6.1 webservice .
    The WSDL is generated from the deployment information at
    runtime.
    3 , when I want to request http://localhost:7001/login/ , error message
    list in my browser :
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it.
    Authorization will not help and the request SHOULD NOT be repeated. If the
    request method was not HEAD and the server wishes to make public why the
    request has not been fulfilled, it SHOULD describe the reason for the
    refusal in the entity. This status code is commonly used when the server
    does not wish to reveal exactly why the request has been refused, or when no
    other response is applicable.
    <servicegen destEar="login.ear" contextURI="login">
    <service ejbJar="login.jar" includeEJBs="LoginSession"
    targetNamespace="http://www.ricobest.com/webservice/login"
    serviceName="LoginSession" serviceURI="/LoginSession" generateTypes="True"
    expandMethods="True"/>
    I think the URL you need to hit is:
    http://localhost:7001/login/LoginSession
    ps , I do need client jar , so in build.xml , does not include client
    element , and when I insert it to the xml file , result is the same.
    You can use clientgen to generate the client.jar file
    by pointing to the deployed WSDL.
    Any response will be appreciated .
    Thank you.
    lcl
    [att1.html]

  • Foreign JMS Providers with WebLogic Server does not close connection

              Hello All,
              We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
              WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
              context factory to bind MQ.
              We found a number of LDAP connections are getting opened by JNDIMapper, but it's
              not getting closed.
              Can some one give some clue to this ?
              Also any suggestion to serve the current purpose is welcome.
              Thanks,
              Sudarson
              

    What version are you using? "wlsmqseries.zip" does enlisting of MQ JMS
              sessions in XA transactions, but WLS 8.1 does that for you out of the box.
              If you're using 8.1, it would be better to use the new 8.1 features for
              foreign JMS providers.
              A place to start is the "Using WebLogic JMS with EJBs and Servlets" section
              of the JMS programming documentation for 8.1, and there have been many other
              posts on this newsgroup with details. (There also appear to be quite a few
              customers using this feature in their own systems, judging from the number
              of posts.)
              greg
              "sudarson" <[email protected]> wrote in message
              news:40bf05ea$1@mktnews1...
              >
              > Reposting the message. Awaiting response from newsgroup or BEA
              > Thanks,
              > Sudarson
              > "sudarson" <[email protected]> wrote:
              > >
              > >Hello All,
              > >
              > >We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for
              integrating
              > >WebLogic Server with MQ so that we can incorporate XA transactions. We
              > >use LDAP
              > >context factory to bind MQ.
              > >
              > >We found a number of LDAP connections are getting opened by JNDIMapper,
              > >but it's
              > >not getting closed.
              > >
              > >Can some one give some clue to this ?
              > >
              > >Also any suggestion to serve the current purpose is welcome.
              > >
              > >Thanks,
              > >Sudarson
              >
              

  • [Fwd: Client accessing MBeanHome for more than one domain receives SecurityException]

    Fwd'ing to security newsgroup
    -------- Original Message --------
    Subject: Client accessing MBeanHome for more than one domain receives
    SecurityException
    Date: 4 Mar 2004 07:27:33 -0800
    From: Dinesh Bhat <[email protected]>
    Reply-To: Dinesh Bhat <[email protected]>
    Organization: BEA NEWS SITE
    Newsgroups: weblogic.developer.interest.management
    Hi,
    When a client accesses MBeans of more than one domains (Weblogic 8.1)
    that have
    different passwords, it receives a SecurityException. This occurs when
    the MBeanHome
    for each domain is looked up at initialization and reused for each
    request ( to
    access MBeans ). The security exception does not occur if the MBeanHome
    for each
    domain is looked up for each request. On initial review, this behavoir
    seems inconsistent.
    Looking up the MBeanHome for each request may introduce a significant
    overhead.
    I am not sure if concurrent lookups would also cause the same problem.
    I have read on another post that we can work around this problem by
    establishing
    a trust relationship between the servers, but this may not be feasible
    when one
    is monitoring a lot of servers and the overhead of configuration may be
    an issue.
    I have attached code that can reproduce the problem.
    Please advise on the correct approach.
    Thanks
    Dinesh Bhat
    Panacya Inc.
    import java.util.ArrayList;
    import java.util.Set;
    import java.util.HashMap;
    import java.util.Iterator;
    import java.util.Hashtable;
    import javax.management.MBeanServer;
    import javax.naming.Context;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    * This class reproduces the Security Exception that is caused when a client tries to access
    * MBeans of more than one domain with different weblogic passwords. Here is the stacktrace of the
    * exception
    * java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
         at weblogic.management.internal.AdminMBeanHomeImpl_811_WLStub.getDomainName(Unknown Source)
         at WLSecurityTest.getWeblogicInfo(WLSecurityTest.java:140)
         at WLSecurityTest.runTest(WLSecurityTest.java:75)
         at WLSecurityTest.<init>(WLSecurityTest.java:66)
         at WLSecurityTest.main(WLSecurityTest.java:51)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.intellij.rt.execution.application.AppMain.main(Unknown Source)
    Caused by: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
         at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:682)
         at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:181)
         at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:814)
         at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:299)
         at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:920)
         at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:841)
         at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
         at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
         at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    * Note: the exception is caused only when the MBeanHome for each domain is cached and used for subsequent
    * transactions. The exception does not occur if the MBeanHome for each domain is looked up for each transaction. This
    * would significant overhead in practice. Also the transactions across the various domains occurs serially, hence
    * the effect of concurrent lookups has to be tested.
    * Usage:
    * This class has been tested with weblogic 8.1
    * The class needs weblogic.jar in its classpath
    * One can specify the weblogic details as System properties. The properties need to be specified in
    * the following format:
    * wls.host.n, wls.userId.n, wls.password.n where n is the weblogix instance number. Also specify
    * the boolean system property reconnect.each.iteration to toggle between reconnecting or not reconnecting
    * for each iteration. When not reconnecting for each iteration, the MBeanHome is reused and the Security Exception
    * occurs.
    * Following is the example of system properties
    * -Dwls.host.0=localhost:7001 -Dwls.userId.0=weblogic -Dwls.password.0=weblogic
    * -Dwls.host.1=localhost:7011 -Dwls.userId.1=weblogic -Dwls.password.1=weblogic1
    * -Dwls.host.2=localhost:7021 -Dwls.userId.2=weblogic -Dwls.password.2=weblogic2
    * -Dreconnect.each.iteration=false
    public class WLSecurityTest
    ArrayList wlsDetailsList = new ArrayList();
    HashMap connectionMap = new HashMap();
    public static void main(String[] args)
    try
    WLSecurityTest wlSecurityTest = new WLSecurityTest();
    catch (Exception e)
    e.printStackTrace();
    * Constructor
    * @throws Exception
    public WLSecurityTest() throws Exception
    int noOfTries = 10;
    getWLSDetails();
    for( int i=0; i <= noOfTries; i++)
    runTest();
    * Runs the test
    private void runTest()
    for (int i = 0; i < wlsDetailsList.size(); i++)
    WLSDetails wlsDetails = (WLSDetails) wlsDetailsList.get(i);
    getWeblogicInfo(wlsDetails);
    * Get Weblogic details from System properties
    * @throws Exception
    private void getWLSDetails() throws Exception
    wlsDetailsList = new ArrayList();
    String hostKeyTmpl = "wls.host";
    String userIdKeyTmpl = "wls.userId";
    String passwordKeyTmpl = "wls.password";
    boolean done = false;
    for (int i = 0; !done; i++)
    WLSDetails wlsDetails = new WLSDetails();
    String hostKey = hostKeyTmpl + "." + Integer.toString(i);
    String userIdKey = userIdKeyTmpl + "." + Integer.toString(i);
    String passwordKey = passwordKeyTmpl + "." + Integer.toString(i);
    wlsDetails.hostName = System.getProperty(hostKey);
    done = (wlsDetails.hostName == null) || (wlsDetails.hostName.length() == 0);
    if (!done)
    wlsDetails.userId = System.getProperty(userIdKey);
    wlsDetails.password = System.getProperty(passwordKey);
    connect(wlsDetails);
    wlsDetailsList.add(wlsDetails);
    * Lookup the MBeanHome for the specified weblogic server
    * @param wlsDetails
    * @throws Exception
    public synchronized void connect(WLSecurityTest.WLSDetails wlsDetails) throws Exception
    Context ctx = null;
    MBeanHome mbHomeLocal = null;
    try
    Environment env = new Environment();
    env.setProviderUrl("t3://" + wlsDetails.hostName);
    env.setSecurityPrincipal(wlsDetails.userId);
    env.setSecurityCredentials(wlsDetails.password);
    Hashtable hashtable = env.getProperties();
    System.out.println(hashtable.toString());
    ctx = env.getInitialContext();
    wlsDetails._mBeanHome = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    catch (Exception e)
    e.printStackTrace();
    * Gets weblogic information using MBeans
    * @param wlsDetails
    public synchronized void getWeblogicInfo(WLSDetails wlsDetails)
    try
    boolean reconnectEachIteration =
    Boolean.getBoolean("reconnect.each.iteration");
    if( (reconnectEachIteration) || ((wlsDetails._mBeanHome == null) && (!reconnectEachIteration) ))
    connect(wlsDetails);
    MBeanHome mbHomeLocal = wlsDetails._mBeanHome;
    String domainName = mbHomeLocal.getDomainName();
    Set allMBeans = mbHomeLocal.getAllMBeans();
    System.out.println("Size: " + allMBeans.size());
    Set clusterMBeans = mbHomeLocal.getMBeansByType("Cluster", domainName);
    System.out.println(clusterMBeans);
    MBeanServer mBeanServer = mbHomeLocal.getMBeanServer();
    catch (Exception ex)
    ex.printStackTrace();
    * Class that holds weblogic server details
    class WLSDetails
    String hostName = "";
    String userId = "";
    String password = "";
    MBeanHome _mBeanHome = null;

    If Server version is 61.
    Make user "system" password of all weblogic servers same.
    If Server version above 61(70,81)
    In the Security Advanced Settings un check generated credential and specify a common credentail for all the weblogic servers(domains).

  • Possible Bug?  autotype + wsdl2service generates implementation that does not conform to the WSDL

    Hey folks,
    I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD that I've
    been using for awhile now to generate an Apache Axis 1.2 beta Document Literal
    Web Service implementation. I'm now trying to use the same WSDL to generate a
    BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running into
    problems.
    I've attached the WSDL, XSD, and build script that I'm using to generate the implementation.
    It deploys fine, but notice that the autogenerated WSDL that is returned from
    the deployed BEA Web Service contains two <xs:schema> sections: one for the imported
    WSDL (as expected) and one for several new elements that seem to get substituted
    for the elements used in the orignal WSDL message parts.
    The results of this are two fold:
    1) the autogenerated WSDL appears to be invalid when loaded into both XMLSpy and
    SOAPscope
    2) the SOAP requests to invoke the operations on the service do not conform to
    the hand crafted original WSDL. I've attached examples of both a BEA generated
    SOAP request and an EXPECTED SOAP request.
    I've poured over both the types.xml and the web-services.xml, and I'll be damned
    if I can see the problem. I'm wondering if the way I import schemas and reference
    elements declared therein is somehow not supported by BEA's ant tasks?
    Any advice or pointers at all would be appreciated.
    Regards,
    -Jonathan Anderson
    Booz Allen Hamilton
    [BankService2.zip]

    I don't know if you already now this but if you are using <autotype> to generate
    the types.xml from the XML Schema then you should first
    1) autotype the imported schema first.
    2) Then for the actual achema (that uses the imported xsd) <autotype> but with
    the
    typeMappingFile="importedSchemas/types.xml"
    option set to the types.xml output from 1)
    The types.xml will then contain all types from both Schemas. You can then pass
    this final types.xml from 2) to <source2wsdd> via
    typesInfo="types.xml"
    Any help ?
    Pete
    "Jonathan Anderson" <[email protected]> wrote:
    >
    Definitely seems as if BEA monitors these newsgroups. Lot's of developers
    talking
    to themselves, it seems.
    <sigh>
    "Jonathan Anderson" <[email protected]> wrote:
    Hey folks,
    I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD
    that I've
    been using for awhile now to generate an Apache Axis 1.2 beta Document
    Literal
    Web Service implementation. I'm now trying to use the same WSDL togenerate
    a
    BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running
    into
    problems.
    I've attached the WSDL, XSD, and build script that I'm using to generate
    the implementation.
    It deploys fine, but notice that the autogenerated WSDL that is returned
    from
    the deployed BEA Web Service contains two <xs:schema> sections: onefor
    the imported
    WSDL (as expected) and one for several new elements that seem to get
    substituted
    for the elements used in the orignal WSDL message parts.
    The results of this are two fold:
    1) the autogenerated WSDL appears to be invalid when loaded into both
    XMLSpy and
    SOAPscope
    2) the SOAP requests to invoke the operations on the service do notconform
    to
    the hand crafted original WSDL. I've attached examples of both a BEA
    generated
    SOAP request and an EXPECTED SOAP request.
    I've poured over both the types.xml and the web-services.xml, and I'll
    be damned
    if I can see the problem. I'm wondering if the way I import schemas
    and reference
    elements declared therein is somehow not supported by BEA's ant tasks?
    Any advice or pointers at all would be appreciated.
    Regards,
    -Jonathan Anderson
    Booz Allen Hamilton

  • Setting Isolation Level In A UserTransaction

    We are having a problem where a class creates a UserTransaction from the InitialContext,
    but does not see any database changes made by other EJBs even though they have
    been committed. This "seems" like an isolation issue.
    What is the default isolation level for UserTransaction? And since it appears
    that it is not seeing committed data, what level should it be set to? (i.e. TRANSACTION_READ_COMMITTED
    would be nice...)

    this is mirrored from the transaction newsgroup:
    Joseph Weinstein <[email protected]> wrote:
    >
    >
    Interesting, but it's not an isolation level issue. There is no DBMS
    isolation level
    that could cause a user not to see already-committed data.Well, we are using Oracle as our backend and it supports Read Uncommitted, Read
    Committed and Serializable. The Serializable option would prevent a transaction
    from seeing any committed data to a table (i.e. prevents unrepeatable reads).
    The default isolation level of most DBMSes is READ_COMMITTED, and you
    should
    never have to change it, and you should be able to see already-committed
    data.I agree, but that is not happening for us (and this gets somewhat complicated
    with JMS). What is Weblogic 8.1's default isolation level for any transaction.
    From the link below, I get the impression it is SERIALIZABLE which would explain
    the behaviour I'm seeing. Athough the article seems to be talking about CMT (container
    transation), I would suspect a BMT (bean managed transaction) be similar (just
    manual).
    If this only confuses things, please let me know the easiest way to communicate
    this issue (code, etc..)
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.transaction&item=227&utag
    (from the article)
    Subject: Re: What is ths default transaction isolation level
    Date: Mon, 12 Feb 2001 15:27:24 -0500
    From: "Cameron Purdy" <[email protected]>
    Organization: BEA SYSTEMS Inc
    Newsgroup: weblogic.developer.interest.transaction
    serializable
    -- Cameron Purdy Tangosol, Inc. http://www.tangosol.com +1.617.623.5782 WebLogic
    Consulting Available
    "mrityunjay" <[email protected]> wrote in message news:3a86c781$[email protected]..
    Hi , > If transaction isolation , for a EJB is not specified what is the > defaulttransaction isolation level > Thanks > Jay > >

  • Problem in loading the WL6.1 Examples Web Applications

    While the server 6.1 is starting, an error message is displayed in the DOS window.
    19.10.2001 14:28:28 CEST> <Debug> <HTTP> <Could not resolve entity "-//BEA Systems, Inc.//DTD Web Application 6.1//EN". Check
    your dtd reference.>
    <19.10.2001 14:28:30 CEST> <Error> <HTTP> <[examplesWebApp] Error reading Web application "C:\bea\wlserver6.1\config\examples\a
    pplications\examplesWebApp"
    java.net.UnknownHostException: www.bea.com
    It sounds to be related with the web.xml file. I thank you by advance for your help.
    Cheers

    Hi there,
    Many thanks for your answer. I am fine but I am sure I will be even more fine
    when I solve this technical issue.
    I checked the weblogic.xml file as you suggested and it is OK.
    I even tried to access the URL "http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd"
    with IE5. I had some doubt regarding our corportate proxy. But it worked fine.
    I can access successfully the dtd with a browser. I really don't see what is going
    wrong. I attached in case of the weblogic.xml file for your examination.
    Here is an extract of the error message displayed in the DOS window.
    <23.10.2001 13:52:50 CEST> <Info> <J2EE> <Deployed : DefaultWebApp>
    <23.10.2001 13:52:50 CEST> <Info> <HTTP> <[HTTP examplesServer] Loading web app:
    examplesWebApp>
    <23.10.2001 13:52:50 CEST> <Info> <HTTP> <[examplesServer] Loading "examplesWebApp"
    from directory: "C:\bea\wlserver6.1\config\
    examples\applications\examplesWebApp">
    <23.10.2001 13:52:50 CEST> <Warning> <HTTP> <servlet DisplaySetToPage is referenced
    but not defined in web.xml>
    <23.10.2001 13:52:50 CEST> <Debug> <HTTP> <Could not resolve entity "//BEA Systems,
    Inc.//DTD Web Application 6.1//EN". Check y
    our dtd reference.>
    <23.10.2001 13:52:52 CEST> <Error> <HTTP> <[examplesWebApp] Error reading Web
    application "C:\bea\wlserver6.1\config\examples\a
    pplications\examplesWebApp"
    java.net.UnknownHostException: www.bea.com
    at java.net.InetAddress.getAllByName0(InetAddress.java:571)
    etc....
    Could the origin of my problem come from the aforementionned error message "<servlet
    DisplaySetToPage is referenced but not defined in web.xml>" ?
    I thank you once again by advance for your help and support.
    Cheers
    Athmani H.
    BEA Weblogic Support <[email protected]> wrote:
    Hi Athmani
    Greetings...!
    How are you doing?.
    Weblogic 6.1 examples web application, examplesWebApp, should have the
    below given DOCTYPE in the weblogic.xml.
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application
    6.1//EN"
    "http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd">
    Please check that.
    Thanks & Regards
    BEA Systems Supoport
    Athmani wrote:
    While the server 6.1 is starting, an error message is displayed inthe DOS window.
    19.10.2001 14:28:28 CEST> <Debug> <HTTP> <Could not resolve entity"-//BEA Systems, Inc.//DTD Web Application 6.1//EN". Check
    your dtd reference.>
    <19.10.2001 14:28:30 CEST> <Error> <HTTP> <[examplesWebApp] Error readingWeb application "C:\bea\wlserver6.1\config\examples\a
    pplications\examplesWebApp"
    java.net.UnknownHostException: www.bea.com
    It sounds to be related with the web.xml file. I thank you by advancefor your help.
    Cheers
    [weblogic.xml]

  • [Fwd: Re: rdbms realm and connection pool]

    Hi,
    One reason why I would like to use the connection pool for the RDBMS
    realm is because there is the retry machanism built into the connection
    pool. With this retry, I don't need to re-start WebLogic if the DB
    server is somehow re-started. With the current implementation, all the
    connections maintained by the realm will become invalid if the DB server
    has been restarted independently.
    -------- Original Message --------
    Subject: Re: rdbms realm and connection pool
    Date: Wed, 27 Sep 2000 09:32:47 +0100
    From: "Terry" <[email protected]>
    Reply-To: "Terry" <[email protected]>
    Organization: BEA SYSTEMS Inc
    Newsgroups: weblogic.developer.interest.security
    References: <[email protected]>
    I believe not- the realm restricts access to connection pools to those
    who
    are allowed it, so if the realm needs the connection pool to start up,
    and
    you can't open the connection pool without the realm then you have a bit
    of
    a no-chicken and no-egg situation, which is I believe one of the reasons
    why
    there is no use of connection pools, ejbs, jndi, servlets etc. in the
    realm
    (along with other reasons, like why would it be provided with a servlet)
    The delegate pool acts somewhat similarly to a connection pool, and can
    even
    use the same database, so I'm not sure what the advantage would be
    Terry
    Nirmala devi <[email protected]> wrote in message
    news:[email protected]..
    >
    I think the rdbms realm uses different connection as it need to be setbefore
    the connection pool for Database.Is there any that i can point my rdbmsrealm to use
    the connection pool for Database instead
    Thanks in advance
    Nirmala

    I believe not- the realm restricts access to connection pools to those who
    are allowed it, so if the realm needs the connection pool to start up, and
    you can't open the connection pool without the realm then you have a bit of
    a no-chicken and no-egg situation, which is I believe one of the reasons why
    there is no use of connection pools, ejbs, jndi, servlets etc. in the realm
    (along with other reasons, like why would it be provided with a servlet)
    The delegate pool acts somewhat similarly to a connection pool, and can even
    use the same database, so I'm not sure what the advantage would be
    Terry
    Nirmala devi <[email protected]> wrote in message
    news:[email protected]..
    >
    I think the rdbms realm uses different connection as it need to be setbefore
    the connection pool for Database.Is there any that i can point my rdbmsrealm to use
    the connection pool for Database instead
    Thanks in advance
    Nirmala

  • Sams Teach Yourself Javaserver Pages in 24 Hours

    Hi.
    I'm a new user of Weblogic and I'm presently learning JSP. Like most people do
    I went out and bought a beginner's book on JSP.
    The book I bought is Sams Teach Yourself Javaserver Pages in 24 Hours by Jose
    Annunziato (DSc) and Stephanie Fesler Kaminaris.
    Up to now I've spent the 5 first hours trying to run my first JSP on Weblogic
    (seems like it's going to take more than 24 hours to complete the book!). The
    problem was simply a wrong path for the compileCommand variable in the weblogic.properties
    file.
    the authors suggest the following:
    compileCommand=c:/jdk1.2.2/javac.exe
    when it should be:
    compileCommand=c:/jdk1.2.2/bin/javac.exe
    The point I want to make is that this type of error is far too frequent in computer
    programming books, considering the prohibitive price they're sold at, and it shows
    a lack of respect on the part of the authors and/or publishers for the people
    who buy them. I encourage everyone to do like me and denounce these people on
    newsgroups all over the Internet. When their sales go down they will surely take
    action.
    On the positive side, I want to congratulate BEA for their newsgroups. This is
    how I finally got on the track to solving my problem. Otherwise, I probably would
    have spent at least 24 hours hacking around just to get that first JSP to work
    in Weblogic.
    Thanks.

    Hi.
    I'm a new user of Weblogic and I'm presently learning JSP. Like most people do
    I went out and bought a beginner's book on JSP.
    The book I bought is Sams Teach Yourself Javaserver Pages in 24 Hours by Jose
    Annunziato (DSc) and Stephanie Fesler Kaminaris.
    Up to now I've spent the 5 first hours trying to run my first JSP on Weblogic
    (seems like it's going to take more than 24 hours to complete the book!). The
    problem was simply a wrong path for the compileCommand variable in the weblogic.properties
    file.
    the authors suggest the following:
    compileCommand=c:/jdk1.2.2/javac.exe
    when it should be:
    compileCommand=c:/jdk1.2.2/bin/javac.exe
    The point I want to make is that this type of error is far too frequent in computer
    programming books, considering the prohibitive price they're sold at, and it shows
    a lack of respect on the part of the authors and/or publishers for the people
    who buy them. I encourage everyone to do like me and denounce these people on
    newsgroups all over the Internet. When their sales go down they will surely take
    action.
    On the positive side, I want to congratulate BEA for their newsgroups. This is
    how I finally got on the track to solving my problem. Otherwise, I probably would
    have spent at least 24 hours hacking around just to get that first JSP to work
    in Weblogic.
    Thanks.

Maybe you are looking for

  • SendRedirect doesn't work!

    Hi all! I've got a strange problem: when I use a PrintWriter for sending data to user in my servlets, response.sendRedirect("smth") works fine, but when I started to use ServletOutputStream, sendRedirect stopped working! Please help! Thnak you

  • Need Help on FM - ISU_S_DEVICEMOD_CHANGE

    Hi Experts, We have a requirement where we have to change the Register Configurations for the Device(EG42) programatically using Function Module: ISU_S_DEVICEMOD_CHANGE. If anyone has worked on similar requirement please suggest me what are all the e

  • SIMPLE APPLET GETTING RUNTIME ERRORS

    I can figure out why this applet will not work, here is the code: import java.awt.*; import java.awt.event.*; import java.applet.*; import javax.swing.*; public class Convert extends Applet { JTextField tCentigrade = new JTextField(); JLabel lCentigr

  • WSDL Access URL for Metadata Access

    Hi Can someone suggest what is the WSDL Access URL in receiver Communication channel for Direct Point-Point connection scenario. I can't find the details in SOAMANAGER service. Thanks, Murthy

  • Playlist not on device but in iTunes

    I added a Playlist in iTUNES.  I use iCloud but after syncing my devide the playlist is not there.   How can I fix this? Also the Icons for iCLoud that used to be there next to each song is gone.