I've been looking for information about this, but I don't find anything. I think there's no version available at Oracle site for installing Weblogic 12.2.1.X on Apple M1 devices, but maybe it's possible to do it using Rosetta 2.
Has somebody tried it? I cannot because I don't have an M1 device yet, but I'm wondering because I still develop soft that runs on Weblogic.
I could, but i had to add an argument -ignoreSysPrereqs (for example java -jar fmw_12.2.1.3.0_wls.jar -ignoreSysPrereqs), because throwed me a error
The error:
Checking if CPU speed is above 300 MHz. Actual unknown. Failed <<<<
I used this documentation:
https://community.oracle.com/tech/apps-infra/discussion/3888969/veridata-installation-checking-cpu-speed-failed
I currently use different versions (10.3.6,..)
I just copy the folder installed in an old mac with intel, an then they work 99%, was necessary fix the folders resource like java.
But just realize have an issue on ServiceConnector, for remote calls ..
Related
We’ve been trying to get SikuliX 2.0.5 to run on a RHEL 8 system, and not having much luck.
We went through the instructions on this webpage:
https://sikulix-2014.readthedocs.io/en/latest/newslinux.html#newslinux
We started on RHEL 7, but the OpenCV shared library required a newer version of GLIBC than is standard on RHEL 7 (version ‘GLIBC_2.27’ not found (required by ~/.Sikulix/SikuliLibs/libopencv_java430.so)), so we moved up to RHEL 8. We had to build OpenCV (v4.3.0) from source because we could not find a java companion package for RHEL 8, which required quite a few other dependencies, but in the end we got it built with most options enabled, and installed as root on the system. We also got Tesseract installed via a package, as well as xdotool and wmctrl.
We are setting LD_LIBRARY_PATH to ensure that the OpenCV libs are picked up, and when we run with the “-v -c” options to the IDE, there are no obvious problems reported. It seems to believe it is moving the mouse, though we can see that it is not, and when we try to capture a screenshot, the “canvas” from which to capture is either uninitialized/garbage frame buffer memory, or a totally black screen. On rare occasions we have seen the actual desktop, but most times we do not.
Originally the system had 2 monitors, but was subsequently reconfigured to a single display system. We were originally running remotely over NoMachine, but have also tried running locally and observed no difference in behavior.
Any pointers or suggestions would be most welcome. Given that no error messages are being reported, we are out of ideas for how to proceed in debugging the problem. It appears that more native support is provided for Debian-based systems, but we’re attempting to validate a product which only advertises support for RHEL systems, so we’d prefer to get it working in this environment if at all possible.
Have multiple versions of Fabric runtimes on local machine (8.1, 8.2, and 9.0 series) which can be listed with:
Get-ServiceFabricRuntimeSupportedVersion
Have combed the Fabric documentation + web for anything about switching (changing) the SDK or Runtime version (effectively rolling back to an earlier installed version not the latest). Nothing. Anybody got an answer. Stopped investigating after trying:
Connect-ServiceFabricCluster
Unregister-ServiceFabricClusterPackage -Code -CodePackageVersion "9.0.1017.9590"
to back out version until I got to the one I want (8.2.1235.9590). But that fail with:
Fabric version has not been registered
Assuming this concerns only the current Powershell context. Start-ServiceFabricClusterRollback flops just like Unregister-ServiceFabricClusterPackage.
This might be very unhelpful, but I think the Supported Runtime Version is just which runtimes does the PS scripts support, not something about the local cluster.
The runtime you have installed is the latest one, so if you want to use an old one you have to uninstall the latest and find the bits for the old runtime and install that.
I am however, not entirely certain! It might be possible to switch runtimes, though it seems unlikely.
From the Control Panel choose Uninstall Programs and removed Fabric (6.0 SDK and Runtime). Restarted Windows (PC). Unclear if a restart is really necessary. Then opened the Web Platform Installer and through Spotlight searched for Fabric to click on Add. That put back 4.2.1235 of the SDK I needed. Done.
I have bought, downloaded and then installed uFlex for Unity. The install seemed to go without any errors, but when I try to run any of the example scenes I get lots of errors. The first and most serious sounding of which is:
DllNotFoundException: flexRelease_x64
uFlex.FlexSolver.Start () (at Assets/uFlex/Scripts/Solver/FlexSolver.cs:102)
Also the scenes don't seem to run/work. Have tried googling to see if it's a common error but that didn't show up anything. Tried finding the missing DLL but not sure where to put it, or whether it's platform/version specific?
Any thoughts on how to troubleshoot this
Anyone else have similar issues?
Not sure if it's relevant but I'm running Unity Version 2017.2.ob11 Personal, and my OS is Ubuntu 16.04.5 LTS. I have windows installed as well - is switching to running Unity under Windows likely to help?
It won't and shouldn't work on Linux at this point.
Read the requirement from the plugin page:
NVidia GPU with at least CUDA 3.0 compute capability
Windows 64 bit (Win 32bit experimental, Android and Linux support planned)
The support is currently for Windows. You get the exception because the dll for Linux has not been provided. It can't load Windows dll on Linux. If the native side (C++) of the plugin is open-source, you can compile it for Linux and include it in your project then it should work. Since it's not, your only option at this moment is to switch to Windows.
i'm trying to install OS through a network interface. also i'm launching console and mounting the shape. Then i'm doing all steps, but finally i see the message "ReferenceError:Land is not defined busy.htm:343"
Installation was tested on different images of systems.
Maybe somebody faced with the problem and can help?
Got same error. HP support says install directly from the ISO not using Intelligent Provisioning. The error may go away with multiple re-tries, or by updating the Intelligent Provisioning version.
I have a very strange issue that I'm hoping someone can help me with. I have various installations of Eclipse on my development machine at work. The one I primarily use is Weblogic WorkSpace Studio 10.2. This installation, along with a few Pulse installations I have set up works fine when I'm logged into my computer physically.
However, when I try to log into the computer using Microsoft's Remote Desktop Connection utility I get an error stating: "Could not create Java virtual machine." and then I get the lovely Eclipse error box which I personally can gather almost nothing from.
Even if you don't have the solution, any help would be greatly appreciated.
Justin
What ended up working for me was the memory settings for the JVM. Apparently the remote desktop connection, or some other setting in Windows, blocks off a fairly large amount of space. By reducing the heap size allocation for the JVM during Eclipse and server start-up I was able to get this working. As a side note, I had PLENTY of space that windows could have used, so I don't think blankly adding more memory would necessarily solve the issue. If you find another solution, please let me know.
• We came across an issue when user RDC’s to a remote system where the OS is Windows 10 and has a running Eclipse instance, the Eclipse instance terminates
• Eclipse is one of the IDE’s for Java
• The issue is because of Windows 10 Exploit protection
• Pre-requisite: You will need Administrative permissions for executing the below
• Navigate to Settings -> Update & Security -> Windows Security -> App & Browser Control -> Exploit Protection Settings
• Add the program to exclude as below
P.s. As of Window 10 1909 MS security advisory mentions we can disable some exploit protections by default.
Perhaps it is permission related. take a look at similar issue that symantec has:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8ea1593f1d1fcee68025759a003d8403?OpenDocument
Try to see if you have same patches installed that causes the security issue. Also refer to application log to see if there is a more specific error. Good luck :)
I think issue happens due to Windows, not Eclipse nor JVM. There is still open Bug report on the Eclipse side and one of the comments state that Microsoft is working on the issue.
I have tried Windows Remote Desktop-ing into my dev machine at work (which had only one version of eclipse installed on it). I had no troubles.
Is it possible that your problems stem from multiple versions of eclipse running at the same time?
Also, have you tried a fresh install of eclipse on your dev machine?
If the above two suggestions don't work, then the only thing that I can think of is what Mohammad said: you might need to check your permissions.
I would check the system log if I were you: Start > run > eventvwr
The first thing to look at is the .log file which is in your eclipse's metadata folder (found in your workspace at $WORKSPACE_ROOT/.metadata/.log). If you post the stack trace that it generates upon initialization, we can give a definitive answer.
I am now experiencing this in Eclipse (the Oxygen release and Java 1.8.0_181). I previously had the same problem with another Java-based program (Oxygen XML/XSL editor - the product name is coincidentally the same as the Eclipse version). Last year the Oxygen support team answered that it may be a known problem in Java.
Even without seeing a crash report, considering your sequence of
events, this seems like a known common cause of crash for the Java
runtime. Keeping Oxygen/Java running for a long time, until the screen
or video card enters sleep then connecting/disconnecting
screens/projectors or connecting/disconnecting RDP can trigger a crash
in the Java runtime. We keep updating the Java runtime (JRE) with each
new version of Oxygen, but so far the issue has not been resolved in
newer versions of the JRE.
e.g. Java VM logged issue:
https://bugs.openjdk.java.net/browse/JDK-8153389