WLS 5.1 and WTE in VA ??

Hi,
anyone managed to get the weblogic integrator for Visual Age and the
websphere test environment up and running in the same workspace ?
Thanks
Anders Mathisen

I don't think this is possible because VAJ does not allow multiple
packages with the same name in the same workspace...
Anders Mathisen wrote:
Hi,
anyone managed to get the weblogic integrator for Visual Age and the
websphere test environment up and running in the same workspace ?
Thanks
Anders Mathisen

Similar Messages

  • Cluster with WLS 5.1 and WLS 8.1 servers?

    hi all,
    we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
    have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
    I'm now thinking of is: is it possible to run a WLS cluster that has 2
    Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
    Reason of thinking so, is that want to have the most failsafe configration
    as possible during our upgrade.
    I searched the BEA docs, but didn't find anything.
    any help would be fine.
    thanks
    Alexander

    You can have it but not for fail-safe configuration.
    It is not possible to have clusters with different
    WLS versions especially between 5.1 & 8.1
    Kumar
    Alexander von Alkier wrote:
    hi all,
    we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
    have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
    I'm now thinking of is: is it possible to run a WLS cluster that has 2
    Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
    Reason of thinking so, is that want to have the most failsafe configration
    as possible during our upgrade.
    I searched the BEA docs, but didn't find anything.
    any help would be fine.
    thanks
    Alexander

  • ConnectionPool problems with WLS 7.0 and Oracle 9.2

    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
    application on the productive system (and only there) we constantly encounter
    a whole set of SQLExceptions which have all in common that the Connection from
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSet
    - Connection has already been closed
    - Closed Statement
    - Transaction is no longer active - status committing
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()
    There are no special Statements which create these errors. They are spread at
    random across practically every query the application creates, and the same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSets are
    closed immediately after use. As an example, I attached a code snippet and a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrent usern,
    since in the approval tests on an almost identical test system these errors never
    occurred.
    I also followed the advice from Oracle and installed the latest Oracle JDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in the application
    classpath (via a reference in the Manifest file of the application jar), not in
    the system classpath? There has never been a problem with that, but in a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script creates for the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath? If
    it is possible, why is it necessary?
    Best regards,
    Andreas Zehrt
    [CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

    Andreas Zehrt wrote:
    Hi Joe,
    Your hint that there is a threading problem was right:
    On further investigation of the code I found out that the class that passes the
    Connection to the DAO not only stores it as a member at some point (which is not
    a good idea anyway) but is also a singleton - then, of course, it's no surprise
    that the Connection gets invalid in a incalculable way when concurrent threads
    share it.
    The singleton instantiation was not so obvious because the way of instantiation
    is controlled by a configuration parameter that can be overridden at different
    levels.
    I changed it and the productive logfiles indicate that the SQLExceptions related
    to that class have disappeared.I am happy to have helped.
    So, thanks a lot for the advice.
    But I am still wondering why this code has worked for so long a time with WLS
    5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
    approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
    it was multi-user environment.Mo idea.
    I still believe that there is a difference between WLS 5.1 and 7.0 in the way
    it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
    a little more explicit about those changes and possible version incompatabilities
    beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
    effect in this case, I will certainly do what I can to see that our documentation
    is explicit about changes.
    Joe
    Best regards, Andreas
    Joe Weinstein <[email protected]> wrote:
    Hi Andreas.
    Andreas Zehrt wrote:
    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
    application on the productive system (and only there) we constantlyencounter
    a whole set of SQLExceptions which have all in common that the Connectionfrom
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSetThat is typically if the statement that created it is either re-executed
    or closed.
    - Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
    would show
    where it was originally closed.
    - Closed Statementsame as above.
    - Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
    datasource,
    and then later trying to use it after the transaction which it was associated
    with,
    is finished.
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
    There are no special Statements which create these errors. They arespread at
    random across practically every query the application creates, andthe same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSetsare
    closed immediately after use. As an example, I attached a code snippetand a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrentusern,
    since in the approval tests on an almost identical test system theseerrors never
    occurred.
    I also followed the advice from Oracle and installed the latest OracleJDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in theapplication
    classpath (via a reference in the Manifest file of the applicationjar), not in
    the system classpath? There has never been a problem with that, butin a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script createsfor the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath?If
    it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
    We also ship
    an oracle thin driver, which becomes obsolete soon...
    I am concerned that your code creates pool connections to be used later.
    The problems
    can arise if more than one thread ever gets the same connection, or if
    the connection
    is used in the same thread, spanning transactions. It does also seem
    that there may
    be a threading issue, because if two threads each call the code to create
    a connection,
    and two connections are made, but one over-writes the other, the two
    threads can
    end up using the same connection, and closing it. The over-written one
    never gets closed,
    resulting in that leak message you got...
    Joe
    The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
    several classes in the business layer, but not used, until the DAOtakes it to make the query.
    So, the Connection is closed where it was opened, not in the DAO class.
    public class ConcernDAOImpl extends BaseDAO {
         public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
    throws DataAccessException, ConstraintException, ComaParseException{>
    sqlMessage.append(")");
    String sqlStmt = sqlMessage.toString();
    PreparedStatement pstmt = null;
    ResultSet rs = null;
    try {
    pstmt = conn.prepareStatement(sqlStmt);
    rs = pstmt.executeQuery();
    while (rs != null && rs.next()) {
    final Concern concern =
    new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
    concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
    return concerns;
    } catch (SQLException sqle) {
    // Wrapps real SQL exception
    String[] message = new String[]{sqle.getMessage(), sqlStmt};
    throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
    sqle);
    } finally {
    closeAll(rs, pstmt);
    _logger.exitDebug(method);
    Here, the Connection is acquired and finally closed
    public class ComaServiceProviderClassicImpl {
         public void updateComplaint(
    final Request updateRequest,
    final ResponseSingleElement response,
    final Principal principal)
    throws SystemException {
    try {
    logger.info("updateComplaint", "store incident");
    // store the incident in the database
    incidentManager.storeIncident(getConnection(), updateIncident);
    // reload the incident from Cache and / or the databaseto get the ContactReferences.
    Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
    getConnection(), updateIncident.getOID());
    } catch (RemoteException rex) {
    // remote exceptions
    rollbackIfNecessary();
    CoreUtils.unwrapRemoteException(rex, logger);
    } catch (SystemException e) {
    // all other exceptions --> rollback if necessary and rethrow
    rollbackIfNecessary();
    throw e;
    } finally {
    removeConnection();
    logger.exitDebug("updateComplaint");
    This is the resulting StackTrace:
    sql exception: [Closed Statement: next] - sql statement: [select *
         at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
         at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
         at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    ####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
    was detected. A Connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed
    by the garbage collector and returned to the connection pool. The following
    stack trace at create shows where the leaked connection was created.
    Stack trace at connection create:
         at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
         at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
         at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

  • WLS 8.1SP2 and AIX 5.1.0.0

    After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
    I am still unable to bring up my server. The following error occurs:
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://[hostname]:[port]/console *
    <May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
    WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
    <May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
    <This server is being started as the administration server.>
    <May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
    Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
    domainconfiguration from configuration repository at
    /users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
    <May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
    serverlog file
    /users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
    opened. All server side log events will be written to this file.>
    <May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
    initializing using security realm myrealm.>
    <May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
    <Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
    JVMDG217: Dump Handler is Processing a Signal - Please Wait.
    JVMDG303: JVM Requesting Java core file
    JVMDG304: Java core file written to
    /users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
    t
    JVMDG215: Dump Handler has Processed Exception Signal 11.
    System Information for dixie
    MODEL Bull ESCALA T (e8ED)
    CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
    MEM 2304 MB real memory
    FIRM 03.03.09
    OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
    KERN System currently booted on 32 bits kernel
    Attached is the Java core file
    Any ideas?
    Eric
    [javacore37624.1083785465.txt]

    BEA currently supports AIX 5.1 ML-4. Your configuration is ML-5.
    Eric Hardesty wrote:
    After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
    I am still unable to bring up my server. The following error occurs:
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://[hostname]:[port]/console *
    <May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
    WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
    <May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
    <This server is being started as the administration server.>
    <May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
    Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
    domainconfiguration from configuration repository at
    /users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
    <May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
    serverlog file
    /users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
    opened. All server side log events will be written to this file.>
    <May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
    initializing using security realm myrealm.>
    <May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
    <Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
    JVMDG217: Dump Handler is Processing a Signal - Please Wait.
    JVMDG303: JVM Requesting Java core file
    JVMDG304: Java core file written to
    /users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
    t
    JVMDG215: Dump Handler has Processed Exception Signal 11.
    System Information for dixie
    MODEL Bull ESCALA T (e8ED)
    CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
    MEM 2304 MB real memory
    FIRM 03.03.09
    OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
    KERN System currently booted on 32 bits kernel
    Attached is the Java core file
    Any ideas?
    Eric
    NULL ------------------------------------------------------------------------
    0SECTION TITLE subcomponent dump routine
    NULL ===============================
    1TISIGINFO signal 11 received
    1TIDATETIME Date: 2004/05/05 at 12:31:05
    1TIFILENAME Javacore filename: /users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.txt
    NULL ------------------------------------------------------------------------
    0SECTION XHPI subcomponent dump routine
    NULL ==============================
    1XHTIME Wed May 5 12:31:05 2004
    1XHSIGRECV SIGSEGV received at 0xd3a96f54 in /usr/java14/jre/bin/classic/libjvm.a. Processing terminated.
    1XHFULLVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
    NULL
    1XHCURRENTTHD Current Thread Details
    NULL ----------------------
    2XHCURRSYSTHD "ListenThread.Default" sys_thread_t:0x41C0F228
    3XHNATIVESTACK Native Stack
    NULL ------------
    3XHSTACKLINE at 0xD46194CC in Java_weblogic_socket_PosixSocketMuxer_initNative
    3XHSTACKLINE at 0xD3A96F54 in mmipInvoke_V_V
    3XHSTACKLINE at 0xD3A909B0 in mmipInvokeLazyJniMethod
    3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
    3XHSTACKLINE at 0xD3A54BBC in xeRunJvmMethod
    3XHSTACKLINE at 0xD3A47628 in JVM_NewInstanceFromConstructor
    3XHSTACKLINE at 0xD3C5658C in Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0
    3XHSTACKLINE at 0xD3A9641C in mmipInvoke_OO_O
    3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
    3XHSTACKLINE at 0xD3BBCDF8 in mmijExecuteJavaFromJIT
    3XHSTACKLINE at 0xD3C8AC90 in jit_init_memory_locks_md
    NULL
    1XHOPENV Operating Environment
    NULL ---------------------
    2XHHOSTNAME Host : dixie.gpv.az05.bull.com:141.112.17.150
    2XHOSLEVEL OS Level : AIX 5.1.0.0
    2XHCPUS Processors -
    3XHCPUARCH Architecture : POWER_PC (impl: POWER_604, ver: PV_604)
    3XHNUMCPUS How Many : 4
    3XHCPUSENABLED Enabled : 4
    NULL
    1XHUSERLIMITS User Limits (in bytes except for NOFILE and NPROC) -
    NULL -----------
    2XHUSERLIMIT RLIMIT_FSIZE : infinity
    2XHUSERLIMIT RLIMIT_DATA : 2147483645
    2XHUSERLIMIT RLIMIT_STACK : 33554432
    2XHUSERLIMIT RLIMIT_CORE : 1073741312
    2XHUSERLIMIT RLIMIT_NOFILE : infinity
    2XHLIMIT NPROC(max) : 4000
    NULL
    1XHPAGESPACES Page Space (in blocks) -
    NULL ----------
    2XHPAGESPACE /dev/hd6: size=200704, free=199709
    2XHPAGESPACE /dev/paging00: size=196608, free=196495
    2XHPAGESPACE /dev/paging01: size=196608, free=196495
    NULL
    1XHSIGHANDLERS JVM Signal Handlers
    NULL -------------------
    2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
    2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGPIPE : ignored
    2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
    NULL
    1XHSIGHANDLERS Chained Signal Handlers
    NULL -----------------------
    2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
    2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
    2XHSIGHANDLER SIGPIPE : ignored
    2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
    NULL
    1XHENVVARS Environment Variables
    NULL ---------------------
    2XHENVVAR _=/usr/java14/bin/java
    2XHENVVAR JAVA_VENDOR=IBM
    2XHENVVAR LANG=en_US
    2XHENVVAR TMOUT2=43200
    2XHENVVAR PRODUCTION_MODE=
    2XHENVVAR LOGIN=interop8
    2XHENVVAR CLASSPATHSEP=:
    2XHENVVAR PAGER=more
    2XHENVVAR POINTBASE_HOME=/users/interop8/bea/weblogic81/common/eval/pointbase
    2XHENVVAR PATH=/users/interop8/bea/weblogic81/server/bin:/usr/java14/jre/bin:/usr/java14/bin:/users/interop8/GCOSInterop/dsad/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin::/app/oracle/product/8.1.7/bin:/usr/local/bin:/usr/lbin:/users/interop8/jte/bin
    2XHENVVAR RES_RETRY=1
    2XHENVVAR JTE_BASE=/users/interop8/jte
    2XHENVVAR JAVA_VM=
    2XHENVVAR LC__FASTMSG=true
    2XHENVVAR POINTBASE_CLASSPATH=:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar
    2XHENVVAR CGI_DIRECTORY=/var/docsearch/cgi-bin
    2XHENVVAR EDITOR=vi
    2XHENVVAR EXINIT=set tabstop=4
    2XHENVVAR HISTFILE=/users/interop8/.sh_history
    2XHENVVAR CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
    2XHENVVAR LOGNAME=interop8
    2XHENVVAR RES_TIMEOUT=2
    2XHENVVAR MAIL=/usr/spool/mail/interop8
    2XHENVVAR ETC_PROFILE=1
    2XHENVVAR POINTBASE_TOOLS=/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbtools44.jar
    2XHENVVAR LOCPATH=/usr/lib/nls/loc
    2XHENVVAR ORACLE_SID=demo
    2XHENVVAR PS1=[dixie] (interop8).${PWD#${HOME}}>
    2XHENVVAR PATHSEP=:
    2XHENVVAR USER=interop8
    2XHENVVAR DOCUMENT_SERVER_MACHINE_NAME=localhost
    2XHENVVAR AUTHSTATE=compat
    2XHENVVAR BEA_HOME=/users/interop8/bea
    2XHENVVAR DEFAULT_BROWSER=netscape
    2XHENVVAR DISPLAY=harp.gpv.az05.bull.com:0
    2XHENVVAR SHELL=/bin/ksh
    2XHENVVAR ODMDIR=/etc/objrepos
    2XHENVVAR JAVA_HOME=/usr/java14
    2XHENVVAR DOCUMENT_SERVER_PORT=49213
    2XHENVVAR TMOUT=43200
    2XHENVVAR HOME=/users/interop8
    2XHENVVAR MEM_ARGS=-Xms32m -Xmx200m
    2XHENVVAR WEBLOGIC_CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar
    2XHENVVAR TERM=vt220
    2XHENVVAR MAILMSG=[YOU HAVE NEW MAIL]
    2XHENVVAR ORACLE_HOME=/app/oracle/product/8.1.7
    2XHENVVAR ITECONFIGSRV=/etc/IMNSearch
    2XHENVVAR PWD=/users/interop8/bea/user_projects/domain/hooxsgb
    2XHENVVAR DOCUMENT_DIRECTORY=/usr/docsearch/html
    2XHENVVAR TZ=MST7
    2XHENVVAR ITECONFIGCL=/etc/IMNSearch/clients
    2XHENVVAR WL_HOME=/users/interop8/bea/weblogic81
    2XHENVVAR ITE_DOC_SEARCH_INSTANCE=search
    2XHENVVAR A__z=! TMOUT2=! LOGNAME=! ETC_PROFILE="*TMOUT
    2XHENVVAR _IBM_JAVA_PIPE_37624=
    2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_OLD_VALUE=
    2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_NEW_VALUE=S
    2XHENVVAR AIXTHREAD_SCOPE=S
    2XHENVVAR IBM_JVM_CHANGED_ENVVARS_37624=AIXTHREAD_SCOPE,LDR_CNTRL
    2XHENVVAR IBM_JVM_LDR_CNTRL_OLD_VALUE=
    2XHENVVAR IBM_JVM_LDR_CNTRL_NEW_VALUE=MAXDATA=0x80000000
    2XHENVVAR LDR_CNTRL=MAXDATA=0x80000000
    2XHENVVAR LIBPATH=/usr/java14/jre/bin:/usr/java14/jre/bin/classic:/usr/java14/jre/bin:/app/oracle/product/8.1.7}/lib:/users/interop8/bea/weblogic81/server/lib/aix
    2XHENVVAR NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/opt/Xprint/MSG/%l/%N:/opt/Xprint/mercator/MSG/%l/%N:/var/spool/Xprint/config/MSG/%l/%N:/var/spool/Xprint/config/mercator/MSG/%l/%N
    2XHENVVAR _IBM_ENV_INITIAL_37624=807444056
    2XHENVVAR IBM_JAVA_COMMAND_LINE=/usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava..security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
    NULL
    1XHLOADEDLIBS Loaded Libraries (sizes in bytes)
    NULL ---------------------------------
    2XHLIBNAME /users/interop8/bea/weblogic81/server/lib/aix/libmuxer.so
    3XHLIBSIZE filesize : 20757
    3XHLIBSTART text start : 0xD4618000
    3XHLIBLDSIZE text size : 0x282E
    3XHLIBLDORG data start : 0x41E97CF4
    3XHLIBLDDATASZ data size : 0x2AC
    2XHLIBNAME /usr/java14/jre/bin/libnio.a
    3XHLIBSIZE filesize : 61140
    3XHLIBSTART text start : 0xD460F000
    3XHLIBLDSIZE text size : 0x8925
    3XHLIBLDORG data start : 0x408A5598
    3XHLIBLDDATASZ data size : 0x50C
    2XHLIBNAME /usr/java14/jre/bin/libnet.a
    3XHLIBSIZE filesize : 122155
    3XHLIBSTART text start : 0xD45F9000
    3XHLIBLDSIZE text size : 0x1437A
    3XHLIBLDORG data start : 0x3F592990
    3XHLIBLDDATASZ data size : 0x820
    2XHLIBNAME /usr/java14/jre/bin/libjitc.a
    3XHLIBSIZE filesize : 2760315
    3XHLIBSTART text start : 0xD3C7D000
    3XHLIBLDSIZE text size : 0x2330F6
    3XHLIBLDORG data start : 0x3E055F40
    3XHLIBLDDATASZ data size : 0x1A8A4
    2XHLIBNAME /usr/lib/libi18n.a
    3XHLIBSIZE filesize : 148825
    3XHLIBSTART text start : 0xD007A100
    3XHLIBLDSIZE text size : 0xA1AE
    3XHLIBLDORG data start : 0x3DFF2A18
    3XHLIBLDDATASZ data size : 0x1290
    2XHLIBNAME /usr/lib/nls/loc/en_US
    3XHLIBSIZE filesize : 14342
    3XHLIBSTART text start : 0xD0074000
    3XHLIBLDSIZE text size : 0x2D71
    3XHLIBLDORG data start : 0xD0077130
    3XHLIBLDDATASZ data size : 0x2324
    2XHLIBNAME /usr/java14/jre/bin/libzip.a
    3XHLIBSIZE filesize : 109272
    3XHLIBSTART text start : 0xD3C69000
    3XHLIBLDSIZE text size : 0x1349A
    3XHLIBLDORG data start : 0x3D80F398
    3XHLIBLDDATASZ data size : 0x1908
    2XHLIBNAME /usr/java14/jre/bin/classic/libcore.a
    3XHLIBSIZE filesize : 172361
    3XHLIBSTART text start : 0xD3C4E000
    3XHLIBLDSIZE text size : 0x1AE66
    3XHLIBLDORG data start : 0x3D801610
    3XHLIBLDDATASZ data size : 0xD934
    2XHLIBNAME /usr/java14/jre/bin/libhpi.a
    3XHLIBSIZE filesize : 159668
    3XHLIBSTART text start : 0xD3C36000
    3XHLIBLDSIZE text size : 0x17708
    3XHLIBLDORG data start : 0x3025DCC8
    3XHLIBLDDATASZ data size : 0x1420
    2XHLIBNAME /usr/java14/jre/bin/libxhpi.a
    3XHLIBSIZE filesize : 44366
    3XHLIBSTART text start : 0xD3C2F000
    3XHLIBLDSIZE text size : 0x6578
    3XHLIBLDORG data start : 0x3024E058
    3XHLIBLDDATASZ data size : 0xE51C
    2XHLIBNAME /usr/lib/libdl.a
    3XHLIBSIZE filesize : 5248
    3XHLIBSTART text start : 0xD070D0F8
    3XHLIBLDSIZE text size : 0x1E0
    3XHLIBLDORG data start : 0x3024D0F8
    3XHLIBLDDATASZ data size : 0x0
    2XHLIBNAME /usr/java14/jre/bin/libjsig.a
    3XHLIBSIZE filesize : 13751
    3XHLIBSTART text start : 0xD3C2D000
    3XHLIBLDSIZE text size : 0x1B6E
    3XHLIBLDORG data start : 0x3024C2F8
    3XHLIBLDDATASZ data size : 0x1D0
    2XHLIBNAME /usr/java14/jre/bin/libjava.a
    3XHLIBSIZE filesize : 197639
    3XHLIBSTART text start : 0xD3C10000
    3XHLIBLDSIZE text size : 0x1CE78
    3XHLIBLDORG data start : 0x30239690
    3XHLIBLDDATASZ data size : 0x132C
    2XHLIBNAME /usr/java14/jre/bin/classic/libjvm.a
    3XHLIBSIZE filesize : 2698157
    3XHLIBSTART text start : 0xD3A28000
    3XHLIBLDSIZE text size : 0x1E71F8
    3XHLIBLDORG data start : 0x302111E0
    3XHLIBLDDATASZ data size : 0x27BE4
    2XHLIBNAME /usr/lib/libiconv.a
    3XHLIBSIZE filesize : 377974
    3XHLIBSTART text start : 0xD0085100
    3XHLIBLDSIZE text size : 0x1403A
    3XHLIBLDORG data start : 0xF0317ED0
    3XHLIBLDDATASZ data size : 0xA544
    2XHLIBNAME /usr/lib/libbsd.a
    3XHLIBSIZE filesize : 63178
    3XHLIBSTART text start : 0xD01504C0
    3XHLIBLDSIZE text size : 0x8183
    3XHLIBLDORG data start : 0xF0169FB0
    3XHLIBLDDATASZ data size : 0x1350
    2XHLIBNAME /usr/lib/libpthreads.a
    3XHLIBSIZE filesize : 912571
    3XHLIBSTART text start : 0xD0047000
    3XHLIBLDSIZE text size : 0x2B5BD
    3XHLIBLDORG data start : 0xF0139000
    3XHLIBLDDATASZ data size : 0x5020
    2XHLIBNAME /usr/lib/libpthreads.a
    3XHLIBSIZE filesize : 912571
    3XHLIBSTART text start : 0xD0043000
    3XHLIBLDSIZE text size : 0x38B1
    3XHLIBLDORG data start : 0xF00D6000
    3XHLIBLDDATASZ data size : 0x62318
    2XHLIBNAME /usr/lib/libC.a
    3XHLIBSIZE filesize : 6961880
    3XHLIBSTART text start : 0xD0521560
    3XHLIBLDSIZE text size : 0x1F983
    3XHLIBLDORG data start : 0xF01E9560
    3XHLIBLDDATASZ data size : 0x6578
    2XHLIBNAME /usr/lib/libC.a
    3XHLIBSIZE filesize : 6961880
    3XHLIBSTART text start : 0xD0507E20
    3XHLIBLDSIZE text size : 0x1846B
    3XHLIBLDORG data start : 0xF01DFE20
    3XHLIBLDDATASZ data size : 0x8511
    2XHLIBNAME /usr/lib/libC.a
    3XHLIBSIZE filesize : 6961880
    3XHLIBSTART text start : 0xD04E7100
    3XHLIBLDSIZE text size : 0x1F75A
    3XHLIBLDORG data start : 0xF01DB700
    3XHLIBLDDATASZ data size : 0x3019
    2XHLIBNAME /usr/lib/libcrypt.a
    3XHLIBSIZE filesize : 11059
    3XHLIBSTART text start : 0xD00730F8
    3XHLIBLDSIZE text size : 0x86E
    3XHLIBLDORG data start : 0xF00D5530
    3XHLIBLDDATASZ data size : 0x128
    2XHLIBNAME /usr/lib/libc.a
    3XHLIBSIZE filesize : 6806102
    3XHLIBSTART text start : 0xD01D5640
    3XHLIBLDSIZE text size : 0x1FDB9F
    3XHLIBLDORG data start : 0xF0042520
    3XHLIBLDDATASZ data size : 0x91B58
    NULL
    NULL ------------------------------------------------------------------------
    0SECTION CI subcomponent dump routine
    NULL ============================
    1CIJAVAVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
    1CIRUNNINGAS Running as a standalone JVM
    1CICMDLINE /usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
    1CIJAVAHOMEDIR Java Home Dir: /usr/java14/jre
    1CIJAVADLLDIR Java DLL Dir: /usr/java14/jre/bin
    1CISYSCP Sys Classpath: /usr/java14/jre/lib/core.jar:/usr/java14/jre/lib/graphics.jar:/usr/java14/jre/lib/security.jar:/usr/java14/jre/lib/server.jar:/usr/java14/jre/lib/xml.jar:/usr/java14/jre/lib/charsets.jar:/usr/java14/jre/classes
    1CIUSERARGS UserArgs:
    2CIUSERARG vfprintf 0x30000B94
    2CIUSERARG -Xms32m
    2CIUSERARG -Xmx200m
    2CIUSERARG -Dweblogic.Name=myserver
    2CIUSERARG -Dweblogic.ProductionModeEnabled=
    2CIUSERARG -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy
    2CIUSERARG -Dinvokedviajava
    2CIUSERARG -Djava.class.path=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
    2CIUSERARG vfprintf
    NULL
    1CIJVMMI JVM Monitoring Interface (JVMMI)
    NULL ------------------------
    2CIJVMMIOFF No events are enabled.
    NULL
    NULL ------------------------------------------------------------------------
    0SECTION DC subcomponent dump routine
    NULL ============================
    1DCHEADEREYE Header eye catcher DCST
    1DCHEADERLEN Header length 24
    1DCHEADERVER Header version 1
    1DCHEADERMOD Header modification 0
    1DCINTERFACE DC Interface at 0x3022270C with 15 entries
    2DCINTERFACE 1 - dcCString2JavaString 0x3021EA7C
    2DCINTERFACE 2 - dcInt642CString 0x3021EA88
    2DCINTERFACE 3 - dcJavaString2NewCString 0x3021EA94
    2DCINTERFACE 4 - dcJavaString2CString 0x3021EAA0
    2DCINTERFACE 5 - dcJavaString2NewPlatformString 0x3021EAAC
    2DCINTERFACE 6 - dcJavaString2UTF 0x3021EAB8
    2DCINTERFACE 7 - dcPlatformString2JavaString 0x3021EAD0
    2DCINTERFACE 8 - dcUnicode2UTF 0x3021EADC
    2DCINTERFACE 9 - dcUnicode2UTFLength 0x3021EAE8
    2DCINTERFACE 10 - dcUTF2JavaString 0x3021EAF4
    2DCINTERFACE 11 - dcUTFClassName2JavaString 0x3021EB00
    2DCINTERFACE 12 - dcJavaString2ClassName 0x3021EAC4
    2DCINTERFACE 13 - dcUTF2UnicodeNext 0x3021EB0C
    2DCINTERFACE 14 - dcVerifyUTF8 0x3021EB18
    2DCINTERFACE 15 - dcDumpRoutine 0x3021EB24
    1DCARRAYINFO Array info at 0x302131B8 with 16 entries
    2DCARRAYINFO 1 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 2 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 3 - index 2 signature L name class[] factor 4
    2DCARRAYINFO 4 - index 0 signature 0 name N/A factor 0
    2DCARRAYINFO 5 - index 4 signature Z name bool[] factor 1
    2DCARRAYINFO 6 - index 5 signature C name char[] factor 2
    2DCARRAYINFO 7 - index 6 signature F name float[] factor 4
    2DCARRAYINFO 8 - index 7 signature D name double[] factor 8
    2DCARRAYINFO 9 - index 8 signature B name byte[] factor 1
    2DCARRAYINFO 10 - index 9 signature S name short[] factor 2
    2DCARRAYINFO 11 - index 10 signature I name int[] factor 4
    2DCARRAYINFO 12 - index 11 signature J name long[] factor 8
    2DCARRAYINFO 13 - index 0 signature 0 name uint[] factor 0
    2DCARRAYINFO 14 - index 0 signature 0 name uint1[] factor 0
    2DCARRAYINFO 15 - index 0 signature 0 name uint2[] factor 0
    2DCARRAYINFO 16 - index 0 signature 0 name uint3[] factor 0
    NULL ------------------------------------------------------------------------
    0SECTION DG subcomponent dump routine
    NULL ============================
    1DGTRCENABLED Trace enabled: No
    1DGJDUMPBUFF Javadump buffer size (allocated): 2621440
    NULL ------------------------------------------------------------------------
    0SECTION ST subcomponent dump routine
    NULL ============================
    1STGCMODES Resettable GC: No
    1STGCMODES Concurrent GC: No
    1STCURHBASE Current Heap Base: 302801fc
    1STCURHLIM Current Heap Limit: 3281fbfc
    1STMWHBASE Middleware Heap Base: 302801fc
    1STMWHLIM Middleware Heap Limit: 3281fbfc
    1STGCHELPERS Number of GC Helper Threads: 3
    1STJVMOPTS -Xconcurrentlevel: 0
    1STJVMOPTS -Xconcurrentbackground: 0
    1STGCCTR GC Counter: 7
    1STAFCTR AF Counter: 7
    1STHEAPFREE Bytes of Heap Space Free: 80db00
    1STHEAPALLOC Bytes of Heap Space Allocated: 259fa00
    1STSMBASE SM Base: 0
    1STSMEND SM End: 0
    1STPAMSTART PAM Start: 0
    1STPAMEND PAM End: 0
    1STCOMACTION Compact Action: 0
    NULL ------------------------------------------------------------------------
    0SECTION XE subcomponent dump routine
    NULL ============================
    1XETHRESHOLD MMI threshold for java methods is set to 1250
    1XEJITINIT JIT is initialized
    1XEJVMPIOFF JVMPI is not activated
    1XEJNITHRESH MMI threshold for JNI methods is set to 0
    1XETRCHIS Trace history length is set to 4
    1XEJITDUMP JIT dump routine is not yet implemented.
    NULL ------------------------------------------------------------------------
    0SECTION LK subcomponent dump routine
    NULL ============================
    NULL
    1LKPOOLINFO Monitor pool info:
    2LKPOOLINIT Initial monitor count: 32
    2LKPOOLEXPNUM Minimum number of free monitors before expansion: 5
    2LKPOOLEXPBY Pool will next be expanded by: 24
    2LKPOOLTOTAL Current total number of monitors: 48
    2LKPOOLFREE Current number of free monitors: 9
    NULL
    1LKMONPOOLDUMP Monitor Pool Dump (flat & inflated object-monitors):
    2LKMONINUSE sys_mon_t:0x3020EE28 infl_mon_t: 0x3020E918:
    3LKMONOBJECT java.lang.ref.Reference$Lock@303017F0/303017F8: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "Reference Handler" (0x3D9C6A28)
    2LKMONINUSE sys_mon_t:0x3020EED8 infl_mon_t: 0x3020E940:
    3LKMONOBJECT java.lang.ref.ReferenceQueue$Lock@30301528/30301530: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "Finalizer" (0x3DA50CA8)
    2LKMONINUSE sys_mon_t:0x3020EF88 infl_mon_t: 0x3020E968:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9830/302E9838: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" (0x3EDB86A8)
    2LKMONINUSE sys_mon_t:0x3020F038 infl_mon_t: 0x3020E990:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9798/302E97A0: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" (0x3EDB8D28)
    2LKMONINUSE sys_mon_t:0x3020F0E8 infl_mon_t: 0x3020E9B8:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9700/302E9708: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.Default'" (0x3EDC2528)
    2LKMONINUSE sys_mon_t:0x3020F198 infl_mon_t: 0x3020E9E0:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9668/302E9670: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" (0x3EDD1EA8)
    2LKMONINUSE sys_mon_t:0x3020F248 infl_mon_t: 0x3020EA08:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E95D0/302E95D8: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '4' for queue: 'weblogic.kernel.Default'" (0x3EDD4528)
    2LKMONINUSE sys_mon_t:0x3020F2F8 infl_mon_t: 0x3020EA30:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9538/302E9540: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '5' for queue: 'weblogic.kernel.Default'" (0x3EDD98A8)
    2LKMONINUSE sys_mon_t:0x3020F3A8 infl_mon_t: 0x3020EA58:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E94A0/302E94A8: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" (0x3EDDCF28)
    2LKMONINUSE sys_mon_t:0x3020F458 infl_mon_t: 0x3020EA80:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9408/302E9410: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '7' for queue: 'weblogic.kernel.Default'" (0x3EDE0528)
    2LKMONINUSE sys_mon_t:0x3020F508 infl_mon_t: 0x3020EAA8:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9370/302E9378: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '8' for queue: 'weblogic.kernel.Default'" (0x3EDE2BA8)
    2LKMONINUSE sys_mon_t:0x3020F5B8 infl_mon_t: 0x3020EAD0:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E92D8/302E92E0: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" (0x3EDE8428)
    2LKMONINUSE sys_mon_t:0x3020F668 infl_mon_t: 0x3020EAF8:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9240/302E9248: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" (0x3EDE8A28)
    2LKMONINUSE sys_mon_t:0x3020F718 infl_mon_t: 0x3020EB20:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E91A8/302E91B0: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" (0x3EDF5E28)
    2LKMONINUSE sys_mon_t:0x3020F7C8 infl_mon_t: 0x3020EB48:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9110/302E9118: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '12' for queue: 'weblogic.kernel.Default'" (0x3EDF94A8)
    2LKMONINUSE sys_mon_t:0x3020F878 infl_mon_t: 0x3020EB70:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9078/302E9080: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '13' for queue: 'weblogic.kernel.Default'" (0x3EDFCAA8)
    2LKMONINUSE sys_mon_t:0x3020F928 infl_mon_t: 0x3020EB98:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8FE0/302E8FE8: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" (0x3EE000A8)
    2LKMONINUSE sys_mon_t:0x3020F9D8 infl_mon_t: 0x3020EBC0:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8F48/302E8F50: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.System'" (0x3EE03728)
    2LKMONINUSE sys_mon_t:0x3020FA88 infl_mon_t: 0x3020EBE8:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8EB0/302E8EB8: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.System'" (0x3EE06D28)
    2LKMONINUSE sys_mon_t:0x3020FB38 infl_mon_t: 0x3020EC10:
    3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8E18/302E8E20: <unowned>
    3LKNOTIFYQ Waiting to be notified:
    3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.System'" (0x3EE0A328)
    2LKMONINUSE sys_mon_t:0x3020FBE8 infl_mon_t: 0x3020EC38:
    3LKMON

  • Getting WLS host url and port number

    Hello Experts,
    I need to forward an authenticated request to JAAS LoginModule. How can I get wls host name and port numbe in the LoginModule?
    Thank you in advance,
    Thanks for reading my post

    Hi friends.
    I have used the last post, but it is not working.
    Mat be the API had changed.
    What class or interface could give me this data in web dynpro component?
    Too, I'm using the SAP NetWeaver Developer Studio
    Version: 2.0.16
    Build id: 200602130353
    Thank you.
    Manuel Loayza
    Living La Vida JAVA
    Edited by: Manuel  Loayza Gahona on Jul 23, 2008 6:54 PM

  • Oracle WebLogic Server (WLS), Time Zones, and DayLight Saving Time (DST) Changes

    Hello,
    We are approaching this time of the year again...
    I would like to redirect you to the Support Note 1370083.1 "Oracle WebLogic Server (WLS), Time Zones, and DayLight Saving Time (DST) Changes"
    This note lists what is to be expected from WebLogic Server regarding this time change period, in terms of behavior, both for the engine and the applications deployed onto WLS.
    Regards,
    Patrick.

    Probably this:
    http://www.jdocs.com/castor/0.9.5.3/api/org/exolab/castor/xml/handlers/DateFieldHandler.html

  • PostgreSQL 8.2, WLS 9.2 and XA Transactions

    Hi all,
    I've got an application that's working great with WLS 8.1sp5 and PostgreSQL 8.2, utilizing XA transactions.
    I'm in the process of upgrading to WLS 9.2, and have ran into the issue that WLS seems to be convinced that Postgresql does not support XA transactions.
    When defining the datasource in the console, if I choose Postgresql as the database type, it then says "You have selected non-XA JDBC driver to create database connection in your new data source." and it then only gives me the options of "emulate 2pc", "one phase commit", and "logging last resource".
    So, since the configuration console seems to be retarded in its knowledge, I thought I'd beat it by going ahead and defining the datasource, then tweak the resulting config file by hand, such that reads:
    <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
    instead of:
    <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
    Restarting the server, it accepts the change and all appears OK. But when I use my application I run into this:
    Caused by: java.sql.SQLException: Connection has already been created in this tx context for pool named DS_1. Illegal attempt to create connection from another pool: DS_2
    ...I do indeed have a few different datasources - all using postgres, but logging into different schemas.
    What gives? Why can I use PostgreSQL + WLS 8.1 + XA transactions but not PostsgresQL + WLS 9.2.1 + XA ?
    Thanks!

    I seem to have resolved this issue, though I'm not happy with the work-around that I've come up with.
    First off, as far as I can tell, it's impossible to create the datasource configuration via the console. If I choose PostgreSQL or Postgres and the database type, the configurator excludes XA transaction support as an option. If I choose "other" as the database type (thinking that I'd then specify all the specifics of PostgreSQL directly), it also excludes XA transaction support as an option.
    So, as far as I can tell, the only way to get a working setup is to build the configuration by hand -- after which the console application is happy, and so, seemingly, is WLS during runtime.
    It would be really nice if a future version of WLS included a change to the console application that added the understanding that there are XA-capable databases out there, other than the limited few that it believes.
    ==============================================
    <name>DS_1</name>
    <jdbc-driver-params>
    <url>jdbc:postgresql://xxx.xxx.net:5432/dev</url>
    <driver-name>org.postgresql.xa.PGXADataSource</driver-name>
    <properties>
    <property>
    <name>port</name>
    <value>5432</value>
    </property>
    <property>
    <name>user</name>
    <value>dev</value>
    </property>
    <property>
    <name>databaseName</name>
    <value>dev</value>
    </property>
    <property>
    <name>server</name>
    <value>xxx.xxx.net</value>
    </property>
    </properties>
    <password-encrypted>{3DES}g1iK4zhw27k=</password-encrypted>
    <use-xa-data-source-interface>true</use-xa-data-source-interface>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <test-table-name>SQL SELECT 1</test-table-name>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>datasource/DS_1/jndi-name>
    <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
    </jdbc-data-source-params>
    =================================================
    Notes about the above:
    1- Notice that I'm specifying the PGXADataSource rather than the driver class as the driver name. A little strange, in that PGXADataSource does not implement Driver.
    2- Notice that I'm specifying properties for host, port, database name, etc. that are redundant to what is in the URL. This is the only way I've been able to make it work. It's as if the URL is completely ignored.

  • Mod_weblogic.c in wls 6.1 and case insensitive URL

    Hi,
    We need to send URL of a given application to a dedicated managed server (7126), the rest on the "default" managed server (7122). The URL may come in uppercase or in lowercase. I do not understand in the httpd.conf below, why only the "/db/owa/pp_pack" Urls are sent to port 7126, but not the "/db/owa/PP_PACK" which go the the 7122.
    Thank's for your help.
    <IfModule mod_weblogic.c>
    <Location /db/owa/pp_pack>
    WebLogicHost lidanl.pt.ch
    WebLogicPort 7126
    SetHandler weblogic-handler
    Order allow,deny
    Allow from all
    </Location>
    <Location /db/owa/PP_PACK>
    WebLogicHost lidanl.pt.ch
    WebLogicPort 7126
    SetHandler weblogic-handler
    Order allow,deny
    Allow from all
    </Location>
    <Location /db>
    WebLogicHost lidanl.pt.ch
    WebLogicPort 7122
    Idempotent OFF
    SetHandler weblogic-handler
    Order allow,deny
    Allow from all
    </Location>
    </IfModule>

    Alex,
    I am facing the same problem as you. It works on certain machines but others.
    Would like to know the answer if you already have one. Thanks
    -Qi
    [email protected] (Alex) wrote:
    I am doing a migration from WLS 5.1 to WLS 6.1.
    My java clients (application for Java Web Start and usual applet)
    call to EJB.
    Both types of applications work fine in WLS 5.1
    as well as a standalone application in WLS 6.1.
    But in WLS 6.1 for Java Web Start application and applet I get an
    exception:
    java.lang.ClassCastException
         at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:296)
         at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
    My code:
    properties = new Properties();
    properties.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    properties.put(Context.PROVIDER_URL, "t3://localhost:7001");
    Context ctx = new InitialContext(properties);
    Object ref = ctx.lookup("EBcatalog");
    System.err.println("Object returned by 'lookup' is of type: " +
    ref.getClass().getName());
    Object obj = PortableRemoteObject.narrow(
    ref, EBcatalogHome.class); /////////// Causes exception !!!!!
    PS. System.err.println writes "$Proxy1&" for standalone application in
    WLS 6.1 and for Java Web Start application and applet in WLS 5.1.
    It writes "weblogic.rmi.internal.StubInfo" for Java Web Start
    application and applet in WLS 6.1.
    What should I do? Thank in advance.
    Best Regards,
    Alex

  • AccessControlException WLS 6.1 and RMI

    I have just upgraded to WLS 6.1 and an existing RMI application runs fine.
    I then converted it from using the WebLogic RMI classes to the standard Sun ones,
    as recommended at a recent course at BEA, and as per the 6.1 documentation. Now
    my RMI Server, which is in the &#8220;Startup Application&#8221; for WLS gives
    an &#8220;AccessControlException&#8221; access denied in the server console.
    I aware that &#8220;rmid&#8221; now requires a security policy file and I added
    what I thought was the correct line, after looking Esmond Pitt&#8217;s excellent
    &#8220;The RMI Guide&#8221; to the java.policy file.
    Scouring the newsgroups I saw a reference to this being a bug in WLS 6.1 Can any
    confirm this or suggest where I might be going wrong.
    Regards,
    Roger Lee, NOTiFY. UK

    Problem with weblogic.policy file.
    "Roger Lee" <[email protected]> wrote:
    >
    I have just upgraded to WLS 6.1 and an existing RMI application runs
    fine.
    I then converted it from using the WebLogic RMI classes to the standard
    Sun ones,
    as recommended at a recent course at BEA, and as per the 6.1 documentation.
    Now
    my RMI Server, which is in the &#8220;Startup Application&#8221; for
    WLS gives
    an &#8220;AccessControlException&#8221; access denied in the server console.
    I aware that &#8220;rmid&#8221; now requires a security policy file and
    I added
    what I thought was the correct line, after looking Esmond Pitt&#8217;s
    excellent
    &#8220;The RMI Guide&#8221; to the java.policy file.
    Scouring the newsgroups I saw a reference to this being a bug in WLS
    6.1 Can any
    confirm this or suggest where I might be going wrong.
    Regards,
    Roger Lee, NOTiFY. UK

  • WLS 6.1 and Struts Applications

    I've been able to deploy a Struts 1.1b2 application on WLS 6.1...but only by
    altering the startweblogic.cmd file (Adding all required jar files to the
    classpath for the server - not an optimal solution by any means.)
    I have not been able to get the application working by simply dumping struts
    jar files in the application's WEB-INF\lib directory (as should be the
    case).
    So, is there any secret to making struts work under WLS 6.1 without
    resorting to editing the startweblogic.cmd file?
    Thanks.

    Oyvind,
    I believe using LDAPv2 with that release of Commerce Server is not supported.
    If you would like more information please contact BEA Support.
    Regards,
    Richard Wallace
    Senior Developer Relations Engineer
    BEA Support.
    "Oyvind" <[email protected]> wrote:
    >
    Hi,
    We have a problem with WLS 6.1 and LDAPRealm v2. Our application was
    working with
    WLS 6.0 and the LDAPRealm v2 patch. It is also working with 6.1 and LDAPRealm
    v1.
    When upgrading to WLS 6.1 we experience problems looking up user properties
    from
    LDAP. I put the same properties in the <CustomRealm> properties in config.xml
    as we had in the old ldaprealm.properties file.
    We are using WLCS 3.5 SP2, and we are looking up the user properties
    using the
    <um:getProperty> tag but it always returns null.
    Any idea what's wrong? This could be both a WLCS or a realm problem I
    guess?
    Below is the realm declaration in config.xml
    <CustomRealm
    ConfigurationData="user.dn=ou=People, o=my.com;server.principal=cn=Directory
    Manager;server.credential=adminadmin;user.filter=(&(cn=%u)(objectclass=person));group.dn=ou=Groups,
    o=my.com;group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=aaa.my.com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames))"
    Name="LDAPRealmV2" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    Any input is appreciated,
    Oyvind

  • WLS 6.1 and WLS 6.1 Service Pack1 install clears out registry.xml

    Hi,
    Just thought I'd post this problem and solution in case others came across it.
    I installed WLS 6.1 and then the Service Pack 1 separately. The Service Pack
    1 install clears out registry.xml.
    I then tried to install WLI V2.1 and it would not let me install as it could not
    find WLS 6.1 SP1 the definition of which it gets from registry.xml. The error
    was WLS 6.1 SP1 not detected.
    To get around this I got sent a registry.xml and edited it to be my home machine.
    (Not the safest thing to do but it worked!).
    I think if you download WLS 6.1 and SP1 and install as one rather than separately
    this does not happen.
    Regards,
    Kathryn

    Oyvind,
    I believe using LDAPv2 with that release of Commerce Server is not supported.
    If you would like more information please contact BEA Support.
    Regards,
    Richard Wallace
    Senior Developer Relations Engineer
    BEA Support.
    "Oyvind" <[email protected]> wrote:
    >
    Hi,
    We have a problem with WLS 6.1 and LDAPRealm v2. Our application was
    working with
    WLS 6.0 and the LDAPRealm v2 patch. It is also working with 6.1 and LDAPRealm
    v1.
    When upgrading to WLS 6.1 we experience problems looking up user properties
    from
    LDAP. I put the same properties in the <CustomRealm> properties in config.xml
    as we had in the old ldaprealm.properties file.
    We are using WLCS 3.5 SP2, and we are looking up the user properties
    using the
    <um:getProperty> tag but it always returns null.
    Any idea what's wrong? This could be both a WLCS or a realm problem I
    guess?
    Below is the realm declaration in config.xml
    <CustomRealm
    ConfigurationData="user.dn=ou=People, o=my.com;server.principal=cn=Directory
    Manager;server.credential=adminadmin;user.filter=(&(cn=%u)(objectclass=person));group.dn=ou=Groups,
    o=my.com;group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=aaa.my.com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames))"
    Name="LDAPRealmV2" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    Any input is appreciated,
    Oyvind

  • Error message when access WLS: active sockets and socket readers configuration

    Hi,
    I got the following error when I tried to access the WLS using a program to get
    the mbeans data.
    This error happens when I have 3 or more servers running ( 1 admin server, 2 or
    more managed servers). With cluster with more than 2 servers running, this error
    also occurs.
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    I creased the socket readers from 33% to 66%, but I still got the same error.
    I'm using WLS version 6.0 sp2
    My configuration is:
    Execute Threads = 15,
    Socket Readers = 33% or 66%
    Does anyone know how to fix this ? I am really appreciate for any suggestions.
    thanks,
    Kieu

    thank you, I just found out about setting those sockets using command line options
    an hour ago. But thanks a lot.
    -Kieu
    Kaye Wilcox <[email protected]> wrote:
    Kieu,
    You could try increasing the number of execute threads, you can do this
    via
    the admin console on the <server> --> Tuning tab.
    See http://edocs.bea.com/wls/docs60/perform/WLSTuning.html#1104317 for
    guidelines on setting the thread pool size and the number of socket readers.
    Here is a link that talks about socket communication in a cluster
    http://edocs.bea.com/wls/docs60/cluster/features.html#1007001.

  • Deploying a webservice on WLS 9.1 and got an wsdl error.

    Hi,
    I hoped it is then right usergroup to publish the following question.
    I'm trying to deploy a EJB webservice on a WLS 9.1.
    But I got the following error message:
    [java] port component "SystemServiceEndpointPort" is not found in wsdl.
    It's simple JAX-RPC based webservice where a SessionBean method is used as
    the service implementation. The same configuration (webservice.xml,
    jaxrpc-mapping-SystemService.xml, SystemService.wsdl) works fine under JBoss 4.0, but not with
    WLS 9.1. Maybe it's a simple configuration error and I hope someone can help.
    I haved remembered the namespace in the webservices.xml file: <wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port> and also defined et in the top of the file.
    Regards
    Torben
    <b>webservices.xml</b>
    <webservices
    xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://www.organisator.dk"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"
    version="1.1">
    <webservice-description>
    <icon></icon>
    <webservice-description-name>SystemService</webservice-description-name>
    <wsdl-file>META-INF/wsdl/SystemService.wsdl</wsdl-file>
    <jaxrpc-mapping-file>META-INF/jaxrpc-mapping-SystemService.xml</jaxrpc-mapping-file>
    <port-component>
    <icon></icon>
    <port-component-name>SystemServiceEndpointPort</port-component-name>
    <wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port>
    <service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
    <service-impl-bean>
    <ejb-link>SCSystem</ejb-link>
    </service-impl-bean>
    </port-component>
    </webservice-description>
    </webservices>
    <b>weblogic-webservices.xml</b>
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <webservice-description>
    <webservice-description-name>SystemService</webservice-description-name>
    <port-component>
    <port-component-name>SystemServiceEndpointPort</port-component-name>
    <service-endpoint-address>
    <webservice-contextpath>/winnie</webservice-contextpath>
    <webservice-serviceuri>/SystemService</webservice-serviceuri>
    </service-endpoint-address>
    </port-component>
    </webservice-description>
    </weblogic-webservices>
    <b>ejb-jar.xml</b>
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
    <description><![CDATA[No Description.]]></description>
    <display-name>Generated by XDoclet</display-name>
    <enterprise-beans>
    <!-- Session Beans -->
    <session >
    <description><![CDATA[System information handler]]></description>
    <display-name>SCSystem</display-name>
    <ejb-name>SCSystem</ejb-name>
    <home>dk.organisator.winnie.system.ejbsystem.services.SCSystemHome</home>
    <remote>dk.organisator.winnie.system.ejbsystem.services.SCSystemRemote</remote>
         <service-endpoint>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint>
    <ejb-class>dk.organisator.winnie.system.ejbsystem.services.SCSystemBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    </ejb-jar>
    <b>SystemService.wsdl</b>
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="SystemService" targetNamespace="http://organisator.dk/winnie/wsdl" xmlns:tns="http://organisator.dk/winnie/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://organisator.dk/winnie/types" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types>
    <schema targetNamespace="http://organisator.dk/winnie/types" xmlns:tns="http://organisator.dk/winnie/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="getXxxxxxxxx">
    <sequence>
    <element name="String_1" type="string" nillable="true"/></sequence></complexType>
    <complexType name="getXxxxxxxxxResponse">
    <sequence>
    <element name="result" type="string" nillable="true"/></sequence></complexType>
    <complexType name="ping">
    <sequence/></complexType>
    <complexType name="pingResponse">
    <sequence>
    <element name="result" type="int"/></sequence></complexType>
    <complexType name="setXxxxxxxx">
    <sequence>
    <element name="String_1" type="string" nillable="true"/></sequence></complexType>
    <complexType name="setXxxxxxxxResponse">
    <sequence/></complexType>
    <element name="getXxxxxxxxx" type="tns:getXxxxxxxxx"/>
    <element name="getXxxxxxxxxResponse" type="tns:getXxxxxxxxxResponse"/>
    <element name="ping" type="tns:ping"/>
    <element name="pingResponse" type="tns:pingResponse"/>
    <element name="setXxxxxxxx" type="tns:setXxxxxxxx"/>
    <element name="setXxxxxxxxResponse" type="tns:setXxxxxxxxResponse"/></schema></types>
    <message name="SystemServiceEndpoint_getXxxxxxxxx">
    <part name="parameters" element="ns2:getXxxxxxxxx"/></message>
    <message name="SystemServiceEndpoint_getXxxxxxxxxResponse">
    <part name="result" element="ns2:getXxxxxxxxxResponse"/></message>
    <message name="SystemServiceEndpoint_ping">
    <part name="parameters" element="ns2:ping"/></message>
    <message name="SystemServiceEndpoint_pingResponse">
    <part name="result" element="ns2:pingResponse"/></message>
    <message name="SystemServiceEndpoint_setXxxxxxxx">
    <part name="parameters" element="ns2:setXxxxxxxx"/></message>
    <message name="SystemServiceEndpoint_setXxxxxxxxResponse">
    <part name="result" element="ns2:setXxxxxxxxResponse"/></message>
    <portType name="SystemServiceEndpoint">
    <operation name="getXxxxxxxxx">
    <input message="tns:SystemServiceEndpoint_getXxxxxxxxx"/>
    <output message="tns:SystemServiceEndpoint_getXxxxxxxxxResponse"/></operation>
    <operation name="ping">
    <input message="tns:SystemServiceEndpoint_ping"/>
    <output message="tns:SystemServiceEndpoint_pingResponse"/></operation>
    <operation name="setXxxxxxxx">
    <input message="tns:SystemServiceEndpoint_setXxxxxxxx"/>
    <output message="tns:SystemServiceEndpoint_setXxxxxxxxResponse"/></operation></portType>
    <binding name="SystemServiceEndpointBinding" type="tns:SystemServiceEndpoint">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="getXxxxxxxxx">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal"/></input>
    <output>
    <soap:body use="literal"/></output></operation>
    <operation name="ping">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal"/></input>
    <output>
    <soap:body use="literal"/></output></operation>
    <operation name="setXxxxxxxx">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal"/></input>
    <output>
    <soap:body use="literal"/></output></operation></binding>
    <service name="SystemService">
    <port name="SystemServiceEndpointPort" binding="tns:SystemServiceEndpointBinding">
    <soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
    <b>jaxrpc-mapping-SystemService.xml</b>
    <?xml version="1.0" encoding="UTF-8"?>
    <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
    <namespaceURI>http://organisator.dk/winnie/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
    <namespaceURI>http://organisator.dk/winnie/wsdl</namespaceURI>
    </package-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:pingResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>result</java-variable-name>
    <xml-element-name>result</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxx</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>String_1</java-variable-name>
    <xml-element-name>String_1</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxxResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    </java-xml-type-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxx</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>String_1</java-variable-name>
    <xml-element-name>String_1</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:ping</root-type-qname>
    <qname-scope>complexType</qname-scope>
    </java-xml-type-mapping>
    <java-xml-type-mapping>
    <java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxxResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>result</java-variable-name>
    <xml-element-name>result</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    <service-interface-mapping>
    <service-interface>dk.organisator.winnie.system.ejbsystem.services.SystemService</service-interface>
    <wsdl-service-name xmlns:serviceNS="http://organisator.dk/winnie/wsdl">serviceNS:SystemService</wsdl-service-name>
    <port-mapping>
    <port-name>SystemServiceEndpointPort</port-name>
    <java-port-name>SystemServiceEndpointPort</java-port-name>
    </port-mapping>
    </service-interface-mapping>
    <service-endpoint-interface-mapping>
    <service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
    <wsdl-port-type xmlns:portTypeNS="http://organisator.dk/winnie/wsdl">portTypeNS:SystemServiceEndpoint</wsdl-port-type>
    <wsdl-binding xmlns:bindingNS="http://organisator.dk/winnie/wsdl">bindingNS:SystemServiceEndpointBinding</wsdl-binding>
    <service-endpoint-method-mapping>
    <java-method-name>getXxxxxxxxx</java-method-name>
    <wsdl-operation>getXxxxxxxxx</wsdl-operation>
    <wrapped-element/>
    <method-param-parts-mapping>
    <param-position>0</param-position>
    <param-type>java.lang.String</param-type>
    <wsdl-message-mapping>
    <wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxx</wsdl-message>
    <wsdl-message-part-name>String_1</wsdl-message-part-name>
    <parameter-mode>IN</parameter-mode>
    </wsdl-message-mapping>
    </method-param-parts-mapping>
    <wsdl-return-value-mapping>
    <method-return-value>java.lang.String</method-return-value>
    <wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxxResponse</wsdl-message>
    <wsdl-message-part-name>result</wsdl-message-part-name>
    </wsdl-return-value-mapping>
    </service-endpoint-method-mapping>
    <service-endpoint-method-mapping>
    <java-method-name>ping</java-method-name>
    <wsdl-operation>ping</wsdl-operation>
    <wrapped-element/>
    <wsdl-return-value-mapping>
    <method-return-value>int</method-return-value>
    <wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_pingResponse</wsdl-message>
    <wsdl-message-part-name>result</wsdl-message-part-name>
    </wsdl-return-value-mapping>
    </service-endpoint-method-mapping>
    <service-endpoint-method-mapping>
    <java-method-name>setXxxxxxxx</java-method-name>
    <wsdl-operation>setXxxxxxxx</wsdl-operation>
    <wrapped-element/>
    <method-param-parts-mapping>
    <param-position>0</param-position>
    <param-type>java.lang.String</param-type>
    <wsdl-message-mapping>
    <wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_setXxxxxxxx</wsdl-message>
    <wsdl-message-part-name>String_1</wsdl-message-part-name>
    <parameter-mode>IN</parameter-mode>
    </wsdl-message-mapping>
    </method-param-parts-mapping>
    </service-endpoint-method-mapping>
    </service-endpoint-interface-mapping>
    </java-wsdl-mapping>

    the problem is with the xmlns:wsdl="http://www.organisator.dk" line in your webservices.xml. It does not match the namespace of the corresponding PortType in your wsdl: targetNamespace="http://organisator.dk/winnie/wsdl"

  • WLS 5.1 and TX support

              The Weblogic 5.10 documentation states:
              "WebLogic Server Version 5.1 is compliant with the JavaSoft EJB 1.1 specification."
              Yet elsewhere in the documentation it states:
              "The following sections describe EJBs in several transaction scenarios. Note that in all cases EJB transactions should be restricted to a single persistent store, because WebLogic Server does not provide a two-phase commit protocol. EJBs that engage in distributed transactions (transactions that make updates in multiple datastores) cannot guarantee that all branches of the transaction commit or roll back as a logical unit."
              Wait a minute. I thought EJB 1.1 specified that an EJB container must provide a transaction coordinator to support distributed two-phase commit across multiple EJB servers.
              From the spec:
              "Regardless whether an enterprise bean uses bean-managed or container-managed transaction demarcation,
              the burden of implementing transaction management is on the EJB Container and Server Provider.
              The EJB Container and Server implement the necessary low-level transaction protocols, such as the
              two-phase commit protocol between a transaction manager and a database system, transaction context
              propagation, and distributed two-phase commit."
              The spec goes on to show several distributed transaction use cases that must be supported by the EJB container.
              This "single repository" limitation of Weblogic severely limits my options.
              What am I missing?
              Greg
              

    I used Loadrunner's WLS monitor while running some performance scripts on our application. I ended up relying on the WLS Console and some SNMP traps (using HP Openview to review data) in order to acurately guauge utilization of system resources...Regards,Steve

  • Setting up the environment in WLS 7.0 and deplying?

    Hi,
    Previously I have used WLS 6.1.
    I have set up the properties file and the required folders in the mydomain folder for the classes. It worked fine for me.
    Now when I am using WLS 7.02.
    This looks complicated. I have seen the documentation, it tells about different folders other than config like stage and server.
    My question is can I use the same old environment setting as in 6.1 in 7.02 and deploy the applications as before.
    If not, am I missing anything.
    If anyone has worked on WLS 7.02, please let me know how you have set up the environment and deplyed the applications.
    Thanks in Advance
    Rama
    [att1.html]

    "rama" <[email protected]> wrote in message news:[email protected]..
    Hi,
    Previously I have used WLS 6.1.
    I have set up the properties file and the required folders in the mydomain folder for the classes. It worked fine for me.
    Now when I am using WLS 7.02.
    This looks complicated. I have seen the documentation, it tells about different folders other than config like stage and server.
    You dont have to setup anything extra for 7.x deployment. The server and stage directories will take suitable defaults.
    See 'Using WebLogic Server 6.x Deployment Protocol' in http://e-docs/wls/docs70/programming/deploying.html
    My question is can I use the same old environment setting as in 6.1 in 7.02 and deploy the applications as before.
    If not, am I missing anything.
    If anyone has worked on WLS 7.02, please let me know how you have set up the environment and deplyed the applications.
    Thanks in Advance
    Rama
    [att1.html]

Maybe you are looking for

  • "Cannot connect to App Store"

    I know this has been asked a million times, I have gone through the steps listed under support. when I tap on the App Store or iTunes Store it says: "Cannot Connect to App/iTunes Store." Also, I get a network error in Facebook- I don't know if that's

  • Microsoft office re-installment

    Hello, my name is Judy Hermosillo, and I recently got a new computer. On my old computer I had Microsoft office, which included, PowerPoint, word, and excel. I was just wondering how I set that up in my new computer, which would be the one im using n

  • Ip address of machines on the switch?

    Is there a way on the switches page (I have the srw 2024) to see the ip address of each computer or other hardware on the system so I can port forward easily if need be (I want to see the address of my kids computers, xbox etc.). I am using a netgear

  • Capture data from previous version of record

    Good day all, I have a table that I am trying to capture information from multiple versions of the same record. In this example the record I want is the one that shows iss_stat of '2' and status of '6'. However, since the fields location, address, ci

  • Cost Center & Org Unit

    Hi Guys is there any transaction or report to know if a particular cost center (K) has relationship with how many / or which org units? thanks W