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

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

java core dump

Java Core Dump

Download the file windows_hang.py and copy the file to your <PROFILE_ROOT>\bin directory. If instead copied to <WAS_HOME>\bin, the default server, which may be the deployment manger (dmgr), will be accessed when wsadmin.bat is launched.


NOTE: This script only works for WebSphere Application Server 6.1 and higher.


If you are looking for the older windows_hang.bat that works with older releases of WebSphere Application Server, see the FAQ section.


To launch the script to produce 3 javacores spaced 2 minutes apart, run this command:

wsadmin -lang jython -f windows_hang.py -j -s SERVER_NAME

Replacing SERVER_NAME with your server's name.

If you have to run this number of times, on windows, you can write a batch file and run the batch file as Administrator.

<WAS_HOME>\profiles\<PROFILE_NAME>\bin\wsadmin -lang jython -username <username> -password <password> -f \<path_to_windows_hang.py>\windows_hang.py -j -s SERVER_NAME

ex.,
\"Program Files"\ibm\WebSphere\AppServer\profiles\AppSrv01\bin\wsadmin -lang jython -username blahblah -password blahblah -f \users\bramaraju\desktop\windows_hang.py -j -s server01

http://www-01.ibm.com/support/docview.wss?uid=swg21111364

PM20642: FAILED APPLICATION DEPLOYMENT DOES NOT LEAVE THE WORKSPACE CLEANED PROPERLY

Error description

• Business-level application (BLA) code plugs into the  application management deployment framework to create a BLA  and composition unit (CU) for the new application. After it  does that, more tasks added by the product extension run and  fail, and the BLA and CU are left hanging around. The sceanrio  is a failed deployment and the session is then saved. If the  session is discarded or if the deployment succeeds, things  work correctly. So, the problem is that a failed deployment is  not leaving the work space clean. No warning is issued to  notify the user.  

Local fix

Remove any directories or files created, clean work space.  

http://www-01.ibm.com/support/docview.wss?uid=swg1PM20642
CUS folder path
<WAS_HOME>/profiles/<dmgr>\Dmgr01\config\cells\<CellName>\cus
BLAS folder path
<WAS_HOME>/profiles/<dmgr>\Dmgr01\config\cells\<CellName>\blas

--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

WASServiceCmd utility

I faced lot of issues with WebSphere services on Windows 2008 R2 64bit boxes.
WASService adds the WAS Services to Windows services list, but fails to stop/start them.

If I bounce the box, then services are getting started. If I stop them, it is setting the service status as blank. If I start it again, it throws "Windows could not start IBM WebSphere Application Server – servicename on local computer". When checked in the event logs "The IBM WebSphere Application Server V7.0 - CellManager01 service terminated with service-specific error %%134220456." is the message.

 

This is how I have added WAS Services to Windows Services

D:\IBM\WebSphere\AppServer\bin\WASService.exe -add CellManager01 -serverName dmgr -profilePath D:\IBM\WebSphere\AppServer\profiles\Dmgr01 -wasHome D:\IBM\WebSphere\AppServer -logFile D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\SystemOut.log -logRoot D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr -restart true -startType automatic -stopArgs "-username xxxxxxxxx -password xxxxxxx" –encodeParams

To solve this, one can use WASServiceCmd Utility. This utility is easy to use, grabs all the info you need to pass, creates the service command, executes it.

Here is the technote about WASServiceCmd

http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21397335

Here is my WASServiceCmd log entry
wasservice.exe -add "CellManager01" -serverName "dmgr" -profilePath "D:\IBM\WebSphere\AppServer\profiles\Dmgr01" -encodeParams -stopArgs "-username xxxxxxxx -password ******** -startType automatic -restart true
wasservice.exe -add "Node01" -serverName "nodeagent" -profilePath "D:\IBM\WebSphere\AppServer\profiles\wlmprime01" -encodeParams -stopArgs "-username xxxxxxx -password ******** -startType automatic -restart true

These services are now, properly working.
 
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

Elevated user privileges

Problem: I have edited a file, say, httpd.conf on Windows 2008 R2 64 bit server. I saved the file and bounced the apache. But, my changes were not in effect. I looked deep into it, then realized that, Windows is storing a copy of httpd.conf on Desktop in VirtualData folder, under this folder, created entire folder structure and stored the file in there.
To avoid this, edit the files or run the commands as an administrator or disable User Access Control (UAC).

Technote from IBM

Running WebSphere Application Server command-line tools might require elevated Microsoft Windows user account privileges

Technote (troubleshooting)   Problem(Abstract) To successfully use some IBM WebSphere Application Server command-line tools, you might need to explicitly elevate Microsoft Windows user account privileges if you are not using the built-in administrator account to run the commands. This action is applicable to the Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 operating systems only. If Windows User Account Control (UAC) is disabled on your system, then this document is not applicable.   Cause You must use a Windows user account that has full Administrator account privileges for certain operations on Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 operating systems. Commands that involve Windows services or access to the Windows system registry require that type of full authority due to the Windows User Account Control implementation for those two operating systems. For example, if you use a regular administrator group account that is not the built-in Administrator account, then you will likely need to explicitly elevate your user account privileges when you run the launchpad or Profile management tool commands. This action assumes that your operating system is running with the default values for system-wide security policies that are related to the Windows User Account Control.

http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=Win7_2008_R2&uid=swg21315375&loc=en_US&cs=utf-8&lang=en
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

uptime

uptime is a measure of the time a machine has up been.
This is pretty useful command.

To know since when the system is up one can do like this at the terminal prompt
$uptime
11:10:27 up 9 mins, 2 users, Load average: 0.02, 0.24, 0.18

Determining system uptime in windows -

1.

C:\> systeminfo | find "Time:"
System Up Time:            0 Days, 8 Hours, 7 Minutes, 19 Seconds

Note: Windows Vista Business 64-bit and Windows 7 do not return a "System Up Time" but "System Boot Time" instead.

2.

C:\> net statistics server | find "since"
Server Statistics for \\COMPUTERNAME
 
Statistics since 8/31/2009 8:52:29 PM

remove directory

If you need to remove a directory, or files and or folders under a directory, in say, Solaris you do like this,
say to remove cache under wstemp
rm -r wstemp/*
which removes files folders under wstemp recursively.
rm test.txt
deletes test.txt file
rm -i wstemp/*
inquires and prompts yes or no for each file
In Linux
rm -f - force removes a file
rm -fr - force removes directory

In DOS -
rmdir is the command to remove a directory.
rmdir dSample
removes if dSample dir is empty.
To force remove
rmdir /S dSample
removes dSample directory but inquires
rmdir /S /Q dSample
removes dSample directory and its sub directories quietly.

Enjoy your day.

Installation Issues

Mr.X installed WAS like this on Win 08 server-

Started to launcher.
Selected WAS installer.
The installer had successfully passed OS verification.
Then selected Cell Topology. WAS 6.1 and above gives you an option to install a Cell. Meaning, installer installs Dmgr, installs an appserver, and federates that to dmgr.
Now, with all the needed inputs, the installer started to install binaries, installed successfully dmgr, appserver and even successfully federated everything.

Now, as this guy didnt configured security at the time of installation, wants to do it in the post installation.

He did like this -
After immediately installing, he ran the ivt (installation verification test).
Then went to admin console, kicked in security setup process.

WHAT IS HE MISSING?

The error what he got was - after configuring security, he wanted to bounce the services, bounce dmgr, bounce node agent, bounce server.
server was failing to start.
dmgr cannot recognize server.

What to do?ADMR0111E is one of the errors.

WASService command

Today one of colleague was trying to add a jvm to Windows Service.
This is the syntax for the command -
WASService.exe -add service_name
-serverName server_name
-profilePath server_profile_directory
[-wasHome
app_server_root]
[-configRoot configuration_repository_directory]
[-startArgs additional_start_arguments]
[-stopArgs additional_stop_arguments]
[-userid user_id -password password]
[-logFile service_log_file]
[-logRoot server_log_directory]
[-restart true | false]
[-startType automatic | manual | disabled]

This guy is fighting with some set of parameters. He is executing, command runs, he goes to the services, he finds that specific jvm in the services, but when he starts it, it simply says *started*, upon right clicking on the service, he sees only start option, remaining faded out.

So, whats the problem?
Go through the command options properly -
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html
He was trying to add jvm to win services like this -
WASService.exe add blabla -logFile path/to/a/location/server.log -logRoot path/to/a/location/

yata yata yata

The problem is - one should pass SERVER LOG FILE as logFile and SERVER_LOG_LOCATION not to another location.
The WASService command looks for a file named server_name .pid to determine if the server is running.

So, if you want to add a jvm, by name server1 to Win services, you need to pass server1 log location.

Have Fun

unix like commands in dos

are you looking for commands like tail, follow this url, http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displayLang=en download rktools.exe and enjoy the following commands -
* Acctinfo.dll (documented in Readme.htm)
* Adlb.exe: Active Directory Load Balancing Tool
* Admx.msi: ADM File Parser
* Atmarp.exe: Windows ATM ARP Server Information Tool
* Atmlane.exe: Windows ATM LAN Emulation Client Information
* Autoexnt.exe: AutoExNT Service
* Cdburn.exe: ISO CD-ROM Burner Tool
* Checkrepl.vbs: Check Replication
* Chklnks.exe: Link Check Wizard
* Chknic.exe: Network Interface Card Compliance Tool for Network Load Balancing
* Cleanspl.exe: Spooler Cleaner
* Clearmem.exe: Clear Memory
* Clusdiag.msi: Cluster Diagnostics and Verification Tool
* Clusfileport.dll: Cluster Print File Port
* Clusterrecovery.exe: Server Cluster Recovery Utility
* Cmdhere.inf: Command Here
* Cmgetcer.dll: Connection Manager Certificate Deployment Tool
* Compress.exe: Compress Files
* Confdisk.exe: Disk Configuration Tool
* Consume.exe: Memory Consumers Tool
* Creatfil.exe: Create File
* Csccmd.exe: Client-Side Caching Command-Line Options
* Custreasonedit.exe: Custom Reason Editor (documented in Readme.htm)
* Delprof.exe: User Profile Deletion Utility
* Dh.exe: Display Heap
* Diskraid.exe: RAID Configuration Tool
* Diskuse.exe: User Disk Usage Tool
* Dnsdiag.exe: SMTP DNS Diagnostic Tool (documented in Readme.htm)
* Dumpfsmos.cmd: Dump FSMO Roles
* Dvdburn.exe: ISO DVD Burner Tool
* Empty.exe: Free Working Set Tool
* Eventcombmt.exe: Check Replication
* Fcopy.exe: File Copy Utility for Message Queuing
* Frsflags.vbs
* Getcm.exe: Connection Manager Profile Update
* Gpmonitor.exe: Group Policy Monitor
* Gpotool.exe: Group Policy Objects
* Hlscan.exe: Hard Link Display Tool
* Ifilttst.exe: IFilter Test Suite
* Ifmember.exe: User Membership Tool
* Inetesc.adm: Internet Explorer Enhanced Security Configuration
* Iniman.exe: Initialization Files Manipulation Tool
* Instcm.exe: Install Connection Manager Profile
* Instsrv.exe: Service Installer
* Intfiltr.exe: Interrupt Affinity Tool
* Kerbtray.exe: Kerberos Tray
* Kernrate.exe: Kernel Profiling Tool
* Klist.exe: Kerberos List
* Krt.exe: Certification Authority Key Recovery
* Lbridge.cmd: L-Bridge
* Linkd.exe
* Linkspeed.exe: Link Speed
* List.exe: List Text File Tool
* Lockoutstatus.exe: Account Lockout Status (documented in Readme.htm)
* Logtime.exe
* Lsreport.exe: Terminal Services Licensing Reporter
* Lsview.exe: Terminal Services License Server Viewer
* Mcast.exe: Multicast Packet Tool
* Memmonitor.exe: Memory Monitor
* Memtriage.exe: Resource Leak Triage Tool
* Mibcc.exe: SNMP MIB Compiler
* Moveuser.exe: Move Users
* Mscep.dll: Certificate Services Add-on for Simple Certificate Enrollment Protocol
* Nlsinfo.exe: Locale Information Tool
* Now.exe: STDOUT Current Date and Time
* Ntimer.exe: Windows Program Timer
* Ntrights.exe
* Oh.exe: Open Handles
* Oleview.exe: OLE/COM Object Viewer
* Pathman.exe: Path Manager
* Permcopy.exe: Share Permissions Copy
* Perms.exe: User File Permissions Tool
* Pfmon.exe: Page Fault Monitor
* Pkiview.msc: PKI Health Tool
* Pmon.exe: Process Resource Monitor
* Printdriverinfo.exe: Drivers Source
* Prnadmin.dll: Printer Administration Objects
* Qgrep.exe
* Qtcp.exe: QoS Time Stamp
* Queryad.vbs: Query Active Directory
* Rassrvmon.exe: RAS Server Monitor
* Rcontrolad.exe: Active Directory Remote Control Add-On
* Regini.exe: Registry Change by Script
* Regview.exe (documented in Readme.htm)
* Remapkey.exe: Remap Windows Keyboard Layout
* Robocopy.exe: Robust File Copy Utility
* Rpccfg.exe: RPC Configuration Tool
* Rpcdump.exe
* Rpcping.exe
* RPing: RPC Connectivity Verification Tool
* Rqc.exe: Remote Access Quarantine Client
* Rqs.exe: Remote Access Quarantine Agent
* Setprinter.exe: Spooler Configuration Tool
* Showacls.exe
* Showperf.exe: Performance Data Block Dump Utility
* Showpriv.exe: Show Privilege
* Sleep.exe: Batch File Wait
* Sonar.exe: FRS Status Viewer
* Splinfo.exe: Print Spooler Information
* Srvany.exe: Applications as Services Utility
* Srvcheck.exe: Server Share Check
* Srvinfo.exe: Remote Server Information
* Srvmgr.exe: Server Manager
* Ssdformat.exe: System State Data Formatter
* Subinacl.exe
* Tail.exe
* Tcmon.exe: Traffic Control Monitor
* Timeit.exe (documented in Readme.htm)
* Timezone.exe: Daylight Saving Time Update Utility
* Tsctst.exe: Terminal Server Client License Dump Tool
* Tsscalling.exe: Terminal Services Scalability Planning Tools
* Uddicatschemeeditor.exe: UDDI Services Categorization Scheme Editor
* Uddiconfig.exe: UDDI Services Command-line Configuration Utility
* Uddidataexport.exe: UDDI Data Export Wizard
* Usrmgr.exe: User Manager for Domains
* Vadump.exe: Virtual Address Dump
* Vfi.exe: Visual File Information
* Volperf.exe: Shadow Copy Performance Counters
* Volrest.exe: Shadow Copies for Shared Folders Restore Tool
* Vrfydsk.exe: Verify Disk
* Winexit.scr: Windows Exit Screen Saver
* Winhttpcertcfg.exe: WinHTTP Certificate Configuration Tool
* Winhttptracecfg.exe: WinHTTP Tracing Facility Configuration Tool
* Winpolicies.exe: Policy Spy
* Wins.dll: WINS Replication Network Monitor Parser
* Wlbs_hb.dll & Wlbs_rc.dll: Windows Load Balancing Server Network Monitor Parsers