To return expected results, you can:
Reduce the number of search terms.
Each term you use focuses the search further.
Check your spelling.
A single misspelled or incorrectly typed term can change your result.
Try substituting synonyms for your original terms.
For example, instead of searching for "java classes", try "java training"
Did you search for an IBM acquired or sold product ?
If so, follow the appropriate link below to find the content you need.
FileNet Deployment Manager (FDM) intermittently errors during the export step and the following error is found in FDM deployment.log file:
filenet_error.api.com.filenet.apiimpl.imex.LoggingStream - The export process is stopping because an exception is being thrown
com.filenet.api.exception.EngineRuntimeException: FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred. The unexpected exception is chained to this exception. Message was: Connection reset
at com.filenet.imex.impl.threads.ContentQueueItem.writeContentToDisk(ContentQueueItem.java:211)
at com.filenet.imex.impl.threads.ContentQueueItem.downloadContent(ContentQueueItem.java:102)
at com.filenet.imex.impl.threads.ExportContentConsumer.run(ExportContentConsumer.java:67)
Caused by:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:200)
at java.net.SocketInputStream.read(SocketInputStream.java:132)
sun.net.
www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnect…
at java.io.FilterInputStream.read(FilterInputStream.java:144)
at java.io.PushbackInputStream.read(PushbackInputStream.java:197)
First
, add the following configuration settings to work around a Java bug:
1. Add the following JVM parameter to the JVM hosting Content Engine (CE):
-DFileNet.WSI.HttpFaultResponseCode=599
2. Add the following JVM parameter on the client (FDM):
-Dsun.net.http.retryPost=false
To do so, add it to DeploymentManager.ini
C:/Program Files (x86)/IBM/FileNet/ContentEngine/tools/_jvm/jre/bin
-vmargs
-Xms256m
-Xmx768m
-Dsun.net.http.retryPost=false
If IBM HTTP Server (IHS) is between FDM and CE, also add to the CE JVM:
-Dsun.net.http.retryPost=false
Second
, set the persistent connections to unlimited to work around a WebSphere bug. This is a connection reset during an HTTP chunked input stream read, and is therefore likely to be caused by this WebSphere APAR.
PI11176: RST CONNECTION IF LEFT 1 OR 2 BYTES UNREAD DURING THE HTTP POST AND CHUNKING
http://www-01.ibm.com/support/docview.wss?uid=swg1PI11176
The current work around for this behavior is to set the "persistent connections" setting in the HTTP Channels of WebSphere to "Unlimited persistent requests per connection".
This can be found in the following location in WAS 8.5.5:
1. Sign in to WebSphere Integrated Solutions.
1. Navigate to Servers > Server Types > WebSphere application servers >
server_name
> Ports.
2. Click "View associated transports" at
WC_defaulthost
.
3. Click HTTPQueueInboundDefault.
4. Click HTTP inbound channel
5. Under Persistent connections,
5.A. Check <checkbox> Use persistent keep alive connections.
5.B. Click Unlimited persistent requests per connection.
You should change this setting for both
WC_defaulthost
and
WC_defaulthost_secure
.
