ErrorHandler example not emailing?

[Andrew McLaughlin]

Hi all,

I'm in the process of learning Mule and going through the examples in 2.0.1. The first couple examples worked great. So, I set up the ErrorHandler test including the ant step to download all the supporting jars. When I run it, no matter which exception I copy to the "in" folder, it only creates an item in the "exception" folder. Even though I configured a valid email address and MTA, it doesn't seem to be attempting to send an email. Or, at least I never get one. The mail.log shows no connections except for my own manual "telnet localhost smtp", which works fine.

Is the error-config.xml perhaps configured wrong that it doesn't hand off the FatalException to the FatalHandler? I apologize in advance as I am struggling to comprehend the finer nuances of how to configure Mule. I've spent a couple hours trying to glean what may be out of place. In spite of making a few changes that might have looked out of place, nothing seems to work. :)

Any advice would be greatly appreciated! Are there any books that I can buy to minimize the learning curve? Support groups? 12-step programs?! :)

Piko

[antoine.borg]

Hi,


What is your configuration for the SMTP connector? Could this be a
permissions issue?

HTH


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: Andrew McLaughlin [mailto:andrew@...]
Sent: Saturday, May 17, 2008 7:58 AM
To: user@...
Subject: [mule-user] ErrorHandler example not emailing?


Hi all,

I'm in the process of learning Mule and going through the examples in 2.0.1.
The first couple examples worked great. So, I set up the ErrorHandler test
including the ant step to download all the supporting jars. When I run it,
no matter which exception I copy to the "in" folder, it only creates an item
in the "exception" folder. Even though I configured a valid email address
and MTA, it doesn't seem to be attempting to send an email. Or, at least I
never get one. The mail.log shows no connections except for my own manual
"telnet localhost smtp", which works fine.

Is the error-config.xml perhaps configured wrong that it doesn't hand off
the FatalException to the FatalHandler? I apologize in advance as I am
struggling to comprehend the finer nuances of how to configure Mule. I've
spent a couple hours trying to glean what may be out of place. In spite of
making a few changes that might have looked out of place, nothing seems to
work. :)

Any advice would be greatly appreciated! Are there any books that I can buy
to minimize the learning curve? Support groups? 12-step programs?! :)

Piko
--
View this message in context:
http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17288475
.html
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew McLaughlin]

Hi Antoine,

Yeah, I already had tested the MTA and it works fine. If I "telnet localhost smtp" it answers and allows me to send an email. In looking at the mule logs  it appears to not be handing off to the appropriate FatalHandler that would have sent an email. So, it begs the question, does the ErrorHandler example have a typo in the config?

I wish I could read the config file easier, but this is all quite Greek to me at this point. Is anyone else getting the ErrorHandler example working?

Andrew

Antoine Borg wrote:

Hi,


What is your configuration for the SMTP connector? Could this be a
permissions issue?

HTH


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: [e-mail] | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: Andrew McLaughlin [mailto:[e-mail]]
Sent: Saturday, May 17, 2008 7:58 AM
To: [e-mail]
Subject: [mule-user] ErrorHandler example not emailing?


Hi all,

I'm in the process of learning Mule and going through the examples in 2.0.1.
The first couple examples worked great. So, I set up the ErrorHandler test
including the ant step to download all the supporting jars. When I run it,
no matter which exception I copy to the "in" folder, it only creates an item
in the "exception" folder. Even though I configured a valid email address
and MTA, it doesn't seem to be attempting to send an email. Or, at least I
never get one. The mail.log shows no connections except for my own manual
"telnet localhost smtp", which works fine.

Is the error-config.xml perhaps configured wrong that it doesn't hand off
the FatalException to the FatalHandler? I apologize in advance as I am
struggling to comprehend the finer nuances of how to configure Mule. I've
spent a couple hours trying to glean what may be out of place. In spite of
making a few changes that might have looked out of place, nothing seems to
work. :)

Any advice would be greatly appreciated! Are there any books that I can buy
to minimize the learning curve? Support groups? 12-step programs?! :)

Piko
--
View this message in context:
http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17288475
.html
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[antoine.borg]

Hi,

I've taken a quick look at the errorHandler code - can you post the content
of your email.properties file? Perhaps there's something there ....

A


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: Andrew McLaughlin [mailto:andrew@...]
Sent: Monday, May 19, 2008 8:57 PM
To: user@...
Subject: RE: [mule-user] ErrorHandler example not emailing?


Hi Antoine,

Yeah, I already had tested the MTA and it works fine. If I "telnet localhost
smtp" it answers and allows me to send an email. In looking at the mule logs
it appears to not be handing off to the appropriate FatalHandler that would
have sent an email. So, it begs the question, does the ErrorHandler example
have a typo in the config?

I wish I could read the config file easier, but this is all quite Greek to
me at this point. Is anyone else getting the ErrorHandler example working?

Andrew



Antoine Borg wrote:

>
> Hi,
>
>
> What is your configuration for the SMTP connector? Could this be a
> permissions issue?
>
> HTH
>
>
> Antoine Borg, Senior Consultant | Tel: [phone] | Fax: +356 21
> 334156 ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142,
> MALTA
> email: antoine.borg@... | blog: blog.ricston.com | web:
> ricston.com
>
> -----Original Message-----
> From: Andrew McLaughlin [mailto:andrew@...]
> Sent: Saturday, May 17, 2008 7:58 AM
> To: user@...
> Subject: [mule-user] ErrorHandler example not emailing?
>
>
> Hi all,
>
> I'm in the process of learning Mule and going through the examples in
> 2.0.1.
> The first couple examples worked great. So, I set up the ErrorHandler
> test including the ant step to download all the supporting jars. When
> I run it, no matter which exception I copy to the "in" folder, it only
> creates an item in the "exception" folder. Even though I configured a
> valid email address and MTA, it doesn't seem to be attempting to send
> an email. Or, at least I never get one. The mail.log shows no
> connections except for my own manual "telnet localhost smtp", which
> works fine.
>
> Is the error-config.xml perhaps configured wrong that it doesn't hand
> off the FatalException to the FatalHandler? I apologize in advance as
> I am struggling to comprehend the finer nuances of how to configure
> Mule. I've spent a couple hours trying to glean what may be out of
> place. In spite of making a few changes that might have looked out of
> place, nothing seems to work. :)
>
> Any advice would be greatly appreciated! Are there any books that I
> can buy to minimize the learning curve? Support groups? 12-step
> programs?! :)
>
> Piko
> --
> View this message in context:
> http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17
> 288475
> .html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>

--
View this message in context:
http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17325623
.html
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew McLaughlin]

Here's the contents of my email.properties:

#
# Properties used to compose a message to the Mule administrator
#

# Substitute e-mail headers as appropriate
email.toAddress=[e-mail]
email.fromAddress=mule-alert@localhost
email.subject=Mule Alert

# Configure properties for your outgoing mail server as needed.
smtp.host=localhost
smtp.port=25
smtp.username=
smtp.password=

Looks pretty straightforward. Strange thing is, my local MTA on localhost is never called. Not even a hello. Does this example work on your machine?!

Andrew



Hi,

I've taken a quick look at the errorHandler code - can you post the content
of your email.properties file? Perhaps there's something there ....

A


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: [e-mail] | blog: blog.ricston.com | web: ricston.com

[Andrew Perepelytsya]

Can you enable debug logging for Mule? This should turn on javamail's session debugging.

Andrew

[Andrew McLaughlin]

Sure, how do I turn that on? :)

Andrew

Andrew Perepelytsya wrote:

Can you enable debug logging for Mule? This should turn on javamail's
session debugging.

Andrew

[Andrew Perepelytsya]

Check the $MULE_HOME/conf/log4j.properties and change org.mule 's category to DEBUG. There was a doc for this, but I'm a bit busy atm to browse for it.

HTH,
Andrew

On Wed, May 21, 2008 at 5:44 PM, Andrew McLaughlin <andrew@...> wrote:

Sure, how do I turn that on? :)

Andrew

Andrew Perepelytsya wrote:
>
> Can you enable debug logging for Mule? This should turn on javamail's
> session debugging.
>
> Andrew
>
>

--
View this message in context: http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17377167.html

Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Andrew McLaughlin]

Here's a log dump showing all debug after copying in the FatalException.xml file from "out" to "in". I can see quite a few references to "smtp" and it appears that it can't find any of the properties items that it needs. Perhaps I have MULE_HOME set wrong? I currently have that set to ~/mule-2.0.1

TIA!
Andrew

DEBUG 2008-05-21 23:35:55,045 [FileConnector.receiver.4] org.mule.transport.file.FileMessageReceiver: Message Received from: file://./test-data/in
DEBUG 2008-05-21 23:35:55,049 [FileConnector.receiver.4] org.mule.DefaultMuleSession: There is no session id on the request using key: ID. Generating new session id: 547ed1e5-27c9-11dd-a20f-13d71ad19b24
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.DefaultMuleSession: dispatching event to service: Error Manager, event is: MuleEvent: 547ef8f6-27c9-11dd-a20f-13d71ad19b24, sync=false, stop processing=false, DefaultInboundEndpoint{endpointUri=file://./test-data/in, connector=FileConnector{this=b7e998, started=true, initialised=true, name='FileConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[file], serviceOverrides=null}, transformer=[XmlToObject{this=ca425c, name='XMLToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class java.lang.String, class [B, class java.io.InputStream, interface org.w3c.dom.Document, interface org.dom4j.Document]}, ExceptionBeanToErrorMessage{this=caad9a, name='ExceptionBeanToErrorMessage', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ErrorMessage, sourceTypes=[class org.mule.example.errorhandler.ExceptionBean]}], name='endpoint.file.test.data.in', properties={}, transactionConfig=Transaction{factory=null, action=NONE, timeout=0}, filter=org.mule.transport.file.filters.FilenameWildcardFilter@25871f, deleteUnacceptedMessages=false, securityFilter=null, synchronous=false, initialState=started, remoteSync=false, remoteSyncTimeout=3000, endpointEncoding=UTF-8}
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.model.seda.SedaService: Service: Error Manager has received asynchronous event on: file://./test-data/in
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.model.seda.SedaService: Service: Error Manager has received asynchronous event on: file://./test-data/in
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.registry.TransientRegistry: lookupObject: key=_muleQueueManager scope=2
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.registry.TransientRegistry: Failed to find object in Registry ID: org.mule.Registry.Transient
DEBUG 2008-05-21 23:35:55,053 [FileConnector.receiver.4] org.mule.config.spring.SpringRegistry: lookupObject: key=_muleQueueManager scope=2
DEBUG 2008-05-21 23:35:55,054 [FileConnector.receiver.4] org.mule.model.seda.SedaService: Service Error Manager putting event on queue Error Manager: MuleEvent: 547ef8f6-27c9-11dd-a20f-13d71ad19b24, sync=false, stop processing=false, DefaultInboundEndpoint{endpointUri=file://./test-data/in, connector=FileConnector{this=b7e998, started=true, initialised=true, name='FileConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[file], serviceOverrides=null}, transformer=[XmlToObject{this=ca425c, name='XMLToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class java.lang.String, class [B, class java.io.InputStream, interface org.w3c.dom.Document, interface org.dom4j.Document]}, ExceptionBeanToErrorMessage{this=caad9a, name='ExceptionBeanToErrorMessage', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ErrorMessage, sourceTypes=[class org.mule.example.errorhandler.ExceptionBean]}], name='endpoint.file.test.data.in', properties={}, transactionConfig=Transaction{factory=null, action=NONE, timeout=0}, filter=org.mule.transport.file.filters.FilenameWildcardFilter@25871f, deleteUnacceptedMessages=false, securityFilter=null, synchronous=false, initialState=started, remoteSync=false, remoteSyncTimeout=3000, endpointEncoding=UTF-8}
DEBUG 2008-05-21 23:35:55,054 [Error Manager.1] org.mule.model.seda.SedaService: Service: Error Manager dequeued event on: file://./test-data/in
DEBUG 2008-05-21 23:35:55,059 [Error Manager.2] org.mule.DefaultMuleMessage: new copy of message for Thread[Error Manager.2,5,main]
DEBUG 2008-05-21 23:35:55,073 [Error Manager.2] org.mule.module.xml.transformer.XmlToObject: Applying transformer XMLToExceptionBean (org.mule.module.xml.transformer.XmlToObject)
DEBUG 2008-05-21 23:35:55,073 [Error Manager.2] org.mule.module.xml.transformer.XmlToObject: Object before transform: org.mule.transport.file.FileMessageAdapter/org.mule.transport.file.FileMessageAdapter@f77e2f{id=/Users/andrew/Project/mule-2.0.1/examples/errorhandler/test-data/in/FatalException.xml, payload=org.mule...
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.module.xml.transformer.XmlToObject: Object after transform: org.mule.example.errorhandler.ExceptionBean@e154b9
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.module.xml.transformer.XmlToObject: The transformed object is of expected type. Type is: ExceptionBean
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.example.errorhandler.ExceptionBeanToErrorMessage: Applying transformer ExceptionBeanToErrorMessage (org.mule.example.errorhandler.ExceptionBeanToErrorMessage)
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.example.errorhandler.ExceptionBeanToErrorMessage: Object before transform: org.mule.example.errorhandler.ExceptionBean@e154b9
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.example.errorhandler.ExceptionBeanToErrorMessage: Object after transform: org.mule.example.errorhandler.ErrorMessage@814af5
DEBUG 2008-05-21 23:35:55,441 [Error Manager.2] org.mule.example.errorhandler.ExceptionBeanToErrorMessage: The transformed object is of expected type. Type is: ErrorMessage
DEBUG 2008-05-21 23:35:55,458 [Error Manager.2] org.mule.model.resolvers.ReflectionEntryPointResolver: Invoking org.mule.example.errorhandler.ErrorManager.onException({class org.mule.example.errorhandler.ErrorMessage})

********************************************************************************
* Exception received in FATAL EXCEPTION HANDLER. Logic could be put in here    *
* to enrich the message content.                                               *
********************************************************************************
ERROR 2008-05-21 23:35:55,467 [Error Manager.2] org.mule.example.errorhandler.handlers.FatalHandler: Exception is: org.mule.api.lifecycle.FatalException
org.mule.api.lifecycle.FatalException
DEBUG 2008-05-21 23:35:55,469 [Error Manager.2] org.mule.model.resolvers.ReflectionEntryPointResolver: Result of call org.mule.example.errorhandler.ErrorManager.onException({class org.mule.example.errorhandler.ErrorMessage}) is not null
DEBUG 2008-05-21 23:35:55,474 [Error Manager.2] org.mule.routing.outbound.FilteringOutboundRouter: No CorrelationId is set on the message, will set a new Id
DEBUG 2008-05-21 23:35:55,475 [Error Manager.2] org.mule.routing.outbound.FilteringOutboundRouter: Extracted correlation Id as: /Users/andrew/Project/mule-2.0.1/examples/errorhandler/test-data/in/FatalException.xml
DEBUG 2008-05-21 23:35:55,475 [Error Manager.2] org.mule.routing.outbound.FilteringOutboundRouter: Setting Correlation info on Outbound router for endpoint: file://test-data/exceptions
Id=/Users/andrew/Project/mule-2.0.1/examples/errorhandler/test-data/in/FatalException.xml
DEBUG 2008-05-21 23:35:55,475 [Error Manager.2] org.mule.registry.TransientRegistry: lookupObjects: type=interface org.mule.api.transformer.Transformer scope=2
DEBUG 2008-05-21 23:35:55,475 [Error Manager.2] org.mule.config.spring.SpringRegistry: lookupObjects: type=interface org.mule.api.transformer.Transformer scope=2
DEBUG 2008-05-21 23:35:55,477 [Error Manager.2] org.mule.transport.email.transformers.StringToEmailMessage: Setting transformer name to: StringToEmailMessage
DEBUG 2008-05-21 23:35:55,477 [Error Manager.2] org.mule.transport.jms.transformers.ObjectToJMSMessage: Setting transformer name to: ObjectToJMSMessage
DEBUG 2008-05-21 23:35:55,477 [Error Manager.2] org.mule.transport.jms.transformers.JMSMessageToObject: Setting transformer name to: JMSMessageToObject
DEBUG 2008-05-21 23:35:55,477 [Error Manager.2] org.mule.module.xml.transformer.XmlToObject: Setting transformer name to: XMLToExceptionBean
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.module.xml.transformer.ObjectToXml: java.lang.Object has been added as source type for this transformer, there will be no source type checking performed
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.module.xml.transformer.ObjectToXml: Setting transformer name to: ExceptionBeanToXML
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.example.errorhandler.ExceptionBeanToErrorMessage: Setting transformer name to: ExceptionBeanToErrorMessage
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.example.errorhandler.ErrorMessageToException: Setting transformer name to: ErrorMessageToException
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.example.errorhandler.ErrorMessageToExceptionBean: Setting transformer name to: ErrorMessageToExceptionBean
DEBUG 2008-05-21 23:35:55,478 [Error Manager.2] org.mule.transformer.simple.ObjectToString: Applying transformer _ObjectToString (org.mule.transformer.simple.ObjectToString)
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.transformer.simple.ObjectToString: Object before transform: org.mule.example.errorhandler.ErrorMessage@814af5
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.transformer.simple.ObjectToString: Object after transform: org.mule.example.errorhandler.ErrorMessage@814af5
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.transformer.simple.ObjectToString: The transformed object is of expected type. Type is: String
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.routing.outbound.FilteringOutboundRouter: Message being sent to: file://test-data/exceptions Message payload:
org.mule.example.errorhandler.ErrorMessage@814af5
 outbound transformer is: [ErrorMessageToExceptionBean{this=b51f4, name='ErrorMessageToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class org.mule.example.errorhandler.ErrorMessage]}, ObjectToXml{this=3174f7, name='ExceptionBeanToXML', ignoreBadInput=false, returnClass=class java.lang.String, sourceTypes=[class java.lang.Object]}]
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.DefaultMuleSession: MuleSession has received asynchronous event on: DefaultOutboundEndpoint{endpointUri=file://test-data/exceptions, connector=FileConnector{this=b7e998, started=true, initialised=true, name='FileConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[file], serviceOverrides=null}, transformer=[ErrorMessageToExceptionBean{this=b51f4, name='ErrorMessageToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class org.mule.example.errorhandler.ErrorMessage]}, ObjectToXml{this=3174f7, name='ExceptionBeanToXML', ignoreBadInput=false, returnClass=class java.lang.String, sourceTypes=[class java.lang.Object]}], name='endpoint.file.test.data.exceptions', properties={outputPattern=Exception-[UUID].xml}, transactionConfig=Transaction{factory=null, action=NONE, timeout=0}, filter=null, deleteUnacceptedMessages=false, securityFilter=null, synchronous=false, initialState=started, remoteSync=false, remoteSyncTimeout=3000, endpointEncoding=UTF-8}
DEBUG 2008-05-21 23:35:55,479 [Error Manager.2] org.mule.DefaultMuleSession: Creating event with data: org.mule.example.errorhandler.ErrorMessage, for endpoint: DefaultOutboundEndpoint{endpointUri=file://test-data/exceptions, connector=FileConnector{this=b7e998, started=true, initialised=true, name='FileConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[file], serviceOverrides=null}, transformer=[ErrorMessageToExceptionBean{this=b51f4, name='ErrorMessageToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class org.mule.example.errorhandler.ErrorMessage]}, ObjectToXml{this=3174f7, name='ExceptionBeanToXML', ignoreBadInput=false, returnClass=class java.lang.String, sourceTypes=[class java.lang.Object]}], name='endpoint.file.test.data.exceptions', properties={outputPattern=Exception-[UUID].xml}, transactionConfig=Transaction{factory=null, action=NONE, timeout=0}, filter=null, deleteUnacceptedMessages=false, securityFilter=null, synchronous=false, initialState=started, remoteSync=false, remoteSyncTimeout=3000, endpointEncoding=UTF-8}
DEBUG 2008-05-21 23:35:55,481 [Error Manager.2] org.mule.DefaultMuleSession: dispatching event: MuleEvent: 54c06ec9-27c9-11dd-a20f-13d71ad19b24, sync=false, stop processing=false, DefaultOutboundEndpoint{endpointUri=file://test-data/exceptions, connector=FileConnector{this=b7e998, started=true, initialised=true, name='FileConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[file], serviceOverrides=null}, transformer=[ErrorMessageToExceptionBean{this=b51f4, name='ErrorMessageToExceptionBean', ignoreBadInput=false, returnClass=class org.mule.example.errorhandler.ExceptionBean, sourceTypes=[class org.mule.example.errorhandler.ErrorMessage]}, ObjectToXml{this=3174f7, name='ExceptionBeanToXML', ignoreBadInput=false, returnClass=class java.lang.String, sourceTypes=[class java.lang.Object]}], name='endpoint.file.test.data.exceptions', properties={outputPattern=Exception-[UUID].xml}, transactionConfig=Transaction{factory=null, action=NONE, timeout=0}, filter=null, deleteUnacceptedMessages=false, securityFilter=null, synchronous=false, initialState=started, remoteSync=false, remoteSyncTimeout=3000, endpointEncoding=UTF-8}
DEBUG 2008-05-21 23:35:55,481 [Error Manager.2] org.mule.MuleSessionHandler: Adding session header to message: ID=547ed1e5-27c9-11dd-a20f-13d71ad19b24
DEBUG 2008-05-21 23:35:55,481 [Error Manager.2] org.mule.transformer.codec.Base64Encoder: Applying transformer Base64Encoder (org.mule.transformer.codec.Base64Encoder)
DEBUG 2008-05-21 23:35:55,481 [Error Manager.2] org.mule.transformer.codec.Base64Encoder: Object before transform: ID=547ed1e5-27c9-11dd-a20f-13d71ad19b24
DEBUG 2008-05-21 23:35:55,489 [Error Manager.2] org.mule.transformer.codec.Base64Encoder: Object after transform: SUQ9NTQ3ZWQxZTUtMjdjOS0xMWRkLWEyMGYtMTNkNzFhZDE5YjI0
DEBUG 2008-05-21 23:35:55,489 [Error Manager.2] org.mule.transformer.codec.Base64Encoder: The transformed object is of expected type. Type is: String
DEBUG 2008-05-21 23:35:55,489 [Error Manager.2] org.mule.transport.file.FileConnector: Borrowing a dispatcher for endpoint: file://test-data/exceptions
DEBUG 2008-05-21 23:35:55,494 [Error Manager.2] org.mule.transport.file.FileConnector: Borrowed a dispatcher for endpoint: file://test-data/exceptions = FileMessageDispatcher{this=13fab7, endpoint=file://test-data/exceptions, disposed=false}
DEBUG 2008-05-21 23:35:55,494 [Error Manager.2] org.mule.transport.file.FileConnector: Borrowed dispatcher: FileMessageDispatcher{this=13fab7, endpoint=file://test-data/exceptions, disposed=false}
DEBUG 2008-05-21 23:35:55,494 [Error Manager.2] org.mule.DefaultMuleMessage: new copy of message for Thread[Error Manager.2,5,main]
DEBUG 2008-05-21 23:35:55,499 [Error Manager.2] org.mule.transport.file.FileConnector: Returning dispatcher for endpoint: file://test-data/exceptions = FileMessageDispatcher{this=13fab7, endpoint=file://test-data/exceptions, disposed=false}
DEBUG 2008-05-21 23:35:55,499 [FileConnector.dispatcher.1] org.mule.DefaultMuleMessage: new copy of message for Thread[FileConnector.dispatcher.1,5,main]
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.transport.file.FileMessageDispatcher: Connecting: FileMessageDispatcher{this=13fab7, endpoint=file://test-data/exceptions, disposed=false}
INFO  2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.transport.file.FileMessageDispatcher: Connected: FileMessageDispatcher{this=13fab7, endpoint=file://test-data/exceptions, disposed=false}
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.example.errorhandler.ErrorMessageToExceptionBean: Applying transformer ErrorMessageToExceptionBean (org.mule.example.errorhandler.ErrorMessageToExceptionBean)
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.example.errorhandler.ErrorMessageToExceptionBean: Object before transform: org.mule.example.errorhandler.ErrorMessage@814af5
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.example.errorhandler.ErrorMessageToExceptionBean: Object after transform: org.mule.example.errorhandler.ExceptionBean@e154b9
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.example.errorhandler.ErrorMessageToExceptionBean: The transformed object is of expected type. Type is: ExceptionBean
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.module.xml.transformer.ObjectToXml: Applying transformer ExceptionBeanToXML (org.mule.module.xml.transformer.ObjectToXml)
DEBUG 2008-05-21 23:35:55,500 [FileConnector.dispatcher.1] org.mule.module.xml.transformer.ObjectToXml: Object before transform: org.mule.transport.DefaultMessageAdapter/org.mule.transport.DefaultMessageAdapter@4cbf96{id=/Users/andrew/Project/mule-2.0.1/examples/errorhandler/test-data/in/FatalException.xml, payload=org.mule.exa...
DEBUG 2008-05-21 23:35:55,526 [FileConnector.dispatcher.1] org.mule.module.xml.transformer.ObjectToXml: Object after transform: <org.mule.example.errorhandler.ExceptionBean>
  <detailMessage>Some fatal exception</detailMessage>
  <cause>
    <detailMessage>Some IO exception</detailMessage>
    <stackTrace>
      <string>org.mu...
DEBUG 2008-05-21 23:35:55,526 [FileConnector.dispatcher.1] org.mule.module.xml.transformer.ObjectToXml: The transformed object is of expected type. Type is: String
INFO  2008-05-21 23:35:55,528 [FileConnector.dispatcher.1] org.mule.transport.file.FileConnector: Writing file to: /Users/andrew/Project/mule-2.0.1/examples/errorhandler/test-data/exceptions/Exception-54c7c1cd-27c9-11dd-a20f-13d71ad19b24.xml
DEBUG 2008-05-21 23:35:55,529 [FileConnector.dispatcher.1] org.mule.transport.file.FileMessageDispatcher: Closing file

Can you enable debug logging for Mule? This should turn on javamail's
session debugging.

Andrew

[antoine.borg]

Hi,

Going back to this post of yours - I'm assuming that localhost does have an
SMTP server running that does not require authentication right? If this is
not the case, your properties file would be incomplete.

Also, is the SMTP server configured to only accept addresses that are valid?
I've seen this before and if this is the case, mule-alert@localhost may be
causing problems.

HTH


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: Andrew McLaughlin [mailto:andrew@...]
Sent: Wednesday, May 21, 2008 8:16 PM
To: user@...
Subject: RE: [mule-user] ErrorHandler example not emailing?


Here's the contents of my email.properties:

> #
> # Properties used to compose a message to the Mule administrator #
>
> # Substitute e-mail headers as appropriate
> email.toAddress=andrew@...
> email.fromAddress=mule-alert@localhost
> email.subject=Mule Alert
>
> # Configure properties for your outgoing mail server as needed.
> smtp.host=localhost
> smtp.port=25
> smtp.username=
> smtp.password=
>

Looks pretty straightforward. Strange thing is, my local MTA on localhost is
never called. Not even a hello. Does this example work on your machine?!

Andrew



Hi,

I've taken a quick look at the errorHandler code - can you post the content
of your email.properties file? Perhaps there's something there ....

A


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com


--
View this message in context:
http://www.nabble.com/ErrorHandler-example-not-emailing--tp17288475p17367220
.html
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew McLaughlin]

Hi Antoine,

I wish it were that easy. The MTA on localhost works fine. I use it all the time is my primary outgoing. Mule isn't even trying to connect to it, according to the mail.log.

Most important question is: Is this example working for you (or anyone else)?!

Thanks,
Andrew

Antoine Borg wrote:

Hi,

Going back to this post of yours - I'm assuming that localhost does have an
SMTP server running that does not require authentication right? If this is
not the case, your properties file would be incomplete.

Also, is the SMTP server configured to only accept addresses that are valid?
I've seen this before and if this is the case, mule-alert@localhost may be
causing problems.

HTH


Antoine Borg, Senior Consultant | Tel: [phone] | Fax: [phone]
ricston Ltd., Lincoln, 7 Ferdinand Grech Street, Lija LJA1142, MALTA
email: [e-mail] | blog: blog.ricston.com | web: ricston.com