You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2005/02/24 23:51:48 UTC
[jira] Created: (DERBY-154) Does Network Server support scroll sensitive read-only and updatable resultsets?
Does Network Server support scroll sensitive read-only and updatable resultsets?
--------------------------------------------------------------------------------
Key: DERBY-154
URL: http://issues.apache.org/jira/browse/DERBY-154
Project: Derby
Type: Bug
Components: Network Server
Versions: 10.0.2.1
Reporter: Mamta A. Satoor
Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
SQLWarning warnings = con.getWarnings();
while (warnings != null)
{
System.out.println("warnings on connection = " + warnings);
warnings = warnings.getNextWarning();
}
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
And the output in Network Server mode for above test case is
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_UPDATABLE? true
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-154) Network Client should not allow
creation of statements with scroll sensitive read-only and updatable
resultsets?
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731156#action_12731156 ]
Myrna van Lunteren commented on DERBY-154:
------------------------------------------
[10.5.2 Triage]
I made a repro using the Derby Net client instead of the JCC driver
( Connection con = DriverManager.getConnection("jdbc:derby://localhost:1527/db1drda;create=true;");)
and got the following output:
Did we get TYPE_SCROLL_SENSITIVE? false
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? false
Did we get CONCUR_UPDATABLE? true
The output for embedded is exactly the same.
As we no longer cater towards the JCC driver, I don't think there's anything more to do here.
> Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets?
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-154
> URL: https://issues.apache.org/jira/browse/DERBY-154
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.0.2.1
> Reporter: Mamta A. Satoor
>
> Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
> Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
> Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
> SQLWarning warnings = con.getWarnings();
> while (warnings != null)
> {
> System.out.println("warnings on connection = " + warnings);
> warnings = warnings.getNextWarning();
> }
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
> s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
> And the output in Network Server mode for above test case is
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_READ_ONLY? true
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_UPDATABLE? true
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-154) Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets?
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-154?page=all ]
Kathey Marsden updated DERBY-154:
---------------------------------
Component: Network Client
(was: Network Server)
Summary: Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets? (was: Does Network Server support scroll sensitive read-only and updatable resultsets?)
Description:
Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
SQLWarning warnings = con.getWarnings();
while (warnings != null)
{
System.out.println("warnings on connection = " + warnings);
warnings = warnings.getNextWarning();
}
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
And the output in Network Server mode for above test case is
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_UPDATABLE? true
was:
Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
SQLWarning warnings = con.getWarnings();
while (warnings != null)
{
System.out.println("warnings on connection = " + warnings);
warnings = warnings.getNextWarning();
}
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
And the output in Network Server mode for above test case is
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_UPDATABLE? true
Environment:
> Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets?
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-154
> URL: http://issues.apache.org/jira/browse/DERBY-154
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.0.2.1
> Reporter: Mamta A. Satoor
>
> Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
> Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
> Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
> SQLWarning warnings = con.getWarnings();
> while (warnings != null)
> {
> System.out.println("warnings on connection = " + warnings);
> warnings = warnings.getNextWarning();
> }
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
> s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
> And the output in Network Server mode for above test case is
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_READ_ONLY? true
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_UPDATABLE? true
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-154) Does Network Server support scroll sensitive read-only and updatable resultsets?
Posted by Mamta Satoor <ms...@gmail.com>.
On Thu, 03 Mar 2005 14:49:16 +0530, Shreyas Kaushik
<Sh...@sun.com> wrote:
> Just to clarify, does this mean that using the JCC driver I can have
> scrollable updatabale ResultSets although Derby
> does not support it ?
>
> thanks
> Shreyas
>
> Mamta A. Satoor (JIRA) wrote:
>
> > [ http://issues.apache.org/jira/browse/DERBY-154?page=comments#action_60102 ]
> >
> >Mamta A. Satoor commented on DERBY-154:
> >---------------------------------------
> >
> >I did some looking through the JCC driver code and the problem is in how JCC class Connection.java handles resultset type downgrading. Since Derby does not support scroll sensitive resultsets, JCC code should downgrade resultset type to scroll insensitive. I will try to work with the JCC team on this. People working on the Derby Net Client - similar change might be necessary in the Derby Net Client code too.
> >
> >
> >
> >>Does Network Server support scroll sensitive read-only and updatable resultsets?
> >>--------------------------------------------------------------------------------
> >>
> >> Key: DERBY-154
> >> URL: http://issues.apache.org/jira/browse/DERBY-154
> >> Project: Derby
> >> Type: Bug
> >> Components: Network Server
> >> Versions: 10.0.2.1
> >> Reporter: Mamta A. Satoor
> >>
> >>
> >
> >
> >
> >>Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
> >>Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
> >>Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
> >>SQLWarning warnings = con.getWarnings();
> >>while (warnings != null)
> >>{
> >> System.out.println("warnings on connection = " + warnings);
> >> warnings = warnings.getNextWarning();
> >>}
> >>System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> >>System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
> >>s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
> >>System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> >>System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
> >>And the output in Network Server mode for above test case is
> >>Did we get TYPE_SCROLL_SENSITIVE? true
> >>Did we get CONCUR_READ_ONLY? true
> >>Did we get TYPE_SCROLL_SENSITIVE? true
> >>Did we get CONCUR_UPDATABLE? true
> >>
> >>
> >
> >
> >
>
No, there is no scrollable resultset support both in embedded and
Network Server mode (coming through JCC or soon to be available Derby
Net Client).
thanks,
Mamta
Re: [jira] Commented: (DERBY-154) Does Network Server support scroll
sensitive read-only and updatable resultsets?
Posted by Shreyas Kaushik <Sh...@Sun.COM>.
Just to clarify, does this mean that using the JCC driver I can have
scrollable updatabale ResultSets although Derby
does not support it ?
thanks
Shreyas
Mamta A. Satoor (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-154?page=comments#action_60102 ]
>
>Mamta A. Satoor commented on DERBY-154:
>---------------------------------------
>
>I did some looking through the JCC driver code and the problem is in how JCC class Connection.java handles resultset type downgrading. Since Derby does not support scroll sensitive resultsets, JCC code should downgrade resultset type to scroll insensitive. I will try to work with the JCC team on this. People working on the Derby Net Client - similar change might be necessary in the Derby Net Client code too.
>
>
>
>>Does Network Server support scroll sensitive read-only and updatable resultsets?
>>--------------------------------------------------------------------------------
>>
>> Key: DERBY-154
>> URL: http://issues.apache.org/jira/browse/DERBY-154
>> Project: Derby
>> Type: Bug
>> Components: Network Server
>> Versions: 10.0.2.1
>> Reporter: Mamta A. Satoor
>>
>>
>
>
>
>>Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
>>Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
>>Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
>>SQLWarning warnings = con.getWarnings();
>>while (warnings != null)
>>{
>> System.out.println("warnings on connection = " + warnings);
>> warnings = warnings.getNextWarning();
>>}
>>System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
>>System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
>>s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
>>System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
>>System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
>>And the output in Network Server mode for above test case is
>>Did we get TYPE_SCROLL_SENSITIVE? true
>>Did we get CONCUR_READ_ONLY? true
>>Did we get TYPE_SCROLL_SENSITIVE? true
>>Did we get CONCUR_UPDATABLE? true
>>
>>
>
>
>
[jira] Commented: (DERBY-154) Does Network Server support scroll sensitive read-only and updatable resultsets?
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-154?page=comments#action_60102 ]
Mamta A. Satoor commented on DERBY-154:
---------------------------------------
I did some looking through the JCC driver code and the problem is in how JCC class Connection.java handles resultset type downgrading. Since Derby does not support scroll sensitive resultsets, JCC code should downgrade resultset type to scroll insensitive. I will try to work with the JCC team on this. People working on the Derby Net Client - similar change might be necessary in the Derby Net Client code too.
> Does Network Server support scroll sensitive read-only and updatable resultsets?
> --------------------------------------------------------------------------------
>
> Key: DERBY-154
> URL: http://issues.apache.org/jira/browse/DERBY-154
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.0.2.1
> Reporter: Mamta A. Satoor
>
> Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
> Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
> Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
> SQLWarning warnings = con.getWarnings();
> while (warnings != null)
> {
> System.out.println("warnings on connection = " + warnings);
> warnings = warnings.getNextWarning();
> }
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
> s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
> And the output in Network Server mode for above test case is
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_READ_ONLY? true
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_UPDATABLE? true
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-154) Network Client should not allow
creation of statements with scroll sensitive read-only and updatable
resultsets?
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-154.
--------------------------------------
Resolution: Won't Fix
I chose to resolve as won't fix to reflect that we're not going to pursue changes for the JCC Driver.
> Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets?
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-154
> URL: https://issues.apache.org/jira/browse/DERBY-154
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.0.2.1
> Reporter: Mamta A. Satoor
>
> Derby in embedded mode does not support scroll sensitive resultsets in both read-only and updatable modes. But when I write a simple test program in Network Server configuration, it appears that scroll sensitive resultsets are supported both in read-only and updatable modes. Is that correct?
> Connection con = DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;", "app", "app");
> Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
> SQLWarning warnings = con.getWarnings();
> while (warnings != null)
> {
> System.out.println("warnings on connection = " + warnings);
> warnings = warnings.getNextWarning();
> }
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_READ_ONLY? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));
> s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
> System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " + (s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
> System.out.println("Did we get CONCUR_UPDATABLE? " + (s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));
> And the output in Network Server mode for above test case is
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_READ_ONLY? true
> Did we get TYPE_SCROLL_SENSITIVE? true
> Did we get CONCUR_UPDATABLE? true
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.