First off download JDK 6
You will get a bin file with the version you may choose by this time I have choose 'jdk-6u45-linux-x64.bin', after we will execute the program and move to another proper directory:
user@user:~$ chmod +x jdk-6u45-linux-x64.bin
user@user:~$ ./jdk-6u45-linux-x64.bin
user@user:~$ sudo mkdir /usr/lib/jvm/
user@user:~$ sudo mv jdk1.6.0_45/ /usr/lib/jvm/
Next of put directory as update alternatives with the priority 1
user@user:~$ sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.6.0_45/bin/java" 1
user@user:~$ sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.6.0_45/bin/javac" 1
user@user:~$ sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.6.0_45/bin/javaws" 1
Securily, regard a correct alternatives on java program and check if there is installed the correct option in the system
user@user:~$ sudo update-alternatives --config java
user@user:~$ sudo update-alternatives --config javac
user@user:~$ sudo update-alternatives --config javaws
user@user:~$ which java
user@user:~$ which javac
user@user:~$ which javaws
Edit the next file and add the following lines at the end of the script:
sudo gedit /etc/profile
----------
JAVA_HOME=/usr/lib/jvm/jdk1.6.0_45
PATH=$PATH:$HOME/bin:$JAVA_HOME/bin
JRE_HOME=/usr/lib/jvm/jdk1.6.0_45/jre
PATH=$PATH:$HOME/bin:$JRE_HOME/bin
export JAVA_HOME
export JRE_HOME
export PATH
---------
Finally execute profile to load variable system
. /etc/profile
update: 25/06/2016
Add reference to jar:
sudo alternatives --install /usr/bin/jar jar /opt/jvm/jdk1.8.0_91/bin/jar 2
sudo alternatives --install /usr/bin/javac javac /opt/jvm/jdk1.8.0_91/bin/javac 2
sudo alternatives --set jar /opt/jvm/jdk1.8.0_91/bin/jar
sudo alternatives --set javac /opt/jvm/jdk1.8.0_91/bin/javac
Monday, September 21, 2015
Sunday, September 13, 2015
How to kill Weblogic Server from console?
If you are wondering how to kill a weblogic instance from console, here are the instructions to try on:
[osh@osh-ThinkPad-T430 bin]$ ps aux | grep 'weblogic'
root 10219 141 4.9 3709388 793312 pts/0 Sl+ 14:09 2:05 /home/osh/Oracle/Middleware/Oracle_Home/oracle_common/jdk/bin/java -Dprod.props.file=/home/osh/Oracle/Middleware/Oracle_Home/wlserver/.product.properties -Dweblogic.wlstHome=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/common/wlst: -DORACLE_HOME=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common -DCOMMON_COMPONENTS_HOME=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common -Xms32m -Xmx1024m -XX:MaxPermSize=384m -Dweblogic.alternateTypesDirectory=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.ossoiap_12.1.3,/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.oamprovider_12.1.3,/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.jps_12.1.3 weblogic.WLST /root/.jdeveloper/system12.1.3.0.41.140521.1008/o.j2ee.adrs/BuildDefaultDomain1.py
osh 10689 0.0 0.0 112640 960 pts/1 S+ 14:10 0:00 grep --color=auto weblogic
[osh@osh-ThinkPad-T430 bin]$ kill -9 10219
After of press an enter key the weblogic should be shutdown.
[osh@osh-ThinkPad-T430 bin]$ ps aux | grep 'weblogic'
root 10219 141 4.9 3709388 793312 pts/0 Sl+ 14:09 2:05 /home/osh/Oracle/Middleware/Oracle_Home/oracle_common/jdk/bin/java -Dprod.props.file=/home/osh/Oracle/Middleware/Oracle_Home/wlserver/.product.properties -Dweblogic.wlstHome=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/common/wlst: -DORACLE_HOME=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common -DCOMMON_COMPONENTS_HOME=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common -Xms32m -Xmx1024m -XX:MaxPermSize=384m -Dweblogic.alternateTypesDirectory=/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.ossoiap_12.1.3,/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.oamprovider_12.1.3,/home/osh/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.jps_12.1.3 weblogic.WLST /root/.jdeveloper/system12.1.3.0.41.140521.1008/o.j2ee.adrs/BuildDefaultDomain1.py
osh 10689 0.0 0.0 112640 960 pts/1 S+ 14:10 0:00 grep --color=auto weblogic
[osh@osh-ThinkPad-T430 bin]$ kill -9 10219
After of press an enter key the weblogic should be shutdown.
Thursday, June 26, 2014
WEBLOGIC JMS: "The persistent file store", "cannot open file"
It is well known that the way to have a persistence store on you JMS Configuration is a good habit on your development mainly if we are talking about of Cluster Enviroment, having a configuration with dat file sored on a filesystem is done by doing asignation on your JMS Server, but what-if something happen with DAT file, perhaps you could even imagine a situation can produce this event, for example a bad configuration throught a unknown familiar user on your server, a kind of application trying to access to DAT file, there some situations could happend, on my experience i have list some specific expection related above:
If you are on this kind of situation my advice to you should please make a backup of your persistence store and follow the next steps:
1. BackUp Persistence Store on a new folder under your filesystem
2. Delete Components on your weblogic likes: Module JMS, Server JMS and Persistence Store.
3. Shutdown all servers involver, including adminserver
4. Start All Servers, please be sure that no one could have any failed exception related.
5. Make your JMS Configuration Again.
6. Most common problems may be resolve by doing this, if there is another problem by creating a JMS Server please try to change the type of writing to save with cache and File locked to false, this is because the time of saving to DAT probably do a mess with another process.
Please take care about situation likes because someone or something on your operating system try to do a connection with your DAT file.
Best Regards,
- The persistence store ... Cannot open file ...
- Cannot find ... DAT File
- GXA... read exception
If you are on this kind of situation my advice to you should please make a backup of your persistence store and follow the next steps:
1. BackUp Persistence Store on a new folder under your filesystem
2. Delete Components on your weblogic likes: Module JMS, Server JMS and Persistence Store.
3. Shutdown all servers involver, including adminserver
4. Start All Servers, please be sure that no one could have any failed exception related.
5. Make your JMS Configuration Again.
6. Most common problems may be resolve by doing this, if there is another problem by creating a JMS Server please try to change the type of writing to save with cache and File locked to false, this is because the time of saving to DAT probably do a mess with another process.
Please take care about situation likes because someone or something on your operating system try to do a connection with your DAT file.
Best Regards,
Subscribe to:
Posts (Atom)