Transactions across managed servers

          I have 2 managed servers S1 and S2. The Tx datasources (e.g. D1 and D2) in S1
          and S2 are different, with D1 deployed in S1 and D2 deployed in S2. Both Tx datasources
          shares the same db connection (Oracle). The EJB in S2 has the transaction attribute
          set as 'Required'. When a call is made within a JTA from S1 to an EJB residing
          in S2 (S1 begins a UserTransaction, makes a call to S2 and then tries to commit
          the transaction), I get the HeuristicMixedException. If the Tx attribute in S2
          changed to "NotSupported" or "RequiresNew", the exception disappears. What is
          going wrong here? Here is stack trace:
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],Xid=6:91439762e5aa8158(3104694),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since
          begin=1,seconds left=119,activeThread=Thread[ExecuteThread: '8' for queue:
          'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed
          ,assigned=sbmejbServer),SCInfo[sbm4.0+sbmejbServer]=(state=committed),SCInfo [sbm4.0+sbmServer]=(state=committed),properties=({weblogic.transaction.name=
          [EJB com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],
          weblogic.jdbc=t3://10.10.102.142:5134}),OwnerTransactionManager =ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm
          4.0+,
          Resources={})],CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm4.0+)
          completed heuristically:
          null>
          <Dec 17, 2002 6:36:16 AM PST> <Error> <EJB> <Exception
          during commit of
          transaction Name=[EJB com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],Xid=6:91439762e5aa8158(3104694),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=1,seconds left=119,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=sbmejbServer),SCInfo[sbm4.0+sbmejbServer]=(state=committed),SCInfo[sbm4.0+sbmServer]=(state=committed),properties=({weblogic.transaction.name=[EJB
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],
          weblogic.jdbc=t3://10.10.102.142:5134}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm
          4.0+, Resources{})],CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm4.0+):
          javax.transaction.HeuristicMixedException
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:236)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
          at
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean_fztxfh_EOImpl.
          connect(BLServerBean_fztxfh_EOImpl.java:4076)
          at
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean_fztxfh_EOImpl_
          WLSkel.invoke (Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274) at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteR
          equest.java:22)
          at
          weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

          I have 2 managed servers S1 and S2. The Tx datasources (e.g. D1 and D2) in S1
          and S2 are different, with D1 deployed in S1 and D2 deployed in S2. Both Tx datasources
          shares the same db connection (Oracle). The EJB in S2 has the transaction attribute
          set as 'Required'. When a call is made within a JTA from S1 to an EJB residing
          in S2 (S1 begins a UserTransaction, makes a call to S2 and then tries to commit
          the transaction), I get the HeuristicMixedException. If the Tx attribute in S2
          changed to "NotSupported" or "RequiresNew", the exception disappears. What is
          going wrong here? Here is stack trace:
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],Xid=6:91439762e5aa8158(3104694),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since
          begin=1,seconds left=119,activeThread=Thread[ExecuteThread: '8' for queue:
          'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed
          ,assigned=sbmejbServer),SCInfo[sbm4.0+sbmejbServer]=(state=committed),SCInfo [sbm4.0+sbmServer]=(state=committed),properties=({weblogic.transaction.name=
          [EJB com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],
          weblogic.jdbc=t3://10.10.102.142:5134}),OwnerTransactionManager =ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm
          4.0+,
          Resources={})],CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm4.0+)
          completed heuristically:
          null>
          <Dec 17, 2002 6:36:16 AM PST> <Error> <EJB> <Exception
          during commit of
          transaction Name=[EJB com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],Xid=6:91439762e5aa8158(3104694),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=1,seconds left=119,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=sbmejbServer),SCInfo[sbm4.0+sbmejbServer]=(state=committed),SCInfo[sbm4.0+sbmServer]=(state=committed),properties=({weblogic.transaction.name=[EJB
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean.connect(java.lang.String,java.lang.String)],
          weblogic.jdbc=t3://10.10.102.142:5134}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm
          4.0+, Resources{})],CoordinatorURL=sbmejbServer+10.10.102.142:5136+sbm4.0+):
          javax.transaction.HeuristicMixedException
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:236)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
          at
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean_fztxfh_EOImpl.
          connect(BLServerBean_fztxfh_EOImpl.java:4076)
          at
          com.savvion.sbm.bizlogic.server.ejb.BLServerBean_fztxfh_EOImpl_
          WLSkel.invoke (Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274) at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteR
          equest.java:22)
          at
          weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

Similar Messages

  • Replicating files across managed servers

              Hi there,
              I have a clustered environment with say 3 managed servers. One of the managed
              server (e.g. A) will try to download some files from a remote location periodically
              (for caching purposes).
              So, when a client tries to connect to the cluster (any of the managed server depending
              on the load balancer), I am supposed to serve the files to the client. My question
              is, say for e.g. server A downloaded the files to save in its local directory,
              how do I make these files replicated to other server as well. Or, how do I automatically
              direct the client to server A only when fetching the document is required?
              Suggestions? Many thanks in advance....
              

              Hi Oscar,
              Many thanks for your feedback and solution, I could give it a try... :)
              "Oscar Cristobal" <[email protected]> wrote:
              >
              >Hi.
              >I had pretty the same problem.
              >In my application, users can upload images.
              >If these images are in server 1, and one user tries to access these images
              >from
              >server 2, we get the same problem.
              >So we solved the situation like follows:
              >1.- When a user uploads an image, this image is saved in database.
              >2.- There is a daemon, running in every server, that checks (every 30secs)
              >if
              >there is any image in the database that is not at the server. If not,
              >it downloads
              >the image from the database. After all, it registers at the database
              >that server
              >X got the image.
              >3.- When all servers downloaded the image, daemon deletes it from the
              >database.
              >
              >That is my solution. I dont know if it can be used by you, because maybe
              >this
              >solution is only ok for low number of file updates.
              >I would like to know if somebody can provide some better solution.
              >
              >Thanks in advance
              >Oscar Cristobal
              >
              >
              >"Stephen S." <[email protected]> wrote:
              >>
              >>Hi there,
              >>
              >>I have a clustered environment with say 3 managed servers. One of the
              >>managed
              >>server (e.g. A) will try to download some files from a remote location
              >>periodically
              >>(for caching purposes).
              >>
              >>So, when a client tries to connect to the cluster (any of the managed
              >>server depending
              >>on the load balancer), I am supposed to serve the files to the client.
              >>My question
              >>is, say for e.g. server A downloaded the files to save in its local
              >directory,
              >>how do I make these files replicated to other server as well. Or, how
              >>do I automatically
              >>direct the client to server A only when fetching the document is required?
              >>
              >>Suggestions? Many thanks in advance....
              >
              

  • Exception when running transactions across 2 servers

              I have the following scenario, all happening within one transaction:
              - Session Bean is instantiated
              - Session Bean gets initial context and creates entity bean home interface and
              creates bean
              - Session Bean hands the entity bean to client.
              If I do this on one server with everything using the same initial context, everything
              works fine.
              But if I create the entity bean on a remote server through JNDI like I would in
              a Java application, I get the following exception:
              <Jul 12, 2001 3:03:42 PM EDT> <Error> <EJB> <Exception during commit of transact
              ion transaction=(IdHash=2954511,Name = [EJB UserBeanImpl.registerUser()],Xid=19:
              1cd29180e262f7f6,Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,second
              s since begin=0,seconds left=29,ServerResourceInfo[weblogic.jdbc.jts.Connection]
              =(state=new,assigned=none),SCInfo[localhost]=(state=active),SCInfo[localserver]=
              (state=active),properties=({weblogic.transaction.name=[EJB UserBeanImpl.register
              User()], weblogic.jdbc=t3://127.0.0.1:7001, weblogic.debug.DebugContext=weblogic
              .utils.DebugContext@6dcfde})): javax.transaction.SystemException: java.lang.Null
              PointerException
              at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.
              java:302)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
              sactionImpl.java:155)
              at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:2
              01)
              at com.clearpulse.ejb.UserBeanEOImpl.registerUser(UserBeanEOImpl.java:37
              at com.clearpulse.ejb.UserBeanEOImpl_WLSkel.invoke(UserBeanEOImpl_WLSkel
              .java:142)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:373)
              at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
              ef.java:128)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:237)
              at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              andler.java:118)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:17)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              I'm getting the initial context remotely through T3 using the Weblogic JNDI factory.
              But I'm getting this error when the transaction is committed.
              We're using Oracle's oracle.jdbc.driver.OracleDriver to connect to Oracle 8i.
              

    Hi Suraj,
    I think that the XI communication channel which i am using for my java server proxy is fine becoz after selecting XI as my adapter type then Adapter Engine contains Integration Server(by default) there i used to write the port number(in this case it is the port number of non central adapter engine where my proxy beans are deployed) as shown below:
    Adapter type: XI
    Adapter Engine: Integration Server.
    Addressing type: URL address
    Target Host: YYYY
    Service number: 51000( port number pointing towards the non central adapter engine installed)
    And also the message log which is coming under MDT is like this after running the scenario:
    2009-10-29 11:55:01 Information The message was successfully received by the messaging system. Protocol: XI URL: http://YYYY:51000/MessagingSystem/receive/JPR/XI Credential (User): XXXX
    2009-10-29 11:55:01 Information Using connection JPR. Trying to put the message into the receive queue.
    2009-10-29 11:55:01 Information Message successfully put into the queue.
    2009-10-29 11:55:01 Information The message was successfully retrieved from the receive queue.
    2009-10-29 11:55:01 Information The message status was set to DLNG.
    2009-10-29 11:55:01 Information Java Proxy Runtime (JPR) accepted the message.
    2009-10-29 11:55:24 Error JPR could not process the message. Reason: Cannot locate proxy bean JavaProxy3.
    2009-10-29 11:55:24 Error Delivering the message to the application using connection JPR failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean JavaProxy3.
    2009-10-29 11:55:24 Information The message status was set to WAIT.
    Please suggest some solution.
    Thanks
    Amit

  • Peter: A question about XA transactions across weblogic servers

    Peter,
              I just read your article about "javax.transaction.HeuristicMixedException"
              problem on WDJ.
              In the article, you said this case applies to WLS 6.1.
              I'd like to know does this applies to WLS 7.0?
              If not, what is the mechanism in WLS7.0 to cope with such problem?
              Thanks,
              William
              

    William,
              The same arguments that I ran through in the article apply to WLS 7. The
              solution is diferent, however since WLS 7 has no "system" user per se.
              Take a look at http://edocs.bea.com/wls/docs70/adminguide/managetx.html#1050458
              for the description of what you need to configure to get cross domain
              transactions with WLS 7.0
              Regards,
              Peter.
              william lee wrote:
              > Peter,
              >
              > I just read your article about "javax.transaction.HeuristicMixedException"
              > problem on WDJ.
              > In the article, you said this case applies to WLS 6.1.
              >
              > I'd like to know does this applies to WLS 7.0?
              >
              > If not, what is the mechanism in WLS7.0 to cope with such problem?
              >
              > Thanks,
              >
              > William
              >
              >
              >
              

  • Transaction span two WLS managed servers (non-clustering)

    (Weblogic 6.1 - non-clustering version)
    I have two managed servers configured on a single machine on different
    ports, and I am not using clustering weblogic. Assuming I have EJB A
    deployed on managed server 1, and EJB B deployed on managed server 2.
    I want to have EJB A to invoke EJB B. In EJB A, I guess I will
    probably create the InitialContext with the URL of managed server 2,
    then do the JNDI look up and call EJB B.
    My questions are:
    - Can weblogic handle transaction that spans two managed servers
    (non-clustering setting)?
    - Does weblogic use XA to handle transaction between managed servers?
    - Do I need to do any JTA code in order to achieve that (instead of
    just letting the EJB container to handle the transaction for me)?
    Thanks in advance!
    B.L.

    Hi,
    "benson" <[email protected]> wrote in message
    news:[email protected]..
    (Weblogic 6.1 - non-clustering version)
    I have two managed servers configured on a single machine on different
    ports, and I am not using clustering weblogic. Assuming I have EJB A
    deployed on managed server 1, and EJB B deployed on managed server 2.
    I want to have EJB A to invoke EJB B. In EJB A, I guess I will
    probably create the InitialContext with the URL of managed server 2,
    then do the JNDI look up and call EJB B.
    My questions are:
    - Can weblogic handle transaction that spans two managed servers
    (non-clustering setting)?Yes, it can.
    - Does weblogic use XA to handle transaction between managed servers?Yes, it does. Make sure you use TX DataSources. If the servers are connected
    to different databases, TX DataSources should be based on connection pools
    used XA drivers.
    - Do I need to do any JTA code in order to achieve that (instead of
    just letting the EJB container to handle the transaction for me)?No, you don't. WebLogic will take care about handling
    distributed TXs.
    Regards,
    Slava Imeshev

  • Managing the Principle and Mirrored DB's across 2 Servers.

    We have mirroring set up across 2 servers with a witness server.  A1, A2 and W1 respectively.  We have 16 Databases.  Can half of the DB's on A1 be the Principle, while A2 is the Principle for the other half?   Basically
    I want to understand if I can sort of balance the DB's across the 2 servers.  Some DB's being Principle on A1 and others on A2.

    Hi,
    Yes, you can configure some DB's being Principle on A1 and others on A2. Because Database Mirroring works at a database level.
    Please note that on a 32-bit system, database mirroring can support a maximum of about 10 databases per server instance because of the numbers of worker threads that are consumed by each database mirroring session. However, these restrictions
    do not apply on 64-bit SQL Server systems.
    More information, please see:
    Mirroring Multiple SQL Server Databases on a Single Instance
    http://blogs.technet.com/b/rob/archive/2010/02/11/mirroring-multiple-sql-server-databases-on-a-single-instance.aspx
    Best Regards,
    Tracy
    Tracy Cai
    TechNet Community Support

  • Using ATMI and tuxedo to institue distributed transactions across multiple DBs

    I am creating the framework for a given application that needs to ensure that data
    integrity is maintained spanning multiple databases not necessarily within an
    instance of weblogic. In other words, I need to basically have 2 phase commit
    "internet transactions" between a given coordinator and n participants without
    having any real knowlegde of their internal system.
    Originally I was thinking of using Weblogic but it appears that I may need to
    have all my particular data stores registered with my weblogic instance. This
    cannot be the case as I will not have access to that information for the other
    participating sytems.
    I next thought I would write my own TP...ouch. Everytime I get through another
    iteration I kept hitting the same issue of falling into an infinite loop trying
    to ensure that my coordinator and the set of participants were each able to perform
    the directed action.
    My next attempt has led me to the world of ATMI. Would ATMI be able to help me
    here. Granted I am using JAVA so I am assuming that I would have to use CORBA
    to make the calls but will ATMI enable me to truly manage and create distributed
    transactions across multiple databases. Please, any advice at all would be greatly
    appreciated.
    Thanks
    Chris

    Andy
    I will not have multiple instances of weblogic as I cannot enfore that
    the other participants involved in the transaction have weblogic as
    their application server. That being said, I may not have the choice
    but to use WTC.
    Does this make more sense?
    Andy Piper <[email protected]> wrote in message news:<[email protected]>...
    "Chris" <[email protected]> writes:
    I am creating the framework for a given application that needs to ensure that data
    integrity is maintained spanning multiple databases not necessarily within an
    instance of weblogic. In other words, I need to basically have 2 phase commit
    "internet transactions" between a given coordinator and n participants without
    having any real knowlegde of their internal system.
    Originally I was thinking of using Weblogic but it appears that I may need to
    have all my particular data stores registered with my weblogic instance. This
    cannot be the case as I will not have access to that information for the other
    participating sytems.I don't really understand this. From 6.0 onwards you can do 2PC
    between weblogic instances, so as long as the things you are calling
    are transaction (EJBs for instance) it should all work out fine.
    I next thought I would write my own TP...ouch. Everytime I get through another
    iteration I kept hitting the same issue of falling into an infinite loop trying
    to ensure that my coordinator and the set of participants were each able to perform
    the directed action.
    My next attempt has led me to the world of ATMI. Would ATMI be able to help me
    here. Granted I am using JAVA so I am assuming that I would have to use CORBA
    to make the calls but will ATMI enable me to truly manage and create distributed
    transactions across multiple databases. Please, any advice at all would be greatly
    appreciated.I don't see that ATMI would give you anything different. Transaction
    management Tux is fairly similar to WebLogic (it was written by the
    same people). If you are trying to do interposed transactions
    (i.e. multiple co-ordinators) then WTC would give you this but it is
    only a beta feature in WLS 6.1. Using Tux domain gateways would also
    give you interposed behaviour but would require you write your servers
    in C or C++ ....
    andy

  • Domain Created: Failed Restarting Managed Servers in a cluster

    Hi,
    I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
    Admin Server - adminServer - 1.1.1.19 - on port 7001
    Managed servers - machines:ip's - port
    1. mgndServer1 - 1.1.1.19 - 7011
    2. mgndServer2 - 1.1.1.20 - 7011
    mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
    node manager ; - 1.1.1.19 - 5555
    In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
    Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
    Log :
    <Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
    <Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
    <Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
    <Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
    <Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
    <Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
    <Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
    <Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
    <Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
    [java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
    java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
    at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
    [java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
    at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
    at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    <Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
    Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
    Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
    Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
    Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    Please help me in understand what went wrong here ? can anyone quickly guide me ..
    thanks
    patrick

    Hi Revanth,
    The issue seems to be with the JMX URL value defined in the 'server URL' property.
    Apparently I ran into the same issue as I was unable to access the Admin Server URL from the SMA.
    Changing the Host and Port value properly resolved the issue for me.
    Regards,
    Anandraj

  • Error : Running Managed Servers in a cluster

    Hi,
    I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
    Admin Server - adminServer - 1.1.1.19 - on port 7001
    Managed servers - machines:ip's - port
    1. mgndServer1 - 1.1.1.19 - 7011
    2. mgndServer2 - 1.1.1.20 - 7011
    mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
    node manager ; - 1.1.1.19 - 5555
    In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
    Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
    Log :
    <Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
    <Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
    <Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
    <Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    <Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
    <Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
    <Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
    <Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
    <Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
    <Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
    <Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
    [java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
    java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
    at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
    [java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
    at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
    at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    <Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
    Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
    Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
    Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
    Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    Please help me in understand what went wrong here ? can anyone quickly guide me ..
    thanks
    patrick

    Hi,
    <font color=red>OPTION-A)</font>
    If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
    If above one works fine...then Just try the following..
    Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
    Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
    for more informations Please refer to "nodemanager.properties" details:
    http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
    <font color=red>OPTION-B)</font>
    Start the ManagedServer using the StartScripts and then open the server OUT file....
    Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
    Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
    In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
    Now restart your Server using AdminConsole.
    Thanks
    Jay SenSharma
    Edited by: Jay SenSharma on Jan 30, 2010 10:55 PM

  • Unable to start the Managed servers OIM and SOA after starting the Weblogic

    Hi,
    We are unable to start the any manager servers after starting the weblogic Admin Server.
    We are getting the below error after trying to start the OIM or SOA managed servers.
    Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
         java.net.BindException: Address already in use
    We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
    Please help us to start the managed servers in the weblogic 10.3.5.
    Thanks.

    We are getting the below errors after starting the Admin server and Managed servers.
    Admin Server:
    <Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
    Managed Server:
    Starting WLS with line:
    /opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
    Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
         java.net.BindException: Address already in use
    We have to find out why the port 5555 is in listening mode after starting the Admin server.

  • Using ATMI and tuxedo for distrubuted transactions across multiple DBs

              I am creating the framework for a given application that needs to ensure that data
              integrity is maintained spanning multiple databases not necessarily within an
              instance of weblogic. In other words, I need to basically have 2 phase commit
              "internet transactions" between a given coordinator and n participants without
              having any real knowlegde of their internal system.
              Originally I was thinking of using Weblogic but it appears that I may need to
              have all my particular data stores registered with my weblogic instance. This
              cannot be the case as I will not have access to that information for the other
              participating sytems.
              I next thought I would write my own TP...ouch. Everytime I get through another
              iteration I kept hitting the same issue of falling into an infinite loop trying
              to ensure that my coordinator and the set of participants were each able to perform
              the directed action.
              My next attempt has led me to the world of ATMI. Would ATMI be able to help me
              here. Granted I am using JAVA so I am assuming that I would have to use CORBA
              to make the calls but will ATMI enable me to truly manage and create distributed
              transactions across multiple databases. Please, any advice at all would be greatly
              appreciated.
              Thanks
              Chris
              

              I am creating the framework for a given application that needs to ensure that data
              integrity is maintained spanning multiple databases not necessarily within an
              instance of weblogic. In other words, I need to basically have 2 phase commit
              "internet transactions" between a given coordinator and n participants without
              having any real knowlegde of their internal system.
              Originally I was thinking of using Weblogic but it appears that I may need to
              have all my particular data stores registered with my weblogic instance. This
              cannot be the case as I will not have access to that information for the other
              participating sytems.
              I next thought I would write my own TP...ouch. Everytime I get through another
              iteration I kept hitting the same issue of falling into an infinite loop trying
              to ensure that my coordinator and the set of participants were each able to perform
              the directed action.
              My next attempt has led me to the world of ATMI. Would ATMI be able to help me
              here. Granted I am using JAVA so I am assuming that I would have to use CORBA
              to make the calls but will ATMI enable me to truly manage and create distributed
              transactions across multiple databases. Please, any advice at all would be greatly
              appreciated.
              Thanks
              Chris
              

  • While starting managed servers asks for password of localhost

    We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
    The problem I have narrowed down is that there are startup.properties file for the managed servers.
    It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
    While SOA1 it is asking for password for the above host and the managed server is not starting.
    Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
    Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
    I could not yet figure out why it is behaving differently in the first node.
    This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
    It works perfectly in production environment.

    Hi
    Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
    ../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
    If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
    Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
    username=domainadminusername
    password=doaminadminpassword
    When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
    In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
    Exmaple locations:
    On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
    On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
    You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
    Thanks
    Ravi Jegga

  • Management Servers in untrusted domains

    Hi,
    I am planning a deployment of SCOM 2012 R2 and have several questions regarding the appropriate placement of management and gateway servers.
    The environment has multiple untrusted domains and need to monitor both Windows and Linux computers on both sides of the firewall. The main domain has 1500 Windows computers and 1300 Linux computers. The untrusted domain has 250 Windows servers and
    450 Linux servers.
    It is understandable that gateway servers are utilized to communicate across the firewall.
    The questions are:
    1. Is it possible to locate one or more management servers in the untrusted domain for the Linux servers and another management server to work with the Windows servers and have those management servers in the untrusted domain communicate through the firewall
    via gateway servers to the databases in the main domain?
    2. If it is not possible to have management servers in the untrusted domain communicate via the gateways; how many gateways would be required to relay to the management servers in the main domains management group?
    3. With the number of Linux servers in the untrusted domain is it better to install a separate management group there?
    Thanks, for any advice in dealing with the above scenario.
    --SG

    Hi There,
    Microsoft recommends you to place all the management servers in the same data center so if 1 goes down the other comes to know about it asap.
    If you place it in another location then fail over may happen late.
    Also you have mentioned to place the management servers in another domain, Which is possible but you need to have trust and permission stuff which is a very hectic work.
    So i would suggest you to place gateways as it will help in compression if the network bandwidth is low between the domains and sites.
    And based on the MS's Sizing and management options a Gateway server can manage 100 Unix boxes for a dedicated gateway server and 500 per management server on the same domain.
    So based on your situation as below:
    1300 Linux - Same domain
    450 - Different domain
    3 Management servers for the main domain for dedicated Linux
    1 MS For Windows Agent monitoring.
    Totally 4 in a management group for the same domain one.
    1 Separate management group with 1 MS will be fine for dedicated Linux monitoring for the 450 servers in the other domain.
    If you want to still place gateways then you will need to place 5 Gateway servers which is difficult to manage.
    Operations Manager supports the following number of monitored items.
    Monitored item
    Recommended limit
    Simultaneous Operations consoles
    50
    Agent-monitored computers reporting to a management server
    3,000
    Agent-monitored computers reporting to a gateway server
    2,000
    Agentless Exception Monitored (AEM)-computers per dedicated management server
    25,000
    Agentless Exception Monitored (AEM)-computers per management group
    100,000
    Collective client monitored computers per management server
    2,500
    Management servers per agent for multihoming
    4
    Agentless-managed computers per management server
    10
    Agentless-managed computers per management group
    60
    Agent-managed and UNIX or Linux computers per management group
    6,000 (with 50 open consoles); 15,000 (with 25 open consoles)
    UNIX or Linux computers per dedicated management server
    500
    UNIX or Linux computers monitored per dedicated gateway server
    100
    Network devices managed by a resource pool with three or more management servers
    1,000
    Network devices managed by two resource pools
    2,000
    Agents for Application Performance Monitoring (APM)
    700
    Applications for Application Performance Monitoring (APM)
    400
    URLs monitored per dedicated management server
    3000
    URLs monitored per dedicated management group
    12,000
    URLs monitored per agent
    50
    Refer the below link for the managing details: https://technet.microsoft.com/en-us/library/dn249696.aspx?f=255&MSPPError=-2147217396
    Gautam.75801

  • Wlw-runtime-config.xml & two managed servers

    I have a problem with WSDL generation and WebLogic workshop in a
    cluster.
    I'm using a wlw-runtime-config.xml file to ensure that my web service
    generates the correct url for it's endpoint.
    The problem I have is that I have two managed servers on one physical
    box, one listening on port 7010, the other on port 7030.
    The wlw-runtime-config.xml file is placed in the domain root, and I
    only seem to be able to specify a single port/dns name in the config
    file.
    My web service request will come in through the IIS plugin, hit one of
    the servers, generate the WSDL containing the port information, which
    may or may not be correct for the WLS instance that it has actually
    been proxied to.
    If that is correct, how do I handle the fact that the web service is
    deployed across all cluster members, two of which are hosted on one
    single machine.
    Am I missing something?
    Pete

    Hi Pete,
    I'm assuming you have seen the "how do i" on this topic [3], plus the
    information on how to setup a cluster [1].
    Your missing link may be the way your DNS entry is configured for the
    cluster. See the docs [2] on this topic, but you will need to specify
    the multiple nodes something like this:
    DNSName1:port1,DNSName1:port2,DNSName1:port3
    Note the folks in our super support group will be best suited to assist
    your efforts.
    Regards,
    Bruce
    [1]
    http://e-docs.bea.com/wls/docs81/cluster/setup.html#684345
    [2]
    http://e-docs.bea.com/wls/docs81/cluster/setup.html#714310
    [3]
    http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/deployment/howClusterDeployment.html
    Pete wrote:
    >
    I have a problem with WSDL generation and WebLogic workshop in a
    cluster.
    I'm using a wlw-runtime-config.xml file to ensure that my web service
    generates the correct url for it's endpoint.
    The problem I have is that I have two managed servers on one physical
    box, one listening on port 7010, the other on port 7030.
    The wlw-runtime-config.xml file is placed in the domain root, and I
    only seem to be able to specify a single port/dns name in the config
    file.
    My web service request will come in through the IIS plugin, hit one of
    the servers, generate the WSDL containing the port information, which
    may or may not be correct for the WLS instance that it has actually
    been proxied to.
    If that is correct, how do I handle the fact that the web service is
    deployed across all cluster members, two of which are hosted on one
    single machine.
    Am I missing something?
    Pete

  • Rolling bounce - Managed Servers

    Hi All,
    We have 3 node cluster. My question is can we restart the servers one by one.
    When there is a problem in one of the managed server, we can restart that particular managed server alone correct. Once the failed server is in RUNNING mode, what happens is all the composites in SOAINFRA is initializing in all the managed servers. All the transactions are failing due to this and it takes 10-15 mins of time for initializing the composites in all the servers.
    My question is it should initialize the composites only in failed server(post restart) but it is happening in all the servers.
    During that case weblogic doesnt aware that the composites are not initialized, but it start sending request. How can we avoid this.
    Once all the composites are initialized it should accept request. Is there is any possible ways to do this.
    Kindly help.
    Thanks,
    Maanik

    Holger Dewes wrote:
    Kumar Allamraju <[email protected]> wrote:
    pls clarify whether the process has died or servers are hung?
    Hello Kumar,
    that's actually a very good question. Does every managed server
    run in its own process?Yes.
    I will have to investigate this. All I
    can say at the moment is that the web console shows the server
    as not running. There's a known issue in 61 sp2 that admin console loosing the discovery
    of managed servers under load. May be this is what you are seeing.
    Then I start it again, and it runs fine... for aRegardless i want you to check the process id of that managed server and
    see if it exists or not...
    Kumar
    while.
    Cheers

Maybe you are looking for