Unable to run test in Flow Designer - mulesoft

I am going through MuleSoft's "Development Fundamentals (Mule 4)" and I'm doing one of the walkthroughs - "WT 2-3: Create an integration application with Flow Designer that consumes an API" and on one of the steps (step 23) the test button does not run and consequently, I can't test the REST endpoint, because I don't have a URL to send requests to.
When I click the Test button, it switches to "Refresh" and on the left of the button it says "Project needs to be refreshed".
However, when I click the Refresh button and wait several minutes for the refresh, it goes back to the Test button, which again doesn't work and shows "Project needs to be refreshed" when clicked, so I am stuck in this endless loop.
I tried deleting everything I had done up to that point and started again from scratch, but when I reached that walkthrough again, I had the same problem.
The only things I have in the Flow Designer are an HTTP Listener and "American Flights API". The problem occurs after I add the API. Before I added in the API, I successfully ran the test with an HTTP Listener and a logger.
The HTTP Listener configuration:
path : flights
The "American Flights API" configuration:
host : training4-american-api.cloudhub.io
port : 80
base path : /
protocol : HTTP
The log in the Runtime Manager shows a LifecycleException, but I don't know what is causing it or how to prevent it.
Here is the log from the Runtime Manager:
[2021-08-22 14:56:32.872] INFO com.mulesoft.ch.queue.boot.PersistentQueueCoreExtension [qtp1112210076-38]: The PersistentQueueManager is NOT configured. The normal VM queue manager will be used.
[2021-08-22 14:56:40.483] INFO org.mule.runtime.api.el.AbstractBindingContextBuilderFactory [qtp1112210076-38]: Loaded BindingContextBuilderFactory implementation 'org.mule.runtime.core.api.el.DefaultBindingContextBuilderFactory' from classloader 'org.mule.runtime.module.reboot.internal.MuleContainerSystemClassLoader#740e48c1'
[2021-08-22 14:56:40.874] INFO org.mule.runtime.core.internal.util.journal.TransactionJournal [qtp1112210076-38]: Using files for tx logs /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-tx-log/tx1.log and /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-tx-log/tx2.log
[2021-08-22 14:56:40.882] INFO org.mule.runtime.core.internal.util.journal.TransactionJournal [qtp1112210076-38]: Using files for tx logs /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-xa-tx-log/tx1.log and /opt/mule/mule-4.3.0/./.mule/americanflightsapp-xslg/queue-xa-tx-log/tx2.log
[2021-08-22 14:56:41.137] INFO com.mulesoft.ch.batch.BatchCoreExtension [qtp1112210076-38]: Persistent queues is not enabled for batch module as it was not configured in Cloudhub console
[2021-08-22 14:56:41.168] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [ArtifactDeployer.start.01]: Starting ResourceManager
[2021-08-22 14:56:41.169] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [ArtifactDeployer.start.01]: Started ResourceManager
[2021-08-22 14:56:41.207] INFO org.mule.runtime.core.internal.logging.LogUtil [ArtifactDeployer.start.01]:
**********************************************************************
* Application: americanflightsapp-xslg *
* OS encoding: UTF-8, Mule encoding: UTF-8 *
* *
**********************************************************************
[2021-08-22 14:59:47.852] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [qtp1112210076-39]: Stopping ResourceManager
[2021-08-22 14:59:47.852] INFO org.mule.runtime.core.internal.util.queue.QueueXaResourceManager [qtp1112210076-39]: Stopped ResourceManager
[2021-08-22 14:59:47.867] INFO org.mule.runtime.core.internal.lifecycle.RegistryLifecycleCallback [qtp1112210076-39]: Failure executing phase stop over object DefaultBatchEngine, error is: org.mule.runtime.api.lifecycle.LifecycleException(Failed to invoke lifecycle phase "stop" on object: com.mulesoft.mule.runtime.module.batch.internal.engine.DefaultBatchEngine#2fd96fde)
[2021-08-22 14:59:47.869] INFO org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableArtifact [qtp1112210076-39]: Stopping app 'americanflightsapp-xslg' with no mule context
[2021-08-22 14:59:47.922] INFO org.mule.runtime.core.internal.logging.LogUtil [qtp1112210076-39]:
**********************************************************************
* Application "americanflightsapp-xslg" shut down normally on: *
* 8/22/21 2:59 PM *
* Up for: 0 days, 0 hours, 3 mins, 6.753 sec *
**********************************************************************
Any help is welcome, thank you.

The problem was coming from MuleSoft's side. I reported the problem on their Help Center and got a response that the issue was under investigation. Several days later, the problem was fixed and the Test button on the Flow Designer page is now working correctly.

Related

Amplify Init - InvalidSignatureException: Signature not yet current

Encountered and solved this problem. Posting for posterity since my situation differed from the usual.
Important: I am running a derivative of Ubuntu in a VirtualBox VM on a freshly installed Windows host.
The Problem
When creating a new react amplify project using create-react-app, amplify init fails with an InvalidSignatureException after selecting a profile:
$ amplify init
...
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html
? Please choose the profile you want to use default
InvalidSignatureException: Signature not yet current: 20220528T081112Z is still later than 20220528T051608Z (20220528T051108Z + 5 min.)
at Object.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/snapshot/node_modules/aws-sdk/lib/protocol/rest_json.js:49:8)
at Request.callListeners (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/snapshot/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
...
at IncomingMessage.EventEmitter.emit (domain.js:483:12)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
code: 'InvalidSignatureException',
time: 2022-05-28T08:11:12.872Z,
requestId: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX',
statusCode: 403,
retryable: false,
retryDelay: 35.74742577991159
}
I also experienced errors with amplify push and amplify pull complaining about things such as "Time skew" and "Timeouts", and AWS Console threw "List apps call failed: Network Error".
Similar Posts
Here are a sample of posts discussing similar problems.
'amplify init' keeps failing
https://github.com/aws-amplify/amplify-js/issues/2014
https://github.com/concourse/s3-resource/issues/34
https://github.com/aws-amplify/amplify-hosting/issues/2417
Failed ideas
Sample of failed ideas:
I tried creating a second project to see if problem persisted. It did.
I tried syncing my time via ntp, ntpdate, ntpd. Same error.
I tried setting time via GUI. Failed to set. Same error.
Story leading to solution
At this point, I noticed my time occasionally jumps on sync with ntpd. Actual time was 01:40; on sync, it jump to 04:40, then back to 01:40. This would occur intermittently on sync. Timezones were set correctly. Trial and error exhausts my ideas, so I return to my host. Host time is 01:40, but discord messages are timestamping at 10:40. Wait.
Windows host timezone was set to UTC-8:00 Pacific Time. VirtualBox Linux guest was set to UTC-5:00 Eastern Time. Oddly, both were displaying 01:40.
Steps to resolve
Set host timezone to UTC-5:00 Eastern Time
Sync Clock in "Time and Date" settings in Windows
Disable/uninstall ntp from Linux guest
Issue was resolved. amplify init succeeded.

Error - Failed to register Fiddler as the system proxy

When I try to run FiddleApplication.Startup(startupConfig)
FiddlerCoreStartupSettings startupSettings = newFiddlerCoreStartupSettingsBuilder()
.ListenOnPort(0)
.RegisterAsSystemProxy()
.DecryptSSL()
.Build();
FiddlerApplication.Startup(startupSettings);
In my log events I see:
Starting FiddlerCore/4.6.20191.7809 (NoSAZ)...
** LogString: !WARNING: The DefaultLAN Gateway information could not be obtained.
** NotifyUser: Error - Failed to register Fiddler as the system proxy.
I'm running the process as administrator.
Note: When I run the normal Fiddler UI application everything works fine. Even running an older FiddlerCore version (2.3) is able to register itself as the system proxy.
P.S - I also see a warning in Visual Studio - "Please use Telerik.NetworkConnections.NetworkConnectionsManager to register the FiddlerCore Proxy as the system proxy." But I couldn't find any documentation/examples using NetworkConnectionsManager and I couldn't figure out how to use it.

How to wait for page load in selenium webdriver

I am using selenium-server-3.7.1 and Firefox 57
How to wait for page to load completely
I tried following
return ((JavascriptExecutor) driver).executeScript(
"return document.readyState").equals("complete");
but it is not working
Basically the above command is not recognizing below operations
[testng] 1535139249496 addons.productaddons INFO sending request to: https://aus5.mozilla.org/update/3/GMP/57.0.4/20180103231032/Linux_x86_64-gcc3/en-US/release/Linux%204.1.12-112.14.10.el7uek.x86_64%20(GTK%203.22.10%2Clibpulse%2010.0.0)/default/default/update.xml
[testng] 1535139249669 addons.productaddons INFO Completed downloading document
[testng] 1535139249818 addons.productaddons INFO downloadXHR File download. status=200
[testng] 1535139249821 addons.productaddons INFO Downloaded file will be saved to /tmp/tmpaddon-c61a84
[testng] 1535139738375 addons.manager INFO Skipping background update check
[testng] 1535139978387 DeferredSave.extensions.json DEBUG Save changes
[testng] 1535139978387 DeferredSave.extensions.json DEBUG Starting timer
[testng] 1535139978409 DeferredSave.extensions.json DEBUG Starting write
[testng] 1535139978412 DeferredSave.extensions.json DEBUG Write succeeded
I gave hard sleep of 30 seconds to finish these operations
Is there a way to wait for these operations to be completed?
In Automation script, There needs to wait on multiple instance. There can not be use Thread.Sleep(); every time. Page need to wait for JQuery, JavaScript, Angular loading. And which can not be handle by only document.readyState We have to wait for all substances if application is built on. So, We can create single method to wait for Page load and that method can call multiple times.
This is the Blog link for same, Which will help you to understand it. Click Here
You can include those method, on which your application is build.
If in case Blog link might loss, there is sample Github project is available for same. Click Here
Wait wait = new FluentWait(driver)
.withTimeout(30000, TimeUnit.SECONDS) .pollingEvery(5, TimeUnit.SECONDS) .ignoring(NoSuchElementException.class);
Hope this will help you

Collecting Metrics with Graphite Plugin leads to "A metric named [..] already exists" error

when i configure the flink-conf.yaml to collect metrics with the graphite plugin,
the most time only incomplete metrics are being sent. On the Taskmanager output multiple errors occur like:
2018-08-15 00:58:59,016 WARN org.apache.flink.runtime.metrics.MetricRegistryImpl - Error while registering metric.
java.lang.IllegalArgumentException: A metric named mycomputer.taskmanager.8ceab4c3dfbf9fc5fa2af0447f1373a1.State machine job.Source: Custom Source.0.numRecordsOut already exists
at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91)
at org.apache.flink.dropwizard.ScheduledDropwizardReporter.notifyOfAddedMetric(ScheduledDropwizardReporter.java:131)
at org.apache.flink.runtime.metrics.MetricRegistryImpl.register(MetricRegistryImpl.java:329)
at org.apache.flink.runtime.metrics.groups.AbstractMetricGroup.addMetric(AbstractMetricGroup.java:379)
at org.apache.flink.runtime.metrics.groups.AbstractMetricGroup.counter(AbstractMetricGroup.java:312)
at org.apache.flink.runtime.metrics.groups.AbstractMetricGroup.counter(AbstractMetricGroup.java:302)
at org.apache.flink.runtime.metrics.groups.OperatorIOMetricGroup.<init>(OperatorIOMetricGroup.java:41)
at org.apache.flink.runtime.metrics.groups.OperatorMetricGroup.<init>(OperatorMetricGroup.java:48)
at org.apache.flink.runtime.metrics.groups.TaskMetricGroup.addOperator(TaskMetricGroup.java:146)
at org.apache.flink.streaming.api.operators.AbstractStreamOperator.setup(AbstractStreamOperator.java:174)
at org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.setup(AbstractUdfStreamOperator.java:82)
at org.apache.flink.streaming.runtime.tasks.OperatorChain.<init>(OperatorChain.java:143)
at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:267)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:711)
at java.lang.Thread.run(Thread.java:748)
I've tried this on a completely freshly prepared flink-1.6.0 release with following config and the precompiled "State machine job" in the examples folder:
metrics.reporters: grph
metrics.reporter.grph.class: org.apache.flink.metrics.graphite.GraphiteReporter
metrics.reporter.grph.host: localhost
metrics.reporter.grph.port: 2003
metrics.reporter.grph.interval: 1 SECONDS
metrics.reporter.grph.protocol: TCP
I use the official graphite docker image (https://hub.docker.com/r/graphiteapp/docker-graphite-statsd/) that is running on the default configuration.
Has anybody an idea, how i can fix this issue?
Thank's and best regards
update
to exclude that a specific local setting is responsible for this behaviour, I repeated the process on a clean EC2 instance. There's exactly the same error here.
How to reproduce:
start EC2 t2.xlarge
installed java
download flink at https://www.apache.org/dyn/closer.lua/flink/flink-1.6.0/flink-1.6.0-bin-scala_2.11.tgz
added the flink-metrics-graphite-1.6.0.jar to lib
configured the flink-yaml.conf as mentioned in my previous post
./bin/start-cluster.sh
./bin/flink run examples/streaming/StateMachineExample.jar
I have not set up graphite in this case, because the error obviously already
occurs before.
After the job has been started you can view the error in the flink dashboard under Task Manager -> Logs

DNN Custom Authentication provider installation error

i developed a custom login module for my dnn site, i could install custom login in my local host installed dnn version 05.06.01 (238), but when i tried to install it in my Live site installed same dnn version, it failed to install and shows the Error as follows
Package Installation Report
See below for the results of the package installation
Error loading files from temporary folder - see below
StartJob Starting Installation
Info Starting Installation - DNN_CustomLoginAuthentication
Info Starting Installation - AuthenticationSystem
Info Authentication registered successfully - CustomLogin
Info Component installed successfully - AuthenticationSystem
Info Starting Installation - Assembly
Info Assembly registered - bin\Providers\DotNetNuke.Authentication.CustomLogin.dll
Info Created - bin\Providers\DotNetNuke.Authentication.CustomLogin.dll
Info Component installed successfully - Assembly
Info Starting Installation - File
Info Folder Created -
C:\inetpub\vhosts\CITYBROKERS.GR\httpdocs\DesktopModules\AuthenticationServices\CustomLogin\App_LocalResources
Info Created - App_LocalResources\Login.ascx.resx
Info Created - App_LocalResources\Settings.ascx.resx
Info Created - Login.ascx
Info Created - Settings.ascx
Info Created - license.txt
Info Created - CustomLogin_05.00.01_ReleaseNotes.txt
Info Created - trusterror.htm
Info Created - install.css
Info Created - logo.gif
Info Component installed successfully - File
Info Starting Installation - ResourceFile
Info Component installed successfully - ResourceFile
Info Starting Installation - Cleanup
Info Component installed successfully - Cleanup
Info Starting Installation - Config
Info Creating backup of previous version - web.config
Failure ExceptionSystem.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode) at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node) at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig) at DotNetNuke.Services.Installer.XmlMerge.UpdateConfig(XmlDocument target) at DotNetNuke.Services.Installer.Installers.ConfigInstaller.Install()
Failure Installation Failed - Config
Info Rolling back component install - AuthenticationSystem
Info Authentication unregistered successfully - CustomLogin
Info Component rolled back successfully - AuthenticationSystem
Info Rolling back component install - Assembly
Info Assembly unregistered - bin\Providers\DotNetNuke.Authentication.CustomLogin.dll
Info Component rolled back successfully - Assembly
Info Rolling back component install - File
Info Component rolled back successfully - File
Info Rolling back component install - ResourceFile
Info Component rolled back successfully - ResourceFile
Info Rolling back component install - Cleanup
Info Component rolled back successfully - Cleanup
Info Installation Failed - DNN_CustomLoginAuthentication
Info Deleted temporary install folder
EndJob Installation Failed
Info Component rolled back successfully - AuthenticationSystem
It failed update the web.config. Check the config section in the provider's manifest, and see if it's referencing nodes that don't exist. Install the Symbols package onto your live site to get a line number for the exception that occurs (or, even better, get a local copy of your live site and walk through the installation in the debugger).
Check your permissions on the installs folder make sure NETWORK SERVICE/S (cant remember if it has an s) has read/write permissions

Resources