Unable to locate asset after submission/approval
We just recently upgraded our RAM server to 7.5.0.1. I created an asset within my community, categorized it and saved it. I received an email regarding its submitted state however it does not show up on my dashboard when logged into RAM. I can only access it by the link provided in the email. When I subsequently approved it, it still does not show up on my dashboard nor is it located through Asset Search after several hours when logged in as myself. What would lead to this type of behavior?
|
6 answers
Your indexer is not running correctly. Verify that it is indexing things
and not throwing errors. -- Rich Kulp Rational Asset Manager developer |
Your indexer is not running correctly. Verify that it is indexing things All the jobs are scheduled appropriately and there are no errors showing in the logs. I can understand the indexer being in play for asset searches but I would not expect it to be on a user's asset display (My Assets). |
The 'My Assets' page does depend on the indexer running properly in order to display up to date data. What logs did you look at? The error may be in one of the following logs.
ramJobServerDebug.log ramDebug.log SystemErr.log SystemOut.log I would suggest stopping the server, deleting all logs, and starting the server. Wait several minutes and submit an asset to ensure the indexer runs at least once. You can download the logs from Administration -> Tools -> 'Support logs changed today.' Also, check Administration -> Tools -> View Job Status to ensure the 'Asset index builder' is reporting that it is running. If you still do not see any errors, you can try running the indexer inside the WAS process. Navigate to http://<host>/ram/admin/repository/advancedConfiguration.faces and uncheck 'Perform all indexing in a remote process'. Then hit save. Running with this setting unchecked is not supported as it can result in performance issues, but it may give a temporary workaround until we have a chance to look at your logs. |
The 'My Assets' page does depend on the indexer running properly in order to display up to date data. What logs did you look at? The error may be in one of the following logs. Thanks Sheehan, Prior to restarting the server (since it is in production use), I would prefer to sniff out the issues further. I checked the job status and the asset index builder has not run since 2/1. I hit the build search index button on tools and waited. Nothing shows up in the job status or logs after several minutes. |
|
The below error was in the logs. The problem was that the number of file descriptors that can be open at once was set too low. See http://publib.boulder.ibm.com/infocenter/ramhelp/v7r5m0/index.jsp?topic=/com.ibm.ram.installguide.doc/topics/t_configure_setup_asst.html for instructions on how to set the appropriate ulimit values.
Caused by: java.net.SocketException: Too many open files at sun.nio.ch.Net.socket0(Native Method) at sun.nio.ch.Net.socket(Net.java:153) at sun.nio.ch.SocketChannelImpl.<init>(SocketChannelImpl.java:121) at sun.nio.ch.SelectorProviderImpl.openSocketChannel(SelectorProviderImpl.java:55) at java.nio.channels.SocketChannel.open(SocketChannel.java:120) at com.ibm.team.repository.transport.client.InterruptableSocketFactory.createSocket(InterruptableSocketFactory.java:49) at com.ibm.team.repository.transport.client.SecureInterruptableSocketFactory.createSocket(SecureInterruptableSocketFactory.java:316) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:148) ... 30 more |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.