Mined Opinions For API: google-threadlocal

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • thanks for the reply will, i tried with the above JVM options too but still no luck.. details
  • Because TCP sockets handled like open file handles.. details
  • Try using another one by setting the correct JVM OPTS: CODESNIPPET_JAVA4 .. details
  • well, but its still just a "guess".. details
  • Yes, very good detective work.. details
  • Yes, very good detective work.. details
  • Thanks for the answer.. details
  • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this.. details
  • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in-responsibility problem occurs, then you may have an open socket file descriptor leak.. details
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.. details
  • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear.. details
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.. details
  • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear.. details
  • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web-apps server code).. details
Summaries the opinions about google-threadlocal using topic modeling.
  • 0. jvm answer tcp solve call prior deserialization reply detective opts: 7
    • thanks for the reply will, i tried with the above JVM options too but still no luck.. details
    • Try using another one by setting the correct JVM OPTS: CODESNIPPET .. details
    • well, but its still just a "guess".. details
    • Because TCP sockets handled like open file handles.. details
    • Yes, very good detective work.. details
    • Thanks for the answer.. details
    • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this.. details
  • 0. open hashtable socket solve add connection database apply dissapear case: 4
    • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web-apps server code).. details
    • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.. details
    • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear.. details
    • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in-responsibility problem occurs, then you may have an open socket file descriptor leak.. details
Summaries of the opinions about google-threadlocal using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • Because TCP sockets handled like open file handles .
  • Try using another one by setting the correct JVM OPTS: CODESNIPPET JAVA4 .
  • thanks for the reply will, i tried with the above JVM options too but still no luck .
  • well, but its still just a "guess" .
  • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this .
  • Thanks for the answer .
  • Yes, very good detective work .
  • Because TCP sockets handled like open file handles .
  • Try using another one by setting the correct JVM OPTS: CODESNIPPET JAVA4 .
  • thanks for the reply will, i tried with the above JVM options too but still no luck .
  • well, but its still just a "guess" .
  • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this .
  • Thanks for the answer .
  • Yes, very good detective work .
  • Because TCP sockets handled like open file handles .
  • Try using another one by setting the correct JVM OPTS: CODESNIPPET JAVA4 .
  • thanks for the reply will, i tried with the above JVM options too but still no luck .
  • well, but its still just a "guess" .
  • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this .
  • Thanks for the answer .
  • Yes, very good detective work .
  • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in responsibility problem occurs, then you may have an open socket file descriptor leak .
  • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web apps server code) .
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic .
  • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear .
  • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in responsibility problem occurs, then you may have an open socket file descriptor leak .
  • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web apps server code) .
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic .
  • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear .
  • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in responsibility problem occurs, then you may have an open socket file descriptor leak .
  • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web apps server code) .
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic .
  • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear .
Summaries of the opinions about google-threadlocal using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about google-threadlocal using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Onlysentiment:
  • Yes, very good detective work.
  • N/A
Features:
  • thanks for the reply will, i tried with the above JVM options too but still no luck.
  • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in-responsibility problem occurs, then you may have an open socket file descriptor leak.
Bug:
  • N/A
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.
Usability:
  • Try using another one by setting the correct JVM OPTS: CODESNIPPET_JAVA4 .
  • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.
  • Onlysentiment: 2
    1. general: 2
      • Yes, very good detective work.. details
      • Thanks for the answer.. details
  • Features: 2
    1. general: 2
      • thanks for the reply will, i tried with the above JVM options too but still no luck.. details
      • Because TCP sockets handled like open file handles.. details
  • Usability: 4
    1. general: 4
      • Try using another one by setting the correct JVM OPTS: CODESNIPPET_JAVA4 .. details
      • well, but its still just a "guess".. details
      • Yes, very good detective work.. details
      • This is not optimal, but if you can access value you need (via ThreadLocal, filled prior to calling deserialization) you would at least be able to solve this.. details
  • Usability: 3
    1. general: 3
      • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.. details
      • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear.. details
      • As a second guess you may also have a HashTable memory leak that can be caused even in Java when not cleaning up a HashTable of Java objects correctly (somewhere in the web-apps server code).. details
  • Features: 1
    1. general: 1
      • If the number of open sockets after tomcat start is less or little and on the other hand is devastating high when your in-responsibility problem occurs, then you may have an open socket file descriptor leak.. details
  • Bug: 2
    1. general: 2
      • So, in my case i solved the problem by designing the database connection in a per thread basis using ThreadLocal generic.. details
      • If that problem applies to you an you add a similar fix to the one i mentioned, your problems will dissapear.. details