This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Application Server Toolkit(6.1.1) - Unable to create more than one servers..

 
Santhosh Kg
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I am having some weird problem with my AST(Application Server Toolkit v 6.1.1) since yesterday.

The problem is I am not able to create a server if I have more than one ear projects in the workspace.
On the contrarily if I have created the server before checking out the EAR(from svn), after checking out the EAR,the add/remove projects is not working..
I tried reinstalling AST and the App server but no luck.

We have WAS license and i am using the same for the last 3 years.
Is this because of any certificate issue..?.
I get the below message when i start my server,

[5/5/11 13:24:44:088 IST] 0000000a WSNotifier I CWPKI0037I: Expiration monitor reports the following information:
**** Subject: Expiration Monitor ****

*** CERTIFICATES WITHIN THE 90 DAY PRE-NOTIFICATION THRESHOLD (MAY BE REPLACED WITHIN 90 DAYS) ***
The expiration monitor has recently run and discovered that the certificates listed below will be replaced within the next 90 days based upon the configured policy to automatically replace expiring self-signed certificates 60 days prior to expiration. This notification is warning you that problems may arise when this automatic replace occurs.

In some cases, automatic updates to the self-signed certificates can cause outages for WebServer plug-ins operating on unmanaged nodes. In such a situation, the plugin will be unable to contact the application servers over HTTPS because it will be using signers for certificates that have been replaced by the automatic replacement process.
To prevent what may be and serious outage you should act before the scheduled replacement date and replace the expiring certificates and update the plugin kdb to use the new signers.

Self-signed personal certificate "default" in the "NodeDefaultKeyStore" key store is due to be replaced on May 29, 2011.
Signer certificate "default" in the "NodeDefaultTrustStore" key store is due to expire on July 28, 2011.


*** CERTIFICATES THAT ARE BEYOND THE EXPIRATION THRESHOLD ***

Checking for expired certificate and certificates about to expire


WAS gurus,please help.

rgds,
Santhosh.

 
Santhosh Kg
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I had installed the latest fix pack for AST and finally the issue is resolved..
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic