I am new to Mule and was following the official tutorial in using the Anypoint Studio. I was trying to test the connection of a database connector when I found that there was an issue with the tooling instance, in which the following message was given.
I went to check the status of the tooling instance, and it was not started. Then I tried to restart the tooling instance, but it failed as shown below.
Below is the corresponding error message (in Workspace/.metadata/.log). Kindly see if there are any insights, thanks.
!ENTRY org.mule.tooling.core 4 0 2018-05-16 15:23:25.104 !MESSAGE
There was an error initializing tooling instance !STACK 0
org.mule.tooling.runtime.controller.MuleControllerException: Timeout
while starting mule instance at
org.mule.tooling.runtime.controller.MuleController.start(MuleController.java:143)
at
org.mule.tooling.client.startup.ToolingManager.restart(ToolingManager.java:154)
at
org.mule.tooling.client.ui.preferences.ToolingClientPreferencesPage$1.run(ToolingClientPreferencesPage.java:127)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Caused
by: org.awaitility.core.ConditionTimeoutException: Condition with
lambda expression in
org.mule.tooling.runtime.controller.MuleController was not fulfilled
within 90 seconds. at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:785)
at
org.mule.tooling.runtime.controller.MuleController.start(MuleController.java:127)
... 3 more
[Environment information]
Platform: macOS 10.13.4
AnyPoint Studio version: 7.1.2
Mule runtime version: 4.1.1 EE
JDK version: 1.8.0_172
Port 3306 outbound connection is open
I had same issue in my MacOS and resolved it by following the below steps
goto Preferences -> Anypoint Studio -> Tooling
Click here to see Tooling screen shot
Click Check status button (can be found under Life cycle)
if you don't see "Tooling instance is running) then try restart instance or restart your Anypoint studio.
if you keep experience this issue on your current project, try opening another project.
For me, the moment I tried in another project (follows all above 3 steps) , I was a able to test connection successfully.
Change the build path from JRE to JDK that will solve this issue.
This video will help you to set the build path.
https://www.youtube.com/watch?v=S5xeXawYgK0
I resorted to using the previous version (Anypoint Studio 6.4 with Mule 3.9) and there is no issue making a DB connection. In fact there isn't even a section in "Preference" which is about "Tooling" under "Anypoint Studio". Maybe there is some issue with Anypoint Studio 7.1.
Nevertheless, falling back with the previous version should be one of the solutions.
Relevant discussion in Mulesoft Forum:
https://forums.mulesoft.com/questions/94528/error-initializing-tooling-instance-in-mule-anypoi-1.html
This tooling was introduced in/from Anypoint Studio version 7.1.+ , Earlier versions do not have this feature at all. Initially I had similar issue and banged my head for several days with the same problem.
If you are setting environment variables, Makesure to restart the machine to take effect.
I use multiple versions of Anypoint Studio, instead-of Environment variables I prefer adding the Java path in (INI) file under the Studio root directory and all versions work me with no issues. However, Mulesoft support says not to touch the INI files. ( which I ignore it )
Keep this in mind, if the path is too long in the environment variables, Studio may not pick up java path from it and tooling in studio seems to be creating issues. So make sure it is mentioned at the beginning of the path.
Hey no above solutions worked for me.
But what I am going to share did work for me.
Check your MAVEN_HOME path which should be set to "C:\Program Files\Apache\maven"
Check your JAVA_HOME path which should be set to "C:\Program Files\Java\jdk1.8.0_172"
Check your "PATH" in system variables which should kept the "C:\Program Files\Java\jdk1.8.0_172\bin" and at FIRST PLACE like C:\Program Files\Java\jdk1.8.0_172\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;. .. . .
In Anypoint studio, windows->Preference->Java->installed JRE and change path to "C:\Program Files\Java\jdk1.8.0_172".
Update anypoint studio from check for updates.
Restart the anypoint studio and it will work.
Note mentioned path could be different for you and Java path is of JDK not for JRE.
So I had the same issue and got it resolved.!
Two steps as following
Before extracting the Anypoint studio zip file I renamed the zip file to a shorter name.
While extracting the zip file, I extracted inside C:/ folder.
It works like a charm.
Followed the below SOLUTION II from Mulesoft support and it worked for me. I was able to connect using MySQL after this step.
https://support.mulesoft.com/s/article/Anypoint-Studio-7-1-3-error-tooling-not-available-exception
SOLUTION II Editing the anypoint studio .ini, changing the line: -Dorg.mule.tooling.runtime.args=-XX:-UseBiasedLocking by appending ",-Dtools.jar=\lib\tools.jar"
Below are the solutions:
First, You have to set manually your proxy configuration(if there is a proxy) in Anypoint Studio:
On the Anypoint Studio menu select “Window –> Preferences”
choose “Network Connections”.
Select “Manual” from Action Provider drop-down list
Select the schema in the List and click the “Edit” button
Fill in the proxy server host and port number, (fill in the username and password if any)
Even after the above step, if the issue is not fixed, check your JDK and Mule compatibility(https://help.mulesoft.com/s/article/Anypoint-Platform-support-for-Oracle-Java-SE-8). After checking do the JDK path setting in Environment variable/Eclipse.ini.
Restart your machine and try to launch your Anypoint Studio.
If the issue is not fixed, then navigate to the Installation location of AnyPoint and then the configuration folder.
Open config.ini and crosscheck whether “eclipse.application” is empty or not.
If it is empty ,then assign “org.eclipse.ui.ide.workbench” as value.
The above steps will fix the null issues while launching the AnypointStudio.
you can also refer below link: https://skolaparthi.com/mulesofterror/
I'm a beginner in RavenDB, but I can't seem to get started. I'm getting stuck at loading an entity in C#.
I am getting a null exception error.
Below is my screenshot for the exception:
And in my RavenDB studio, it looks like this:
So, I'm totally stuck now.
I am very sure i have done everything else right.
The client has connected to the server with correct Url, the DefaultDatabase is correct, and the session.Load parameter is correct id
Hope someone can help :-)
Make sure that versions of server package and client nuget match. In your code, you use Url and DefaultDatabase for DocumentStore, both of which were changed a long time ago (May 2017) to Urls and Database.
It is very likely that you use an outdated client package. Install the client package for matching version of RavenDB using Package Manager Console in Visual Studio using a command like this:
Install-Package RavenDB.Client -Version 4.0.0-nightly-20180123-0500 -Source https://www.myget.org/F/ravendb/api/v3/index.json
This command is for the latest nightly version, you want to use -Version matching the server you are running.
Find the appropriate version here: https://ravendb.net/download
I'm struggling to get the default logging working for a deployed application.
From my understanding, for a Mule app that contains no log4j.properties/xml file the Mule server will generate a log file named (going by the wrapper.conf file) %MULE_BASE%/logs/%MULE_APP%.log.
This isn't happening, instead all the logging is going into mule_ee.log, no app log file is created.
Are there any settings I should be looking at to make this happen?
Thanks in advance.
This is a known issue in 3.5.0 in windows platform, see this. In the next few days 3.5.1 will be released and you can upgrade.
I'm starting out with mule and I noticed that the mflow files tend to get rather large and even if you use the visual view in Mule Studio it's hard to take it all in. I read somewhere that you could put each flow in a different file and then all the flows get deployed together and can call each other.
The problem now is I created my own custom transformer that I want to use in two different flows. But if I declare a global custom transformer in each file I get an error saying that the name already exists.
So now I tried and placed the custom transformer in its own mflow file and it works in runtime but the problem is Mule Studio doesn't seem to understand it at "compile time" and my mflow files are riddled with errors stating "Reference to unknown global element". How can I import global elements from one mflow file to another so that Mule Studio stops complaining.
Maybe this isn't the correct way to do it at all. If so I'd be happy to know how to achieve my goal in any other way.
Thanks in advance
This was a known issue with Studio whereby it doesn't recognise global elements in other config files but still runs the application fine: https://www.mulesoft.org/jira/browse/STUDIO-1881
This should be fixed in version 3.4 of Studio. What version of Studio are you using?
And yes, centralising reusable config elements is a common approach. More info on sustainable development with Mule here: http://www.mulesoft.org/documentation/display/current/Team+Development+with+Mule
Global Elements are accessible among all the mule flows, since Mule Studio 3.4
I'm a newbie to Worklight. I have imported module 6.1 from the developerWorks getting started with Worklight sample http://www.ibm.com/developerworks/mobile/worklight/getting-started/
I am getting the error in the error as configured in the javascript
"Can't get cities list. Check database connection"
Does anyone know how to troubleshoot? The connection parameters in "SQLAdapter.xml" are very straight forward.
For the Worklight MySQL adapter request to reach the MySQL database, you need to add the mysql-connector-java-5.1.23-bin.jar to your project.
You can download the MySQL Connector/J file via this URL: http://dev.mysql.com/downloads/connector/j/
Choose "platform Independent" in the dropdown, and click the Download button for the .zip option.
Uncompress the .zip file and copy the mysql-connector-java-5.1.23-bin.jar to yourProject\server\lib.
Got it working. Seems there was a problem with my Eclipse install, or Java on Windows. So I switched back to causing my Eclipse and Java installed on IOS and all is working. Also, the IBM documentation was unclear, but now that I am using mysql-connector-java-5.1.23-bin.jar in my Project\server\lib folder.