User should be able to login to other server without password using command  “ssh -l username remotehost”.

For this I used SSH public key based authentication as below:-

For this to work you need a file named id_dsa.pub in your ~/.ssh Directory. If it’s not there, simply create it with below command:

ssh-keygen -t dsa

above command will create below directory with public and private keys:

.ssh/id_dsa
.ssh/id_dsa.pub

now copy id_dsa.pub file to remote server .ssh/ directory as “authorized_keys2” with whom you would like to do an automated login.

 After that try below command from source server, no need for password

ssh -l username remotehost

 For more details can view link

java.io.NotSerializableException: com.xxxx.xxx.xxx.thunderhead.Project
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
    at java.util.ArrayList.writeObject(ArrayList.java:570)

Later I realized that I forget to implement Serializable interface in my bean. That fixed issue.

java.security.NoSuchAlgorithmException: Cannot find any provider supporting RSA/NONE/OAEPPADDING
at javax.crypto.Cipher.getInstance(DashoA12275)
at org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:703)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:145)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:114)

This appears to BouncyCastle is missing from class path.  Or Bouncycastle jar may still in the classpath – but it’s not picked as a crypto provider.

Try below solution:

Download the Bouncycastle jar corresponding to your JDK from here and copy it to [JAVA_HOME]\jre\lib\ext\

Set following in [JAVA_HOME]\jre\lib\security\java.security under;

#
# List of providers and their preference orders (see above):
#
security.provider.X=org.bouncycastle.jce.provider.BouncyCastleProviderOR

In code add Bouncycastle as a provider.

import java.security.Security;  
import org.bouncycastle.jce.provider.BouncyCastleProvider;  
 
Security.addProvider(new BouncyCastleProvider());

Caused by: java.security.InvalidKeyException: Illegal key size or default parameters
    at javax.crypto.Cipher.a(DashoA13*..) ~[na:1.6]
    at javax.crypto.Cipher.a(DashoA13*..) ~[na:1.6]
    at javax.crypto.Cipher.a(DashoA13*..) ~[na:1.6]
    at javax.crypto.Cipher.init(DashoA13*..) ~[na:1.6]
    at javax.crypto.Cipher.init(DashoA13*..) ~[na:1.6]


There are key size restrictions with the default crypto files local_policy.jar and US_export_policy.jar comes with JDK – which limits it to 128. If your security policy using a key size larger than this – then the above exception is thrown.

For example – if your security policy specifies the algorithmic suite as Basic256 – then the key size to be used is 256.

For the solution of above issue, you need to patch your JDK with Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files.

For JDK1.5 visit, download the crypto files and copy the two jar files from the extracted jce directory (local_policy.jar and US_export_policy.jar) to $JAVA_HOME/jre/lib/security.

For JDK1.6 visit

If your IDE using it’s own specific JDK then patch that as well with these files to resolve the issue.

org.apache.axis2.AxisFault: Error in signature with X509Token
    at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:70)
    at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
    at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254)
    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:419)
    at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
    at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
    at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 Caused by: org.apache.rampart.RampartException: Error in signature with X509Token
    at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:746)
    at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:419)
    at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:95)
    at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
    at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
    … 102 more

Caused by: org.apache.ws.security.WSSecurityException: Signature creation failed; nested exception is:
    java.security.UnrecoverableKeyException: Cannot recover key
    at org.apache.ws.security.message.WSSecSignature.computeSignature(WSSecSignature.java:721)
    at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:737)
    … 106 more
Caused by: java.security.UnrecoverableKeyException: Cannot recover key
    at sun.security.provider.KeyProtector.recover(KeyProtector.java:311)
    at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:121)
    at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:38)
    at java.security.KeyStore.getKey(KeyStore.java:763)
    at org.apache.ws.security.components.crypto.CryptoBase.getPrivateKey(CryptoBase.java:216)
    at org.apache.ws.security.message.WSSecSignature.computeSignature(WSSecSignature.java:713)
    … 107 more

Above issue is caused by CallbackHandler, because Incorrect password is provided for the private key. Correct the password you are good to go.

Later debug I found that I duplicated the Controller definition stuff inside XXX-Servlet.xml as below.

<context:component-scan base-package="org.me.spring.web" />

and

<bean  class="org.me.spring.web.SampleController" >

The first line will auto-discover and register a SampleController for you. By explicitly declaring another one, you get a duplicate, and the url-mapping will clash.

You need to either remove the <context:component-scan>, or remove the explicit bean definitions for the controller and the DAO. If you do the latter, then you’ll need to use autowiring to inject their dependencies.

Below command will find all the logs with given name pattern inside the directory including sub directories and then WC will count it’s lines and display on screen in total.

wc -l `find . -name usage*.log`

Sample output of command

     4 ./2011-08-08/usage.log
     5 ./2011-08-09/usage.log
     5 ./2011-08-10/usage.log
     4 ./2011-08-11/usage.log
     2 ./2011-08-12/usage.log
     4 ./2011-08-13/usage.log
   24 total

Below command will not count the blank lines.

grep -cv ‘^\s*$’ `find . -name “usag*.log”`

Sample Output, see below blank lines are not counted.

./2011-08-08/usage.log:3
./2011-08-09/usage.log:4
./2011-08-10/usage.log:4
./2011-08-11/usage.log:3
./2011-08-12/usage.log:1
./2011-08-13/usage.log:3

I was searching for some utility on Google but not get any. Later I thought about DOS Batch command to do the same but a simple copy command did it for me.

Copy /a *.log USAGE-Consildated.log

Create an enum :

 public enum Months{ JAN, FEB, MAR, APRIL;}

Given this enum, the following switch statement could be used:

switch (Months.valueOf(str))
{
case JAN:
case FEB:
// processing
break;
default:
// processing ...
}

Enum.valueOf() matches the given String to the actual enum name using the same basic hashcode() matching technique that earlier proposals have suggested; but with this , all of that machinery is generated by the compiler and Enum implementation. The set of possible String values is also maintained in a more structured way when held in an enum.

Of course, the above suffers from the serious drawback that Enum.valueof() can throw an unchecked IllegalArgumentException or NullPointerException. The only real way to get around this issue is to create a new static method that absorbs these Exceptions and instead returns some default value:

public enum Months {
 JAN, FEB, MAR, APR, JUN, JUL, AUG, SEP, OCT, NOV,DEC,NOVALUE;
public static Months toDay(String str)
{
   try { return valueOf(str); } catch (Exception ex) { return NOVALUE; }
}
 }

Then the switch can be written to include a default clause that handles unexpected String values:

switch (Months.toDay(str)) {
 case JAN:
case FEB:
case MAR:
// etc ...
default:
// any non-Day value
}

addEventListener(“load”, function(event) {
      _init();
);

with

addEventListener(“load”, function(event) {
      _init();
},false);