WLS Logs in a Cluster Environment

          We would like to have all WLS logs from the WLS server instances in the clluster
          to be written to the same file on a common file system, such as an NFS mounted
          partition. By default, WLS writes all logs to the local file system. In a distributed
          environment, this can make debugging pretty difficult.
          Has anyone had any experience with having all WLS logs written to the same file?
          Regards,
          Chet
          

Hi,
To uninstall you have to first run the Server tools and there you can uncheck the sbo mailer. There is not way you can uninstall SBO mailer service and you cannot find it under control panel its a service...not an applicaiton.
Run the server tools and then choose repair.
Regards,
Rakesh N

Similar Messages

  • Forced user logged out in cluster environment

              Hi there,
              We have 2 managed server instances (WL7.0sp2) in our cluster environment. Under
              heavy load,
              the user gets kicked out of the system at random. This could possibly be either
              as a result of httpsession not getting replicated on the secondary server instance
              or the request not getting routed to the right server. Has any one experienced
              this problem before? When the proxy server is by-passed using a custom app, the
              prob no longer occurs!
              Any help would be appreciated.
              

    We have 2 managed server instances (WL7.0sp2) in our cluster          > environment. Under heavy load, the user gets kicked out of the
              > system at random. This could possibly be either as a result of
              > httpsession not getting replicated on the secondary server instance
              > or the request not getting routed to the right server. Has any one
              > experienced this problem before? When the proxy server is by-
              > passed using a custom app, the prob no longer occurs!
              Yes, I've seen it under heavy load. I'm not sure what it is, though. It
              sounds, in your case, that the problem is in the proxy. Perhaps it is
              incorrectly thinking that a server has died (that seems to happen
              sometimes).
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Bala" <[email protected]> wrote in message
              news:[email protected]..
              >
              

  • Logging in a Cluster environment

    Hi Folks,
    We need to monitor ?application level logging? in our team. I have been looking for some tools which can merge and monitor application log files, not server logs like access.log, etc. based on a unique transaction id. Our application will be deployed in a clustered environment. The clustered environment consists of two application servers on two ?physical? machines. When a user accesses our application through a transaction, the transaction may span over both these application servers which are deployed on two physical machines. Each application server writes into it?s own log file. In order to resolve a potential bug or a problem with the transaction, our support team has to look at both these log files and it?ll be difficult for our support team to look into both the log files simultaneously to solve the issue. Hence we need a tool which could provide one single view of both the log files and help our support team resolve any issues with a transaction.
    Please note that, we should be able to specify a log format that?ll be picked up by this tool so that we may be able to sort the log files based on the unique transaction id.
    Please let me know if you are aware of any such tool or plugin to WebLogic Cluster which may fulfill our need. Any suggestions are greatly appreciated.
    Also please CC to [email protected]
    Thanks and regards,
    Sarin

    Try SuperLogging at http://www.acelet.com/super/SuperLogging/
    It provides a centralized, chronological logging. It allows you to dynamically config.
    There is no way you can merge two log files. See http://www.acelet.com/whitepaper/loggingInJ2eeWorld.html
    The next version (end of this year or beginning of next month) of SuperLogging will combine current SuperLogging and LimpidLog together. LimpidLog is a revolutionay logging system: you do not need to hard-code log statement. LimpidLog is at: http://www.acelet.com/limpidlog/

  • Where to keep the archived log in a cluster environment.

    Hi
    Where it is good to keep the archive log file. on shared storage or on local instance.
    thanks.

    Where it is good to keep the archive log file. on shared storage or on local instance.
    It is always good to keep the archivelog files at shared storage location. This location is accessible to all instances, so in case of failure you can recover the database from any of the instances.
    Rgds.

  • Managed SOA Server not started in cluster environment.

    Hi,
    I am trying to make a SOA cluster environment on Linux based machines. After doing domain configuration which also involved packing of domain on machine 1 and unpacking on machine2, I tried to start the servers. I'm able to start AdminServer successfully and also the managed soa server on the same machine. When I'm trying to start managed soa server on other machine, I'm getting the following error..
    *<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
    java.io.IOException>
    My machine IP is XXX.XX.XXX.41 for Admin and XXX.XX.XXX.42 for Machine2. I guess the IP 192.168.122.1 is being used for cluster connection by Machine2 to make connection to Machine1. the managed soa server is getting started after the chain of error logs but it is not starting as a part of the entire cluster and comes as shutdown in WLS Console.
    I'm using Linux 5 Update 7 OS and SOA 11.1.1.5.0. Any help will be appreciated for resolving this issue.
    Please find the logs below.
    *<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
    java.io.IOException
    *     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)*
    *     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
    *     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
    *     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
    *Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:*
    *     java.net.ConnectException: Connection refused; No available router to destination]*
    *     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)*
    *     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)*
    *     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:315)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:285)*
    *     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
    *     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
    *     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
    *     at javax.naming.InitialContext.init(InitialContext.java:223)*
    *     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
    *     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
    *     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
    *     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
    *     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
    Caused By: java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:
    *     java.net.ConnectException: Connection refused; No available router to destination*
    *     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)*
    *     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
    *     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
    *     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:315)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:285)*
    *     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
    *     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
    *     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
    *     at javax.naming.InitialContext.init(InitialContext.java:223)*
    *     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
    *     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
    *     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
    *     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
    *     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
    Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
    *     java.net.ConnectException: Connection refused; No available router to destination*
    *     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)*
    *     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)*
    *     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)*
    *     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)*
    *     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)*
    *     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)*
    *     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
    *     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
    *     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:315)*
    *     at weblogic.jndi.Environment.getContext(Environment.java:285)*
    *     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
    *     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
    *     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
    *     at javax.naming.InitialContext.init(InitialContext.java:223)*
    *     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
    *     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
    *     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
    *     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
    *     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
    *     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
    *>*
    Cheers,
    Varun

    hi,
    I was able to resolve this issue. I haven't given Listen IP address for Admin Server as I have selected All Local Addresses during domain creation. As per some blog this allows Managed Server on remote machine to use any of the Address to speak to Admin Server. In this case it is using 192.168.122.1 rather than so called IP Address.
    Simple fix will be giving DNS Name of Machine or IP Address.
    Cheers,
    Varun

  • Changing the listener port number in a cluster environment

    Hello,
    I have an Oracle 10g database on a Windows cluster environment with Oracle Fail safe. I am trying to change the default listener port number - these are the steps I have done to change the port number:
    1) Take the listener offline via Oracle Fail safe
    2) stop the original listener from the command line
    3) change the port number in the listener.ora file & save
    4) start the original listener
    5) bring the listener online in Fail safe
    6) register the listener in the database with ALTER SYSTEM SET LOCAL_LISTENER....
    After all this, when i check the status of the listener via lsnrctl, i see that the new port number is used, however in the Fail safe administrator, I still see the default port 1521. How do I go about changing the port number so that Fail safe also registers the change?

    I did troubleshooting to verify the group, but this just changed the port number back to the default in the listener.ora & tnsnames.ora.
    So I did all the steps again to change the port number from the default to another - via lsnrctl status, i see that the new port number is being used, I can also log in to the database via Toad using the new port number, in v$parameter i see that the local_listener is registered on the new port number....only under the Fail Safe manager, the port number (under listener parameter) has not changed....it still shows the default port number. Anyone know how to change this???

  • ADS Configuration issue in HA cluster environment

    Hi All,
    We have HA cluster environment in which we have installed primary node, secondary node and additional application server. We have configured ADS in HA cluster but when we execute "fp_test_00" program in SE38 it throws "ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)" exception. As well as RFC destination "FP_ICF_DATA_<SID>" in java system throws "Error during ping operation: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect"  while we ping destination.
    I have checked URL,Port and Logon data all information provided for RFC is fine. Please help me to resolve this issue.
    Thanks

    Hi Reagan
    As you suggested I have checked the URL(http://hostname:8000) has been used for connection, logon data is also fine. Below I have attached dev_icm trace file and there I can see that system throwing error while "reading data from message server"
    dev_icm
    Thr 14116] Mon May 19 01:11:29 2014
    [Thr 14116] {0000a598} Traffic Control: Nettimeout (30) exceeded by peer: 10.15.212.11:23327 [icxxthr.c 4303]
    [Thr 16228] Mon May 19 03:51:29 2014
    [Thr 16228] *** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c      2829]
    [Thr 16228]
    [Thr 16228] *****************************************************************************
    [Thr 16228] *
    [Thr 16228] *  ERROR       Reading data from the message server (hostname / 3901)
    [Thr 16228] *              failed.
    [Thr 16228] *              Please check the trace file of the message server.
    [Thr 16228] *
    [Thr 16228] *  TIME        Mon May 19 03:51:29 2014
    [Thr 16228] *  RELEASE     721
    [Thr 16228] *  COMPONENT   MS (message handling interface, multithreaded)
    [Thr 16228] *  VERSION     4
    [Thr 16228] *  RC          -36
    [Thr 16228] *  MODULE      msxxi.c
    [Thr 16228] *  LINE        2848
    [Thr 16228] *  COUNTER     173
    [Thr 16228] *
    [Thr 16228] *****************************************************************************
    [Thr 16228]
    [Thr 16228] *** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c      1867]
    [Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken
    [Thr 16228] IcmJncmConnBrokenCallback called
    [Thr 16228] JNCMReconnectAsync: Start Message Server reconnect, command MS_J2EE_RECO(2), allow 3600 sec for reconnect
    [Thr 16228] JNCMReconnectAsync: Allow 30 sec for consistent cluster reconnect
    [Thr 16228] Mon May 19 03:51:30 2014
    [Thr 16228]
    [Thr 16228] *****************************************************************************
    [Thr 16228] *
    [Thr 16228] *  ERROR       The connection to the specified message server
    [Thr 16228] *              (hostname / 3901) failed. Please check the trace file
    [Thr 16228] *              of the message server. If a network filter has
    [Thr 16228] *              been activated (see message server parameters
    [Thr 16228] *              ms/acl_file_...) please check the configuration
    [Thr 16228] *
    [Thr 16228] *  TIME        Mon May 19 03:51:30 2014
    [Thr 16228] *  RELEASE     721
    [Thr 16228] *  COMPONENT   MS (message handling interface, multithreaded)
    [Thr 16228] *  VERSION     4
    [Thr 16228] *  RC          -35
    [Thr 16228] *  MODULE      msxxi.c
    [Thr 16228] *  LINE        2783
    [Thr 16228] *  COUNTER     176
    [Thr 16228] *
    [Thr 16228] *****************************************************************************
    [Thr 16228]
    [Thr 16228] *** ERROR => MsIAttachEx: MsINiWrite (rc=-35) [msxxi.c      884]
    [Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken during reconnect
    [Thr 16228] JNCMReconnectAsync: cannot reconnect to message server [cmd=MS_J2EE_RECO(2),loop=1],  rc=-35(-35)
    dev_server0
    [Thr 10444] Mon May 19 03:51:30 2014
    M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 26/sock 4824
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 42/sock 8104
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 50/sock 368
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7128
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 6832] Mon May 19 03:51:32 2014
    M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 19208] Mon May 19 03:51:32 2014
    M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 10444] Mon May 19 03:51:32 2014
    M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 4680] Mon May 19 03:51:32 2014
    M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 368
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 27/sock 7592
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 43/sock 8104
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 51/sock 4824
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 6832] Mon May 19 03:51:35 2014
    M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 10444] Mon May 19 03:51:35 2014
    M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 44/sock 7780
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 4680] Mon May 19 03:51:35 2014
    M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 368
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 19208] Mon May 19 03:51:35 2014
    M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 52/sock 8104
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 28/sock 7592
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 19208] Mon May 19 03:51:40 2014
    M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 6832] Mon May 19 03:51:40 2014
    M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 53/sock 7128
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 45/sock 7952
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 4680] Mon May 19 03:51:40 2014
    M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 10444] Mon May 19 03:51:40 2014
    M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 29/sock 4824
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 8508
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M 
    M [Thr 19208] Mon May 19 03:51:49 2014
    M  [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 10444] Mon May 19 03:51:49 2014
    M  [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 4680] Mon May 19 03:51:49 2014
    M  [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M 
    M [Thr 6832] Mon May 19 03:51:49 2014
    M  [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    M  [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 30/sock 4824
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 54/sock 7592
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 46/sock 7128
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    M  [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7952
        (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
    Please see these logs and let me how I can resolve this issue.

  • Best practice: Deployment plan for cluster environment

    Hi All,
    I want to know, which way is the best practice for preparing and deploying new configuration for WLS-cluster environment. How can I plan a simultan deployment of ALL of nodes, with out single point of failure?
    Regards,
    Moh

    Hi All,
    I get the Answer as followed:
    When you deploy an application OR redeploy an application, the deployment is initiated from the Admin Server and it it initiated on all targets (managed servers in the cluster) at the same time based on targets (which is expected to be cluster).
    We recommend that applications should be targeted to a cluster instead of individual servers whenever a cluster configuration is available.
    So, as long as you target the application to the cluster, the admin server will initiate the deployment on all the servers in a cluster at the same type, so application is in sync on all servers.
    Hope that answers your queries. If not, please let me know what exactly you mean by synchronization.
    Regards,
    Moh

  • OSB Email Transport polling in multi cluster environment

    Hi,
    I have following scenario: email needs to be read by OSB proxy using the Email transport. The proxy service service will poll the IMAP mail box and processes messages, upon reading a message message is deleted.
    The email transport works fine in a cluster environment by using a dedicated managed node for polling, so no duplicate messages will occur.
    However, we have two clusters in our environment pointing to one mailbox. In this case, two clusters have no visibility of each other. So, two pollers may poll the same mailbox.
    Please, advice if there any configuration on OSB, Weblogic or IMAP can be done to solve this issue.
    thanks,
    Djail

    Dont think it will work in an Active-Active setup. If you have both clusters listening to same email address then both will receive a copy (just like you receive same email on your desktop's email client and also on your mobile's email client) because SMTP servers distribute to clients similar to how a JMS Topic works.
    Dont know if there is a setup in IMAP which will allow an email to be sent to only one client (in this case one of the OSB clusters).
    If you want to make it work in Active-Active then you will need to do it at functional level, for ex. after receiving an email if you have any unique id then log that in a transaction table, before calling the backend, check if the same email was already processed by the other cluster. Alternatively, check at the backend before processing it.

  • How do i setup WTC in cluster environment using WLS6.1 sp3?

    Hello:
    the situation is:
    (1)Two solaris machines.
    (2)one WLS domain.
    (3)one admin server and four managed servers in this domain.
    (4)we cluster these 4 managed servers.
    (5)each machine contains 2 managed server.
    Here is the problem,
    when we start managed servers in the same machine, the wtc is ok, but when we start managed servers in diffent machine, the wtc fail.
    here is the error message:
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.187 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
    So, how can i setup wtc in cluster environment using WLS 61. sp3?
    Regards,
    cjyang

    cjyang <[email protected]> writes:
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.] I believe that this is a known problem and that WTC clustering is not
    supported in WLS 6.1.
    andy

  • Failed to replicate non-serializable object  Weblogic 10 3 Cluster environ

    Hi,
    We have problem in cluster environment, its showing all the objects in Session needs to be serialized, is there any tool to find what objects in session needs to be serialized or any way to find. There was no issue in WLS 8 when the application again setup in WLS 10, we are facing the session replication problem.
    The setup is there are two managed server instance in cluster, they are set to mulicast(and also tried with unicast).
    stacktrace:
    ####<Jun 30, 2010 7:11:16 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939476284> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    ####<Jun 30, 2010 7:11:19 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939479750> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    Thanks,

    Hi
    Irrespective of WLS 8.x or WLS 9.x, 10.x, in general any objects that needs to be synced/replicated across the servers in cluster should be Serializable (or implement serializable). The object should be able to marshall and unmarshall. Simple reason why it did not showed in WLS 8.x is may be in that version they could not show these details like Error. May be they showed as Info or Warn or Just Ignored it. Weblogic Server became more and more stable and more efficient down the lines like from its oldest version 4.x, 5.x, 6.x, 7.x to latest 10.x. So my guess is they added more logic and more functionality to capture all possible errors and scenarios. I did worked on WLS 8.1 SP4 to SP6 long time back. Could not remember if I saw or did not see these errors for cluster domain with non-serializabe objects. I vaguley remember seeing it for Portal Domains but not sure. I do not have 8.x installed, otherwise I would have given a quick shot and confirm it.
    So even though it did not showed up in WLS 8.x, still underneath rule is any object that needs to be replicated that is getting replicated in cluster needs to implement Serializable interface.
    Thanks
    Ravi Jegga

  • Session Problem With Cluster Environment

    Issue:
    To test our web application, we build a simply cluster environment containing 2 nodes, web server and admin. server. if we start all related servers and nodes in the following manner, the web server can not maintain the correct session ID, and mirror them across the nodes due to which the first session/request goes to the first node (node1) and the second request goes to the second (Node2). But Node2 does not have a successful session ID. Thus, our deployed application get a Session Time Out message.
    1.     Start WebLogic Application server
    2.     Started the nodes.
    3.     First start the Webserver
    However, when we change the start sequence as follows, the issue will disappear.
    1.     First start the WebServer
    2.     Start WebLogic Application server
    3.     Lastly started the nodes.
    Question:
    Why does the different start sequences effect the different result of Session Affinity in the cluster environment?
    Thanks for any responses!

    Hmmm... Never thought about it.
    Somehow I always start the environment in this sequence:
    - Admin Server
    - WebServer
    - Cluster
    I assume you are using the Apache HTTP server with the WebLogic proxy plug-in as your WebServer.
    Here you can configure
    - WebLogicCluster - which is a static starting point for the server list, and
    - DynamicServerList - enables that WebLogic automatically adds new servers to the server list when they become part of the cluster.
    What I can think of is that the last option is set to OFF in which case when new servers are added to the cluster, the plug-in cannot proxy requests to the new server.
    This could explain why the start-up sequence matters, i.e., when you first start the WebServer than the cluster nodes, the static list will do its work.
    When on the other hand, the cluster nodes are started before the WebServer the starting point for the server list is not created, because somehow
    to WebServer is not receiving notifications.
    One remark is in order, is that when you did not alter the DynamicServerList property, the default is ON.
    Hope the above makes some sense to you. (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/index.html)

  • SBO Mailer in a cluster environment

    Hi,
    I am currently facing an issue where when I install SBO Mailer on a cluster environment, the installation removes applications and license manager for some reason gets uninstalled.. When I want to uninstall the SBO Mailer, I do not see it under the Control Panel and neither do I see it in running in services. But if i look at the Service Manager the SBO Mailer Service is running.
    The strange part is that after this installation, there is an add-on that stopped working.
    Has anyone come across such a scenario?

    Hi,
    To uninstall you have to first run the Server tools and there you can uncheck the sbo mailer. There is not way you can uninstall SBO mailer service and you cannot find it under control panel its a service...not an applicaiton.
    Run the server tools and then choose repair.
    Regards,
    Rakesh N

  • Deploying Java Web Application (WAR-File) into a cluster environment

    Hi,
    we have a web application which has to read from and write to the file system.
    Since a short time we have a cluster environment (2 parallel servers) and since thisa time we have the problem, that files are worked double in the cluster. The application is working on both servers now and so we have this problem.
    Does anybody know how we have to deploy the application correctly in a cluster environment or do we have to change anything in our source code of the application?
    I didn't find any documentation about this.
    At the moment we have deployed the application on one of the two servers only, but I think there must be a better way to solve this problem.
    Thanks for your replies.
    Regards
    Thorsten

    Hi,
    I think first you need to wrap it into an EAR file, then you can deploy it.
    As far as I know standalone deployment of WAR is deprecated as of 640.
    similar threads:
    How to deploy .war on NWDI
    Deploying an existing WAR file into the Portal
    Hopefully this tutorial also gives some idea:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
    Regards,
    Ervin

  • PI 7.1 in a cluster environment (multiple ip-adresses): P4 port

    We want to  install PI 7.1 on unix in a cluster environment.Therefore we  installed also DEV+QA with virtual hostnames like the prodsystem, which will be later installed.
    At all sapinst installation screens we have used only the virtual hostname <virtual-hostname-server interface>.We have also set the SAPINST_USE_HOSTNAME=<virtual-hostname-server interface>. Although the P4-port seems to have used the physical hostname: in step 57 of sapinst we got problems and in dev_icm were:
    [Thr 05] *** ERROR => client with this banner already exists:
    1:<physical-hostname>:35644 {000306f5} [p4_plg_mt.c 2495]
    After we have set
    icm/server_port_1 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-server interface>
    icm/server_port_6 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-user interface>
    icm/server_port_7 = PROT=P4,PORT=5$$04, HOST=<physical hostname>
    icm/server_port_8 = PROT=P4,PORT=5$$04, HOST=127.0.0.1
    the sapinst was successfull.
    Now we're not sure how to set these P4-parameters in our  future productive cluster environment.
    Our productive system PX1 will live in a HA environment, so we don't want to use the physical hostnames in any profile.
    Our environment will look like:
    HOST-A (<physical-hostname-A>):
    <virtual-hostname-server interface>
    <virtual-hostname-user interface>
    HOST-B (<physical-hostname-B>):
    Normally our prodsystem will live on Host-A (physical-hostname-A). All parameters should
    only take the virtual hostname <virtual-hostname-server-interface>. During switchover the
    virtual hostnames (server and user interface) will be taken over to HOST-B, while the physical
    hostnames of HOST-A and HOST-B will stay like there are.
    How do the parameters have to be set here ?
    Have also the physical hostnames of both cluster nodes set in the
    instance profile, e.g:
    icm/server_port_1 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-server interface>
    icm/server_port_6 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-user interface>
    icm/server_port_7 = PROT=P4,PORT=5$$04, HOST=<physical-hostname-A>
    icm/server_port_8 = PROT=P4,PORT=5$$04, HOST=<physical-hostname-B>
    icm/server_port_9 = PROT=P4,PORT=5$$04, HOST=<localhost>
    Any recommendations ? In note 1158626 is some infomation regarding P4 ports with multiple network interfaces, but it's not 100% clear for us.
    Best regards,
    Uta

    Hi Uta!
    Obviously we are the only human beings in the SAP community having this problem. Nevertheless let's give it another try with a - hopefully - more simple problem description (and maybe it will be helpful to copy and paste this description into the open SAP CSN also).
    So here comes the scenario:
    We have one physical host:
    Physical hostname: physhost
    Physical IP address: 1.1.1.1
    On this physical host there is running one OS: SUN Solaris 10/SPARC
    On top of this we have two virtual hosts where we install 2 completely independent PI 7.1 instances with separate virtual hostnames and separate virtual IP addresses and separate DB2 9.1 databases. That is this is not an MCOD installation.
    Virtual Host no. 1 is PI 7.1 Development System:
    Virtual hostname: virthostdev
    Virtual IP address: 2.2.2.2
    Java Port numbers: 512xx
    Virtual Host no. 2 is PI 7.1 QA System:
    Virtual hostname: virthostqa
    Virtual IP address: 3.3.3.3
    Java Port numbers: 522xx
    With this constellation we face serious problems with the P4 port. Currently for example the JSPM for virthostdev does not start, because JSPM cannot connect to the P4 port.
    In SAP note 1158626 we have learned that by default always the physical hostname/IP address is used to address the P4 port and that we have to configure instance profile parameter icm/server_port_xx to avoid this.
    So how do we have to configure the instance profile parameter icm/server_port_xx for both systems to resolve these P4 port conflicts?
    Additionally: Is it important to use distinct server port slot numbers xx in both systems?
    Additionally: Is it possible to configure this parameter with hostnames instead of using IP addresses?
    So far we have tried several combinations, but with each combination at least one or even both systems have problems with that f.... P4 port.
    Please help! Thanx a lot in advance!
    Regards,
    Volker

Maybe you are looking for