There is a requirement to generate thread and heap dumps of running Java process on a Window server. We have JDK 7 on the server, but the Java process runs using java in JRE 8. Installing JDK 8 on the server takes time due to lots of paperwork required for it (company process). The team who will be doing it insists that they need JDK 8 from Azul to generate the dumps since current java process uses Zulu JRE 8. For reasons known only to them, they do not even want to try with the tools available with JDK 7 (OpenJDK?) installed on the server. Does these versions really matter?
Question: Can I use JDK tools from any version, specifically JDK 7, to generate heap and thread dumps of the java process running from a Zulu JRE 8 environment?
The answer appears to be yes.
I just tried this on my Mac and could generate a thread dump and heap dump using the Zulu 7 version of jstack and jmap on a running instance of Zulu 8. This would indicate that jstack/jmap are not troubled by the version number of the JVM (and also seem compatible).
Certainly, from a licensing perspective, there is no issue with using tools from a Zulu 7 build on other versions of Zulu (like 8).
Related
I got only a short warning during build in VS2010
the helper process was unable to initialize due to an unknown error
We use incredibuild 5.0 on Windows 7 and windows 10 helper machines. The coordinator is running under Win10.
Also on the warning window there was an line about .net framework is not compatible. On every machine 4.0 and 4.6.1 .net framework has installed, so no sense... but somehow the only one helper could assign to build which is running windows 7. Any idea what should I try?
coordinator window
warnings
Windows 10 was release long after IncrediBuild version 5.0
Once Windows 10 was released, a new version of IncrediBuild was which certifies the Win10 OS. Once you'll upgrade to the latest IncrediBuild version (which currently certifies the latest Windows updates), your problem will go away :)
Disclaimer: the writer of this message works at IncrediBuild.
I am trying to install SQL Server 2008 Enterprise Edition on Windows Server 2008. I have done all the process till the Installation correctly. However, the installer displays the message "Managed SQL Server Installer has stopped working".
No online Solution has been provided yet....
Anyone sorted this problem before?
This is usually a problem with your installation of .NET framework. E.g:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/34671131-a095-4068-b4d8-ab5ef6f5b8cc/managed-sql-server-installer-has-stopped-working
Check that your installations are all in working order by using the tools on this site:
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
You may have to re-install any or all of your .NET framework versions.
Instead of trying several methods that have not been approved, it is better to repair the MSSQL Server installation. On the other hand, there is some other issues that can be encountered during the repair process i.e. Installing the .NET Framework 3.5 on Windows 8, Windows 8.1 and Windows 10 as shown below.
In this case, if you have trouble during .NET Framework installation, you can install it by following the steps below (requires Windows 8, 8.1 or 10) setup disc or ISO file):
1) First you'll need to copy Windows 8 setup files to your hard disk. If you have Windows 8 setup ISO copied in your system, you can mount it by right-click on it and select "Mount" option or you can extract its content using 7-Zip.
If you have Windows 8 setup disc and don't want to copy its content, its ok. Just insert the disc in your CD/DVD drive so that Windows can access its content.
2) Now open Command Prompt as Administrator as mentioned here and then provide following command:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:F:\sources\sxs /LimitAccess
Here "F:" represents the CD/DVD drive letter in your system which contains Windows 8 setup disc. Replace it with the correct drive letter according to your system.
If you extracted Windows 8 setup files in a directory, replace F:\sources\sxs with the correct path.
3) As soon as you execute the above mentioned command, Windows will start installing .NET Framework 3.5 in your system and it'll not require Internet connection.
It'll take a few minutes and you'll get a message that the operation completed successfully.
4) That's it. Now you have installed .NET Framework 3.5 in Windows 8 without using Internet connection.
For more information have a look at How to Install Microsoft .NET Framework 3.5 Offline in Windows 8 and Later without Internet Connection?. Hope this helps...
The download page does not have a Windows build for the most recent version - 2.0.1. There is a windows 64 bits installation for the version 2.0.0.
I was wondering about the reasons of not supporting Windows 32 bits since 2.0.0 and Windows at all since 2.0.1.
Is it that they do not provide the binaries, but one could still build it for Windows 32 bits using the build instructions ?
Or there is a deeper reason, like using an API unavailable for Windows 32 bits (2.0.0) or unavailable for Windows at all (2.0.1) ?
I am asking because I am considering building it on Windows, both 32 and 64 bits, but would like to be sure the effort is not doomed to failure from the start.
we are well aware of the situation. The plan is to release 2.0.1 for 64 bits as soon as possible. We're having some delays for our Windows builds and want to make sure the quality is as high as possible. So expect a 2.0.1 64bit soon.
That said, I don't think that we'll have production ready versions of 2.0.x 32bit. What we are currently working on is a 32bit build that people can use to develop against, but is not recommended to use in production (similar to our Mac OS X builds).
I can't give you a specific timeline, but I think we're talking about "weeks". If you want to get direct feedback from one of the developers, please get in touch with Trond Norbye over twitter (#trondn).
Does this answer your question?
I have the following strange situation here I need some help with:
I am building a Qt application with MySQL access. For this I have:
- a dedicated building machine, using Qt 2010.05 and a MySQL 5.1 just for the libraries, Windows 7 32 bit. This machine creates the install package.
- a dedicated development machine, CentOS 5.5
- two testing machines:
- - an "always" fresh install of Windows 7
- - another Windows 7 machine with a newer Qt on it used for other stuff too.
I have built the previous version of the application sometime in February this year (on the bilding machine), it works nicely and perfectly, loads the MySQL driver (I have put it in the sqldrivers directory as indicated by everyone else). The install package installs, works everywhere (at least on all my Windows machines).
Now, I have built another release of the application, on the same machine. In the install package the only important difference is the executable (and some HTML files, but those are not relevant). Everything else is the same. When I run the NEW executable on the build machine I get ("QSQLITE", "QMYSQL3", "QMYSQL", "QODBC3", "QODBC") as the QSqlDatabase::drivers() output. If I run the NEW exectuable on any other machine I get an empty list of drivers. If I run the OLD package on any machine it works...
The loaded modules by the two processess (old executable, new executable) are basically the same, except is the qtmysql DLL which gets loaded in the old one and not in the new.
Have you ever encountered a situation like this? If yes do you have a feasible solution for it?
Thanks,
f.
Qt will only load plugins which are compatible with the program or version of Qt used. See the Deploying Plugins document.
You could also try using QPluginLoader to manually load a plugin and check what is reported as the QPluginLoader::errorString when it doesn't load (add the error message to your question if you can't fix it still).
Can MySQL 5.4 beta be compiled for 32-bit processors under Linux?
The current beta only has binaries for some 64-bit versions, but if you're keen on starting to beta test right now you should be able to compile from the sources on a 32-bit systems. (It IS a beta, of course, so unreliability IS to be expected -- don't run it in production, whether on 32-bit or 64-bit systems!)
According to this blog it's only available for 64-bit machines.
http://willysr.blogspot.com/2009/04/mysql-54-preview.html
or here
First, the preview release of MySQL
5.4 only includes the InnoDB scalability fixes (addressing more
CPU's/cores). Second, it is limited to
the Solaris and Linux 64-bit platforms
at this time. The other features
mentioned in this article and
additional platform support will be
appearing very shortly, so be looking
for upcoming announcements soon.
http://74.125.93.132/search?q=cache:iLgUTcXAmGUJ:mirror.facebook.com/mysql/tech-resources/articles/mysql-54.html+mysql+5.4+64bit+only&cd=9&hl=en&ct=clnk&gl=us&client=firefox-a
google cache because that website is down
if you can run ./configure and make without any errors, it should work properly.