Linux 下后台启动Weblogic 博客分类: 技术天地 LinuxWeblogicJavaSSHJ2SE
程序员文章站
2024-02-05 16:53:22
...
正常情况下,使用telnet或SSH登陆linux后,使用./startWeblogic.sh在用户推出登陆后,weblogic也会停掉,这是因为wls进程依赖于telnet进程,解决方法有二:
1:切换到csh,键入命令 nohup ./startWeblogic.sh &
2: 切换到csh, ./startWeblogic.sh 启动后ctrl+z, 输入bg,进入后台模式
修改startWeblogic.sh 添加
JAVA_OPTIONS=-Djava.awt.headless=true可以是wls在linux上输出图片
java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/
原因如下
1:切换到csh,键入命令 nohup ./startWeblogic.sh &
2: 切换到csh, ./startWeblogic.sh 启动后ctrl+z, 输入bg,进入后台模式
修改startWeblogic.sh 添加
JAVA_OPTIONS=-Djava.awt.headless=true可以是wls在linux上输出图片
java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/
原因如下
java 代码
- The Sun AWT classes on Unix and Linux have a dependence on the X Window System: when you use the classes, they expect to load X client libraries and be able to talk to an X display server. This makes sense if your client has a GUI... unfortunately, it's required even if your client uses AWT but does not have a GUI. For example, you need access to an X server to use the java.awt.BufferedImage class.
- Access to an X display server means a few things:
- * An X display server is running somewhere.
- * The environment in which you run Java includes an environment variable DISPLAY identifying how to reach the server.
- * There are no security settings in the server to prevent your client from opening a connection.
- In general, if you're running your program from a terminal within the X Window System, all these things are true and the program just works. If you can run other X applications, like xterm or xclock, you should be able to run your Java AWT application.
- In non-graphical environments, such as a servlet engine, your program may not know how to find or connect to an X display server. A common solution here is to run a special non-display version of the X display server, Xvfb, and set DISPLAY to point to it.
- New information forJDK1.4: JDK1.4 evidently includes a new property that will allow the AWT to run in a headless (without a display) environment. This setting is supposed to solve the problem: java.awt.headless=true