Singleton deployed in cluster runs in both managed servers

Hi,
I have deployed a singleton service in a Weblogic (9.2) cluster. This cluster has two managed servers.
Recently we saw instances of this singleton services running on both these managed servers, which resulted in a lot of duplicate data in our system.
Is this a bug in the system? How can we prevent this?

Hi,
Could you please refer the following links and confirm me if you had defined and configured the singleton service as mentioned in the links:
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/ConfigureSingletonService.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/DefineSingletonService.html
regards,
Zeno

Similar Messages

  • Problems with deploying file to one of the managed servers on a cluster

    We are running Weblogic 10.3.
    When I start both managed servers from the Admin Console, one fails with the error below and in Admin state, but the other managed server starts up correctly.
    The only difference from when it was first working is that the managed server ServerBox1 was imaged and loaded onto new hardware and all network/os properties configured the same as the old box.
    ####<Timestamp> <Info> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292425> <BEA-149059> <Module DocFile.war of application DocFile is transitioning from STATE_NEW to STATE_PREPARED on server ServerBox1.>
    ####<Mar 29, 2012 3:11:32 PM EDT> <Error> <HTTP> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292488> <BEA-101064> <[WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
    java.lang.NullPointerException
           at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
           at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
           at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
           at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
           at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
           at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
           at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
           at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
           at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
           at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
           at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
           at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
           at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
           at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
           at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
           at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
           at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
           at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
           at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
           at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
           at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
           at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
           at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
           at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
           at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
           at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
           at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
           at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
           at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
           at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
           at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
           at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
           at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
           at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
           at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Timestamp> <Info> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292506> <BEA-149061> <Module DocFile.war of application DocFile failed to transition from STATE_NEW to STATE_PREPARED on server ServerBox1.>
    ####<Mar 29, 2012 3:11:32 PM EDT> <Error> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292727> <BEA-149205> <Failed to initialize the application 'DocFile' due to error weblogic.application.ModuleException: [HTTP:101064][WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
    java.lang.NullPointerException
           at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
           at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
           at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
           at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
           at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
           at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
           at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
           at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
           at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
           at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
           at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
           at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
           at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
           at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
           at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
           at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
           at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
           at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
           at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
           at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
           at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
           at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
           at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
           at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
           at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
           at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
           at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
           at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
           at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
           at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
           at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
           at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
           at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
           at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
           at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    null.
    weblogic.application.ModuleException: [HTTP:101064][WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
    java.lang.NullPointerException
           at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
           at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
           at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
           at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
           at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
           at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
           at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
           at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
           at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
           at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
           at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
           at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
           at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
           at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
           at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
           at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
           at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
           at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
           at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
           at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
           at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
           at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
           at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
           at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
           at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
           at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
           at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
           at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
           at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
           at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
           at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
           at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
           at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
           at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
           at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
           at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
           at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
           at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
           at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
           at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
           at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
           at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
           at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
           at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    null
    I also noticed that the DocFile directory inside the stage directory is deleted once the ServerBox1 is started completely.
    Thanks for the assistance.

    Hi Partha. Did you get a solution to your problem with high connection delay times on your server? I'm having a similar problem and saw your post.
    Thanks,
    Mark

  • How to install Window service for Managed Servers of a Cluster

    Dear All,
              I am preparing a production setup consist of three machines A,B and C. Machines A is the Admin Server which hosts a cluster consist of two managed nodes. I intend to schedule both these nodes, targeted to two different machines (machines B node-b and machine C host node-c), as startup task on daily basis. I have no Node Manager running on machine A, but on machine B and machine C.
              I am only interested to schedule started task for node-b and node-c only. I need to know how to install the Windows services for the node-b and node-c since there are targeted on remote machines. Starting managed server as Win sevice works in the case of standalone managed servers but not sure when it comes to cluster setup.I appreciate if you can throw some light on this question.
              Thanks
              Kris

    Krish,
              >Let say I gracefully shutdown both managed servers while >Admin is running. Do you think both these nodes while be >brought up ? I dont think they will come up.
              If you require an automatic restart when the managed server did not enter a failed state you can use the weblogic.Admin utility to ping the servers and kick off a server startup in the normal way with nodemanger see:
              http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
              http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
              If your servers entered a failed state you can use weblogics self health monitoring.
              >Can we use JMX MBean to start managed servers ?
              Yes.
              As long as the nodemanagers are running you can start the managed servers using scripted commands using the weblogic.Admin class or your own java app using JMX.
              I think you may also be able to use WLST
              http://dev.bea.com/codelibrary/code/wlst.jsp
              hope this helps
              cheers
              Please see the
              Hussein Badakhchani
              www.orbism.com

  • OSB Managed Servers - How to add one to the OSB Cluster

    Hi,
    I have an OSB Cluster of two managed servers. There is an Admin Server that controls the two.
    On the Admin Server I see that there are about 137 odd Applications and a list of Libraries installed.
    However on the Managed Servers I see there is not a single application.
    Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?
    If I create a new Managed Server that I want to Add to the Cluster there is no option to deploy those applications to the newly created Managed server in one shot. The only time it can get those applications is if the Applications were deployed to the OSB Cluster and not to the managed servers.
    Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well?

    Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?Your understanding is correct. Managed server should have libraries and adapters targetted to it.
    Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well? Yes, manually you have to target each and every application to the cluster but it may not be an effective process. The basic funda of cluster is to make applications independent of managed server, so that if you add/remove a managed server then it does not affect the existing configuration. I think you should follow the standard practice and always create a clustered domain where all applications are targetted to cluster and NOT to the managed server. You may like to refer -
    http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15022/config.htm#i1531648
    Regards,
    Anuj

  • What should be the client url for managed servers in a cluster

    Hi guys,
    I have created a cluster(cluster_1) having 4 managed servers. 2 managed servers on my machine(IP1) and 2 managed servers on other machine(IP2).
    I am able to deploy a xxx.war file on my admin server
    also
    I am able to deploy the same war file on my cluster
    When I try to hit the client url, it gives me back the correct data, but it creates the session on the admin server and not the cluster.
    If I remove the xxx.war file from the deployment(deployed on admin server) and redeploy the xxx,war file on the cluster, it gets deployed successfully , but the client url gives me a 404 error.
    What should I do, so that after hitting the client url, it creates the session on the managed servers in the cluster ?
    My admin server is not the part of this cluster.
    cluster ip:127.0.0.1
    ip1: 10.25.63.130
    ip2: 10.25.63.131
    please help
    Salil

    Hi Salil
    This is exactly what I mentioned in my earlier post. You CANNOT and should NOT expose the managed server url (host, port) to the end users. Because as you already figured out, you can specify only one. Or they cannot try one at a time like that.
    This is where, the Load Balancer will come into picture like Apache Web Server. After installing Apache web server, usually it runs at default port 80. So you just expose the apache host to outside world. Also most companies will have Firewalls and Apache is outside of Firewall and all weblogic servers are inside the Firewall. In apache, you configure the weblogic cluster details like the host names and ports of each managed server etc in httpd.conf file etc.
    Ex: For outside users, they may try like http://apachehost/myWeb/myHello.jsp -> apachehost is the host name where Apache web server is running at port 80. NOW Apache is smart enough to do Load Balancing and Failover. If 100 users access the site with 4 managed servers, ideally each managed server will get 25 requests (load balancing). Also if 2 servers are killed, automatically, request will NOT go to them, but to other 2 live servers etc etc. Apache takes care of this.
    Bottom line, please see my earlier post, and you need to have some sort of Web Server like Apache for your cluster setup.
    Thanks
    Ravi Jegga

  • Weblogic.Admin command for stopping all Managed Servers in cluster

    Hello All,
    I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
    I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
    I am looking for a way to do that using java weblogic.Admin utility
    Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
    Thanks
    Weblogic Consultant

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • How to deploy config files to managed servers

    We have several configuration files that are used by our EJB application at
    startup. Is there a way to automatically deploy these configuration files
    to the managed servers. Right now, we are forced to FTP to files over to
    the managed servers as part of the deployment process. It would be nice if
    there were an easier way.
    Randy Ott

    why cant you include them inside your ejbjar as resource files ?
    prasen
    Nitin Shenoy wrote:
    >
    Guess no one replied!!
    "Randy Ott" <[email protected]> wrote in message
    news:3b67022e$[email protected]..
    We have several configuration files that are used by our EJB applicationat
    startup. Is there a way to automatically deploy these configuration files
    to the managed servers. Right now, we are forced to FTP to files over to
    the managed servers as part of the deployment process. It would be niceif
    there were an easier way.
    Randy Ott

  • Managed servers dies regularly

    Hello,
    we have two managed servers on two different machines (not
    running in a cluster) and both of them die regularly, i.e.
    they simply stop. There is nothing in the log files at all
    that hints at any problems. Both managed servers are started
    via node manager. The admin servers on both machines work fine.
    We use WLServer 6.1 sp1 running under Win NT 4. Any ideas?
    Cheers

    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

  • Jsf Bean target unable to reach in one of managed servers

    Hi All,
    We are using portal 10.3.0 and jsf 1.2
    Application working gud on both managed servers but suddenly,
    In one of managed servers getting "javax.el.PropertyNotFoundException: Target Unreachable" and resolved my bean to null
    Any idea ....Please do help me...
    Thanks in advance
    Siddu

    what is your domain structure ? You deploy your application to stand alone managed server or cluster ?

  • How nodemanager starts managed servers?

    Hello All,
    I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
    To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
    NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
    ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
    CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
    cd /u001/wls8/bea/weblogic81/server/bin/
    su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
    sleep 60
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
    sleep 1200
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
    Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
    I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
    Can anyone tell me how nodemanager starts the managed servers automatically??
    Thanks,
    HK

    can you please tell me what is this .startCluster.sh script.
    is it your custom script?
    And the idea i have in my mind is that after
    cd /u001/wls8/bea/weblogic81/server/bin/
    su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
    sleep 60
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
    sleep 1200
    you can give the command to start the individual managed servers like:
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
    I think this way it will work....

  • Performance Clustered Managed Servers

    I posted it in the cluster thread, want it be visible here as well.
    Performance of Clustered Managed Servers

    Hi,
    According to the info you sent, there are 71GB of swap area in use and 7GB of real memory free.
    This is not conclusive, as we don't know what is in the swap area. It could be part or the entire JVM for your application. Also, we have to take into consideration shared memory.
    I believe you are running many applications in that server, and possible multiple environments.
    In order to avoid spending too much time investigating other config issues that might not exist, I think you should try to eliminate the swap to see if this is the issue. I believe that this could be the main issue, based on the info I have so far.
    Would be possible for you to stop all or some of the applications running in that server? Then you should check the available RAM (make sure that there are at least 10GB available before starting both managed servers) and restart both managed servers which you have your application running.
    Regarding the response times for the login, does it always take the same time to login? You mentioned about 30 seconds, this also seems very high to me. Are your discarding the first login after the server restart? Depending on which framework you are using, it might be interpreting some artifacts or compiling the JSPs in the first execution.
    Regards,
    Fabio Douek

  • Performance of Clustered Managed Servers

    WLS 10.3.5 on Solaris10
    we have the clustered weblogic10.3.5 domain with two managed servers, which a web app deployed.
    we use proxy server (an ohs server) as the frontend host.
    we tested for the app login, if both managed servers are started, the login takes about 2 mins.
    however if only one managed server is started, the login only takes less 1/2 min.
    There is no problem to support two managed servers in the ram and cpu on the server
    Why?
    where should we start to look into the issue?

    Hi,
    According to the info you sent, there are 71GB of swap area in use and 7GB of real memory free.
    This is not conclusive, as we don't know what is in the swap area. It could be part or the entire JVM for your application. Also, we have to take into consideration shared memory.
    I believe you are running many applications in that server, and possible multiple environments.
    In order to avoid spending too much time investigating other config issues that might not exist, I think you should try to eliminate the swap to see if this is the issue. I believe that this could be the main issue, based on the info I have so far.
    Would be possible for you to stop all or some of the applications running in that server? Then you should check the available RAM (make sure that there are at least 10GB available before starting both managed servers) and restart both managed servers which you have your application running.
    Regarding the response times for the login, does it always take the same time to login? You mentioned about 30 seconds, this also seems very high to me. Are your discarding the first login after the server restart? Depending on which framework you are using, it might be interpreting some artifacts or compiling the JSPs in the first execution.
    Regards,
    Fabio Douek

  • Log4j and managed servers

    This seems somewhat obvious, but...
              I have a Solaris based WLS 8.1.6 cluster with two managed servers.
              In the log4j.xml for BOTH managed servers, the logs for output from both go to the same file.
              What happens is one managed server writes to dctm_api.log and one writes to the previous log file.
              Is this as simple as Log4J in one of the Managed Servers has the file open and Log4J from two process can't have the same file open and write to it at the same time?
              Thanks,
              Michael Geiser

    Static fields won't get serialized.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "rohit" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Hi, can someone please advice if using log4j in the clustered environment
              would
              > in any way result in the failure of in memory session replication. We are
              using
              > WL 7.0 and log4j is installed on each managed servers. The log4j class
              "org.apache.log4j.Logger"
              > is used as a static reference within java classes which are put in the
              session.
              > Any response greatly appreciated. Thanks. Rohit
              

  • 1 NodeManager, 1 Admin Server and 2 Managed Servers

    Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
    Setup:
    1 Machine (RedHat Enterprise Linux 5.5)
    1 NodeManager
    1 AdminServer (Name: APP)
    2 Managed Servers (Name: APPLIVE, APPUAT)
    Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
    Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
    Edited by: user13602952 on Jan 2, 2011 9:54 PM

    Hi Hong,
    Following are the few things which you help you understand about NodeManager and nmEnroll
    - First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
    - When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
    Example:
    nmEnroll([domainDir], [nmHome])
    - With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
    Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
    For more information have a look at the below links:
    Topic: Search for "nmEnroll"
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
    Topic: Overview of Node Manager
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • Shutdown(block='false') only works via Admin Server, not managed servers

    Hello,
    We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
    I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
    connect(user, pwd, http://localhost:7001)
    shutdown('myserver1', 'Server', block='false')
    shutdown('myserver3', 'Server', block='false')
    shutdown('myserver5', 'Server', block='false')
    shutdown('myserver7', 'Server', block='false')
    shutdown('myserver9', 'Server', block='false')
    All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
    However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
    connect(user, pwd, url='t3://localhost:8001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:9001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:10001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:11001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:12001')
    shutdown(block='false')
    disconnect()
    NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
    Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
    We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
    What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
    Best regards,
    Michael

    Hi Mike,
    WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
    One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
    If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
    Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
    java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
    or
    java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
    This will be useful to make shutdown of servers without any problem.
    Note: block=false will always works it should not be the problem.
    Regards,
    Kal

Maybe you are looking for

  • Failed to start dependent service com.sap.portal.usermapping

    Hi I am trying to retrieve the User mapping information from my Webdynpro application. I added PORTAL:sap.com/com.sap.portal.usermapping to my service references in the web dynpro application. However, I am getting an error while deploying the applic

  • What is going on!?!?

    Why does iPhoto keep attempting to republish my albums randomly!??! I made one gallery and after several unexpectely quits and what not and several complete from the beggining repulishes(it just started on its own didn't check to see what was already

  • How to make more cells in one table by DataGridView

    Hello, I have a question, Firstly I'm using VB How can I make invoice by datagridview I'm trying to type customer information in the Textbox and Inventory Items in datagridview but the problem is datagrid give me one cell and I can type one inventory

  • Shades of Yellow

    Over the time of using my Toshiba Excite Pro, I noticed that the display does not seem to show yellow well. Of course yellow is a somewhat fragile colour, and there are different shades around, but it seems that a lot of them turn out a lot more lime

  • Creating AP drafts

    Hello, We are trying to create a AP draft and when pressing the Add button the following message is appearing: "No matching records found 'Payment Terms' (OCTG) (ODBC-2028)" However, the draft is created. Do you know why that message is appearing if