Alejandro Sequeira (JIRA | 19 Jun 2013 19:58

[mule-jira] (MULE-6888) Anchor file is created before application is fully deployed

Issue Type: Bug
Affects Versions: 3.4.0
Assignee: Unassigned
Components: Core: Deployment
Created: 19/Jun/13 12:57 PM
Description:
  1. Copy flight-reservation example to apps dir
  2. Run bin/mule
  3. Wait for flight-reservation example anchor file to be created
  • Expected: flight-reservation example deployment is complete
  • Actual: flight-reservation app has been unpacked and deployment is in progress
Project: Mule
Labels: esb-backlog
Priority: To be reviewed
Reporter: Alejandro Sequeira
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Alejandro Sequeira (JIRA | 19 Jun 2013 14:35

http://www.mulesoft.org/schema/mule/activiti]

Alejandro Sequeira closed MULE-6885 as Cannot Reproduce
Change By: Alejandro Sequeira (19/Jun/13 07:33 AM)
Resolution: Cannot Reproduce
Fix Version/s: 3.3.1
Status: Open Closed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Alejandro Sequeira (JIRA | 19 Jun 2013 14:33

http://www.mulesoft.org/schema/mule/activiti]

Moved to mule-module-activity github project: https://github.com/mulesoft/mule-module-activiti/issues/1

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Pablo Kraan (JIRA | 19 Jun 2013 00:31

[mule-jira] (MULE-6887) Duplicating instanceName in quartz connectors cause weird application failures

Issue Type: Bug
Affects Versions: 3.4.0, 3.3.3 (EE only)
Assignee: Pablo Kraan
Components: Transport: Quartz
Created: 18/Jun/13 05:29 PM
Description:

Quartz connectors use a property named org.quartz.scheduler.instanceName. Duplicating that property value in different applications will cause application errors.

When duplicating the instance name, the first app will be normally deployed, then the second one will overwrite some elements in quartz.
The quartz connector from the first app will never be executed.
The quartz connector from the second app will be executed, but it will fail because it contains a reference to the connector from the first app:

org.quartz.JobExecutionException: No connector named "quartzConnectorpeople" found in MuleManager at org.mule.transport.quartz.jobs.EventGeneratorJob.doExecute(EventGeneratorJob.java:65) at org.mule.transport.quartz.jobs.AbstractJob.execute(AbstractJob.java:36) at org.quartz.core.JobRunShell.run(JobRunShell.java:216) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Project: Mule
Priority: To be reviewed
Reporter: Pablo Kraan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Damian Sima (JIRA | 18 Jun 2013 23:44

[mule-jira] (MULE-6886) flow initialState does not work with placeholders

Issue Type: Bug
Affects Versions: 3.4.0
Assignee: Unassigned
Components: Core: (other)
Created: 18/Jun/13 04:43 PM
Description:

The property initialState comes handy when developing mainly to shutdown stuff you don't need running.

But when I've try to put a placeholder like:

initialState=${some.inital.state} if fails with the following error:

FO 2013-06-18 18:43:17,005 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising RegistryBroker
INFO 2013-06-18 18:43:17,152 [main] org.mule.config.spring.MuleApplicationContext: Refreshing org.mule.config.spring.MuleApplicationContext <at> 61578aab: startup date [Tue Jun 18 18:43:17 GMT-03:00 2013]; root of context hierarchy
ERROR 2013-06-18 18:43:18,426 [main] org.mule.module.launcher.application.DefaultMuleApplication: null
org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processOneAttribute(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
at org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:113)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)
at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89)
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:109)
at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:119)
at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.config.builders.AutoConfigurationBuilder.autoConfigure(AutoConfigurationBuilder.java:101)
at org.mule.config.builders.AutoConfigurationBuilder.doConfigure(AutoConfigurationBuilder.java:57)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:84)
at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:207)
at org.mule.module.launcher.application.ApplicationWrapper.init(ApplicationWrapper.java:64)
at org.mule.module.launcher.DefaultMuleDeployer.deploy(DefaultMuleDeployer.java:47)
at org.mule.tooling.server.application.ApplicationDeployer.main(ApplicationDeployer.java:127)
INFO 2013-06-18 18:43:18,429 [main] org.mule.module.launcher.application.DefaultMuleApplication: App 'servicesource-dataloader' never started, nothing to dispose of
Exception in thread "main" org.mule.module.launcher.DeploymentInitException: SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'.
at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:219)
at org.mule.module.launcher.application.ApplicationWrapper.init(ApplicationWrapper.java:64)
at org.mule.module.launcher.DefaultMuleDeployer.deploy(DefaultMuleDeployer.java:47)
at org.mule.tooling.server.application.ApplicationDeployer.main(ApplicationDeployer.java:127)
Caused by: org.mule.api.config.ConfigurationException: Line 82 in XML document from URL file:/Users/damiansima/Documents/mulestudioworkspace/.mule/apps/servicesource-dataloader/servicesource-dataloader.xml is invalid; nested exception is org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'. (org.mule.api.lifecycle.InitialisationException) (org.mule.api.config.ConfigurationException)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:52)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:84)
at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:207)
... 3 more
Caused by: org.mule.api.config.ConfigurationException: Line 82 in XML document from URL file:/Users/damiansima/Documents/mulestudioworkspace/.mule/apps/servicesource-dataloader/servicesource-dataloader.xml is invalid; nested exception is org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'. (org.mule.api.lifecycle.InitialisationException)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:52)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.config.builders.AutoConfigurationBuilder.autoConfigure(AutoConfigurationBuilder.java:101)
at org.mule.config.builders.AutoConfigurationBuilder.doConfigure(AutoConfigurationBuilder.java:57)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
... 6 more
Caused by: org.mule.api.lifecycle.InitialisationException: Line 82 in XML document from URL file:/Users/damiansima/Documents/mulestudioworkspace/.mule/apps/servicesource-dataloader/servicesource-dataloader.xml is invalid; nested exception is org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'.
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:117)
at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:119)
at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
... 10 more
Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 82 in XML document from URL file:/Users/damiansima/Documents/mulestudioworkspace/.mule/apps/servicesource-dataloader/servicesource-dataloader.xml is invalid; nested exception is org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'.
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
at org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:113)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)
at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89)
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:109)
... 13 more
Caused by: org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${consume.staging.area.flow.initial.state}' is not a valid value for 'NMTOKEN'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processOneAttribute(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)
... 22 more

Project: Mule
Priority: To be reviewed
Reporter: Damian Sima
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Alejandro Sequeira (JIRA | 18 Jun 2013 21:50

http://www.mulesoft.org/schema/mule/activiti]

Matias Pentreath, mule-module-activity is not a Mule ESB module

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Damian Bakarcic (JIRA | 17 Jun 2013 21:59

[mule-jira] (MULE-6884) HTTP/HTTPS Connectors: tcpNoDelay

Issue Type: Bug
Affects Versions: 3.3.0
Assignee: Damian Bakarcic
Components: Transport: HTTP(S) / Jetty
Created: 17/Jun/13 02:58 PM
Description:

HttpServerConnection ignores the tcpNoDelay attribute on the HTTP/HTTPS connector, always setting it to true.

  • This seems to be quite intentional, but is absent from the documentation.
  • Especially interesting is that the TCP Connector defaults to the opposite...
  • This discrepancy only appears on inbound HTTP/HTTPS; outbound HTTP/HTTPS connections do seem to honour the configuration.
Project: Mule
Priority: To be reviewed
Reporter: Damian Bakarcic
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Roine Edmundsson (JIRA | 17 Jun 2013 11:26

[mule-jira] (MULE-6883) CLONE - pattern:http-proxy not allowing []

Issue Type: Bug
Affects Versions: 3.3.1, 3.4 M3
Assignee: Pablo Kraan
Components: Core: Configuration
Created: 17/Jun/13 04:26 AM
Description:

MuleStudio on Windows 7, JDK7, 3.3.1 CE
MuleStudio on Mac, defaultJava, 3.3.1 CE and 3.4 ME3
Calls made with Chrome Version 24.0.1312.57 m and IE Version 9.0.8812.16421

When trying to use the pattern:http-proxy to proxy a REST service residing on an SSL endpoint to an internal address over normal http I get the error that is in the log when posting REST queries with hard bracets(i.e. []) in the URL. If I call the REST service directly I have no issues with the hard brackets.

I also noticed that if I do not provide a path in the configuration of the http-inbound it will fail. Also if I move the path from the server.URI to path on the https-outbound it will also fail. Seems to be doing the authentication directly to the server field and not the full URI.

Main issue is that [] aren't allowed though, making it very hard to utilize the pattern:http-proxy for a REST service.

Environment:

Mule Studio, tried and tested on Windows 7 with Studio and Mule 3.3.1 CE and on Mac with Studio and mule 3.3.1 CE and 3.4 ME3. Using JDK7 on windows and mac native Java on Mac.

Project: Mule
Priority: To be reviewed
Reporter: Roine Edmundsson
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Pablo Kraan (JIRA | 14 Jun 2013 16:40

[mule-jira] (MULE-6882) TCP Outbound Endpoint ignores responseTimeout

Issue Type: Bug
Affects Versions: 3.3.3 (EE only)
Assignee: Unassigned
Attachments: tcptimeout-issue.zip
Components: Transport: TCP / UDP / SSL / Multicast
Created: 14/Jun/13 09:39 AM
Description:

While the HTTP and HTTPS transports correctly use the responseTimeout when reading the response, this is ignored when using TCP.

Project: Mule
Priority: To be reviewed
Reporter: Pablo Kraan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Philip Parker (JIRA | 14 Jun 2013 02:48

[mule-jira] (MULE-6881) No way to catch errors from individual message processors

Philip Parker commented on MULE-6881

Moved Jira here as it should be in ESB team because functionality does not currently exist in ESB (As Eugene kindly pointed out to me).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Pablo Kraan (JIRA | 13 Jun 2013 22:19

[mule-jira] (MULE-6880) FTP responseTimeout has no effect

Issue Type: Bug
Affects Versions: 3.4.0, 3.3.3 (EE only)
Assignee: Pablo Kraan
Components: Transport: FTP / SFTP
Created: 13/Jun/13 03:18 PM
Description:

Currently if the FTP server hung, the responseTimeout configured in the endpoint has no effect (i.e. the thread that is trying to perform the put operation will never get released)

Project: Mule
Priority: To be reviewed
Reporter: Pablo Kraan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Gmane