date:20080225

On Windows XP, if I start a Geronimo Tomcat 2.1 server using
bin\start-server from a command prompt, I am noticing that the server can
not be shutdown using Control+C.  So, I am using Admin Console to shutdown
the server.  But it does not return to command prompt unless I kill the java
process from Windows Task Manager.  Has anyone else came across this
problem?  Is there a JIRA for this?  Any insight into what is happening?

++Vamsi

Re: [BUILD] 2.1: Successful

Is this for 2.1.1?  If not why build 2.1 as it is already released!!

++Vamsi

On 25 Feb 2008 15:19:32 -, [EMAIL PROTECTED] wrote:

 Geronimo Revision: 630832 built with tests included

 See the full build-0800.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/build-0800.log

 Download the binaries from
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225
 [INFO] BUILD SUCCESSFUL
 [INFO]
 
 [INFO] Total time: 35 minutes 52 seconds
 [INFO] Finished at: Mon Feb 25 08:50:50 EST 2008
 [INFO] Final Memory: 294M/1013M
 [INFO]
 

 TESTSUITE RESULTS (Failures only)
 =
 See detailed results at
 http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html

 Assembly: tomcat
 =
 See the full test.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-tomcat/test.log


 Assembly: jetty
 =
 See the full test.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-jetty/test.log

Re: [BUILD] 2.1: Successful

2008-02-25 Thread Jarek Gawor

That really means 2.1 branch or 2.1.x version. I can change the
subject if that helps.

Jarek

On Mon, Feb 25, 2008 at 10:31 AM, Vamsavardhana Reddy
[EMAIL PROTECTED] wrote:
 Is this for 2.1.1?  If not why build 2.1 as it is already released!!

 ++Vamsi



 On 25 Feb 2008 15:19:32 -, [EMAIL PROTECTED] wrote:
  Geronimo Revision: 630832 built with tests included
 
  See the full build-0800.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/build-0800.log
 
  Download the binaries from
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225
  [INFO] BUILD SUCCESSFUL
  [INFO]
 
  [INFO] Total time: 35 minutes 52 seconds
  [INFO] Finished at: Mon Feb 25 08:50:50 EST 2008
  [INFO] Final Memory: 294M/1013M
  [INFO]
 
 
  TESTSUITE RESULTS (Failures only)
  =
  See detailed results at
 http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
  Assembly: tomcat
  =
  See the full test.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-tomcat/test.log
 
 
  Assembly: jetty
  =
  See the full test.log file at
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-jetty/test.log

[jira] Closed: (GERONIMO-3834) Connection pool leak when connections cannot be created

2008-02-25 Thread Donald Woods (JIRA)


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

Donald Woods closed GERONIMO-3834.
--

   Resolution: Fixed
Fix Version/s: 2.0.x
 Assignee: David Jencks  (was: Donald Woods)

2.0.3-SNAPSHOT has been published and is used by the 2.0.x server branch

 Connection pool leak when connections cannot be created
 ---

 Key: GERONIMO-3834
 URL: https://issues.apache.org/jira/browse/GERONIMO-3834
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: connector
Affects Versions: 2.0.x, 2.1, 2.1.1, 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.0.x, 2.1, 2.2


 Through the persistence of Tomasz Mazan we've discovered that the connection 
 pool leaks permits when connections are requested but cannot be created.

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

Server startup timeout setting

2008-02-25 Thread Dan Becker

While debugging and single-stepping Geronimo v2.2 under Eclipse, I 
notice the server times out and throws a signal/exception after 240s.


Eclipse complains with an Eclipse Problem Occurred dialog:
Timeout waiting for vApache Geronimo v2.2 Server at localhost to start. 
Server did not start after 240s.


Does anyone know where to set this value? I would like to get a little 
more time when I am debugging the startup. I checked 
assemblies\geronimo-tomcat6-javaee5\target\assembly\var\config\config.xml, 
but this did not seem to contain a value.


--
Thanks, Dan Becker

Re: [BUILD] 2.1: Successful

On Mon, Feb 25, 2008 at 9:18 PM, Jarek Gawor [EMAIL PROTECTED] wrote:

 That really means 2.1 branch or 2.1.x version. I can change the
 subject if that helps.

It will surely help.  Thank you.




 Jarek

 On Mon, Feb 25, 2008 at 10:31 AM, Vamsavardhana Reddy
 [EMAIL PROTECTED] wrote:
  Is this for 2.1.1?  If not why build 2.1 as it is already released!!
 
  ++Vamsi
 
 
 
  On 25 Feb 2008 15:19:32 -, [EMAIL PROTECTED] wrote:
   Geronimo Revision: 630832 built with tests included
  
   See the full build-0800.log file at
 
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/build-0800.log
  
   Download the binaries from
  http://geronimo.apache.org/maven/server/binaries/2.1/20080225
   [INFO] BUILD SUCCESSFUL
   [INFO]
  
   [INFO] Total time: 35 minutes 52 seconds
   [INFO] Finished at: Mon Feb 25 08:50:50 EST 2008
   [INFO] Final Memory: 294M/1013M
   [INFO]
  
  
   TESTSUITE RESULTS (Failures only)
   =
   See detailed results at
  http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
  
   Assembly: tomcat
   =
   See the full test.log file at
 
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-tomcat/test.log
  
  
   Assembly: jetty
   =
   See the full test.log file at
 
 http://geronimo.apache.org/maven/server/binaries/2.1/20080225/logs-0800-jetty/test.log

Re: Server startup timeout setting

2008-02-25 Thread David Jencks



On Feb 25, 2008, at 8:57 AM, Dan Becker wrote:

While debugging and single-stepping Geronimo v2.2 under Eclipse, I  
notice the server times out and throws a signal/exception after 240s.


Eclipse complains with an Eclipse Problem Occurred dialog:
Timeout waiting for vApache Geronimo v2.2 Server at localhost to  
start. Server did not start after 240s.


Does anyone know where to set this value? I would like to get a  
little more time when I am debugging the startup. I checked  
assemblies\geronimo-tomcat6-javaee5\target\assembly\var\config 
\config.xml, but this did not seem to contain a value.


This doesn't happen if you start g. using gshell with debug options  
set.  I think its part of the maven plugin or eclipse integration.


david jencks



--
Thanks, Dan Becker

Re: Server startup timeout setting

2008-02-25 Thread Dan Becker


David Jencks wrote:


On Feb 25, 2008, at 8:57 AM, Dan Becker wrote:

While debugging and single-stepping Geronimo v2.2 under Eclipse, I 
notice the server times out and throws a signal/exception after 240s.




This doesn't happen if you start g. using gshell with debug options 
set.  I think its part of the maven plugin or eclipse integration.




You are correct. gshell with debug worked for me.

--
Thanks, Dan Becker

Geronimo sessions at ApacheCon Europe 2008

Hernan,

Will you add ApacheCon Europe 2008 to the news and events pages?  Details of
Geronimo sessions are given below.

April 7-11, 2008 -- ApacheCon Europe 2008, Amsterdam
http://eu.apachecon.com/eu2008/images/buttons/basic_234x60.jpg
Conference web site: http://eu.apachecon.com/eu2008/

Friday, Apr 11 10:00 *Administering Apache Geronimo 2.x* by Vamsavardhana
Reddy
http://eu.apachecon.com/eu2008/program/talk/2514

Wednesday, Apr 09 11:30  *Securing Java EE 5.0 Applications with Apache
Geronimo* by Vamsavardhana Reddy
http://eu.apachecon.com/eu2008/program/talk/2379

Link to conference schedule --
http://eu.apachecon.com/eu2008/program/schedule

++Vamsi

Re: Geronimo sessions at ApacheCon Europe 2008

I have added it to the events page.  I could not figure how to add it to the
news page.

++Vamsi

On Mon, Feb 25, 2008 at 11:46 PM, Vamsavardhana Reddy [EMAIL PROTECTED]
wrote:

 Hernan,

 Will you add ApacheCon Europe 2008 to the news and events pages?  Details
 of Geronimo sessions are given below.

 April 7-11, 2008 -- ApacheCon Europe 2008, Amsterdam
 http://eu.apachecon.com/eu2008/images/buttons/basic_234x60.jpg
 Conference web site: http://eu.apachecon.com/eu2008/

 Friday, Apr 11 10:00 *Administering Apache Geronimo 2.x* by Vamsavardhana
 Reddy
 http://eu.apachecon.com/eu2008/program/talk/2514

 Wednesday, Apr 09 11:30  *Securing Java EE 5.0 Applications with Apache
 Geronimo* by Vamsavardhana Reddy
 http://eu.apachecon.com/eu2008/program/talk/2379

 Link to conference schedule --
 http://eu.apachecon.com/eu2008/program/schedule

 ++Vamsi

Monitoring portlet - Server with JMX as protocol has problems

In the monitoring portlet, I have added a server with JMX as the protocol.
Upon clicking, Enable Query, the following error is displayed.

*MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1:
geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring
/agent-car-jmx/2.1/car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean
*
Is this a known problem?

Re: Monitoring portlet - Server with JMX as protocol has problems

Aah...  that is the missing link.  Thanks.

++Vamsi

On Tue, Feb 26, 2008 at 12:53 AM, Erik B. Craig [EMAIL PROTECTED] wrote:

 Vamsi,
 Did you deploy the JMX Monitoring agent plugin before attempting to
 connect?

 Thanks,
 Erik B. Craig
 [EMAIL PROTECTED]




 On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote:

 In the monitoring portlet, I have added a server with JMX as the
 protocol.  Upon clicking, Enable Query, the following error is displayed.

 *MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1:
 geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring
 /agent-car-jmx/2.1/car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean
 *
 Is this a known problem?

Re: Monitoring portlet - Server with JMX as protocol has problems

2008-02-25 Thread Erik B. Craig


On that note,
While i was making sure everything was okay, seems as though the  
plugin repository we host at geronimo.apache.org is out of date for  
2.1 (version on everything is still 2.1-snapshot), and is also  
therefore lacking the JMX agent... so, heads up on that until that  
gets updated.


Thanks,
Erik B. Craig
[EMAIL PROTECTED]




On Feb 25, 2008, at 1:30 PM, Vamsavardhana Reddy wrote:


Aah...  that is the missing link.  Thanks.

++Vamsi

On Tue, Feb 26, 2008 at 12:53 AM, Erik B. Craig [EMAIL PROTECTED]  
wrote:

Vamsi,

Did you deploy the JMX Monitoring agent plugin before attempting to  
connect?


Thanks,
Erik B. Craig
[EMAIL PROTECTED]




On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote:

In the monitoring portlet, I have added a server with JMX as the  
protocol.  Upon clicking, Enable Query, the following error is  
displayed.


MRC ERROR: Snapshot thread could NOT be started on server  
127.0.0.1:  
geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent- 
car-jmx/2.1/ 
car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean


Is this a known problem?

Re: Monitoring portlet - Server with JMX as protocol has problems

2008-02-25 Thread Erik B. Craig


Vamsi,

Did you deploy the JMX Monitoring agent plugin before attempting to  
connect?


Thanks,
Erik B. Craig
[EMAIL PROTECTED]




On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote:

In the monitoring portlet, I have added a server with JMX as the  
protocol.  Upon clicking, Enable Query, the following error is  
displayed.


MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1:  
geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent- 
car-jmx/2.1/ 
car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean


Is this a known problem?

[jira] Updated: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code


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

Erik B. Craig updated GERONIMO-3833:


Affects Version/s: (was: 2.0.x)
   2.2
   2.1.1

 Hard-coded gbean names and versions in monitoring code
 --

 Key: GERONIMO-3833
 URL: https://issues.apache.org/jira/browse/GERONIMO-3833
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Jarek Gawor

 The monitoring code has hard-coded values in Java code and sql file:
 1)
 The 
 ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java
  contains the following constant:
 private static final String PATH = 
 geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo,
 name=MasterRemoteControlJMX,j2eeType=GBean;
 2)
 The  
 ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql 
 contains a bunch of the following values:
 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector'
 I'm not sure how these are used but in general these type of hardcoded values 
 should be avoided. It's really hard to maintain and keep track of.

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

[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly


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

Erik B. Craig updated GERONIMO-3685:


Fix Version/s: 2.2

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.1.1, 2.2


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

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

Re: Problem when Geronimo Tomcat 2.1 server is started using start-server

2008-02-25 Thread Kevan Miller



On Feb 25, 2008, at 10:29 AM, Vamsavardhana Reddy wrote:

On Windows XP, if I start a Geronimo Tomcat 2.1 server using bin 
\start-server from a command prompt, I am noticing that the server  
can not be shutdown using Control+C.  So, I am using Admin Console  
to shutdown the server.  But it does not return to command prompt  
unless I kill the java process from Windows Task Manager.  Has  
anyone else came across this problem?  Is there a JIRA for this?   
Any insight into what is happening?


What happens if you run 'stop-server' prior to ctrl-c? Can you  
generate a stack trace for the gsh java process after ctrl-c? I forget  
how to do this on windows 'fn - prt sc' ?


Both cases work for me on a Mac.

--kevan

[jira] Updated: (GERONIMO-3870) Expose JSR77 stats in OpenEJB


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

Erik B. Craig updated GERONIMO-3870:


Affects Version/s: 2.2
   2.1.1
   2.1
Fix Version/s: 2.2

 Expose JSR77 stats in OpenEJB
 -

 Key: GERONIMO-3870
 URL: https://issues.apache.org/jira/browse/GERONIMO-3870
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring, OpenEJB
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Erik B. Craig
 Fix For: 2.2


 There should be JSR77 compliant statistics exposed in OpenEJB so that they 
 may be monitored/tracked with the monitoring plug-in

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

[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly


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

Erik B. Craig updated GERONIMO-3685:


Affects Version/s: 2.2
   2.1.1
   2.1
Fix Version/s: (was: 2.1.1)

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.2


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

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

Re: Monitoring portlet - Server with JMX as protocol has problems

I plan to build 2.1 locally so that my local m2 repo will have the required
plugin.

++Vamsi

On Tue, Feb 26, 2008 at 1:09 AM, Erik B. Craig [EMAIL PROTECTED] wrote:

 On that note,While i was making sure everything was okay, seems as though
 the plugin repository we host at geronimo.apache.org is out of date for
 2.1 (version on everything is still 2.1-snapshot), and is also therefore
 lacking the JMX agent... so, heads up on that until that gets updated.

 Thanks,
 Erik B. Craig
 [EMAIL PROTECTED]




 On Feb 25, 2008, at 1:30 PM, Vamsavardhana Reddy wrote:

 Aah...  that is the missing link.  Thanks.

 ++Vamsi

 On Tue, Feb 26, 2008 at 12:53 AM, Erik B. Craig [EMAIL PROTECTED] wrote:

  Vamsi,
  Did you deploy the JMX Monitoring agent plugin before attempting to
  connect?
 
   Thanks,
  Erik B. Craig
  [EMAIL PROTECTED]
 
 
 
 
  On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote:
 
  In the monitoring portlet, I have added a server with JMX as the
  protocol.  Upon clicking, Enable Query, the following error is displayed.
 
  *MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1:
  geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring
  /agent-car-jmx/2.1/car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean
  *
  Is this a known problem?

[jira] Updated: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code


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

Erik B. Craig updated GERONIMO-3833:


Fix Version/s: 2.2
   2.1.1

 Hard-coded gbean names and versions in monitoring code
 --

 Key: GERONIMO-3833
 URL: https://issues.apache.org/jira/browse/GERONIMO-3833
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Jarek Gawor
 Fix For: 2.1.1, 2.2


 The monitoring code has hard-coded values in Java code and sql file:
 1)
 The 
 ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java
  contains the following constant:
 private static final String PATH = 
 geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo,
 name=MasterRemoteControlJMX,j2eeType=GBean;
 2)
 The  
 ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql 
 contains a bunch of the following values:
 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector'
 I'm not sure how these are used but in general these type of hardcoded values 
 should be avoided. It's really hard to maintain and keep track of.

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

[jira] Commented: (GERONIMO-3697) Monitoring Console fix ups


[ 
https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572200#action_12572200
 ] 

Erik B. Craig commented on GERONIMO-3697:
-

Anita, what is the status of this Jira? Do you consider it finished?

 Monitoring Console fix ups 
 ---

 Key: GERONIMO-3697
 URL: https://issues.apache.org/jira/browse/GERONIMO-3697
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1
 Environment: All
Reporter: Anita Kulshreshtha
Assignee: Anita Kulshreshtha

 This issue is for minor fixes to monitoring console and monitoring agent.

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

[jira] Updated: (GERONIMO-3682) The Monitoring Console should keep information about Stats available from a managed object


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

Erik B. Craig updated GERONIMO-3682:


Affects Version/s: 2.2
   2.1.1

 The Monitoring Console should keep information about Stats available from a 
 managed object
 --

 Key: GERONIMO-3682
 URL: https://issues.apache.org/jira/browse/GERONIMO-3682
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha

The monitoring console should do a getStats on each of the available 
 StatisticsProvider (without the query being enabled).
 It should use this information to build a DB about the nature of the 
 statistics. This information should be used to fill in the 
 default values in 'add a graph page'. Currently the description, x label, y 
 label show as empty.

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

[jira] Updated: (GERONIMO-3719) Monitoring agent uses sun classes


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

Erik B. Craig updated GERONIMO-3719:


Affects Version/s: 2.2
Fix Version/s: 2.2

 Monitoring agent uses sun classes
 -

 Key: GERONIMO-3719
 URL: https://issues.apache.org/jira/browse/GERONIMO-3719
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: David Jencks
Assignee: Viet Hung Nguyen
 Fix For: 2.1.1, 2.2


 SnapshotConfigXMLBuilder uses a couple sun classes to write out xml.  This 
 doesn't work on non-sun jvms.

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

[jira] Updated: (GERONIMO-3681) The Monitoring Console should allow the type of graph to be chosen


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

Erik B. Craig updated GERONIMO-3681:


Affects Version/s: 2.2
   2.1.1

 The Monitoring Console should allow the type of graph to be chosen
 --

 Key: GERONIMO-3681
 URL: https://issues.apache.org/jira/browse/GERONIMO-3681
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha

   The CountStatistics can be displayed in 2 ways, the raw count and the 
 throughput/utilization (count/sec). For raw count
 like ErrorCount a bar graph is more appropriate. The curvedArea is good for 
 throughput. The user should be able to choose which 
 graph style (bar, curvedArea, etc) to use.

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

[jira] Updated: (GERONIMO-3680) The Monitoring agent should optimize DB activity


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

Erik B. Craig updated GERONIMO-3680:


Affects Version/s: 2.2
   2.1.1
Fix Version/s: 2.2

 The Monitoring agent should optimize DB activity
 

 Key: GERONIMO-3680
 URL: https://issues.apache.org/jira/browse/GERONIMO-3680
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha
 Fix For: 2.2

 Attachments: view4.jpg


Currently the agent needs to be loaded in the same JVM as the server being 
 monitored. The agent skews the 
 statistics being monitered. 

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

[jira] Assigned: (GERONIMO-3869) geronimo/stop-server doesn't use connection established by deploy/connect in gshell


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

Jarek Gawor reassigned GERONIMO-3869:
-

Assignee: Jarek Gawor

 geronimo/stop-server doesn't use connection established by deploy/connect in 
 gshell
 ---

 Key: GERONIMO-3869
 URL: https://issues.apache.org/jira/browse/GERONIMO-3869
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: startup/shutdown
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Jason Warner
Assignee: Jarek Gawor
 Fix For: 2.1.1, 2.2


 When using the gshell command line to work with geronimo, hostname and 
 possibly port (depending on geronimo configuration) must be provided to 
 geronimo/stop-server even if the gshell session is already connected to that 
 remote server via deploy/connect.

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

Re: Monitoring portlet - Server with JMX as protocol has problems

2008-02-25 Thread Joe Bohn


Erik B. Craig wrote:

On that note,
While i was making sure everything was okay, seems as though the plugin 
repository we host at geronimo.apache.org is out of date for 2.1 
(version on everything is still 2.1-snapshot), and is also therefore 
lacking the JMX agent... so, heads up on that until that gets updated.




FYI, I just checked in what I think is the correct, updated 
geronimo-plugins.xml by building 2.1 and the 2.1 samples locally and 
making some minor edits to add in the license header and remove 
references to .m2/repository.  Hopefully it will be correct.  Give it 
about an hour or so to get pushed to the site.


Joe

[jira] Commented: (GERONIMO-3530) provide activemq destination and connector stats


[ 
https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572203#action_12572203
 ] 

Erik B. Craig commented on GERONIMO-3530:
-

Anita,
What is the status of this patch/jira?

 provide activemq destination and connector stats
 

 Key: GERONIMO-3530
 URL: https://issues.apache.org/jira/browse/GERONIMO-3530
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: linux, windows
Reporter: Viet Hung Nguyen
Assignee: Anita Kulshreshtha
 Fix For: 2.2

 Attachments: geronimo-3530.patch


 there are some stats that can easily be surfaced with how we use AMQ in our 
 source. These are JSR 77 compliant statistics that are being provided by AMQ 
 (DestinationStatistics and ConnectorStatistics). 

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

[jira] Updated: (GERONIMO-3530) provide activemq destination and connector stats


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

Erik B. Craig updated GERONIMO-3530:


Affects Version/s: 2.2
   2.1.1
Fix Version/s: 2.2

 provide activemq destination and connector stats
 

 Key: GERONIMO-3530
 URL: https://issues.apache.org/jira/browse/GERONIMO-3530
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: linux, windows
Reporter: Viet Hung Nguyen
Assignee: Anita Kulshreshtha
 Fix For: 2.2

 Attachments: geronimo-3530.patch


 there are some stats that can easily be surfaced with how we use AMQ in our 
 source. These are JSR 77 compliant statistics that are being provided by AMQ 
 (DestinationStatistics and ConnectorStatistics). 

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

[jira] Updated: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class


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

Erik B. Craig updated GERONIMO-3774:


Affects Version/s: 2.2
   2.1.1
Fix Version/s: 2.2

 monitoring agent should separate any constant assignment inside one class
 -

 Key: GERONIMO-3774
 URL: https://issues.apache.org/jira/browse/GERONIMO-3774
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: windows
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Trivial
 Fix For: 2.2


 There are constant variables such as DEFAULT_RETENTION that are used by both 
 the agent-jmx and agent-ejb. These constants should be placed inside a class 
 dedicated to just constants in agent-jar.

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

[BUILD] 2.2: Failed for Revision: 630973

2008-02-25 Thread gawor

Geronimo Revision: 630973 built with tests included
 
See the full build-1500.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080225/build-1500.log
 
 
See the unit test reports at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080225/unit-test-reports
 
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir: 
/home/geronimo/geronimo/trunk/plugins/mejb/geronimo-mejb/target/classes/META-INF
[INFO] Copying 2 files to 
/home/geronimo/geronimo/trunk/plugins/mejb/geronimo-mejb/target/classes/META-INF
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 1 source file to 
/home/geronimo/geronimo/trunk/plugins/mejb/geronimo-mejb/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/mejb/geronimo-mejb/target/geronimo-mejb-2.2-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-mejb-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/mejb/geronimo-mejb/target/geronimo-mejb-2.2-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/geronimo-mejb/2.2-SNAPSHOT/geronimo-mejb-2.2-SNAPSHOT.jar
[INFO] 

[INFO] Building Geronimo Plugins, MEJB :: Config
[INFO]task-segment: [install]
[INFO] 

[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir: 
/home/geronimo/geronimo/trunk/plugins/mejb/mejb/target/classes/META-INF
[INFO] Copying 2 files to 
/home/geronimo/geronimo/trunk/plugins/mejb/mejb/target/classes/META-INF
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: 
/home/geronimo/geronimo/trunk/plugins/mejb/mejb/target/resources/META-INF/plan.xml
[INFO] [car:package]
Downloading: http://download.java.net/maven/1//xerces/jars/xercesImpl-2.8.0.jar
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar
Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar
Downloading: 
http://repo1.maven.org/maven2/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar
1178K downloaded
Downloading: 
http://download.java.net/maven/1//org.apache.geronimo.components/jars/geronimo-connector-2.1.jar
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/components/geronimo-connector/2.1/geronimo-connector-2.1.jar
Downloading: 
http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/components/geronimo-connector/2.1/geronimo-connector-2.1.jar
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository/org/apache/geronimo/components/geronimo-connector/2.1/geronimo-connector-2.1.jar
Downloading: 
http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/components/geronimo-connector/2.1/geronimo-connector-2.1.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/geronimo/components/geronimo-connector/2.1/geronimo-connector-2.1.jar
98K downloaded
[INFO] snapshot org.apache.geronimo.plugins:geronimo-mejb:2.2-SNAPSHOT: 
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.plugins:geronimo-mejb:2.2-SNAPSHOT: 
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.plugins:geronimo-mejb:2.2-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] Packaging module configuration: 
/home/geronimo/geronimo/trunk/plugins/mejb/mejb/target/resources/META-INF/plan.xml
[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[INFO] Started deployer: 
org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] org/apache/openejb/jee/EjbReference
[INFO] 
[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/openejb/jee/EjbReference
at 
org.apache.openejb.config.AnnotationDeployer.init(AnnotationDeployer.java:157)
at 
org.apache.openejb.config.ConfigurationFactory.init(ConfigurationFactory.java:166)
at 
org.apache.openejb.config.ConfigurationFactory.init(ConfigurationFactory.java:110)
at 
org.apache.geronimo.openejb.deployment.EjbModuleBuilder.configureApplication

[jira] Commented: (GERONIMO-3869) geronimo/stop-server doesn't use connection established by deploy/connect in gshell


[ 
https://issues.apache.org/jira/browse/GERONIMO-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572221#action_12572221
 ] 

Jarek Gawor commented on GERONIMO-3869:
---

Committed changes to trunk (revision 630982) that enable the 
geronimo/stop-server command to reuse the connection from the deploy/connect 
command. These changes also included the following fixes:
1) The deploy/connect command will now automatically disconnect the previous 
cached connection.
2) The deploy/disconnect command will remove the connection from cache even if 
connection.close() fails.


 geronimo/stop-server doesn't use connection established by deploy/connect in 
 gshell
 ---

 Key: GERONIMO-3869
 URL: https://issues.apache.org/jira/browse/GERONIMO-3869
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: startup/shutdown
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Jason Warner
Assignee: Jarek Gawor
 Fix For: 2.1.1, 2.2


 When using the gshell command line to work with geronimo, hostname and 
 possibly port (depending on geronimo configuration) must be provided to 
 geronimo/stop-server even if the gshell session is already connected to that 
 remote server via deploy/connect.

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

[jira] Resolved: (GERONIMO-3869) geronimo/stop-server doesn't use connection established by deploy/connect in gshell


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

Jarek Gawor resolved GERONIMO-3869.
---

Resolution: Fixed

Committed the same set of changes to branches/2.1 (revision 630987).


 geronimo/stop-server doesn't use connection established by deploy/connect in 
 gshell
 ---

 Key: GERONIMO-3869
 URL: https://issues.apache.org/jira/browse/GERONIMO-3869
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: startup/shutdown
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: Jason Warner
Assignee: Jarek Gawor
 Fix For: 2.1.1, 2.2


 When using the gshell command line to work with geronimo, hostname and 
 possibly port (depending on geronimo configuration) must be provided to 
 geronimo/stop-server even if the gshell session is already connected to that 
 remote server via deploy/connect.

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

[jira] Resolved: (GERONIMODEVTOOLS-280) Remove Runtime from the Server Runtime view

2008-02-25 Thread Tim McConnell (JIRA)


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

Tim McConnell resolved GERONIMODEVTOOLS-280.


   Resolution: Fixed
Fix Version/s: 2.1.0

Fixed with revision 631023 changes

 Remove Runtime from the Server Runtime view
 ---

 Key: GERONIMODEVTOOLS-280
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-280
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.0
Reporter: Jacek Laskowski
Assignee: Tim McConnell
 Fix For: 2.1.0


 Upon defining a new server runtime all Geronimos show as Apache Geronimo vX.Y 
 whereas Apache Geronimo v2.1 as Apache Geronimo v2.1 Runtime. Runtime should 
 be removed as it's inconsistent at the very least.

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

[jira] Closed: (GERONIMODEVTOOLS-284) Geronimo 2.1 server runtime name is inappropriate.

2008-02-25 Thread Tim McConnell (JIRA)


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

Tim McConnell closed GERONIMODEVTOOLS-284.
--

   Resolution: Fixed
Fix Version/s: 2.1.0

Closing as a duplicate of GERONIMODEVTOOLS-280, which is now resolved.

 Geronimo 2.1 server runtime name is inappropriate.
 --

 Key: GERONIMODEVTOOLS-284
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-284
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.0
 Environment: Eclipse WTP 2.0 (Release Build: R-2.0.1-20070926042742)
Reporter: Kan Ogawa
Assignee: Tim McConnell
 Fix For: 2.1.0

 Attachments: GERONIMODEVTOOLS-284.patch, New-Server-Runtime-Wizard.jpg




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

Too many levels of menu before content in docs?

2008-02-25 Thread David Jencks


This seems a wee bit excessive to me...

Documentation  Administration  Administrative Tasks   
Administering applications  Installing and removing applications


Can we get expandable trees in the Documentation page?  If so I think  
the links on Documentation should take you directly to documentation


If not I'd be happier with a maximum of 1 layer of additional menus

thanks
david jencks

[jira] Updated: (GERONIMO-3861) cookies need to be validated and filtered

2008-02-25 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated GERONIMO-3861:
--

Attachment: GERONIMO-3861.patch

I'm submitting a suggested fix. Please take a look at it, and let me know if
you would like to discuss some of the elements of the fix...

- Created an interface that encapsulates the cookie validation strategy:
CookiePolicy.
- Provided a couple of implementations: DefaultCookiePolicy NullCookiePolicy.
- When parsing incoming cookies, provide default values for domain path
attributes if either is missing.
- To do the above, HttpResponseMessage now has a reference to the request URL
(I did not add a reference to the HttpRequestMessage object as I think it's bit
more heavyweight than retaining the request URL).
- CookiePolicy is set on AsyncHttpClient, and is transferred to
HttpRequestMessage when messages are sent.
- The default CookiePolicy is DefaultCookiePolicy.
- Wrote unit tests for cookie validation.

It is working as expected, but I think some details still have room for
discussion. I'd love to hear your thoughts.

Thanks,
Sangjin

cookies need to be validated and filtered
-

Key: GERONIMO-3861
URL: https://issues.apache.org/jira/browse/GERONIMO-3861
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: AsyncHttpClient
Affects Versions: 1.x
Reporter: Sangjin Lee
Assignee: Rick McGuire
Priority: Minor
Attachments: GERONIMO-3861.patch

Today AHC simply accepts all cookies from the response and emit all cookies
in the request. However, the attributes need to be taken into consideration
when we set the cookies as well as when we send them. Two parts of the issue:
[1] When we emit the cookies in the request, we need to check
- if the domain matches
- if the path matches
- if the cookie has not expired
- and if the cookie is secure (if the request protocol is http)
before adding it to the Cookie header.
[2] When we accept the cookies in the response, we need to check for the
domain and the path. Note that we do not discard expired cookies, as that's
often a way to delete an existing cookie.

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

Re: svn commit: r631012 - in /geronimo/server/trunk/plugins/openejb/geronimo-openejb: pom.xml src/main/resources/META-INF/geronimo-dependency.xml

2008-02-25 Thread David Blevins


Thanks for this.  Excellent change.

-David

On Feb 25, 2008, at 1:49 PM, [EMAIL PROTECTED] wrote:


Author: gawor
Date: Mon Feb 25 13:49:02 2008
New Revision: 631012

URL: http://svn.apache.org/viewvc?rev=631012view=rev
Log:
less maintainace headaches

Modified:
   geronimo/server/trunk/plugins/openejb/geronimo-openejb/pom.xml
   geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/ 
resources/META-INF/geronimo-dependency.xml


Modified: geronimo/server/trunk/plugins/openejb/geronimo-openejb/ 
pom.xml

URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/openejb/geronimo-openejb/pom.xml?rev=631012r1=631011r2=631012view=diff
= 
= 
= 
= 
= 
= 
= 
= 
==
--- geronimo/server/trunk/plugins/openejb/geronimo-openejb/pom.xml  
(original)
+++ geronimo/server/trunk/plugins/openejb/geronimo-openejb/pom.xml  
Mon Feb 25 13:49:02 2008

@@ -146,4 +146,13 @@
/dependency
/dependencies

+build
+resources
+resource
+directorysrc/main/resources/directory
+filteringtrue/filtering
+/resource
+/resources
+/build
+
/project

Modified: geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/ 
main/resources/META-INF/geronimo-dependency.xml

URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/resources/META-INF/geronimo-dependency.xml?rev=631012r1=631011r2=631012view=diff
= 
= 
= 
= 
= 
= 
= 
= 
==
--- geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/ 
resources/META-INF/geronimo-dependency.xml (original)
+++ geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/ 
resources/META-INF/geronimo-dependency.xml Mon Feb 25 13:49:02 2008

@@ -20,32 +20,32 @@
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-loader/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-ejbd/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-server/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-client/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-javaagent/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.openejb/groupId
  artifactIdopenejb-jee/artifactId
-  version3.0.0-SNAPSHOT/version
+  version${openejbVersion}/version
/dependency
dependency
  groupIdorg.apache.xbean/groupId

[jira] Assigned: (GERONIMO-3828) Provide jaxws-tools stack traces to the server.log


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

Jarek Gawor reassigned GERONIMO-3828:
-

Assignee: Jarek Gawor

 Provide jaxws-tools stack traces to the server.log
 --

 Key: GERONIMO-3828
 URL: https://issues.apache.org/jira/browse/GERONIMO-3828
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: webservices, Wish List
Reporter: Cedric Hurst
Assignee: Jarek Gawor

 Even with the logging level set to DEBUG, if jaxws-tools throws an Exception, 
 it does not seem to show up in the server log or console output.  This seems 
 to be the case even if -Dorg.apache.geronimo.jaxws.wsgen.fork=false is set. 
  Logging the output of wsgen is critical to debug issues with @WebService 
 classes.

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

[jira] Assigned: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin