|
Problem(Abstract) |
When generating a start server script using
-script option, nothing is written to native_stdout.log or
native_stderr.log at the start of the JVM, such as starting the WebSphere®
Application Server. |
|
|
|
Cause |
This is a limitation of the -script option. |
|
|
Resolving the
problem |
Start script generated by using following command:
startServer
server_name [options]
Options:
- -script [<script
fileName>] -background
Generates a launch script with the
startServer command instead of launching
the server process directly. The launch script name is an optional
argument. If you do not supply the launch script name, the default script
file name is start_server_name based on the
server_name name passed as the first
argument to the startServer command. The -background
parameter is an optional parameter that specifies that the generated
script will run in the background when you execute it.
- startServer
server_name -script
Produces the start_server_name.sh or
start_server_name.bat files, such as
start_server1.bat, when you invoke the script to start the JVM.
Output: Script generated successfully.
- start_server1.sh
server_name
Example: start_server1.sh server1
No native_stdout.log or native_stderr.log will be
created. This is design limitation. When we start the server using this
start_server1.sh script, you will notice that the command prompt
never returns so that we can type a new command that is because it is
showing you whatever is printed to the
native_stdxxx.logs. So instead of
logging that information to those logs, it just prints it to the screen.
So this is not a defect, it is by design.
We have extensively investigated with developer and this is normal
behavior. The native logs will not get generated, when the server is
started using script.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Historical Number |
73144
999
760 |
|
|
|
|