Module 4, Walkthrough 4-2, no option to configure with spring bean under global element properties

Hi all, thank you for looking into the issue.

I have solved my issue..

firstly i made sure the whole path of Anypointstudio.exe is as short as possible.. say C:\Any7\Anypointstudio.exe , i deleted the old works space completely and started new one.

I simply followed the procedure step to step for connecting to deby client..and it worked for me ( earlier for some reason it dint worked).

if any one facing the similar issue.. please shorten the path of the anypointstudio.exe and make sure java home and all point to JDK and the first element in the path is JDK..

Thanks.

also if possible can some one please guide me to the concept of tooling what it is and what will do.. i tried to search but dint found anything relatively ..

i have checked and made sure java path and all looks good and pointing to jdk 1.8

@gopale

i tried to check all.. when i clicked on check status it says running.. but when i clicked on Restart instance it giving the following error

 !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:150) at org.mule.tooling.client.startup.ToolingManager.restart(ToolingManager.java:154) at org.mule.tooling.client.ui.preferences.ToolingClientPreferencesPage$2.run(ToolingClientPreferencesPage.java:171) 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 120 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:134) ... 3 more
 
 !ENTRY org.mule.tooling.ui.contribution.munit 1 1 2019-04-15 15:34:26.025

i tried what every listed in the forums.. checked the jdk path, build path.. installed JRE..and also added tools.jar as an external jar .. still the same issue...

but when i checked the status of tooling service and it said running.. then i clicked on test connection for derby ( yes the derby jar was running at that time) . i used the JDBC driver (generic connection) and then configured with derbyclient-10.14.2.0.jar and i can see the following from the log

 aused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.InstallException: Config for app 'tooling-application-e6ef8ce0-5fbc-11e9-852a-146620524153' not found: mule-config.xml
 Caused by: org.mule.runtime.deployment.model.api.InstallException: Config for app 'tooling-application-e6ef8ce0-5fbc-11e9-852a-146620524153' not found: mule-config.xml
 ,additionalProperties={}]
     at org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException.newToolingServiceAPIException(ToolingServiceAPIException.java:82)
     at org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException.newToolingServiceAPIException(ToolingServiceAPIException.java:67)
     at org.mule.tooling.agent.rest.client.tooling.applications.Applications.put(Applications.java:99)
     at org.mule.tooling.agent.rest.client.RestAgentToolingService.lambda$deployApplication$3(RestAgentToolingService.java:167)
     at org.mule.tooling.agent.rest.client.service.ServiceFunction.serviceCallWrapper(ServiceFunction.java:27)
     at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:166)
     at org.mule.tooling.agent.RuntimeToolingService.deployApplication(RuntimeToolingService.java:92)
     at org.mule.tooling.client.internal.application.FileSystemArtifactDeployer.lambda$new$2(FileSystemArtifactDeployer.java:51)
     at org.mule.tooling.client.internal.application.FileSystemArtifactDeployer.doInternalDeploy(FileSystemArtifactDeployer.java:67)
     at org.mule.tooling.client.internal.application.AbstractArtifactDeployer.deploy(AbstractArtifactDeployer.java:52)
     at org.mule.tooling.client.internal.application.DefaultApplication.evaluateWithRemoteApplication(DefaultApplication.java:100)
     at org.mule.tooling.client.internal.ApplicationConnectivityTestingService.doTestConnection(ApplicationConnectivityTestingService.java:45)
     at org.mule.tooling.client.internal.AbstractConnectivityTestingService.testConnection(AbstractConnectivityTestingService.java:44)
     at org.mule.tooling.client.internal.AbstractConnectivityTestingService.invokeMethod(AbstractConnectivityTestingService.java:57)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:498)
     at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher$ToolingCallable.call(Dispatcher.java:232)
     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
     at java.lang.Thread.run(Thread.java:748)
 
     at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:176)
     at org.mule.tooling.agent.RuntimeToolingService.deployApplication(RuntimeToolingService.java:92)
     at org.mule.tooling.client.internal.application.FileSystemArtifactDeployer.lambda$new$2(FileSystemArtifactDeployer.java:51)
     at org.mule.tooling.client.internal.application.FileSystemArtifactDeployer.doInternalDeploy(FileSystemArtifactDeployer.java:67)
     at org.mule.tooling.client.internal.application.AbstractArtifactDeployer.deploy(AbstractArtifactDeployer.java:52)
     at org.mule.tooling.client.internal.application.DefaultApplication.evaluateWithRemoteApplication(DefaultApplication.java:100)
     at org.mule.tooling.client.internal.ApplicationConnectivityTestingService.doTestConnection(ApplicationConnectivityTestingService.java:45)
     at org.mule.tooling.client.internal.AbstractConnectivityTestingService.testConnection(AbstractConnectivityTestingService.java:44)
     at org.mule.tooling.client.internal.AbstractConnectivityTestingService.invokeMethod(AbstractConnectivityTestingService.java:57)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:498)
     at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher$ToolingCallable.call(Dispatcher.java:232)
     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
     at java.lang.Thread.run(Thread.java:748)
 

Based on the screenshot of your error, it looks like your Tooling Service is not runnning. Go to Window > Preferences > AnypointStudio > Tolling and start the Tooling service. Wait for 45 sec for it to start completely. Then test your connection.

Second, are you running the local training service using the provided jar file? If you are not, then your Derby DB is also not running, and connectivity test will fails as well.

Third, please copy your error log next time and upload it for us to see, rather than a screenshot.

-gopal

can some one please help, i followed the same steps given in Mulesoft document also the steps given by @andresmorales

Studio : Version: 7.3.2

Muler Server 4.1.4 EE

Thanks.. tried this at work place.. but will give a try at home too.. but i checked no other services are running at that ports..

adding the pom file @gopale

 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
     <modelVersion>4.0.0</modelVersion>
 
     <groupId>com.mycompany</groupId>
     <artifactId>training4-american-ws</artifactId>
     <version>1.0.0-SNAPSHOT</version>
     <packaging>mule-application</packaging>
 
     <name>training4-american-ws</name>
 
     <properties>
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
 
         <app.runtime>4.1.1</app.runtime>
         <mule.maven.plugin.version>3.1.6</mule.maven.plugin.version>
     </properties>
 
     <build>
         <plugins>
             <plugin>
                 <groupId>org.mule.tools.maven</groupId>
                 <artifactId>mule-maven-plugin</artifactId>
                 <version>${mule.maven.plugin.version}</version>
                 <extensions>true</extensions>
                 <configuration>
                 <sharedLibraries>
                         <sharedLibrary>
                             <groupId>mysql</groupId>
                             <artifactId>mysql-connector-java</artifactId>
                         </sharedLibrary>
                     <sharedLibrary>
                             <groupId>org.apache.derby</groupId>
                             <artifactId>derbyclient</artifactId>
                         </sharedLibrary>
                     <sharedLibrary>
                             <groupId>com.mycompany</groupId>
                             <artifactId>derbyclient-10.14.2.0</artifactId>
                         </sharedLibrary>
                     <sharedLibrary>
                             <groupId>org.apache.derby</groupId>
                             <artifactId>derby</artifactId>
                         </sharedLibrary>
                     </sharedLibraries>
                 </configuration>
             </plugin>
         </plugins>
     </build>
 
     <dependencies>
         <dependency>
             <groupId>org.mule.connectors</groupId>
             <artifactId>mule-http-connector</artifactId>
             <version>1.3.2</version>
             <classifier>mule-plugin</classifier>
         </dependency>
         <dependency>
             <groupId>org.mule.connectors</groupId>
             <artifactId>mule-sockets-connector</artifactId>
             <version>1.1.2</version>
             <classifier>mule-plugin</classifier>
         </dependency>
         <dependency>
             <groupId>org.mule.connectors</groupId>
             <artifactId>mule-db-connector</artifactId>
             <version>1.4.0</version>
             <classifier>mule-plugin</classifier>
         </dependency>
         <dependency>
             <groupId>mysql</groupId>
             <artifactId>mysql-connector-java</artifactId>
             <version>5.1.46</version>
         </dependency>
         <dependency>
             <groupId>org.apache.derby</groupId>
             <artifactId>derbyclient</artifactId>
             <version>10.15.1.3</version>
         </dependency>
         <dependency>
             <groupId>com.mycompany</groupId>
             <artifactId>derbyclient-10.14.2.0</artifactId>
             <version>0.1</version>
         </dependency>
         <dependency>
             <groupId>org.apache.derby</groupId>
             <artifactId>derby</artifactId>
             <version>10.14.2.0</version>
         </dependency>
     </dependencies>
 
     <repositories>
           <repository>
             <id>anypoint-exchange</id>
             <name>Anypoint Exchange</name>
             <url>https://maven.anypoint.mulesoft.com/api/v1/maven</url>
             <layout>default</layout>
         </repository>
         <repository>
             <id>mulesoft-releases</id>
             <name>MuleSoft Releases Repository</name>
             <url>https://repository.mulesoft.org/releases/</url>
             <layout>default</layout>
         </repository>
     </repositories>
     <pluginRepositories>
         <pluginRepository>
             <id>mulesoft-releases</id>
             <name>mulesoft release repository</name>
             <layout>default</layout>
             <url>https://repository.mulesoft.org/releases/</url>
             <snapshots>
                 <enabled>false</enabled>
             </snapshots>
         </pluginRepository>
     </pluginRepositories>
 
 </project>
 

Thanks, Pavan.

@zongwei

Please check if you are doing Development Fundamentals with Mule-3 or Mule-4. If I am not mistaken, Mule-3 based course talks about creating Spring Bean configuration prior to DB connection, where as Mule-4 based course does not. So, check that first.

If you are using this course based on Mule-3, you need to install Studio-6 from https://www.mulesoft.com/lp/dl/studio/previous Note that Studio7 will not work this version of the course.

If you are using teh course based on Mule-4, then the Studio version should be 7.x

Confirm that first, and download the correct content to proceed.

-gopal

Hello,

I've been stuck at this module since yesterday...I followed the solution you gave @andresmorales but still no luck... I have the same config as you but my tooling instance is not available...

When I try to proceed with the module even though the test connection failed, the application return the good request. But on the next walkthough, when I need to add the transform message, that's where I have issue...when I look at the input section and review the payload metadata there is nothing... And when I try to launch the app, here is what's returned on Advanced Rest Client:

I really don't know what to do anymore...I've tried to change the workspace, to check the status of the instance, to download another version of Anypoint Studio...But I still get the same issue. Can someone help me with this ? Thank you !

Hi @zongwei,

This is the definite solution:

Now the derby connector in the Anypoint Studio requires the subsubprotocol (based on the new changes for the derby connector: https://db.apache.org/derby/docs/10.0/manuals/reference/sqlj178.html)

There's no current way to connect to a JDBC URL derby DB through this connector, use the generic instead.

Solution

• Select Generic Connection

• Configure the JDBC Driver (load the derbyclient.jar any version from 10.13.1.1 to 10.14.2.0)

• Put the complete derby JDBC URL: jdbc:derby://localhost:1527/memory:training

• Set the Driver class: org.apache.derby.jdbc.ClientDriver

• Leave user and password empty

• Test connection & OK

Please upvote it, to make this answer visible.

Andres.

References:

• https://db.apache.org/derby/docs/10.0/manuals/reference/sqlj178.html

• https://db.apache.org/derby/docs/10.0/manuals/develop/develop14.html

• http://db.apache.org/derby/docs/10.6/devguide/cdevdvlpinmemdb.html

• https://db.apache.org/derby/docs/10.3/ref/rrefjdbc37352.html

• https://db.apache.org/derby/papers/DerbyClientSpec.html

@rahul_chaki , I couldn't proceed, and downloaded an older version of Anypoint Studio to follow the tutorial.

Hey @zongwei , were you able to resolve the issue? I'm facing the same issue and a bit confused how to go forward. If you were able to resolve the issue ,can you kindly tell me the process?

Thanks!