FAQ
FAQ by Product
Most Popular
Load More
Latest
(Application General Settings>Interface Options>Logoff)
and set the “Session Timeout” value as needed. Changes here affect only the application you’re editing.
b) for WebBridge timeout: edit the file $MUSE_HOME/web/MusePeer.xml
and modify the MAX_INACTIVE_INTERVAL tag. Values of this tag are specified in seconds. Http server restart is necessary to load this value. Changes here affect all applications using the Muse WebBridge.
c) for ICE level: edit the file $MUSE_HOME/use/ice/ICECore.xml
and modify the MAX_INACTIVE_INTERVAL tag. Values of this tag are specified in milliseconds. ICE server restart is necessary to load this value. Changes here affect the application on the installation.If all Sources work within a Muse application individually but some fail when they are searched together, this is an indication that the target site(s) and/or your Internet connection might be slow or under stress conditions.
First check the following:
– Is the Internet connection slow? Check independently (outside of Muse) to see if the network is generally slow. If so, increase the timeout for all Sources (see below), or possibly limit the number of Sources users search simultaneously to conserve bandwidth or relieve Source overloading issues.
– Do the same Source Packages always timeout no matter how many other Sources are searched simultaneously? In this case it is likely that the Source site is the problem rather than the network. Increase the timeout only for those Sources (see below).
– Does the machine running Muse have a high load? Stop unnecessary processes and/or increase the memory allocated to Muse servers. Check the “Search Details” (or “+” button) if it is available on the search page and look at the information icon for each failed source to see the cause of the failure. This will be useful in diagnosing where the problem lies.
In cases where the target site is working but the communication is slow for some reason the solution is to increase the
If you experience this problem only in only the Muse Admin Console (where a source works when tested individually but fails when tested in a group with others). You may have a different issue. See FAQ “Why do some Sources fail when tested in a group in the Admin Console but they work when tested individually?”
If all Sources work within a Muse application individually but some fail when they are searched together, this is an indication that the target site(s) and/or your Internet connection might be slow or under stress conditions.First check the following:
– Is the Internet connection slow? Check independently (outside of Muse) to see if the network is generally slow. If so, increase the timeout for all Sources (see below), or possibly limit the number of Sources users search simultaneously to conserve bandwidth or relieve Source overloading issues.
– Do the same Source Packages always timeout no matter how many other Sources are searched simultaneously? In this case it is likely that the Source site is the problem rather than the network. Increase the timeout only for those Sources (see below).
– Does the machine running Muse have a high load? Stop unnecessary processes and/or increase the memory allocated to Muse servers. Check the “Search Details” (or “+” button) if it is available on the search page and look at the information icon for each failed source to see the cause of the failure. This will be useful in diagnosing where the problem lies.
In cases where the target site is working but the communication is slow for some reason the solution is to increase the
If you experience this problem only in only the Muse Admin Console (where a source works when tested individually but fails when tested in a group with others). You may have a different issue. See Why do some Sources fail when tested in a group in the Admin Console but they work when tested individually?
There are two parameters involved here:
CONNECT_TIME_OUT
: specifies the timeout value, in milliseconds, to be used when opening the communication link for each resource (e.g. URL) used by this source.READ_TIME_OUT
: specifies the timeout value, in milliseconds, that is involved upon reading on the communication channels.
One can increase the timeout for a given Source Package by increasing the value in the CONNECT_TIME_OUT
and READ_TIME_OUT
fields (the entry is in milliseconds; 1,000 milliseconds = 1 second). To edit these fields of the source profile one must use the Muse Source Console:
- login into the Muse Source Console
- select the desired application from the list of applications
- go to the “Configure” tab
- click on the “Modify” button for the desired source
- update the “Connect Time Out” and “Read Time Out” inputs with the desired values
- to submit the modifications click on the “Update” button
Note: The values for the “Connect Time Out” and “Read Time Out” fields must be given in milliseconds.