Ubuntu 14.04 LTS Java Development Environment Configuration

Install and configure environment:
  • Download the Ubuntu 64bit LTS install image
  • Create a bootable DVD or flash drive
  • Install Ubuntu
  • Update software
  • Install gnome classic
  • Synaptic Package Manager
  • PulseAudio Preferences - open and check the Make discoverable...
  • PulseAudio Volume Control
  • OpenConnect Cisco VPN client
Update grub to reduce wait seconds

   sudo gedit /etc/default/grub
   #change timeout from 10 to 2 or whatever
   GRUB_TIMEOUT=2

   sudo grub-update

Install gnome classic

  sudo apt-get update; sudo apt-get install gnome-session-fallback
  Fix 14.10 vanishing cursor with sudo apt-get install ibus-gtk
  • Reboot and select Classic before logging in
Install Network Manager Open Connect Plugins (for Cisco VPN configuration)
  • Open Applications : System Tools : Adinistration : Synaptic Package Manger
  • Search for network-manager-openconnect
  • Mark both entries for installation and apply
Add launch icons to top menu/launcher/toolbar with

    Super(Window Key) + Alt + Mouse Right Click

Rearrange launcher icons with:

    Alt + Mouse Middle click and drag

 Remove launcher icon with:

     Super(Window Key) + Alt + Mouse Right Click then Remove From Panel

Open Firefox and search for Google Chrome, download and install the 64bit version

Open Applications : System Tools : System Settings and:
  • update Brightness and Lock to reduce display shutdown time
  • update Power for appropriate low power and screen close actions
  • update Mouse & Touchpad to disable touchpad and accelerate the mouse
  • in appearance you can enable menus on windows for Unity, unnecessary in Classic
Open Applications : Accessories : Files : Settings : Preferences:
  • set View new folders using: List View 
Open Applications : Ubuntu Software Center and install:
  • gparted
  • GIMP
  • KDiff3
  • Graphical Disk Map
  • Revelation Password Manager
Download and install the latest JDK:
uncompress and untar into ~/java with
     tar xfz jdk-8u31-linux-x64.tar.gz

create symlink with:
     ln -s ~/java/jdk1.8.0_31 jdk

gedit ~/.profile and add:
     export JAVA_HOME='~/java/jdk'
     PATH=$JAVA_HOME/bin:$PATH

 Download and install the latest:
Eclipse plugins
  • EclEmma - code coverage
  • Subclipse - tigris subversion
  • Egit - official eclipse git support
Google Chrome Extensions:
  • Hangouts
  • Voice
  • Calendar
Ansible Configuration

Configure ansible:
In /etc/ansible/hosts comment out all entries and add an entry like the following for your machines IP
> 192.168.25.120 ansible_connection=local
In /etc/ansible/ansible.cfg add an entry like the following with your linux username
> ansible_ssh_user=someUserName
uncomment both:
ask_sudo_pass = True
ask_pass      = True

SSH

sudo apt-get install openssh-server

Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more