[esb-issues] [JBoss JIRA] (JBESB-3854) NPE in SqlTableGatewayListener when Oracle goes down

[RH Bugzilla Integration (JIRA)]

     [ https://issues.jboss.org/browse/JBESB-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated JBESB-3854:
-------------------------------------------

    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=861907

    
> NPE in SqlTableGatewayListener when Oracle goes down
> ----------------------------------------------------
>
>                 Key: JBESB-3854
>                 URL: https://issues.jboss.org/browse/JBESB-3854
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>    Affects Versions: 4.9 CP2
>            Reporter: Tom Cunningham
>            Assignee: Tom Cunningham
>             Fix For: 4.9 CP2
>
>
> Description of problem:
> Listener is not fetching the data from the database after the Data source disconnect and reconnect. To resolve the issue we have to redeploy the esb.
> Version-Release number of selected component (if applicable):
> JBoss SOA-P 5.2.0
> How reproducible:
> always
> Steps to Reproduce:
> 1. deploy ESB project which uses SQL listener
> 2. restart database, wait few minutes
> 3. notice that SQL listener is stopped
>   
> Actual results:
> SQL listener not polling
> Expected results:
> SQL listener polling
> Additional info:
> Proposed fix:
> Index: src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java
> ===================================================================
> --- src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java	(revision 37737)
> +++ src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java	(working copy)
> @@ -507,7 +507,7 @@
>          	    RS.close();
>          	
>                  oConn.rollback();
> -            } catch (final SQLException sqle) {
> +            } catch (Exception ex) {
>              	refreshDatasource();
>              }

--
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