In apple jdk6 if we get default charset, it returns for example, gb2313,if we set system language to chinese. But openjdk returns utf-8.
How does JDK 6 get the map info from the encoding to the language?
Iam running the java app in a bundle,however, in IDEA, the jdk jvm returns utf-8.
Related
Using Firebird 2, we had to deploy 3 files with our applications to be able to connect to remote firebird servers:
fbclient.dll
msvcr80.dll
Microsoft.VC80.CRT.manifest
The first file was retrieved from the "normal" Firebird installer, the other 2 files from the "embedded" installer.
Firebird 4 doesn't provide an embedded installer, and I don't find proper information what to deploy for clients.
Reading this: https://ib-aid.com/download/docs/fb4migrationguide.html#_installing_client looks like Firebird 3 has lower demands. Is that the case? I just need communication-encryption and longer passwords, so FB3 would also be fine. (BTW, following the guide didn't bring success, otherwise I would not ask).
The minimum necessary files are listed in the document you link:
If we speak about installing Firebird client only, you need to have
fbclient.dll file. Firebird 4.0 client requires Microsoft Runtime C++
2017 with the same bitness as fbclient.dll. If Microsoft Runtime is
not installed, you may just copy it’s two files, msvcp140.dll and
vcruntime140.dll that are included in ZIP for Windows.
So the absolute minimum you need is fbclient.dll, and in some cases you may also need msvcp140.dll and vcruntime140.dll when those are not already installed on your system.
In addition, it is advisable to include firebird.msg for error messages, and for some use cases, adding the ICU files is advisable (if you use the functions of fbclient to render/parse WITH TIME ZONE types).
If you want wire compression, you'll also need zlib1.dll, and if you want to use Chacha wire encryption instead of the less secure ARC4, then you also need plugins/chacha.dll (the chacha.dll needs to be in a plugins folder relative to fbclient.dll).
All these libraries must be the same bitness as your application. As discussed in the comments, the problem seems to have been that you tried the 64-bit DLLs from a 64-bit Firebird installation, while your application was 32-bit.
If your application is 32-bit, then obtain the files from a 32-bit installation or zip kit, or look in the WOW64(*) folder of a 64-bit installation (from the installer, the 64-bit zip kit doesn't contain this directory). This WOW64 folder contains the 32-bit files fbclient.dll, msvcp140.dll and vcruntime140.dll (for the additional DLLs you need to use a 32-bit installer or zip kit).
* This follows the awkward Windows naming of 64-bit Windows having 64-bit files in %WINDIR%\System32, and 32-bit files in %WINDIR%\SysWOW64
I have a 64-bit Postgres server and 32-bit Windows applications. This worked perfectly until I upgraded Postgres from 12 to 13. The new server works well but applications raise an error authentication method 10 not supported on login.
I edited 13/data/pg_hba.conf, replaced the authentication method from scram-sha-256 to md5 in all entries, and restarted the server but the problem remained.
I think I need a new version of 32-bit libpq.dll but cannot find any newer than this from Postgres 10. Two questions. Will a newer version of libpq.dll solve the issue? And if so, where can I find it?
The problem is analogous to that described in PostgreSQL authentication method 10 not supported. An additional difficulty in my case was that I could not get the dlls from the server installation due to a 64-bit vs 32-bit incompatibility. I have just found a solution and post it that may be useful to others in the same situation.
Download the binaries for Postgres 10.17 Win x86-32 from this page. You can find the file libpq.dll in lib folder but it is not enough as it needs two other (new) libraries: libcrypto-1_1.dll and libssl-1_1.dll. Copy the libraries and make available to your 32-bit applications. These three libraries are necessary for proper login. The lib folder contains more libraries that your application may need.
Note that the authentication method scram-sha-256 is safer than md5 so it is no reason to replace it in the way described in the question.
I'm using ATG 9.1. how can I know which version of JDK must be used for different versions of ATG?
With JDK 6 I am able to work normally, whereas ACC is not working as it Requires a small version of JRE.
Why is that only ACC requires a small version of JRE and not other modules?
ATG/Oracle Commerce's required versions can be found on https://support.oracle.com -- you will need to log-in, and you may need access to be granted by an Oracle representative.
ATG 9.1 compatibility is covered in document "Oracle Art Technology Group (ATG) Commerce Supported Environments - Release 9.x (Doc ID 1342327.1)", which will link you to https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1342327.1&attachid=1342327.1:ATG9404&clickstream=yes
The 'compatibility matrix' shows the required JDK is "Sun 32-bit or 64-bit JDK 1.6.0_41" on all supported platforms (Windows, Solaris, RedHat) for JBoss and Weblogic application servers, but different for WebSphere.
The ACC can be run from within the app server, or in separate JVM. I don't know a reason why it would require a different JDK version.
Oracle usually suggest that this as a base version, so if a minor update to your application server requires a minor update to the JVM, you should probably follow your appserver's requirements.
I just installed GitHub for Windows on my 64-bit Windows 7 computer, and the GitHub always get the following two errors complaining about two components are 16-bit applications incompatible with the 64-bit Windows OS. The two error messages are attached below.
I think there should be many users running GitHub on 64-bit Windows, so could someone please provide some workaround for this issue?
1) The first error
Unsupported 16-Bit Application
The program or feature "\??\C:\Users\mikez\AppData\Local\GitHub\PortableGit_054f2e797ebafd44a30203088cd3d58663c627ef\bin\ssh-agent.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
2) The second error
Unsupported 16-Bit Application
The program or feature "\??\C:\Users\mikez\AppData\Local\GitHub\PortableGit_054f2e797ebafd44a30203088cd3d58663c627ef\bin\ssh-keygen.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
Give msysgit a try. I heard that this works fine.
I have just watched the bug report http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6972329 so I want to ask... Is there a JDK upgraded version which handles the problem? Because if I develop an app with 32-bit JDK 6 will it work on 64-bit linux?
I have compiled my project with jdk 1.6.0_05 so I am not sure will it work for 32 or 64 bit linux ... won't it be the user.home as '?'
Thanks
The bug has absolutely nothing to do with the JDK used to compile Java code - Java bytecode is completely platform independant. The bug only occurs when you run a Java app on a 32bit JVM on a 64bit Linux, and even then it seems to depend on a specific (and possibly faulty) LDAP configuration.