Lines 185-190
Link Here
|
185 |
standardHost.notContext=Child of a Host must be a Context |
185 |
standardHost.notContext=Child of a Host must be a Context |
186 |
standardHost.nullName=Host name is required |
186 |
standardHost.nullName=Host name is required |
187 |
standardHost.problematicAppBase=Using an empty string for appBase on host [{0}] will set it to CATALINA_BASE, which is a bad idea |
187 |
standardHost.problematicAppBase=Using an empty string for appBase on host [{0}] will set it to CATALINA_BASE, which is a bad idea |
|
|
188 |
standardHostValue.customStatusFailed=Custom error page {0} could not be dispatched correctly. Probably missing servlet mapping in web.xml |
188 |
standardServer.accept.timeout=The socket listening for the shutdown command experienced an unexpected timeout [{0}] milliseconds after the call to accept(). Is this an instance of bug 56684? |
189 |
standardServer.accept.timeout=The socket listening for the shutdown command experienced an unexpected timeout [{0}] milliseconds after the call to accept(). Is this an instance of bug 56684? |
189 |
standardServer.shutdownViaPort=A valid shutdown command was received via the shutdown port. Stopping the Server instance. |
190 |
standardServer.shutdownViaPort=A valid shutdown command was received via the shutdown port. Stopping the Server instance. |
190 |
standardServer.storeConfig.notAvailable=No StoreConfig implementation was registered as an MBean named [{0}] so no configuration could be saved. A suitable MBean is normally registered via the StoreConfigLifecyleListener. |
191 |
standardServer.storeConfig.notAvailable=No StoreConfig implementation was registered as an MBean named [{0}] so no configuration could be saved. A suitable MBean is normally registered via the StoreConfigLifecyleListener. |