Stop Listener
Change the port number in the following path:
D:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\listener.ora
Change the port number to desired port number and save.
Start the listener.
Run the following statement in the SQL prompt as sys dba.
ALTER SYSTEM SET LOCAL_LISTENER='(ADDRESS = (PROTOCOL = TCP)(HOST = host-name)(PORT = 1522))';
Check the status of listener, it should pick up your service name.
WebSphere Commerce Suite, WebSphere Application server, IBM HTTP Server and Oracle
Thursday, November 12, 2009
Changing ORACLE LISTENER port number
Monday, November 2, 2009
SOAP request Timeout
In wsadmin.traceout, the exception was thrown:org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]"
follows:
---------------------------
com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invokeat com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:642)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:512)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:332)
----------------------------
SocketTimeoutException was possibly thrown because the SOAP timeout was not be long enough, if the exporting of the ear takes longer than the value specified by the SOAP timeout, it would fail.The SOAP timeout parameter was specified in \opt\IBM\WebSphere\AppServer\profiles\FairPrice\properties\soap.client.props, as following in your environment:
#------------------------------------------------------------------------------
# SOAP Request Timeout #
# - timeout (specified in seconds [default 180], 0 implies no timeout)#
#------------------------------------------------------------------------------
com.ibm.SOAP.requestTimeout=180
#------------------------------------------------------------------------------
So I have following suggestion to resolve the problem:
1. Chanage com.ibm.SOAP.requestTimeout to 0 or a larger value (e.g. 3600)
2. Restart server1
follows:
---------------------------
com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invokeat com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:642)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:512)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:332)
----------------------------
SocketTimeoutException was possibly thrown because the SOAP timeout was not be long enough, if the exporting of the ear takes longer than the value specified by the SOAP timeout, it would fail.The SOAP timeout parameter was specified in \opt\IBM\WebSphere\AppServer\profiles\FairPrice\properties\soap.client.props, as following in your environment:
#------------------------------------------------------------------------------
# SOAP Request Timeout #
# - timeout (specified in seconds [default 180], 0 implies no timeout)#
#------------------------------------------------------------------------------
com.ibm.SOAP.requestTimeout=180
#------------------------------------------------------------------------------
So I have following suggestion to resolve the problem:
1. Chanage com.ibm.SOAP.requestTimeout to 0 or a larger value (e.g. 3600)
2. Restart server1
Export fix while Applying APAR
Find exportEar.jacl under $Commerce_installDIR/config/deployment/scripts. Make a backup.
2. Change
$WCSHelper exportApplication $AppName $AppPath
to
$AdminApp export $AppName $AppPath
3. Launch UPDI and retry the APAR deployment
2. Change
$WCSHelper exportApplication $AppName $AppPath
to
$AdminApp export $AppName $AppPath
3. Launch UPDI and retry the APAR deployment
Subscribe to:
Posts (Atom)