Decidedly kitsch !, a set on Flickr.
Tuesday, 12 February 2013
Tuesday, 5 February 2013
ColdFusion IceBreaker #8 : ColdFusion 32 bit or 64 bit ???
So what happens when you take over an existing ColdFusion installation and want to update it ?
Or something doesn't work and you want to verify if its "supposed" to work for a particular bit version???
Its a bit typical to check whether ColdFusion was installed in its 32bit or 64 bit flavor,particularly if you were not the one who installed it
Here are a few ways to detect the current bit version of your installed ColdFusion server
1)Use your install logs
Open the install log (Adobe_ColdFusion_X_xxxxx(optional for 9)_InstallLog.log.
It will contain the following information:
-java.version : This is the version of the Java used in the installer.Might not necessarily match your system's java version
-java.vm.name : Observe this carefully .If its a 64bit install ,this value will mention 64 Eg: Java HotSpot(TM) 64-Bit Server VM' .If its a 32 bit install there wont be any such mention Eg: Java HotSpot(TM) Server VM'
Instead of "Server" it might say "Client' depending on installation,but that is irrelevant for judging whether its a 32bit or a 64 bit install
-os.arch : This explicitly states x86 for 32 bit install and x64 for 64 bit install
2)Use java -version
Goto <ColdFusion-Home>/runtimr/jre/bin
Give java.exe -version
You should be able to see java version,runtime environment and the java vm name
N.B. The Java information in Administrator->System information reflects the java that CF is using as opposedto the java that the installer used,so don't count on it
Or something doesn't work and you want to verify if its "supposed" to work for a particular bit version???
Its a bit typical to check whether ColdFusion was installed in its 32bit or 64 bit flavor,particularly if you were not the one who installed it
Here are a few ways to detect the current bit version of your installed ColdFusion server
1)Use your install logs
Open the install log (Adobe_ColdFusion_X_xxxxx(optional for 9)_InstallLog.log.
It will contain the following information:
-java.version : This is the version of the Java used in the installer.Might not necessarily match your system's java version
-java.vm.name : Observe this carefully .If its a 64bit install ,this value will mention 64 Eg: Java HotSpot(TM) 64-Bit Server VM' .If its a 32 bit install there wont be any such mention Eg: Java HotSpot(TM) Server VM'
Instead of "Server" it might say "Client' depending on installation,but that is irrelevant for judging whether its a 32bit or a 64 bit install
-os.arch : This explicitly states x86 for 32 bit install and x64 for 64 bit install
2)Use java -version
Goto <ColdFusion-Home>/runtimr/jre/bin
Give java.exe -version
You should be able to see java version,runtime environment and the java vm name
N.B. The Java information in Administrator->System information reflects the java that CF is using as opposedto the java that the installer used,so don't count on it
Tuesday, 22 January 2013
Adding extra packages to Android SDK
Recently I wanted to download some additional packages to my existing Android SDK.
The simplest way to go about anything is seemingly the UI way.
So I went ahead and launched my Android SDK from the Start Menu.,and as expected it displayed the sdk contents.But to my absolute amazement ,even thought the updates options was checked the Packages View would not show me any updates to the folders.
All it would show me was that updates were available for "Android SDK Tools" and "Android SDK Platform-tools".
Since I had no use for an update I happily ignored those two and focussed on the Extras folder which is where the said packages were supposed to reside.
No matter how many restarts I made to the SDK Manager (including launching it from eclipse,starting it from Start menu with administrator permissions)
Finally I decided to do the minimal and updated the suggested updates to "Android SDK Tools" and "Android SDK Platform-tools" and restarted the SDK Manager
And to my utter surprise .....
The Packages View goes ahead and shows all that is available for download in all the expected folders: Tools,Various Android Versions and the Extras.
now it was easy to download whatever I required .
The simplest way to go about anything is seemingly the UI way.
So I went ahead and launched my Android SDK from the Start Menu.,and as expected it displayed the sdk contents.But to my absolute amazement ,even thought the updates options was checked the Packages View would not show me any updates to the folders.
All it would show me was that updates were available for "Android SDK Tools" and "Android SDK Platform-tools".
Since I had no use for an update I happily ignored those two and focussed on the Extras folder which is where the said packages were supposed to reside.
No matter how many restarts I made to the SDK Manager (including launching it from eclipse,starting it from Start menu with administrator permissions)
Finally I decided to do the minimal and updated the suggested updates to "Android SDK Tools" and "Android SDK Platform-tools" and restarted the SDK Manager
And to my utter surprise .....
The Packages View goes ahead and shows all that is available for download in all the expected folders: Tools,Various Android Versions and the Extras.
now it was easy to download whatever I required .
Moral of the Story : Need an extra package? update exisiting packages and restart SDK Manager (run as administrator)
Monday, 21 January 2013
Tuesday, 15 January 2013
Subscribe to:
Posts (Atom)