[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

2015-08-04 Thread sagi.sinai-gla...@ericsson.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sagi Sinai-Glazer commented on  JENKINS-27514 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM  
 
 
 
 
 
 
 
 
 
 
Same here... see attached Support Bundle (support_2015-08-04_14.10.32.zip) for more details. Also seems to be related to JENKINS-23560 and JENKINS-26769. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

2015-08-04 Thread sagi.sinai-gla...@ericsson.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sagi Sinai-Glazer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27514 
 
 
 
  Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sagi Sinai-Glazer 
 
 
 

Attachment:
 
 support_2015-08-04_14.10.32.zip 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [monitoring] (JENKINS-21902) Add Waiting / Blocked on information in textual thread dump

2014-06-16 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-21902


Add Waiting / Blocked on information in textual thread dump















The problem with using /threadDump is that it uses the main Jenkins UI to display it.
This means that in case you have the Queue is locked, the page will not be generated.
The nice thing about the monitoring plugin is the fact that it doesn't use any Jenkins UI, and therefore isn't influenced by such problems and actually help detect them... but again, without the locking information - it's not really helpful. 

One more note - in many cases the administrators of the instance do not have access to the backend VM and therefore it's hard or almost impossible to get a jstack thread-dump.

And as for Jenkins development - I don't think that in the near future we'll see the enough lock-free patterns to replace all that is currently used.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit

2014-04-01 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-21547


Add information to console log when a job is aborted by gerrit















@rin_ne - if your pull request was already merged (20.3.2014) - then why is this ticket not yet resolved?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit

2014-03-31 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-21547


Add information to console log when a job is aborted by gerrit















"Aborted by Anonymous" - is confusing and misleading!
I would suggest using this or similar text: "Aborted by Gerrit-Trigger" or even better "Aborted by Gerrit-Trigger due to new patchset created"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-19544) OutOfMemory due to unbounded storage in OldDataMonitor

2014-03-24 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-19544


OutOfMemory due to unbounded storage in OldDataMonitor















Will this fix be back-ported to LTS versions?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [monitoring] (JENKINS-21902) Add Waiting / Blocked on information in textual thread dump

2014-02-21 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-21902


Add Waiting / Blocked on information in textual thread dump















I managed to find a BLOCKED state example that clearly shows that the monitoring plugin is not helping in these cases.

Monitoring plugin:
"Thread-127432" daemon prio=5 BLOCKED
	com.sun.jndi.ldap.Connection.getInputStream(Connection.java:710)
	com.sun.jndi.ldap.Connection.run(Connection.java:832)
	java.lang.Thread.run(Thread.java:722)

jenkins-url/threadDump:
"Thread-127432" Id=193884 Group=main BLOCKED on com.sun.jndi.ldap.Connection@77b338dc owned by "Jenkins cron thread" Id=23
	at com.sun.jndi.ldap.Connection.getInputStream(Connection.java:710)

	blocked on com.sun.jndi.ldap.Connection@77b338dc
	at com.sun.jndi.ldap.Connection.run(Connection.java:832)
	at java.lang.Thread.run(Thread.java:722)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [monitoring] (JENKINS-21902) Add Waiting / Blocked on information in textual thread dump

2014-02-20 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 created  JENKINS-21902


Add Waiting / Blocked on information in textual thread dump















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


monitoring



Created:


20/Feb/14 6:54 PM



Description:


A waiting thread will show in the Monitoring plugin like this:
"http-bio-9029-exec-3493" daemon prio=5 TIMED_WAITING
But on host-url/threadDump screen it'll give more information on the object that is being waited for:
"http-bio-9029-exec-3493" Id=194353 Group=main TIMED_WAITING on com.sun.jndi.ldap.LdapRequest@10f324c

This goes the same for Blocked state.
Without this information the thread-dump feature becomes kind of useless in these situations.




Project:


Jenkins



Priority:


Major



Reporter:


Sagi Sinai-Glazer

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [jobconfighistory] (JENKINS-21600) Enable paging to improve performance

2014-01-31 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 created  JENKINS-21600


Enable paging to improve performance















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Mirko Friedenhagen



Components:


jobconfighistory



Created:


31/Jan/14 3:39 PM



Description:


In case there are jobs with a very long configuration history - currently loading the history page takes a few minutes.
Enabling paging that show only a portion of the information at the time will significantly improve the performance.
This way you can show 100 entries per page, or even better set a default number and let the user change it in case he wants to see more.




Project:


Jenkins



Labels:


performance
paging




Priority:


Major



Reporter:


Sagi Sinai-Glazer

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [jobconfighistory] (JENKINS-19874) Loading job config history with over 20,000 entries takes over 5 minutes

2014-01-31 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-19874


Loading job config history with over 20,000 entries takes over 5 minutes















Stefan - If it's not going to be fixed - then you can close it. I have no use for an open-unaddressed JIRA ticket.
Having said that, I would prefer to keep it as a backlog item...
Purging part of the history does help, but it's still not efficient to go through ALL the entries.
As far as I can tell - enabling paging or some other form of partial loading is the only way to actually resolve this issue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [jobconfighistory] (JENKINS-21411) Add option to easily review changes sequentially (Add Next & Previous links)

2014-01-30 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 commented on  JENKINS-21411


Add option to easily review changes sequentially (Add Next & Previous links)















Yordan - I agree that in case the changes are not consecutive then the question does arise. This is why I stated that in case they are sequential (which is easy to determine programmatically) then we can add the Next/Previous pair comparison. I also agree with your proposition in case they are not one after the other - a next/prev button for each would we a good addition.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [cli] (JENKINS-21017) Jenkins CLI update-job misses custom workspace deletion

2013-12-17 Thread sagi.sinai-gla...@ericsson.com (JIRA)














































Sagi Sinai-Glazer
 updated  JENKINS-21017


Jenkins CLI update-job misses custom workspace deletion
















additional-identities plugins has nothing to do with the ticket.
It's a CLI issue. And a bit of a GUI issue since it's not being updated properly.





Change By:


Sagi Sinai-Glazer
(17/Dec/13 8:42 PM)




Labels:


gui jenkins





Component/s:


cli





Component/s:


additional-identities



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.