Re: Build problems
I had this problem and re-built oejb and its fine now. I was't able to deploy the new version as I'm travelling. Hope this helps. Matt Hogstrom (919)656-0564 On Dec 20, 2007, at 14:57, Erik B. Craig [EMAIL PROTECTED] wrote: All, Has anyone else been experiencing problems building since yesterday? Attempting to build trunk with a clean repo, and it's breaking on the mejb plan.xml [INFO] snapshot org.apache.geronimo.applications:geronimo-mejb:2.1- SNAPSHOT: checking for updates from apache.snapshots [INFO] Packaging module configuration: /home/ebcraig/g-src/trunk/ applications/mejb/mejb/target/resources/META-INF/plan.xml [INFO] --- - [ERROR] BUILD ERROR [INFO] --- - [INFO] java.lang.NullPointerException [INFO] --- - [INFO] For more information, run Maven with the -e switch [INFO] --- - [INFO] Total time: 20 minutes 13 seconds [INFO] Finished at: Thu Dec 20 13:48:24 CST 2007 [INFO] Final Memory: 299M/395M [INFO] --- - -- Thanks, Erik B. Craig [EMAIL PROTECTED]
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: geronimo-3714.patch The root cause of this is because the skipCount value is equal to 0 in some instances because of integer division. With skipCount = 0, it is meaningless to the method getSpecificStatistics() in the agent. Whenever this happens, I set skipCount = 1, meaning, grab each snapshot without skipping any in between. Additionally, I also reformatted the MRCConnector.java to abide by the Apache Geronimo coding standards specified at http://geronimo.apache.org/coding-standards.html. Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3717) Queries provided through the URL argument to HttpRequestMessage get lost
Queries provided through the URL argument to HttpRequestMessage get lost Key: GERONIMO-3717 URL: https://issues.apache.org/jira/browse/GERONIMO-3717 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee There are two different ways of providing a query parameter to HttpRequestMessage, and both ways should be supported. One way is through the URL argument in the HttpRequestMessage constructor, and the other is via HttpRequestMessage.setParameter(). However, if you supply a query parameter via the former, it gets lost, and is not sent. For example, suppose you want to make a request to http://some_host/path?foo=bar;. One way to construct the request object is HttpRequestMessage msg = new HttpRequestMessage(new URL(http://some_host/path?foo=bar;, cb); The other way is HttpRequestMessage msg = new HttpRequestMessage(new URL(http://some_host/path;), cb); msg.setParameter(foo, bar); However, the encoder (HttpRequestEncoder) uses only URL.getPath() (which returns only /path in this example) to form the request line. The correct method it should have used is URL.getFile() (which returns /path?foo=bar in this example). It is apparent that AHC expects to support both usages, as there is code that tries to add any parameter in addition to any existing queries already in the URL, except it's not done quite right. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: (was: geronimo-3714.patch) Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: geronimo-3714.patch I forgot to add the JS checks to ensure that the user cannot specify anything less than 2*(snapshot_duration) for the graph's time window. So I have added that stuff in this new patch Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3717) Queries provided through the URL argument to HttpRequestMessage get lost
[ https://issues.apache.org/jira/browse/GERONIMO-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3717: -- Attachment: 3717.patch a suggested fix Queries provided through the URL argument to HttpRequestMessage get lost Key: GERONIMO-3717 URL: https://issues.apache.org/jira/browse/GERONIMO-3717 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Attachments: 3717.patch There are two different ways of providing a query parameter to HttpRequestMessage, and both ways should be supported. One way is through the URL argument in the HttpRequestMessage constructor, and the other is via HttpRequestMessage.setParameter(). However, if you supply a query parameter via the former, it gets lost, and is not sent. For example, suppose you want to make a request to http://some_host/path?foo=bar;. One way to construct the request object is HttpRequestMessage msg = new HttpRequestMessage(new URL(http://some_host/path?foo=bar;, cb); The other way is HttpRequestMessage msg = new HttpRequestMessage(new URL(http://some_host/path;), cb); msg.setParameter(foo, bar); However, the encoder (HttpRequestEncoder) uses only URL.getPath() (which returns only /path in this example) to form the request line. The correct method it should have used is URL.getFile() (which returns /path?foo=bar in this example). It is apparent that AHC expects to support both usages, as there is code that tries to add any parameter in addition to any existing queries already in the URL, except it's not done quite right. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3714: --- Assignee: Erik B. Craig (was: Viet Hung Nguyen) Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
