EbXML 2.0 support in WLI

Hi all,
Is there any information available on when (or if) "ebXML 2.0" will be supported in WLI?
Thanks!
Jim

According to the current plans, we will have support for WSRP 2.0, which addresses most of the limitations of the portlet 1.0 spec (JSR 168).
Peter

Similar Messages

  • EDI support in WLI 8.1

    Hi,
    I am designing an application that will need to integrate with other systems using EDI and am trying to find out about support for EDI in the WebLogic platform. I've found some documentation for EDI in WLI 7.0 (http://e-docs.bea.com/wli/docs70/edi/index.htm) but can't find anything for 8.1 - has EDI support been dropped in 8.1?
    Francis

    If you are looking for doing EDI over internet, the most reliable solution would be to use Cyclone. You can consider using Cyclone Interchange as gateway to external EDI, then integrate Cyclone with WLI. The integration between CI and WLI can be either JMS or file based.
    Jack

  • Transaction support in WLI

    We have multiple EIS for which we have resource adapters used to integrate them in the WLI space. We need transaction capability. How do i handle the same as a single transaction?
    For example: We have 2 legacy systems which listen on sockets for incomming requests.Now, we have 2 socket adapters to include them in the WLI business process definition. These 2 EIS are not XA compliant and need transaction coordination. Based on the response from the first EIS, we need to invoke the second EIS. Can we handle these conditions as a single transaction? If so, please provide some directions.
    Regards,

    While going through the availaible documentation, i came across this: "You can have only one local-only resource in the transaction. The business process designer must ensure that only one local resource gets enlisted anywhere within a given set of explicit transaction tags (or the implicit outer transaction tags if none are given explicitly). If a second local-only resource is required, you must separate the first and second resources across transaction tags in the process definition language."
    Does this mean that we cannot handle more than 1 local resource in one transaction?

  • Windows 7 and Wireless N

    I'm on my second USB wireless N network device and my PC on Windows 7 is still only operating on B and G. I have tried to set the time capsole to manually seperate the 2.4ghz from the 5ghz, but my PC still doesn't see the 5ghz network.  My new TV and my tivo both can connect to the faster channel.
    I believe there is an issue with the network settings on my PC but I am not sure what to change. I have a bufflow adapter WLI-UC-GN.
    My Macbookpro also has no trouble connecting at 300bps. Is there some kind of conflict between the apple and windows software? Has anyone
    had a simular situation to mine and fixed it?

    ...but my PC still doesn't see the 5ghz network...I have a bufflow adapter WLI-UC-GN....
    Does it support 5GHz?  If the below link is the correct user manual, it only mentions 2.4 and not 5GHz.
    http://www.buffalotech.com/support/getfile/wli-uc-gn_manual.pdf

  • Windows Applications and AirPort N

    I have a W2k PC on my LAN hardwired to an Airport Ethernet port. A web log analysis application runs weekly reports to co-located servers across town. The application uses FTP to access the web logs and to post HTML reports. Since switching from my Belkin router to the AirPort Extreme N the application will not work. I have Internet access on the PC. I can access the logs using the application configuration tool but the reports fail due to the FTP connection being dropped.
    Any help in resolving this issue would be greatly appreciated.
    Thanks
    JA
    Dual 2.7 G5   Mac OS X (10.4.8)  

    ...but my PC still doesn't see the 5ghz network...I have a bufflow adapter WLI-UC-GN....
    Does it support 5GHz?  If the below link is the correct user manual, it only mentions 2.4 and not 5GHz.
    http://www.buffalotech.com/support/getfile/wli-uc-gn_manual.pdf

  • JMS headers for supporting ebxml attachments

    Hi,
    We have just tried out the attachment support in ebxml. it seems to be working fine with using AQ headers but it is failing for JMS headers. Can you please give us the exact headers for JMS for attachment? Waiting for an early reply.
    Thanks
    Kavitha

    Thanks all for the prompt replies.
    It works fine with the JMS header ATTACHMENT. The error we got was something unrelated to this and we solved that issue. We are using Oracle 10g.
    As of now, we are using standalone jms stub to post the message. We will try to integrate this with WLI(JMS) and let you know if we face any issues.
    Regards
    Kavitha

  • Attachment support in ebXML

    Hi,
    Is it possible to support attachments in ebxml protocol in Oracle B2B? If so, can you please give me the details or point me to the URL where I could get this. Is there a way to strip the attachment coming in the ebxml message and place it on some directory(which is configurable).
    Thanks...
    kavitha

    Are you using 10g or 11g ?
    For 10g ,Refer to below link:
    http://www.b2bgurus.com/2008/11/attachment-feature-in-ebms-using-oracle.html
    Rgds,
    Nitesh

  • Support for ebxml in BizTalk

    Hi,
    I read a couple of threads about ebxml and BizTalk. It seems that BizTalk does not have support for ebxml outofthebox.
    I noticed that there are a couple of 3:rd-party solutions (Covast for example), but my question is if Microsoft will have this kind of ebxml support outofthebox in coming versions ocf BizTalk.
    Regards,
    Daniel
    DW

    Hi Daniel,
    I think Covast solution is best bet for now and coming years. They have team supporting this solution. If you view last part of this
    presentation
    given during last TechEd 2010 (November Berlin) you will see what will be coming in next couple of years. Depending on demand by customers it could turn up as feature in next version. I wouldn't wait for that if I had a requirement for this from a
    customer.
    HTH
    Regards,
    Steef-Jan Wiggers
    MVP & MCTS BizTalk Server
    http://soa-thoughts.blogspot.com/
    If this answers your question please mark it accordingly
    BizTalk

  • WLI 10.2 Support for oracle 10GR2 or not .......

    We are evaluating ALSB 3.0 with WLI 10.2 and we would like to use Oracle RAC 10GR2.
    The BEA article at http://edocs.bea.com/platform/suppconfigs/configs102/102_over/supported_db.html#1178367
    suggests that WLI 10.2 is not supported with Oracle RAC 10GR2.
    I find this surprising since we are currently using WLI 8.1 SP4 with Oracle 9i RAC and its supported and its also possible to use WLI 9.2 with Oracle RAC 10GR2 according to this article http://edocs.bea.com/platform/suppconfigs/configs92/92_over/supported_db.html#1177976
    and assuming you apply the appropriate Patch ID: 1VLA, Pass code: SJ88M5JJ
    Anyone have any ideas on why WLI 10.2 is not supported with Oracle RAC 10GR2 as its an important architectural issue for us if we can not use RAC. Also does anyone know if BEA has any plans and timescales for when they will be supoporting Oracle RAC with WLI 10.2 ?

    As luck would have it CR370015 was submitted to request a post GA certification of WLI 10.2 with Oracle RAC and it passed in the last few days. The docs have been updated to remove the comment on WLI not being supprted. See http://edocs.bea.com/platform/suppconfigs/configs102/102_over/supported_db.html#1178367
    :-D

  • Does WLI support Transaction on multiple pools ?

    hI,
    I use WLI 2.0 SP 2.
    I am working with JDBC POOL (My Pool) that is different from the WLI Pool.
    I run a WLI flow that use some business operations that use 'My Pool'.
    When an exception occure and the trnsaction is rolled back the records that
    I insert using the 'My Pool' did not rolledback.
    When I am using one pool (WLI Pool) all the records are rolled back with no
    problems.
    Does WLI 2.0 support transaction on multiple jdbc pools ?
    Thanxs,
    Ronen Yaari

    Why is it worth 100 hours of your time to remove them?
    (While I think_if_ there is a way to do what you want.)

  • JCA Support in WLS 7.0... is WLI required?

              I've been digging into the documentation of the Administration guide and documentation
              about WLI. WLI makes it sound like it is required to use JCA Resource adapters.
              I can't find any topics in the administration guide for WLS which cover JCA.
              With this I assumed that WLI is required, but when I read thru messages here
              I find ones that sound like all you need is WLS and the control pannel has options
              for JCA.
              Can anyone clear this up for me.
              Thanks,
              Michael
              

    Hi Michael,
              As per as I know, If you want to work with JCA adapters developed by BEA
              weblogic by using WLI. You can install specific WLI and can see/test the
              functionality with Weblogic server.
              But if you want to work with your own JCA adapter implementation to
              specified EIS like any RDBMS, MQSeries like systems, You can start
              implementing the JCA to develop adapter without WLI also.
              Please ignore this, if this is not answers your question.
              Thanks
              Kumar
              "Michael Caughey" <[email protected]> wrote in message
              news:3df7bda9$[email protected]..
              >
              > I found that WLI IS required for MQ Series Adapter. Is this true for all
              JCA adapters.
              >
              > "Michael Caughey" <[email protected]> wrote:
              > >
              > >I've been digging into the documentation of the Administration guide
              > >and documentation
              > >about WLI. WLI makes it sound like it is required to use JCA Resource
              > >adapters.
              > > I can't find any topics in the administration guide for WLS which cover
              > >JCA.
              > > With this I assumed that WLI is required, but when I read thru messages
              > >here
              > >I find ones that sound like all you need is WLS and the control pannel
              > >has options
              > >for JCA.
              > >
              > >Can anyone clear this up for me.
              > >
              > >Thanks,
              > >Michael
              >
              

  • 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

  • Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

    hi,erveryone,
    one difficult question need help.
    Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
    when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
    wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
    archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
    following steps:
    (1) in WLI console, delete wli.internal.worklist.timer.queue;
    (2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
    (3) restart wli server.
    after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    java.sql.SQLException: Transaction rolled back: Unknown reason.
    java.sql.SQLException: Transaction rolled back: Unknown reason
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1055)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1165)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
    is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
    archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
    completely override by <BEA-010049> excetpion.
    I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
    found that in statistics table :
    ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
    attachment)
    WorklistTimerMDB: transaction rollback ratio = 99.97%
    It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
    output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
    to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
    transaction-attribute from 'Required' to 'RequiresNew'.
    $weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
    <ejb-name>CommentBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>ListenerBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
    RequiresNew.
    </container-transaction>
    <container-transaction>
    really it works, the log file output resume normal. But there are still some problems:
    (1) this exception is still exist:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
    (2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
    (3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
    ####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    How can I solve these problem ? any suggestion is warm welcome.
    Thanks in advance.
    Great Lou

    Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
    Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
    Using Setup Assistant
    Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
    If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

  • 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]>

  • How to do a service callout to a service with/without MTOM support

    I have a problem trying to call a business service from a proxy service as a service callout related to MTOM.
    Specifically, the service I have is a Java based web service with the following signature:
    void archive(byte[] bytes, String fileName)
    When the WSDL is generated it maps the byte array to base64Binary as follows:
    <xs:element name="archive">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="bytes" type="xs:base64Binary"/>
    <xs:element name="fileName" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    Now in order to call this I try to build the XML payload withint the proxy message flow and I get this (from the logger):
    <8/06/2009 01:07:12 PM NZST> <Debug> <AlsbStagesTransformRuntime> <BEA-000000> <Service callout request payload:
    <archive xmlns="http://mtm.oracle.com/tools">
    <bytes>
    <con:binary-content ref="cid:518df4b0:121bd6029c5:-7fd9" xmlns:con="http://www.bea.com/wli/sb/context"/>
    </bytes>
    <fileName>RQRETMAINT20090608130711.csv</fileName>
    </archive>
    as you can see the bytes are being passed by reference and then when the service is called I get the following ("*non-MTOM endpoint received a MTOM message*") error:
    <8/06/2009 01:07:13 PM NZST> <Debug> <AlsbPipeline> <BEA-000000> <RegistryOutbound_SB_New/ProxyServices/ftpRqRetMaintToRegistry: +PipelineContextImpl.generateFault - messageID:2169050999921023879-518df4b0.121bd6029c5.-7fdc, errorCode:BEA-382500, errorReason:OSB Service Callout action received SOAP Fault response, errorDetails:<xml-fragment xmlns:con="http://www.bea.com/wli/sb/stages/transform/config">
    <con:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</con:faultcode>
    <con:faultstring>[Server CodecHandler] Failed to decode
    -> non-MTOM endpoint received a MTOM message</con:faultstring>
    <con:detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">weblogic.wsee.codec.CodecException: non-MTOM endpoint received a MTOM message
         at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:170)
         at etc
    </bea_fault:stacktrace>
    </con:detail>
    <con:http-response-code>500</con:http-response-code>
    </xml-fragment>>
    So it seems the business service expects the "bytes" passed by value whereas the proxy is passing by reference. I tried changing the proxy to not use MTOM by disabling XOP/MTOM support in the Message Content tab (actually I did this in the proxy that calls the one in question since it uses the local transport and so doesn't have such a tab) and leaving it enabled but pass by value and it had no effect for some reason.
    I've read the User Guide section on MTOM support but it was not that helpful so any pointers to better information would be much appreciated.
    regards
    Edited by: mdsrobbins on Jun 8, 2009 1:44 PM

    Can you test back-end MTOM end point through a route node and see if its working? I doubt the issue has nothing to do with SC but with the MTOM end-point implementation.
    non-MTOM endpoint received a MTOM message") error: hints that the service call out is sending a mtom message but the end-point is not accepting the message
    Manoj
    Edited by: mneelapu on Jun 8, 2009 11:25 AM

Maybe you are looking for

  • Problem with busy cursor

    IHey there, i have a popping up window in my Flex app. This window needs a little time to get created. In this time I want to set the Cursor to busy. But instead of the busy cursor Flex displays no cursor, also the arrow cursor disappears. I tried th

  • Cannot get Shuffle to be recognized by pc. Have went through asst. 5 times. Don't know what I am doing wrong.

    Cannot get Shuffle to be recognized by pc. Have went through asst. 5 times, don't know what to do now!!

  • G/L Account FS01(Mass-Recon Generation)

    Hi Friends, I'm developing an tool in ABAP , Where it should generate mass Recon account when we execute the program, In the Selection -Screen there will be one Referance(Title) G/L Account and Company Code in one frame in the second frame there will

  • Correction Invoice and "invalid document structure" problem

    Hello! Can anybody explain what properties are obligatory for correction invoices? I'm trying to add() one and it always say -5002: invalid document structure. In the CSI1 table I see linenum has to be unique, every baseline is twice. Do I make any s

  • Adobe Indesign CC 9.1 and Adobe Indesign CS6

    Hello, I am really new to indesign and bought Adobe Indesign CS6 for the office. I took a course on indesin and made a SWEET template for my work newsletter and was beyond thrilled to open it up at work. Well low and behold I go to open it and it say