Could not start the server via the SOA node Manager
Hi allI try to install AIA 11.1.1.6.0 on top of the SOA Suite 11.1.1.6.0.
I was able to install the weblogic, UCR, soa and osb servers server correctly. Now, before installing the AIA, the document I am following it says, make sure to start the server soa through the Manager of nodes.
Now I start to the administrator of the server, then the node Manager, to make sure I checked the node Manager is in place, I logged the weblogic console, went to the Machines, and I see that it's upward and accessible.
Now using WLST commands, first of all, I have connected to Manager nodes by using the nmConnect() command, so I try to start the server soa through node Manager with the command start ('soa_server1').
I get an error when you try to start the server with the command nmStart() soa, below is the error message...
«Error at startup server soa_server1: weblogic.nodemanager.NMException: Exception when starting Server «soa_server1»»
I ran the command dumpStack(), and I get the output as 'no trace available battery.
If I am able to start the server soa through the node Manager, I can go ahead and install the pack of AIA, but wrong to let me go forward.
I also tried to boot the server from soa through the weblogic console, go to the servers tab, select the soa_server1 and start, the State of the soa server will "FAILED_NOT_RESTARTABLE".
I followed some of those blogs like...
http://Neeraj-SOA-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your opinion.
Thank you very much
N
Hi Patricia,
I had exactly the same problem some time ago...
The cause:
There are two servers trying to run in debug mode and use the same debug port
-Xrunjdwp: transport = dt_socket, address = 8453, server = y, suspend = n
Possible solutions:
1. turn off debugging (this is what I did)
2 use the various debugging ports to different servers (difficult to do because the servers share the same scripts)
What worked for me was:
1. in % DOMAIN_HOME%\bin, I created a script called startWebLogic_nodebug.cmd with the following content:
%CD%\bin\startWebLogic.cmd /nodebug % *.
2. in nodemanager.properties, I changed the following property
StartScriptName = startWebLogic_nodebug.cmd
Now my servers start without debugging...
I hope this helps.
See you soon,.
Vlad
Tags: Fusion Middleware
Similar Questions
-
Could not start the SOA in the IAM 11.1.2.3 Server installation
Hello
I followed steps below so far to install IAM 11.1.2.3
1 created patterns of DB with the remote control 11.1.1.9
2 installed WLS 10.3.6
3 installed SOA 11.1.1.9
4 installed IAM 11.1.2.3
5 domain created for IAM
6 creation of database of store security
7 WLS server started.
8A tried to launch the SOA server before configuring the server of the IOM
But SOA server could not start and error message. Anyone know the reason?
===================================
< 29 July 2015 21:08:08 > < INFO > < NodeManager > < output server log file is "D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\servers\soa_server1\logs\soa_server1.out" >
< 29 July 2015 9:08:09 CEST > < Info > < security > < BEA-090905 > < disabling CryptoJ JCE provider auto-intégrité for better startup performance. To allow this control, enter - Dweblogic.security.allowCryptoJDefaultJCEVerification = true >
< 29 July 2015 9:08:09 CEST > < Info > < security > < BEA-090906 > < change the default Random Number Generator in RSA CryptoJ of ECDRBG to FIPS186PRNG. To disable this change, specify - Dweblogic.security.allowCryptoJDefaultPRNG = true >
< 29 July 2015 9:08:10 CEST > < Info > < WebLogicServer > < BEA-000377 > < since Java hotspot 64-bit Server VM WebLogic Server Version 20, 5 - b03 Sun Microsystems Inc. >
< 29 July 2015 9:08:21 CEST > < Info > < management > < BEA-141107 > < Version: WebLogic Server 10.3.6.0 Mar 15 Nov 08:52:36 PST 1441050 2011 >
< 29 July 2015 9:08:26 CEST > < error > < management > < BEA-141244 > < errors diagram validation when parsing D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\config\config.xml - qname for xsi: type invalid: 'ext:oam-servlet-authentication-filter-ia-providerType' in the realm of element @ http://xmlns.Oracle.com/WebLogic/domain >
< 29 July 2015 9:08:26 CEST > < error > < management > < BEA-141244 > < schema when parsing D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\config\config.xml - D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\ < unknown > validation errors: 14:9: error: unable to load the java type corresponding to t=oam-servlet-authentication-filter-ia-providerType@ http://xmlns.Oracle.com/WebLogic/security/extension >
< 29 July 2015 9:08:26 CEST > < opinion > < WebLogicServer > < BEA-000365 > < server status changed initially >
< 29 July 2015 9:08:26 CEST > < Info > < WorkManager > < BEA-002900 > < self-adjusting Initializing of thread pool >
< 29 July 2015 9:08:26 CEST > < opinion > < LoggingService > < BEA-320400 > < D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\servers\soa_server1\logs\soa_server1.log log file will be rotated. Reopen the log file if stopped tailings. This can happen on some platforms such as Windows. >
< 29 July 2015 9:08:26 CEST > < opinion > < LoggingService > < BEA-320401 > < log file was shot in D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\servers\soa_server1\logs\soa_server1.log00001. Log messages will continue to be logged in D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\servers\soa_server1\logs\soa_server1.log. >
< 29 July 2015 9:08:26 CEST > < opinion > < Log Management > < BEA-170019 > < D:\Oracle_IAM_PS3\Middleware\user_projects\domains\base_domain\servers\soa_server1\logs\soa_server1.log server log file is opened. All events in the log server-side will be written to this file. >
< 29 July 2015 9:08:29 CEST > < error > < security > < BEA-090870 > < the domain 'myrealm' could not be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: class of service name [Security: 097533] SecurityProvider of IAMSuiteAgent is not specified...
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: class of service name [Security: 097533] SecurityProvider of IAMSuiteAgent is not specified.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1789)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:443)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:841)
Truncated. check the log file full stacktrace
Caused by: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: class of service name [Security: 097533] SecurityProvider of IAMSuiteAgent is not specified.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
Truncated. check the log file full stacktrace
Caused by: com.bea.common.engine.SecurityServiceRuntimeException: class of service name [Security: 097533] SecurityProvider of IAMSuiteAgent is not specified.
at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
Truncated. check the log file full stacktrace
>
< 29 July 2015 9:08:29 CEST > < opinion > < security > < BEA-090082 > < security initialization using security realm myrealm. >
< 29 July 2015 9:08:29 CEST > < critical > < WebLogicServer > < BEA-000362 > < server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: Security Services [Security: 090399] not available
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:917)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
< 29 July 2015 9:08:29 CEST > < opinion > < WebLogicServer > < BEA-000365 > < changed failed State Server >
==============================================
Problem solved by following Doc ID 1271932.1
-
Hello
I installed oralce soa suite 11 g more...! dorsal oracle 10g database... !!!
I am able to start my domain server
G:\Oracle\Middleware\user_projects\domains\base_domain\bin > startWebLogic
G:\Oracle\Middleware\user_projects\domains\base_domain\bin > startManagedWebLogic soa_server1
(1) when I go to my
httP://localhost:7001 / em, I saw my soa_server running, but when I could not start resources soa-infra adapters... !!!
(2) in my jdeveloper when I create the connection to my application server, test the connection c shows all 9 of 9 success, but when I try to deploy
in the select a server page, I chose my connection, but on the page of soa server select next page, it displays an error
error in search of SOA server configured for the deployment of archive.deploying cannot continue.
I posted the error occurred in G:\Oracle\Middleware\user_projects\domains\base_domain\bin > startManagedWebLogic soa_server1 in nxt message
and
error message occurred in the deployment... !!!
pls help me guysIt sounds like the question that you get when you run 11.1.1.4.0 SOA Suite on Oracle XE.
To fix:
(1) (use UCR of abandonment of the SOA Suite schemas and tablespaces
(2) set the environmental variable RCU_JDBC_TRIM_BLOCKS = TRUE and then run UCR again to recreate patterns on SOA and storage -
I use a single node of consistency on Solaris 10, 64-bit 1.7 JVM. It works very well. However, the problems start when I'm trying to start a 2nd node of Eclipse running on the JVM 64-bit Windows that is configured exactly the same as on Solaris. Observing these two newspapers JVMs, I can see that each node detects the other, however, the node that was started the 2nd always gets the exception below and ends. It doesn't matter on what OS I starts it's always the 2nd JVM that gets this error.
What can be wrong? What is my config? If it wasn't, why the first node set up and working properly?
Here's the exception:
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] ERROR consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < error > (thread = Cluster, member = 3): this cluster node failed to deserialize the config
java.io.StreamCorruptedException: invalid type: 100
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2348)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:74)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:1)
at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
to com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService$ ServiceJoining.read (ClusterService.CDB:14)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.deserializeMessage(Grid.CDB:19)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:21)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onNotify(ClusterService.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:51)
at java.lang.Thread.run(Thread.java:724)
Stop the Cluster service.
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] ERROR consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < error > (thread = Cluster, member = 3): asked to stop the cluster service.
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] DEBUG consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < D5 > (thread = Cluster, Member = n/a): Service de Cluster in the cluster on the left
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] ERROR consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < error > (thread = Invocation: management, Member = n/a): InvocationService ending because of an exception not handled: java.lang.RuntimeException
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] ERROR consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < error > (thread = Invocation: management, Member = n / a):
java.lang.RuntimeException: join query has been abandoned
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.doServiceJoining(ClusterService.CDB:86)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onServiceState(Grid.CDB:23)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.setServiceState(Service.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.setServiceState(Grid.CDB:21)
to com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$ NotifyStartup.onReceived (Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:23)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:51)
at java.lang.Thread.run(Thread.java:724)
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] DEBUG consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < D5 > (thread = Invocation: management, Member = n/a): service management left the cluster
2013-09-26 14:15:29, 378 [Logger@9254847 12.1.2.0.0] DEBUG consistency - 2013-09-26 Oracle coherence GE 12.1.2.0.0 14:15:29.378/6.164 < D4 > (thread = Cluster, Member = n/a): delayed ignorant response to the JoinRequest for management 14:15:29.42 2013-09-26
POF serialization (-System Dtangosol.pof.enabled = true property) is enabled on the first node and disabled the second.
-
Problems with VSS and DTC... dunno how or serious errors are
One of the two messages I get the message this is the right place to post
Volume shadow copy Service information: could not start the Server COM with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV. [0 x 80110802]
Operation:
Get an interface that can be called by for this provider
List of interfaces for all providers support this contextContext:
Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167}
Class ID: {790f2886-9889-4c99-8ef5-531add05d044}
Snapshot context: 0
Snapshot context: 0Hey artinusa,.
Welcome to the Microsoft Answers site.
This error message is seen only in a Windows Server environment.
The community more suited for this problem would be the Microsoft TechNet community. Please post your query it better support.
http://social.technet.Microsoft.com/forums/en-us/winserverfiles/threads
Have a great day.
Kind regards
Shinmila H - Microsoft Support
Visit our Microsoft answers feedback Forum and let us know what you think.
-
Could not start the time service windows on the local computer 2 error
Cannot update the system clock of time Internet.After double click to display the time in the taskbar, the Date and time properties window appears.
Then I time tab-click Internet, and then click Update now - this produces the following message..."Year error occurred getting the status of the last synchronization." The RPC server is unavailable ".Then I clicked on start > Control Panel > Administrative Services > Services > time WindowsI click Start the service and get the following message..."Could not start the time service windows on local computer.""error 2: the system cannot find the file specified."Help! What now?Hello
Glad to know that the problem has been resolved. If you have additional questions on the computer, please ask your question about Windows and we will be happy to help you.
-
Could not start the Windows Vista firewall
Hi all
I can't start the Windows Firewall service in anyway.I can't open it via Control Panel, as it is said simply: "the Windows Firewall settings cannot poster because the asscioated service is not running. You want to start the Windows Firewall service? »I click "Yes", then he said: 'Windows cannot start the Windows Firewall service. There is no error code indicated.I tried running "wf.msc" using the Microsoft Management Console. When this window appears, he says: "there was an error opening the Windows Firewall with advanced snap-in security.; The Windows Firewall with Advanced Security snap could not load. Restart the Windows Firewall service on the computer that you are managing. "Error code: 0x6D9.As it seems, I can not start it this way or the other.I pressed Ctrl + Alt + Delete and click on the Services tab, then click services on the bottom, and this opens the Services window.In the new Services window, I try to start the service "Windows Firewall". I get a message saying: "Windows could not start the Windows Firewall service on the Local computer.; Error 1068: the dependency service or group could start. »Therefore, it does not. The service is set to automatic.I found another process called 'Base filtering engine', which I discovered is related to the use of the Windows Firewall service. Then, that I try to start this service, and he said: "Windows has no start the engine service of filtering based on Local computer." Error 0 x 80320009: an object with this GUID or LUID already exists. »Still, I can't find a way to fix the problem. In addition, the service is set to automatic.So if someone could help me, give me ideas or tell me how to solve the problem, it would be greatly appreciated. Thanks in advance.P. S. sometimes, when I type things in the command prompt, I get a message saying that "the requested operation requires a rise." What it means?EDIT:The base filtering engineIKE and AuthIPsec Keying ModulesInternet Connection Sharing (ICS)IPsec policy agentRouting and remote accessWindows event collectorWindows FirewallAll of these services don't work, with each saying "Windows did not start the * service * service on Local computer.; Error 1068: The dependency service or group could start. ", with the exception of the Base Filtering Engine service.EDIT:I believe that the motor of filter of Bae is the root cause of the problem, because when I try to start it, it says "Windows cannot start the engine service of filtering based on Local computer. Error 0 x 80320009: an object with this GUID or LUID already exists. ", so that all the other programs on this service, said depedent" Windows did not start the * service * service on Local computer. " ; Error 1068: The dependency service or group could start. ».EDIT:Hello everyone, I solved the problem. The problem is a corrupted, file called "secdrv.sys. To resolve this problem, I had to first download the file "secdrv.sys' out of my operating system CD. To do this, you must create a partition and "mount" a file on CD, on the newly created partition. The file you have to climb is and is called: "*: \sources\install.wim. Extending .wim means a "file system Windows Image" and to see what files it contains, you will need to download what we call the "Windows Automated Installation Kit". Explicit instructions on the installation procedure and where to get this program, is here: "http://www.vistax64.com/tutorials/86959-access-vista-install-dvd-files.html". Once you have the file mounted, just search the area mounted for "secdrv.sys", then copy and paste it in "C:\Windows\System32\drivers" or that where the drivers from your system. After that, restart and the BFE service and all of its dependencies should work properly. Thanks for the good help like SpiritX.Hello everyone, I solved the problem. The problem is a corrupted, file called "secdrv.sys. To resolve this problem, I had to first download the file "secdrv.sys' out of my operating system CD. To do this, you must create a partition and "mount" a file on CD, on the newly created partition. The file you have to climb is and is called: "*: \sources\install.wim. Extending .wim means a "file system Windows Image" and to see what files it contains, you will need to download what we call the "Windows Automated Installation Kit". Explicit instructions on the installation procedure and where to get this program, is here: "http://www.vistax64.com/tutorials/86959-access-vista-install-dvd-files.html". Once you have the file mounted, just search the area mounted for "secdrv.sys", then copy and paste it in "C:\Windows\System32\drivers" or that where the drivers from your system. After that, restart and the BFE service and all of its dependencies should work properly. Thanks for the good help like SpiritX.
-
NAC AD SSO error: could not start the SSO service. Please check the configuration.
Hi, can someone please help me with a problem of SSO?
I'm trying to start the SINGLE sign-on service, but when I try to update I get the error message: "error: could not start the SSO service.» Please check the configuration. »
The announcement is a Windows 2008 Server Standard R2 (64-bit) running at a 2003 domain functional level. (several servers) with the deployment of the OOB
I was unable to ping the advertising server CASE CLI, so I created a static route to the announcement on the server of the ANC, and after that I successfully of the NAC Server ping IP address of the AD. The nac_server.log when I try to start the SSO:
[[email protected]/ * / _primary_ag ~] # ping 10.200.0.3
PING 10.200.0.3 (10.200.0.3) 56 (84) bytes of data.
64 bytes from 10.200.0.3: icmp_seq = 1 ttl = 128 time = 0,247 ms
64 bytes from 10.200.0.3: icmp_seq = 2 ttl = 128 time = 0,232 ms
-ping - 10.200.0.3 statistics
2 packets transmitted, 2 received, 0% packet loss, time 999ms
RTT min/avg/max/leg = 0.232/0.239/0.247/0.017 ms
[[email protected]/ * / _primary_ag ~] # tail-f /perfigo/access/tomcat/logs/nac_server.log
2012-07-27 17:20:39.079-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:20:39.079-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:20:39.080-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:20:39.080-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:20:39.080 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:20:39.080 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:20:39.081 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:20:39.081 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:20:39.081-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:20:39.081-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:20:41.776-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:20:41.776-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:20:41.777 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:20:41.777 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:20:41.777-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 1
2012-07-27 17:20:41.777-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 1:DURATION = 0
2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = casuser
2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = casuser:DURATION = 0
2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = nissin.com.br
2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = nissin.com.br:DURATION = 0
2012-07-27 17:20:41.779-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = NISSIN.COM.BR
2012-07-27 17:20:41.779-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = NISSIN.COM.BR:DURATION = 0
2012-07-27 17:20:41.779 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:save
2012-07-27 17:20:41.779 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:save:DURATION = 0
2012-07-27 17:20:41.780 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer
2012-07-27 17:20:41.780 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer:DURATION = 0
2012-07-27 17:20:58.605-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300
2012-07-27 17:20:58.608-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}
[2012-07-27 17:20:58.608-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997
[2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: removed socket: 173d72d [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=11093,localport=1099]]
2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 0 DEBUG
2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE DEBUG =]
2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 0 DEBUG
2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE DEBUG =]
2012-07-27 17:21:18.610-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300
2012-07-27 17:21:18.613-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}
[2012-07-27 17:21:18.613-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997
2012-07-27 17:21:38.615-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300
2012-07-27 17:21:38.618-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}
[2012-07-27 17:21:38.618-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997
2012-07-27 17:21:41.794-0300 DEBUG Thread-246 com.perfigo.wlan.common.HttpClientResource - go to url https://10.200.48.100:443 / wlan/gss/GSSNotificationServlet ...
[2012-07-27 17:21:41.813-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: added the socket: 1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]
2012-07-27 17:21:41.814-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1
[2012-07-27 17:21:41.814-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]
2012-07-27 17:21:41.814-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOStatus
2012-07-27 17:21:41.814-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOStatus:DURATION = 0
2012-07-27 17:21:44.103-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:44.103-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:21:44.106 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 1
2012-07-27 17:21:44.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:21:44.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:49.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:21:49.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:21:49.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:21:49.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:21:54.107-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:54.107-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:21:54.109 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:21:54.109 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:21:54.110 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:21:54.110 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:21:54.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:21:54.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:21:58.619-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300
2012-07-27 17:21:58.622-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}
[2012-07-27 17:21:58.622-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997
2012-07-27 17:21:59.109-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:59.109-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:21:59.111 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:21:59.111 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:21:59.112 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:21:59.112 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:21:59.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:21:59.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:04.111-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:04.111-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:04.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 1
2012-07-27 17:22:04.113 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:04.113 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:22:04.114 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:04.114 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:04.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:04.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:09.115-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:09.115-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 1
2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:09.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:09.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:14.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:14.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:14.117 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 1
2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:14.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:14.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:17.017-0300 DEBUG RMI RenewClean-[10.200.2.103:1099] com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 2
[[2012-07-27 17:22:17.017 - 0300 DEBUG RMI RenewClean-[10.200.2.103:1099] com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]]]
[2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: socket: 59725 c added [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]
2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 3
[[[2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]], 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]]
2012-07-27 17:22:18.624-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300
2012-07-27 17:22:18.627-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}
[2012-07-27 17:22:18.627-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997
2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:19.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:19.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:19.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:19.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:24.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:24.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:24.121 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:24.121 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:22:24.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:24.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:24.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:24.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
2012-07-27 17:22:29.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:29.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:29.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:29.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:22:29.123 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:29.123 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:29.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:29.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
[2012-07-27 17:22:32.022-0300 RMI Scheduler (0) DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: removed socket: 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]]
2012-07-27 17:22:32.022-0300 com.perfigo.wlan.ssl.SSLLog RMI Scheduler (0) DEBUG - RMISocketFactory:CACHED_SOCKETS_SIZE = 2
[[2012-07-27 17:22:32.022-0300 RMI Scheduler (0) com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]]
[2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: moved socket: 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]
2012-07-27 17:22:32.022-0300 TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1 connection
[2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]
2012-07-27 17:22:32.022-0300 TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1 connection
[2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]
2012-07-27 17:22:34.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 1
2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo
2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0
2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader
2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0
2012-07-27 17:22:34.124 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init
2012-07-27 17:22:34.124 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0
2012-07-27 17:22:34.125 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync
2012-07-27 17:22:34.125 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0
2012-07-27 17:22:34.125-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip
2012-07-27 17:22:34.125-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0
[[email protected]/ * / _primary_ag ~] #.
Thank you
Moises,
I wanted to know if you have followed these steps:
Thank you
Tarik Admani
* Please note the useful messages *. -
I ask a question, expanding to another thread '', on the start-up and stop SQLFire.
My topography has four servers, two locators, and two servers (Server 2 SQLFire each) on which the database is deployed. When you start the batch, without no history running, all right. Adding and removing servers in the cluster, also seems to work very well. However, when the whole of the system, its stopped by sqlf shut-down-all, it starts up, things go wrong.
I met the same problem described by the called thread, that is, it seems to be an addiction to data - which is not resolved. I start locators first, one at a time. When one starts, data dependence becomes apparent. The Locator seems to start, but the sequence goes in a loop around the data dependence. When you try to stop the same Locator, he returned in a "stopping" State, where it does not recover. Try a reboot, translated by [A SQLFire Locator works already in the directory "C:\SQLFire\Locator"]. The "stoppage of sqlf Locator", producing a further: "timeout for SQLFire Locator at the stop, the status is: SQLFire Locator pid: 4956 status: stop ' results; and the "sql shut-down-all:, throws a long error that includes:" java.io.FileNotFoundException: shut_down_all.log (access is denied) "and 'Could not start the 'sqlfire' database'. '. Both of these appear to be the crux of the matter.
I don't know what data it is dependent, because I haven't added all the data that will be persisted. However, the system starts with default records. I tried to check if these default disks are required, which seem not to be and I'm leaving for the partition and replication information, to read when the system starts / begins. I can't understand why locators cannot start without the database, without any dependence on the data, and also why the system seems to require a sequence to start. Is that not the purpose of SQLFire, i.e. a solution supporting the cross, which can be started in any sequence of old? If an operator needs to get this bad, for a production system, should be that the entire solution be recharged from external sources, and that could take awhile. It would seem, once the system in this state, i.e. the dog chasing its tail, he doesn't get, and I have to delete all the bookmarks and servers and launch all to reboot from external data sources.
I'll be dilly, or is it a problem in general, experienced by others?
I would be grateful for any comments, and if you could indicate the respective documentation, as I struggle to establish a correlation between the problems of documentation, even Google hits, when it encounters any problems with SQLFire.
I appreciate your time and efforts.
Hello
I checked the docs and they are not accurate on information in Windows when using the cmd shell. The ampersand does not work correctly when called from a shell, Cygwin, or on UNIX/POSIX systems. Will get corrected.
Please, use the start command to start in the background of a single command window / batch script:
beginning of "locator" cmd /c sqlf locator...
beginning of "server1" cmd /c sqlf server...
etc.
Add option/min to start the minimized for example windows cmd start 'locator' / min cmd /c sqlf locator beginning...
Or launch each 'start-up of the sqlf Locator', 'sqlf-start server' etc to separate windows command prompt.
Thank you
Felicia
Post edited by: SumedhWale
-
root.sh failed with the CRS-2800: could not start the 'ora.ctssd' resource as it is
Cannot start the "ora.ctssd" resource as it is already in the INTERMEDIATE State.
I tried to install two-node RAC on linux REDHAT, I met because of errors:
Beginning of the resource 'ora.crsd' failed
CRS-2800: could not start the 'ora.ctssd' resource as it is already in the State INTERMEDIARY on the server
CRS-4000: Start command has failed, or completed with errors.
Exclusive mode Clusterware ready beginning of Clusterware Services failed to 6475 /u01/app/11.2.0/grid/crs/install/crsconfig_lib.pm line.
/U01/app/11.2.0/grid/Perl/bin/perl-I/U01/app/11.2.0/grid/Perl/lib-I/U01/app/11.2.0/grid/CRS/install /u01/app/11.2.0/grid/crs/install/rootcrs.pl execution failed
How to solve this problem?
runCluvfy has been correctly executed.
I discovered on the second node (oracle02), there is no any daemon running. But on the local installation (oracle01) node:
[[email protected] bin] #. / stat crsctl res-t--init
--------------------------------------------------------------------------------
TARGET STATE SERVER STATE_DETAILS NAME
--------------------------------------------------------------------------------
Cluster resources
--------------------------------------------------------------------------------
ORA.asm
1 road to oracle01 online
ORA.cluster_interconnect.haip
1 oracle01 online
ORA. FIU
1 OFFLINE IN OFFLINE MODE
ORA.crsd
1 ONLINE OFFLINE
ORA. CSSD
1 oracle01 online
ORA.cssdmonitor
1 oracle01 online
ORA.ctssd
1 LINE intermediate oracle01 bad check return.
ORA. DiskMon
1 oracle01 online
ORA.drivers.ACFS
1 oracle01 online
ORA.evmd
1 OFFLINE IN OFFLINE MODE
ORA.gipcd
1 oracle01 online
ORA.gpnpd
1 oracle01 online
ORA.mdnsd
1 oracle01 online
[[email protected] bin] #.
How to make the next step? What is the difficulty so that my installation is successful.
Thanks in advance.Hi Angelina,.
I got this error when I tried to install Oracle RAC on VMware with unassigned shared disk. When I attributed it which fixed the problem.
Kind regards
Gennady -
Could not start the print job. Is available from the printer? Charge of CS3 on Windows 7 64 bit
Hi all:
I have a PC network. As part of their basic installation, I load on CS3. I started to integrate Windows 7 and found the following on each problem, but not on one of the XP.
When my users try to print from Acrobat 8 that they receive the following message is displayed: "could not start the print job. I have a printer? ».
This happens when trying to print to one of our printers, the printer HP designjet 1055. I have the drivers 32 bit and 64 bit installed on our print server.
I read a post somewhere in program files common files could play up because there are 2 location of files of program on windows 7 - but I'm no more on this one here.
I don't know there is a work around for this issue, recorded for the 101 others.
Someone at - it ideas?
CS3 has AA7 I think, maybe AA8. Compatibility Win7's AA9. Others may work, but the risk becomes yours. Adobe will tell you simply to upgrade. Several people have AA8 working most of the time. I think that a few may have succeeded with AA7, but I'm a little surprised.
-
Original title: HELPPPPP
My computer a little flag in the background with a x... said red it turn security service windows, but when I try to turn it on... it said windows security service cannot be started :/
Hey ChelseaHarris,
Take a look at two responses in the thread below the link to see if they allow the Windows launch security service:
Could not start the Windows Security Center service.If these steps do not help, try to run a full scan using the Scanner from Microsoft which can be downloaded using the link below:
Microsoft safety scannerHope that helps.
-
I have error #1053 windows could not start the printer spooler. Help
Windows could not start the printer spooler. I received the error #1053.
whatever it is sent to the printer never finished loading and crashes to the top
my computer, so I have to re - start.This forum is for posting comments on the web site of Microsoft Answers, is not for technical questions. Ask your questions to http://answers.microsoft.com/en-us/windows/forum/hardware, making sure that you specify your Windows version in the drop-down lists at the top.
-
Update CPU which proved later to be bad. Replaced by original CPU. Re-installed Windows XP Home using a slipstreamed CD that I burned the original non - OEM drive that has Service Pack 2. Integrated Service Pack 3 which I got from the MS. site Everything works well except for Windows Update. The setting seem to be correct in Administrative Tools/Services. The status of the Service is "stopped". When I try to start the automatic updates from Administrative Tools/Services I receive "error 127: the specified procedure could not be found." Also "error 0 x 80240036: could not start the service automatic updates on local computer» Used the range of anti-virus and malware and found nothing. Currently using Avast 7.0.1426. I also used various tools of Fix - It MS nothing helps. Any help would be greatly appreciated. Thank you.
Hello
1. what application or antivirus security suite is installed and your current subscription?
2 Norton (another) or a McAfee application ever installed on this machine?
3. What are the fix applications that you used so far to try to fix this problem?
Try the next method and check if that helps you with the question of the 127 error you receive.
Method 1: Rdding the DLL file by doing the following:
1. Click Start and click Run, in the search box type CMD and press to enter.
2. right click on CMD in the list and click "Run as Administrator".
3. type the following command and press ENTER. Regsvr32 msvcp71.dll
4. close the command prompt window.Method 2: run the file system (CFS) Checker:
(Note: you need an XP installation disk to start the System File Checker search.)
The SFC command is used to detect and resolve problems with the files on Windows XP and Windows Vista computers. This command allows you to launch the Windows File Protection Service and allows you to analyze all integrity-protected Windows files and replace all problematic files identified.
1. click on start, and in the box to start, search type CMD
2. right click on CMD in the list and click "Run as Administrator"
3. type the following command and press ENTER. Sfc/scannow
4. close the command prompt window.For more information on scan SFC (System File Checker), please look in the link mentioned below.
http://support.Microsoft.com/kb/310747
I hope this helps.
-
Could not start the Security Center Service
I clicked on Windows security alerts, it showed "The Security Center Service is disabled". Then I clicked "Activate now", came a "Could not start the Security Center Service" message. Please tell me what I need to do.
Thank you very much!!!
Longpo
See if these are useful:
http://support.Microsoft.com/kb/2519899
OR
-
I had a crash dump blue screen, tried solutiions to the problem and told me to go to windows update and download all windows updates. downlownloading all updates failed and I got the error.
Code 80246008
Click on get help with this error and was instructed to go to services and start the background intelligent service services, it gave me the error message;
Windows could not start the background service Itelligent transfer service on local computer. 87 error: The parameter is incorrect
Not very computer savvy! no idea what it all means or what I would do to this topic! Thanks a lot for any help
Try this:
To change or restart the Service (BITS) Background Intelligent Transfer
Open administrative tools by clicking the start
, clicking Control Panel, clicking system and Maintenance, and then clicking Administrative Tools.Double-click Services.
If you are prompted for an administrator password or a confirmation, type the password or provide confirmation.Right click on the service of Intelligent Transfer (BITS) background and then click Properties.
Under the tab general, next to startup type, make sure that automatic (delayed start) is selected.
Next to Service status, check whether the service is started. If not, click Start.
Maybe you are looking for
-
Satellite L755: Win8.1 update - message Flash cards: free trial win 8
Salvation; After that I updated to windows 8.1 win8 mc I get message after my laptop (Toshiba Flash Card) is like the image below, No idea how to solve this problem? I remove VAP functions, and then system key utility and re driver install - no chang
-
Inspection of band continues using the Texture palette
Hi all I'm working on a system of continuous inspection of nonwoven. I was thinking of using the Texture palette that seems to work well for my application. However when playing manual Concepts of vision, I found a sentence which confuses me a bit: "
-
My favorite game of all time seems to not work with VISTA, because VISTA has more MSVBVM50. DLL. is there other than to throw my VISTA into the trash. I am an old user of WINDOWS ME 2000 and feels a heck of a time getting like VISTA. I'm not slightly
-
Driver power state failure; BSOD; Cannot open the minidump files
Two weeks, my computer with Vista has started giving me a BSOD with status message driver failure. I found the minidump files, but cannot open them. The BSOD usually occurs after the computer has entered a sleep or hibernation. I have not added an
-
Question about my windows experience index number
I have a windows 7 and my lowest number is 7.7 except my main hard drive, which is 5.9, so my overall is 5.9. I think this is because when I set up the computer that I lowered the score of 2 terabytes on hard drive to a a 1 terabyte hard drive. My qu