CreateProcess error=87, The parameter is incorrect.

On computers running Microsoft Windows XP or later, the maximum length of the string that you can use at the command prompt is 8191 characters. On computers running Microsoft Windows 2000 or Windows NT 4.0, the maximum length of the string that you can use at the command prompt is 2047 characters.

This limitation applies to the command line, individual environment variables (such as the PATH variable) that are inherited by other processes, and all environment variable expansions. If you use Command Prompt to run batch files, this limitation also applies to batch file processing. read more

Solution:

Rename the folder(s), give short names. e.g. C:\maven\repository to c:\m2\rep.

EXCEPTION: real time example

try {
     Agile: Scrum & XP
     Teamwork and integrity
     Continous learning
     Self Motivation and Commitment
     Intensity to WIN
} catch {
     Learn from mistakes and failures.
} finally {
     Deliver results.
     Career growth.
     Work-Life balance.
}

ORACLE: delete duplicate rows

Oracle SQL to remove duplicate rows from a table:

DELETE FROM
   TABLE_NAME A
WHERE
  A.COLUMN_NAME >
   ANY (
     SELECT
        B.COLUMN_NAME
     FROM
        TABLE_NAME B
     WHERE
        A.COLUMN_NAME = B.COLUMN_NAME

   );

!!! PROGRAMMERS-TO-PROGRAMMERS !!!

List of blogs and forums to find solutions to common Java/JEE technical issues plus nice  tutorials.

http://www.mkyong.com/ 

Quick introduction to many open source frameworks with simple examples

http://www.vogella.com/tutorials.html 

Quick introduction to many open source frameworks with simple examples

Proxy Based AOP Framework 

Implement Your Own Proxy-Based AOP Framework using JDK Dynamic Proxy or CGLib proxy

Code Smells 

Quick intro on code smells in programming.

Spring Web Sessions 

Quick intro on code smells in programming.

ORA-12519 Listener refused the connection

ORA-12519 error while connecting to the database, I asked other developers to disconnect from the db and then I tried to connect to the database, this time no error!!! So I guess this is due to insufficient sessions. 

Execute the following commands to increase the session, process and transactions.

connect sys as sysdba;




alter system set processes = 150 scope = spfile;

alter system set sessions = 300 scope = spfile;

alter system set transactions = 330 scope = spfile;



shutdown immediate;

startup;

select name, value

from v$parameter

where name in ('processes', 'sessions', 'transactions');

Above commands copied from this link More info