Products
- Muse^® Federated Search, today’s most powerful of its kind, is known as best of multiple target searching and content normalization to a single data model.
- Muse^® Proxy is a highly customizable multi-platform proxy server, easy to use and manage, acting as a gateway to authenticated content.
- Muse^® Harvest is based on different types of controlled extraction, such as search, date or feed based. it features a consistent delivery record format.
  - Overview
  - Features
- Muse^® Hybrid brings a powerful new approach to content discovery by combining real-time global federated searching with high performance central indexed searching.
  - Overview
  - Features
Services
Support
- FAQ
- Downloads
About
Contact

FAQ Tag: timeout

How to increase the inactivity timeout of a Muse Proxy Application?

The default session timeout of a Muse Proxy Application is of 30 minutes. When the authentication session of the Muse Proxy Application is close to end, a Session Timeout warning pop-up and/or a Session Timeout warning window will appear. Each of them displays a message which notifies the user regarding the remaining time from the…

What are the application (inactivity) timeouts in Muse?

There are three inactivity timeouts levels in Muse. In ascending order they are: – application level – WebBridge level – ICE level So the application times out before the WebBridge which times out before ICE. This means that values for the timeout levels must go in ascending order too where ICE is longest and application…

When I test/search many Sources at a time some fail, but when searched individually they work.

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…

I often get “timeout” messages from a Source. When performing a search in the native site it takes around 3 minutes to receive results. How do I increase the timeout of a Source?

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…