I am new to use Mulesoft and thus I have started learning it by following the steps in "https://docs.mulesoft.com/mule-user-guide/v/3.7/build-a-hello-world-application".
However, when I try to run the project by selecting "Run As > Mule Application", It gives me this error messages:
Launching a JVM...
JVM exited while loading the application.
Automatic JVM Restarts disabled. Shutting down.
backend pipe closed.
backend pipe closed.
<-- Wrapper Stopped
Note that: I am using Windows 7 (64 bit), Mulesoft 7.1 (64 bit), jdk1.8.0_171 (64 bit) and I have added java home into system variable as instructed in this post "https://forums.mulesoft.com/questions/90429/unable-to-install-mule-4-anypoint-studio-71.html"
Any suggestion, please !!!
See image and check your Run configuration I have post image under bellow url...
Related
I am working on Windows 10 with Windows Mixed Reality Runtime and Hololens 2 emulator to run the hello_xr test . I was able to build the project using Visual Studio 19 and run it from command prompt as follows
hello_xr.exe -g D3D12 -ff Hmd -vc Stereo -bm Opaque -s Local
This is unable to get system and throws the following error although Hololens 2 emulator has been launched prior to running the above command
[16:09:52.495][Info ] Press any key to shutdown...
[16:09:52.586][Info ] Available Layers: (0)
[16:09:52.616][Info ] Instance RuntimeName=Windows Mixed Reality Runtime RuntimeVersion=112.2211.2002
[16:09:52.623][Error ] XrResult failure [XR_ERROR_FORM_FACTOR_UNAVAILABLE]
Origin: xrGetSystem(m_instance, &systemInfo, &m_systemId)
Source: ..\..\..\src\tests\hello_xr\openxr_program.cpp:298
Maybe I should launch the test from within Visual Studio using Hololens 2 emulator as debug target for this to work. But I am not sure how that can be achieved.
How do I go about debugging this? I just started with XR development.
This was solved in the Khronos forums.
Update (adding some context in case the link is unavailable later):
Instead of hololens emulator we can also use Windows Mixed Reality Portal or SteamVR to run the hello_xr sample. I used SteamVR along with an android phone. Steps followed were
Install SteamVR.
Change the active runtime from Windows Mixed Reality to SteamVR. The path to the manifest json file for SteamVR should be {drive}:\Program Files (x86)\Steam\steamapps\common\SteamVR\steamxr_win64.json . Registry editor can be updated to change the active runtime, details about runtime discovery can be found in the loader spec.
I'm trying to set up a remote debug properly. I have already set a remote debug and it works, but it not working on an application initialization stage, which means I can not see how a cache fills and so on.
My environment: Payara 4 (it is Glassfish) and IntelliJ IDEA Community Edition.
How to make a correct setup?
You can suspend the JVM on remote debugging by using suspend=y which make the JVM to wait until the remote debugger is attached.
So the debugger's JVM options will be as below
Java 5-8
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005
Java 9 and later
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005
Note: Adjust the port based on your settings.
I have an IoTEdge module which runs a deep learning model on a Raspberry Pi 3 and runs well but then somehow returns this error:
Error: Time:Mon Jan 28 22:45:21 2019 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:InitializeConnection Line:2230 mqtt_client timed out waiting for CONNACK
Is this a network connection issue? It seems afterwards, this error disappears. Not sure why this is the case. I thought there might be a communication error between this IoTEdge module and the IoTHub, so I even restarted the IoTEdge module and rebooted the Raspberry Pi device.
How can this be resolved? Does it have to deal with a time.sleep(1) code in Python?
You are using the original version of the Azure IoT Python SDK. This is a wrapper around the C SDK and the message you are encountering is a known bug in the C SDK. This has been fixed in the C SDK but was never propagated into the Python v1 reposiotry.
I suggest that you rebuild your Edge module using the new Python v2 SDK (https://github.com/Azure/azure-iot-sdk-python). By default, this is the version now used by the Visual Studio Cloud Azure Edge extension.
No information found for this. Is there any way to start weblogic in profiling mode? Or, maybe, it's activated by default?
Profiling action can be initiated 2 ways
1) Pass the profiling action while you execute the startWeblogic.sh. Following parameters can be appended
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8010
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
2) The same parameters can be appended from startup tab in weblogic server
Here's what i got. Mainly focused on remote profiling using NetBeans
generated remote profiling package for target OS and JVM architecture (32 or 64 bit) (Netbeans -> Profile -> Attach Profiler -> Change link, select OS and Java platform -> click "Create a remote profiling package" link)
copy this package to target machine
execute calibration script (calibrate.bat / calibrate.sh (chmod +x))
add specific argument to java_otps with path to this package
-agentpath:PathToProfilerPackage\lib\deployed\jdk16\windows-amd64\profilerinterface.dll=PathToProfilerPackage\lib,5140
restart weblogic. Startup will be interrupted until remote profiler connected
connect to a server using NetBeans profiler. Weblogic startup will continue.
However, i still can't download heap dump (which is available when attaching to local java.exe Weblogic process) but that's something.
I've created my mule application, and i deploy it on mule ce 5.3.0 my question now is how to keep my server running which means even if i close my CMD (the window where my mule is running) my application keep running.
See here: https://developer.mulesoft.com/docs/display/current/Starting+and+Stopping+Mule+ESB#StartingandStoppingMuleESB-StartingandStoppingMuleViatheCommandLine
Starting In the Background
Use the cd command to navigate to the $MULE_HOME/bin directory.
Run the startup script according to the options below.
Unix: ./mule start
Windows: mule.bat start
To further add on to what Ryan said, you can also install Mule as a service if you're running on Windows. From then you can also configure your Mule server to start up every time your machine boots up.
You can do so using the following command:
mule install