[OP-232] spuhnik and memory issues Created: 19/Feb/16  Updated: 11/May/16  Resolved: 20/Apr/16

Status: Closed
Project: Opush
Component/s: None
Affects Version/s: 3.1.1
Fix Version/s: 3.2.0

Type: Bug Priority: Blocker
Reporter: Slim CADOUX Assignee: David Dolcimascolo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS release 6.7


Attachments: HTML File hs_error    
Story Points: 0
Rank: 6965
Sprint: 2016#01

 Description   

Code fixing it

see branch thilaire/OP-232, we are testing it in production but unit tests still to be done

Pre-conditions

Fully capable OBM-stack splitted or in the same server.
Have a configured healthcheck user for everydomain your OBM is controlling.

Reproduction steps

start spushnik probe and monitor it.

Current behavior

  1. after an average time of 2 hours and 30 minutes. spushnik stops to work properly.
  2. It is also impossible to check the heap dump because there is not enough memory avaliable for the java runtime environment NOK

Expected behavior

  1. we should not have to restart spushnik every 2 hours.OK

Additional informations



 Comments   
Comment by Thomas HILAIRE [ 22/Feb/16 ]

Impacts: verify that spushnik continue to work as expected for one request
QA: should be tested with endurance tests (fix already validated in production)

Comment by Jenkins Continuous Integration Server [ 22/Feb/16 ]

SUCCESS: Integrated in opush-master-3.1 #36
OP-232 Close streams used internally (thilaire: 931637abf2e63e972d32c2eaa739451b34d2fb1c)

  • spushnik-server/src/test/java/org/obm/push/spushnik/resources/ScenarioTest.java
  • spushnik-server/src/main/java/org/obm/push/spushnik/resources/Scenario.java
  • client/src/main/java/org/obm/sync/push/client/commands/TemplateDocument.java
    OP-232 Use 0 for the core pool size (thilaire: 90301c61fe0818b951e1c73037a08580e436f68b)
  • wbxml/src/main/java/org/obm/push/wbxml/WBXMLTools.java
Comment by Stephane COLSON [ 20/Apr/16 ]

No need to test anything more that a simple healthcheck with opush. Already in LNG Prod

Comment by Jenkins Continuous Integration Server [ 11/May/16 ]

ABORTED: Integrated in opush-master #262
OP-232 Close streams used internally (thilaire: 99b9c502e623b65bba87f6984445012b4fabb9d3)

  • spushnik-server/src/main/java/org/obm/push/spushnik/resources/Scenario.java
  • spushnik-server/src/test/java/org/obm/push/spushnik/resources/ScenarioTest.java
  • client/src/main/java/org/obm/sync/push/client/commands/TemplateDocument.java
    OP-232 Use 0 for the core pool size (thilaire: b74281a414d91c112bc9be4dea148b2afa360b34)
  • wbxml/src/main/java/org/obm/push/wbxml/WBXMLTools.java
Generated at Fri Aug 23 15:28:03 CEST 2019 using JIRA 6.1.1#6155-sha1:7188aeec9a6b57d61ea04c52f235f15f55c105e2.