Webservices on WLI 2.0 (WLPI)

Hi everyone!,
I hope somebody can help me with this, very urgent!
We implement a Workflow using WLI 2.0 (WLPI), on this process we need to call
a WebService message style on WLS6.1 hosted by another Company. After searching
for something we found a plug-in (client.jar) to use with Weblogic process integrator
but this is just for a RPC-style webservice, can anyone have solved something
like that.
Could I implement an EJB on the process side that call the webservice without
compatibility problems.
Thanks&Regards.
Mauricio Del Moral

Hi again,
The plug-in for WLI2.0 (client) calls RPC-style Webservice on WLS6.1, but at the
end appears a Java.Lang.NullPointerException.
Why? This is the 63M dlls question?
I'm sending the stack trace error on WLPI side.Is important to say that the functionality
on Webservice (WLS6.1) is done correctly, When Webservice ends and sends SOAP
message to WLPI this error comes up.
Thanks&Regards
Mauricio Del Moral
[WLI&WS.txt]

Similar Messages

  • OnAsyncFailure event + buffered WebService

    Hi,
    From a JPD, we call an external WebService using WLI (8.1 SP4) WebService control.
    The WebService control was generated from the WSDL.
    The WebService control method has the Message Buffer property enabled (this is required by the application).
    It works fine except if an error occurs during the WebService call.
    For example if we have a connection error, the JPD is not able to handle the error (as the call is buffered). I tried to handle in the JPD the onAsyncFailure callback of the WebService control but the JPD did not receive the error and goes the "Aborted" state each time an error occured.
    Thanks in advance for any solution.
    Azim
    Edited by makboulhoussen at 06/06/2007 2:34 AM

    Hi,
    From a JPD, we call an external WebService using WLI (8.1 SP4) WebService control.
    The WebService control was generated from the WSDL.
    The WebService control method has the Message Buffer property enabled (this is required by the application).
    It works fine except if an error occurs during the WebService call.
    For example if we have a connection error, the JPD is not able to handle the error (as the call is buffered). I tried to handle in the JPD the onAsyncFailure callback of the WebService control but the JPD did not receive the error and goes the "Aborted" state each time an error occured.
    Thanks in advance for any solution.
    Azim
    Edited by makboulhoussen at 06/06/2007 2:34 AM

  • How to create business operation for starting workflows

    How to create business operation for starting workflows from worklist?
    When I call methods that implements business operation from java class everything
    works fine(wlpi-ejb.jar is required), but when I call business operation from
    Studio I can't use classes from wlpi-ejb.jar.

    Business operation is called by WLIS. So, I include wlpi-ejb.jar into WLIS classpath.
    Studio uses deployed EJB from wlpi-*.jar, I don't know why Studio doesn't see
    methods from deployed EJBs when WLIS classpath contains wlpi-ejb.jar.
    "Andrew Pitonyak" <[email protected]> wrote:
    >
    When studio starts, what is your classpath? If you use the included batch
    file to start it, then your class path may not include this :-)
    Andrew
    "Raul" <[email protected]> wrote in message
    news:[email protected]..
    How to create business operation for starting workflows from worklist?
    When I call methods that implements business operation from java classeverything
    works fine(wlpi-ejb.jar is required), but when I call business operationfrom
    Studio I can't use classes from wlpi-ejb.jar.

  • Changeing Transaction timeouts

    Hi..
    While trying to tune the WLI ejbs, I came across the following documentation
    on edocs.bea.com. It mentions to change the trans-timeout-seconds attribute
    for the wlpi-ejb.jar file.
    But when I accessed the ejb descriptor using weblogic console, I could not
    find the trans-timeout-seconds attribute in the ejb-jar.xml. Can anyone
    please inform me where to find it ?
    Configuring EJB Transactions
    If your system returns an exception indicating that a transaction timed out
    while a message was being processed, we recommend that you tune the
    transaction timeout parameters in the following BPM resources:
    a.. WLI-BPM Server (wlpi-ejb.jar)
    b.. WLI-BPM Event Processor EJB (wlpi-mdb-ejb.jar)
    Note: Transaction timeouts are more likely to occur when large messages,
    rather than small messages, are being processed.
    To tune the transaction timeout parameters, we recommend that you change the
    trans-timeout-seconds attribute in the wlpi-ejb.jar and wlpi-mdb-ejb.jar
    files from 90 seconds to 1090 seconds. To access the JAR files:
    1.. In the Administration Console navigation tree, select
    Deployments->EJB.
    2.. Select WLI-BPM Server EJB or WLI-BPM Event Processor EJB.
    3.. Click Edit EJB Descriptor to display a new window in which you can
    edit the EJB descriptor.
    Thanks..
    Mandar

    Hi,
    The trans time out value is set in "weblogic-ejb-jar.xml" Choose edit EJB descriptor
    for BPM server,In wlpi-ejb.jar, there are three jars, choose weblogic EJB jar.
    You can find the Transaction descriptor in Weblogic Enterprise beans.
    Regards,
    Anandhi
    "Mandar Gandhe" <[email protected]> wrote:
    Hi..
    While trying to tune the WLI ejbs, I came across the following documentation
    on edocs.bea.com. It mentions to change the trans-timeout-seconds attribute
    for the wlpi-ejb.jar file.
    But when I accessed the ejb descriptor using weblogic console, I could
    not
    find the trans-timeout-seconds attribute in the ejb-jar.xml. Can anyone
    please inform me where to find it ?
    Configuring EJB Transactions
    If your system returns an exception indicating that a transaction timed
    out
    while a message was being processed, we recommend that you tune the
    transaction timeout parameters in the following BPM resources:
    a.. WLI-BPM Server (wlpi-ejb.jar)
    b.. WLI-BPM Event Processor EJB (wlpi-mdb-ejb.jar)
    Note: Transaction timeouts are more likely to occur when large messages,
    rather than small messages, are being processed.
    To tune the transaction timeout parameters, we recommend that you change
    the
    trans-timeout-seconds attribute in the wlpi-ejb.jar and wlpi-mdb-ejb.jar
    files from 90 seconds to 1090 seconds. To access the JAR files:
    1.. In the Administration Console navigation tree, select
    Deployments->EJB.
    2.. Select WLI-BPM Server EJB or WLI-BPM Event Processor EJB.
    3.. Click Edit EJB Descriptor to display a new window in which you
    can
    edit the EJB descriptor.
    Thanks..
    Mandar

  • Exception in WLPI after upgrading to WLI 2.0 SP4 from SP2

    Environment is :
    WLS 6.0 SP2 and WLI 2.0 SP4 on Solaris 2.8.
    We get the following exception when the server starts up and tries to deploy
    wlpi-mdb-ejb.jar. This started only after upgrading to WLI 2.0 SP4 from WLI
    2.0 SP2.
    Any help will be highly appreciated.
    ####<Feb 12, 2002 6:08:49 PM PST> <Info> <J2EE> <spruce> <edevServer31>
    <main> <system> <> <160003> <Deployed : wlpi-master-ej
    b.jar>
    ####<Feb 12, 2002 6:08:49 PM PST> <Info> <EJB> <spruce> <edevServer31>
    <main> <system> <> <010008> <EJB Deploying file: wlpi-m
    db-ejb.jar>
    ####<Feb 12, 2002 6:08:50 PM PST> <Info> <EJB> <spruce> <edevServer31>
    <main> <system> <> <010052> <An exception occurred whil
    e creating the freepool.>
    java.rmi.RemoteException: Error in the bean's constructor : ; nested
    exception is:
    java.lang.reflect.InvocationTargetException
    java.lang.reflect.InvocationTargetException:
    java.lang.ExceptionInInitializerError:
    weblogic.ejb20.internal.MethodPermissionEx
    ception: Security violation: insufficient permission to access method
    at
    weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:91)
    at
    weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
    :55)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.getState(PluginManager
    CfgBeanEOImpl.java:1411)
    at
    com.bea.wlpi.server.plugin.PluginManagerImpl.refreshState(PluginManagerImpl.
    java:187)
    at
    com.bea.wlpi.server.plugin.PluginManagerImpl.<init>(PluginManagerImpl.java:1
    72)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.<clinit>(EventProcessor.ja
    va:37)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.ejbCreate(EventListenerB
    ean.java:47)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDrivenEJBHome
    .java:297)
    at
    weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:98)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:100)
    at weblogic.ejb20.pool.Pool.<init>(Pool.java:74)
    at weblogic.ejb20.pool.EntityPool.<init>(EntityPool.java:34)
    at
    weblogic.ejb20.pool.MessageDrivenPool.<init>(MessageDrivenPool.java:43)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getPool(MessageDrivenBeanI
    nfoImpl.java:336)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
    foImpl.java:403)
    at
    weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    at weblogic.j2ee.Application.addComponent(Application.java:133)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:327)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:277)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:232)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:192)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:562)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    48)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:285)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
    at $Proxy0.updateDeployments(Unknown Source)
    Regards,
    Adarsh

    Hi Feng,
    In 2.0.10, we strictly evualuate the xpath queries:
    1. According to bpel spec 1.1 section 14.3, xpath queries should be absolute queries. you need to change query="//sessionID" to /cstaPrefix:iRequest/cstaPrefix:sessionID.
    2.If your xml documents are namespace aware then you must use qualified xpath queries. in your case you have to add prefix to your query like "/tns:disconnect_cstaRequest/tns:input. So please change the unqualified query //sessionId to qualified one by just prefixing. (Same rule goes for /xmlMessage query, please change all your queries to have prefix.)
    Here is the link to xpath spec which explains this in more detail.
    http://www.w3.org/TR/xpath#node-tests
    A QName in the node test is expanded into an expanded-name using the namespace
    declarations from the expression context. This is the same way expansion is
    done for element type names in start and end-tags except that the default
    namespace declared with xmlns is not used: if the QName does not have a
    prefix, then the namespace URI is null (this is the same way attribute names
    are expanded). It is an error if the QName has a prefix for which there is no
    namespace declaration in the expression context.

  • Com.bea.wli.bpm.EventQueue vs com.bea.wlpi.EventQueue

    Hi
    Which event queue should be used if an external application wants to post a message
    to wli to be consumed by an event node?
    com.bea.wli.bpm.EventQueue vs com.bea.wlpi.EventQueue ????????
    I am using WLI 7.0 and tried with com.bea.wli.bpm.EventQueue but the event node
    doesn't seem to be consuming the messages at all.
    With com.bea.wlpi.EventQueue, the messages are being consumed but the event node
    is not necessarily waiting. Moreover com.bea.wlpi.EventQueue is not listed at
    all in the weblogic admin console.
    Any comments
    -Thanks
    Sreeram

    Hi Sreeram,
    The WLI_BPM_Event (com.bea.wli.bpm.Event) queue is the default event
    queue for BPM. Here is a link that describes how to take a JMS message
    and deliver it to BPM process engine:
    http://e-docs.bea.com/wli/docs70/devclient/jms.htm
    Cheers,
    Chris
    Sreeram wrote:
    Hi
    Which event queue should be used if an external application wants to post a message
    to wli to be consumed by an event node?
    com.bea.wli.bpm.EventQueue vs com.bea.wlpi.EventQueue ????????
    I am using WLI 7.0 and tried with com.bea.wli.bpm.EventQueue but the event node
    doesn't seem to be consuming the messages at all.
    With com.bea.wlpi.EventQueue, the messages are being consumed but the event node
    is not necessarily waiting. Moreover com.bea.wlpi.EventQueue is not listed at
    all in the weblogic admin console.
    Any comments
    -Thanks
    Sreeram

  • Application view creation in WLI SERVER

              Hi folks,
              w,r.to my previous mail,Iam getting the following errors while i try to login
              to the Application view console in WLI
              Server.pl. anyone try to help me to sort this problem.Iam new to WLI Server.
              <Cannot startup connection pool "wliPool" java.sql.SQLException: No suitable driver>
              <Jun 13, 2003 5:02:45 PM IST> <Error> <JDBC> <001059> <Error during Data Source
              creation: weblogic.common.ResourceException: DataSource(WLAI_DataSource) can't
              be created with non-existent Pool (connection or multi) (wliPool)
              at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
              at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:260)
              at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
              at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
              <Jun 13, 2003 5:02:49 PM IST> <Alert> <JMS> <040052> <JMSServer "WLIJMSServer",
              store failed to open, java.io.IOException: JMS JDBC store, connection pool = <wliPool>,
              prefix = <myserver___PBPUBLIC>: connection pool does not exist.
              java.io.IOException: JMS JDBC store, connection pool = <wliPool>, prefix = <myserver___PBPUBLIC>:
              connection pool does not exist
              >
              <Jun 13, 2003 5:02:52 PM IST> <Error> <Connector> <190024> << Calumma LDAP JCA
              Resource Adapter_LdapConnector > Error making initial connections for pool. Reason:
              CreateManagedConnection Error: 192.168.66.144:389>
              <Jun 13, 2003 5:03:04 PM IST> <Error> <AI> <000000> <Failed to initialize the
              WLI-Application Integration enterprise application due to an exception while initializing
              JMS resources.
              com.bea.wlai.JMSResourceException: Failed to initialize the WLAI asynchronous
              service request JMS Queue 'WLAI_ASYNC_REQUEST_QUEUE' bound at JNDI context 'com.bea.wlai.ASYNC_REQUEST_QUEUE'.
              Root Cause: javax.naming.NameNotFoundException: Unable to resolve 'com.bea.wlai.ASYNC_REQUEST_QUEUE'
              Resolved: 'com.bea.wlai' Unresolved:'ASYNC_REQUEST_QUEUE' ; remaining name 'ASYNC_REQUEST_QUEUE'
              at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
              at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source)
              at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
              at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
              at javax.naming.InitialContext.lookup(InitialContext.java:347)
              at com.bea.wlai.JMSHelper.initQueue(Unknown Source)
              <Jun 13, 2003 5:03:05 PM IST> <Critical> <WebLogicServer> <000286> <Failed to
              invoke startup class "LwcStartup", java.lang.ClassNotFoundException: com.bea.lwclient.Startup>
              <Jun 13, 2003 5:03:07 PM IST> <Notice> <Management> <141052> <Application Poller
              started for development server.>
              <Jun 13, 2003 5:03:11 PM IST> <Error> <HTTP> <101165> <Could not load user defined
              filter: com.bea.b2b.transport.http.TransportServletFilter
              java.lang.ClassNotFoundException: com.bea.b2b.transport.http.TransportServletFilter
              at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:179)
              at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:62)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:262)
              at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
              at weblogic.servlet.internal.WebAppServletContext.loadClass(WebAppServletContext.java:4714)
              at weblogic.servlet.internal.WebAppServletContext.registerFilter(WebAppServletContext.java:2446)
              at weblogic.servlet.internal.WebAppServletContext.initFilters(WebAppServletContext.java:2433)
              at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:2703)
              at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:563)
              at weblogic.servlet.internal.WebService.preloadResources(WebService.java:476)
              at weblogic.t3.srvr.ServletInitRunner$1.run(ServletInitRunner.java:50)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
              at weblogic.t3.srvr.ServletInitRunner.run(ServletInitRunner.java:46)
              at java.lang.Thread.run(Thread.java:536)
              >
              <Jun 13, 2003 5:03:11 PM IST> <Error> <socket> <000433> <Unable to load performance
              pack, using Java I/O instead.
              Please ensure that libmuxer library is in :'/home/tsuresh/j2sdk1.4.0/jre/lib/i386/client:/home/tsuresh/j2sdk1.4.0/jre/lib/i386:/home/tsuresh/j2sdk1.4.0/jre/../lib/i386'
              java.lang.UnsatisfiedLinkError: no muxer in java.library.path
              java.lang.UnsatisfiedLinkError: no muxer in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1410)
              at java.lang.Runtime.loadLibrary0(Runtime.java:772)
              at java.lang.System.loadLibrary(System.java:832)
              at weblogic.socket.PosixSocketMuxer.<init>(PosixSocketMuxer.java:180)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
              at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
              at java.lang.Class.newInstance0(Class.java:296)
              at java.lang.Class.newInstance(Class.java:249)
              at weblogic.socket.SocketMuxer.makeTheMuxer(SocketMuxer.java:54)
              at weblogic.socket.SocketMuxer.getMuxer(SocketMuxer.java:37)
              at weblogic.t3.srvr.ListenThread.run(ListenThread.java:205)
              >
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <Management> <141030> <Starting discovery
              of Managed Server... This feature is on by default, you may turn this off by passing
              -Dweblogic.management.discover=false>
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <WebLogicServer> <000354> <Thread "ListenThread.Default"
              listening on port 7010>
              <Jun 13, 2003 5:03:12 PM IST> <Notice> <WebLogicServer> <000331> <Started WebLogic
              Admin Server "myserver" for domain "ldap_adapterdomain" running in Development
              Mode>
              <Jun 13, 2003 5:03:15 PM IST> <Notice> <WebLogicServer> <000365> <Server state
              changed to RUNNING>
              <Jun 13, 2003 5:03:15 PM IST> <Notice> <WebLogicServer> <000360> <Server started
              in RUNNING mode>
              <Jun 13, 2003 5:04:18 PM IST> <Error> <AI> <000000> <Could not create NamespacePersistence
              Object.
              -------- Begin level 0 Exception Stack Trace --------
              com.bea.wlai.repository.PersistenceException: Failed to initialize WLI repository
              access layer for the Application Integration subcomponent because the JDBC data
              source was not found at JNDI name WLAI_DataSource due to Unable to resolve 'WLAI_DataSource'
              Resolved: '' Unresolved:'WLAI_DataSource'
              at com.bea.wlai.repository.NamespacePersistence.initDataSource(Unknown
              Source)
              at com.bea.wlai.repository.NamespacePersistence.<init>(Unknown Source)
              at com.bea.wlai.NamespaceManagerImpl.<init>(Unknown Source)
              at com.bea.wlai.NamespaceManagerImpl.getInstance(Unknown Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean.establishImpl(Unknown
              Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean.ejbCreate(Unknown Source)
              at com.bea.wlai.client.bean.NamespaceManagerBean_k6j0cj_Impl.ejbCreate(NamespaceManagerBean_k6j0cj_Impl.java:122)
              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.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
              at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:101)
              at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:142)
              at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:127)
              at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:61)
              at com.bea.wlai.client.bean.NamespaceManagerBean_k6j0cj_EOImpl.getRootNamespace(NamespaceManagerBean_k6j0cj_EOImpl.java:83)
              at jsp_servlet.__nshierarchy._jspService(__nshierarchy.java:115)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
              at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:543)
              at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:369)
              at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:136)
              at jsp_servlet.__display._jspService(__display.java:511)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
              rgds
              Suresh.K
              

    1) http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=4
              2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd
              3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.
              http://dev2dev.bea.com/codelibrary/code/examples_jdbc.jsp

  • Calling A Secured webservice using Username and password in the Soap header

    I want to call a secured webservice.
    The Username and password should be sent with the payload in the SOAP Header
    as
    <wsse:Security S:mustunderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken wsu:Id="SecurityToken-XXXXXXXXXXXXXXXXXXXXXXXXX" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:Username>uname</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pwd</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    Can you please send me the steps?
    I tried with giving the username and password under Service Account.
    I tried to create a wspolicy under business service. But nothing works...
    Please help me at the earliest.
    Also please give me steps in sequence.

    Now i made sure that the endpoint is available!
    Now am getting this error:
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>BEA-380002: localhost1</faultstring>
    <detail>
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-380002</con:errorCode>
    <con:reason>localhost1</con:reason>
    <con:location>
    <con:node>RouteNode1</con:node>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    </detail>
    </soapenv:Fault>
    Also in the invocation trace i can observe the following things:
    Under Invocation Trace:-
    ========================
         Receiving request =====> Initial Message context
         ===============================================
         under added header:-
         ==================
         <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
         </soap:Header>
         under RouteNode1
    ================
         Route to "TargetMyService_BS"
    $header (request):-
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    Under Message Context changes:-
    *===============================*
    I can find this element also:-
    con:security>
    *<con:doOutboundWss>false</con:doOutboundWss>*
    *</con:security>*
    eventhough we enabled ws security, how the above tag can be false?
    I think its getting failed to populate the header with the required login credentials.
    The other doubt i have is:-
    =================
    I have chosen the service account type is static...is this right?

  • Problem creating user in RDBMS realm Using com.bea.wlpi.rdbmsrealm.RDBMSRealm

    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file. As far
    as I understand, the caching realm entry has attribute pointing to the wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through the
    console. I get no error message and it seems to work fine. ( I also click on the
    save it to database link, and it returns with msg that cache is refreshed ).
    3: I see an entry in the fileRealm.properties file, but no record is inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the WLI ?
    Is there anything that I have not configured here that is causing this behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish
    [noaa1.zip]

    Hi,
    I turned on the caching realm through the WLS Console, (Security).
    After this I get a very unusual error, which seems to be comming
    from the RDBMS implementation class (from WLI 2.0 SP2 distribution).
    Here is the msg that I get while WLS server boots (the WLS server boots ok, but
    WLPI does not initialize) ....
    Unable to initialize WebLogic Process Integrator:
    SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.j_(Unknown Source)
    at c8e.k.n.checkIfClosed(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.next(Unknown Source)
    at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.getGroup(RDBMSDelegate.java:425)
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:235)
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <WebLogic Server started>
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    com.bea.wlpi.rdbmsrealm.RDBMSException: caught SQL exception - with nested exception:
    [SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.]
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:242)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <ListenThread listening
    on port 7101>
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "Girish Gupte" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual
    thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file.
    As far
    as I understand, the caching realm entry has attribute pointing to the
    wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through
    the
    console. I get no error message and it seems to work fine. ( I also click
    on the
    save it to database link, and it returns with msg that cache is refreshed
    3: I see an entry in the fileRealm.properties file, but no record is
    inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead
    of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the
    WLI ?
    Is there anything that I have not configured here that is causing this
    behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish

  • SOAP Attachment & performances for WLI

    Dear all,
    I am implementing webservices, accepting a SOAP attachment as parameter. The implementation is based on Workshop / WLI jws file. The web service is RPC style since WorkShop is unable to generate a correct WSDL file with SOAP atttachment & document style (known limitation from BEA).
    My problem is concerning attachments. Indeed, in my mind, attaachement are there in order to prevent extra load into the XML parser and to speedup processing and avoid heavy use of memory.
    So I made some tests with a simple soap request and attachments. Here are the results (I calculate the time to send and receive response from web service), the web service itself just prints the content type, anything else.
    Attachement size | Time
    39 kb 344ms
    78 kb 406ms
    155 kb 484ms
    300 kb 750ms
    463 kb 1000ms
    1389 kb 4600ms
    2700 kb 23609ms
    5500 kb 140000ms
    Of course, the client and server are running on the same machine and are using the loopback interface. So there is no network bootleneck to take into account.
    As conclusion, we can see that for small messages, (<300kb) the curve is good... But performances start to fall drastically with messages larger than 300kb. This is not a problem of memory but CPU usage (fully used diring the 1400 seconds).
    Any idea, any opened cases ?
    Thansk for all,
    Pascal Bourgeois

    This post :
    http://soastuff.wordpress.com/2007/06/06/handling-opaque-datatypes-in-bpelesb/
    Describes how to use the opaque-schema for sending files over the ESB.
    Hope you can use this.
    or do you want to use the soap-headers for this?

  • WLI 8.1SP2 Cluster over 2 Physical Machines Errs on Managed Svrs on 2nd mac

    I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
    While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
    ####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
    >
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
    Listen Address informatica-svr:7001
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
    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>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
    ####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<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.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
    ####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
    weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
    at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
    at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    >
    ####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]>

    I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
    While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
    ####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
    >
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
    Listen Address informatica-svr:7001
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
    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>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
    ####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<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.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
    ####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
    weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
    at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
    at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    >
    ####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]>

  • Invoking WLI 9.2 Process as a web service

    Hello All,
    Does someone know how to publish WLI Process as a web service and invoke it through command line?
    If yes, then please comment with the necessary information.
    Thanks & Regards,
    Anand K Singh

    I dont think what is the issue that you have here. Now there are multiple ways to expose a WLI process as a webservice.
    1. The WLI workshop allows you to direcly expose a .jpd file (process file) as a WSDL.
    2. In case you want you Web service to have multiple methods for different processes, create a process control from the .jpd file and then create a Weblogic Webservice using these controls.
    Hope this helps.

  • Invoking wli process as web service

    Hello,
    I've developed a WLI process which I want to access as web service.
    I'm using conversation as explained in
    "How Do I: Tell Developers of Non-WebLogic Workshop Clients How to Participate in Conversations?"
    http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
    But I don't know how to access this web service and to set the conversationID in the SOAP header.
    Thanks a lot.
    Victor.

    I dont think what is the issue that you have here. Now there are multiple ways to expose a WLI process as a webservice.
    1. The WLI workshop allows you to direcly expose a .jpd file (process file) as a WSDL.
    2. In case you want you Web service to have multiple methods for different processes, create a process control from the .jpd file and then create a Weblogic Webservice using these controls.
    Hope this helps.

  • Differences between WLI 7.0 and WLI 8.1?

    I am trying to make a determination on Workflow products, and I have used WLI 7.0
    (and back to WLPI days), but 8.1 looks very foreign to me.
    Can anyone give me an idea of whether you think the modifications to the tool
    for 8.1 were beneficial from the standpoint of functionality and ease of use?
    Did it lose anything that was good about the tool from prior releases? Did it
    gain anything?
    Or if anyone knows of a article or place that might tell me this information (I
    didn't get much out of the "What's new in this release").
    So far, one thing that I don't think I like is the fact that there does not seem
    to be a visual representation of a task anymore. With the "controls", it looks
    like what you see in the graphical view of the process is a method (or several
    methods) from a "control" rather than an actual task object.
    Thanks in advance,
    Andy

    Hi Yamini,
    The Release Notes list the new functionality and are available on OTN at http://docs.oracle.com/cd/E22582_01/v121_release_notes.pdf
    You can find the rest of the documentation for Documaker there as well at http://www.oracle.com/technetwork/documentation/insurance-097481.html#Documaker
    If you are interested in bug fixes and minor adjustments then you should check out the readme that is included with each new release on EDelivery. Simply download Documaker and inside the zip package you'll find a readme listing all the minor changes and bug fixes.
    -DA

  • How to define callback in conversation webservice on WLS

    Hello,
    I have a very simple Conversation WS (source included) for WebLogic and I like to use it in BPEL process. But BPEL Designer does not recognize callback method. I can see callback method as standard WS operation for synchronous call. Please help me. When I use this WS in WLI (Web Logic Integration Server) everything is ok.
    Thank you for your help.
    JMELICHN
    --- Code of WS: --------------------------------------
    package ws;
    public class SimpleAsynchrWS implements com.bea.jws.WebService
    * @common:control
    * @jc:timer timeout="10 s"
    private com.bea.control.TimerControl timer;
    public Callback callback;
    static final long serialVersionUID = 1L;
    private String internal = "";
    * @common:operation
    * @jws:conversation phase="start"
    public void setString(String text)
    this.internal = text;
    this.timer.start();
    return;
    public interface Callback extends com.bea.control.ServiceControl
    * @jws:conversation phase="finish"
    void textCallback(String text);
    public void timer_onTimeout(long time)
    callback.textCallback(internal);
    timer.stop();

    I'm allmost sure that they are using SOAP converation. I attached WSDL generated for my service:
    <?xml version="1.0" encoding="utf-8" ?>
    - <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.openuri.org/">
    - <types>
    - <s:schema xmlns:s="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.openuri.org/">
    - <s:element name="setString">
    - <s:complexType>
    - <s:sequence>
    <s:element name="text" type="s:string" minOccurs="0" />
    </s:sequence>
    </s:complexType>
    </s:element>
    - <s:element name="setStringResponse">
    - <s:complexType>
    <s:sequence />
    </s:complexType>
    </s:element>
    - <s:element name="textCallbackResponse">
    - <s:complexType>
    <s:sequence />
    </s:complexType>
    </s:element>
    - <s:element name="textCallback">
    - <s:complexType>
    - <s:sequence>
    <s:element name="text" type="s:string" minOccurs="0" />
    </s:sequence>
    </s:complexType>
    </s:element>
    </s:schema>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.openuri.org/2002/04/soap/conversation/">
    <s:element name="StartHeader" type="conv:StartHeader" />
    <s:element name="ContinueHeader" type="conv:ContinueHeader" />
    <s:element name="CallbackHeader" type="conv:CallbackHeader" />
    - <s:complexType name="StartHeader">
    - <s:sequence>
    <s:element minOccurs="0" maxOccurs="1" name="conversationID" type="s:string" />
    <s:element minOccurs="0" maxOccurs="1" name="callbackLocation" type="s:string" />
    </s:sequence>
    </s:complexType>
    - <s:complexType name="ContinueHeader">
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="conversationID" type="s:string" />
    </s:sequence>
    </s:complexType>
    - <s:complexType name="CallbackHeader">
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="conversationID" type="s:string" />
    </s:sequence>
    </s:complexType>
    </s:schema>
    </types>
    - <message name="setStringSoapIn">
    <part name="parameters" element="s0:setString" />
    </message>
    - <message name="setStringSoapOut">
    <part name="parameters" element="s0:setStringResponse" />
    </message>
    - <message name="textCallbackSoapIn">
    <part name="parameters" element="s0:textCallbackResponse" />
    </message>
    - <message name="textCallbackSoapOut">
    <part name="parameters" element="s0:textCallback" />
    </message>
    - <message name="setStringHttpGetIn">
    <part name="text" type="s:string" />
    </message>
    <message name="setStringHttpGetOut" />
    <message name="textCallbackHttpGetIn" />
    - <message name="textCallbackHttpGetOut">
    <part name="text" type="s:string" />
    </message>
    - <message name="setStringHttpPostIn">
    <part name="text" type="s:string" />
    </message>
    <message name="setStringHttpPostOut" />
    <message name="textCallbackHttpPostIn" />
    - <message name="textCallbackHttpPostOut">
    <part name="text" type="s:string" />
    </message>
    - <message name="StartHeader_literal">
    <part name="StartHeader" element="conv:StartHeader" />
    </message>
    - <message name="CallbackHeader_literal">
    <part name="CallbackHeader" element="conv:CallbackHeader" />
    </message>
    - <portType name="SimpleAsynchrWSSoap">
    - <operation name="setString">
    <input message="s0:setStringSoapIn" />
    <output message="s0:setStringSoapOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackSoapOut" />
    <input message="s0:textCallbackSoapIn" />
    </operation>
    </portType>
    - <portType name="SimpleAsynchrWSHttpGet">
    - <operation name="setString">
    <input message="s0:setStringHttpGetIn" />
    <output message="s0:setStringHttpGetOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackHttpGetOut" />
    <input message="s0:textCallbackHttpGetIn" />
    </operation>
    </portType>
    - <portType name="SimpleAsynchrWSHttpPost">
    - <operation name="setString">
    <input message="s0:setStringHttpPostIn" />
    <output message="s0:setStringHttpPostOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackHttpPostOut" />
    <input message="s0:textCallbackHttpPostIn" />
    </operation>
    </portType>
    - <binding name="SimpleAsynchrWSSoap" type="s0:SimpleAsynchrWSSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    - <operation name="setString">
    <soap:operation soapAction="http://www.openuri.org/setString" style="document" />
    <cw:transition phase="start" />
    - <input>
    <soap:body use="literal" />
    <soap:header xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" wsdl:required="true" message="s0:StartHeader_literal" part="StartHeader" use="literal" />
    </input>
    - <output>
    <soap:body use="literal" />
    </output>
    </operation>
    - <operation name="textCallback">
    <soap:operation soapAction="http://www.openuri.org/textCallback" style="document" />
    <cw:transition phase="finish" />
    - <input>
    <soap:body use="literal" />
    </input>
    - <output>
    <soap:body use="literal" />
    <soap:header xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" wsdl:required="true" message="s0:CallbackHeader_literal" part="CallbackHeader" use="literal" />
    </output>
    </operation>
    </binding>
    - <binding name="SimpleAsynchrWSHttpGet" type="s0:SimpleAsynchrWSHttpGet">
    <http:binding verb="GET" />
    - <operation name="setString">
    <http:operation location="/setString" />
    <cw:transition phase="start" />
    - <input>
    <http:urlEncoded />
    </input>
    <output />
    </operation>
    - <operation name="textCallback">
    <http:operation location="/textCallback" />
    <cw:transition phase="finish" />
    - <input>
    <mime:mimeXml part="Body" />
    </input>
    - <output>
    <http:urlEncoded />
    </output>
    </operation>
    </binding>
    - <binding name="SimpleAsynchrWSHttpPost" type="s0:SimpleAsynchrWSHttpPost">
    <http:binding verb="POST" />
    - <operation name="setString">
    <http:operation location="/setString" />
    <cw:transition phase="start" />
    - <input>
    <mime:content type="application/x-www-form-urlencoded" />
    </input>
    <output />
    </operation>
    - <operation name="textCallback">
    <http:operation location="/textCallback" />
    <cw:transition phase="finish" />
    - <input>
    <mime:mimeXml part="Body" />
    </input>
    - <output>
    <mime:content type="application/x-www-form-urlencoded" />
    </output>
    </operation>
    </binding>
    - <service name="SimpleAsynchrWS">
    - <port name="SimpleAsynchrWSSoap" binding="s0:SimpleAsynchrWSSoap">
    <soap:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    - <port name="SimpleAsynchrWSHttpGet" binding="s0:SimpleAsynchrWSHttpGet">
    <http:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    - <port name="SimpleAsynchrWSHttpPost" binding="s0:SimpleAsynchrWSHttpPost">
    <http:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    </service>
    </definitions>
    I'd like to try definition of explicite correlationSet in BPEL, but i think that callback must be recognized.
    Thnak you for yor attention.
    JMELICHN

Maybe you are looking for

  • ODI with Sql Server

    Hi Frnds, I'm working on ODI 10g. JDK - 1.6 Version. I downloaded Sqljdbc4 jar file and placed it in Oracledi\drivers And, i was successfully able to connect to ms sql server 2000 DB i.e. able to insert data server with In definition tab - i gave dat

  • How can I disable prompt to ask viewers to dload Flash?

    Thanks to this forum, I now have a Flash video on my website. And I'm on a mac! Now, here' s my latest problem. When I added the Flash video, there was a selection in Dreamweaver where, when clicked, the page will prompt viewers who don't have the la

  • Rented a movie and it doesn't work at all, how do i get a refund?

    apple if you're reading this you have gotten seriously on my last nerves. i have been typing non stop trying to get my answer but you guys really have THE WORST  customer service. i tried renting a movie and it says that it need 55 hours to load and

  • Referencing a instance inside a Class

    Hi -- I am working on converting a movie clip to a Class so that I can more easily reuse it in later projects. I have pretty succesfully converted my AS code from my include file to a Class file. However, I have two objects on the stage, topBG and bo

  • Searching for function modul which insert adressdata bevor fm vendor_insert

    hello, i read many threads, but I find no solution. I want use the fm vendor_insert for a migration. But using the fm vendo_insert require an existing address entry. Is there any central fm which create the whole address. regards Kim Werner