Cloudscape in weblogic

          Hi,
          I am trying to run a sample application using cloudscape in weblogic. I am
          trying to create some stored procedures in cloudscape. I looked in the manual
          and was unable to find it. I have basicall two questions.
          1. How is cloudscape started in weblogic.
          2. How do you include the classes that you created in the cloudscape database.
          (I did try including in the jars of cloudscape but was not successful)
          thanks,
          babu
          

It looks like the server is unable to locate the cloudscape JDBC driver.
You should make sure that it is in your class path.
Michael Girdley
BEA Systems Inc
"Josef Vavra" <[email protected]> wrote in message
news:[email protected]..
>
Hi, I've just installed WebLogic5.1 on WindowsNT. Without problems. Now Iwant to create a connection to the sample cloudscape DB. I uncommented the
appropriate block in weblogic.properties and then tried in wlconsole 'create
connection pool'. I've got this error:
---------------begin error---------------------------
Property change error for property "CreatePool".
Failed to create pool "demoPool": weblogic.common.ResourceException:weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
DriverManager failed with No suitable driver while trying to create
a Connection for the demoPool pool. This indicates that the URL,
jdbc:cloudscape:demo
is not supported by the Driver
COM.cloudscape.core.JDBCDriver
The following is a list of currently loaded JDBC Drivers:
weblogic.jdbc.pool.Driver
weblogic.jdbc20.jts.Driver
weblogic.jdbc20.pool.Driver
---------------end error-------------------------------------
Can anyone tell me the next step(s) I have to do?
I'm sorry for this stupid question, but I'm totally new to weblogic andlost a bit among the helps.
>
Thanx very much
Josef

Similar Messages

  • Cloudscape documentation

    Hi!,
    "Programming Weblogic JDBC" doc says that wls6.1 comes with Cloudscape eval copy.
    Where can I find documentation about "Using Cloudscape with weblogic server 6.1"
    There seems to be no link provided.
    Thanks in advance
    Latha

    "Latha Ganesan" <[email protected]> wrote in message
    news:3bd582e8$[email protected]..
    "Programming Weblogic JDBC" doc says that wls6.1 comes with Cloudscapeeval copy.
    Where can I find documentation about "Using Cloudscape with weblogicserver 6.1"
    There seems to be no link provided.www.cloudscape.com
    Regards,
    Slava Imeshev

  • Username and password with Access and JDBC application

    Hello all,
    I have written an application which accesses a MS Access database. I have created a dialog which asks the user for a username and password. I then include the username and password to connect to the database. I have created groups and users in the Access database and have given each user different privaleges. However, when I run my application, any user can get any privelage. I am missing something. Thanks in advance.

    // ConnectToDatabase.java
    // Copyleft (c) 2001 RatKing
    // ��������������������������������Java Bean
    // E-mail: [email protected]
    // This can use in JSP or Java Application or Applet
    // AFTER you have setup the ODBC source in Windoz.
    package rat;
    import java.sql.*;
    import java.util.*;
    public class ConnectToDatabase{
    private String driverClass = "sun.jdbc.odbc.JdbcOdbcDriver"; // JDBC-ODBC Bridge Driver
    private String dbURL = "jdbc:odbc:yourdbname"; // the name of your ODBC Source's Database
    private String userName = "yourname"; // user ID
    private String password = "yourpassword"; // user password
    private Connection connection = null; // Connection to the Database
    private Statement statement = null; // Statement object
    public ConnectToDatabase () {
    // ������������������
    public Connection getConnection() throws ClassNotFoundException, SQLException {
    if(connection != null) {
    return connection;
    Class.forName(driverClass);
    connection = DriverManager.getConnection(dbURL, userName, password);
    return connection;
    } // getConnection()
    public void closeConnection() throws SQLException {
    if (connection != null) {
    // Makes all changes made since the previous commit/rollback permanent
    // and releases any database locks currently held by this Connection object.
    if (!connection.getAutoCommit())
    connection.commit();
    closeStatement();
    connection.close();
    connection = null;
    } // closeConnection()
    * If not connected to database...connect to database, create a statement,
    * and, return the Statement.
    protected void createStatement() throws SQLException, Exception {
    if(statement == null) {
    Connection connection = getConnection();
    statement = connection.createStatement();
    * This method executes a statement and returns true or false. Any type
    * of Statement may be executed by this command.
    public boolean execute(String sqlString) throws SQLException, Exception {
    if(statement == null){
    createStatement();
    boolean returnValue = statement.execute(sqlString);
    return returnValue;
    * This method executes the statement and returns a ResultSet from
    * execution of the query. Only a SELECT Statemet is applicable here.
    public ResultSet executeQuery(String sqlString) throws SQLException, Exception {
    if(statement == null){
    createStatement();
    ResultSet rs = statement.executeQuery(sqlString);
    return rs;
    * This method executes update statements and returns a count of
    * the updates. Only a INSERTS, DELETES, and UPDATES are applicable here.
    * In addition, SQL statements that return nothing such as SQL DDL statements
    * can be executed.
    public int executeUpdate(String sqlString) throws SQLException, Exception {
    if(statement == null){
    createStatement();
    int returnValue = statement.executeUpdate(sqlString);
    return returnValue;
    * This method closes the Statement.
    public void closeStatement() throws SQLException {
    if(statement != null){
    statement.close();
    statement = null;
    * If it is not connected to database, connect to database and
    * create a statement and returns the Statement
    * @param scrollType should be ResultSet.TYPE_FORWARD_ONLY
    * or ResultSet.TYPE_SCROLL_INSENSITIVE
    * or ResultSet.TYPE_SCROLL_SENSITIVE
    * @param updateType should be ResultSet.CONCUR_READ_ONLY or
    * ResultSet.CONCUR_UPDATABLE ;
    protected Statement getStatement(int scrollType, int updateType)
    throws SQLException, Exception {
    Connection connection = getConnection();
    // for cloudscape to work with scrollable resultsets, the autocommit
    // should be false.
    connection.setAutoCommit(false);
    Statement statement = connection.createStatement(scrollType,
    updateType);
    return statement;
    * If it is not connected to database, connect to database and
    * create a preparestatement and returns the Statement
    * @param sqlString queryString to make a statement
    * @param scrollType should be ResultSet.TYPE_FORWARD_ONLY
    * or ResultSet.TYPE_SCROLL_INSENSITIVE
    * or ResultSet.TYPE_SCROLL_SENSITIVE
    * @param updateType should be ResultSet.CONCUR_READ_ONLY or
    * ResultSet.CONCUR_UPDATABLE ;
    protected PreparedStatement getStatement(String sqlString,
    int scrollType,
    int updateType) throws SQLException,
    Exception {
    Connection connection = getConnection();
    // for cloudscape to work with scrollable resultsets, the autocommit
    // should be false.
    connection.setAutoCommit(false);
    PreparedStatement preparedStatement =
    connection.prepareStatement(sqlString, scrollType, updateType);
    return preparedStatement;
    * this method executes the statement and resuts the resultSet due to
    * execution of Statement.
    * only SELECT Statemet is applied here.
    public ResultSet executeQueryScrollInsensitiveReadOnly(String sqlString,
    Vector values) throws SQLException, Exception {
    PreparedStatement preparedStatement = getStatement(sqlString,
    ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY);
    for (int i = 1; i <= values.size(); i++) {
    preparedStatement.setObject(i, values.elementAt(i - 1));
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = preparedStatement.executeQuery();
    return rs;
    * this method executes the statement and resuts the resultSet due to
    * execution of Statement. only SELECT Statemet is applied here.
    public ResultSet executeQueryScrollInsensitiveReadOnly(String sqlString)
    throws SQLException, Exception {
    Statement statement = getStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY);
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = statement.executeQuery(sqlString);
    return rs;
    * this method executes the statement and returns the resultSet due to execution
    * of Statement. only SELECT Statemet is applied here.
    public ResultSet executeQueryScrollForwardOnly(String sqlString,
    Vector values) throws SQLException, Exception {
    PreparedStatement preparedStatement = getStatement(sqlString,
    ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY);
    for (int i = 1; i <= values.size(); i++) {
    preparedStatement.setObject(i, values.elementAt(i - 1));
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = preparedStatement.executeQuery();
    return rs;
    * this method executes the statement and returns the resultSet due to
    * execution of Statement. only SELECT Statemet is applied here.
    public ResultSet executeQueryScrollForwardOnly(String sqlString)
    throws SQLException, Exception {
    Statement statement = getStatement(ResultSet.TYPE_FORWARD_ONLY,
    ResultSet.CONCUR_READ_ONLY);
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = statement.executeQuery(sqlString);
    return rs;
    * Method executeQueryScrollSensitiveReadOnly
    * @param sqlString String
    * @param values Vector
    * @return ResultSet returns ResultSet due to statement execution
    * @throws Exception
    * @throws SQLException
    * @see
    public ResultSet executeQueryScrollSensitiveReadOnly(String sqlString,
    Vector values) throws SQLException, Exception {
    PreparedStatement preparedStatement = getStatement(sqlString,
    ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
    for (int i = 1; i <= values.size(); i++) {
    preparedStatement.setObject(i, values.elementAt(i - 1));
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = preparedStatement.executeQuery();
    return rs;
    * Method executeQueryScrollSensitiveReadOnly
    * @param sqlString
    * @return
    * @throws Exception
    * @throws SQLException
    * @see
    public ResultSet executeQueryScrollSensitiveReadOnly(String sqlString) throws SQLException, Exception {
    Statement statement = getStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
    ResultSet.CONCUR_READ_ONLY);
    // Execute a SQL statement that returns a single ResultSet.
    ResultSet rs = statement.executeQuery(sqlString);
    return rs;
    //////////////Other things maybe useful ///////////////////
    # Refer to Appendix A for more info on configuring the JDBC
    # driver via setting of the DRIVER_CLASS and DATABASE_URL properties
    #JDBC Driver Class
    # for ODBC Driver:
    #DRIVER_CLASS=sun.jdbc.odbc.JdbcOdbcDriver
    # for Oracle Driver
    #DRIVER_CLASS=jdbc.oracle.driver.OracleDriver
    # for CloudScape Driver equipped with J2EE reference implementation
    #DRIVER_CLASS=RmiJdbc.RJDriver
    # for CloudScape Driver equipped with BEA Weblogic Server
    DRIVER_CLASS=COM.cloudscape.core.JDBCDriver
    #Database URL
    # for ODBC URL
    #DATABASE_URL=jdbc:odbc:tShirts
    # for Oracle URL
    #DATABASE_URL=jdbc:oracle:thin:@localhost:1521:ORCL
    # for URL with CloudScape equipped with J2EE reference implementation
    #DATABASE_URL=jdbc:rmi:jdbc:cloudscape:beeshirtsdb
    # for URL with CloudScape equipped with BEA Weblogic Server
    DATABASE_URL=jdbc:cloudscape:D:\\weblogic\\eval\\cloudscape\\beeshirts
    #UserName to connect to database
    UserName=TSHIRTS
    #Password to connect to database
    Password=TSHIRTS
    #otherParameters
    SUB_PROPERTIES=
    #SQL Query
    SQL_QUERY_STATEMENT = SELECT * FROM TSHIRTS.CUSTOMER
    #SQL Update , if you run this program please change the id 129 to different value each time
    SQL_UPDATE_STATEMENT = INSERT INTO TSHIRTS.CUSTOMER VALUES ('129','Sam','Cheng','S','123 Sam St.', 'C3','Baltimore','MD','20222','4104444444' ,'[email protected]')
    #Join STATEMENT
    SQL_QUERY_STATEMENT_JOIN = SELECT TSHIRTS.CUSTOMER.*, TSHIRTS.ORDERS.* FROM TSHIRTS.CUSTOMER, TSHIRTS.ORDERS WHERE CUSTOMER.CUSTOMER_ID = ORDERS.CUSTOMER_ID_FK
    #OUTER JOIN for ORACLE
    #SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT CUSTOMER.* FROM TSHIRTS.CUSTOMER,STATE WHERE CUSTOMER.STATE(+) = STATE.CODE(+)
    #OUTER JOIN for MSACCESS
    #SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT C.* , S.* FROM CUSTOMER C OUTER JOIN STATE S on C.STATE = S.CODE
    #OUTER JOIN for MSACCESS and Cloudscape
    SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT C.* , S.* FROM TSHIRTS.CUSTOMER C LEFT OUTER JOIN TSHIRTS.STATE S on C.STATE = S.CODE
    #SQL Statement with Like for MSACCESS
    #SQL_QUERY_STATEMENT_WITH_LIKE = SELECT CUSTOMER.* FROM CUSTOMER WHERE CUSTOMER.FIRST_NAME LIKE \'*R*\'
    #SQL Statement with Like for ORACLE and Cloudscape
    SQL_QUERY_STATEMENT_WITH_LIKE = SELECT * FROM TSHIRTS.CUSTOMER WHERE FIRST_NAME LIKE '%R%'
    #Prepared QUERY Statement
    PREPARED_SQL_QUERY_STATEMENT = SELECT * FROM TSHIRTS.CUSTOMER WHERE FIRST_NAME = ?
    PREPARED_SQL_QUERY_STATEMENT_VALUES = Roy
    #Prepared Insert
    PREPARED_SQL_INSERT_STATEMENT = INSERT INTO TSHIRTS.CUSTOMER VALUES(?,?,?,?,?,?,?,?,?,?,?)
    PREPARED_SQL_INSERT_STATEMENT_VALUES =130,John,Hiller,Miller,125 S St.,C6,Baltimore,MD,20100,4104444444,[email protected]
    #Prepared Update
    PREPARED_SQL_UPDATE_STATEMENT = UPDATE TSHIRTS.STATE SET STATE_NAME = 'California' WHERE CODE = ?
    PREPARED_SQL_UPDATE_STATEMENT_VALUES =CA
    #Data base schema name
    SCHEMA_NAME =TSHIRTS

  • LotusXSL and WLS 5.1...

    Is there anyone using the IBMs LotusXSL 1.0.1 package (Xalan.jar and
              Xeres.jar) with WLS 5.1 SP3?
              Because I can't make it work...
              Here's what I want to do my JSP:
              - Take XML stream
              - Take XSL stream (file)
              - generate an HTML stream (page) from the 2 streams with the help of an XSL
              processor
              the LotusXSL processor works fine at the command line but I use it in my JSP
              I this error when I put the code in the JSP:
              Compilation of 'D:\weblogic\myserver\classfiles\jsp_servlet\merchant1.java'
              failed:
              D:\weblogic\myserver\classfiles\jsp_servlet\merchant1.java:0: Class
              org.xml.sax.ext.LexicalHandler not found in interface
              org.apache.xalan.xslt.XSLTProcessor.
              (No more information available, probably caused by another error)
              Fri Jun 23 11:10:15 CEST 2000
              And I get this error when I wrap the code in JavaBean:
              Error 500--Internal Server Error
              From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              10.5.1 500 Internal Server Error
              The server encountered an unexpected condition which prevented it from
              fulfilling the request.
              Thanks for helping!
              David Pare
              Accor Corporate Services
              

    It seems odd to me, as well, that the jar doesn't work, but the expanded
              classes do.
              Anyway, I'm using SP3 w/ Xalan 1.0.3 and Xerces 1.0.1. Here are my
              settings.
              classpath
              e:\weblogic\lib\weblogic510sp3boot.jar;.\classes\boot;.\eval\cloudscape\lib\
              cloudscape.jar
              weblogic.class.path=.\lib\weblogic510sp3.jar;.\license;.\classes;.\lib\weblo
              gicaux.jar;.\myserver\serverclasses;e:\xml\xerces.jar;e:\xml\xalan.jar;e:\jd
              k1.2.2\lib\tools.jar;\weblogic\license;\weblogic\classes;\weblogic\lib\weblo
              gicaux.jar;\weblogic\myserver\clientclasses;\weblogic\myserver\serverclasses
              ;E:\jdk1.2.2\jre\lib\ext\jndi.jar;E:\jdk1.2.2\jre\lib\ext\ldap.jar;E:\jdk1.2
              .2\jre\lib\ext
              You'll notice the xml jars come after the weblogic classes. However, I
              might not be using classes that conflict w/ WL.
              Jim Clark
              Idea Integration
              http://www.idea.com
              "David Pare" <[email protected]> wrote in message
              news:[email protected]...
              > I tried it and it doesn't work for me :(
              >
              > The only thing that works for me is to expand the JAR files onto my
              > CLASSPATH and it works fine... other than that I don't know... Worse... I
              > don't know why it makes a difference wheater it's in a JAR file or not?
              >
              > Thanks anyway:)
              >
              > Dave
              >
              >
              > "Brian J. Levine" <[email protected]> wrote in message
              > news:[email protected]...
              > > Hi David,
              > >
              > > How are you loading xalan.jar and xerces.jar? Are these in your
              > WEB-INF/lib
              > > directory? If so, you may be running into a conflict with the XML
              parser
              > > classes included with WLS in weblogicaux.jar. The only solution I've
              > found
              > > so far is to prepend xerces.jar to the WLS classpath making sure that is
              > > comes before weblogicaux.jar in the classpath. I do this in my
              > > startweblogic.cmd script by setting PRE_CLASSPATH=[somedir]/xerces.jar.
              > > Xalan.jar doesn't conflict with anything so it can remain in your
              > > WEB-INF\lib directory.
              > >
              > > I've reported this bug to Weblogic but no resolution so far.
              > >
              > > Hope this helps.
              > >
              > > -brian
              > >
              > > "David Pare" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > Is there anyone using the IBMs LotusXSL 1.0.1 package (Xalan.jar and
              > > > Xeres.jar) with WLS 5.1 SP3?
              > > >
              > > > Because I can't make it work...
              > > >
              > > > Here's what I want to do my JSP:
              > > >
              > > > - Take XML stream
              > > > - Take XSL stream (file)
              > > > - generate an HTML stream (page) from the 2 streams with the help of
              an
              > > XSL
              > > > processor
              > > >
              > > > the LotusXSL processor works fine at the command line but I use it in
              my
              > > JSP
              > > > I this error when I put the code in the JSP:
              > > >
              > > > Compilation of
              > > 'D:\weblogic\myserver\classfiles\jsp_servlet\merchant1.java'
              > > > failed:
              > >
              >
              > --------------------------------------------------------------------------
              > > --
              > > > ----
              > > > D:\weblogic\myserver\classfiles\jsp_servlet\merchant1.java:0: Class
              > > > org.xml.sax.ext.LexicalHandler not found in interface
              > > > org.apache.xalan.xslt.XSLTProcessor.
              > > > (No more information available, probably caused by another error)
              > >
              >
              > --------------------------------------------------------------------------
              > > --
              > > > ----
              > > > Fri Jun 23 11:10:15 CEST 2000
              > > >
              > > >
              > > > And I get this error when I wrap the code in JavaBean:
              > > > -----------------------
              > > > Error 500--Internal Server Error
              > > > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              > > > 10.5.1 500 Internal Server Error
              > > > The server encountered an unexpected condition which prevented it from
              > > > fulfilling the request.
              > > >
              > > > Thanks for helping!
              > > >
              > > > David Pare
              > > > Accor Corporate Services
              > > >
              > > >
              > >
              > >
              >
              >
              

  • Deploython provided on Sun's Site Problem

    Hi:
    I was trying to run the deployathon for CloudScape and Weblogic
    5.1 using Jdk1.2.2.
    the deployathon is available at
    http://developer.java.sun.com/developer/technicalArticles/J2EE/deployathon2/BEAreadme.html
    I keep getting this error. Can you let me know where I am going
    wrong. I followed all the instructions provided.
    I would really appreciate any help regarding this.
    Thanks
    Sunitha
    Thu Mar 15 16:57:27 PST 2001:<I> <System Props> weblogic.system.home
    = petStore
    Thu Mar 15 16:57:27 PST 2001:<I> <System Props> weblogic.system.name
    = petStoreServer
    Thu Mar 15 16:57:27 PST 2001:<I> <WebLogicServer> Loaded License
    : C:/weblogic/license/WebLogicLicense.xml
    Thu Mar 15 16:57:27 PST 2001:<I> <WebLogicServer> Server loading
    from weblogic.class.path. EJB redeployment enabled.
    Unable to initialize server: com.bea.estore.rdbmsrealm.RDBMSException:
    realm initialization failed, action 'DriverManager.getConnection',
    - with nested excepti
    on:
    [SQL Exception: Failed to start database 'petStoreDB', see the
    next exception fo
    r details.]
    fatal initialization exception
    com.bea.estore.rdbmsrealm.RDBMSException: realm initialization
    failed, action 'D
    riverManager.getConnection', - with nested exception:
    [SQL Exception: Failed to start database 'petStoreDB', see the
    next exception fo
    r details.]
    at com.bea.estore.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:169
    at com.bea.estore.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDel
    egate.java:912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    at com.bea.estore.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    at com.bea.estore.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:51
    5)
    at weblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:16
    98)
    at weblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java:757)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1747)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1084)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)

    It doesn't appear that your cloudscape instance is available. Remember,
    only one process can access a Cloudscape install at a time.
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    "Sunitha" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi:
    I was trying to run the deployathon for CloudScape and Weblogic
    5.1 using Jdk1.2.2.
    the deployathon is available at
    http://developer.java.sun.com/developer/technicalArticles/J2EE/deployathon2/
    BEAreadme.html
    >
    I keep getting this error. Can you let me know where I am going
    wrong. I followed all the instructions provided.
    I would really appreciate any help regarding this.
    Thanks
    Sunitha
    Thu Mar 15 16:57:27 PST 2001:<I> <System Props> weblogic.system.home
    = petStore
    Thu Mar 15 16:57:27 PST 2001:<I> <System Props> weblogic.system.name
    = petStoreServer
    Thu Mar 15 16:57:27 PST 2001:<I> <WebLogicServer> Loaded License
    : C:/weblogic/license/WebLogicLicense.xml
    Thu Mar 15 16:57:27 PST 2001:<I> <WebLogicServer> Server loading
    from weblogic.class.path. EJB redeployment enabled.
    Unable to initialize server: com.bea.estore.rdbmsrealm.RDBMSException:
    realm initialization failed, action 'DriverManager.getConnection',
    - with nested excepti
    on:
    [SQL Exception: Failed to start database 'petStoreDB', see the
    next exception fo
    r details.]
    fatal initialization exception
    com.bea.estore.rdbmsrealm.RDBMSException: realm initialization
    failed, action 'D
    riverManager.getConnection', - with nested exception:
    [SQL Exception: Failed to start database 'petStoreDB', see the
    next exception fo
    r details.]
    atcom.bea.estore.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:169
    atcom.bea.estore.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDel
    egate.java:912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    atcom.bea.estore.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    >
    atcom.bea.estore.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:51
    5)
    atweblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:16
    98)
    atweblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java:757)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1747)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1084)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)

  • WLEC does not work

    Hello,
    after trying unsuccessfully for several hours to get WLEC to work on
    WLS 5.1, I think I might ask this group.
    It simply does not work.
    I have installed the latest service pack (6) and I'm now trying to
    install the WLEC version included therein. I've merged the files from
    wlec_classes.jar (some classes in the package
    com.beasys.CORBA.pool.weblogic) into the $WLS_HOME/classes tree,
    copied the files wleorb.jar and wlepool.jar to $WLS_HOME/lib and added
    them to the appropriate class paths as described in the
    README_wlec.txt file that comes with WLEC. WLS is started as follows:
    /opt/JAVA/JDK/1.2.2/bin/java -ms64m -mx64m -classpath ./lib/weblogic510sp6boot.jar:./lib/wleorb.jar:./classes/boot:./eval/cloudscape/lib/cloudscape.jar -Dweblogic.class.path=./lib/weblogic510sp6.jar:./lib/wlepool.jar:./license:./classes:./lib/weblogicaux.jar:./myserver/serverclasses -Dweblogic.home=. -Djava.security.manager -Djava.security.policy=$WLSHOME/weblogic.policy -Dweblogic.system.name=myserver -Djava.naming.ldap.version=2 weblogic.Server
    (README_wlec.txt does not document the order in which the jar files
    should appear in the class paths..?)
    Furthermore, I've defined an IIOP connection pool in
    weblogic.properties like this:
    weblogic.CORBA.connectionPool.myIIOPConnectionPool=\
    appaddrlist=//wlehost:3800,\
    failoverlist=//wlehost:3800,\
    minpoolsize=4,\
    maxpoolsize=7,\
    domainname=test
    A WLE 5.1 instance is waiting for IIOP connections at wlehost:3800,
    providing the WLE domain "test".
    WLS starts up and functions flawlessly, but the IIOP connection pool
    doesn't show up in the WebLogic Console (the "IIOP Connection Pool
    Manager" branch is missing completely). An attempt to connect to the
    pool with the following code:
    com.beasys.Tobj_Bootstrap tBootstrap
    = com.beasys.BootstrapFactory.getClientContext("myIIOPConnectionPool")
    results in a NullPointerException in getClientContext.
    I can connect to the running WLE server directly, bypassing the pool,
    like this:
    String[] args = new String[0];
    org.omg.CORBA.ORB tOrb = org.omg.CORBA.ORB.init(args, null);
    com.beasys.Tobj_Bootstrap tBootstrap
    = new com.beasys.Tobj_Bootstrap(tOrb,"//wlehost:3800");
    This works, which proves that WLE is not the problem, right?
    The java version is:
    $ /opt/JAVA/JDK/1.2.2/bin/java -version
    java version "1.2.2"
    Classic VM (build JDK-1.2.2_006, green threads, sunwjit)
    $
    (I've tried 1.3, too)
    running on:
    $ uname -a
    SunOS bird 5.8 Generic_108528-01 sun4u sparc
    $
    WLE runs on:
    wlehost:~$ uname -a
    AIX wlehost 3 4 002013145700
    wlehost:~$
    What might be the problem here?
    Thanks,
    Olaf
    Olaf Klischat | Fraunhofer ISST
    Oberfeldstrasse 132 | Mollstrasse 1
    12683 Berlin, Germany | 10178 Berlin, Germany
    phone: +49 30 54986231 | mail: [email protected]

    Craig Perez <[email protected]> writes:
    WLS starts up and functions flawlessly, but the IIOP connection pool
    doesn't show up in the WebLogic Console (the "IIOP Connection Pool
    Manager" branch is missing completely). An attempt to connect to the
    pool with the following code:
    com.beasys.Tobj_Bootstrap tBootstrap
    = com.beasys.BootstrapFactory.getClientContext("myIIOPConnectionPool")
    results in a NullPointerException in getClientContext.Have you examined your WLS startup log very carefully to look
    for any connection pool errors?Yes I have. I've searched (case-insensitively) for "iiop" and the
    hostname of the host running WLE ("wlehost"), and there was always
    only one log entry per WLS session:
    Mon Dec 04 16:36:50 CET 2000:<I> <Config> Property name: 'weblogic.CORBA.connectionPool', current value: '[weblogic.CORBA.connectionPool.myIIOPConnectionPool=appaddrlist=//wlehost:3800,failoverlist=//wlehost:3800,minpoolsize=4,maxpoolsize=7,domainname=test ]'
    This seems to be a generic notification that the property was read and
    that the property name
    "weblogic.CORBA.connectionPool.myIIOPConnectionPool" was recognized
    (otherwise there would have been an "undeclared property" error
    message, right?).
    How would a log message look which notifies the user that an IIOP
    conection pool has been set up successfully?
    When I delete or rename the file wleorb.jar or remove it from the
    classpath, I get the following exception when WLS boots:
    Tue Dec 05 15:42:11 CET 2000:<E> <WebLogicServer> Failed startup on com.beasys.CORBA.pool.weblogic.PoolStartUp
    java.lang.NoClassDefFoundError: com/beasys/CORBA/pool/ConnectionPoolManagerImpl
    at java.lang.Class.getMethod0(Native Method)
    at java.lang.Class.getMethod(Class.java:888)
    at weblogic.t3.srvr.T3Srvr.callPoolStartupMehtod(T3Srvr.java:1444)
    at weblogic.t3.srvr.T3Srvr.startIIOPConnectionPools(T3Srvr.java:1422)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1262)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    (note the spelling mistake ("callPoolStartupMehtod"). Could this be
    part of the problem?)
    When I remove the connection pool entry from weblogic.properties, the
    exception disappears.
    I examined the file $WLS_HOME/myserver/weblogic.log as well as the
    standard output and standard error of the WLS process. Are there any
    other places to look at?
    I'm still suspecting the order in which the JAR files appear in my
    system class path and weblogic class path. As pointed out in my
    previous posting, the order is as follows:
    system class path:
    ./lib/weblogic510sp6boot.jar:./lib/wleorb.jar:./classes/boot:./eval/cloudscape/lib/cloudscape.jar
    weblogic.class.path:
    ./lib/weblogic510sp6.jar:./lib/wlepool.jar:./license:./classes:./lib/weblogicaux.jar:./myserver/serverclasses
    Is anything wrong with that? I could try out all permutations, but
    that would take a while....
    Could anybody post the class paths of a WLS configuration with a
    working WLEC?
    Thank you,
    Olaf
    Olaf Klischat | Fraunhofer ISST
    Oberfeldstrasse 132 | Mollstrasse 1
    12683 Berlin, Germany | 10178 Berlin, Germany
    phone: +49 30 54986231 | mail: [email protected]

  • Problem with clloudscape rmi jdbc driver

    I am using Cloudscape rmi jdbc driver, where Cloudscape runs as
    a separate server. I am using WL6.1 running on Red Hat Linux
    7.1. I defined a Cloudscape connection pool and data source. I
    have to start Cloudscape before WebLogic or I get the following
    exception:
    <Feb 18, 2002 11:39:42 PM EST> <Error> <JDBC> <Cannot startup
    connection pool "EStoreConnectionPool"
    weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: Connection refused to host: localhost;
    nested exception is:
    java.net.ConnectException: Connection refused
    at RmiJdbc.RJDriver.connect(RJDriver.java:149)
    at java.sql.DriverManager.getConnection
    (DriverManager.java:512)
    etc.
    No surprises here: However if I start Cloudscape first and
    WebLogic second, I get the following message in Weblogic:
    Starting WebLogic Server ....
    <Feb 19, 2002 12:58:21 AM EST> <Notice> <Management>
    <Loading configuration file ./config/mydomain/config.xml ...>
    <Feb 19, 2002 12:58:43 AM EST> <Notice> <WebLogicServer>
    <Starting WebLogic Admin Server "myserver" for domain "mydomain">
    <Feb 19, 2002 12:59:00 AM EST> <Notice> <Management>
    <Starting discovery of Managed Server... This feature is on by
    default, you may turn this off by passing
    -Dweblogic.management.discover=false>
    This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
    It is a violation of the license agreement to deploy this version
    in a production application.
    For information about licensing Cloudscape for application
    deployment, contact [email protected] or call
    888/595-2821 ext. 7664.
    Additional licensing information can be found at
    http://www.cloudscape.com/licensing.
    <Feb 19, 2002 12:59:31 AM EST> <Notice> <Management>
    <Application Poller started for development server.>
    <Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
    <ListenThread listening on port 7001>
    <Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
    <SSLListenThread listening on port 7002>
    <Feb 19, 2002 12:59:32 AM EST> <Notice> <WebLogicServer>
    <Started WebLogic Admin Server "myserver" for domain "mydomain"
    running in Development Mode>
    The console running cloudscape then contains this message:
    This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
    It is a violation of the license agreement to deploy this version
    in a production application.
    For information about licensing Cloudscape for application
    deployment, contact [email protected] or call
    888/595-2821 ext. 7664.
    Additional licensing information can be found at
    http://www.cloudscape.com/licensing.
    Tue Feb 19 00:56:43 EST 2002: [RmiJdbc]
    COM.cloudscape.core.JDBCDriver registered in DriverManager
    Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] Binding RmiJdbcServer...
    Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] No installation of RMI
    Security Manager...
    Tue Feb 19 00:56:46 EST 2002: [RmiJdbc] RmiJdbcServer bound in
    rmi registry
    WARNING: Cloudscape (instance
    c013800d-00ec-1cf6-94ca-007f00000100) is
    attempting to boot the database
    /app/cloudscape_3.6/database/acme/estore even
    though cloudscape (instance c013800d-00ec-1cca-ed1d-007f00000100)
    may still be active. Only one instance of cloudscape should boot
    a database at a time. Severe and non-recoverable corruption can
    result and may have already occurred.
    Well, it looks like I'm damned if I do and damned if I don't.
    Any suggestions?

    Actually, it happened because Cloudscape was not properly shut down. Thanks for
    responding. I was having some troble with the stopCS script, but its OK now.
    "Laurent Goldsztejn" <[email protected]> wrote:
    >
    Hi Douglass,
    The evaluation version of Cloudscape is limited to one concurrent user
    per session,
    so only one instance of cloudscape can be running at a time. The problem
    reported
    here can occur if you try to run more than once instance of any product
    that
    uses Cloudscape -- including WLS or Cloudview. This evaluation version
    of Cloudscape
    is intended for test purposes only.
    This error can also occur on Solaris if you stop the server using ctrl-C
    or ctrl-D,
    which causes a database lock to remain in place after the server has
    stopped.
    You can get rid of it by deleting $BEA_HOME/wlserver6.1/samples/eval/cloudscape/data/demo/db.lck
    The safest way to stop the server is to use the Admin console or the
    SHUTDOWN
    command from the command line.
    Laurent Goldsztejn
    Developer Relations Engineer
    BEA Support

  • How to create a database using Cloudscape provided by Weblogic

    Hi,
    I am new to EJB and i am trying to run the sample Entity bean given in the book "Enterprise
    Java Beans" by Richard Monson-Haefel.In the 4th chapter he has given a example Cabin
    Entity bean.
    My problem is i am not able to execute Cloudscape to create a table called CABIN.
    I first set the environment by giving command \weblogic\setEnv (i have done the CLASSPATH
    setting for cloudscape in this).When i give the command >java COM.cloudscape.tools.cview
    , I get a error "Exception in thread Main".
    Can anyone help me on this ?
    Thanx in advance.
    Sanjay.

    Labview configuration files are very easy to use and can hold any type of information you wish.  There are functions in the File palette ready to use for configuration files.  A configuration file is similar to a registry entry.  You can have sections and keys.  So you can create a section called "Data1" and keys called "Name", "Age", etc.  Create the same for a new section called "Data2", and so on.  The functions are useful for writing the config file and reading from the file.  To read a certain piece of data, just supply the section name and the key name.  So you could ask for section "Data20", key "Name", and you would get the 20th name in the database (config file).  This way you don't have to write code to search the database for certain items, the functions do it for you and they are already written.  Look into config files.  They are very easy to use, very useful, and very underused even by the most experienced LV programmer.
    - tbob
    Inventor of the WORM Global

  • Cloudscape-Weblogic XA mismatch

    Hello,
    First, yes I know Cloudscape may not be the best database for production and
    XA, but anyway, I have to use it, and it supports XA.
    Now my question :
    I'm using WLS 6.1 SP1.
    I defined a Cloudscape XA pool which seems to initialize well (the server
    logs shows initial connections creations for the XA pool successfully). For
    this pool, the driver classname I use is COM.cloudscape.core.XADataSource.
    Over this pool I defined a Tx Data Source which some JNDI name, let's say
    "MyXADataSource".
    This works well and I can get and use connections from this "MyXADataSource"
    datasource while I use it as a javax.sql.DataSource (from a BMP for
    example).
    However this DataSource is not XA. I mean that it does not implement
    javax.sql.XADataSource (the concrete class is actually
    weblogic.jdbc.common.internal.RmiDataSource). This is a problem for example
    when a connector (let's say the BlackBoxXA sample connector) tries to use
    this datasource as an XA datasource, leading to a ClassCastException.
    So why the concrete weblogic.jdbc.common.internal.RmiDataSource class is not
    an XA class ? Did I configure something wrong or forget something ?
    Thanks for your help.
    Jérôme.

    Hello Slava,
    Thank for your reply.
    However as I said, this remains a problem when the BlackBoxXA connector
    tries to use this datasource as an XA datasource, because its implementation
    does an explicit cast to XADataSource (leading to a ClassCastException).
    Jérôme.
    "Slava Imeshev" <[email protected]> a écrit dans le message de news:
    3c412a2c$[email protected]..
    Hi,
    When you lookup for a datasource, you get an object
    implementing DataSource interface, not XADataSource.
    You don't have to cast it to XADataSource. If you need
    XA behavior, all you need is setting up a TXDataSource
    with a driver implementing XADataSource. weblogic will
    take care about the rest.
    Regards,
    Slava Imeshev
    "Jérôme Beau" <[email protected]> wrote in message
    news:3c3ec603$[email protected]..
    Hello,
    First, yes I know Cloudscape may not be the best database for productionand
    XA, but anyway, I have to use it, and it supports XA.
    Now my question :
    I'm using WLS 6.1 SP1.
    I defined a Cloudscape XA pool which seems to initialize well (the
    server
    logs shows initial connections creations for the XA pool successfully).For
    this pool, the driver classname I use is
    COM.cloudscape.core.XADataSource.
    >>
    Over this pool I defined a Tx Data Source which some JNDI name, let'ssay
    "MyXADataSource".
    This works well and I can get and use connections from this"MyXADataSource"
    datasource while I use it as a javax.sql.DataSource (from a BMP for
    example).
    However this DataSource is not XA. I mean that it does not implement
    javax.sql.XADataSource (the concrete class is actually
    weblogic.jdbc.common.internal.RmiDataSource). This is a problem forexample
    when a connector (let's say the BlackBoxXA sample connector) tries to
    use
    this datasource as an XA datasource, leading to a ClassCastException.
    So why the concrete weblogic.jdbc.common.internal.RmiDataSource class isnot
    an XA class ? Did I configure something wrong or forget something ?
    Thanks for your help.
    Jérôme.

  • Weblogic 6.1 hangs (no response) with cloudscape

    Hi,
    I am running WLS 6.1 with JDK 1.3.1 on cloudscape db - WIN2K.
    After every 20-30 minutes I get this problem of server getting stuck up(no
    response) and get blank pages.
    I have heap size of ms=mx=64mb, tried to increase that, but with no
    improvement.
    I have ThreadCount=15, VM used is hotspot(client).
    Is this a thread deadlock problem ?
    Any help appreciated,
    Baiju.
    Thread dump follows ....
    Full thread dump:
    "SSLListenThread" prio=5 tid=0x9b3878 nid=0x558 runnable
    [0xadff000..0xadffdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :126)
    at
    weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:117)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "ListenThread" prio=5 tid=0x9b3750 nid=0x538 runnable [0xadbf000..0xadbfdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Application Manager Thread" prio=5 tid=0x91764f8 nid=0x520 waiting on
    monitor [0xad3f000..0xad3fdbc]
    at java.lang.Thread.sleep(Native Method)
    at
    weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
    pplicationManager.java:1016)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=5
    tid=0x8c8e9c8 nid=0x4b8 waiting on monitor [0xa4ff000..0xa4ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c8e818 nid=0x4bc waiting on monitor [0xa4bf000..0xa4bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c64d80 nid=0x564 waiting on monitor [0xa47f000..0xa47fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c66818 nid=0x568 waiting on monitor [0xa43f000..0xa43fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8b63838 nid=0x56c waiting on monitor [0xa3ff000..0xa3ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "rawStoreDaemon" daemon prio=5 tid=0x8c83d20 nid=0x570 waiting on monitor
    [0xa3bf000..0xa3bfdbc]
    at java.lang.Object.wait(Native Method)
    at c8e._x.a.c(Unknown Source)
    at c8e._x.a.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:484)
    "antiGC" daemon prio=2 tid=0x8c5f298 nid=0x7e8 waiting on monitor
    [0xa37f000..0xa37fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at c8e.ad.a.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fd7b0
    nid=0x588 waiting on monitor [0xa33f000..0xa33fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fcbf8
    nid=0x58c waiting on monitor [0xa2ff000..0xa2ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fc040
    nid=0x590 waiting on monitor [0xa2bf000..0xa2bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fb488
    nid=0x594 waiting on monitor [0xa27f000..0xa27fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fa900
    nid=0x598 waiting on monitor [0xa23f000..0xa23fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8f9df0
    nid=0x780 waiting on monitor [0xa1ff000..0xa1ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x908be0
    nid=0x59c waiting on monitor [0xa1bf000..0xa1bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x9080a0
    nid=0x5a0 waiting on monitor [0xa17f000..0xa17fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x907590
    nid=0x5a4 waiting on monitor [0xa13f000..0xa13fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8e60d58
    nid=0x5a8 waiting on monitor [0xa0ff000..0xa0ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8ad3e48
    nid=0x5ac waiting on monitor [0xa0bf000..0xa0bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9fbd8
    nid=0x5b0 waiting on monitor [0xa07f000..0xa07fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9fab0
    nid=0x5f0 waiting on monitor [0xa03f000..0xa03fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9f6b8
    nid=0x5f8 waiting on monitor [0x9fff000..0x9fffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x901008
    nid=0x5fc waiting on monitor [0x9fbf000..0x9fbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8c316d0 nid=0x600 waiting on monitor [0x9f7f000..0x9f7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8c31928 nid=0x604 waiting on monitor [0x9f3f000..0x9f3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8b9cdd0 nid=0x608 waiting on monitor [0x9eff000..0x9effdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8c24008 nid=0x60c waiting on monitor [0x9ebf000..0x9ebfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8bfa2a0 nid=0x610 waiting on monitor [0x9e7f000..0x9e7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8bf9818 nid=0x618 waiting on monitor [0x9e3f000..0x9e3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8be9180 nid=0x648 waiting on monitor [0x9dff000..0x9dffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8be8670 nid=0x630 waiting on monitor [0x9dbf000..0x9dbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8c15dd8 nid=0x62c waiting on monitor [0x9d7f000..0x9d7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8f04d78 nid=0x560 waiting on monitor [0x9d3f000..0x9d3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8ee8e08 nid=0x764 waiting on monitor [0x9cff000..0x9cffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8efbba0 nid=0x75c waiting on monitor [0x9cbf000..0x9cbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8efb948 nid=0x7c8 waiting on monitor [0x9c7f000..0x9c7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon prio=5
    tid=0x8bcf588 nid=0x80c waiting on monitor [0x9c3f000..0x9c3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon prio=5
    tid=0x8bcf400 nid=0x55c waiting on monitor [0x9bff000..0x9bffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x8c01568 nid=0x6a0 waiting on
    monitor [0x9bbf000..0x9bbfdbc]
    at java.lang.Object.wait(Native Method)
    at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :138)
    at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=5 tid=0x8bc1288 nid=0x6c8 waiting on
    monitor [0x9b7f000..0x9b7fdbc]
    at java.lang.Object.wait(Native Method)
    at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :138)
    at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x8bbbf40 nid=0x704 waiting on
    monitor [0x9b3f000..0x9b3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:5
    7)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x8b5bac0
    nid=0x54c runnable [0x9aff000..0x9affdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at
    weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:501)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x8b5a350
    nid=0x688 runnable [0x9a7f000..0x9a7fdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at
    weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:501)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x8b59818
    nid=0x790 waiting on monitor [0x9a3f000..0x9a3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x8bf8c50
    nid=0x4a0 waiting on monitor [0x99ff000..0x99ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x8bf8110
    nid=0x5d0 waiting on monitor [0x99bf000..0x99bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x8bf75d0
    nid=0x74c waiting on monitor [0x997f000..0x997fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x8bf6a90
    nid=0x7e0 waiting on monitor [0x993f000..0x993fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x8bf6008
    nid=0x7f8 waiting on monitor [0x98ff000..0x98ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x8bce3f0
    nid=0x818 waiting on monitor [0x98bf000..0x98bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x8bcd8e0
    nid=0x6e4 waiting on monitor [0x987f000..0x987fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x8b579e0
    nid=0x814 waiting on monitor [0x983f000..0x983fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=5 tid=0x8bc1e48
    nid=0x7ec waiting on monitor [0x97ff000..0x97ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x8bc1d20
    nid=0x7f4 waiting on monitor [0x97bf000..0x97bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=5 tid=0x8b93d28
    nid=0x770 waiting on monitor [0x977f000..0x977fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=10 tid=0x8adce30 nid=0x808 waiting on monitor
    [0x973f000..0x973fdbc]
    at java.lang.Thread.sleep(Native Method)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1543)
    at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=10 tid=0x911c48 nid=0x620 waiting on monitor
    [0..0]
    "Finalizer" daemon prio=9 tid=0x90dd10 nid=0x614 waiting on monitor
    [0x8d5f000..0x8d5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=10 tid=0x8aa0bc0 nid=0x7f0 waiting on
    monitor [0x8d1f000..0x8d1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=5 tid=0x234db0 nid=0x800 waiting on monitor [0x6f000..0x6fc34]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:591)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=5 tid=0x966a90 nid=0x6b4 runnable
    "VM Periodic Task Thread" prio=10 tid=0x910980 nid=0x7d0 waiting on monitor
    "Suspend Checker Thread" prio=10 tid=0x9112d0 nid=0x6fc runnable

    Did you guys make any progress here? We have a similar problem, however, we don't
    get it every 20-30 minutes, it's intermittant.
    Jim Zhou wrote:
    Try to make following changes to your cloudscape connection pool in config.xml:
    <JDBCConnectionPool CapacityIncrement="1"
    DriverName="COM.cloudscape.core.XaDataSource"
    .........other options.......
    PreparedStatementCacheSize="0"/>
    to see if it make any difference.
    Jim Zhou.
    "Baiju Gajjar" <[email protected]> wrote:
    Hi,
    I am running WLS 6.1 with JDK 1.3.1 on cloudscape db - WIN2K.
    After every 20-30 minutes I get this problem of server getting stuck
    up(no
    response) and get blank pages.
    I have heap size of ms=mx=64mb, tried to increase that, but with no
    improvement.
    I have ThreadCount=15, VM used is hotspot(client).
    Is this a thread deadlock problem ?
    Any help appreciated,
    Baiju.
    Thread dump follows ....
    Full thread dump:
    "SSLListenThread" prio=5 tid=0x9b3878 nid=0x558 runnable
    [0xadff000..0xadffdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :126)
    at
    weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:117)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "ListenThread" prio=5 tid=0x9b3750 nid=0x538 runnable [0xadbf000..0xadbfdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Application Manager Thread" prio=5 tid=0x91764f8 nid=0x520 waiting on
    monitor [0xad3f000..0xad3fdbc]
    at java.lang.Thread.sleep(Native Method)
    at
    weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
    pplicationManager.java:1016)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=5
    tid=0x8c8e9c8 nid=0x4b8 waiting on monitor [0xa4ff000..0xa4ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c8e818 nid=0x4bc waiting on monitor [0xa4bf000..0xa4bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c64d80 nid=0x564 waiting on monitor [0xa47f000..0xa47fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8c66818 nid=0x568 waiting on monitor [0xa43f000..0xa43fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=5
    tid=0x8b63838 nid=0x56c waiting on monitor [0xa3ff000..0xa3ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "rawStoreDaemon" daemon prio=5 tid=0x8c83d20 nid=0x570 waiting on monitor
    [0xa3bf000..0xa3bfdbc]
    at java.lang.Object.wait(Native Method)
    at c8e._x.a.c(Unknown Source)
    at c8e._x.a.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:484)
    "antiGC" daemon prio=2 tid=0x8c5f298 nid=0x7e8 waiting on monitor
    [0xa37f000..0xa37fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at c8e.ad.a.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fd7b0
    nid=0x588 waiting on monitor [0xa33f000..0xa33fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fcbf8
    nid=0x58c waiting on monitor [0xa2ff000..0xa2ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fc040
    nid=0x590 waiting on monitor [0xa2bf000..0xa2bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fb488
    nid=0x594 waiting on monitor [0xa27f000..0xa27fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8fa900
    nid=0x598 waiting on monitor [0xa23f000..0xa23fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8f9df0
    nid=0x780 waiting on monitor [0xa1ff000..0xa1ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x908be0
    nid=0x59c waiting on monitor [0xa1bf000..0xa1bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x9080a0
    nid=0x5a0 waiting on monitor [0xa17f000..0xa17fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x907590
    nid=0x5a4 waiting on monitor [0xa13f000..0xa13fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8e60d58
    nid=0x5a8 waiting on monitor [0xa0ff000..0xa0ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8ad3e48
    nid=0x5ac waiting on monitor [0xa0bf000..0xa0bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9fbd8
    nid=0x5b0 waiting on monitor [0xa07f000..0xa07fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9fab0
    nid=0x5f0 waiting on monitor [0xa03f000..0xa03fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8c9f6b8
    nid=0x5f8 waiting on monitor [0x9fff000..0x9fffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x901008
    nid=0x5fc waiting on monitor [0x9fbf000..0x9fbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8c316d0 nid=0x600 waiting on monitor [0x9f7f000..0x9f7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8c31928 nid=0x604 waiting on monitor [0x9f3f000..0x9f3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5 tid=0x8b9cdd0 nid=0x608 waiting on monitor [0x9eff000..0x9effdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8c24008 nid=0x60c waiting on monitor [0x9ebf000..0x9ebfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8bfa2a0 nid=0x610 waiting on monitor [0x9e7f000..0x9e7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8bf9818 nid=0x618 waiting on monitor [0x9e3f000..0x9e3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8be9180 nid=0x648 waiting on monitor [0x9dff000..0x9dffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8be8670 nid=0x630 waiting on monitor [0x9dbf000..0x9dbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8c15dd8 nid=0x62c waiting on monitor [0x9d7f000..0x9d7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8f04d78 nid=0x560 waiting on monitor [0x9d3f000..0x9d3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8ee8e08 nid=0x764 waiting on monitor [0x9cff000..0x9cffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8efbba0 nid=0x75c waiting on monitor [0x9cbf000..0x9cbfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x8efb948 nid=0x7c8 waiting on monitor [0x9c7f000..0x9c7fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=5
    tid=0x8bcf588 nid=0x80c waiting on monitor [0x9c3f000..0x9c3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=5
    tid=0x8bcf400 nid=0x55c waiting on monitor [0x9bff000..0x9bffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x8c01568 nid=0x6a0 waiting on
    monitor [0x9bbf000..0x9bbfdbc]
    at java.lang.Object.wait(Native Method)
    at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :138)
    at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=5 tid=0x8bc1288 nid=0x6c8 waiting on
    monitor [0x9b7f000..0x9b7fdbc]
    at java.lang.Object.wait(Native Method)
    at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :138)
    at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x8bbbf40 nid=0x704 waiting on
    monitor [0x9b3f000..0x9b3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:5
    7)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x8b5bac0
    nid=0x54c runnable [0x9aff000..0x9affdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at
    weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:501)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x8b5a350
    nid=0x688 runnable [0x9a7f000..0x9a7fdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at
    weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:501)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x8b59818
    nid=0x790 waiting on monitor [0x9a3f000..0x9a3fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x8bf8c50
    nid=0x4a0 waiting on monitor [0x99ff000..0x99ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x8bf8110
    nid=0x5d0 waiting on monitor [0x99bf000..0x99bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x8bf75d0
    nid=0x74c waiting on monitor [0x997f000..0x997fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x8bf6a90
    nid=0x7e0 waiting on monitor [0x993f000..0x993fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x8bf6008
    nid=0x7f8 waiting on monitor [0x98ff000..0x98ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x8bce3f0
    nid=0x818 waiting on monitor [0x98bf000..0x98bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x8bcd8e0
    nid=0x6e4 waiting on monitor [0x987f000..0x987fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x8b579e0
    nid=0x814 waiting on monitor [0x983f000..0x983fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=5 tid=0x8bc1e48
    nid=0x7ec waiting on monitor [0x97ff000..0x97ffdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x8bc1d20
    nid=0x7f4 waiting on monitor [0x97bf000..0x97bfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=5 tid=0x8b93d28
    nid=0x770 waiting on monitor [0x977f000..0x977fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=10 tid=0x8adce30 nid=0x808 waiting on monitor
    [0x973f000..0x973fdbc]
    at java.lang.Thread.sleep(Native Method)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1543)
    at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=10 tid=0x911c48 nid=0x620 waiting on
    monitor
    [0..0]
    "Finalizer" daemon prio=9 tid=0x90dd10 nid=0x614 waiting on monitor
    [0x8d5f000..0x8d5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=10 tid=0x8aa0bc0 nid=0x7f0 waiting on
    monitor [0x8d1f000..0x8d1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=5 tid=0x234db0 nid=0x800 waiting on monitor [0x6f000..0x6fc34]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:591)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=5 tid=0x966a90 nid=0x6b4 runnable
    "VM Periodic Task Thread" prio=10 tid=0x910980 nid=0x7d0 waiting on monitor
    "Suspend Checker Thread" prio=10 tid=0x9112d0 nid=0x6fc runnable

  • Error in starting weblogic commerce server on Win2000

    I downloaded the evaluation release of Weblogic Commerce 3.1 and th licence,
    and installed it on Windows 2000 Professional,
    I have a Weblogic Application Server 5.1 installed
    the server did not start and gave an error, please help us as to what the
    problem is and how to get it running.
    =========== Error Message ===============
    JAVA_CLASSPATH IS
    C:\jdk\lib\tools.jar;C:\weblogic\lib\weblogic510sp6boot.jar;C:
    \weblogic\classes\boot
    WEBLOGIC_CLASSPATH IS
    C:\weblogic\lib\weblogic510sp6.jar;C:\weblogic\lib\WebLogi
    c_RDBMS.jar;C:\weblogic\license;C:\weblogic\classes;C:\weblogic\lib\weblogic
    aux.
    jar;C:\weblogic\lib\weblogic-tags-510.jar;C:\WebLogicCommerceServer3.1\licen
    se;C
    :\WebLogicCommerceServer3.1\classes;C:\WebLogicCommerceServer3.1\lib\rules.j
    ar;C
    :\WebLogicCommerceServer3.1\lib\jrulesserviceprovider.jar;C:\WebLogicCommerc
    eSer
    ver3.1\deploy\bmp\classes;C:\WebLogicCommerceServer3.1\eval\win32\Taxware\cl
    asse
    s;C:\weblogic\eval\cloudscape\lib\cloudscape.jar;C:\weblogic\eval\cloudscape
    \lib
    \tools.jar;C:\weblogic\eval\cloudscape\lib\client.jar
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <WebLogicServer> Read global
    properties C:\WebLogicCommerceServer3.1\weblogic.propertie
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <WebLogicServer> No per-server
    properties files found
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Logging> FileLogger initialized.
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <WebLogicServer> ************
    WebLogic Server (5.1.0 04/03/2000 17:13:23 #66825) 'serve
    :\WebLogicCommerceServer3.1
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <WebLogicServer> ************ (c)
    1995, 1996, 1997, 1998 WebLogic, Inc., (c) 1999 BEA S
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.swapIntervalSecs', current value: '10'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.ConnectionConsumer', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.enforceClientCert', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.login.readTimeoutMillis', current value: '5000'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.propertiesFile', current value: 'C:\WebLogicCo
    .properties'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.bindAddr', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.servlet.reloadCheckSecs', current value: '-1'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.authRealmName', current value: 'WebLogic Server
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.SSLHandler.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.startupFailureIsFatal', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.http.keepAliveSecs', current value: '60'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.servlet.classpath', current value: ''
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.tunneling.clientPingSecs', current value: '45'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.defaultWebApp', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.persistentStoreDir', current value: 'se
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.perServerPropertiesFile', current value: 'null
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.queue', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.invalidationIntervalSecs', current valu
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.persistence', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.user.enable', current value: 'tr
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.rmi.dgc.callSystemGC', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.enableEvents', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.maxTransactedDurableSubscribers', current value:
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.weight', current value: '100'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.connectionPoolArgs', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.disableGuest', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.persistentStorePool', current value: ''
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.URLAclFile', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.percentSocketReaders', current value: '33'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.zac.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jdbc.TXDataSource', current value: '[weblogic.jdbc.TX
    .jts.commercePool=commercePool ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.DNSName', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.ejb.deploy', current value: 'C:/WebLogicCommerceServe
    C:/WebLogicCommerceServer3.1/lib/axiom.jar,C:/WebLogicCommerceServer3.1/lib/
    ebusiness.jar,C:/WebLogicCommerceServer3.1/lib/adv
    erceServer3.1/lib/bridge.jar,C:/WebLogicCommerceServer3.1/lib/document.jar,C
    :/WebLogicCommerceServer3.1/lib/p13nadvisor.jar,C:
    .1/lib/portal.jar,C:/WebLogicCommerceServer3.1/lib/ruleeditorbeans.jar,C:/We
    bLogicCommerceServer3.1/lib/rulesservice.jar,C:/We
    lib/servicemgr.jar'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.workspace.showUserKeysOnly', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.allow', current value: '[weblogic.allow.reserve.weblo
    commercePool=everyone
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    weblogic.allow.execute.weblogic.servlet.Admin
    low.execute.weblogic.servlet.AdminLicense=system
    weblogic.allow.execute.weblogic.servlet.AdminConnections=system
    weblogic.allo
    et.classes=everyone
    weblogic.allow.execute.weblogic.servlet.AdminClients=system
    weblogic.allow.execute.weblogic.servlet.AdminV
    llow.execute.weblogic.servlet.AdminMain=system
    weblogic.allow.execute.weblogic.servlet.AdminThreads=system
    weblogic.allow.rese
    tionPool.docPool=everyone weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.execute.weblogic.servlet.AdminEvents=
    ite.weblogic.workspace=everyone
    weblogic.allow.execute.weblogic.servlet.AdminJDBC=system
    weblogic.allow.execute.weblogic.servl
    ow.execute.weblogic.servlet.AdminProps=system
    weblogic.allow.execute.weblogic.servlet.ConsoleHelp=everyone ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.listenPort', current value: '7501'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.allow', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.servlet.reloadOnModify', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.io.fileSystem', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.startupArgs', current value: '[weblogic.system
    p=TraceFlags=E ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jdbc.enableLogFile', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookie.domain', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.debug', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.clustering.enable', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.shutdownArgs', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.rmi.startupClass', current value: '[weblogic.rmi.star
    blogic.rmi.internal.RegistryImpl ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.keepAlive.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.jdbc.connTimeoutSecs', current value: '
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.name', current value: 'server'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.helpPageURL', current value: 'http://www.weblo
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.key.server', current value: 'C:\WebLogicComm
    okey.pem'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.rmi.startupArgs', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.topicSessionPool', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.logFileBufferKBytes', current value: '8'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.home', current value: 'C:\weblogic'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.documentRoot', current value: 'public_html'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.servlet.reloadOnModifyRecursive', current value
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.errorPage', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.certificate.authority3', current value: 'nul
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.administrativePort', current value: '0'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.certificate.authority2', current value: 'nul
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.startupClass', current value: '[weblogic.syste
    tup=com.beasys.commerce.foundation.plugin.weblogic.TraceStartup
    weblogic.system.startupClass.KeyBootstrap=com.beasys.commerce.
    otstrap
    weblogic.system.startupClass.serviceManager=com.beasys.commerce.servicemanag
    er.CommerceServiceManagerStartup ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.nonPrivGroup', current value: 'nobody'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.multicastTTL', current value: '1'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.home', current value: 'C:\WebLogicCommerceServ
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.https.keepAliveSecs', current value: '120'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jndi.transportableObjectFactories', current value: ''
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.certificateCacheSize', current value: '3'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.tunneling.clientTimeoutSecs', current value: '4
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jdbc.DataSource', current value: '[weblogic.jdbc.Data
    l.docPool=docPool ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.nonPrivUser', current value: 'nobody'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.zac.publishRoot', current value: 'exports'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.clientRootCA', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.defaultLoadAlgorithm', current value: 'round-
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.enable', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.administrator.phone', current value: '(None)'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jdbc.connectionPool', current value: '[weblogic.jdbc.
    rl=jdbc:beasys:docmgmt:com.beasys.commerce.axiom.document.ref.RefDocumentPro
    vider,driver=com.beasys.commerce.axiom.document.jd
    =0,initialCapacity=10,maxCapacity=20,capacityIncrement=1,allowShrinking=true
    ,shrinkPeriodMins=15,refreshMinutes=5,props=jdbc.u
    mmercePool;jdbc.isPooled=true;weblogic.t3.waitForConnection=true;weblogic.t3
    .waitSecondsForConnection=999999999999;weblogic.jt
    onSecs=999999999999;docBase=C:/WebLogicCommerceServer3.1/dmsBase;schemaXML=C
    :/WebLogicCommerceServer3.1/dmsBase/doc-schema.xml
    nPool.commercePool=url=jdbc:cloudscape:Commerce;create=true;upgrade=true,dri
    ver=COM.cloudscape.core.JDBCDriver,loginDelaySecs=
    Capacity=20,capacityIncrement=1,allowShrinking=true,shrinkPeriodMins=15,test
    ConnsOnReserve=true,testTable=WLCS_IS_ALIVE,refres
    ne;password=none;server=none;weblogic.t3.waitForConnection=true;weblogic.t3.
    waitSecondsForConnection=999999999999,weblogic.jts
    nSecs=999999999999,verbose=false ]'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.debug', current value: 'false'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jdbc.logFileName', current value: 'C:\WebLogicCommerc
    og'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.dnsName', current value: 'null'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.requireAuthentication', current value: 'true'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.multicastAddress', current value: ''
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.defaultSecureProtocol', current value: 't3s'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.auth.enable', current value: 'tr
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.executeThreadCount', current value: '15'
    Fri Dec 01 11:04:39 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookie.comment', current value: 'Weblog
    ng Cookie'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.tableNamePrefix', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.connectionPool', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.shutdownClass', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.defaultServlet', current value: 'file'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.name', current value: 'mycluster'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.defaultProtocol', current value: 't3'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.postTimeoutSecs', current value: '30'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.group', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.caseSensitive', current value: '
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.certificate.server', current value: 'C:\WebL
    rver\democert.pem'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.mimeType', current value: '[weblogic.httpd.mime
    .wmlscriptc=wmlsc weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.image/gif=gif weblogic.httpd.mim
    stream=exe weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.application/pdf=pdf weblogic.httpd.mimeType.appl
    ar weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    weblogic.httpd.mimeType.applica
    tpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.application/vnd.
    ttpd.mimeType.application/x-java-serialized-object=ser ]'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.webApp', current value: '[weblogic.httpd.webApp
    rceServer3.1/server/webapps/examples/portal/portal.war
    weblogic.httpd.webApp.tools=C:/WebLogicCommerceServer3.1/server/webapps
    c.httpd.webApp.wlcs=C:/WebLogicCommerceServer3.1/server/webapps/wlcs/ ]'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.minPasswordLen', current value: '8'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.connectionFactoryArgs', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.persistentStoreType', current value: 'f
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cacheEntries', current value: '1024'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.certificate.authority', current value: 'C:\W
    \server\ca.pem'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.resource.MailSession', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookie.maxAgeSecs', current value: '-1'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.login.readTimeoutMillisSSL', current value: '25000'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.cluster.enable', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.SSL.ciphersuites', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.indexFiles', current value: 'index.html,index.h
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.password', current value: '[weblogic.password.system=
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.enableLogFile', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.enableReverseDNSLookups', current value: 'fals
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.indexDirectories', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.maxLogFileSize', current value: '1024'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.logFile', current value: 'C:\WebLogicCommerceS
    .log'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.timeoutSecs', current value: '3600'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.logFileFormat', current value: 'common'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.perClusterPropertiesFile', current value: 'nul
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.key.export.lifespan', current value: '500'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.CORBA.connectionPool', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'java.system.property', current value: '[java.system.property.c
    /WebLogicCommerceServer3.1/db/data ]'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.logFileName', current value: 'C:\WebLogicCommer
    s.log'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.defaultMimeType', current value: 'text/plain'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.debug.httpd.servlet', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.connectionFactoryName', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.SSLListenPort', current value: '7502'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.URLResource', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookie.name', current value: 'WebLogicS
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.quiescent', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.register', current value: '[weblogic.httpd.regi
    sys.commerce.foundation.flow.FlowManager
    weblogic.httpd.register.AdminProps=admin.AdminProps
    weblogic.httpd.register.classes=w
    hServlet weblogic.httpd.register.AdminEvents=admin.AdminEvents
    weblogic.httpd.register.AdminMain=admin.AdminMain weblogic.http
    gic.servlet.ServerSideIncludeServlet
    weblogic.httpd.register.servletimages=weblogic.servlet.internal.InternalImag
    eServlet webl
    oleHelp=weblogic.servlet.ClasspathServlet
    weblogic.httpd.register.AdminJDBC=admin.AdminJDBC
    weblogic.httpd.register.ShowDocSer
    .content.ShowDocServlet
    weblogic.httpd.register.*.jsp=weblogic.servlet.JSPServlet
    weblogic.httpd.register.AdminCaptureRootCA=a
    weblogic.httpd.register.AdminRealm=admin.AdminRealm
    weblogic.httpd.register.AdminLicense=admin.AdminLicense weblogic.httpd.reg
    certificate weblogic.httpd.register.AdminConnections=admin.AdminConnections
    weblogic.httpd.register.AdminClients=admin.AdminCl
    ister.file=weblogic.servlet.FileServlet
    weblogic.httpd.register.AdminVersion=admin.AdminVersion
    weblogic.httpd.register.authen
    .ClientAuthenticationServlet
    weblogic.httpd.register.AdminThreads=admin.AdminThreads ]'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.clientRootCA4', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.clientRootCA3', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.clientRootCA2', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookies.enable', current value: 'true'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.servlet.extensionCaseSensitive', current value:
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.group.enable', current value: 't
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.nativeIO.enable', current value: 'true'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.rmi.enableServerSideStubs', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.cookie.path', current value: '/'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.session.URLRewriting.enable', current value: 't
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.enableSetUID', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.acl.enable', current value: 'tru
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.topic', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.administrator.name', current value: 'WebLogic Adminis
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.jms.queueSessionPool', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.ssl.enable', current value: 'true'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.administrator.location', current value: '(None)'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.enableSetGID', current value: 'false'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.initArgs', current value: '[weblogic.httpd.init
    Filename=/weblogic/admin/help/NoContent.html
    weblogic.httpd.initArgs.*.jsp=pageCheckSeconds=0,packagePrefix=jsp,compileCo
    mmand
    gDir=C:/WebLogicCommerceServer3.1/server/classfiles,verbose=false,keepgenera
    ted=false weblogic.httpd.initArgs.file=defaultFile
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.administrator.email', current value: 'root'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.enableConsole', current value: 'true'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.security.realm.cache.perm.enable', current value: 'tr
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.system.user', current value: 'system'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <Config> Property name:
    'weblogic.httpd.charsets', current value: 'null'
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> awt.toolkit =
    sun.awt.windows.WToolkit
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> cloudscape.system.home
    = C:/WebLogicCommerceServer3.1/db/data
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> commerce.properties =
    C:\WebLogicCommerceServer3.1\weblogiccommerce.prop
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> file.encoding = Cp1252
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> file.encoding.pkg =
    sun.io
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> file.separator = \
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.awt.fonts =
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.awt.graphicsenv =
    sun.awt.Win32GraphicsEnvironment
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.awt.printerjob =
    sun.awt.windows.WPrinterJob
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.class.path =
    C:\jdk\lib\tools.jar;C:\weblogic\lib\weblogic510sp6boo
    s\boot
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.class.version =
    46.0
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.compiler =
    symcjit
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.ext.dirs =
    C:\jdk\jre\lib\ext
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.home = C:\jdk\jre
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.io.tmpdir =
    C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.library.path =
    C:\jdk\bin;.;C:\WINNT\System32;C:\WINNT;C:\WINNT\sys
    System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program
    Files\Microsoft Visual Studio\Common\MSDev98\Bin;
    ft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual
    Studio\VC98\bin;C:\jdk\bin;C:\weblogic\bin;C:\weblogic\bin;C:\
    1\eval\win32\CyberCash\bin;C:\WebLogicCommerceServer3.1\eval\win32\Taxware\b
    in
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.protocol.handler.pkgs = weblogic.utils|weblogic.utils
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.security.manager
    =
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.security.policy =
    C:\weblogic\weblogic.policy
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.specification.name = Java Platform API Specification
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.specification.vendor = Sun Microsystems Inc.
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.specification.version = 1.2
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vendor = Sun
    Microsystems Inc.
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vendor.url =
    http://java.sun.com/
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vendor.url.bug =
    http://java.sun.com/cgi-bin/bugreport.cgi
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.version = 1.2.2
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vm.info = build
    JDK-1.2.2-001, native threads, symcjit
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vm.name = Classic
    VM
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.vm.specification.name = Java Virtual Machine Specification
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.vm.specification.vendor = Sun Microsystems Inc.
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    java.vm.specification.version = 1.0
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vm.vendor = Sun
    Microsystems Inc.
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> java.vm.version =
    1.2.2
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> line.separator =
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> os.arch = x86
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> os.name = Windows NT
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> os.version = 5.0
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> path.separator = ;
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> pipeline.properties =
    C:\WebLogicCommerceServer3.1\pipeline.properties
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> sun.boot.class.path =
    C:\jdk\jre\lib\rt.jar;C:\jdk\jre\lib\i18n.jar;C:\j
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> sun.boot.library.path
    = C:\jdk\jre\bin
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props>
    sun.io.unicode.encoding = UnicodeLittle
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> user.dir =
    C:\WebLogicCommerceServer3.1
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> user.home =
    C:\Documents and Settings\Administrator
    Fri Dec 01 11:04:40 GMT+05:30 2000:<I> <System Props> user.language = en
    Fri Dec 01 11:04:40 GMT+05:30 2

    Hello Muffy,
    It looks like you do not have WLS 5.1 service pack 6 installed correctly. I
    say this because I do not see the sp6 message at the top of your log and I saw
    this message in your log:
    org.xml.sax.SAXParseException: Element "weblogic-enterprise-bean" allows no
    further input; "transaction-isolation" is not allowed
    Ture Hoefner
    BEA Systems, Inc.
    2590 Pearl St.
    Suite 110
    Boulder, CO 80302
    www.bea.com

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # CORE PROPERTIES
    # You should set these before you start the WebLogic Server the first time.
    # If you need more instructions on individual properties in this
    # section, check the same section in the Optional Properties, where
    # we've left the long explanations. Or, better yet, go to our
    # website and read all about properties, at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # CORE SYSTEM PROPERTIES
    # TCP/IP port number at which the WebLogic Server listens for connections
    weblogic.system.listenPort=7001
    # CORE SECURITY-RELATED PROPERTIES
    # Read important information about security at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # REQUIRED: The system password MUST be set in order to start the
    # WebLogic Server. This password is case-sensitive, at least 8 characters.
    # The username for the privileged user is ALWAYS "system".
    # This username and password also includes httpd access (see
    # HTTPD properties below).
    weblogic.password.system=12345678
    # RECOMMEND Set to 'everyone' if HTTPD is enabled
    weblogic.allow.execute.weblogic.servlet=everyone
    # Set individual ACLs to restrict access to HTTP-related resources,
    # such as the Administration servlets.
    # To make your own servlets generally available, follow this
    # pattern (provide a weblogic.allow.execute) for your packages and
    # set ACLs as appropriate.
    # CORE SECURITY-RELATED PROPERTIES FOR SSL
    # Read important information about SSL at:
    # http://www.weblogic.com/docs51/classdocs/API_secure.html
    # Enable SSL
    # (default if property not defined is false)
    weblogic.security.ssl.enable=true
    # SSL listen port
    weblogic.system.SSLListenPort=7002
    # Servlets for SSL
    # Authentication servlet for creating tokens for applets
    weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
    ervlet
    # Limits number of unclaimed stored tokens
    weblogic.security.certificateCacheSize=3
    # Capture CA root of client servlet
    weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
    # Certificates for SSL
    # Name of acceptable CA roots
    # For client authentication change value to a valid .pem file
    #weblogic.security.clientRootCA=SecureServerCA.pem
    # Server certificates for SSL
    weblogic.security.certificate.server=democert.pem
    weblogic.security.key.server=demokey.pem
    weblogic.security.certificate.authority=ca.pem
    # registration for certificate generator servlet
    weblogic.httpd.register.Certificate=utils.certificate
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    # CORE HTTPD ADMINISTRATIVE PROPERTIES
    # True permits the HTTPD to run (default)
    # Uncomment this property to disable HTTPD
    #weblogic.httpd.enable=false
    # If authentication is required, add username/password for each user
    # who will be included in an ACL, as in this commented-out example:
    #weblogic.password.peter=#8gjsL4*
    # SYSTEM PROPERTIES
    # System properties in this section are set to system defaults
    # Performance pack. The shared library must be accessible from your
    # PATH (NT) or from your shared library path (UNIX; the name of the
    # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
    weblogic.system.nativeIO.enable=true
    # Outputs logging information to the console as well as to the log file
    weblogic.system.enableConsole=true
    # Sets the directory or URL for the WebLogic Admin help pages
    # The help pages are shipped in the "docs/adminhelp" directory, in the
    # default document root in public_html
    weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
    # If you prefer to access the most recent help pages, you can do so online
    # by commenting out the previous property and uncommenting this one:
    #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
    # Properties for tuning the server's performance
    # Number of WebLogic Server execute threads.
    weblogic.system.executeThreadCount=15
    # Other optional system properties
    # Limits size of weblogic.log (in K) and versions old log
    weblogic.system.maxLogFileSize=1024
    # Adjust minimum length of password
    weblogic.system.minPasswordLen=8
    # UNIX only: If running on port 80 on UNIX, enable the setUID program
    #weblogic.system.enableSetUID=false
    # UNIX only: Unprivileged user to setUID to after starting up
    # WebLogic Server on port 80
    #weblogic.system.nonPrivUser=nobody
    # CLUSTER-SPECIFIC PROPERTIES
    # Cluster-specific properties in this section are set to system defaults.
    # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
    # in the per-cluster properties file ONLY.
    # Time-to-live (number of hops) for the cluster's multicast messages
    # (default 1, range 1-255).
    #weblogic.cluster.multicastTTL=1
    # Sets the load-balancing algorithm to be used between
    # replicated services if none is specified. If not specified,
    # round-robin is used.
    #weblogic.cluster.defaultLoadAlgorithm=round-robin
    # SERVER-SPECIFIC CLUSTER PROPERTIES
    # Cluster-related properties in this section are set to system defaults.
    # CLUSTER USERS: Note that these server-specific cluster-related properties
    # should be set in the per-server properties file ONLY.
    # Sets the weight of the individual server for the weight-based
    load-balancing.
    # Range is 0 - 100.
    # Larger numbers increase the amount of traffic routed to this server.
    #weblogic.system.weight=100
    # SYSTEM STARTUP FILES - Examples
    # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
    # objects should be registered in the per-server properties file.
    # All other startup classes should be registered in the per-cluster
    # properties file.
    # For more info on writing and using startup file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a startup class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.startupClass.[virtual_name]=[full_pathname]
    # Add arguments for the startup class
    #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/StartupQuery.java
    #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
    #weblogic.system.startupArgs.doquery=\
    # query=select * from emp,\
    # db=jdbc:weblogic:pool:demoPool
    # SYSTEM SHUTDOWN FILES - Examples
    # For more info on writing and using shutdown file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a shutdown class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
    # Add arguments for the shutdown class
    #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/ShutdownTest.java
    #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
    #weblogic.system.shutdownArgs.ShutdownTest=\
    # outfile=c:/temp/shutdown.log
    # SECURITY-RELATED PROPERTIES FOR WORKSPACES
    # For backward compatibility, the following entries disable Access
    # Control on Workspaces
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    # JOLT FOR WEBLOGIC PROPERTIES
    # These properties configure a BEA Jolt connection pool for use with
    # the simpapp and bankapp examples, and register a servlet for use with
    # with the simpapp example. The default server address provided here
    # points to a public TUXEDO server that is hosted by BEA for use with
    # this example.
    # Servlet registration for simpapp example:
    #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
    t
    # Pool creation and cleanup
    # note this example is set up to work with the public
    # demo TUXEDO server available from BEA's website:
    #weblogic.system.startupClass.demojoltpoolStart=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    #weblogic.system.startupArgs.demojoltpoolStart=\
    # poolname=demojoltpool,\
    # appaddrlist=//beademo1.beasys.com:8000,\
    # failoverlist=//beademo1.beasys.com:8000,\
    # minpoolsize=1,\
    # maxpoolsize=3
    #weblogic.system.shutdownClass.demojoltpoolStop=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    #weblogic.system.shutdownArgs.demojoltpoolStop=\
    # poolname=demojoltpool
    # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
    # The registrations enable a BEA IIOP connection pool and
    # register servlets for use with the simpapp and university examples.
    # Configure for your environment and uncomment to use.
    # Uncommenting these properties requires WebLogic Enterprise Connectivity
    # and an operating WebLogic Enterprise Server.
    # Servlet registration for simpapp servlet example
    #weblogic.httpd.register.SimpappServlet=\
    # examples.wlec.servlets.simpapp.SimpappServlet
    #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
    # Servlet registration for simpapp EJB example
    # (You'll need to add the wlec_ejb_simpapp.jar to the
    # weblogic.ejb.deploy property in this file.)
    #weblogic.httpd.register.ejbSimpappServlet=\
    # examples.wlec.ejb.simpapp.ejbSimpappServlet
    #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
    # Pool creation and cleanup for the simpapp example
    #weblogic.CORBA.connectionPool.simplepool=\
    # appaddrlist=//wlehost:2468,\
    # failoverlist=//wlehost:2468,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # domainname=simpapp
    # Servlet registration for university Servlet example:
    #weblogic.httpd.register.UniversityServlet=\
    # examples.wlec.servlets.university.UniversityServlet
    #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
    # Pool creation and cleanup for the University example:
    #weblogic.CORBA.connectionPool.Univpool=\
    # appaddrlist=//wlehost:2498,\
    # failoverlist=//wlehost:2498,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # apppassword=wlepassword,\
    # domainname=university
    # WEBLOGIC FILE PROPERTIES
    # Maps a volume name to a path, for client file read/write
    #weblogic.io.fileSystem.[volumeName]=[fullPathName]
    # WEBLOGIC JMS DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL JMS deployment should be done in the
    # per-cluster properties file ONLY.
    # You set up a JDBC connection pool if you want persistent messages
    # (including durable subscriptions). To use JMS and EJBs in the same
    # transaction, both must use the same JDBC connection pool. Uncomment
    # the following property to use the default JDBC connection pool
    # 'demo', which is defined in the Demo connection pool section of this file.
    #weblogic.jms.connectionPool=demoPool
    # The JMS Webshare example demonstrates how the ClientID for a
    # durable subscriber is configured in the connection factory:
    #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
    #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
    #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
    #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
    # The JMS trader example shows how to use JMS with an EJB. In addition
    # to uncommenting the following properties, you must also set up and
    # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
    # ejb_basic_statelessSession.jar to try out this JMS example:
    #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
    #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
    #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
    #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
    # Registers the underlying servlet
    #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
    # These properties are used with the ServerReceive JMS example,
    # which demonstrates how to establish a JMS message consumer
    # in a startup class:
    #weblogic.system.startupClass.serverReceive=\
    # examples.jms.startup.ServerReceive
    #weblogic.system.startupArgs.serverReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    # These properties are used with the PoolReceive JMS example,
    # which demonstrates how to establish a pool of JMS message consumers
    # in a startup class:
    #weblogic.system.startupClass.poolReceive=\
    # examples.jms.startup.PoolReceive
    #weblogic.system.startupArgs.poolReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
    # WEBLOGIC RMI DEMO PROPERTIES
    # CLUSTER USERS: Note that pinned RMI objects should be registered
    # in the per-server properties file ONLY. All other RMI startup
    # classes should be registered in the per-cluster properties file.
    # Remote classes registered at startup after the pattern:
    #weblogic.system.startupClass.[virtualName]=[fullPackageName]
    # These examples can be compiled to see RMI in action. Uncomment to use:
    #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
    #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
    #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
    # WEBLOGIC EJB DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL EJB deployment should be done in the
    # per-cluster properties file ONLY.
    # See WebLogic Demo Connection Pool below for a connection pool
    # to use with these examples.
    # Deploys EJBeans. Uncomment the appropriate lines below and
    # modify DBMS-related info and paths to match your particular installation:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/weblogic/myserver/jolt_ejb_bankapp.jar
    # Servlet used by the EJB basic beanManaged example
    # Uncomment to use:
    weblogic.httpd.register.beanManaged=\
    examples.ejb.basic.beanManaged.Servlet
    # Add a list of users (set the password with
    weblogic.password.[username]=XXX)
    # to set an ACL for this servlet:
    #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
    #weblogic.password.user1=user1Password
    #weblogic.password.user2=user2Password
    # WEBLOGIC XML DEMO PROPERTIES
    # These properties are required to run the XML examples.
    # Uncomment to use.
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
    # BizTalk example properties
    #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
    #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
    #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
    dapter
    #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
    # WEBLOGIC ZAC DEMO PROPERTIES
    # These registrations enable the ZAC Publish Wizard.
    weblogic.zac.enable=true
    # Set the publish root for a WebLogic Server. Edit and
    # uncomment to use.
    #weblogic.zac.publishRoot=d:/weblogic/zac
    # Set an ACL for each package you publish. The [name] is
    # the "Package name" you assign in the ZAC Publish Wizard.
    # Publish a package, edit this property, and uncomment to use.
    #weblogic.allow.read.weblogic.zac.[name]=[user list]
    #weblogic.allow.write.weblogic.zac.[name]=system
    # HTTPD ADMINISTRATIVE PROPERTIES
    # Enables logging of HTTPD info in common log format and
    # sets the log file name (default is "access.log" in "myserver")
    weblogic.httpd.enableLogFile=true
    weblogic.httpd.logFileName=access.log
    # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
    weblogic.httpd.enableEvents=false
    # Enables HTTP sessions
    weblogic.httpd.session.enable=true
    # Sets an optional cookie name. The default name is "WebLogicSession".
    # Prior to version 4.0, the default was "TengahSession". To make
    # this backward compatible with cookies generated from previous
    # installations, you should set this property to "TengahSession".
    # Uncomment this line and set this to any string of your choice,
    # or comment out this property to use the default.
    #weblogic.httpd.session.cookie.name=WebLogicSession
    # MIME types
    weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.image/gif=gif
    weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.application/pdf=pdf
    weblogic.httpd.mimeType.application/zip=zip
    weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.application/x-java-archive=jar
    weblogic.httpd.mimeType.application/x-java-serialized-object=ser
    weblogic.httpd.mimeType.application/octet-stream=exe
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
    weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    # In seconds, the keep-alive for HTTP and HTTPS requests
    weblogic.httpd.http.keepAliveSecs=60
    weblogic.httpd.https.keepAliveSecs=120
    # WEBLOGIC JDBC DRIVER PROPERTIES
    # Enables JDBC driver logging and sets the file name for the log
    # The weblogic.jdbc.logFile is placed in the per-server
    # directory (default is "myserver")
    weblogic.jdbc.enableLogFile=false
    weblogic.jdbc.logFileName=jdbc.log
    # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # For creating JDBC connection pools. This example shows a connection
    # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
    # to use 4 JDBC connections (with a potential for up to 10 connections,
    # incremented by two at a time, with a delay of 1 second between each
    # attempt to connect to the database), to an Oracle database server called
    # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
    # connections are dropped from the pool until only 4 connections remain
    open.
    # Every 10 minutes, any unused connections in the pool are tested and
    # refreshed if they are not viable.
    #weblogic.jdbc.connectionPool.oraclePool=\
    # url=jdbc:weblogic:oracle,\
    # driver=weblogic.jdbc.oci.Driver,\
    # loginDelaySecs=1,\
    # initialCapacity=4,\
    # maxCapacity=10,\
    # capacityIncrement=2,\
    # allowShrinking=true,\
    # shrinkPeriodMins=15,\
    # refreshMinutes=10,\
    # testTable=dual,\
    # props=user=SCOTT;password=tiger;server=DEMO
    # Get more details on each argument for this property in the
    # Administrators Guide on setting properties at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # Set up ACLs for this connection pool with the following:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • TagExtraInfo example in weblogic 5.1 doesn't work!!!!!

              Hi
              i was trying example given in weblogic 5.1 i.e. session list. that uses tagextrainfo
              class to set the attributes in JSP. but it doesn't work.
              Please respond to this error.
              i am attaching error docs error.txt
              On Browser
              Compilation of 'E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java'
              failed:
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:93: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 49:
              <td><%= name %></td>
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:95: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 50:
              <td><%= value %></td>
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:99: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 51:
              <td><a href="<%=request.getRequestURI()%>?action=delete&delName=<%=name%>">
              On Server Console
              Mon Oct 08 18:26:06 GMT+05:30 2001:<I> <ServletContext-General> looking for taglib
              uri session.tld a
              s resource /WEB-INF/session.tld in Web Application root:
              Mon Oct 08 18:26:10 GMT+05:30 2001:<I> <ServletContext-General> Generated java
              file: E:\weblogic\mys
              erver\classfiles\jsp_servlet\_sessionlist.java
              Mon Oct 08 18:26:29 GMT+05:30 2001:<E> <ServletContext-General> Compilation of
              E:\weblogic\myserver\
              classfiles\jsp_servlet\_sessionlist.java failed:
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:93: cannot resolve
              symbol
              symbol : variable name
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf( name )); //[ /SessionList.jsp;
              Line: 49]
              ^
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:95: cannot resolve
              symbol
              symbol : variable value
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf( value )); //[ /SessionList.jsp;
              Line: 50]
              ^
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:99: cannot resolve
              symbol
              symbol : variable name
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf(name)); //[ /SessionList.jsp;
              Line: 51]
              ^
              3 errors
              java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[d:/jdk1.3/bin/javac.exe,
              -c
              lasspath, d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\jdk1.3\jre\lib\sunrsasign.jar;d:\jd
              k1.3\jre\classes;.\lib\weblogic510sp10boot.jar;.\classes\boot;.\eval\cloudscape\lib\cloudscape.jar;d
              :\jdk1.3\lib\tools.jar;;.\license;.\lib\weblogic510sp10.jar;.\classes;.\lib\weblogicaux.jar;.\myserv
              er\serverclasses;E:\weblogic\myserver\servletclasses;E:\weblogic\myserver\public_html;E:\weblogic\my
              server\classfiles;null, -d, E:\weblogic\myserver\classfiles, E:\weblogic\myserver\classfiles\jsp_ser
              vlet\_sessionlist.java])
              at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:459)
              at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:249)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:366)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
              269)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              Mon Oct 08 18:26:31 GMT+05:30 2001:<E> <ServletContext-General> Servlet failed
              with Exception
              java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[d:/jdk1.3/bin/javac.exe,
              -c
              lasspath, d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\jdk1.3\jre\lib\sunrsasign.jar;d:\jd
              k1.3\jre\classes;.\lib\weblogic510sp10boot.jar;.\classes\boot;.\eval\cloudscape\lib\cloudscape.jar;d
              :\jdk1.3\lib\tools.jar;;.\license;.\lib\weblogic510sp10.jar;.\classes;.\lib\weblogicaux.jar;.\myserv
              er\serverclasses;E:\weblogic\myserver\servletclasses;E:\weblogic\myserver\public_html;E:\weblogic\my
              server\classfiles;null, -d, E:\weblogic\myserver\classfiles, E:\weblogic\myserver\classfiles\jsp_ser
              vlet\_sessionlist.java])
              at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:459)
              at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:249)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:366)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
              269)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              waitng for answer.
              Regards
              Abhi
    </a>

              Hi
              i was trying example given in weblogic 5.1 i.e. session list. that uses tagextrainfo
              class to set the attributes in JSP. but it doesn't work.
              Please respond to this error.
              i am attaching error docs error.txt
              On Browser
              Compilation of 'E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java'
              failed:
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:93: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 49:
              <td><%= name %></td>
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:95: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 50:
              <td><%= value %></td>
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:99: cannot resolve
              symbol
              probably occurred due to an error in /SessionList.jsp line 51:
              <td><a href="<%=request.getRequestURI()%>?action=delete&delName=<%=name%>">
              On Server Console
              Mon Oct 08 18:26:06 GMT+05:30 2001:<I> <ServletContext-General> looking for taglib
              uri session.tld a
              s resource /WEB-INF/session.tld in Web Application root:
              Mon Oct 08 18:26:10 GMT+05:30 2001:<I> <ServletContext-General> Generated java
              file: E:\weblogic\mys
              erver\classfiles\jsp_servlet\_sessionlist.java
              Mon Oct 08 18:26:29 GMT+05:30 2001:<E> <ServletContext-General> Compilation of
              E:\weblogic\myserver\
              classfiles\jsp_servlet\_sessionlist.java failed:
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:93: cannot resolve
              symbol
              symbol : variable name
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf( name )); //[ /SessionList.jsp;
              Line: 49]
              ^
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:95: cannot resolve
              symbol
              symbol : variable value
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf( value )); //[ /SessionList.jsp;
              Line: 50]
              ^
              E:\weblogic\myserver\classfiles\jsp_servlet\_sessionlist.java:99: cannot resolve
              symbol
              symbol : variable name
              location: class jsp_servlet._sessionlist
              out.print(weblogic.utils.StringUtils.valueOf(name)); //[ /SessionList.jsp;
              Line: 51]
              ^
              3 errors
              java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[d:/jdk1.3/bin/javac.exe,
              -c
              lasspath, d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\jdk1.3\jre\lib\sunrsasign.jar;d:\jd
              k1.3\jre\classes;.\lib\weblogic510sp10boot.jar;.\classes\boot;.\eval\cloudscape\lib\cloudscape.jar;d
              :\jdk1.3\lib\tools.jar;;.\license;.\lib\weblogic510sp10.jar;.\classes;.\lib\weblogicaux.jar;.\myserv
              er\serverclasses;E:\weblogic\myserver\servletclasses;E:\weblogic\myserver\public_html;E:\weblogic\my
              server\classfiles;null, -d, E:\weblogic\myserver\classfiles, E:\weblogic\myserver\classfiles\jsp_ser
              vlet\_sessionlist.java])
              at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:459)
              at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:249)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:366)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
              269)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              Mon Oct 08 18:26:31 GMT+05:30 2001:<E> <ServletContext-General> Servlet failed
              with Exception
              java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[d:/jdk1.3/bin/javac.exe,
              -c
              lasspath, d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\jdk1.3\jre\lib\sunrsasign.jar;d:\jd
              k1.3\jre\classes;.\lib\weblogic510sp10boot.jar;.\classes\boot;.\eval\cloudscape\lib\cloudscape.jar;d
              :\jdk1.3\lib\tools.jar;;.\license;.\lib\weblogic510sp10.jar;.\classes;.\lib\weblogicaux.jar;.\myserv
              er\serverclasses;E:\weblogic\myserver\servletclasses;E:\weblogic\myserver\public_html;E:\weblogic\my
              server\classfiles;null, -d, E:\weblogic\myserver\classfiles, E:\weblogic\myserver\classfiles\jsp_ser
              vlet\_sessionlist.java])
              at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:459)
              at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:249)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:366)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
              269)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              waitng for answer.
              Regards
              Abhi
    </a>

  • Error during creation of datasource on weblogic 6.1

    I was setting up jdbc datasource/connection pool for cloudscape and MS access database on weblogic 6.1. When i am goingto set target afrom available list to chosen it throws an error saying
    Distributed Management [1 exceptions]
    Upon clicking on message its notshowing any details.
    What should be the problem?

    Did u set the datasource first?

  • Memory leak in weblogic 6.0 sp2 oracle 8.1.7 thin driver

    Hi,
         I have a simple client that opens a database connection, selects from
    a table containing five rows of data (with four columns in each row)
    and then closes all connections. On running this in a loop, I get the
    following error after some time:
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
    <OutOfMemoryError in
    Adapter
    java.lang.OutOfMemoryError
    <<no stack trace available>>
    >
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
    failed
    java.lang.OutOfMemoryError
    I am running with a heap size of 64 Mb. The java command that runs
    the client is:
    java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
    -Djava.naming.f
    actory.initial=weblogic.jndi.WLInitialContextFactory
    -Djava.naming.provider.url=
    t3://garlic:7001 -verbose:gc Test
    The following is the client code that opens the db connection and does
    the select:
    import java.util.*;
    import java.sql.*;
    import javax.naming.*;
    import javax.sql.*;
    public class Test {
    private static final String strQuery = "SELECT * from tblPromotion";
    public static void main(String argv[])
    throws Exception
    String ctxFactory     = System.getProperty
    ("java.naming.factory.initial");
    String providerUrl     = System.getProperty
    ("java.naming.provider.url");
    Properties jndiEnv          = System.getProperties ();
    System.out.println ("ctxFactory : " + ctxFactory);
    System.out.println ("ProviderURL : " + providerUrl);
    Context ctx     = new InitialContext (jndiEnv);
    for (int i=0; i <1000000; i++)
    System.out.println("Running query for the "+i+" time");
    Connection con = null;
    Statement stmnt = null;
    ResultSet rs     = null;
    try
    DataSource ds     = (DataSource) ctx.lookup
    (System.getProperty("eaMDataStore", "jdbc/eaMarket"));
    con = ds.getConnection ();
    stmnt = con.createStatement();
    rs = stmnt.executeQuery(strQuery);
    while (rs.next ())
    //System.out.print(".");
    //System.out.println(".");
    ds = null;
    catch (java.sql.SQLException sqle)
    System.out.println("SQL Exception : "+sqle.getMessage());
    finally
    try {
    rs.close ();
    rs = null;
    //System.out.println("closed result set");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    stmnt.close ();
    stmnt = null;
    //System.out.println("closed statement");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    con.close();
    con = null;
    //System.out.println("closed connection");
    } catch (Exception e) {
    System.out.println("Exception closing connection");
    I am using the Oracle 8.1.7 thin driver. Please let me know if this
    memory leak is a known issue or if its something I am doing.
    thanks,
    rudy

    Repost in JDBC section ... very serious issue but it may be due to Oracle or
    to WL ... does it happen if you test inside WL itself?
    How many iterations does it take to blow? How long? Does changing to a
    different driver (maybe Cloudscape) have the same result?
    Peace,
    Cameron Purdy
    Tangosol Inc.
    << Tangosol Server: How Weblogic applications are customized >>
    << Download now from http://www.tangosol.com/download.jsp >>
    "R.C." <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I have a simple client that opens a database connection, selects from
    a table containing five rows of data (with four columns in each row)
    and then closes all connections. On running this in a loop, I get the
    following error after some time:
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Adapter>
    <OutOfMemoryError in
    Adapter
    java.lang.OutOfMemoryError
    <<no stack trace available>>
    >
    <Nov 28, 2001 5:57:40 PM GMT+06:00> <Error> <Kernel> <ExecuteRequest
    failed
    java.lang.OutOfMemoryError
    I am running with a heap size of 64 Mb. The java command that runs
    the client is:
    java -ms64m -mx64m -cp .:/opt/bea/wlserver6.0/lib/weblogic.jar
    -Djava.naming.f
    actory.initial=weblogic.jndi.WLInitialContextFactory
    -Djava.naming.provider.url=
    t3://garlic:7001 -verbose:gc Test
    The following is the client code that opens the db connection and does
    the select:
    import java.util.*;
    import java.sql.*;
    import javax.naming.*;
    import javax.sql.*;
    public class Test {
    private static final String strQuery = "SELECT * from tblPromotion";
    public static void main(String argv[])
    throws Exception
    String ctxFactory = System.getProperty
    ("java.naming.factory.initial");
    String providerUrl = System.getProperty
    ("java.naming.provider.url");
    Properties jndiEnv = System.getProperties ();
    System.out.println ("ctxFactory : " + ctxFactory);
    System.out.println ("ProviderURL : " + providerUrl);
    Context ctx = new InitialContext (jndiEnv);
    for (int i=0; i <1000000; i++)
    System.out.println("Running query for the "+i+" time");
    Connection con = null;
    Statement stmnt = null;
    ResultSet rs = null;
    try
    DataSource ds = (DataSource) ctx.lookup
    (System.getProperty("eaMDataStore", "jdbc/eaMarket"));
    con = ds.getConnection ();
    stmnt = con.createStatement();
    rs = stmnt.executeQuery(strQuery);
    while (rs.next ())
    //System.out.print(".");
    //System.out.println(".");
    ds = null;
    catch (java.sql.SQLException sqle)
    System.out.println("SQL Exception : "+sqle.getMessage());
    finally
    try {
    rs.close ();
    rs = null;
    //System.out.println("closed result set");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    stmnt.close ();
    stmnt = null;
    //System.out.println("closed statement");
    } catch (Exception e) {
    System.out.println("Exception closing result set");
    try {
    con.close();
    con = null;
    //System.out.println("closed connection");
    } catch (Exception e) {
    System.out.println("Exception closing connection");
    I am using the Oracle 8.1.7 thin driver. Please let me know if this
    memory leak is a known issue or if its something I am doing.
    thanks,
    rudy

Maybe you are looking for