date:20080201

Results page of plugin install having issues handling array config
--

 Key: GERONIMO-3800
 URL: https://issues.apache.org/jira/browse/GERONIMO-3800
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Reporter: Joseph Leong
Assignee: Joseph Leong
Priority: Minor


The result page summarizing the installations that has occurred in the plugin 
installer is having issues handling the new config arrays.

Will be fixed shortly with the master page at Jira 3746

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

[jira] Commented: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Joseph Leong commented on GERONIMO-3746:


The continue form page isn't resolving the CRSF issue, will explicitly handle 
this with a new session pairing.

 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
 Attachments: GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

How to figure what port is in use from a BindException

2008-02-01 Thread Vamsavardhana Reddy

Very often I run into Geronimo startup failure with a BindException since
some port or the other is in use.  Then I change the PortOffset to get
going.  How do I figure which port/address is resulting in the exception?

[jira] Commented: (GERONIMO-3769) artifactory 1.2.2 deployment is failing on 2.1

2008-02-01 Thread Joe Bohn (JIRA)


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

Joe Bohn commented on GERONIMO-3769:


I moved plexus to the confg/plugin from j2ee-system and that part seemed to go 
fine (the server worked fine and I could still export a new server that was 
functional).  However, it did not resolve the problem here with artifactory.  
Actually, it seemed to make things worse as I received some strange spring 
exception on deploy.  I'll have to set-up my environment again to get the 
details on the exception and dig more into those failures (I got distracted 
with validating specs and attempting to switch saaj spec).

 artifactory 1.2.2 deployment is failing on 2.1
 --

 Key: GERONIMO-3769
 URL: https://issues.apache.org/jira/browse/GERONIMO-3769
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1
Reporter: Kevan Miller
Assignee: Joe Bohn
 Fix For: 2.1


 A deploy of artifactory is failing on 2.1. Same deploy works on 2.0.2. I'm 
 seeing the following exceptions on the server:
 Second exception is most significant, I think:
 2008-01-20 12:42:22,616 [ERROR] 0.0].[/artifactory]   - Exception sending 
 context initialized event to listener instance of class 
 org.artifactory.webapp.servlet.ArtifactoryContextConfigurer
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'maven' defined in ServletContext resource 
 [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested 
 exception is org.springframework.beans.BeanInstantiationException: Could not 
 instantiate bean class [org.artifactory.maven.Maven]: Constructor threw 
 exception; nested exception is java.lang.NoClassDefFoundError: 
 org/codehaus/classworlds/NoSuchRealmException
 Caused by: 
 org.springframework.beans.BeanInstantiationException: Could not instantiate 
 bean class [org.artifactory.maven.Maven]: Constructor threw exception; nested 
 exception is java.lang.NoClassDefFoundError: 
 org/codehaus/classworlds/NoSuchRealmException
 Caused by: 
 java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException
 at org.codehaus.plexus.embed.Embedder.init(Embedder.java:62)
 at 
 org.apache.maven.embedder.MavenEmbedder.start(MavenEmbedder.java:582)
 at org.artifactory.maven.Maven.init(Maven.java:99)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)
 at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at 
 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:85)
 at 
 org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)
 at 
 org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:170)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:773)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:716)
 at 
 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:386)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
 at 
 org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
 at 
 org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
 at 
 org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:279)
 at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:360)
 at 
 org.artifactory.webapp.servlet.ArtifactoryContextConfigurer.contextInitialized(ArtifactoryContextConfigurer.java:45)
 at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3826)
 at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4327)
 at 
 org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:60)
 at

Re: [VOTE] Release the specs



On Feb 1, 2008, at 2:46 AM, Guillaume Nodet wrote:


What do you mean by skipped version numbers and different formats ?


By format, I meant the new, non-standard tags/specs-1.4 destination.  
By skipped version numbers -- the current released version of  
annotations is 1.0, the previous vote was for 1.1.1, and this vote was  
for 1.1.2 (IIRC). Looks like in your new vote, the version number is  
back to 1.1.1.


--kevan

[jira] Commented: (GERONIMO-2758) Upgrade to Howl 1.0.2


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

Kevan Miller commented on GERONIMO-2758:


Ah. Thanks for the info. Futures sounds good to me. I'd rather not create a 
private build, without more justification.

 Upgrade to Howl 1.0.2
 -

 Key: GERONIMO-2758
 URL: https://issues.apache.org/jira/browse/GERONIMO-2758
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: dependencies
Affects Versions: 2.0-M5
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.1


 Howl 1.0.2 was released on 2007-01-02, but has not been published to the m2 
 repo yet.
 Will attach a patch once the jar is available on the default m2 repo.

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

Re: How to figure what port is in use from a BindException

2008-02-01 Thread Upul Godage

You can use a tool like netstat to check which ports programs are listening
on at the moment and unusable by the server instance.
netstat -anb
You can find which ports the server instance will use by the
config.substitutions.properties entries.

Upul


On Feb 1, 2008 6:38 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:

 Very often I run into Geronimo startup failure with a BindException since
 some port or the other is in use.  Then I change the PortOffset to get
 going.  How do I figure which port/address is resulting in the exception?

Re: [ANNOUNCE] Viet Nguyen as Geronimo's most recent committer

2008-02-01 Thread Donald Woods


Congrats and welcome aboard!

-Donald

Kevan Miller wrote:

All,
I'd like to welcome Viet Nguyen as a new committer on the Geronimo 
project. Viet has made a number of contributions to Geronimo, including 
our new monitoring capabilities, the J2G conversion tool, as well as a 
number of bug fixes, and other helpful contributions.


Let's lay some props on Viet!

--kevan 



smime.p7s
Description: S/MIME Cryptographic Signature

[jira] Closed: (GERONIMO-2550) Plugin enhancement to allow the download of a Zip/Jar bundle and extraction location outside repository

2008-02-01 Thread Donald Woods (JIRA)


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

Donald Woods closed GERONIMO-2550.
--

Resolution: Won't Fix

OK, I'll give it a try on 2.1 and open a new JIRA if any changes/enhancements 
are needed.  Thanks.

 Plugin enhancement to allow the download of a Zip/Jar bundle and extraction 
 location outside repository
 ---

 Key: GERONIMO-2550
 URL: https://issues.apache.org/jira/browse/GERONIMO-2550
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Plugins
Affects Versions: 1.x
Reporter: Donald Woods
Assignee: Donald Woods
 Fix For: 2.0.x


 Plugin enhancement to allow the download of a Zip/Jar bundle and extraction 
 to a filesystem location besides /repository.
 Example uses:
 1) Download a Docs zipfile bundle and extract it to GERONIMO_HOME/docs
 2) Download a Samples zipfile bundle and extract it to GERONIMO_HOME/samples
 3) Download Java Service Wrapper and extract it to GERONIMO_HOME/jsw
 4) Download PHP and extract it to GERONIMO_HOME/php
 . . .

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

Re: How to figure what port is in use from a BindException

2008-02-01 Thread Vamsavardhana Reddy

I am wondering if there is anyway to find out the exact port number
resulting in the exception from the exception itself.

++Vamsi

On Feb 1, 2008 7:30 PM, Upul Godage [EMAIL PROTECTED] wrote:

 You can use a tool like netstat to check which ports programs are
 listening on at the moment and unusable by the server instance.
 netstat -anb
 You can find which ports the server instance will use by the
 config.substitutions.properties entries.

 Upul



 On Feb 1, 2008 6:38 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:

  Very often I run into Geronimo startup failure with a BindException
  since some port or the other is in use.  Then I change the PortOffset to get
  going.  How do I figure which port/address is resulting in the exception?

Re: [ANNOUNCE] Viet Nguyen as Geronimo's most recent committer

2008-02-01 Thread Jacek Laskowski

On Jan 31, 2008 4:47 AM, Kevan Miller [EMAIL PROTECTED] wrote:

 Let's lay some props on Viet!

Welcome Viet! Well deserved.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Closed: (GERONIMO-1293) Provide tomcat statistics

2008-02-01 Thread Anita Kulshreshtha (JIRA)

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

Anita Kulshreshtha closed GERONIMO-1293.

The ServletStats(JSR77) can easily be added when we incorporate 'Servlet'
J2EEManagedObject.
Alternately a user can get raw servlet statistics from mbeanserver.

Provide tomcat statistics
-

Key: GERONIMO-1293
URL: https://issues.apache.org/jira/browse/GERONIMO-1293
Project: Geronimo
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.0-M5
Environment: All environments
Reporter: Anita Kulshreshtha
Assignee: Anita Kulshreshtha
Priority: Minor
Fix For: 2.0, 2.1

Attachments: geronimo-stats-1.0-SNAPSHOT.war,
geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war,
geronimo-stats-1.1-SNAPSHOT.war, geronimo-stats-2.0-SNAPSHOT.war,
management.patch, management.patch, management.patch, project.patch,
properties.patch, properties.patch, stats.zip, stats.zip, stats.zip,
statsApp.zip, tomcat-builder.patch, tomcat.patch, tomcat.patch, tomcat.patch,
tomcat.patch, TomcatWebAppContext.patch

Provide following statistics for tomcat :
1. Per Host/Container -
a. Initially provide the following per connector statistics for
each connector -
Cummulative statistics about all request
handled by this connector since the stat were turned on.
b. If time (before 1.0 release) permits, use 'a' to generate
(rename/compute) statistics similar to the ones provided by Jetty
2. Per application -
a.. processingTime : The cumulative processing times of all
servlets in this StandardContext
b. startTime - The time this context was started.
c. startupTime - The time (in milliseconds) it took to start
this context.
d.. tldScanTime() -
Later add session statistics and jsp statistics.
3. Per Servlet - Explore using statistics from RequestInfo to provide
statistics for a servlet.

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

[jira] Commented: (GERONIMO-2758) Upgrade to Howl 1.0.2

2008-02-01 Thread Donald Woods (JIRA)


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

Donald Woods commented on GERONIMO-2758:


Howl 1.0.2 was released on their website, but never published to a m2 repo.
I can either pull into our private repo or just move this to Futures.
Thoughts?


 Upgrade to Howl 1.0.2
 -

 Key: GERONIMO-2758
 URL: https://issues.apache.org/jira/browse/GERONIMO-2758
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: dependencies
Affects Versions: 2.0-M5
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.1


 Howl 1.0.2 was released on 2007-01-02, but has not been published to the m2 
 repo yet.
 Will attach a patch once the jar is available on the default m2 repo.

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

[jira] Created: (GERONIMODEVTOOLS-273) Server status detection is erroneous

Server status detection is erroneous


 Key: GERONIMODEVTOOLS-273
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-273
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0.0
 Environment: Win XP, GEP 2.0.0
Reporter: Vamsavardhana Reddy
Assignee: Tim McConnell
 Fix For: 2.1.0, 2.1.x


I have added a Geronimo 2.0.2 Server under Servers view with Naming port 1100 
and HTTP Port 8081 and server installation directory 
c:\geronimo-tomcat6-jee5-2.0.2.  But when I start a Geronimo-2.1-SNAPSHOT 
installed in a different directory but using the same ports, the Geronimo 2.0.2 
Server instance in the Servers view changes the status to Starting and then 
shows Started!!

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

[jira] Created: (GERONIMODEVTOOLS-274) Automatic republish function not working for GEP 2.1

2008-02-01 Thread Tim McConnell (JIRA)

Automatic republish function not working for GEP 2.1


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




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

[jira] Updated: (GERONIMO-2758) Upgrade to Howl 1.0.2

2008-02-01 Thread Donald Woods (JIRA)


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

Donald Woods updated GERONIMO-2758:
---

Affects Version/s: (was: 2.0-M5)
   2.1
   2.0.x
   2.0
   2.0.1
   2.0.2
Fix Version/s: (was: 2.1)
   Wish List

 Upgrade to Howl 1.0.2
 -

 Key: GERONIMO-2758
 URL: https://issues.apache.org/jira/browse/GERONIMO-2758
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: dependencies
Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.x, 2.1
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
 Fix For: Wish List


 Howl 1.0.2 was released on 2007-01-02, but has not been published to the m2 
 repo yet.
 Will attach a patch once the jar is available on the default m2 repo.

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

Re: [VOTE] Release the specs

2008-02-01 Thread Guillaume Nodet

On Feb 1, 2008 4:25 PM, Kevan Miller [EMAIL PROTECTED] wrote:

 On Feb 1, 2008, at 2:46 AM, Guillaume Nodet wrote:
 
  What do you mean by skipped version numbers and different formats ?

 By format, I meant the new, non-standard tags/specs-1.4 destination.
 By skipped version numbers -- the current released version of
 annotations is 1.0, the previous vote was for 1.1.1, and this vote was
 for 1.1.2 (IIRC). Looks like in your new vote, the version number is
 back to 1.1.1.

I guess I did something wrong but I think both problems has been fixed.
I have rebuild the whole release a few hours ago and restarted a vote.


 --kevan





-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Re: How to figure what port is in use from a BindException

2008-02-01 Thread Donald Woods

Just a quick look at the JavaDocs, it seems that it's up to the code 
creating the exception to call new BindException(String) to provide the 
port in an exception message, instead of using BindException() with no 
details.


You could always start/attach to the server in Eclipse and add that 
exception as a breakpoint and inspect the code for the port being used



-Donald

Vamsavardhana Reddy wrote:
I am wondering if there is anyway to find out the exact port number 
resulting in the exception from the exception itself.


++Vamsi

On Feb 1, 2008 7:30 PM, Upul Godage [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


You can use a tool like netstat to check which ports programs are
listening on at the moment and unusable by the server instance.
netstat -anb
You can find which ports the server instance will use by the
config.substitutions.properties entries.

Upul



On Feb 1, 2008 6:38 PM, Vamsavardhana Reddy [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:

Very often I run into Geronimo startup failure with a
BindException since some port or the other is in use.  Then I
change the PortOffset to get going.  How do I figure which
port/address is resulting in the exception?





smime.p7s
Description: S/MIME Cryptographic Signature

[jira] Commented: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Joseph Leong commented on GERONIMO-3746:


Update:

Wrapped up results page to display the summary correctly.  Having the Done 
button bring you back to index page of plugin installer instead of 
viewplugindownload page. Tackling CRSF issue next.


 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
 Attachments: GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

[jira] Updated: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Joseph Leong updated GERONIMO-3746:
---

Attachment: GERONIMO-3746.patch

Additions in this patch: Fixed results summary, NPE, Redirect page at Done to 
the index screen.

-Joe

 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
 Attachments: GERONIMO-3746.patch, GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

[CLOSED][VOTE] Release ws-metadata 2.0 spec, 1.1.2



On Jan 29, 2008, at 11:36 AM, Guillaume Nodet wrote:


I've uploaded a release of ws-metadata 2.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-ws-metadata_2.0_spec-1.1.2/

Please review and vote:
  [ ] +1 Release ws-metadata 2.0 spec, v 1.1.2
  [ ] -1 Do not release it



There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release Connector 1.5 spec, v 2.0



On Jan 29, 2008, at 10:06 AM, Guillaume Nodet wrote:


I've uploaded a release of J2EE Connector 1.5 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0/
Repo
   
http://people.apache.org/~gnodet/staging/geronimo-j2ee-connector_1.5_spec-2.0/
Note: this release depens on the JTA 1.1 spec currently being voted.

Please review and vote:
  [ ] +1 Release j2ee connector 1.5 spec, v 2.0
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JMS 1.1 spec, v 1.1.1



On Jan 29, 2008, at 10:51 AM, Guillaume Nodet wrote:


I've uploaded a release of JMS 1.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jms_1.1_spec-1.1.1/


Please review and vote:
  [ ] +1 Release jms 1.1 spec, v 1.1.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JPA 3.0 spec, v 1.1.1



On Jan 29, 2008, at 11:18 AM, Guillaume Nodet wrote:


I've uploaded a release of JPA 3.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jpa_3.0_spec-1.1.1/


Please review and vote:
  [ ] +1 Release JPA 3.0 spec, v 1.1.1
  [ ] -1 Do not release it



There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JACC 1.1 spec, v 1.0.1



On Jan 29, 2008, at 11:12 AM, Guillaume Nodet wrote:


I've uploaded a release of JACC 1.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jacc_1.1_spec-1.0.1/


Please review and vote:
  [ ] +1 Release JACC 1.1 spec, v 1.0.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release the specs



On Jan 31, 2008, at 6:34 PM, Guillaume Nodet wrote:


I have tagged and uploaded a new set of the specs jars for review:
  http://people.apache.org/~gnodet/staging/specs-1.4
The tag is available at
  https://svn.apache.org/repos/asf/geronimo/specs/tags/specs-1.4

All the jars, source and javadocs should contain the legal files, the
resources have been fixed in the jsp spec and the servlet legal
files have been updated with w3c license.
Please double check and vote:

[ ] +1 Release the specs
[ ] -1 Do not release those specs (another problem ?)


There were some issues uncovered with these specs builds. This vote  
has been cancelled and a new vote started


--kevan

[CLOSED][VOTE] Release SAAJ 1.3 spec, v 1.0



On Jan 29, 2008, at 9:37 AM, Guillaume Nodet wrote:


I've uploaded a release of JAAS 1.3 spec for vote.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaas_1.3_spec-1.0/
Repo
   http://people.apache.org/~gnodet/staging/geronimo- 
jaas_1.3_spec-1.0/


Please review and vote:
  [ ] +1 Release jaas 1.3 spec
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release EJB 3.0 spec, v 1.0.1



On Jan 29, 2008, at 10:33 AM, Guillaume Nodet wrote:


I've uploaded a release of EJB 3.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-ejb_3.0_spec-1.0.1/
This release depends on the following releases that are being voted  
on:

   geronimo-jta_1.1_spec
   geronimo-interceptor_3.0_spec
   geronimo-annotation_1.0_spec

Please review and vote:
  [ ] +1 Release ejb 3.0 spec, v 1.0.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JAXR 1.0 spec, v 2.0



On Jan 29, 2008, at 9:25 AM, Guillaume Nodet wrote:


I've uploaded a release of JAXR 1.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0/
Repo
   http://people.apache.org/~gnodet/staging/geronimo- 
jaxr_1.0_spec-2.0/


Please review and vote:
  [ ] +1 Release jaxr 1.0 spec
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JTA 1.1 spec, v 1.1.1



On Jan 29, 2008, at 9:56 AM, Guillaume Nodet wrote:


I've uploaded a release of JTA 1.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jta_1.1_spec-1.1.1/


Please review and vote:
  [ ] +1 Release jta 1.1 spec, v 1.1.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release J2EE Management 1.1 spec, v 1.0.1



On Jan 29, 2008, at 10:45 AM, Guillaume Nodet wrote:


I've uploaded a release of J2EE Management 1.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/
Repo
   
http://people.apache.org/~gnodet/staging/geronimo-j2ee-management_1.1_spec-1.0.1/
This release depends on the following releases that are being voted  
on:

   geronimo-ejb_3.0_spec
and its own dependencies

Please review and vote:
  [ ] +1 Release j2ee management 1.1 spec, v 1.0.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[jira] Updated: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due


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

Kevan Miller updated GERONIMO-1761:
---

Affects Version/s: 2.1
 Assignee: Kevan Miller  (was: Jason Dillon)

OK. I have geronimo-util swapped over to geronimo-crypto. Anybody have 
objections to committing?

 Change geronimo-util module to geronimo-crypto, give credit where credit is 
 due
 ---

 Key: GERONIMO-1761
 URL: https://issues.apache.org/jira/browse/GERONIMO-1761
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: core
Affects Versions: 1.0, 2.1
Reporter: Aaron Mulder
Assignee: Kevan Miller
 Fix For: 2.1


 The util module holds a bunch of crypto-related stuff.  Speculation is that 
 it's the non-encumbered code from bouncycastle.  It should be in a more 
 accurately named module and package, since it's not just generic util code. 
  It would also be nice to put a note in every file header saying where it's 
 from, or at least in NOTICE.txt perhaps.  There may be improvements we want 
 to track?

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

[CLOSED][VOTE] Release annotation 1.0 spec, v 1.1.1



On Jan 29, 2008, at 10:19 AM, Guillaume Nodet wrote:


I've uploaded a release of annotations 1.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1
Repo
   http://people.apache.org/~gnodet/staging/geronimo-annotation_1.0_spec-1.1.1


Please review and vote:
  [ ] +1 Release annotation 1.0 spec, v 1.1.1
  [ ] -1 Do not release it



There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release interceptor 3.0 spec, v 1.0.1



On Jan 29, 2008, at 10:25 AM, Guillaume Nodet wrote:


I've uploaded a release of Interceptor 3.0 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-interceptor_3.0_spec-1.0.1/


Please review and vote:
  [ ] +1 Release interceptor 3.0 spec, v 1.0.1
  [ ] -1 Do not release it



There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

Re: [VOTE] Release JSP 2.1 spec, v 1.0.1



On Jan 29, 2008, at 11:24 AM, Guillaume Nodet wrote:


I've uploaded a release of JSP 2.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jsp_2.1_spec-1.0.1/
This release depends on EL 1.0 spec which is being voted


Please review and vote:
  [ ] +1 Release JSP 2.1 spec, v 1.0.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JSP 2.1 spec, v 1.0.1



On Jan 29, 2008, at 11:24 AM, Guillaume Nodet wrote:


I've uploaded a release of JSP 2.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jsp_2.1_spec-1.0.1/
This release depends on EL 1.0 spec which is being voted


Please review and vote:
  [ ] +1 Release JSP 2.1 spec, v 1.0.1
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

[CLOSED][VOTE] Release JAXRPC 1.1 spec, v 2.0



On Jan 29, 2008, at 9:51 AM, Guillaume Nodet wrote:


I've uploaded a release of JAXRPC 1.1 spec for vote.
The main change is that the jar is packaged as an OSGi bundle.
Tag:
   
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0/
Repo
   http://people.apache.org/~gnodet/staging/geronimo-jaxrpc_1.1_spec-2.0/
Note that this release depends on the SAAJ 1.3 spec which is being  
released atm



Please review and vote:
  [ ] +1 Release jaxrpc 1.1 spec
  [ ] -1 Do not release it


There were some issues uncovered with the specs builds. This vote was  
cancelled and a new vote (for all the specs) started


--kevan

Re: [VOTE] Release specs

2008-02-01 Thread Joe Bohn


Kevan Miller wrote:


On Feb 1, 2008, at 6:04 AM, Guillaume Nodet wrote:


Third try ...


is the charm... ;-)




Tags are here:
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-activation_1.1_spec-1.0.2/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.1/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0.0/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-saaj_1.3_spec-1.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1.2/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/
 http://svn.apache.org/viewvc/geronimo/specs/tags/specs-1.4/

Staging repo is
http://people.apache.org/~gnodet/staging/geronimo-specs/

I'm calling a single vote, as it is imho easier, but if there is any
concern, I can create other vote threads if needed.

[ ] +1 release these specs
[ ] -1 another problem ?

FYI, I won't be able for the next two weeks, so I won't be able to
close the votes and move the specs
to their final location. Hopefully someone can do it (provided that
this vote is ok).


K. I'm sure we can find a volunteer. Thanks for all the quick turn-around. 


These all look good. Pending positive TCK test results, here's my +1

--kevan



These looks good to me too.  I've pick them up and updated my local 
image to use them (along with switching from the axis2-saaj-api to the 
new geronimo-saaj_1.3_spec-1.0.0).  I've run a few tck tests and they 
look promising.  The next step for me is to get the changes on a machine 
that I can let run for a while and go through all of the TCK tests.  The 
full tests will take a few days to complete.


Joe

Re: [VOTE] Release specs



On Feb 1, 2008, at 6:04 AM, Guillaume Nodet wrote:


Third try ...


is the charm... ;-)




Tags are here:
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-activation_1.1_spec-1.0.2/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.1/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0.0/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/
 http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-saaj_1.3_spec-1.0.0/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1.2/
 
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/
 http://svn.apache.org/viewvc/geronimo/specs/tags/specs-1.4/

Staging repo is
http://people.apache.org/~gnodet/staging/geronimo-specs/

I'm calling a single vote, as it is imho easier, but if there is any
concern, I can create other vote threads if needed.

[ ] +1 release these specs
[ ] -1 another problem ?

FYI, I won't be able for the next two weeks, so I won't be able to
close the votes and move the specs
to their final location. Hopefully someone can do it (provided that
this vote is ok).


K. I'm sure we can find a volunteer. Thanks for all the quick turn- 
around.


These all look good. Pending positive TCK test results, here's my +1

--kevan

Re: svn commit: r617547 [1/3] - in /geronimo/xbean/trunk/xbean-reflect/src: main/java/org/apache/xbean/recipe/ test/java/org/apache/xbean/recipe/



On Feb 1, 2008, at 11:23 AM, [EMAIL PROTECTED] wrote:


Author: dain
Date: Fri Feb  1 08:23:21 2008
New Revision: 617547

URL: http://svn.apache.org/viewvc?rev=617547view=rev
Log:
Work in progress on graph building


Hey Dain,
Having fun? ;-)

Can you give us an idea on what you mean by graph building and where  
you're heading with this?


--kevan

[jira] Updated: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Joseph Leong updated GERONIMO-3746:
---

Attachment: (was: GERONIMO-3746.patch)

 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
 Attachments: GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

[jira] Created: (GERONIMO-3801) Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.

2008-02-01 Thread Rick McGuire (JIRA)

Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.
-

 Key: GERONIMO-3801
 URL: https://issues.apache.org/jira/browse/GERONIMO-3801
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: AsyncHttpClient
Reporter: Rick McGuire
Assignee: Rick McGuire
Priority: Minor


The recent changes that have been made to the AsyncHttpClient based on Mina 
1.1.5 need to be merged into the sandbox branch based on the 2.0 Mina API. 

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

[jira] Created: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.

In plugin installer, assembling a server, add a page at the end to confirm or 
deny the assembly of a server package.


 Key: GERONIMO-3802
 URL: https://issues.apache.org/jira/browse/GERONIMO-3802
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
Priority: Minor
 Fix For: 2.1


Add a type of confirmation page at the end of Assembling a server to inform the 
user whether the creation of there server was successful or not.

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

[jira] Assigned: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


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

Kevan Miller reassigned GERONIMO-3802:
--

Assignee: Kevan Miller  (was: Joseph Leong)

 In plugin installer, assembling a server, add a page at the end to confirm or 
 deny the assembly of a server package.
 

 Key: GERONIMO-3802
 URL: https://issues.apache.org/jira/browse/GERONIMO-3802
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Kevan Miller
Priority: Minor
 Fix For: 2.1


 Add a type of confirmation page at the end of Assembling a server to inform 
 the user whether the creation of there server was successful or not.

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

[jira] Resolved: (GERONIMO-3801) Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.

2008-02-01 Thread Rick McGuire (JIRA)


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

Rick McGuire resolved GERONIMO-3801.


Resolution: Fixed

Committed revision 617593.

Based on several patches originally submitted by Sangjin Lee for the 1.1.5 
version. 

 Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.
 -

 Key: GERONIMO-3801
 URL: https://issues.apache.org/jira/browse/GERONIMO-3801
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: AsyncHttpClient
Reporter: Rick McGuire
Assignee: Rick McGuire
Priority: Minor

 The recent changes that have been made to the AsyncHttpClient based on Mina 
 1.1.5 need to be merged into the sandbox branch based on the 2.0 Mina API. 

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

[jira] Updated: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Joseph Leong updated GERONIMO-3746:
---

Attachment: GERONIMO-3746-2.patch

Patch 2:
*Null Pointer Exception Fixed at ContinueForm.
*Summary Page of Results is Now Compatible with ArrayConfigs
*Aesthetic, Buttons renamed.. to support multi-plugin
*Done Button At End Links Back To Index Page As Opposed to the ViewPlugin Page.



 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
 Attachments: GERONIMO-3746-2.patch, GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

[jira] Assigned: (GERONIMO-3746) Plugin Progress Bar Not Updating


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

Kevan Miller reassigned GERONIMO-3746:
--

Assignee: Kevan Miller  (was: Joseph Leong)

 Plugin Progress Bar Not Updating
 

 Key: GERONIMO-3746
 URL: https://issues.apache.org/jira/browse/GERONIMO-3746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Kevan Miller
 Attachments: GERONIMO-3746-2.patch, GERONIMO-3746.patch


 When installing any plugin from the repository, the progress bar fails to 
 update correctly.

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

[jira] Updated: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


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

Kevan Miller updated GERONIMO-3802:
---

Assignee: Joseph Leong  (was: Kevan Miller)

 In plugin installer, assembling a server, add a page at the end to confirm or 
 deny the assembly of a server package.
 

 Key: GERONIMO-3802
 URL: https://issues.apache.org/jira/browse/GERONIMO-3802
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1
Reporter: Joseph Leong
Assignee: Joseph Leong
Priority: Minor
 Fix For: 2.1


 Add a type of confirmation page at the end of Assembling a server to inform 
 the user whether the creation of there server was successful or not.

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

facing problem in deploying war file on Geronimo

2008-02-01 Thread puneetjain


Hi,

I am facing a problem while deploying sample mule-examples.war in Geronimo.

Environment:
=

Mule 1.4.3
Geronimo-tomcat6-jee5-2.0.2
JDK 1.5
WindowsXP

Step Perform:
=

1. I have built the example war file.
2. I have deployed Mule JCA on Geronimo.
3. I m trying to deploy the mule-examples.war file on geronimo is thorw
bellow exception:


23:29:30,672 ERROR [[/PerfTester2]]
org.mule.util.StringUtils.defaultIfEmpty(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
java.lang.NoSuchMethodError:
org.mule.util.StringUtils.defaultIfEmpty(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
at
org.mule.providers.AbstractConnector.getReceiverKey(AbstractConnector.java:813)
at
org.mule.providers.AbstractConnector.getReceiver(AbstractConnector.java:1094)
at
org.mule.providers.AbstractConnector.registerListener(AbstractConnector.java:786)
at
org.mule.impl.model.AbstractComponent.registerListeners(AbstractComponent.java:539)
at
org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:217)
at
org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:204)
at org.mule.impl.model.AbstractModel.start(AbstractModel.java:323)
...
...
...
...
...
...
23:29:30,797 ERROR [[/PerfTester2]] Exception sending context initialized
event to listener instance of class
org.mule.config.builders.MuleXmlBuilderContextListener
java.lang.NoSuchMethodError:
org.mule.util.StringUtils.defaultIfEmpty(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
at
org.mule.providers.AbstractConnector.getReceiverKey(AbstractConnector.java:813)
at
org.mule.providers.AbstractConnector.getReceiver(AbstractConnector.java:1094)
at
org.mule.providers.AbstractConnector.registerListener(AbstractConnector.java:786)
at
org.mule.impl.model.AbstractComponent.registerListeners(AbstractComponent.java:539)
at
org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:217)
at
org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:204)
at org.mule.impl.model.AbstractModel.start(AbstractModel.java:323)
at org.mule.MuleManager.start(MuleManager.java:892)
at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:278)



Please help me to resolve my problem.

Thanks,
Puneet
-- 
View this message in context: 
http://www.nabble.com/facing-problem-in-deploying-war-file-on-Geronimo-tp15231881s134p15231881.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

[jira] Commented: (GERONIMO-3801) Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.

2008-02-01 Thread Sangjin Lee (JIRA)


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

Sangjin Lee commented on GERONIMO-3801:
---

Wow, this quick? :)  Thanks!  I'll also take a quick look at it.

Sangjin

 Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.
 -

 Key: GERONIMO-3801
 URL: https://issues.apache.org/jira/browse/GERONIMO-3801
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: AsyncHttpClient
Reporter: Rick McGuire
Assignee: Rick McGuire
Priority: Minor

 The recent changes that have been made to the AsyncHttpClient based on Mina 
 1.1.5 need to be merged into the sandbox branch based on the 2.0 Mina API. 

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

[jira] Closed: (GERONIMO-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due


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

Kevan Miller closed GERONIMO-1761.
--

Resolution: Fixed

Moved geronimo-util to geronimo-crypto. Also moved package name from 
org.apache.geronimo.util to org.apache.geronimo.crypto

 Change geronimo-util module to geronimo-crypto, give credit where credit is 
 due
 ---

 Key: GERONIMO-1761
 URL: https://issues.apache.org/jira/browse/GERONIMO-1761
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: core
Affects Versions: 1.0, 2.1
Reporter: Aaron Mulder
Assignee: Kevan Miller
 Fix For: 2.1


 The util module holds a bunch of crypto-related stuff.  Speculation is that 
 it's the non-encumbered code from bouncycastle.  It should be in a more 
 accurately named module and package, since it's not just generic util code. 
  It would also be nice to put a note in every file header saying where it's 
 from, or at least in NOTICE.txt perhaps.  There may be improvements we want 
 to track?

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

[jira] Commented: (GERONIMO-3764) DeployerReaper fails to cleanup the temp directories left behind by deployer


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

Vamsavardhana Reddy commented on GERONIMO-3764:
---

Completed: At revision: 617648  in branches\2.0 and trunk (2.1)
 o EARConfigBuilder should close modules when deployment fails due to already 
existing configuration.  Otherwise deployer leaves temp files behind.


 DeployerReaper fails to cleanup the temp directories left behind by deployer
 

 Key: GERONIMO-3764
 URL: https://issues.apache.org/jira/browse/GERONIMO-3764
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.0.1, 2.0.2, 2.0.x, 2.1
Reporter: Vamsavardhana Reddy
Assignee: Vamsavardhana Reddy
 Fix For: 2.0.x, 2.1

 Attachments: GERONIMO-3764-2.0.patch, 
 GERONIMO-3764-deploymentutil.patch


 Deployer creates a temporary directory and cleans up the directory once 
 deployment operation is completed.  When deletion of a temp dir fails, the 
 deployer leaves it upto DeployerReaper to cleanup the directory later on.  
 DeployerReaper is failing to cleanup these directories as only the dir name 
 (not the complete path) is available to it.

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

[jira] Closed: (GERONIMO-3764) DeployerReaper fails to cleanup the temp directories left behind by deployer


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

Vamsavardhana Reddy closed GERONIMO-3764.
-

Resolution: Fixed

I think I really nailed this one :).  If anyone finds I cracked open something 
else in the process, please reopen the JIRA or create a new one.

 DeployerReaper fails to cleanup the temp directories left behind by deployer
 

 Key: GERONIMO-3764
 URL: https://issues.apache.org/jira/browse/GERONIMO-3764
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.0.1, 2.0.2, 2.0.x, 2.1
Reporter: Vamsavardhana Reddy
Assignee: Vamsavardhana Reddy
 Fix For: 2.0.x, 2.1

 Attachments: GERONIMO-3764-2.0.patch, 
 GERONIMO-3764-deploymentutil.patch


 Deployer creates a temporary directory and cleans up the directory once 
 deployment operation is completed.  When deletion of a temp dir fails, the 
 deployer leaves it upto DeployerReaper to cleanup the directory later on.  
 DeployerReaper is failing to cleanup these directories as only the dir name 
 (not the complete path) is available to it.

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

[jira] Commented: (GERONIMO-3764) DeployerReaper fails to cleanup the temp directories left behind by deployer

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

Vamsavardhana Reddy commented on GERONIMO-3764:
---

Completed: At revision: 617659 in branches\2.0 and trunk (2.1)
o Offline deployer leaves temporary files behind since using URLs with jar
protocol locks the jar file and prevents deletion. This is prevented by
creating a temporary file when the protocol is jar.
o This behaviour is controlled using a system property
org.apache.geronimo.deployment.util.DeploymentUtil.jarUrlRewrite which is
false by default, meaning no change from existing behavior for online-deployer.
o Offline deployer sets the system property to true.
o See http://www.mail-archive.com/dev@geronimo.apache.org/msg55811.html

DeployerReaper fails to cleanup the temp directories left behind by deployer

Key: GERONIMO-3764
URL: https://issues.apache.org/jira/browse/GERONIMO-3764
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.1, 2.0.2, 2.0.x, 2.1
Reporter: Vamsavardhana Reddy
Assignee: Vamsavardhana Reddy
Fix For: 2.0.x, 2.1

Attachments: GERONIMO-3764-2.0.patch,
GERONIMO-3764-deploymentutil.patch

Deployer creates a temporary directory and cleans up the directory once
deployment operation is completed. When deletion of a temp dir fails, the
deployer leaves it upto DeployerReaper to cleanup the directory later on.
DeployerReaper is failing to cleanup these directories as only the dir name
(not the complete path) is available to it.

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

[jira] Updated: (GERONIMO-3801) Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.

2008-02-01 Thread Sangjin Lee (JIRA)


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

Sangjin Lee updated GERONIMO-3801:
--

Attachment: GERONIMO-3801.patch

It looks good...  I did do a minor clean-up on the code.  I cleaned up most of 
the compiler warnings on the code.  The main thing was parametrized types (I 
used proper parametrized types and got rid of casts).

Please review it, and commit the changes if you find them acceptable...  Thanks!

Sangjin

 Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.
 -

 Key: GERONIMO-3801
 URL: https://issues.apache.org/jira/browse/GERONIMO-3801
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: AsyncHttpClient
Reporter: Rick McGuire
Assignee: Rick McGuire
Priority: Minor
 Attachments: GERONIMO-3801.patch


 The recent changes that have been made to the AsyncHttpClient based on Mina 
 1.1.5 need to be merged into the sandbox branch based on the 2.0 Mina API. 

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

Re: facing problem in deploying war file on Geronimo



On Feb 1, 2008, at 2:19 PM, puneetjain wrote:



Hi,

I am facing a problem while deploying sample mule-examples.war in  
Geronimo.


Answered this same question on our user list...

--kevan

[BUILD] 2.1: Failed for Revision: 617625

2008-02-01 Thread gawor

Geronimo Revision: 617625 built with tests included
 
See the full build-1500.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080201/build-1500.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080201
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 30 minutes 58 seconds
[INFO] Finished at: Fri Feb 01 16:06:56 EST 2008
[INFO] Final Memory: 303M/996M
[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/trunk/20080201/logs-1500-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080201/logs-1500-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.709 
sec  FAILURE!

[reflect] Object graph support

2008-02-01 Thread Dain Sundstrom

I've committed my initial work on build object graphs with xbean  
reflect.  The code works, but I need to do more testing and a few more  
features are needed.  I'm going to be on vacation for the next 10  
days, and if you all decide to do another release of xbean for the  
quick fix Guillaume suggested, please don't release this code.


Thanks,

-dain

[jira] Updated: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole


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

Viet Hung Nguyen updated GERONIMO-3803:
---

Attachment: geronimo-3803.patch

 monitoring plugin: agent-jmx does not provide the correct interface for 
 mconsole
 

 Key: GERONIMO-3803
 URL: https://issues.apache.org/jira/browse/GERONIMO-3803
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1
 Environment: ubuntu
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical
 Attachments: geronimo-3803.patch


 the agent-jmx does not specify the right method signatures that the mconsole 
 needs to run properly. 

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

[jira] Created: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole

monitoring plugin: agent-jmx does not provide the correct interface for mconsole


 Key: GERONIMO-3803
 URL: https://issues.apache.org/jira/browse/GERONIMO-3803
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: monitoring
Affects Versions: 2.1, 2.1.1
 Environment: ubuntu
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical
 Attachments: geronimo-3803.patch

the agent-jmx does not specify the right method signatures that the mconsole 
needs to run properly. 

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

[jira] Created: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx

monitoring pluging: mconsole-graphs does not detect any servers that was 
connected through jmx
--

 Key: GERONIMO-3804
 URL: https://issues.apache.org/jira/browse/GERONIMO-3804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: monitoring
Affects Versions: 2.1
Reporter: Viet Hung Nguyen
Priority: Critical


the mconsole does not detect any servers connected using jmx when trying to add 
a graph. I suspect it has something to do with the db query, because it detects 
all servers connected through MEJB just fine. I checked to ensure an instance 
of the server-jmx was present in the mconsole db and it is.

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

[jira] Commented: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole

2008-02-01 Thread Erik B. Craig (JIRA)


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

Erik B. Craig commented on GERONIMO-3803:
-

Patch Committed revision 617721.
Hold Jira open until I see whether or not it needs to be committed to 2.1 
branch as well
Thanks Viet

 monitoring plugin: agent-jmx does not provide the correct interface for 
 mconsole
 

 Key: GERONIMO-3803
 URL: https://issues.apache.org/jira/browse/GERONIMO-3803
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1
 Environment: ubuntu
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical
 Attachments: geronimo-3803.patch


 the agent-jmx does not specify the right method signatures that the mconsole 
 needs to run properly. 

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

[jira] Assigned: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx

2008-02-01 Thread Erik B. Craig (JIRA)


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

Erik B. Craig reassigned GERONIMO-3804:
---

Assignee: Erik B. Craig

 monitoring pluging: mconsole-graphs does not detect any servers that was 
 connected through jmx
 --

 Key: GERONIMO-3804
 URL: https://issues.apache.org/jira/browse/GERONIMO-3804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1
Reporter: Viet Hung Nguyen
Assignee: Erik B. Craig
Priority: Critical

 the mconsole does not detect any servers connected using jmx when trying to 
 add a graph. I suspect it has something to do with the db query, because it 
 detects all servers connected through MEJB just fine. I checked to ensure an 
 instance of the server-jmx was present in the mconsole db and it is.

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

[jira] Closed: (GERONIMO-3467) Confusing security exception thrown while authenticating using JMX with a just starting server

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

Kevan Miller closed GERONIMO-3467.
--

Resolution: Won't Fix

Looks like we have a fix/work-around for the reported problem in eclipse.

I'm guessing that your looking for a NoLoginModuleConfigured exception and
want to use this as a trigger for waiting for the server to finish startup.
Seems like you can use the SecurityException for the same purpose. Will just
delay user notification for truly invalid login attempts.

Reopen, if you think this requires a server change.

Confusing security exception thrown while authenticating using JMX with a
just starting server
--

Key: GERONIMO-3467
URL: https://issues.apache.org/jira/browse/GERONIMO-3467
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: security
Affects Versions: 2.0.2, 2.0.x, 2.1
Reporter: Shiva Kumar H R
Fix For: 2.0.x, 2.1

Scenario is as below:
Let's say server is starting and
org.apache.geronimo.configs/rmi-naming/2.0.1/car has started, but
org.apache.geronimo.configs/j2ee-security/2.0.1/car hasn't yet started. If an
external entity (like Geronimo Eclipse Plug-in) now tries to connect to the
kernel remotely through JMX, although rmi connection succeeds, authenticate
will fail (because security realm has not yet been started).
In this case, org.apache.geronimo.jmxremoting.Authenticator.authenticate() is
getting a LoginException with error
javax.security.auth.login.LoginException: No LoginModules configured for
geronimo-admin. However this exception is not propogated, but rather is
thrown back as a 'SecurityException(Invalid login)'.

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

[jira] Assigned: (GERONIMO-2905) We need to accept broken app client spec dds for a while


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

Kevan Miller reassigned GERONIMO-2905:
--

Assignee: Kevan Miller  (was: David Jencks)

 We need to accept broken app client spec dds for a while
 

 Key: GERONIMO-2905
 URL: https://issues.apache.org/jira/browse/GERONIMO-2905
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: application client, deployment
Affects Versions: 2.0-M3
Reporter: David Jencks
Assignee: Kevan Miller
 Fix For: 2.1


 To progress towards certification we need to accept invalid app client spec 
 dd documents whose version is 5.0 rather than the correct 5.

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

[jira] Updated: (GERONIMO-3408) Clean up deployer login code in ServerConnection


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

Kevan Miller updated GERONIMO-3408:
---

   Patch Info:   (was: [Patch Available])
Fix Version/s: (was: 2.1)
   2.1.1

This patch is dated, now. Will keep the jira around for a while longer. 
Interested in updating to 2.1?

 Clean up deployer login code in ServerConnection
 

 Key: GERONIMO-3408
 URL: https://issues.apache.org/jira/browse/GERONIMO-3408
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.0, 2.0.x, 2.1
Reporter: Ted Kirby
Assignee: Donald Woods
 Fix For: 2.0.x, 2.1.1

 Attachments: G3408.patch


 Currently, the normal login path of the deploy command is a two-pass 
 approach, where an exception is thrown in the first pass.  I am cleaning this 
 up and removing what looks like old code.

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

[jira] Resolved: (GERONIMO-3444) EJBContext


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

Kevan Miller resolved GERONIMO-3444.


   Resolution: Fixed
Fix Version/s: (was: 2.0.x)

Looks like this was fixed. Could you close this jira, if you agree?

 EJBContext
 --

 Key: GERONIMO-3444
 URL: https://issues.apache.org/jira/browse/GERONIMO-3444
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: OpenEJB
Affects Versions: 2.0.x
 Environment: Windows XP SP2
Reporter: Aman Nanner
 Fix For: 2.1


 During the initial running of our J2EE application, the following error 
 inconsistently occurs:
 {panel:title=Stack Trace}
 16:49:57,268 ERROR [OpenEJB] The bean instance null threw a system 
 exception:javax.naming.NameAlreadyBoundException: EJBContext
 javax.naming.NameAlreadyBoundException: EJBContext
   at 
 org.apache.xbean.naming.context.WritableContext.addBinding(WritableContext.java:91)
   at 
 org.apache.xbean.naming.context.WritableContext$NestedWritableContext.addBinding(WritableContext.java:235)
   at 
 org.apache.xbean.naming.context.AbstractContext.addBinding(AbstractContext.java:320)
   at 
 org.apache.xbean.naming.context.AbstractContext.addDeepBinding(AbstractContext.java:240)
   at 
 org.apache.xbean.naming.context.AbstractContext.bind(AbstractContext.java:652)
   at 
 org.apache.xbean.naming.context.AbstractContext.bind(AbstractContext.java:643)
   at 
 org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:111)
   at 
 org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:156)
   at 
 org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:211)
   at 
 org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:65)
   at 
 org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:320)
   at 
 org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
   at $Proxy164.executeUpdate(Unknown Source)
   at 
 com.mxi.mx.common.ejb.job.StaleJobResetJobBean.processMessage(StaleJobResetJobBean.java:79)
   at 
 com.mxi.mx.common.ejb.job.MxMessageDrivenBean.onMessage(MxMessageDrivenBean.java:135)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:146)
   at 
 org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:129)
   at 
 org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
   at 
 org.apache.openejb.core.mdb.MdbContainer._invoke(MdbContainer.java:332)
   at 
 org.apache.openejb.core.mdb.MdbContainer.invoke(MdbContainer.java:304)
   at 
 org.apache.openejb.core.mdb.EndpointHandler.deliverMessage(EndpointHandler.java:229)
   at 
 org.apache.openejb.core.mdb.EndpointHandler.invoke(EndpointHandler.java:170)
   at $Proxy163.onMessage(Unknown Source)
   at 
 org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:121)
   at 
 org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:61)
   at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:696)
   at 
 org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:165)
   at 
 org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:290)
   at 
 org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32)
   at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201)
   at 
 org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
   at java.lang.Thread.run(Thread.java:595)
 16:49:57,284 ERROR [MxMessageDrivenBean] Error executing stale job reset job
 javax.ejb.EJBException: Cannot obtain a free instance.; nested exception is: 
   javax.naming.NameAlreadyBoundException: EJBContext
   at 
 org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:365)
   at 
 org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:322)
   at

[jira] Updated: (GERONIMO-3545) Upgrade Apache Derby to 10.3.1.4


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

Kevan Miller updated GERONIMO-3545:
---


Looks like we could give 10.3.2.1 a try.

 Upgrade Apache Derby to 10.3.1.4
 

 Key: GERONIMO-3545
 URL: https://issues.apache.org/jira/browse/GERONIMO-3545
 Project: Geronimo
  Issue Type: Task
  Security Level: public(Regular issues) 
  Components: databases
Affects Versions: 2.1
Reporter: Jacek Laskowski
Assignee: Jacek Laskowski
 Fix For: 2.1


 Upgrade Derby to 10.3.1.4

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

[jira] Closed: (GERONIMO-3621) Jetty can not handle url like http://localhost:8080//console


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

Kevan Miller closed GERONIMO-3621.
--

Resolution: Won't Fix

IIUC, Jetty treats // chars as significant. Not aware of a spec which makes 
Jetty's behavior incorrect.

 Jetty can not handle url like http://localhost:8080//console
 

 Key: GERONIMO-3621
 URL: https://issues.apache.org/jira/browse/GERONIMO-3621
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Jetty
Affects Versions: 2.1
Reporter: YunFeng Ma
 Fix For: 2.1


 For the Geronimo-Jetty build, access the console with url: 
 http://localhost:8080//console , get the following error in browser:
 HTTP ERROR: 404
 NOT_FOUND
 RequestURI=//console/
 Powered by Jetty://
 But it works fine with Geronimo-Tomcat build.

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

[jira] Updated: (GERONIMO-3762) Web Applications displayed during server startup include system console plugins


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

Kevan Miller updated GERONIMO-3762:
---

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

 Web Applications displayed during server startup include system console 
 plugins
 -

 Key: GERONIMO-3762
 URL: https://issues.apache.org/jira/browse/GERONIMO-3762
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1, 2.1.1
Reporter: Kevan Miller
 Fix For: 2.1.1


 During server startup, the following web applications are displayed. 
   Web Applications:
 /
 /CAHelper
 /activemq
 /console
 /console-base
 /debug-views
 /dojo
 /dojo/1.0
 /juddi
 /monitoring
 /plan-creator
 /plugin
 /remote-deploy
 /system-database
 In 2.0.2, they were:
   Web Applications:
 /
 /console
 /console-standard
 /dojo
 /remote-deploy
 Is it possible to filter these system apps (e.g. activemq, CAHelper, etc.)? 
 Or group in some way to make them more intuitive?

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

[jira] Updated: (GERONIMO-3768) deployment failure is not logged in either geronimo.log or deployer.log


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

Kevan Miller updated GERONIMO-3768:
---

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

 deployment failure is not logged in either geronimo.log or deployer.log
 ---

 Key: GERONIMO-3768
 URL: https://issues.apache.org/jira/browse/GERONIMO-3768
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1, 2.1.1
Reporter: Kevan Miller
 Fix For: 2.1.1


 Deployment failures should be logged, IMO. Yet there's no indication of the 
 following deploy failure. The only failure info is in STDOUT for both server 
 and deploy processes.
 coltrane:bin kevan$ ./deploy.sh deploy 
 ~/Desktop/OS-Projects/artifactory-1.2.2/webapps/artifactory.war   
 ~/Desktop/OS-Projects/artifactory-1.2.2/webapps/geronimo-web.xml   Using 
 GERONIMO_BASE:   /Users/kevan/downloads/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
 Using GERONIMO_HOME:   
 /Users/kevan/downloads/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
 Using GERONIMO_TMPDIR: var/temp
 Using JRE_HOME:
 /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
 12:42:02,694 WARN  [AbstractGBeanReference] GBean references are not using 
 proxies
 org.apache.geronimo.kernel.config.LifecycleException: start of 
 com.kevan/artifactory/1.2.2/war failed
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:551)
 at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:515)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
 at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
 at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
 at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
 at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
 at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
 at 
 org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
 at 
 com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
 at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
 at 
 com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
 at 
 com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
 at 
 javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
 at 
 javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
 at 
 javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
 at java.security.AccessController.doPrivileged(Native Method)
 at 
 javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
 at 
 javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
 at sun.rmi.transport.Transport$1.run(Transport.java:153)
 at java.security.AccessController.doPrivileged(Native Method)
 at

[jira] Updated: (GERONIMO-3433) Admin Console Wizard to auto generate geronimo-application.xml


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

Kevan Miller updated GERONIMO-3433:
---

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

 Admin Console Wizard to auto generate geronimo-application.xml
 --

 Key: GERONIMO-3433
 URL: https://issues.apache.org/jira/browse/GERONIMO-3433
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: console, deployment, usability
Affects Versions: 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.1


 For a background about this work please see GERONIMO-3254  GERONIMO-3432.
 Enhance Create Plan portlet  other Admin Console Wizards to help 
 server-administrators in auto creating the Geronimo Deployment Plan for a 
 J2EE/Java-EE application.

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

[jira] Updated: (GERONIMO-3700) alias command fails


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

Kevan Miller updated GERONIMO-3700:
---

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

 alias command fails
 ---

 Key: GERONIMO-3700
 URL: https://issues.apache.org/jira/browse/GERONIMO-3700
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: general
Affects Versions: 2.1, 2.1.1
Reporter: Kevan Miller
Assignee: Jason Dillon
 Fix For: 2.1.1


 Running the alias command fails with an IllegalStateException:
 [EMAIL PROTECTED]:/ alias
 ERROR IllegalStateException: Alias file 
 /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml
  does not exist
 Could be that Geronimo should be including this file in assemblies, or gshell 
 should create (if not present), or something else is wrong...

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

[jira] Closed: (GERONIMO-3127) ERROR [DriverDownloader] Unable to download driver properties


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

Kevan Miller closed GERONIMO-3127.
--

Resolution: Invalid

Might have been a problem at one time, but is working for me (at least for the 
mysql driver). Please reopen, if you have an explicit test case for us...

 ERROR [DriverDownloader] Unable to download driver properties
 -

 Key: GERONIMO-3127
 URL: https://issues.apache.org/jira/browse/GERONIMO-3127
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: databases
Affects Versions: 2.0-M5, 2.0-M6, 2.0, 2.1
 Environment: Window 2K, Jre 6. firefox
Reporter: nrkkalyan
Assignee: Donald Woods
 Fix For: 2.0.x, 2.1


 When we try to download driver in the 2 step of creating Database pool we are 
 getting the following error
 *
 Geronimo Application Server started
 11:19:32,396 ERROR [DriverDownloader] Unable to download driver properties
 java.net.UnknownHostException: geronimo.apache.org
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
 at java.net.Socket.connect(Socket.java:516)
 at java.net.Socket.connect(Socket.java:466)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
 at sun.net.www.http.HttpClient.init(HttpClient.java:214)
 at sun.net.www.http.HttpClient.New(HttpClient.java:287)
 at sun.net.www.http.HttpClient.New(HttpClient.java:299)
 at 
 sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:796)
 at 
 sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:748)
 at 
 sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:673)
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:917)
 at java.net.URL.openStream(URL.java:1007)
 at 
 org.apache.geronimo.console.databasemanager.wizard.DriverDownloader.readDriverFile(DriverDownloader.java:57)
 at 
 org.apache.geronimo.console.databasemanager.wizard.DriverDownloader.loadDriverInfo(DriverDownloader.java:70)
 at 
 org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.getDriverInfo(DatabasePoolPortlet.java:206)
 at 
 org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.renderDownload(DatabasePoolPortlet.java:765)
 at 
 org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.doView(DatabasePoolPortlet.java:672)
 at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
 at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
 at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
 at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
 at 
 org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
 at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
 at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
 at 
 org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
 at 
 org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73)
 at 
 org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119)
 at 
 org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70)
 at 
 org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168)
 at 
 jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at

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

Kevan Miller updated GERONIMO-3719:
---

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

Unless there's a fix on hand, can fix this in 2.1.1.

 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
Reporter: David Jencks
Assignee: Viet Hung Nguyen
 Fix For: 2.1.1


 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-3440) DB2-XA: when trace file is not specified, it caused error when running the sample


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

Kevan Miller updated GERONIMO-3440:
---

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

 DB2-XA: when trace file is not specified, it caused error when running the 
 sample
 -

 Key: GERONIMO-3440
 URL: https://issues.apache.org/jira/browse/GERONIMO-3440
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: databases
Affects Versions: 2.1, 2.1.1
Reporter: Lin Sun
Assignee: David Jencks
Priority: Minor
 Fix For: 2.1.1

 Attachments: tranql-tracefile.patch


 This is a tranql issue found when I plug the db2-xa rar into G's console.   
 Basically, if a user leaves the tracefile property to empty (meaning dont 
 want any trace), I can deploy my sample fine.   But when I run the sample, I 
 got -
  
 ---
  
   Got DataSource: [EMAIL PROTECTED]
 com.ibm.db2.jcc.b.SqlException: Unable to open file
 at com.ibm.db2.jcc.b.ig.a(ig.java:93)
 A simple fix in DB2XA is to only settrace when it is a valid value.

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

[jira] Updated: (GERONIMO-3440) DB2-XA: when trace file is not specified, it caused error when running the sample


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

Kevan Miller updated GERONIMO-3440:
---

Fix Version/s: (was: 2.1)

 DB2-XA: when trace file is not specified, it caused error when running the 
 sample
 -

 Key: GERONIMO-3440
 URL: https://issues.apache.org/jira/browse/GERONIMO-3440
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: databases
Affects Versions: 2.1, 2.1.1
Reporter: Lin Sun
Assignee: David Jencks
Priority: Minor
 Fix For: 2.1.1

 Attachments: tranql-tracefile.patch


 This is a tranql issue found when I plug the db2-xa rar into G's console.   
 Basically, if a user leaves the tracefile property to empty (meaning dont 
 want any trace), I can deploy my sample fine.   But when I run the sample, I 
 got -
  
 ---
  
   Got DataSource: [EMAIL PROTECTED]
 com.ibm.db2.jcc.b.SqlException: Unable to open file
 at com.ibm.db2.jcc.b.ig.a(ig.java:93)
 A simple fix in DB2XA is to only settrace when it is a valid value.

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

[jira] Updated: (GERONIMO-3399) Need JSR88 DConfigBeans for GerSecurityType


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

Kevan Miller updated GERONIMO-3399:
---

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

 Need JSR88 DConfigBeans for GerSecurityType
 ---

 Key: GERONIMO-3399
 URL: https://issues.apache.org/jira/browse/GERONIMO-3399
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console, deployment
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Priority: Minor
 Fix For: 2.1.1


 We currently miss this functionality. Admin console portlet CreatePlan 
 needs this. Hence this request.

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

[jira] Closed: (GERONIMO-2340) Network Listener state not persisted across server startups


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

Kevan Miller closed GERONIMO-2340.
--

Resolution: Won't Fix

stopping does not permanently disable a gbean. You'll need to delete the 
gbean if you don't want it started after a server restart. This will set 
load=false on the gbean. 

 Network Listener state not persisted across server startups
 ---

 Key: GERONIMO-2340
 URL: https://issues.apache.org/jira/browse/GERONIMO-2340
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 1.1.1
 Environment: Win XP, Geronimo 1.1.1-SNAPSHOT
Reporter: Vamsavardhana Reddy
Assignee: Donald Woods
 Fix For: 2.0.x, 2.1


 I have stopped the HTTPS and AJP Network Listeners thru Web Servers 
 portlet.  Upon restarting the server, these stopped listeners have started 
 automatically.  Happens with both Jetty and Tomcat.

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

[jira] Assigned: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx


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

Viet Hung Nguyen reassigned GERONIMO-3804:
--

Assignee: Viet Hung Nguyen  (was: Erik B. Craig)

 monitoring pluging: mconsole-graphs does not detect any servers that was 
 connected through jmx
 --

 Key: GERONIMO-3804
 URL: https://issues.apache.org/jira/browse/GERONIMO-3804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical

 the mconsole does not detect any servers connected using jmx when trying to 
 add a graph. I suspect it has something to do with the db query, because it 
 detects all servers connected through MEJB just fine. I checked to ensure an 
 instance of the server-jmx was present in the mconsole db and it is.

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

[jira] Updated: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx


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

Viet Hung Nguyen updated GERONIMO-3804:
---

Attachment: geronimo-3804.patch

 monitoring pluging: mconsole-graphs does not detect any servers that was 
 connected through jmx
 --

 Key: GERONIMO-3804
 URL: https://issues.apache.org/jira/browse/GERONIMO-3804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical
 Attachments: geronimo-3804.patch


 the mconsole does not detect any servers connected using jmx when trying to 
 add a graph. I suspect it has something to do with the db query, because it 
 detects all servers connected through MEJB just fine. I checked to ensure an 
 instance of the server-jmx was present in the mconsole db and it is.

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

[jira] Commented: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx

2008-02-01 Thread Erik B. Craig (JIRA)


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

Erik B. Craig commented on GERONIMO-3804:
-

Committed revision 617750.

Thanks viet

 monitoring pluging: mconsole-graphs does not detect any servers that was 
 connected through jmx
 --

 Key: GERONIMO-3804
 URL: https://issues.apache.org/jira/browse/GERONIMO-3804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Priority: Critical
 Attachments: geronimo-3804.patch


 the mconsole does not detect any servers connected using jmx when trying to 
 add a graph. I suspect it has something to do with the db query, because it 
 detects all servers connected through MEJB just fine. I checked to ensure an 
 instance of the server-jmx was present in the mconsole db and it is.

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

[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members


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

Kevan Miller updated GERONIMO-3759:
---

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

 Geronimo Tomcat Clustering - No GBeans for adding Static Members
 

 Key: GERONIMO-3759
 URL: https://issues.apache.org/jira/browse/GERONIMO-3759
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
 Fix For: 2.1.1


 Tomcat uses multicasting for discovering cluster members. It also supports 
 static memberships using the StaticMembershipInterceptor if you want to 
 extend your membership to points beyond multicasting, using configuration as 
 below:
  Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
   port=5678
   securePort=-1
   host=tomcat01.mydomain.com
   domain=staging-cluster
   uniqueId={0,1,2,3,4,5,6,7,8,9}/
  /Interceptor
 http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
 http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
 However, to add this configuration in Geronimo's config.xml, we don't have 
 the required GBeans for Member element.

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

[jira] Closed: (GERONIMO-2905) We need to accept broken app client spec dds for a while


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

Kevan Miller closed GERONIMO-2905.
--

Resolution: Fixed

TCK DeploymentDescriptors were fixed a while back. We didn't need this schema 
version hack, any longer. Tests look good...

 We need to accept broken app client spec dds for a while
 

 Key: GERONIMO-2905
 URL: https://issues.apache.org/jira/browse/GERONIMO-2905
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: application client, deployment
Affects Versions: 2.0-M3
Reporter: David Jencks
Assignee: Kevan Miller
 Fix For: 2.1


 To progress towards certification we need to accept invalid app client spec 
 dd documents whose version is 5.0 rather than the correct 5.

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

[jira] Updated: (GERONIMO-3503) DBPool wizzard creates plans only for local-transactions


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

Kevan Miller updated GERONIMO-3503:
---

Fix Version/s: (was: 2.1)
   2.1.1

 DBPool wizzard creates plans only for local-transactions
 

 Key: GERONIMO-3503
 URL: https://issues.apache.org/jira/browse/GERONIMO-3503
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Reporter: Tomasz Mazan
 Fix For: 2.0.x, 2.1.1


 I use DatabasePool Wizzard to deploy Pools for PostgresQL. 
 In both cases - I choosed PostgreAQL XA or PostgreSQL Local - wizzard 
 generated plan with model 
 connectionmanager
 local-transaction/
 single-pool
 max-size10/max-size
 min-size0/min-size
 match-one/
 /single-pool
 /connectionmanager

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

[jira] Updated: (GERONIMO-3432) Admin Console Wizard to auto generate openejb-jar.xml


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

Kevan Miller updated GERONIMO-3432:
---

Fix Version/s: (was: 2.1)
   2.1.1

 Admin Console Wizard to auto generate openejb-jar.xml
 -

 Key: GERONIMO-3432
 URL: https://issues.apache.org/jira/browse/GERONIMO-3432
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: console, deployment, usability
Affects Versions: 2.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.1


 For a background about this work please see GERONIMO-3254.
 Currently the plan creation wizard only takes a web-app (.war) as an input 
 and helps in auto-creating geronimo-web.xml. Enhance the wizard to take an 
 EJB-JAR input and help in auto-creating openejb-jar.xml.

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

[jira] Closed: (GERONIMO-3115) MDB pool size should be able to be configurable in openejb-jar.xsd


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

Kevan Miller closed GERONIMO-3115.
--

Resolution: Won't Fix

as described in the jira, pool size is configurable.

 MDB pool size should be able to be configurable in openejb-jar.xsd
 --

 Key: GERONIMO-3115
 URL: https://issues.apache.org/jira/browse/GERONIMO-3115
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: OpenEJB
Affects Versions: 2.0-M6
Reporter: Aman Nanner
 Fix For: 2.0.x, 2.1


 There should be an attribute for message driven beans in the openejb-jar.xsd 
 schema that will configure the pool size.  For example, if a pool size of 1 
 were configured for a specific bean, then there would only be a maximum of 1 
 message driven bean instance of that type that would be instantiated.

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

Kevan Miller updated GERONIMO-3685:
---

Fix Version/s: (was: 2.1)
   2.1.1

Assume we're ok, as is. If someone, could answer anita's question, would be good

 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


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

[jira] Updated: (GERONIMO-2622) Implement PolicyContextHandlerSOAPMessage


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

Kevan Miller updated GERONIMO-2622:
---

Affects Version/s: 2.1
   2.0
   2.0.1
   2.0.2
Fix Version/s: (was: 2.1)
   2.1.1

Not sure what needs to be done, here. David, perhaps you can give someone a 
pointer?

 Implement PolicyContextHandlerSOAPMessage
 -

 Key: GERONIMO-2622
 URL: https://issues.apache.org/jira/browse/GERONIMO-2622
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: security
Affects Versions: 2.0-M5, 2.0, 2.0.1, 2.0.2, 2.1
Reporter: David Jencks
Assignee: David Jencks
Priority: Critical
 Fix For: 2.1.1


 I just discoverd PolicyContextHandlerSOAPMessage is not yet implemented!

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

[jira] Updated: (GERONIMO-2246) Why resource-env-ref:admin-object-module?