Replicating a non-clustered VM to a clustered server

hi,
I am trying to setup a VM Replication from non-clustered VM to a clustered server, everything is going smooth but at when it start replication it come with error messag below is snap of the error message

it is not issue with access it was related to the conflict in port on IIS, i changed the port number other than 80, & it worked fine,
Please refer this article for more details
http://blogs.technet.com/b/filecab/archive/2013/10/15/windows-server-2012-r2-resolving-port-conflict-with-iis-websites-and-work-folders.aspx

Similar Messages

  • Can I remotely failover clusters with powershell from a non clustered server? Windows Server 2008 R2

    Hello,
    I'm trying to remotely administer my windows clusters and fail them over with a PowerShell Script.  The server I'm using is not a clustered server.  I've already installed the Failover Clustering Tools.  I'm able to retrieve information about
    my clusters but when I try to fail them over I receive an error saying "The cluster service is not running."
    The command I'm using is 'Get-ClusterNode $Server | Get-ClusterGroup | Move-ClusterGroup'
    Error message:  'Get-ClusterNode : The cluster service is not running.  Make sure that the service is running on all nodes in the cluster'
    Is there a way to install the cluster service or is there a different way to go around this error?
    Thank you!

    Hi Armando,
    To get cluster node information, please try to use the cmd cluster.exe, like:
    cluster.exe node NodeName /force
    For more detailed information to use clusterexe, please refer to this article:
    Mapping Cluster.exe Commands to Windows PowerShell Cmdlets for Failover Clusters
    To remotely manage Cluster server, you can also try the powershell pssession with the cmdlet enter-pssession to accesss the remote server:
    Learn How to Manage Remote PowerShell Sessions
    I hope this helps.

  • Error with running Singleton Service in a non-clustered mode

    Hello,
    I'm getting this error when try to deploy an app with defined Singleton Service in a WebLogic 10.3.5:
    <Error> <Deployer> <localdomain> <AdminServer><[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default(self-tuning)'> <<WLS Kernel>> <><7785ef355ffde3d6:-4c7bfbbc:138dd48f82b:-8000-0000000000000002><1343742871514> <BEA-149231> <Unable to set the activation state to true for the application 'MyApp'.
    weblogic.management.DeploymentException:
    at weblogic.application.internal.flow.SingletonServicesFlow.activate(SingletonServicesFlow.java:67)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.IllegalArgumentException: Cannot add Singleton Service MySingletonService as SingletonServicesManager not started. Check if MigrationBasis for cluster is configured.
    at weblogic.cluster.singleton.SingletonServicesManager.addConfiguredService(SingletonServicesManager.java:280)
    at weblogic.cluster.singleton.SingletonServicesManager.addConfiguredService(SingletonServicesManager.java:297)
    at weblogic.application.internal.flow.SingletonServicesFlow.activate(SingletonServicesFlow.java:65)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    It gets run only after deleting singleton-service entry from weblogic-application.xml:
    <singleton-service>
         <class-name>my.app.SingletonClass</class-name>
         <name>MySingletonService</name>
    </singleton-service>
    Is it possible to run it in a non-clustered server without deleting Singleton entry from weblogic-application.xml?
    Thanks

    Did this help you ??
    Not sure if it's related as here the issue is with clustered/non clustred and versioning!! the application which the bug talks about.

  • ASSERTION FAILED of replica-related stub in a non-clustered SLSB

    Wl 6.1 sp2
    Solaris 2.8
    We have 50 SLSBs running on non-clustered WL servers. Yet we are seeing
    the following ASSERTION FAILED error, which from the stacktrace seems to
    hint the ejb stub is doing something cluster-related... I have attached
    ejb-jar.xml of the offending bean; someone please verify we are not
    building cluster-capable stubs, and if we are building the right stub,
    please explain why the exception is happening. Thanks!
    ******** STACKTRACE
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
    violated ]
    at weblogic.utils.Debug.assert(Debug.java:74)
    at weblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
    at
    weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
    marySecondaryReplicaHandler.java:94)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
    RemoteRef.java:294)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :265)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy14.getStatus(Unknown Source)
    at
    com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
    ******* EJB-JAR.XML
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    <remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    <remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>

    Hi Rajesh,
    This error was reported on our QA system error log, and only occurred a
    couple of times in a very specific time frame. I will ask QA again if it
    has happened since the first report.
    However, even if this bug is minor and not production-worthy, what I am more
    concerned about is the fact that the stacktrace seem to indicate the bug is
    cluster-related, when we set our SLSBs to be non-clustered. Can someone
    please confirm, given the ejb-jar.xml and weblogic-ejb-jar.xml I've posted
    below, that I have properly configured and deployed our beans to be
    non-clustered? I don't want to introduce cluster overhead (and cluster
    bugs) when we don't need to!
    Gene
    "Rajesh Mirchandani" <[email protected]> wrote in message
    news:[email protected]...
    The reason I asked you if it is readily reproducable is because I had seenthis
    issue (support case) in WLS 6.1(no sp). The problem there was that itcould not
    be reproduced again and so I did not analyze it further.
    Is this happening under load ?
    Gene Chuang wrote:
    Hi Rob,
    AccountStatus is calling AccountService, which is a SLSB. I have
    attached
    its ejb-jar.xml in my original post, and here's the corresponding
    weblogic-ejb-jar.xml:
    !DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic6.0.0
    EJB//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
    <!-- Generated XML! -->
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </pool>
    <stateless-clustering>
    <stateless-bean-is-clusterable>False</stateless-bean-is-clusterable>
    >>
    >>
    <stateless-bean-methods-are-idempotent>False</stateless-bean-methods-are-ide
    mpotent>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    <trans-timeout-seconds>300</trans-timeout-seconds>
    </transaction-descriptor>
    <jndi-name>accountservice.AccountServiceHome</jndi-name>
    </weblogic-enterprise-bean>
    <transaction-isolation>
    <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    </transaction-isolation>
    </weblogic-ejb-jar>
    "Rob Woollen" <[email protected]> wrote in message
    news:[email protected]...
    It looks like AccountStatus is calling a stateful session bean that
    uses
    in-memory replication. (The PrimarySecondary stub is only used forin-memory
    replicated sfsb.)
    Do you have any sfsb?
    -- Rob
    Gene Chuang wrote:
    Wl 6.1 sp2
    Solaris 2.8
    We have 50 SLSBs running on non-clustered WL servers. Yet we are
    seeing
    the following ASSERTION FAILED error, which from the stacktrace
    seems to
    hint the ejb stub is doing something cluster-related... I haveattached
    ejb-jar.xml of the offending bean; someone please verify we are not
    building cluster-capable stubs, and if we are building the rightstub,
    please explain why the exception is happening. Thanks!
    ******** STACKTRACE
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Assertion
    violated ]
    at weblogic.utils.Debug.assert(Debug.java:74)
    atweblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
    at
    weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
    marySecondaryReplicaHandler.java:94)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
    RemoteRef.java:294)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :265)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy14.getStatus(Unknown Source)
    at
    com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
    >>>>
    ******* EJB-JAR.XML
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    ><remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >>>>>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    ><remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >>>>>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • Transactional Replication Not replicating non-clustered Indexes

    Hi
    I have created a transactional replication.I am sure that I have configured it to replicate Non-Clustered indexes,
    but It does not do so.
    I tried several times to reinitialize the subscription,but still no luck.
    Regards

    It is True for sure.
    But the problem is solved.I had to wait until the Initialize process get completed.
    But I am sure that this problem happened before.Sometimes it works fine but sometimes not.
    Hi ArashMasroor,
    According to your description, it seems that you encounter the issue that non-clustered indexes property is reset to “False” sometimes.
    To work around this issue, you can use a post-replication SQL script to create the indexes. Whatever articles you’re publishing open up the indexes drop down list of the article in object explorer, right-click on an index and levitate over Script Index as,
    then Create-to, then click New Query Window editor.
    Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
    Once you’re done find a safe folder somewhere on your hard drive and  save the SQL query as an .sql file with a sensible name. Then you can execute this script after applying the Snapshot. For more details, please review this
    blog.
    There is also a similar thread for your reference.
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b0f3870d-1a65-4384-a17b-96825ec5f098/transactional-replication-nonclustered-indexes-not-copying?forum=sqlreplication
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Apache HTTP proxying for load balancing only to a group of non-clustered WL servers

              Hi,
              We're running WL Server 6.1 SP 2 on Solaris 2.8.
              For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf option,
              do the WL servers you want to load balance across have to be part of a WebLogic
              cluster (if you are prepared to do without failover, as I know it would need to be
              a proper WL cluster to replicate session info for failover). Can you load balance
              across a group of non-clustered WL servers, and maintain the user session to the
              one WL server so that it doesn't switch between servers on alternate requests for
              the same user session, or must the servers be configured as a WebLogic cluster?
              Paul
              We find that if you have a collection of WL servers that are not configured as a
              cluster, that it will load balance alternate requests to each server, but it will
              not pin a user to a single machine according to their session so for 2 servers, 2
              differetn sessions get created, one on each machine.
              Is this because it doesn't normally do this, but sends the user alternately to a
              primary then secondary which works in a cluster because the session is replicated.
              I thought the secondary was only used when the primary failed.
              

    We're running WL Server 6.1 SP 2 on Solaris 2.8.          >
              > For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf
              option,
              > do the WL servers you want to load balance across have to be part of a
              WebLogic
              > cluster (if you are prepared to do without failover, as I know it would
              need to be
              > a proper WL cluster to replicate session info for failover). Can you load
              balance
              > across a group of non-clustered WL servers, and maintain the user session
              to the
              > one WL server so that it doesn't switch between servers on alternate
              requests for
              > the same user session, or must the servers be configured as a WebLogic
              cluster?
              You don't have to use the clustering option. To get failover, you'll have to
              use the JDBC persistence option of WL.
              > We find that if you have a collection of WL servers that are not
              configured as a
              > cluster, that it will load balance alternate requests to each server, but
              it will
              > not pin a user to a single machine according to their session so for 2
              servers, 2
              > differetn sessions get created, one on each machine.
              >
              > Is this because it doesn't normally do this, but sends the user
              alternately to a
              > primary then secondary which works in a cluster because the session is
              replicated.
              > I thought the secondary was only used when the primary failed.
              The primary/secondary stuff requires clustering. If Apache continues to
              "load balance" after the first request, you need to either use JDBC session
              persistence or use a different load balancer (like mod_jk for Apache or a
              h/w load balancer with support for sticky).
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Paul Hammond" <[email protected]> wrote in message
              news:[email protected]...
              >
              

  • Non clusterable

    I have two members in the cluster,when i deploy my application,i get the
              following error message:
              <2002-7-15 ??09?37?13?> <Error> <Cluster> <Conflict start: You tried to bin
              d an object under the name FundCollectionManager in the JNDI tree. The
              object yo
              u have bound from 191.1.1.5 is non clusterable and you have tried to bind
              more
              than once from two or more servers. Such objects can only deployed from one
              serv
              er.>
              How to make the object clusterable?
              We user wls6.1 sp2 and Tru64unix
              Thanks
              

    Implement serializable?
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "wliu" <[email protected]> wrote in message
              news:[email protected]..
              > I have two members in the cluster,when i deploy my application,i get the
              > following error message:
              > <2002-7-15 ??09?37?13?> <Error> <Cluster> <Conflict start: You tried to
              bin
              > d an object under the name FundCollectionManager in the JNDI tree. The
              > object yo
              > u have bound from 191.1.1.5 is non clusterable and you have tried to bind
              > more
              > than once from two or more servers. Such objects can only deployed from
              one
              > serv
              > er.>
              > How to make the object clusterable?
              > We user wls6.1 sp2 and Tru64unix
              > Thanks
              >
              >
              

  • What is RID in non clustered index and its use

    Hi All,
    I need help regarding following articles on sql server
    1) what is RID in non clustered index and its use.
    2) What is Physical and virtual address space. Difference in 32 bit vs 64 bit Virtual address space
    Regards
    Rahul

    Next time Please ask single question in a thread you will get better response.
    1. RID is location of heap. When you create Non clustered index on heap and
    lookup happens to get extra records RID is used to locate the records. RID is basically Row ID. This is basic definition for you. Please read
    this Thread for more details
    2. I have not heard of Physical address space. I Know Virtual address space( VAS)
    VAS is simple terms is amount of memory( virtual )  'visible' to a process, a process can be SQL Server process or windows process. It theoretically depends on architecture of Operating System. 32 bit OS will have maximum range of 4 G VAS, it's calculated
    like a process ruining on 32 bit system can address max up to 2^32 locations ( which is equivalent to 4 G). Similarly for 64 bit max VAS will be 2^64 which is theoretically infinite. To make things feasible maximum VAS for 64 bit system is kept to 8 TB. Now
    VAS acts as layer of abstraction an intermediate .Instead of all request directly mapping to physical memory it first maps to VAS and then mapped to physical memory so that it can manage request for memory in more coordinated fashion than allowing process
    to do it ,if not it will  soon cause memory crunch.Any process when created on windows will see virtual memory according to its VAS limit.
    Please read
    This Article for detailed information
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Space occupied by clustered index Vs non-clustered index

    I am trying to understand the indexes. Does clustered index occupy more space than a non-clustered index because it carries the information about rest of the other columns also. Could you guys please help me understand this. Thanks in advance.
    svk

    Hi czarvk,
    Clustered index in SQL Server takes up more space than non-clustered indexes.
    Clustered index arranges the way records are stored in a table putting them in order (key, value), all the data are sorted on the values of the index.
    A non-clustered index is a completely different object in a table, containing only a subset of columns and a row locator to the table’s rows or to the clustered index’s key.
    So clustered index in SQL Server takes up more space than non-clustered indexes.
    If you have any question, please feel free to let me know.
    Regards,
    Donghui Li

  • OSM v7.2 - More that 1 instance in a non clustered environment

    I am just wondering...
    1) Can i install OSM separately on 2 servers while using the same database instance in a non-clustered manner?
    This is for circumstances where I need a dedicated server resource for bulk provisioning for example.
    2) If I am not using AIA in my implementation, how does COM calls a SOM cartridge and how does SOM reply COM on the completed status?
    Is it via some default provided webservice, or do i need to find a way to implement it myself.
    Thanks :)

    Hi,
    1. Though technically it is feasible to use two OSM instances with same database, it is not suggested as it may lead to locking issues and not sure how you are planning to acheive bulk provisioning by this way
    2. The calling of SOM cartridge by COM and status updates of SOM to COM has to be implemented by yourself if you are not using AIA. You can make use of default webservices proivded by OSM
    Regards,
    JP

  • Weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non clusterable object with jndiName ]

    Hi,
    I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
    I am getting following error during deployment.
    Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
         Module: Sample.jar     Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
    Unable to deploy EJB: SampleBean from Sample.jar:
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
    clusterable object with jndiName ]
         at weblogic.utils.Debug.assertion(Debug.java:57)
         at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
         at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
         at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Any clue?, what its talking about?
    Thanks
    Naresh

    Hi,
    I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
    I am getting following error during deployment.
    Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
         Module: Sample.jar     Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
    Unable to deploy EJB: SampleBean from Sample.jar:
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
    clusterable object with jndiName ]
         at weblogic.utils.Debug.assertion(Debug.java:57)
         at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
         at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
         at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Any clue?, what its talking about?
    Thanks
    Naresh

  • Non Clustered Indexing not working for SQL server 2005

    I have create two non clustered index on two particular tables. Now the problem is its working fine..but after restarting my server its working stop and then again I have to delete that index and recreate it.

    try these links 
    http://blog.sqlauthority.com/2009/02/07/sql-server-introduction-to-force-index-query-hints-index-hint/
    http://blog.sqlauthority.com/2009/02/08/sql-server-introduction-to-force-index-query-hints-index-hint-part2/
    http://www.brentozar.com/archive/2013/10/index-hints-helpful-or-harmful/
    Hope it Helps!!

  • Running BizTalk on multiple non-clustered servers. Potential serious issue

    Hi,
    I have just discovered what has potential to be a fairly large issue in our current BizTalk Architecture. We are running BizTalk Server 2006 R2 on 2 different servers, running Windows Server 2003 R2. These servers are NOT clustered. Instead, BizTalk is installed
    to both, configured on 1 and then on the 2nd, they have joined the existing BizTalk environment. We have 1 host with 2 host-instances for say an Orchestration Host. (So 1 Orchestration Host and then 1 Orchestration Host Instance on each server), we also have
    a host instance for Receive and Send on each server.
    This is a problem that I have identified on an application currently in UAT:
    We have a routine called 'Recovery Mode'. It doesn't matter what Recovery Mode is but what does matter is that only a single instance can go into recovery mode at the same time. 
    Consider this:
    bool inRecovery;
    while (isBroken) {
    if (!inRecovery){
    inRecovery = true;
    // Recover
    inRecovery = false;
    else {
    // Wait, recheck until not in recovery, or fixed.
    Imagine an instance on server 1 needs to go into recovery, it first checks the inRecovery flag, gets returned false so goes into recovery, let's say this takes 5 minutes to complete. During this time, an instance on server 2 needs to go into recovery, checks
    the flag, but the flag on server 2 has not been set to true.... Now I have 2 instances in Recovery...
    My questions are:
    1. Can I cluster 2 non-clustered servers? I'd need to upgrade from Windows Server 2003 R2 Standard to Enterprise is that possible? If so, Can I simply upgrade and cluster the servers or would I need to format the disks?
    2. If no to number 1, where would you store the 'inRecovery' flag'? I can't store in a DB as there will be slight cross over where instance 2 might return false in my example just as instance 1 is writing unless I can lock it on write or something.
    Some advice would be greatly appreciated.
    Thanks
    Rod

    To answer your specific question:
    1. Yes, but you would need to upgrade to at least Enterprise.  Windows Server 2003 R2 Standard does not support clustering.  IIRC, the upgrade from Standard to Enterprise is pretty easy, perhaps just a SKU change.
    2. If you absolutely cannot upgrade Windows Server, then you'd have to store the state externally, such as SQL Server.  There shouldn't be any concurrency issues if you do the check in the right sequence.  Basically, begin a transaction, attempt
    to UPDATE, return weather the UPDATE was successful, meaning that call grabbed the lock.  If you check then update, yes, there is a miniscule chance both will return the same value but only one near-sumultaneous UPDATE will succeed.

  • Load balancing, failover and fallback in Non-Clustered WebLogic environment

    hi,
    Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
    We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
    The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
    All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
    Any help appreciated.
    Thanks.
    Best regards,
    Bala

    hi,
    Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
    We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
    The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
    All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
    Any help appreciated.
    Thanks.
    Best regards,
    Bala

  • Transactional Replication: Non-Clustered Indexes not copying.

    Hello,
    I set up replication on our servers at work to streamline some procedures we run daily/weekly on them.
    This copies around 15 articles from two databases on the "Master" server to another server used for execution purposes. For the most part it was a pretty straight forward task and it seemed to work nicely; but I realised after some investigation that the
    non-clustered indexes weren't copying over to the child server.
    I set the non-clustered indexes property in the properties of the publishing articles to "True" and generated a new snapshot, this seemed to work, but I've come into work this morning to find the property has reset to "False" and I have no indexes on the
    table again. Why is this happening and is there any way I can resolve the matter so the indexes are copied over concurrently?
    Thanks in advance for your advice.
    JB

    I actually solved this.
    You can use a post-replication SQL script to create the indexes. Whatever articles you're publishing open up the indexes drop down list of the article in object explorer, right-click on an index and hover over Script Index as, then Create-to, then click
    New Query Window editor.
    Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
    Once you're done find a safe folder somewhere on your harddrive and save the SQL query as an .sql file with a sensible name.
    Right click on the publication and goto properties. Click on the "Snapshot" tab, in there; there should be a section saying "Run additional scripts". Choose the browse button next to "After applying the Snapshot; execute this script:"
    Navigate to your script file and choose it. Once done click ok and it'll prompt you that something has changed and if you'd like to generate a new snapshot, make sure you do or it won't work.
    That's it, you'll find once the publication has bulk copied over the the subscriptions successfully there are non clustered indexes on the tables. Pretty simple!

Maybe you are looking for