Weblogic Integration 2.1  problem

<b>I have installed Oracle 9.X then installed Weblogic 6.1 and then installed Weblogic Integration 2.1
after instalation i have started Weblogic server by clicking wlintegration2.1/config/bpmDomain/startWeblogic.cmd
Then i am getting this problem</b>
java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException:  [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException:  [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.getConfiguredPlugins(
PluginManagerCfgImpl.java:749)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.initializePlugins(Plu
ginManagerCfgImpl.java:873)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(PluginManagerCfg
Impl.java:80)
at com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(Pl
uginManagerCfgBean_gebmxi_EOImpl.java:1300)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListe
nerBean.java:153)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Oct 31, 2006 4:49:49 PM IST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "myserver" for domain "bpmdomain" running in Production Mode>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
<b>Please resolve this ASAP</b>.

I'm having this issue as well. Can you tell me how you fixed the problem???
Thanks

Similar Messages

  • Weblogic Integration WLW Message Queue Problem

    I am using BEA Weblogic Integration (BEA WLI). While testing processes, I get the following error on Weblogic Server Console:
    <Feb 27, 2006 10:56:55 AM CET> <Warning> <WLW> <000000>
    A message was unable to be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure event
    Please can you suggest what can be the problem.

    The bridge does not do anything to the properties on the messages. It just sends the messages that it received from the WLS JMS queue to MQSeries queue.
              Have you tried to receive directly from the WLS JMS queue and see if the receiver can retrieve the String property?
              Dongbo

  • Problem on starting weblogic integration 2.1

    I would like to ask you for advise/information on the start-up of the
    weblogic integration 2.1.
    I have tried to setup the weblogic integration 2.1 (sp1) at home, but
    without any success yet.
    There was nothing helpful that I can found in the BEA knowledge base.
    My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
    I have followed
    all the steps in the installation document, including create and setup the
    database.
    I have also executed the setenv.cmd and make sure the domain in use is
    "wlidomain".
    When I try to start up the weblogic integration 2.1, it give me the
    following exception.
    C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.ArrayIndexOutOfBoundsException
    at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
    at com.bea.utils.misc.Process.validate(Process.java:1231)
    at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
    at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
    at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance, and looking forward for your reply soon.
    Best Regards,
    Matthew Ho

    Hi.
    Try posting this on either weblogic.integration.interest or
    weblogic.integration.developer.
    Thanks,
    Michael
    Matthew Ho wrote:
    I would like to ask you for advise/information on the start-up of the
    weblogic integration 2.1.
    I have tried to setup the weblogic integration 2.1 (sp1) at home, but
    without any success yet.
    There was nothing helpful that I can found in the BEA knowledge base.
    My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
    I have followed
    all the steps in the installation document, including create and setup the
    database.
    I have also executed the setenv.cmd and make sure the domain in use is
    "wlidomain".
    When I try to start up the weblogic integration 2.1, it give me the
    following exception.
    C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.ArrayIndexOutOfBoundsException
    at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
    at com.bea.utils.misc.Process.validate(Process.java:1231)
    at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
    at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
    at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance, and looking forward for your reply soon.
    Best Regards,
    Matthew Ho--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Integration Directory(Configuration) Problem

    Hi All,
    I am facing one Probelm. I am working one the client through Citrix. I am not able to open Integration Directory(Configuration Problem) . In onsite it's working fine. Reming all other applications(Integartion Repository and SLD and Runtime work bench) are working fine.
    if I open Integration Directory i am getting this messge.
    <jnlp spec="1.0+" codebase="http://filp55.group.upm-kymmene.com:50100/dir">
        <information>
            <title>Integration Builder</title>
            <vendor>SAP AG</vendor>
            <homepage href="http://www.sap.com" />
            <description type="one-line">Directory</description>
            <description type="short">Directory</description>
            <description type="tooltip">Directory</description>
            <icon hight="64" href="start/graphics/sap6464.gif" type="splash" width="64" />
            <icon hight="32" href="start/graphics/SAP3232.gif" width="32" />
        </information>
        <security>
            <all-permissions />
        </security>
        <resources>
            <j2se version="1.4+" initial-heap-size="32m" max-heap-size="1024m" />
            <jar href="directory/aii_ibdir_client.jar" />
            <jar href="directory/aii_ibdir_core.jar" />
            <jar href="directory/aii_ibdir_sbeans.jar" />
            <jar href="directory/aii_ibdir_rb.jar" />
            <jar href="directory/aii_ib_client.jar" />
            <jar href="directory/aii_ib_core.jar" />
            <jar href="directory/aii_ib_sbeans.jar" />
            <jar href="directory/aii_ib_rb.jar" />
            <jar href="directory/aii_util_icons.jar" />
            <jar href="directory/aii_util_swing.jar" />
            <jar href="directory/aii_util_xml.jar" />
            <jar href="directory/aii_util_xsd.jar" />
            <jar href="directory/aii_utilxi_misc.jar" />
            <jar href="directory/aii_util_rb.jar" />
            <jar href="directory/clientaii_ib_sbeans.jar" />
            <jar href="directory/clientaii_ibdir_sbeans.jar" />
            <jar href="directory/frog.jar" />
            <jar href="directory/focus14.jar" />
            <jar href="directory/sapxmltoolkit.jar" />
            <jar href="directory/jta.jar" />
            <jar href="directory/ejb20.jar" />
            <jar href="directory/exception.jar" />
            <jar href="directory/logging.jar" />
            <jar href="directory/guidgenerator.jar" />
            <jar href="directory/jperflib.jar" />
            <jar href="directory/sapni.jar" />
            <jar href="directory/sapj2eeclient.jar" />
            <property name="sap.theme" value="Streamline" />
            <property name="jnlp.log.initialConfiguration" value="FILE, SIMPLE" />
        <property name="jnlp.com.sap.aii.ib.client.properties" value="com.sap.aii.ib.client., com.sap.aii.ib.core., com.sap.aii.util.xml., com.sap.aii.connect., com.sap.aii.repository.mapping.additionaltypes, com.sap.aii.docu., com.sap.aii.ibrep.core., com.sap.aii.ibdir.core.*" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.connect.landscape.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.cr.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.ib.client.content.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.repository.contextroot" value="rep" /><property name="jnlp.com.sap.aii.ib.client.login.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.directory.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.cr.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.rwb.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.directory.contextroot" value="dir" /><property name="jnlp.com.sap.aii.connect.rwb.contextroot" value="rwb" /><property name="jnlp.com.sap.aii.connect.landscape.httpsport" value="@com.sap.aii.server.httpsport.lcr@" /><property name="jnlp.com.sap.aii.connect.repository.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.repository.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.cr.httpsport" value="@com.sap.aii.server.httpsport.cr@" /><property name="jnlp.com.sap.aii.connect.repository.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.contextroot" value="run" /><property name="jnlp.com.sap.aii.connect.integrationserver.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.rwb.httpsport" value="@com.sap.aii.connect.rwb.httpsport@" /><property name="jnlp.com.sap.aii.connect.landscape.httpport" value="50000" /><property name="jnlp.com.sap.aii.docu.languages" value="null" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.initialheapsize" value="32m" /><property name="jnlp.com.sap.aii.util.xml.parserFactory" value="com.sap.engine.lib.jaxp.SAXParserFactoryImpl" /><property name="jnlp.com.sap.aii.connect.directory.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.httpsport" value="@com.sap.aii.server.httpsport.directory@" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpport" value="8001" /><property name="jnlp.com.sap.aii.connect.rwb.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.cr.httpport" value="50000" /><property name="jnlp.com.sap.aii.connect.landscape.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.SAPMYNAME" value="filp55_GTX_01" /><property name="jnlp.com.sap.aii.connect.rwb.httpport" value="50100" /><property name="jnlp.com.sap.aii.docu.url" value="null" /><property name="jnlp.com.sap.aii.ib.client.applicationname.directory" value="sap.com/com.sap.xi.directory/" /><property name="jnlp.com.sap.aii.util.xml.transformerFactory" value="com.sap.engine.lib.jaxp.TransformerFactoryImpl" /><property name="jnlp.com.sap.aii.ib.client.applicationname.repository" value="sap.com/com.sap.xi.repository/" /><property name="jnlp.com.sap.aii.ib.client.login.InitialContextFactory" value="com.sap.engine.services.jndi.InitialContextFactoryImpl" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpport" value="50100" /><property name="jnlp.client" value="true" /><property name="jnlp.com.sap.aii.connect.repository.httpsport" value="@com.sap.aii.server.httpsport.repository@" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.maxheapsize" value="1024m" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpsport" value="@com.sap.aii.connect.integrationserver.httpsport@" /><property name="jnlp.com.sap.aii.connect.integrationbuilder.startpage.url" value="rep/start/index.jsp" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpsport" value="@com.sap.aii.connect.integrationserver.r3.httpsport@" /><property name="jnlp.com.sap.aii.connect.rwb.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.util.xml.schemaValidator" value="com.sap.engine.lib.schema.validator.SchemaValidator" /><property name="jnlp.rc.release" value="7_00" /><property name="jnlp.rc.applname" value="DIRECTORY" /><property name="jnlp.rc.supportpackage" value="09" /><property name="jnlp.rc.synctime" value="${sync.time}" /></resources>
        <application-desc main-class="com.sap.aii.ibdir.gui.appl.ApplicationImpl">
            <argument>webstart</argument>
        </application-desc>
    </jnlp>
    Please help me on this..........
    Thanks in Advacne.
    Regards,
    Chandra

    Hello,
    1)
    May be the problem is a network connectivity issue. Do one thing copy the "cahce" folder from some other client PC(which has successfully opened IR and ID) to your client PC. The folder resides in "C:Documents and Settings<yourUserProfile>Application DataSunJavaDeploymentjavaws".
    Copy "cache" folder to your client PC under the above path.
    /people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]
    2) Go to http://filp55.group.upm-kymmene.com:50100/rep/
    Click on Administration -> Java™ Web Start -> Java™ Web Start Administration ->
    Try
    1. Re-initialization (then try logging)
    2. Re-initialization and force-signing (then try logging)
    3. Delete lock (then try logging)
    Do this for IR and ID tabs.
    3) Check can be a firewall issue.
    4) Check wether sufficient roles have been assigned -> Tcode -> SU01 -> roles tab. These roles need to be assigned to your username
    SAP_BC_AI_LANDSCAPE_DB_RFC
    SAP_SLD_CONFIGURATOR
    SAP_SLD_DEVELOPER
    SAP_XI_BPE_CONFIGURATOR_ABAP
    SAP_XI_BPE_MONITOR_ABAP
    SAP_XI_DEVELOPER
    SAP_XI_DEVELOPER_ABAP
    SAP_XI_DEVELOPER_J2EE
    SAP_XI_MONITOR
    SAP_XI_MONITOR_ABAP
    SAP_XI_MONITOR_J2EE
    <b>*******************Reward,if found useful</b>
    Edited by: BVS on May 7, 2008 3:01 PM

  • Weblogic Integration 10r3 error in msg-header-2_0.xml

    Hello,
    I am trying to go through te WLI workshops, but cannot publish a WLI process.
    The Tutorial_Process_Application RequestQoute.java has the following error in the msg-header-2_0.xml:
    Severity and Description     Path     Resource     Location     Creation Time     Id
    Referenced file contains errors (http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd). For more information, right click on the message and select "Show Details..."     Tutorial_Process_Application_Utility/schemas/system     msg-header-2_0.xsd     line 1     1257804610777     410
    A new WLI project from scratch gives te same error, it is as if the msg-header-2_0.xml is not correctly generated when the WLI process is created.

    Aha! problem solved :)
    The tutorial states : 'Select the Add WebLogic Integration System and Control Schemas to Utility Project check box to add the system schemas to the Schemas folder under the Utility project.'
    If you do that it does not work, and i get the errors I discribed in the post, howerver if ypu leave it blanked out, the process can be published, without error or warnings.
    As I am new to WLI (use to work with Oracle Bpel) I have no idea about the importance of adding the Integration system and control schemas to the utility project.
    However as my goal is to work through the workshops, I wil worry about it later.
    Edited by: DaveVQ on 14-nov-2009 5:39

  • WLST and WebLogic Integration

    Hi all,
    I have installed WebLogic Integration 8.5 bundle. Meaning i have also installed weblogic server 8.1. on Windows XP
    I am now trying to use Weblogic Scripting Tool WLST. But there is no tools on the menu(tools->weblogic scripting tool) this was added in the 9.1 installation...
    How do I configure my installation weblogic server 8.1 with WLI8.5 to run WLST?
    after i run setELSEnv.cmd to set the environment. Then i try java weblogic.WLST and the error is "java.lang.NoClassDefFoundError: weblogic/WLST"
    Where are the libs, how do i configure WLST to run.
    I also tried starting the WLST from the 9.1 installation, but it cannot connect to 8.1 installation, tough connecting to 9.1 installation is no problem. If i try i get this error: "weblogic.management.ManagementRuntimeException: java.lang.NoSuchMethodError: isCachable"
    (I installed weblogic 9.1 and there the WLST was installed during installation and all works just fine. unfortenatly my system must run on 8.1->wli8.5)

    Hi
    I am trying to use WLST tool for configuring Weblogic domain in 9.1 OFFLINE.
    I have done with almost all except JTA configuration.
    Can you please give me smaples for the same.
    The following is part iof my script...
    readTemplate('F:/AuctionDoc/Installer/inDomain.jar')
    cd('/JDBCSystemResource/localNonTxPool/JdbcResource/localNonTxPool')
    create('myJdbcDataSourceParams','JDBCDataSourceParams')
    cd('JDBCDataSourceParams/NO_NAME_0')
    set('JNDIName', 'jdbc/NonTxDataSource')
    #JDBC settings and other JMS settings worked
    But the JTA settings dint work
    #=======================================================================================
    # Set JTA timeout
    #=======================================================================================
    cd("/JTA/inInstDomain")
    set("TimeoutSeconds", "1200")
    set("AbandonTimeoutSeconds", "1200")
    I have to do the above OFFLINE.
    I could not locate the JTA folder or any thing related with JTA configuration to do offline using WLST
    Can you please give an example of JTA settings
    Thanks
    Binu

  • Weblogic Integration Sample is available for download from developer site

    Hi, All,
    The Weblogic Integration 2.0 Sample is available for download from the
    developer site:
    http://developer.bea.com/ftp_bin/download/code/wliSample_1.zip
    This sample shows how to develop a standard based integration solution
    within and across enterprises using the key functionalities of the WebLogic
    Integration 2.0, including Business Process Management (BPM), Enterprise
    Information System (EIS) connectivity, inter-enterprise collaboration
    (B2Bi), and XML/non-XML data transformation.
    Chunbo Huang
    BEA System

    It shoud not took 3 hours. Normally, you expect wait for 1 -2 minutes.
    For your case, I suggest to
    (1)run the cleanWF.cmd script then shutdown the server
    (2)restart the server
    (3) run cleanWF again
    (4) run the sample.
    let me know if you still have problems
    Chunbo
    "Chris Stead" <[email protected]> wrote in message
    news:[email protected]..
    Chunbo/Henry,
    While running the WLI sample, I have been waiting for a QPA Reponse frommy
    suppliers for about three hours, is this expected behavior? I havechecked the
    weblogic.log file and there are no exceptions. I seem to be stuck on the
    "Check QPA Reponse" screen. This was addressed briefly in the user guide,
    however, it didn't say how long you should wait. Please advise, thanks.
    Cheers,
    Chris
    Chunbo Huang wrote:
    Hi, All,
    The Weblogic Integration 2.0 Sample is available for download from the
    developer site:
    http://developer.bea.com/ftp_bin/download/code/wliSample_1.zip
    This sample shows how to develop a standard based integration solution
    within and across enterprises using the key functionalities of the
    WebLogic
    Integration 2.0, including Business Process Management (BPM),Enterprise
    Information System (EIS) connectivity, inter-enterprise collaboration
    (B2Bi), and XML/non-XML data transformation.
    Chunbo Huang
    BEA System

  • Weblogic Integration failed to build Cluster ENV

    Dear buddies,
    I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
    Here is the process how I created WLI cluster:
    ENV:RedHat9+ WL8.1_SP4
    Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
    BEA_HOME=/opt/bea/
    1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
    and I didn't create extra JDBC POOL except the standard one.
    2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
    Now I am having following problem.
    1.admin Server(cgServer) can startup without any problem
    2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
    3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
    but seems the pointbase only listen 9092!!
    4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
    below are detailed output when I startManagedServers:
    command:
    [root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
    ####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
    Listen Address          172.16.4.236:7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
    Channel Weight          50
    Accept Backlog          50
    Login Timeout          5000ms
    Max Message Size     10000000
    Message Timeout     60s
    Idle Timeout          65s
    Tunneling Timeout     40s
    Tunneling Ping          45s>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)

    Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.

  • New article: Exploring the WebLogic Integration 8.1 RDBMS Event Generator

    Dev2Dev has just published an article that you may be interested in:
    Exploring the WebLogic Integration 8.1 RDBMS Event Generator
    http://dev2dev.bea.com/pub/a/2007/02/rdbms-event-generator.html
    If you'd like to write for Dev2Dev on a WebLogic Integration (or any other) topic, please contact me!
    Regards,
    Jon
    Jon Mountjoy - Editor, Dev2Dev - http://dev2dev.bea.com/pub/au/13

    If you are using a cluster you need to make sure the connection pool and data source are deployed on the admin server. I have had this problem many times before.

  • Weblogic Integration Business Process Tutorial (10.2)

    Hi I'm going through the weblogic integration business process tutorial and when I get to Step 5, "Run the business process" I get a bunch of errors, including the ones below:
    s4s-elt-invalid-content.1: The content of '#AnonType_Acknowledgment' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.
    s4s-elt-invalid-content.1: The content of '#AnonType_AckRequested' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.
    s4s-elt-invalid-content.1: The content of '#AnonType_Description' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.
    src-resolve: Cannot resolve the name 'eb:MessageHeader' to a(n) 'element declaration' component.
    src-resolve: Cannot resolve the name 'soap:mustUnderstand' to a(n) 'attribute declaration' component.
    Has any one run into this problem while going through this tutorial and if so, have you found a solution for this?
    Thanks.

    The following page is right from the WLI documentation. Are none of these samples useful to you?
    [http://edocs.bea.com/wli/docs102/sol_samples/index.html]

  • Help: Why cann't I install WebLogic Integration?

    Hi,
    I have installed WebLogic Server 6.0 on e:\bea (Windows 2000). When I
    install WebLogic Integration 2.0 sp2, I get the message "WebLogic Server 6.0
    is a prerequisite for this installion, you do not seem to have it installed
    to e:\bea". How can I do?

    I have the same problem like yang.
    I use 6.0.sp2 !
    Any ideas?
    Maik
    "Christo" <[email protected]> wrote:
    Is it 6.0 SP2?
    "yang songqi" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I have installed WebLogic Server 6.0 on e:\bea (Windows 2000).When I
    install WebLogic Integration 2.0 sp2, I get the message "WebLogic Server6.0
    is a prerequisite for this installion, you do not seem to have itinstalled
    to e:\bea". How can I do?

  • Weblogic integration kit with VAJ 4.0

    Will support be added for the Weblogic integration kit for IBM VAJ 4.0 now
    that 4.0 professional is available?
    Alex Garrison

    Hi,
    In VAJ3.5.3 Weblogic Bridge documentation ...
    The docs/userguide.pdf says that (In service-PAck for Integration-Kit)
    Import VAJ35weblogic510spX.zip where 'X' is the service-pack number
    BUT...I don't find VAJ35weblogic510sp10.zip Anywhere on BEA site.
    Please let me know where to get it from if it is ever available.
    How do you upgrade the bridge to SP10?
    Thanks,
    Harish.
    Jim Edwards-Hewitt <[email protected]> wrote:
    >
    Hi, Alex,
    While I'm not in a position to commit to anything official (I'm in
    engineering, not PM), I think I can safely say that if the name "IBM"
    isn't a problem for us, the name "WebSphere" won't be either. (And the
    way IBM is going with slapping "WebSphere" on everything they can so
    they can claim more WebSphere sales, they're practially synonmymous.
    I'm not working on our VisualAge stuff now, but I did in the past. We
    put a tremendous amount of effort into integrating with VisualAge for
    comparatively little return, because the VAJ API is so limited, but it
    was worth it to do the best we can to allow you to use VAJ to develop
    for WebLogic, and not abandon VisualAge users to WebSphere. If IBM
    moves to a tool that makes it easier for us to do that and lets us
    provide a better user experience, then I believe we'll take advantage
    of
    it. (And of course, IBM is using tools to try to steer developers to
    WebSphere, so if we can make them work well for WebLogic, too, that
    helps us as well as benefiting developers.)
         -- Jim
    Alex Garrison wrote:
    Michael,
    I will certainly do so, and I will ask the other developers here todo so as
    well. However, since IBM is phasing out VAJ in favor of a WSW-basedIDE,
    and since WSW is open source/open API, perhaps this will be a mootpoint a
    year from now. BTW: I know that IBM says it will continue to supportVAJ
    for at least the next two years, but I dont have to be beat over thehead to
    see that VAJ is dying and IBM is moving to the WSW-based IDE.
    A big concern in the VAJ community is whether partners like BEA willwant to
    remain partners with a product that has the name "websphere" in it(WSW =
    Websphere Studio Workbench). I would move to a more platform-neutralIDE
    like JBuilder in a heartbeat if it wasnt for the $3000 (oh excuse me,$2999)
    per seat enterprise license.
    Alex Garrison
    "Michael Girdley" <----> wrote in message
    news:[email protected]...
    It is being worked on. No ETA yet.
    I would encourage you to vote on IBM's Web sites open the VisualAge
    APIs
    to
    partners like BEA.
    http://commerce.bea.com/downloads/weblogic_server_tools.jsp
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    Buy the only book covering J2EE & WebLogic 6:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/103-9227026-
    4636613
    "Alex Garrison" <[email protected]> wrote in message
    news:[email protected]...
    Will support be added for the Weblogic integration kit for IBM
    VAJ 4.0
    now
    that 4.0 professional is available?
    Alex Garrison

  • Cannot run WebLogic Integration Samples from QuickStart

    I have installed the full WebLogic platform on an Intel box running Red Hat Linux
    8.0. From QuickStart I am unable to run the WebLogic Integration Samples. Everything
    else seems to work as expected.
    The error message that results when attempting to run the Integration samples
    is as follows:
    RunSamples execution failed: /usr/local/bea/weblogic700/samples/integration/samples/lib/RunSamples.xml:106:
    Cannot execute switchdb pointbase

    Dear Micha,
    Did you maintain the host file in Drivers\etc file:
    hope this will solve the problem
    If you did not add them plz add the hosts as follows:
          102.54.94.97     rhino.acme.com          # source server
           38.25.63.10     x.acme.com              # x client host
          (your PI server IP)   server Id name
    And also check your Java web start version.
    download the correct version for sun website.
    Best Regards
    Praveen K Kurni

  • CgPool in WebLogic Integration 10.2

    Hi everyone.
    I'm working on Best Practice for WebLogic Integration 10.2 Link:[Document is here|http://download.oracle.com/docs/cd/E13214_01/wli/docs102/pdf/bestpract.pdf]
    In the WLI Application recovery topic, it says "cgDataSource is configured in cgPool.Best Practices for WebLogic® Integration Application Life Cycle"
    The problem is I can't find a cgPool in WLI 10.2 but it can be found in WLI 8.1. There's only cgDatasource and how can i know which pool it's in.
    However, my point is to test and preparing Application Recovery scenario but I think the information is too less and not enough. Could anyone help or advice me?
    Thank for advance.

    Hi,
    In WLI 8.1x the Concept of creating the DataSource was different...First we used to create the Connection Pool (Suppose: cgPool), then We Used to create the DataSource (Suppose: cgDataSource), While Creating the DataSource we used to add the Connection Pool to the DataSource.
    But from WLI9.x onwards, the dataSource Creation concept is changed...Now we Need not to Separately create the ConnectionPool, We Can directly Create a DataSource ... ConnectionPool will internally configured...
    Could you please explain a Bit about "Which kind of Application Recovery" you are talking about...?
    One Way is to Achieve Application Failover& recovery Using WebLogic clustering ...
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic At A Glance)

  • Weblogic Integration 2.0 fails to install on Win2000

    Hi,
    I was installing Weblogic Integration 2.0 (eval copy) on Windows 2000. The first
    component which got installed was the Process Integrator 2.0 piece. I chose Cloudscape
    for the database. All other inputs were default values. At the end of the installation,
    the installer came up with a message that it did not install properly. The install
    errors text file tells me that there was a runtime error during Cloudscape db
    creation. (listed below)
    Does anyone have an idea what the problem could be? Any kind of input would be
    helpful.
    Thanks
    Karthik.
    contents of installErrors.txt file:
    Jul 12, 2001 5:13:19 PM -- Error During The "Cloudscape" database creation. --
    Runtime exec failed.

    Karthik,
    We also got this error installing WebLogic Integration 2.0 on a Windows 2000 machine.
    It seems that the Cloudscape initialisation fails if you are installing to a directory
    with spaces anywhere in the path. After changing our target path from c:\program
    files\etc... to c:\wli20\etc... the installation concluded successfully.
    Hope this helps.
    Edward Wichmann
    Perpsective Technologies
    WebLogic Consulting available in the UK
    Tel: +44 (0)7866 425774
    E-mail: [email protected]
    "Karthik Krishnamoorthy" <[email protected]> wrote:
    >
    Hi,
    I was installing Weblogic Integration 2.0 (eval copy) on Windows 2000.
    The first
    component which got installed was the Process Integrator 2.0 piece. I
    chose Cloudscape
    for the database. All other inputs were default values. At the end of
    the installation,
    the installer came up with a message that it did not install properly.
    The install
    errors text file tells me that there was a runtime error during Cloudscape
    db
    creation. (listed below)
    Does anyone have an idea what the problem could be? Any kind of input
    would be
    helpful.
    Thanks
    Karthik.
    contents of installErrors.txt file:
    Jul 12, 2001 5:13:19 PM -- Error During The "Cloudscape" database creation.
    Runtime exec failed.

Maybe you are looking for

  • Difference between primary eindex and secondary index?

    hi experts pls answer me difference between primary eindex and secondary index? rewads apply. thanks. naresh.

  • Printing in List View

    Does anyone know a way to print in a LIST of images with META data instead of printing thumbnails?

  • IMac 24" brown patches on LCD SCreen

    My iMac 24" has had three screens replaced since I bought it in May 2009. Dark brown patches appear and get darker in random areas of the screen. Since I am a photographer, it is a serious problem. The last replacement was only 5 weeks ago. Have many

  • SEM CPM  BSC Value Field with AGGREGATION is working wrong

    Hi everyone We have a balanced scorecard defined and working fine until now. Since a week, the value fields with "aggregation" (accummulated each month) is showing the correct value for the periods 2 -12, but the Period 1 is showing the value of the

  • Distorted sound quality in AIR 2.6 on iOS

    I am experiencing significant distortion of mp3 audio files (a child speaking) in my iPad app built with AIR 2.6. I have tested the audio files on the device in other apps, and can confirm that the problem is specifically with my app, not a problem w