I am installing jprofiler on 64bit Scientific Linux release 6.2 (Carbon)
But the installer shows:
---> Package jprofiler.i386 0:8.0.4-1 will be installed
Should I be worried that the Arch is i386?
JProfiler ships with native libraries for 32-bit and 64-bit. They are located in bin/linux-x86 and bin/linux-x64.
The JProfiler GUI is written in Java and uses the appropriate JRE. The selection of the correct native library is only important when adding an -agentpath VM parameter to a start script. The integration wizard has a check box for profiling 64-bit JREs, this changes the library path in the -agentpath VM parameter accordingly.
Related
I am currently having an issue with running mule-standalone-3.4.0 on a windows 64 bit machine below is the issue.
*> Launching a JVM... Starting the Mule Container... Wrapper (Version
3.2.3) http://wrapper.tanukisoftware.org Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
WARNING - Unable to load the Wrapper's native library because none of
the
following files:
wrapper-windows-x86-64.dll
wrapper.dll
could be located on the following java.library.path:
C:\Users\jdudla\%LD_LIBRARY_PATH%
C:\Mule\mule-standalone-3.4.0\lib\boot
Please see the documentation for the wrapper.java.library.path
configuration property.
System signals will not be handled correctly.*
Has anyone else had this issue and corrected it?
Problem was fixed by installing a 32 bit JVM. Mule Standalone CE only works with 32bit. Mule enterprise works with 64bit...
**> Mule CE ship with community version of the Tanuki Wrapper. The
Community version of Tanuki wrapper does not support windows 64 bit.
http://wrapper.tanukisoftware.org/doc/english/download.jsp#downloadNote2
To run on windows 64 bit you will have to use Mule EE.**
So to run Standalone on a 64bit machine install a 32bit JVM and it will run fine.
You don't have a 64 bit JVM installed. Type java -version from a command line.
c:\> java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
You need to install the a 64 bit JVM or use the 32 bit Mule distro.
I installed Titanium Studio properly and when I execute it, gives me an error like this
"Failed to load the JNI shared library C:\Program files\Java\JDK 1.7.0_17\bin\...\jre\bin\server\jvm.dll"
NOTE: I have java 64bit version.
It might be the issue with the SDK. In order to run Titanium Studio and the Titanium Mobile SDK successfully, your system environment must meet the following condition
For Windows, the 32-bit version of Java JDK is required regardless of
whether Titanium is running on a 32-bit or 64-bit system.
Please read System Requirements before installing the Titanium Studio.
I hope this will help you
Is there any way to find the sql server is 64 bit or 32 bit in machine using wix.
I am building the wix in visual studio 2010.Based on configuration the installer will install. At install time it will check sql is 64 or 32. If OS is 64bit but 32 sql is installed my installer will install.
Thanks,
Rajeev Kumar.
To detect if the target machine is 32-bit or 64-bit you can use VersionNT64 property. This property can be used as a launch condition to stop the 32-bit package from installing on a 64-bit machine. A 64-bit package cannot run on a 32-bit machine and is stopped automatically.
For detecting SQL Server there are multiple approaches. For example you can search for registry values or use a custom action. Perhaps this article will help:
http://blogs.msdn.com/b/sqlexpress/archive/2006/07/29/682254.aspx
I'm developing SharePoint solutions on a virtual 32bit machine, and I use Wix to package the setup.
I'm targeting both 32bit and 64bit environments with my solutions, but in order to create 64bit MSI's, I need to have have a 64bit machine and the 64bit version of WiX.
Normally, this wouldn't be an issue, since I would have just simply use a 64bit dev environment.
But there are some issues with developing SharePoint solutions on a 64bit platform, which more or less forces me to develop on the 32bit platform.
Because of that, I can't create a 64bit MSI's, unless I copy the source files to a 64bit machine just to build the 64bit MSI, which feels a little bit cumbersome.
Is there any trick to flag/build the 64bit MSI package on my 32bit dev box, if it's even possible?
You do not need to run a 64-bit development machine to create a 64-bit MSI file.
What makes an MSI file "64-bit" is simply that the "Template Summary" field in the Summary Information Stream is set to "AMD64;1033" (one possible example) instead of "Intel;1033".
This MSDN article might provide you more information.
AFAIK the Wix tools set is agnostic to platform, you need to install the x64 version, and you need to use the proper flags inside the setup (there are various of places you need to be explicit about x64, more info here).
Does a 64-bit CruiseControl.NET exist or do I need to install the 32-bit version? Our CI server is Server2003 64-bit. Currently I have been testing on WinXP Pro and no problems.
If I do need to run cc.net 32-bit on a 64-bit OS, what issues should I expect to encounter? This post mentions a couple, Running 32-bit ASP.NEt 3.5 apps in Windows 2003 64-bit . I would also need to have the .NET 2.0 and 3.5 framework installed. Do I install the 32-bit versions if running cc.net 32-bit? Can 32-bit and 64-bit coexist on the same server?
A quick peek at the source code reveals that CruiseControl.NET is compiled with "Any CPU" platform, so it will (and does) run on either a 32 or 64 bit runtime.
My notebook runs 64 bit O/S and has no problems with CruiseControl.NET server or web dashboard (IIS 7). Just install it as per normal and you should be fine.
Personally I'd be really worried if it needed > 3GB of memory :)
It shouldn't be anything you need to worry about. Cruise control just launches the build, subsequent steps such as compilation can be 64-bit.
I don't think there's much benefit from making CruiseControl 64-bit at the moment. I'm running CruiseControl without issues on a 64-bit machine. The setup was not much different, other than the folder which it was installed into (Program files (x86)).
Generally speaking, all 32bit applications will work on a 64bit OS. I have been doing this with my webapps for some time. You will encounter issues only if you are trying to reference assemblies across the bit boundary, ie. 64bit assembly from 32bit application.
You should be already to run CC on 32bit mode on 64bit OS.
There are no seperate version of CruiseControl for 64-bit. But but you may run into an ASP.NET error if working with Win. Server 2008 and IIS7.
Workaround:
"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe" -i
and
"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe" -i "W3SVC/1/ROOT/ccnet"
NOTE: it is using Framework64 as this would not work for 32-bit.