Showing posts with label WAS 8. Show all posts
Showing posts with label WAS 8. Show all posts

3/30/18

{xor} password decode

I came across this while googling to decode {xor} password

WAS_HOME="path to AppServer"
MYCLASSPATH=$WAS_HOME/plugins/com.ibm.ws.runtime.jar:$WAS_HOME/lib/bootstrap.jar:$WAS_HOME/plugins/com.ibm.ws.emf.jar:$WAS_HOME/lib/ffdc.jar:$WAS_HOME/plugins/org.eclipse.emf.ecore.jar:$WAS_HOME/plugins/org.eclipse.emf.common.jar
$WAS_HOME/java/bin/java -cp $MYCLASSPATH com.ibm.ws.security.util.PasswordDecoder {xor}


7/11/13

java.io.IOException: Async IO operation failed (1), reason: RC: 10054

Here is a good link to solve the issue
java.io.IOException: Async IO operation failed (1), reason: RC: 10054

http://h30499.www3.hp.com/t5/Networking/10054-WSAECONNRESET-Connection-reset-by-peer/td-p/3436931#.Ud3JfaxGagx

6/12/13

HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected.

Problem

HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected.

Symptom

HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected. The sending process has a name of myplex1\nodea\nodeagent and an IP address of /123.456.115.115. Global security in the local process is Disabled. Global security in the sending process is Disabled. The received token starts with ab1c234:56abc7848e4:-8000. The exception is <null>

So, when I tried to sync node, I got the above error. Found this IBM Technote
http://www-01.ibm.com/support/docview.wss?uid=swg21596835
Per this technote, the solution is -

Resolving the problem

Resolve LTPA token mismatch or remove DCS_SECURE setting.



The DCS_SECURE setting can be removed by changing the Transport chain for the coregroup.

1. In the administrative console, click Servers > Core groups > Core group settings and select the respective core group

2. Under Transport type > Channel Framework
change the transport chain from DCS_SECURE to DCS
When checked in my config, it transport Type > Channel Framework > Transport chain was set to DCS.

I manually did a syncNode on the server process, got it fixed. Here is the procedure -
1. Stop Server
2. Stop Node
3. From the Node, issue syncNode like this
D:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>syncNode <dmgrnode> -conntype
 SOAP -username <adminuid> -password <adminpassword>

This command syncs the node with the DMGR.
ADMU0116I: Tool information is being logged in file
           D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node DMGRNode01 with Deployment
           Manager dmgr: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node DMGRNode01 has been synchronized
           with Deployment Manager dmgr: 8879
Once this command executes,
4. start the node agent
5. start server



--
Thanks and Regards

Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar