[ 
https://issues.apache.org/jira/browse/DERBY-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kathey Marsden updated DERBY-4489:
----------------------------------

    Issue & fix info: [Newcomer, Repro attached]  (was: [Repro attached])
             Urgency: Normal
              Labels: derby_triage10_8  (was: )

Triage for 10.8.  Marking normal urgency as it seems to impact a test suite 
running against Derby. Marked newcomer as it probably would not be too hard to 
fix this one case.  In general, however it should be noted that the client is 
not well behaved and can get protocol errors and other symptoms when the server 
exits while it is still connected.  A general fix would be a bigger project.



> NetXAResource.start() throws NullPointerException when connection to server 
> is lost
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-4489
>                 URL: https://issues.apache.org/jira/browse/DERBY-4489
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.5.3.0, 10.6.1.0
>            Reporter: Knut Anders Hatlen
>              Labels: derby_triage10_8
>         Attachments: XA_NPE_Repro.java
>
>
> If you have a ClientXAConnection and then stop or restart the network server, 
> subsequent calls to XAResource.start() will fail with a NullPointerException:
> Exception in thread "main" java.lang.NullPointerException
>         at org.apache.derby.client.net.Request.sendBytes(Request.java:1415)
>         at org.apache.derby.client.net.Request.flush(Request.java:1409)
>         at org.apache.derby.client.net.NetAgent.sendRequest(NetAgent.java:387)
>         at org.apache.derby.client.net.NetAgent.flush_(NetAgent.java:267)
>         at org.apache.derby.client.am.Agent.flowOutsideUOW(Agent.java:196)
>         at 
> org.apache.derby.client.net.NetXAResource.start(NetXAResource.java:626)
>         at XA_NPE_Repro.main(XA_NPE_Repro.java:21)
> (This bug was originally seen when running failure-injection tests against 
> GlassFish with an XA connection pool and connection validation turned off.)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to