• Monitoring
  • Status
  • Logs
  • Statistics
  • Packages
  • Technical Support
• System Setup
  • User
  • Network
  • Email
  • Date & Time
  • License
  • Log Level
  • Backup
  • Database Archive
  • Restore
  • Upgrade
  • Language Pack
• Configuration
  • Database
  • Authetication
  • Mediaout Ports
  • Virtual Matrix
  • SNMP Trap Destination
  • Media Server
  • Storage
  • Drivers
  • Devices
  • Camera Firmware Upgrade
• Downloads

Description
2010-04-08 12:02:46,726 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-08 12:08:51,880 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-16 16:07:26,029 Thread-24 ERROR comm - comm.SSLConnectionManager : Error In Closing A Channel. Exception :Inbound closed before receiving peer's close_notify: possible truncation attack?
2010-04-17 12:02:46,726 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-18 12:08:51,880 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-19 16:07:26,029 Thread-24 ERROR comm - comm.SSLConnectionManager : Error In Closing A Channel. Exception :Inbound closed before receiving peer's close_notify: possible truncation attack?
2010-04-20 12:02:46,726 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-20 12:08:51,880 pool-1-thread-5 ERROR credentials - credential.CredentialServiceCC : Cred Sequence is null after gw ready message for the gateway /SanJose/gw_FHH1129000F
2010-04-21 16:07:26,029 Thread-24 ERROR comm - comm.SSLConnectionManager : Error In Closing A Channel. Exception :Inbound closed before receiving peer's close_notify: possible truncation attack?