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.
Related
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/
Summary: The pkg-bootstrap.jar and related files are missing from the latest GlassFish 4.1.2 and this prevents the updatetool from running. What is the proper way to install and run updatetool on Windows 10?
Detail: I was working with the Java EE 7 tutorial and downloaded the Java EE 7 SDK Update 3 (not Web Profile) which is based on GlassFish Open Source Edition 4.1.2. I ran into a problem running the updatetool on Windows 10. When run, it gives the option to install itself but the installation fails. It looks like the update tool uses the pkg tool, and that uses a pkg-bootstrap to install itself the first time. However, this is no longer included in GlassFish 4.1.2. When the updatetool is run, it produces the following errors:
C:\glassfish4\bin>updatetool
The software needed for this command (updatetool) is not installed.
If you choose to install Update Tool, your system will be automatically
configured to periodically check for software updates. If you would like
to configure the tool to not check for updates, you can override the
default behavior via the tool's Preferences facility.
When this tool interacts with package repositories, some system information
such as your system's IP address and operating system type and version
is sent to the repository server. For more information please see:
http://wikis.oracle.com/display/updatecenter/UsageMetricsUC2
Once installation is complete you may re-run this command.
Would you like to install Update Tool now (y/n): y
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar" refresh
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar" "C:\Users\[userid]\AppData\Local\Temp\pkg-bootstrap21687.props"
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar
C:\glassfish4\bin\pkg does not exist in either the latest Java EE 7 SDK Update 3 or the latest GlassFish 4.1.2. Some research on the nightly builds shows that the directory trees glassfish4/.org.opensolaris,pkg and glassfish4/pkg were removed between builds glassfish-4.1.2-b03-02_25_2017 and glassfish-4.1.2-b03-03_07_2017. I can't find anything that explains why they were removed or an alternate way to install the updatetool. My work around was to copy the two trees from glassfish-4.1.2-b03-02_25_2017 into c:\glassfish4 (from the Java EE 7 SDK Update 3) and that seems to work. But, I figure that if this was removed, there was a good reason for it, and I shouldn't be hacking it.
If there was a separate installation step for the package tool, I missed it. What is the proper way to get the updatetool to run on GlassFish 4.1.2?
I have jdk1.8.0_121 and jre1.8.0_121.
Thanks for your help.
I had the same problem as DevDevDev.
I went to the link in his post:
http://download.oracle.com/glassfish/4.1.2/nightly/index.html
Downloaded the archive:
glassfish-4.1.2-b03-02_25_2017
http://download.oracle.com/glassfish/4.1.2/nightly/glassfish-4.1.2-b03-02_25_2017.zip
Extracted the missing folders into my glassfish directory:
/glassfish4/pkg
/glassfish4/.org.opensolaris,pkg
As DevDevDev I have questions about why it was removed but it works for me...for now.... Hope it helps someone else. Thank you DevDevDev I would not have solved this without your post!
I was working with Java SE. Then I needed to work with JAX-WS, so I went into the same website as you.
Basically, it says that you have to:
Download the package (a compressed file with a folder called glassfish4)
Unzip the downloaded file (does not specify where)
voilá
It did not work for me, so I kept searching and I found this: https://forums.netbeans.org/post-91328.html
You just need to download this update from netbeans plugin Manager:
"Java EE Base"
Good luck!
I got the same problem too. It seems that glassfish 4.1 did not integrate the Update Tool, so as doc of oracle suggests, we'd better install SDK 6(glassfish 3). Here is Java EE 6 SDK Update 3, note that the version provided here is with JDK 7. If you already installed JDK in your windows 10, you may ignore it.
When you finish downloading the .exe file, you should not install SDK by double-click the .exe file. Instead, you should run below command:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j [JRE-Home]
note, command here is the name of your .exe file and it needs console arg of JRE Home, mine command is as below:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j D:\JDK\jre
It seems that unzipping the file using Windows explorer's zip support doesn't work properly. If you instead do as described in the README and run:
jar xvf glassfish-4.1.zip
The archive is extracted properly and all the needed pkg files are there.
What files do you need? I had the save problem I was looking for the files of tutorial. Finally I found them here: ..../glassfish4/docs/javaee-tutorial/
I'm using the trial version of Mule Standalone EE server (checked the error message). I can run my project within Anypoint Studio, but when I deploy to Mule Standalone, it fails with the error - Invalid content was found starting with element 'data-mapper:config'
Anyone has any idea on this error?
I believe even I use Tomcat server, I would end up with same error or would it be using any other run time.
The Datamapper is not included in 3.7 anymore. So if you use it you must use the latest 3.6 runtime.
But still when deploying through Anypoint Studio, it should still work normally.
It says in 3.7 datamapper was replaced by another enterprise feature called DataWeave.
As per this reference :- http://forum.mulesoft.org/mulesoft/topics/developing-applications-using-mule-soft-community-ide-and-enterprise-ide-and-deploying-in-community-standalone-and-enterprise-standalone
also here :- https://developer.mulesoft.com/docs/display/EARLYACCESS/Including+the+DataMapper+Plugin
Thanks Anirban for the response. Found the resolution in second link you provided.
However the second link informs us to download the plugin zip, which I couldnt' find anywhere.
Instead, I searched in the Anypoint studio files and found data-mapper-plugin folder which I copied to MuleServer\Plugins location. And it worked.
I have a problem when deploying my Worklight project on the server . It shows the following Error Message :
FWLSE3041E: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans.
and when I tried to preview my application it showed this message :
SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:420'
I had the same issue using Worklight 6.2 CLI, but recreating the project did not work.
One issue that I had was that worklight did not build a .war-file properly, so I copied the .war-file from a backup.
Edit: This happens regularly in our project now, and we have no idea why. We fix it by invoking any procedure, which makes it work until you restart the server. Worklight must be building something when invoking a procedure that it does not do when building.
I Solved The problem by creating a new Worklight Project and copied all my files , it works just fine :) I used Worklight 6.1 instead of 6.2
I solved this by fixing a recently created security test in
server/conf/authenticationConfig.xml
The problem was I mispelled the Realm name I previously defined.
I solved this problem by deleting the application from the worklight server and rebuild it.
Delete WorklightServerConfig folder in workspace and rebuild your application.
I was able to fix this in MobileFirst 7.0 (Fka Worklight) by opening the Servers view, Window -> Show View -> Servers. Then expanding the MobileFirst Development Server and right click on the project in question, chose delete.
Once you do that go back to the applications' directory in the "apps" directory and right click -> Run As -> Run On MobileFirst Development Server
This should rebuild and deploy the project on the server.
I solved the problem by using ibm jdk not open jdk. My solution is to make sure the env parameters are correct
export JAVA_HOME = $your_ibm_jdk
export PATH + $your_ibm_jdk/bin:$PATH
run java -version to make sure the setting work
I want to upgrade Glassfish without internet connection. But I have already downloaded the latest version.
I have done the following steps,
For eg. galssfish-3.0 is the older version and glassfish-3.1 is the newer version.
Step: 1
I just copied the glassfish-3.0/glassfish/domains/domain1 and pasted in glassfish-3.1/glassfish/domains
Step: 2
In glassfish-3.1/bin ./asadmin i just give the command asadmin> start-domain --upgrade
then i checked the version asadmin> version the ouput was
Version = GlassFish Server Open Source Edition 3.1.1 (build 12)
Command version executed successfully.
Is this correct or I need to follow some other ways to achieve this? If wrong Please guide me the right way.
Can anyone help me?
Thanks in advance,
Gnik
Regarding the Oracle GlassFish Server 3.1 Upgrade Guide you did it right.
There are some hints in this guide for the migration of deployed applications:
Application archives (EAR files) and component archives (JAR, WAR, and
RAR files) that are deployed in the source server do not require any
modification to run on Oracle GlassFish Server 3.1. Components that
may have incompatibilities are deployed on GlassFish Server 3.1 with
the compatibility property set to v2 and will run without change on
GlassFish Server 3.1. You may, however, want to consider modifying the
applications to conform to Java EE 6 requirements.
...
Applications and components that are deployed in the source server are
deployed on the target server during the upgrade. Applications that do
not deploy successfully on the target server must be deployed manually
on the target server by the user.
If a domain contains information about a deployed application and the
installed application components do not agree with the configuration
information, the configuration is migrated unchanged, without any
attempt to reconfigure the incorrect configurations.
You should read through the guide carefully and check your deployed applications for any errors / exceptions during server startup or manual redeployment.
Some time ago I made an update as described in the update guide from 3.0 to 3.1.1 and cannot remember any bigger problems.