You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Vanjikumaran Sivajothy (JIRA)" <ji...@apache.org> on 2017/09/24 19:50:00 UTC
[jira] [Commented] (SYNAPSE-1057) Spelling mistake and un handled
exceptions
[ https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178340#comment-16178340 ]
Vanjikumaran Sivajothy commented on SYNAPSE-1057:
-------------------------------------------------
Configuration for reproducing the issue.
{code}
<dblookup>
<connection>
<pool>
<password>admin</password>
<user>test123</user>
<url>jdbc:mysql://localhost:3306/TESTDB</url>
<driver>com.mysql.jdbc.Driver</driver>
</pool>
</connection>
<statement>
<sql>SELECT * FROM employee WHERE name =?</sql>
<parameter value="STRINGVALUE" type="INTEGER"/>
<result name="company_id" column="id"/>
</statement>
</dblookup>
{code}
Observation
{code}
ERROR {org.apache.synapse.mediators.db.DBLookupMediator} - Error executing statement : SELECT * FROM employee WHERE name =? against DataSource : jdbc:mysql://localhost:3306/TESTDB {org.apache.synapse.mediators.db.DBLookupMediator}
java.lang.NumberFormatException: For input string: "STRINGVALUE"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:492)
at java.lang.Integer.parseInt(Integer.java:527)
at org.apache.synapse.mediators.db.AbstractDBMediator.getPreparedStatement(AbstractDBMediator.java:338)
at org.apache.synapse.mediators.db.DBLookupMediator.processStatement(DBLookupMediator.java:45)
{code}
> Spelling mistake and un handled exceptions
> ------------------------------------------
>
> Key: SYNAPSE-1057
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1057
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Vanjikumaran Sivajothy
> Assignee: Vanjikumaran Sivajothy
> Priority: Minor
> Labels: patch
> Fix For: FUTURE
>
> Attachments: SYNAPSE1057.patch
>
>
> When DBLookup/DBreport exception happens, The flow doesn't go to faultSequence as the handled exception.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org