When do the CBR indexing, got this error in p8 trace log as below. The reason is document injecting is slower than indexing. We got the FileStorage I/O bottleneck issue, or it can be resolved by optimizing indexing.
/gpfs/gpfsdev/icf_contentfiles/content/FN0/FN7/28E9F203-84FA-4809-871E-4977D32B654D{BEA940A5-1480-4150-BF72-96ADD540F595}0 (No such file or directory)\n at com.filenet.engine.content.RetryableFileIO.getExistingFileInputStream(RetryableFileIO.java:109)\n at com.filenet.engine.cbr.br.CBRFileInfo.fetchContentTypeResult(CBRFileInfo.java:337)\n at com.filenet.engine.cbr.br.CBRFileInfo.<init>(CBRFileInfo.java:274)\n at com.filenet.engine.cbr.spi.IndexHandle.init(IndexHandle.java:760)\n at com.filenet.engine.cbr.spi.IndexHandle.<init>(IndexHandle.java:429)\n at com.filenet.engine.cbr.spi.CSEIndexProcessor.processRequestList(CSEIndexProcessor.java:1672)\n at com.filenet.engine.cbr.spi.CSEIndexProcessor.submitRequestsForOneIndex(CSEIndexProcessor.java:1161)\n at com.filenet.engine.cbr.spi.CSEIndexProcessor.getAndProcessBatches(CSEIndexProcessor.java:730)\n at com.filenet.engine.cbr.spi.CSEIndexProcessor.indexRequests(CSEIndexProcessor.java:418)\n at com.filenet.engine.cbr.CBRExecutor.execute(CBRExecutor.java:187)\n at com.filenet.engine.tasks.BackgroundTask.safeExecute(BackgroundTask.java:248)\n at com.filenet.engine.tasks.BackgroundTask$BackgroundTaskPriviledgedExceptionAction.run(BackgroundTask.java:1036)\n at com.filenet.engine.context.CallState.doAsSystem(CallState.java:417)\n at com.filenet.engine.tasks.BackgroundTask.run(BackgroundTask.java:204)\n at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908)\n at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931)\n at java.lang.Thread.run(Thread.java:773)\nCaused by: java.io.FileNotFoundException:
Friday, 8 November 2013
Monday, 4 November 2013
How to read CE built-in perf log?
Enable it:
1: verify
there is a file created called "perflog_config.properties" under the
folder of the CE err and trace logs, like this
".../filenet/server1"...
2: open
the file, edit "use.me=true", and also change the
"perflog.dir=<> " to a good existing directory, and save it.
Verify to see if the perflog is writing to that folder
Performance log
format:
[Audit Interval]
[Execution Count] [Avg. Duration (ms)] [Total Duration (ms)] 0 0 [Performance
Counter]
The first column in
the IBM FileNet CPE performance log is the audit interval. This is denoted by
#Audit#-X, where X is 1, 10, 60 or 240. Each reported interval also includes a
time stamp to clearly identify when the performance data was collected. The second
column represents the number of executions for that performance counter during
the audit interval. The third column represents the average duration of those
executions and the fourth column is the total duration. The fifth and sixth
columns are always zero and reserved for future needs. The final column is the
actual performance counter being reported.
This file is located under the [application server
profile]/FileNet/[server_name] directory.
Security disallow access
The one reason for this error is the time of all servers are not synchronized.
Why we need to delete WAS window's service?
By default,
when installing WebSphere 6.1, it is selected to start as windows services
(unlike WebSphere 6.0, you can choose manual startup during the install). By
having WebSphere start as a Windows services (starts up WebSphere when Windows
starts) can cause various problems. Some of them are 1) WebSphere CE server
will not start properly if WebSphere is started before DC is up and running,
this is usually a problem for environment with Tivoli DS since Tivoli DS
require a longer time to start. 2) WebSphere server will not start up/shut down
if the WASService.exe is corrupted
the message
stating that WASServices.exe is not a valid WIN32 application and your
WASService.exe file is 0K (this probably means that your WASServices.exe file
is corrupted), you need to copy the WASService.exe from other WebSphere 6.1
server and then execute the WASService.exe -remove command again to remove it.
Please note that by doing so will enable you to start WebSphere server again,
but it is not guarantee that your server is clean. The proper way to reghost or
rebuild your WebSphere 6.1 server.
ClassNotFoundException
Error:
20:09:42.535
com.ibm.rmi.pi.InterceptorManager runPreInit:176 P=781098:O=0:CT
ORBRas[default] java.lang.ClassNotFoundException:
com.ibm.ws.activity.remote.cos.ActivityServiceClientInterceptor (no security
manager: RMI class loader disabled)
at
sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:386)
Resolve:
Djava.ext.dirs
add "%WAS_HOME%\plugins"
Failed to login
Error message :
SECJ0395E: Could not
locate the SecurityServer at host/port: Unable to determine host / port
information to validate the userid and password entered. You might need to
specify valid securityServerHost/Port in
WAS_INSTALL_ROOT/profiles/profile_name/properties/sas.client.props file.
com.ibm.websphere.security.auth.AuthenticationFailedException:
SECJ0395E: Could not locate the SecurityServer at host/port: Unable to
determine host / port information to validate the userid and password entered.
You might need to specify valid securityServerHost/Port in
WAS_INSTALL_ROOT/profiles/profile_name/properties/sas.client.props file.
CWPKI0019E: Error
parsing the SSL client configuration file
Reason :
- P8 server is not started.
- Check the file existed or not
- Check the WAS client version matches with server or not
- Check the SSL enable or not.
Subscribe to:
Posts (Atom)