www.michalscorner.com what I have recently discovered

15Aug/120

websphere: Caused by: com.ibm.websphere.ce.cm.StaleConnectionException: Io exception: There is no process to read data written to a pipe.

Stale connection may occur when:

  • The application tries to get a connection and fails, as when the database is not started.
  • A connection is no longer usable because of a database failure. When an application tries to use a previously obtained connection, the connection is no longer valid. In this case, all connections currently in use by the application can get this error when they try to use the connection.
  • The connection is orphaned (because the application had not used it in at most two times the value of the unused timeout setting) and the application tries to use the orphaned connection. This case applies only to Version 4.0 data sources.
  • The application tries to use a JDBC resource, such as a statement, obtained on a stale connection.
  • A connection is closed by the Version 4.0 data source auto connection cleanupfeature and is no longer usable. Auto connection cleanup is the standard mode in which connection management operates. This mode indicates that at the end of a transaction, the transaction manager closes all connections enlisted in that transaction. This enables the transaction manager to ensure that connections are not held for excessive periods of time and that the pool does not reach its maximum number of connections prematurely.A negative ramification does ensue, however, when the transaction manager closes the connections and returns the connection to the free pool after a transaction ends. An application cannot obtain a connection in one transaction and try to use it in another transaction. If the application tries this, aStaleConnectionexception occurs because the connection is already close

 

 

30May/120

websphere: how to refresh security settings with scriptnig

after changing security settings, creating or modifying authentication alias you can reload security settings without restarting websphere processes.

reload security settings on specific websphere process

set agm [ $AdminControl queryNames type=AuthorizationGroupManager,process=,* ]
$AdminControl invoke $agm refreshAll

reload security settings on all processes

set agm [ $AdminControl queryNames type=AuthorizationGroupManager,* ]
for a $agm {
$AdminControl invoke $a refreshAll
}

18Apr/120

websphere mq: basic administration commands

launch
runmqsc

display queue manager(s)
display qmmgr(*)

display queue(s)
display queue(*)

display channel(s)
display channel(*)

display listener(s)
display listener(*)

check queue status
display qstatus(*)

clear queue
clear qlocal(queue_name)

display connections
display conn(*)