You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jeff Genender (JIRA)" <de...@geronimo.apache.org> on 2006/02/27 22:38:45 UTC

[jira] Created: (GERONIMO-1658) NPE in the ConnectionTrackingCoordinator with Roller

NPE in the ConnectionTrackingCoordinator with Roller
----------------------------------------------------

         Key: GERONIMO-1658
         URL: http://issues.apache.org/jira/browse/GERONIMO-1658
     Project: Geronimo
        Type: Bug
  Components: connector  
    Versions: 1.0, 1.0.1, 1.1, 1.x    
    Reporter: Jeff Genender


An NPE exception occurs in the ConnectionTrackingCoordinator when running Roller weblogger.  On line 127, the infos is null, so for some reason the line:

Set infos = (Set)resources.get(connectionTrackingInterceptor);

is returning null.  I set a null guard around line 127 to test for the null which gets rid of the error.  But we should look at why it's returning null in the first place.

To reporduce, follow the instructions found here:

http://www.savoirtech.com/roller/page/jgenender/20060227

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


[jira] Assigned: (GERONIMO-1658) NPE in the ConnectionTrackingCoordinator with Roller

Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1658?page=all ]

David Jencks reassigned GERONIMO-1658:
--------------------------------------

    Assign To: David Jencks

> NPE in the ConnectionTrackingCoordinator with Roller
> ----------------------------------------------------
>
>          Key: GERONIMO-1658
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1658
>      Project: Geronimo
>         Type: Bug
>   Components: connector
>     Versions: 1.0, 1.1, 1.x, 1.0.1
>     Reporter: Jeff Genender
>     Assignee: David Jencks

>
> An NPE exception occurs in the ConnectionTrackingCoordinator when running Roller weblogger.  On line 127, the infos is null, so for some reason the line:
> Set infos = (Set)resources.get(connectionTrackingInterceptor);
> is returning null.  I set a null guard around line 127 to test for the null which gets rid of the error.  But we should look at why it's returning null in the first place.
> To reporduce, follow the instructions found here:
> http://www.savoirtech.com/roller/page/jgenender/20060227

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


[jira] Closed: (GERONIMO-1658) NPE in the ConnectionTrackingCoordinator with Roller

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-1658.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta1
                   1.2

According to Peter Petersson it's possible to run sufficiently recent rollers on geronimo 1.2 and 2.0.  See GERONIMO-2994

> NPE in the ConnectionTrackingCoordinator with Roller
> ----------------------------------------------------
>
>                 Key: GERONIMO-1658
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1658
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector
>    Affects Versions: 1.0, 1.1, 1.2, 1.x
>            Reporter: Jeff Genender
>         Assigned To: David Jencks
>             Fix For: 1.2, 2.0-beta1
>
>
> An NPE exception occurs in the ConnectionTrackingCoordinator when running Roller weblogger.  On line 127, the infos is null, so for some reason the line:
> Set infos = (Set)resources.get(connectionTrackingInterceptor);
> is returning null.  I set a null guard around line 127 to test for the null which gets rid of the error.  But we should look at why it's returning null in the first place.
> To reporduce, follow the instructions found here:
> http://www.savoirtech.com/roller/page/jgenender/20060227

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.