Startup Sequence for ISS With New Broker Integrated With Current GlassFish
(Doc ID 2178367.1)
Last updated on MARCH 07, 2019
Applies to:
Oracle GlassFish Server - Version 3.1.2 and laterOracle Communications Indexing and Search Service - Version 1.0.5.18.0 and later
Oracle Solaris on x86-64 (64-bit)
Symptoms
Question:
What is the new startup sequence for ISS with new broker integrated with GlassFish?
Problem:
The automated installation and setup of GlassFish and Indexing and Search Service (ISS) causes the Service Management Framework (SMF) service (On Solaris) for domain1 to go into maintenance state.
Changes
Previously, the startup sequence needed to be:
- Broker
- Indexing and Search Service (ISS)
- GlassFish
That way the broker was running before ISS started, but the web server could not try to use ISS until after ISS was started.
Now with broker integrated in GlassFish, the startup sequence needs to be:
- GlassFish
- Indexing and Search Service (ISS)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |