Showing posts with label bug. Show all posts
Showing posts with label bug. Show all posts
Wednesday, November 20, 2013
sonarqube presentation
I did a SonarQube presentation at work. Feel free to check and use it as you like here.
at
16:24
Labels:
architecture,
bug,
checkstyle,
coding rules,
complexity,
design,
documentation,
duplication,
findbugs,
pmd,
sonarqube,
unit test
Wednesday, May 11, 2011
a great way of improving your java code: findbugs!
We decided to make our project's code more robust and bug-free. I suggested the use of Findbugs which is basically a program that uses static analysis to search for bugs in your java code. It can be used as IDE plug-in or as a stand-alone application. Findbugs pinpoints problematic places in your code. There are many type of pre-defined problems that Findbugs looks for like duplicate case branches in switch statements, streams which are not closed in all cases, inefficient use of map iterator, redundant comparison to null ... etc. I can't recommend Findbugs enough.
Monday, February 7, 2011
thank you axis2 for this handful of close_wait
In one of our projects we are using axis2 1.4 for generating the client side of the web service. Our web service part is working for few hours but gets stuck for no apparent reason. After I investigate a little I saw that it generates lots of sockets with CLOSE_WAIT state which results this freeze. I google a bit about similar problems with Axis2 and saw that this a known bug. Here's the source I used for fixing it. As explicitly calling the garbage collector didn't seem like a good solution, and as I can't upgrade axis2, I opt for changing the HTTP version to 1.0. For this I set a single field in the ServiceStub by calling
from ServiceStub where this object is created.
After that, this CLOSE_WAIT bug is fixed.
serviceStub._getServiceClient().getOptions()
.setProperty(
org.apache.axis2.transport.http.HTTPConstants.HTTP_PROTOCOL_VERSION,
org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10)
from ServiceStub where this object is created.
After that, this CLOSE_WAIT bug is fixed.
Wednesday, May 27, 2009
vncconfig's copy/paste bug
I'm doing my coding on a workstation by connecting to it with a vnc client. To be able to do copy/paste or cut/paste between my computer and the workstation I use vncconfig. But there are times it does not work at all. You copy your text on one computer and when you try to paste it on the other computer, nothing happens. I discovered a workaround for this. Assume that you're trying to copy/paste from computer A to computer B and nothing happens. Open the screen of computer B, copy some text from it (anything). Then open computer A and copy the desired text, later paste it in computer B. It'll do the paste now.
Subscribe to:
Posts (Atom)