Pushkar Dhawale - Software Blog

JBoss 6.0.0 java.lang.ClassCastException: javax.naming.Reference cannot be cast to

2012-07-02T15:35:00.000+12:00

Error: JBoss 6.0.0 java.lang.ClassCastException: javax.naming.Reference cannot be cast to com.xxx.xx.xxx.java

I am using maven3 to remotely run the JUnit based regression test on JBoss 6.0.0. While running a regression test for a Stateless Entity Persistence Bean on JBoss 6.0.0, I encountered the following error:

java.lang.ClassCastException: javax.naming.Reference cannot be cast to com.pfmclient.glt.GLT
    at com.pfmclient.helper.EJBSupport.getGLT(EJBSupport.java:327)

Initially I thought that it means I don't have the ObjectFactory class on my client ClassPath. Thus throwing this error. However, I did have the Object Factory on my client classpath. I had spent hours then I found a solution that fixed the problem.

Fix:

Basically, I needed to include jbossall-client jar in the pom.xml as maven dependency for my project. However, the easiest and correct way to do this in JBoss 6.0.0 is to add the correct maven co-ordidnates for jboss-as-client pom. Add the following dependency to your pom.xml

<dependency>
        <groupId>org.jboss.jbossas</groupId>
        <artifactId>jboss-as-client</artifactId>
        <version>6.0.0.Final</version>
        <type>pom</type>
</dependency>

Please remember this is a fix for you if you use Maven 3 and JBoss 6.0.0

The above Maven artifact dependency will include all the necessary JBoss specific classes and even Java EE API classes required for JBoss 6.0.0.

Reference:

Maven artifact id for JBoss AS6 client jar

JBoss 4.2.2 NoSuchMethodError CommonMessageContext cleanupAttachments

2012-02-01T10:07:00.001+13:00

Getting error in your JBoss 4.2.2 for Web service: NoSuchMethodError

JBoss 4.2.2 NoSuchMethodError CommonMessageContext cleanupAttachments

I was getting a NoSuchMethodError in my JBoss 4.2.2 while trying to invoke my web service. I did not find any relevant information for this on google search. So decided to add this post once I find the solution.

There was nothing wrong with my code. It was happening due to mismatch between jbossws jars while we had upgraded our JBoss ESB to 4.7 version.

The complete stack trace is as given below:

------------------------------------------------------------------------------------------------

java.lang.NoSuchMethodError: org.jboss.ws.core.CommonMessageContext.cleanupAttachments(Lorg/jboss/ws/core/CommonMessageContext;)V
   at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:341)
    at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
    at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
    at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
    at java.lang.Thread.run(Thread.java:662)

-------------------------------------------------------------------------------------------------------

FIX

To fix this, you will need to get the latest for JBoss 4.2.x (or whatever version you have) of these jars jbossws-client.jar and jbossws-core.jar from the JBoss Website

I had to download the complete jboss-4.2.3.GA.zip from this download link
Unpack the jboss-4.2.3.GA.zip to a temp location
You will find the jbossws-client.jar in jboss-4.2.3.GA\client\ folder
You will find other jbossws specific jars in this above folder too that you could think of using/upgrading to.
You will find the jbossws-core.jar in jboss-4.2.3.GA\server\default\deploy\jbossws.sar\ folder
copy the "jbossws-client.jar" to this location: {JBOSS_HOME}\client\ folder
copy the "jbossws-core.jar" to this location of your esb server: {JBOSS_HOME}\server\{your_server}\deploy\jbossws.sar\ folder
Then restart your JBoss server

This should fix your issue. Hope it helps someone..

Google Charts not displayed in IE9

2012-01-26T15:09:00.001+13:00

Google Charts not displayed in IE9 / Google Charts not rendered in IE9 / IE9 is not showing the Google Charts

Google charts are displayed correctly in Firefox and Chrome. But when I open the same page in Internet Explorer 9 (IE9), it shows blank area instead. IE9 does not throw any error either.

Bug:

We usually load the packages in the page before drawing the cart. So check out the package that you are using. If you are using "areachart" or "piechart" then this is the issue. These packages have known IE9 compatibility issues.

Your existing code may look something like this:

google.load("visualization", "1", {packages:["piechart"]});
google.setOnLoadCallback(drawChart);

....

.....

chart.draw(data, {width: 400, height: 240, is3D: true, legend: 'right', legendFontSize: 10, colourArray});

Fix:

change your package to "corechart" and your chart.draw parameters will also change as follows;

google.load("visualization", "1", {packages:["corechart"]});

google.setOnLoadCallback(drawChart);

....

.....

chart.draw(data, {chartArea:{left:20},width: 400, height:240, is3D: true, legend: 'right',title:'Portfolio %', pieSliceText: 'none', legendFontSize: 10, colourArray});

The new charts available in this "corechart" package are compatible with IE9, even in standard
mode of IE9. The older charts ( available in "areachart" and "piechart" are using VML in IE9) - it seems that - are not supported anymore.

Changing the package this way should fix your issue. It will now correctly show your Google Chart in IE9.

Reference:

Google Pie Charts

How to turn on the SSL Debugging in JBoss

2011-09-22T16:42:00.002+12:00

How to turn on the SSL Debugging in JBoss

You need to add this to your JAVA_OPTIONS in your run.bat. Or if you have a batch file that does environment before running the run.bat batch file then you can add this config setting to your jboss startup batch file:

REM to turn ON the SSL debugging in JBoss
set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.debug=ssl:handshake:verbose:keymanager:trustmanager -Djava.security.debug=access:stack

this will turn on the ssl debugging on ssl handshake process and will be verbose in telling which keymanager and trustmanager will be used.

if you want all debugging information on start up then you can use following config setting:

set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.debug=all -Djava.security.debug=access:stack

The above commands will give you more information to be able to diagnose the error.

How to explicitly specify keystore and truststore in JAVA_OPTIONS in JBoss

You can explicitly specify the keystore and truststore with -D option in JBoss. Please see the configuration settings below:

REM to explicitly set the keystore and truststore

set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.ssl.trustStore=C:/Java/jboss-4.2.2.GA/server/{your_server_instance}/conf/server.truststore -Djavax.net.ssl.trustStorePassword=[your_password] -Djavax.net.ssl.keyStore=C:/Java/jboss-4.2.2.GA/server/{your_server_instance}/conf/server.keystore -Djavax.net.ssl.keyStorePassword=[your_password]

2011-09-17T09:18:00.001+12:00

How to fix "incompatible debugger version" error in eclipse PHP?

Bug:

when you are using PHP perspective in Eclipse IDE, you will often see a error popup alert. The popup alert will keep coming up for every 30 seconds or so. This is a known bug in Eclipse PDT and you can find more information on this link: "Incompatible debugger version" when not debugging

Incompatible Debugger version error alert

Fix:

As this bug gets fix sometime sooner in future, you would want that annoying popup to go away. Well there is a way to stop that alert from popping up.

Change the debug ports in "Eclipse -> Preferences -> PHP -> Debug -> Installed Debuggers", with these values:

Zend Debugger (40000)

XDebug (29000)

This is how I fixed the annoying popup for Incompatible debugger Version

InstallCert.java

2011-09-09T12:13:00.000+12:00

package com.aw.ad.util;

/*

 * Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.

 *

 * Redistribution and use in source and binary forms, with or without

 * modification, are permitted provided that the following conditions

 * are met:

 *

 *   - Redistributions of source code must retain the above copyright

 *     notice, this list of conditions and the following disclaimer.

 *

 *   - Redistributions in binary form must reproduce the above copyright

 *     notice, this list of conditions and the following disclaimer in the

 *     documentation and/or other materials provided with the distribution.

 *

 *   - Neither the name of Sun Microsystems nor the names of its

 *     contributors may be used to endorse or promote products derived

 *     from this software without specific prior written permission.

 *

 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS

 * IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR

 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

 * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

 * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

 * NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 */

/**

 * http://blogs.sun.com/andreas/resource/InstallCert.java

 * Use:

 * java InstallCert hostname

 * Example:

 *% java InstallCert ecc.fedora.redhat.com

 */

import javax.net.ssl.*;

import java.io.*;

import java.security.KeyStore;

import java.security.MessageDigest;

import java.security.cert.CertificateException;

import java.security.cert.X509Certificate;

/**

 * Class used to add the server's certificate to the KeyStore

 * with your trusted certificates.

 */

public class InstallCert {

    public static void main(String[] args) throws Exception {

        String host;

        int port;

        char[] passphrase;

        if ((args.length == 1) || (args.length == 2)) {

            String[] c = args[0].split(":");

            host = c[0];

            port = (c.length == 1) ? 443 : Integer.parseInt(c[1]);

            String p = (args.length == 1) ? "changeit" : args[1];

            passphrase = p.toCharArray();

        } else {

            System.out.println("Usage: java InstallCert <host>[:port] [passphrase]");

            return;

        }

        File file = new File("jssecacerts");

        if (file.isFile() == false) {

            char SEP = File.separatorChar;

            File dir = new File(System.getProperty("java.home") + SEP

                    + "lib" + SEP + "security");

            file = new File(dir, "jssecacerts");

            if (file.isFile() == false) {

                file = new File(dir, "cacerts");

            }

        }

        System.out.println("Loading KeyStore " + file + "...");

        InputStream in = new FileInputStream(file);

        KeyStore ks = KeyStore.getInstance(KeyStore.getDefaultType());

        ks.load(in, passphrase);

        in.close();

        SSLContext context = SSLContext.getInstance("TLS");

        TrustManagerFactory tmf =

                TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());

        tmf.init(ks);

        X509TrustManager defaultTrustManager = (X509TrustManager) tmf.getTrustManagers()[0];

        SavingTrustManager tm = new SavingTrustManager(defaultTrustManager);

        context.init(null, new TrustManager[]{tm}, null);

        SSLSocketFactory factory = context.getSocketFactory();

        System.out.println("Opening connection to " + host + ":" + port + "...");

        SSLSocket socket = (SSLSocket) factory.createSocket(host, port);

        socket.setSoTimeout(10000);

        try {

            System.out.println("Starting SSL handshake...");

            socket.startHandshake();

            socket.close();

            System.out.println();

            System.out.println("No errors, certificate is already trusted");

        } catch (SSLException e) {

            System.out.println();

            e.printStackTrace(System.out);

        }

        X509Certificate[] chain = tm.chain;

        if (chain == null) {

            System.out.println("Could not obtain server certificate chain");

            return;

        }

        BufferedReader reader =

                new BufferedReader(new InputStreamReader(System.in));

        System.out.println();

        System.out.println("Server sent " + chain.length + " certificate(s):");

        System.out.println();

        MessageDigest sha1 = MessageDigest.getInstance("SHA1");

        MessageDigest md5 = MessageDigest.getInstance("MD5");

        for (int i = 0; i < chain.length; i++) {

            X509Certificate cert = chain[i];

            System.out.println

                    (" " + (i + 1) + " Subject " + cert.getSubjectDN());

            System.out.println("   Issuer  " + cert.getIssuerDN());

            sha1.update(cert.getEncoded());

            System.out.println("   sha1    " + toHexString(sha1.digest()));

            md5.update(cert.getEncoded());

            System.out.println("   md5     " + toHexString(md5.digest()));

            System.out.println();

        }

        System.out.println("Enter certificate to add to trusted keystore or 'q' to quit: [1]");

        String line = reader.readLine().trim();

        int k;

        try {

            k = (line.length() == 0) ? 0 : Integer.parseInt(line) - 1;

        } catch (NumberFormatException e) {

            System.out.println("KeyStore not changed");

            return;

        }

        X509Certificate cert = chain[k];

        String alias = host + "-" + (k + 1);

        ks.setCertificateEntry(alias, cert);

        OutputStream out = new FileOutputStream("jssecacerts");

        ks.store(out, passphrase);

        out.close();

        System.out.println();

        System.out.println(cert);

        System.out.println();

        System.out.println

                ("Added certificate to keystore 'jssecacerts' using alias '"

                        + alias + "'");

    }

    private static final char[] HEXDIGITS = "0123456789abcdef".toCharArray();

    private static String toHexString(byte[] bytes) {

        StringBuilder sb = new StringBuilder(bytes.length * 3);

        for (int b : bytes) {

            b &= 0xff;

            sb.append(HEXDIGITS[b >> 4]);

            sb.append(HEXDIGITS[b & 15]);

            sb.append(' ');

        }

        return sb.toString();

    }

    private static class SavingTrustManager implements X509TrustManager {

        private final X509TrustManager tm;

        private X509Certificate[] chain;

        SavingTrustManager(X509TrustManager tm) {

            this.tm = tm;

        }

        public X509Certificate[] getAcceptedIssuers() {

            throw new UnsupportedOperationException();

        }

        public void checkClientTrusted(X509Certificate[] chain, String authType)

                throws CertificateException {

            throw new UnsupportedOperationException();

        }

        public void checkServerTrusted(X509Certificate[] chain, String authType)

                throws CertificateException {

            this.chain = chain;

            tm.checkServerTrusted(chain, authType);

        }

    }

}

PKIX path building Faild for SSL in JBoss

2011-09-09T12:10:00.003+12:00

Enabling SSL on JBoss. Using CA signed Certificate. PKIX path building Faild.

Exception at TCP connection sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Background Information:

I am using JBoss 4.2.2.GA server with SSL enabled. ( {jboss_server_path}\deploy\jboss-web.deployer\server.xml )

<Connector port="28443" address="${jboss.bind.address}"

   maxThreads="250"
maxHttpHeaderSize="8192" 

  
emptySessionPath="true" protocol="HTTP/1.1" 

  
enableLookups="false" redirectPort="8443"
acceptCount="100"

  
connectionTimeout="20000"
disableUploadTimeout="true" 

  
strategy="ms" scheme="https" secure="true"
   

   clientAuth="false"

  
SSLEnabled="true"

   keystoreFile="C:/Java/jboss-4.2.2.GA/server/{your_server_folder}/conf/server.keystore"

  
keystorePass="your_password_here"         

   truststoreFile="C:/Java/jboss-4.2.2.GA/server/{your_server_folder}/conf/server.truststore"

   truststorePass="your_password_here"

sslProtocol="TLS" />

I used the java keytool to generate the private keystore (server.keystore) and public truststore (server.truststore).
I generated the CSR using java keytool and then supplied it to www.comodo.com to buy a SSL certificate (CA Signed Certificate)
On Comodo, I selected "Server Software" as "Tomcat". Because JBoss uses tomcat as the web container for SSL.
Received 5 files from Comodo (1 Domain crt, 3 intermediate certificates and 1 Root Certificate)
Imported them into my server.truststore successfully
Then I imported the CA certificates supplied by our host server that we are trying to connect to using our JBoss server.

Error Message:

When I started up my server, I got this error:

Exception at TCP connection sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I tried to find information on the Google. Did find a very good example as well which I will mention below. But this example was not directly relevant to my situation. SO, this is why I am writing this blog to help people who are stuck in same situation as mine. :)

Explanation Of why error happened and what it means?

What this error means is that the certificate received from host server (other server you are trying to connect to) during the SSL Handshake is not available or did not match to certificates in our Truststore (server.truststore).

This error happens when we are doing the SSL handshake.

Simple, as JSSE does not have ability to handle popup messages and cannot interact automatically to accept the certificate, it throws this error by default. So, the certificate we received for doing the ssl handshake does not exist in our truststore or do not match to any one in our truststore.

How to fix this error?

Fixing this error is simple. Simply import the Certificate that is sent by the host server while connecting to it. Import this certificate to your truststore (server.truststore) file. Then restart the JBoss server again. This time it should pass the SSL Handshake.

You had already imported the certificates supplied by your host server (into your truststore) and still it threw the "PKIX path building failed" error?

Reason 1:

This means the certificate supplied by your host server to be imported in your trust store is different from what [certificate] they actually have in their truststore. Obviously, their actual certificate was not imported by us into our truststore. Therefore, failing on SSL handshake.

Reason 2:

Another reason for the failure could be that we are using CA signed certificates for our server identity. But (other party's) host server is using self signed certificate.

Easiest way is that either both parties should have self-signed certificate for their ssl identification OR both parties should have CA signed certificates.

Important Tip:

Following communications can happen and setup is straight forward:

Client (With Self-signed certificate) <-----------> Host Server (with Self-signed certificate)

Client (With Self-signed certificate) <-----------> Host Server (with CA-signed certificate)

In this type of communication, you will use two files: server.keystore and server.truststore.

Special case:

Following communications CANNOT happen straightaway:

1) Client (With CA-signed certificate) <-----------> Host Server (with CA-signed certificate)

Tomcat has a glitch in their code. So for this type of communication to happen, you need to use only one keystore file and you don't need truststore file as a separate file. Import all the CA certificates in your server.keystore file. The order that you import is important as well.

To start with, your server.keystore will only have your private key. then import the other certificates in following order:

CA Root Certificate

CA Intermediate Certificate

Your Domain Certificate -- You should use same alias you had used for private certificate. This way a correct reply is stored in the certificate

Host Server's CA Root Certificate

Host Server's Intermediate Certificate

Host Server's Domain Certificate

2) Client (With CA-signed certificate) <-----------> Host Server (with Self-signed certificate)

same as explained above. Only difference is that you will import only one self-signed certificate of Host server, into your server.keystore file.

Reason 3:

Check your Host Server's IP address again. If you are using INET then you may have your internal IP different than the Public IP. Same applies to the hosting server that you are trying to connect to. Make sure that the public certificate in your truststore belongs to the right server and you are connecting to the same server for which you have certificate in your truststore.

Reason 4:

May be you still have old ssl certificates of the host server in your system-wide keystore such as cacerts and/or jssecacerts. Usual location of these files : C:\Java\jdk6\jre-lib\security folder
So, please make sure that these cacerts and jssecacerts do NOT contain your host server's certificate.
The host server's certificate should only be imported in your server.keystore or server.truststore files that you are using in your JBoss.

How to turn on the SSL debugging in JBoss?
You need to add this to your JAVA_OPTIONS in your JBoss run.bat. Or if you have a batch file that does environment before running the run.bat batch file then you can add this command to your this jboss startup batch file:

REM to turn ON the SSL debugging in JBoss
set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.debug=ssl:handshake:verbose:keymanager:trustmanager -Djava.security.debug=access:stack

this will turn on the ssl debugging on ssl handshake process and will be verbose in which keymanager and trustmanager will be used.

if you want all debugging information on start up then you can use following command:
set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.debug=all -Djava.security.debug=access:stack

The above commands will give you more information to fix the error.

The following is only for awareness.. if you use Jboss then you do NOT need to do any of the following:

Reference:
Very Useful blog by Leeland for this error: http://dreamingthings.blogspot.com/2006/12/no-more-unable-to-find-valid.html

In this blog, they are talking same error. But they are not using the JBoss server. They are using JSSE directly to connect to their host server. Therefore, they talk about importing the certificates in the JAVA_HOME\lib\security\cacerts using the InstallCert.java written by andreas.

However, their link to download the InstallCert.java is broken. You can easily find this java file somewhere else or download it from this blog of mine.

Steps to run the InstallCert.java

Download the InstallCert.java from here
Open a "command prompt" or "command console"
In your command prompt, go to your "JAVA_HOME\lib\security\" folder
Using Windows explorer, create this package in this folder mentioned in step 2: \com\aw\ad\util
In your command prompt, go to this newly created package: "JAVA_HOME\lib\security\com\aw\ad\util"
copy the downloaded file InstallCert.java here
In your command prompt, compile this java file: javac InstallCert.java
In your command prompt, now go up to the level: "JAVA_HOME\lib\security\"
run this command to execute the InstallCert program: java com.aw.ad.util.InstallCert {your_host_name}:{port}
you have to mention the full path [com.aw.ad.util] for running the InstallCert
Then it will ask you if you wish to add the certificate to the cacaerts? type 1 at command prompt and press enter.
It will add the certificate to cacerts now, and will tell you how many certificates it imported.

Please correct me if I made any mistake in this blog. I hope this helps someone who is stuck with bloody painful ssl implementation in JBoss. :)

SONAR : Database schema must be updated [version/required=152/170]

2011-01-20T16:39:00.000+13:00

My sonar build keeps on failing with this error:

[INFO] PicoLifecycleException: method 'public void org.sonar.jpa.session.AbstractDatabaseConnector.start()', instance 'org.sonar.jpa.session.DriverDatabaseConnector@3f26f816, java.lang.RuntimeException: wrapper

Database schema must be updated [version/required=152/170]. Please browse to your sonar homepage.

Firstly, I thought my jtds version is wrong. So, I downloaded the latest one ( jtds-1.2.5.jar ) and copied that to my Sonar installation folder at this location: C:\sonar\extensions\jdbc-driver\mssql
Then Stopped and started the Sonar..But this did not fix my issue.

Then I could not find anything on the google... Then it came to me that this message may be misleading.. and something else might be wrong.. so I checked my maven projects' POM file.

Then only it occurred to me that I did not specify the version for my sonar-maven-plugin in the POM file. SO, it must be always going for the latest version by default.. which is 2.5 and this 2.5 version of sonar-maven plugin was conflicting (i.e. not compatible) with my installed sonar server (which is at 2.4.1 version). Then, I specified the version number for the sonar-maven-plugin to be 2.4.1 and this fixed my issue.

Error Message that I was getting:

[INFO] ------------------------------------------------------------------------
[INFO] Building Suite Modules Build Project
[INFO]    task-segment: [sonar:sonar] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [sonar:sonar {execution: default-cli}]
[INFO] Database dialect class org.sonar.jpa.dialect.MsSql
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] PicoLifecycleException: method 'public void org.sonar.jpa.session.AbstractDatabaseConnector.start()', instance 'org.sonar.jpa.session.DriverDatabaseConnector@3f26f816, java.lang.RuntimeException: wrapper
Database schema must be updated [version/required=152/170]. Please browse to your sonar homepage.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.picocontainer.PicoLifecycleException: PicoLifecycleException: method 'public void org.sonar.jpa.session.AbstractDatabaseConnector.start()', instance 'org.sonar.jpa.session.DriverDatabaseConnector@3f26f816, java.lang.RuntimeException: wrapper
    at org.picocontainer.monitors.NullComponentMonitor.lifecycleInvocationFailed(NullComponentMonitor.java:77)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.monitorAndThrowReflectionLifecycleException(ReflectionLifecycleStrategy.java:132)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:115)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.start(ReflectionLifecycleStrategy.java:89)
    at org.picocontainer.adapters.InstanceAdapter.start(InstanceAdapter.java:108)
    at org.picocontainer.behaviors.AbstractBehavior.start(AbstractBehavior.java:169)
    at org.picocontainer.behaviors.Stored$RealComponentLifecycle.start(Stored.java:132)
    at org.picocontainer.behaviors.Stored.start(Stored.java:110)
    at org.picocontainer.DefaultPicoContainer.potentiallyStartAdapter(DefaultPicoContainer.java:996)
    at org.picocontainer.DefaultPicoContainer.startAdapters(DefaultPicoContainer.java:989)
    at org.picocontainer.DefaultPicoContainer.start(DefaultPicoContainer.java:746)
    at org.sonar.batch.Batch.execute(Batch.java:65)
    at org.sonar.maven.SonarMojo.executeBatch(SonarMojo.java:142)
    at org.sonar.maven.SonarMojo.execute(SonarMojo.java:133)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.RuntimeException: wrapper
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.monitorAndThrowReflectionLifecycleException(ReflectionLifecycleStrategy.java:130)
    ... 31 more
Caused by: org.sonar.jpa.session.DatabaseException: Database schema must be updated [version/required=152/170]. Please browse to your sonar homepage.
    at org.sonar.jpa.session.AbstractDatabaseConnector.start(AbstractDatabaseConnector.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:110)
    ... 30 more

Solution to fix this issue

1) Check the version of your installed sonar server. e.g mine is 2.4.1
2) specify this same version number for your sonar-maven-plugin in your projects POM file as shown below:

<build>

      ....................

        <plugins>

            ......................

            .......................            

            <plugin>

                <groupId>org.codehaus.sonar</groupId>

                <artifactId>sonar-maven-plugin</artifactId>

                <version>2.4.1</version> <!-- please do not remove this version.. we need this one only.. -->

            </plugin>

          .............

        </plugins>

        .................... 

</build>

It is a standard behavior of Maven POMs that if we do not specify the version number for the given artifact then maven will try to find the latest version for this artifact. So, in our case, the latest version of sonar-maven-plugin was not compatible with installed version of sonar server. So, I had to specify the version number for the sonar-maven-plugin explicitly.

I hope this helps you. If something is wrong here... and you think of a better solution then please let me know on this blog. Cheers!

Running Bamboo Service as a local user

2011-01-20T09:58:00.007+13:00

I was having problems with my bamboo builds failing to read/write the test results on the server. I was getting this error:

org.apache.maven.surefire.booter.SurefireBooterForkException:  Error  creating properties files for forking; nested exception is   java.io.IOException: The system cannot find the path specified

When I checked, Bamboo service was using a system login to access the machine instead of the local user that was setup especially for the Bamboo build plans. So, I set up the bamboo service to run as a local user and it fixed the problem. In this blog, I will show the error that I was getting and instructions on how to setup the bamboo service to run as local.

Problem:

When we install the Bamboo on the windows server, and install the bamboo service, it by default uses the system user login to run the service. Therefore we get this error:

------------------------------------------------------------------------------------------------------------------------------

22-Jul-2010 10:55:35 [INFO] Surefire report directory:  C:\Users\automake\bamboo-home\xml-data\build-dir\SUITE-SUITE\monowai\trunk\monowai-jar\target\surefire-reports 

22-Jul-2010 10:55:35 [INFO] ------------------------------------------------------------------------

22-Jul-2010 10:55:35 [ERROR] BUILD ERROR

22-Jul-2010 10:55:35 [INFO] ------------------------------------------------------------------------

22-Jul-2010 10:55:35 [INFO] Error creating properties files for forking;  nested exception is java.io.IOException: The system cannot find the  path specified

22-Jul-2010 10:55:35

22-Jul-2010 10:55:35 [INFO] ------------------------------------------------------------------------

22-Jul-2010 10:55:35 [INFO] Trace

22-Jul-2010 10:55:35  org.apache.maven.lifecycle.LifecycleExecutionException: Error creating  properties files for forking; nested exception is java.io.IOException:  The system cannot find the path specified

22-Jul-2010 10:55:35 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)

22-Jul-2010 10:55:35 at  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)

22-Jul-2010 10:55:35 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)

22-Jul-2010 10:55:35 at  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)

22-Jul-2010 10:55:35 at  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)

22-Jul-2010 10:55:35 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)

22-Jul-2010 10:55:35 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)

22-Jul-2010 10:55:35 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)

22-Jul-2010 10:55:35 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)

22-Jul-2010 10:55:35 at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)

22-Jul-2010 10:55:35 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

22-Jul-2010 10:55:35 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

22-Jul-2010 10:55:35 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

22-Jul-2010 10:55:35 at java.lang.reflect.Method.invoke(Unknown Source)

22-Jul-2010 10:55:35 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

22-Jul-2010 10:55:35 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

22-Jul-2010 10:55:35 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

22-Jul-2010 10:55:35 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

22-Jul-2010 10:55:35 Caused by:  org.apache.maven.plugin.MojoExecutionException: Error creating  properties files for forking; nested exception is java.io.IOException:  The system cannot find the path specified

22-Jul-2010 10:55:35 at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:541)

22-Jul-2010 10:55:35 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)

22-Jul-2010 10:55:35 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)

22-Jul-2010 10:55:35 ... 17 more

22-Jul-2010 10:55:35 Caused by:  org.apache.maven.surefire.booter.SurefireBooterForkException: Error  creating properties files for forking; nested exception is  java.io.IOException: The system cannot find the path specified

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:629)

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:479)

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:379)

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:245)

22-Jul-2010 10:55:35 at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:537)

22-Jul-2010 10:55:35 ... 19 more

22-Jul-2010 10:55:35 Caused by: java.io.IOException: The system cannot find the path specified

22-Jul-2010 10:55:35 at java.io.WinNTFileSystem.createFileExclusively(Native Method)

22-Jul-2010 10:55:35 at java.io.File.checkAndCreate(Unknown Source)

22-Jul-2010 10:55:35 at java.io.File.createTempFile(Unknown Source)

22-Jul-2010 10:55:35 at java.io.File.createTempFile(Unknown Source)

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.writePropertiesFile(SurefireBooter.java:523)

22-Jul-2010 10:55:35 at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:621)

22-Jul-2010 10:55:35 ... 23 more

22-Jul-2010 10:55:35 [INFO] ------------------------------------------------------------------------

What this means that the user who owns the bamboo process, do not have write permissions to create the "surefire-reports" folder under target directory.
I checked the Bamboo System Information and found out that we are using "SYSTEM" as a user to run the bamboo. This is default user to run windows services. So, changed this user to local user. Then ran the bamboo build and this has fixed the problem.

Solution:

You should run the bamboo service as local user. To change the user from SYSTEM to local user, I went to

Windows Service Manager >> Configuration >> Services >> Bamboo Server.
Right click on the service and select "properties" option. Set the user here..

You can also follow the instructions given on the atlassian support website as shown below:
http://confluence.atlassian.com/display/BAMBOO/Running+Bamboo+service+on+Windows+as+the+local+user

SVN Pre-commit hook failed - jira-client.py throws error

2010-12-22T11:03:00.005+13:00

SVN Pre-commit hook failed - jira-client.py throws error

We recently upgraded our Atlassian Products (crowd, Jira, fisheye, crucible), particulary Jira from 4.0.1 to 4.2.1

Since this upgrade we could not do SVN commits. It keeps on failing and gives this message:

Problem:

svn: Commit failed (details follow):
svn: 'pre-commit' hook failed with error output:
Committer: pdhawale
Commit message: "SUITE-XXXX - Audit History changes"
Commit rejected: Unable to connect to the JIRA server at "http://xxxx.xxxxxx.co.nz".

Then I did some digging in the my SVN-server folder and found out that there is a python script for JIRA Commit Acceptance Plugin. This script gets run when we do SVN Commits. The error was thrown from this python script.

JIRA Commit Acceptance Plugin:
This plug-in lets you define certain basic rules that will determine whether a commit to your version control system will be accepted based on the issues in JIRA. For example, you can define a rule that no commit will be accepted unless it contains a valid issue key. Or you can set a rule that no commit would be accepted if the issue was not in an "open" state.
For more information go to JIRA Commit Acceptance Plugin

The python script is called jira-client.py and it is located in this location: {svn-server}\repo\hooks
In case you are using perl, The perl script is called jira-client.pl and it is located in this location: {svn-server}\repo\hooks

Solution:

JIRA Commit Acceptance plugin is not part of the Standard Jira Package. So, whenever you install or upgrade your Jira Application, you will need to explicitly (or you can say 'manually') install this plugin every time.
For more information on installation steps go to JIRA Commit Acceptance Plugin

So, the jira-client.py is one part of the JIRA Commit Acceptance plugin, The plugin adds an extra remote method that the jira-client.py script is trying to call, but because the plugin isn't installed yet, there's no remote method for the script to connect to and thus it fails and throws the error mentioned above.

You should be able to install the plugin (its free) in your JIRA server and everything should work again. You may want to double-check within JIRA that the plugin is configured properly though, as I'm not sure if the settings are kept as part of an XML backup or not.

Also, you will need to configure JIRA access and svnlookup path in the new jira-client.py for your SVN-server, as follows:

# configure JIRA access
# ("projectKey" can contain multiple comma-separated JIRA project keys like "projectKey = 'TST,ARP'".
# If you specify multiple keys, the commit will be accepted if at least one project listed accepts it.
# Or you can specify "projectKey = '*'" to force using the global commit acceptance settings if you don't
# want to specify any exact project key.)
jiraBaseURL = 'http://xxxx.xxxx.co.nz'
jiraLogin = 'xxxx'
jiraPassword = 'xxxx01'
projectKey = '*'

# configure svn lookup path
svnlookPath = 'D:\\svn-server\\bin\\svnlook.exe'

Also, please edit your new pre-commit.bat file to look at the python installation location as follows:

@c:\\Progra~2\Python25\python.exe D:\\svn-server\\repo\\hooks\\jira-client.py %1 %2

Quick Work Arround Available:

If you do not have enough time, as your Jira is already in production and people want to commit their work urgently. Then disable the SVN check on Code Check-in, as follows:
Comment out the code in your existing jira-client.py

## invoke JIRA web service
#xmlrpcUrl = jiraBaseURL + '/rpc/xmlrpc'
#try:
#    s = xmlrpclib.ServerProxy(xmlrpcUrl)
#    acceptance, comment = s.commitacc.acceptCommit(jiraLogin, jiraPassword, committer, projectKey, commitMessage).split('|');
#except:
#    acceptance, comment = ['false', 'Unable to connect to the JIRA server at "' + jiraBaseURL + '".']

#if acceptance == 'true':
#    print >> sys.stderr, 'Commit accepted.'
#       sys.exit(0)
#else:
#    print >> sys.stderr, 'Commit rejected: ' + comment
#    sys.exit(1)

And put this line AFTER the commented lines shown above:

sys.exit(0)

This should then disable the SVN check on Code Check-in and you would be able to commit the code changes. The only problem with this quick fix is that, user is able check in the code changes without any Jira Issue key or comment.

I could not find a good solution that would tell all this to me and I had to spend one whole day to figure out what is wrong.. I hope this blog helps you and save some time for you.

java.sql.SQLException: Prepared or callable statement has more than 2000 parameter markers.

2010-12-03T12:56:00.002+13:00

This one is pretty simple...

We use MSSQL 2005. We had a sql query as given below,

----------------------------------------------------------------------------------------------

select f from FooData f 

         where f.id = :id and f.date <= :today 

         and f.accountID in (:list)

----------------------------------------------------------------------------------------------

For one particular scenario, list was of size 2069

This crashed the sql query in run time with this error

-----------------------------------------------------------------------------------------------------------
"java.sql.SQLException: Prepared or callable statement has more than 2000 parameter markers."
-----------------------------------------------------------------------------------------------------------

If you guys don't know what this error means... and trying to find an answer on the google and various blogs...then please read on..

Interpretation

What this error means is that I cannot have the list of input parameters to be more than 2000. Some how you need to either split the large list into smaller ones.. or optimize your sql query. Both of these solutions are given below.

Solution 1

I had to fix this issue by partitioning the list in to small lists of size 1990 and then run the query for each of those smaller lists. Then combine the results into one list again. Now you can partition the list the way you want.. I used this implementation like below.. this uses a private class to do the partition and returns a List<List<T>>. the you can iterate through this list to run your query.

public static <T> List<List<T>> partition(List<T> list, int size) {

        if (list == null)
            throw new NullPointerException(
                    "'list' must not be null");
        if (!(size > 0))
            throw new IllegalArgumentException(
                    "'size' must be greater than 0");

        return new Partition<T>(list, size);
    }

    private static class Partition<T> extends AbstractList<List<T>> {

        final List<T> list;
        final int size;

        Partition(List<T> list, int size) {
            this.list = list;
            this.size = size;
        }

        @Override
        public List<T> get(int index) {
            int listSize = size();
            if (listSize < 0)
                throw new IllegalArgumentException("negative size: " + listSize);
            if (index < 0)
                throw new IndexOutOfBoundsException(
                        "index " + index + " must not be negative");
            if (index >= listSize)
                throw new IndexOutOfBoundsException(
                        "index " + index + " must be less than size " + listSize);
            int start = index * size;
            int end = Math.min(start + size, list.size());
            return list.subList(start, end);
        }

        @Override
        public int size() {
            return (list.size() + size - 1) / size;
        }

        @Override
        public boolean isEmpty() {
            return list.isEmpty();
        }
    }

But this solution is slow and could take more time to load the screen results.. Therefore, you can also consider the following solution

Solution 2

The second solution is as follows. My list is actually another sql query to get account IDs. So, What I did is to use "inner joins" in my sql query to combine these two queries. This solution is much faster and cleaner. Its done as follows:

------------------------------------------------------------------------------

select f from FooData f 

         inner join FooAccount fa on f.accountID = fa.accountID 

         where f.id = :id and f.date <= :today 

-------------------------------------------------------------------------------

I hope this helps you and saves your time.

Thanks for reading this post!

Sonar Cobertura OutOfMemory Java Heap Size

2010-11-30T15:50:00.000+13:00

When you configure and install the Sonar for to analyze and report metrics on source code, it sets the default code coverage tool as Cobertura. The "Maximum memory to pass to JVM of Cobertura processes" is defaulted to 64m. This max memory size is often too small for running sonar on big projects which generate large metrics.

Usually, it fails in the Collection phase of Cobertura with the "OutOfMemory Java Heap size" exception.

To fix this you will need increase the maxmem for the cobertura.

If you are using the Sonar web application for doing the settings then follow these steps:
1) Go to your Sonar Web applications' home page. it will be something like http://{your sonar host url}:9000
2) Go to Configuration >> Settings >> Cobertura.
3) put 512m in the Maxmem field
4) Save it.
5) Now you need to stop and start your Sonar server for the changes to take effect.

6) Thats it! your OutOfMemory issue should be fixed now.

If you are doing the sonar settings in the maven pom files of your project then add following to your main/parent pom file

<project>
...<build>
...</build>
<properties>
    <cobertura.maxmem>512m</cobertura.maxmem>
</properties>
</project>

If above does not work for you then try this:

<project>
   ...
<build>
   ...
   <plugins>
   ...
   <plugin>
   <groupId>org.codehaus.mojo</groupId>
   <artifactId>cobertura-maven-plugin</artifactId>
   <configuration>
   <maxmem>512m</maxmem>

   </configuration>
   </plugin>
   </plugins>
   </build>
</project>

I hope this helps.