[jira] Commented: (GERONIMODEVTOOLS-575) GEP errors that are logged to the Eclipse error log are not always seen by end-user

[Tim McConnell (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734482#action_12734482
 ] 

Tim McConnell commented on GERONIMODEVTOOLS-575:


Hi Delos, thanks much for the stopserver patch. Given what we currently know 
about the implementation of the stop() method in WTP's ServerBehaviourDelegate 
class, this works very nicely. When I inject an Exception during the stop 
process in GeronimoServerBehaviourDelegate on the GEP side we get a "Problem 
Occurred" dialog that presents the "Stopping Apache Geronimo v2.1 server at 
local host has encountered a problem" message and an entry to the Eclipse Error 
log stating that "Error calling delegate stop() Apache Geronimo v2.1 server at 
local host" from the org.eclipse.wst.server.core plugin. Note that we were 
getting neither of these before and they are precisely what needs to be 
presented to the GEP user during this type of failure. 

With all this said though, just for the sake of completeness I've posted a 
question to the Eclipse wtp-dev mailing list to ensure we're doing exactly what 
they expect in this case (i.e., throwing a Runtime Exception instead of a 
CoreException). Will let you know what they respond with. 

Thanks again

> GEP errors that are logged to the Eclipse error log are not always seen by 
> end-user
> ---
>
> Key: GERONIMODEVTOOLS-575
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-575
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.4, 2.2.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Attachments: 575.patch, 575_new.patch, 575_stopserver.patch
>
>
> For example, when deploying an erroneous war file to the Geronimo server will 
> result in the following to the Eclispe.log that the end-user may not likely 
> see.
> !ENTRY org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Distribution of module failed.  See log for details.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Unable to resolve resource reference 'jdbc/users' (Could not 
> auto-map to resource.  Try adding a resource-ref mapping to your Geronimo 
> deployment plan.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Search conducted in current module and dependencies:
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE )
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE org.apache.geronimo.common.DeploymentException: Unable to resolve 
> resource reference 'jdbc/users' (Could not auto-map to resource.  Try adding 
> a resource-ref mapping to your Geronimo deployment plan.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Search conducted in current module and dependencies:
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE )
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.connector.deployment.ResourceRefBuilder.buildNaming(ResourceRefBuilder.java:216)
> !SUBENTRY 1 org.apache.geronimo.

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

[Jack Cai]

I agree that clustering would be a great topic to cover! Might also mention
some performance tuning options together with it?

-Jack

On Thu, Jul 23, 2009 at 8:52 AM, Kevan Miller wrote:

>
> On Jul 22, 2009, at 6:58 PM, David Jencks wrote:
>
>  I think this is a good division of topics.
>>
>> I wonder if it would be more interesting to cover the various clustering
>> stuff we have in 2.2 rather than the security stuff.  I've talked about
>> security a couple of times before and it has a little bit of documentation
>> but I don't think anyone has ever pulled together all the clustering
>> stuff...
>>
>> wadi jetty/tomcat/ejb
>> ejb client failover
>> farm management
>> how to set up a web load balancer.
>>
>
> I'm good with that.
>
>
> 
> Session 1: Apache Geronimo 2.2
> Speakers: David Jencks and Vamsavardhana Reddy Chillakuru
>
> This talk will provide an overview of the Geronimo 2.2 release. Along with
> providing an overview of the new features found in 2.2, the talk will also
> discuss Geronimo Custom Assemblies and Application Security. Geronimo makes
> it easy to assemble a custom server around your applications, including only
> those features needed to run your apps. We'll see how to use maven to
> integrate this into your build process. This session will also discuss the
> clustering options available with Geronimo and configuring load-balancing
> and failover of web applications using mod_jk & Apache HTTP Server. After
> completing this session, the audience will be familiar with the clustering
> and farming features provided by Geronimo, running multiple instances of
> Geronimo server from the same installation, preparing their applications for
> deployment on the cluster and know how to configure Geronimo clusters to
> suit their needs.
>
>
>
> 
>
> Session 2: OSGi Blueprint Container Specification and Geronimo
> Speaker: Jarek Gawor
>
> This talk will provide a general overview of the Blueprint Container
> Specification and demonstrate some of its core features using Geronimo's
> Blueprint Container implementation. The talk will also describe some more
> advanced features of the Geronimo implementation such as Configuration Admin
> Service support and custom namespace handlers. Future plans will be
> discussed as well as how the Blueprint Container might be used and
> integrated within the existing Geronimo Kernel.
>
>
> 
>
> Session 3: Apache Geronimo 3.0: OSGi and Java EE6
> Speakers: David Jencks and Donald Woods
>
> This talk will provide a preview of the new features in Apache Geronimo
> 3.0. Including the OSGi support with the Geronimo kernel. We'll also discuss
> the new Java EE 6 features: Web Profiles, JPA 2.0, Servlet 3.0, EJB 3.1,
> etc. We'll also include demonstration of current functionality and discuss
> development outlook.
>
>
> 
>
> --kevan
>

[jira] Reopened: (GERONIMO-4709) start-server's -j flag does not work

[viola.lu (JIRA)]

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

viola.lu reopened GERONIMO-4709:



On windows: 
When run start-server.bat -j "c:\programme files\Java60\bin\java.exe", there is 
an parse error :Lexical Error at line 1 , Encountered "P" after "\\"
But on linux: ./start-server.sh -j /opt/ibm/java-i386-60/bin/java, this command 
runs well.


> start-server's -j flag does not work
> 
>
> Key: GERONIMO-4709
> URL: https://issues.apache.org/jira/browse/GERONIMO-4709
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: commands
>Affects Versions: 2.1.4
>Reporter: Jason Dillon
>Assignee: Jason Dillon
> Fix For: 2.1.5, 2.2
>
>
> Problem is that node.setAttribute(String, String) won't coerce 2nd param of 
> type java.io.File to string.

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

A question on GBean attribute

[Jack Cai]

In GAttributeInfo, there are 3 properties defined for an attribute,
including -

* persistent
* manageable
* framework

Can somebody explain what these properties mean? I have some vague
understanding but would like to hear from the experts. Thanks in advance!

-Jack

Re: Encrypt password in deployment plans and config.ser

[Jack Cai]

Thanks Ivan.

So the way I'm going to do this is to capture the encryption
meta-information in GBeanOverride whenever such information is passed into
it. Currently there are three palces -

1. When a GBeanOverride is constructed with a given GBeanData.
2. When a GBeanOverride is called to do "applyOverride".
3. When an attribute is set into a GBeanOverride at runtime.

This ensures that all the attributes for loaded GBeans will get the
up-to-date encryption information.

In addition to that, I will also retain the encryption information when
reading config.xml. This ensures that even if a GBean is not loaded during
one server run, the encrypted attribute will continue to be encrypted the
server is stopped.

With the above approach, the only occasion that an attribute does not get
encrypted when saving into config.xml even though it's specified as
"encrypted" in GBeanInfo is that -
 * the attribute value is written in clear text by user by editting the
config.xml, and
 * the GBean containing this attribute is not loaded during server runs

I suppose this is a reasonable exception.

Comments are welcome.

-Jack

On Tue, Jul 21, 2009 at 10:50 PM, Ivan  wrote:

> gbeanInfo is used to delare the class name of the gbean, it is used to add
> new gbean in the config.xml.
> eg. 
>
> 2009/7/21 Jack Cai 
>
> I've completed most of the coding for this small feature. Now I need to
>> figure out a way to get the "encrypted" meta-information from GAttributeInfo
>> in the GBeanOverride class so that it will encrypt attributes according to
>> the meta-information when saved to config.xml. This turns out to be a
>> non-trivial work, as GBeanOverride does not maintain any direct/indirect
>> reference to GAttributeInfo! It does contain a "gbeanInfo" field, but its
>> type is String and I cannot understand how its value could be used in any
>> way.
>>
>> One possible solution is to duplicate the "encrypted“ meta-information in
>> the config.xml, in a similar way as what we are doing with "null"
>> attributes. But apparently this is not the ideal way. Does anybody have a
>> better idea? Thanks a lot!
>>
>> -Jack
>>
>>
>>
>> On Wed, May 13, 2009 at 4:04 PM, Jack Cai  wrote:
>>
>>> Thanks Jarek for your comments! I should have provided more description
>>> about the fix -
>>>
>>> 1. setAttribute() is usually called by the unmarshaller, so it should
>>> actually do the decryption. Since the decryption will automatically bypass
>>> unecrypted values, it won't do any harm if the passed-in attribute value is
>>> not encrypted.
>>>
>>> 2. getAttribute() is usually called by various consumers that wants to
>>> read the real value (decrypted), so it just returns what is stored in the
>>> GBeanData (already decrypted value).
>>>
>>> 3. The current patch does do encryption for writeExternal(). The reason
>>> decryption is not done for readExternal() directly is because readExternal()
>>> calls setAttribute() which does the decryption.
>>>
>>> I agree that it's not optimal to hard-code to encrypt "password"
>>> attributes, and better to use the GAttributeInfo to make this configurable.
>>> My suggestion is to set encryption on for all attributes whose name contains
>>> "password" and off for the rest. We can thus eliminate the hard-code logic
>>> in GBeanOverride too (for encrption in config.xml).
>>>
>>> I'm going to create a patch if no objection.
>>>
>>> -Jack
>>>
>>> 2009/5/13 Jarek Gawor 
>>>
>>> Jack,

 I was thinking about this a while ago and had a slightly different
 approach. I was thinking of adding a 'protected' or 'encrypted'
 attribute to the GAttributeInfo (for example, just like the
 'persistent' attribute) to indicate that this attribute should be
 "encrypted" in the serialized file. I wanted to allow for any
 attribute to be encrypted even if it doesn't have the "password" name
 in it. And I think with this way we could also expose that setting via
 our GBean annotations.

 Btw, hmm... shouldn't encrypt be called in setAttribute() and decrypt
 in getAttribute() or at least encrypt in writeExternal() and decrypt
 in readExternal() ?

 Jarek

 On Tue, May 12, 2009 at 4:06 AM, Jack Cai  wrote:
 > Recently someone pointed out to us that password specified in the
 deployment
 > plan is stored in clear text in the config.ser after deployment, for
 > example, when deploying a datasource with the database password
 specified in
 > the deployment plan. I notice that there was another user mentioning
 exactly
 > the same problem in the geronimo-user list two years ago [1].
 >
 > I did a little more dig and also found this JIRA [2] along with this
 > discussion [3] on encrypting passwords in deployment plans.
 >
 > I understand that there are different arguments on what is "real"
 security.
 > But I also well appreciate users' concerns on having clear text
 password
 > appearing in the system. In Ch

[jira] Created: (GERONIMO-4763) i18n properties files should be converted to ascii at build time.

[Shawn Jiang (JIRA)]

i18n properties files should be converted  to ascii at build time.
--

 Key: GERONIMO-4763
 URL: https://issues.apache.org/jira/browse/GERONIMO-4763
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: usability
Affects Versions: 2.1.5, 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor


Current i18n properties files are stored in source code repo after they are 
converted to ascii from native offline.  It's very hard to contribute new 
translations.

We should keep native characters in source code while convert them to ascii at 
build time. maven plugin native2ascii-maven-plugin could be used here:

{code}

org.codehaus.mojo
native2ascii-maven-plugin
1.0-alpha-1

target/classes
src/main/resources



native2ascii-utf8

native2ascii


UTF8

ConsoleResources_jp.properties,
ConsoleResources_zh*.properties





{code}


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

Re: [BUILD] branches/2.1: Failed for Revision: 796663

[Shawn Jiang]

I got these failures locally.

On Wed, Jul 22, 2009 at 10:34 PM, Kevan Miller wrote:

> Are other people getting these failures? I don't see them on a local
> build...
>
> --kevan
>
> On Jul 22, 2009, at 9:02 AM, ga...@apache.org wrote:
>
>  Geronimo Revision: 796663 built with tests included
>>
>> See the full build-0800.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/build-0800.log
>>
>> Download the binaries from
>> http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> 
>> [INFO] Total time: 38 minutes 57 seconds
>> [INFO] Finished at: Wed Jul 22 08:46:43 EDT 2009
>> [INFO] Final Memory: 314M/946M
>> [INFO]
>> 
>>
>> TESTSUITE RESULTS (Failures only)
>> =
>>
>> Assembly: tomcat
>> =
>> See full test results and logs at
>> http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-tomcat/
>>
>> [INFO] Running corba-testsuite.corba-mytime
>> [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.453 sec <<< FAILURE!
>> --
>> [INFO] Running sec-testsuite.security
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.695 sec <<< FAILURE!
>> [INFO] Running web-testsuite.jsps
>> [INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed:
>> 1.199 sec <<< FAILURE!
>> --
>> [INFO] Running web-testsuite.myfaces
>> [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.318 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
>> [INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 2.035 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.183 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.207 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.198 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.215 sec <<< FAILURE!
>>
>> Assembly: jetty
>> =
>> See full test results and logs at
>> http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-jetty/
>>
>> [INFO] Running corba-testsuite.corba-mytime
>> [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.495 sec <<< FAILURE!
>> --
>> [INFO] Running sec-testsuite.security
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.74 sec <<< FAILURE!
>> [INFO] Running web-testsuite.jsps
>> [INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed:
>> 1.24 sec <<< FAILURE!
>> --
>> [INFO] Running web-testsuite.myfaces
>> [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.351 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
>> [INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 1.679 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.19 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.204 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.201 sec <<< FAILURE!
>> --
>> [INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
>> [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 0.231 sec <<< FAILURE!
>>
>> Samples: branches/2.1
>> =
>> Log:
>> http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/samples-0800.log
>>
>> Build status: OK
>>
>>
>


-- 
Shawn

[jira] Updated: (GERONIMODEVTOOLS-575) GEP errors that are logged to the Eclipse error log are not always seen by end-user

[Delos Dai (JIRA)]

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

Delos Dai updated GERONIMODEVTOOLS-575:
---

Attachment: 575_stopserver.patch

To handle server stopping failure, throw RuntimeException in terminate() 
method. It will simplify the solution in previous patch.

Thanks a lot!

> GEP errors that are logged to the Eclipse error log are not always seen by 
> end-user
> ---
>
> Key: GERONIMODEVTOOLS-575
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-575
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.4, 2.2.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Attachments: 575.patch, 575_new.patch, 575_stopserver.patch
>
>
> For example, when deploying an erroneous war file to the Geronimo server will 
> result in the following to the Eclispe.log that the end-user may not likely 
> see.
> !ENTRY org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Distribution of module failed.  See log for details.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Unable to resolve resource reference 'jdbc/users' (Could not 
> auto-map to resource.  Try adding a resource-ref mapping to your Geronimo 
> deployment plan.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Search conducted in current module and dependencies:
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE )
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE org.apache.geronimo.common.DeploymentException: Unable to resolve 
> resource reference 'jdbc/users' (Could not auto-map to resource.  Try adding 
> a resource-ref mapping to your Geronimo deployment plan.
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE Search conducted in current module and dependencies:
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE )
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.connector.deployment.ResourceRefBuilder.buildNaming(ResourceRefBuilder.java:216)
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53)
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:842)
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:347)
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
> !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
> !MESSAGE  at 
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARCon

When will geronimo release org/apache/geronimo/ext/tomcat 6.0.20 ?

[Shawn Jiang]

Will geronimo release it's own org/apache/geronimo/ext/tomcat/xxx 6.0.20 ?
if yes, When will it be released ?

-- 
Shawn

[jira] Closed: (GERONIMO-4760) Started ejb module cannot be stopped

[Forrest Xia (JIRA)]

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

Forrest Xia closed GERONIMO-4760.
-

Resolution: Fixed

Verify it in my latest local build, yes, it's fixed. So close it. thanks!

> Started ejb module cannot be stopped
> 
>
> Key: GERONIMO-4760
> URL: https://issues.apache.org/jira/browse/GERONIMO-4760
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.2
> Environment: Linux x86
> IBM Java 6
> 2.2 snapshot build 2009.07.16-15:10:04.515-0400
>Reporter: Forrest Xia
>Priority: Critical
> Attachments: bank-ear-2.1.1.2.ear
>
>
> Steps:
> 1. deploy the attached sample app bank, which includes an EJB module
> 2. try to stop it in admin console
> 2. try to uninstall it
> Problem:
> 1. when trying to stop the app, an exception appears in system console as 
> follows:
> 2009-07-22 16:12:19,888 ERROR [GBeanInstance] Problem in doStop of 
> org.apache.geronimo.samples/bank-ear/2.1.1.2/car?J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.2/car,j2eeType=EJBModule,name=bank-ejb-2.1.1.2.jar
> java.lang.ClassCastException: 
> org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper incompatible 
> with org.apache.openejb.core.ivm.naming.IvmContext
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:897)
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:784)
>   at 
> org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428)
>   at 
> org.apache.geronimo.openejb.EjbModuleImpl.stop(EjbModuleImpl.java:127)
>   at 
> org.apache.geronimo.openejb.EjbModuleImplGBean.doStop(EjbModuleImplGBean.java:43)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:181)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:227)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:207)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:702)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:683)
>   ... more
> 2. After uninstalled it, if you want to redeploy it without restarting 
> server, you will encounter deployment error, that tells you the ejb module is 
> still running.

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

[jira] Resolved: (GERONIMO-4714) Turn on openejb.strict.interface.declaration for OpenEJB

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4714.


Resolution: Fixed

Remove the workaround setting, after running the whole ejb30 cases, currently, 
we only have two cases failed. 
Revert the configurations from trunk at revision: 796926


> Turn on openejb.strict.interface.declaration for OpenEJB
> 
>
> Key: GERONIMO-4714
> URL: https://issues.apache.org/jira/browse/GERONIMO-4714
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
>
> In OpenEJB 3.1.*, a new option openejb.strict.interface.declaration is 
> imported.
> I would like to set this option with true, by default its value is false. 
> Currently, there maybe some issues of this option with the default value.
> Please refer to OpenEJB 1039, 
> https://issues.apache.org/jira/browse/OPENEJB-1039.

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

Re: [jira] Commented: (GERONIMO-4760) Started ejb module cannot be stopped

[Rodger]

I meet the same problem in

geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip

  17-Jul-2009 02:58   95M

It is latest build I can get. I'll test in the new build,if there is.

when stop the ejb,
ERROR [GBeanInstance] Problem in doStop of
org.apache.geronimo.samples/calculator-ejb/2.2.0/jar?J2EEApplication=null,j2eeType=EJBModule,name=org.apache.geronimo.samples/calculator-ejb/2.2.0/jar
java.lang.ClassCastException:
org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper
incompatible with org.apache.openejb.core.ivm.naming.IvmContext

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

[Kevan Miller]

On Jul 22, 2009, at 6:58 PM, David Jencks wrote:


I think this is a good division of topics.

I wonder if it would be more interesting to cover the various  
clustering stuff we have in 2.2 rather than the security stuff.   
I've talked about security a couple of times before and it has a  
little bit of documentation but I don't think anyone has ever pulled  
together all the clustering stuff...


wadi jetty/tomcat/ejb
ejb client failover
farm management
how to set up a web load balancer.


I'm good with that.


Session 1: Apache Geronimo 2.2
Speakers: David Jencks and Vamsavardhana Reddy Chillakuru

This talk will provide an overview of the Geronimo 2.2 release. Along  
with providing an overview of the new features found in 2.2, the talk  
will also discuss Geronimo Custom Assemblies and Application Security.  
Geronimo makes it easy to assemble a custom server around your  
applications, including only those features needed to run your apps.  
We'll see how to use maven to integrate this into your build process.  
This session will also discuss the clustering options available with  
Geronimo and configuring load-balancing and failover of web  
applications using mod_jk & Apache HTTP Server. After completing this  
session, the audience will be familiar with the clustering and farming  
features provided by Geronimo, running multiple instances of Geronimo  
server from the same installation, preparing their applications for  
deployment on the cluster and know how to configure Geronimo clusters  
to suit their needs.




Session 2: OSGi Blueprint Container Specification and Geronimo
Speaker: Jarek Gawor

This talk will provide a general overview of the Blueprint Container  
Specification and demonstrate some of its core features using  
Geronimo's Blueprint Container implementation. The talk will also  
describe some more advanced features of the Geronimo implementation  
such as Configuration Admin Service support and custom namespace  
handlers. Future plans will be discussed as well as how the Blueprint  
Container might be used and integrated within the existing Geronimo  
Kernel.




Session 3: Apache Geronimo 3.0: OSGi and Java EE6
Speakers: David Jencks and Donald Woods

This talk will provide a preview of the new features in Apache  
Geronimo 3.0. Including the OSGi support with the Geronimo kernel.  
We'll also discuss the new Java EE 6 features: Web Profiles, JPA 2.0,  
Servlet 3.0, EJB 3.1, etc. We'll also include demonstration of current  
functionality and discuss development outlook.




--kevan

[jira] Commented: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up

[David Jencks (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734412#action_12734412
 ] 

David Jencks commented on GERONIMO-4756:


This is a great sample!  I'd like to add it as a testsuite program... 

I have a simple change to jetty that AFAICT fixes the problem, I'm discussing 
it with the jetty community.  With it I get responses like
hello null

for the non-authenticated non-system pages,

hello foo after I log in as foo to customer,

and 

Secure service saying hello to null

for system.

Is this what you expect?

I can also take a look at the ServerAuthModule to see why it might not be 
working properly.



> jetty 7 ignores default subject settings unless authentication is set up
> 
>
> Key: GERONIMO-4756
> URL: https://issues.apache.org/jira/browse/GERONIMO-4756
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: Geronimo-4766.patch, jgs.tar.gz
>
>
> Jetty 7 should be setting up security stuff if a  is 
> definied, not only if authentication is specifically configured: this will 
> make default subjects work when no auth is configured.  Should not be a 
> problem for tomcat for some reason I found this problem there already :-)

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

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

[David Jencks]

I think this is a good division of topics.

I wonder if it would be more interesting to cover the various  
clustering stuff we have in 2.2 rather than the security stuff.  I've  
talked about security a couple of times before and it has a little bit  
of documentation but I don't think anyone has ever pulled together all  
the clustering stuff...


wadi jetty/tomcat/ejb
ejb client failover
farm management
how to set up a web load balancer.

thanks
david jencks


On Jul 22, 2009, at 3:32 PM, Kevan Miller wrote:



On Jul 21, 2009, at 9:23 AM, Donald Woods wrote:


Maybe we can create a mashup of the proposals to cover the following:

Session 1 - Geronimo 2.2 topics (current user community)
Administering Geronimo
Custom Server Assemblies
Securing Apps
Load balancing and high-availability
Would expect this session would contain more than we could cover in  
50 minutes, but we should introduce each topic and include pointers  
to the online docs that users could reference later for more details.


Session 2 - Blueprint Container Spec and Geronimo

Session 3 - Geronimo 3.0 and Java EE 6 (futures)
Geronimo 3.0 based on OSGi
Current milestone features
Present how much of Web Profile is available
JPA 2.0, EJB 3.1, Servlet 3.0, ...
How to start using 3.0 builds



OK. We're getting urged to finalize our agenda. In the spirit of  
Donald's mashup. How does the following work for everyone?



Session 1: Apache Geronimo 2.2
Speakers: David Jencks and Vamsavardhana Reddy Chillakuru

This talk will provide an overview of the Geronimo 2.2 release.  
Along with providing an overview of the new features found in 2.2,  
the talk will also discuss Geronimo Custom Assemblies and  
Application Security. Geronimo makes it easy to assemble a custom  
server around your applications, including only those features  
needed to run your apps. We'll see how to use maven to integrate  
this into your build process. Also, Apache Geronimo enables storing  
user credentials in a variety of data stores viz., simple text  
files, a database, an LDAP server and digital certificates. In this  
session we see how these data stores can be used to configure  
application security and how the necessary infrastructure can be run  
in Apache Geronimo itself.




Session 2: OSGi Blueprint Container Specification and Geronimo
Speaker: Jarek Gawor

This talk will provide a general overview of the Blueprint Container  
Specification and demonstrate some of its core features using  
Geronimo's Blueprint Container implementation. The talk will also  
describe some more advanced features of the Geronimo implementation  
such as Configuration Admin Service support and custom namespace  
handlers. Future plans will be discussed as well as how the  
Blueprint Container might be used and integrated within the existing  
Geronimo Kernel.




Session 3: Apache Geronimo 3.0: OSGi and Java EE6
Speakers: David Jencks and Donald Woods

This talk will provide a preview of the new features in Apache  
Geronimo 3.0. Including the OSGi support with the Geronimo kernel.  
We'll also discuss the new Java EE 6 features: Web Profiles, JPA  
2.0, Servlet 3.0, EJB 3.1, etc. We'll also include demonstration of  
current functionality and discuss development outlook.




--kevan

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

[Kevan Miller]

On Jul 21, 2009, at 9:23 AM, Donald Woods wrote:


Maybe we can create a mashup of the proposals to cover the following:

Session 1 - Geronimo 2.2 topics (current user community)
Administering Geronimo
Custom Server Assemblies
Securing Apps
Load balancing and high-availability
Would expect this session would contain more than we could cover in  
50 minutes, but we should introduce each topic and include pointers  
to the online docs that users could reference later for more details.


Session 2 - Blueprint Container Spec and Geronimo

Session 3 - Geronimo 3.0 and Java EE 6 (futures)
Geronimo 3.0 based on OSGi
Current milestone features
Present how much of Web Profile is available
JPA 2.0, EJB 3.1, Servlet 3.0, ...
How to start using 3.0 builds



OK. We're getting urged to finalize our agenda. In the spirit of  
Donald's mashup. How does the following work for everyone?



Session 1: Apache Geronimo 2.2
Speakers: David Jencks and Vamsavardhana Reddy Chillakuru

This talk will provide an overview of the Geronimo 2.2 release. Along  
with providing an overview of the new features found in 2.2, the talk  
will also discuss Geronimo Custom Assemblies and Application Security.  
Geronimo makes it easy to assemble a custom server around your  
applications, including only those features needed to run your apps.  
We'll see how to use maven to integrate this into your build process.  
Also, Apache Geronimo enables storing user credentials in a variety of  
data stores viz., simple text files, a database, an LDAP server and  
digital certificates. In this session we see how these data stores can  
be used to configure application security and how the necessary  
infrastructure can be run in Apache Geronimo itself.




Session 2: OSGi Blueprint Container Specification and Geronimo
Speaker: Jarek Gawor

This talk will provide a general overview of the Blueprint Container  
Specification and demonstrate some of its core features using  
Geronimo's Blueprint Container implementation. The talk will also  
describe some more advanced features of the Geronimo implementation  
such as Configuration Admin Service support and custom namespace  
handlers. Future plans will be discussed as well as how the Blueprint  
Container might be used and integrated within the existing Geronimo  
Kernel.




Session 3: Apache Geronimo 3.0: OSGi and Java EE6
Speakers: David Jencks and Donald Woods

This talk will provide a preview of the new features in Apache  
Geronimo 3.0. Including the OSGi support with the Geronimo kernel.  
We'll also discuss the new Java EE 6 features: Web Profiles, JPA 2.0,  
Servlet 3.0, EJB 3.1, etc. We'll also include demonstration of current  
functionality and discuss development outlook.




--kevan

[jira] Commented: (GERONIMO-4759) Remove repository entries via Console

[JIRA]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734320#action_12734320
 ] 

Jürgen Weber commented on GERONIMO-4759:


A "non-server" jar is a jar that was added after the creation/installation of 
the server.

> Remove repository entries via Console
> -
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Reporter: Jürgen Weber
> Fix For: 2.2
>
>
> The Repository Viewer portlet should offer to remove entries that were 
> formerly added by the user (that are not part of the server configuration 
> itself).
> If you can add repository entries via the console it would be consistent to 
> remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"

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

[jira] Commented: (GERONIMO-4703) Upgrade scout to 1.1 when released

[Kurt T Stam (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734314#action_12734314
 ] 

Kurt T Stam commented on GERONIMO-4703:
---

We are about to start a vote on scout 1.1. Can someone check that the applied 
fix is what the doctor ordered?

Thx,

--Kurt

> Upgrade scout to 1.1 when released
> --
>
> Key: GERONIMO-4703
> URL: https://issues.apache.org/jira/browse/GERONIMO-4703
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: David Jencks
>
> Scout has a 1.0 release , unfortunately we can't use it due to 
> https://issues.apache.org/jira/browse/SCOUT-72.
> There does appear to be some activity there, so perhaps there will be a 1.1 
> we can use soon.

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

[jira] Commented: (GERONIMO-4703) Upgrade scout to 1.1 when released

[Kurt T Stam (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734317#action_12734317
 ] 

Kurt T Stam commented on GERONIMO-4703:
---

We are about to start a vote for release of Scout-1.1rc1. Can someone check 
that the fix for scout-72 does the trick for you?

thx,

--Kurt

> Upgrade scout to 1.1 when released
> --
>
> Key: GERONIMO-4703
> URL: https://issues.apache.org/jira/browse/GERONIMO-4703
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: David Jencks
>
> Scout has a 1.0 release , unfortunately we can't use it due to 
> https://issues.apache.org/jira/browse/SCOUT-72.
> There does appear to be some activity there, so perhaps there will be a 1.1 
> we can use soon.

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

[jira] Created: (GERONIMO-4762) Databinding exception issue with Axis

[Robert Palmer (JIRA)]

Databinding exception issue with Axis
-

 Key: GERONIMO-4762
 URL: https://issues.apache.org/jira/browse/GERONIMO-4762
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.1.4
 Environment: Linux x64
Reporter: Robert Palmer


I'm having an issue with Axis from the version of Geronimo I downloaded last 
night (on July 21, 2009): geronimo-tomcat6-javaee5-2.1.4.  The bug relates to 
this exact description of the problem I'm having that was fixed in April of 
2007: https://issues.apache.org/jira/browse/AXIS2-2313

It's caused by a web service accessing the soap header from a handler when two 
web services are active (i.e., a web service calls another web service).  The 
exact exception thrown is: "javax.xml.ws.WebServiceException: An internal error 
occurred. The org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl 
block object is already consumed. Processing cannot continue. Run with the 
debug option to determine where the block was first consumed."

Does anyone know if this fix was included in the version of Geronimo that I 
downloaded?

Thanks,
Robert

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

[BUILD] trunk: Failed for Revision: 796820

[gawor]

Geronimo Revision: 796820 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 9 seconds
[INFO] Finished at: Wed Jul 22 15:45:36 EDT 2009
[INFO] Final Memory: 399M/1007M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/logs-1500-tomcat/
 
 
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:47.718
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:18.350) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.187) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:41.352) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.531) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:39.483) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:34.627) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.703) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:55.398) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:04.841) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.240) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.819) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.864) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:35.549) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:10.021) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.260) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.728) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.964) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:52.941) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:46.468) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.116) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.118) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.759) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.147) 
[INFO] web-testsuite/test-web-forward RUNNING
[INFO

[BUILD] branches/2.1: Failed for Revision: 796793

[gawor]

Geronimo Revision: 796793 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/build-1400.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 3 seconds
[INFO] Finished at: Wed Jul 22 14:43:03 EDT 2009
[INFO] Final Memory: 318M/937M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-1400-tomcat/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.461 
sec <<< FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.718 
sec <<< FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.178 
sec <<< FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.344 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.845 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.186 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.204 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.207 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.211 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-1400-jetty/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.502 
sec <<< FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.756 
sec <<< FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.227 
sec <<< FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.355 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.636 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.19 sec 
<<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.21 sec 
<<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.201 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.24 sec 
<<< FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/samples-1400.log
 
Build status: OK
 

[jira] Commented: (GERONIMO-4759) Remove repository entries via Console

[David Jencks (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734187#action_12734187
 ] 

David Jencks commented on GERONIMO-4759:


I think that "remove" functionality is a moderately good idea but
-- there's really no way to distinguish between "server" and "non-server" jars 
since you can assemble a server out of any plugins you want
-- any such action should show all the dependencies that would be affected so 
you can see the consequences

> Remove repository entries via Console
> -
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Reporter: Jürgen Weber
> Fix For: 2.2
>
>
> The Repository Viewer portlet should offer to remove entries that were 
> formerly added by the user (that are not part of the server configuration 
> itself).
> If you can add repository entries via the console it would be consistent to 
> remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"

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

[BUILD] trunk: Failed for Revision: 796684

[gawor]

Geronimo Revision: 796684 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 39 seconds
[INFO] Finished at: Wed Jul 22 09:47:18 EDT 2009
[INFO] Final Memory: 400M/1015M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/logs-0900-tomcat/
 
 
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:46.715
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:14.428) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:34.801) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.596) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.533) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:32.708) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:36.079) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:03.322) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:53.830) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:02.181) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.343) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.668) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.468) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:34.705) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:41.558) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:01.080) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.303) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.030) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:52.823) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:46.055) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.230) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.248) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.059) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.155) 
[INFO] web-testsuite/test-web-forward RUNNING

Re: [BUILD] branches/2.1: Failed for Revision: 796663

[Kevan Miller]

Are other people getting these failures? I don't see them on a local  
build...


--kevan
On Jul 22, 2009, at 9:02 AM, ga...@apache.org wrote:


Geronimo Revision: 796663 built with tests included

See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/build-0800.log

Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722
[INFO] BUILD SUCCESSFUL
[INFO]  


[INFO] Total time: 38 minutes 57 seconds
[INFO] Finished at: Wed Jul 22 08:46:43 EDT 2009
[INFO] Final Memory: 314M/946M
[INFO]  



TESTSUITE RESULTS (Failures only)
=

Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-tomcat/

[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.453 sec <<< FAILURE!

--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.695 sec <<< FAILURE!

[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time  
elapsed: 1.199 sec <<< FAILURE!

--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.318 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 2.035 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.183 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.207 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.198 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.215 sec <<< FAILURE!


Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-jetty/

[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.495 sec <<< FAILURE!

--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.74 sec <<< FAILURE!

[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time  
elapsed: 1.24 sec <<< FAILURE!

--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.351 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 1.679 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.19 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.204 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.201 sec <<< FAILURE!

--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time  
elapsed: 0.231 sec <<< FAILURE!


Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/samples-0800.log

Build status: OK

[jira] Commented: (GERONIMODEVTOOLS-583) and coexistence results in error in geronimo-application deployment plan on eclipse 3.5

[Delos Dai (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734126#action_12734126
 ] 

Delos Dai commented on GERONIMODEVTOOLS-583:


After investigation, I found it's a problem of xml editor validation in WTP. I 
have create a bug in eclipse bugzilla and provide them with a test case.

Here is the bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=284272

>  and  coexistence results in error in 
> geronimo-application deployment plan on eclipse 3.5
> --
>
> Key: GERONIMODEVTOOLS-583
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-583
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
> Environment: os:win 2003
> eclipse: 3.5
> JDK: 1.5
>Reporter: viola.lu
>Assignee: Delos Dai
>Priority: Minor
>
> 1.Install GEP in eclipse 3.5 , and create an enterprise application project, 
> add 
> 
>   admin
>   
>  in application.xml deployment descriptor, 
> 2.Open geronimo-application.xml , add:
>  
> 
> 
>  class="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal" 
> name="geronimo-default"/>
> 
> 
> 
>  class="org.apache.geronimo.system.logging.log4j.ApplicationLog4jConfigurationGBean"
>  name="test"/>
> to it, but there is an error in deployment plan.
> This problem doesn't exist in eclipse 3.4.*

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

[jira] Commented: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up

[Trygve Hardersen (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734105#action_12734105
 ] 

Trygve Hardersen commented on GERONIMO-4756:


Hi

I've been trying to upgrade our application to use Jetty7, but can't get the 
run-as security to work. Since our application is rather complex and big, I've 
created a sample project that illustrates the problem in a more controlled 
environment using the current Geronimo trunk (rev 796620) without any 
modifications.

The sample project is called JGS (Jotta Geronimo Security) and has 3 components 
that are deployed as Geronimo plugins:

realm-plugin - Holds the security realm and credential store
ejb-plugin - Holds the EJB service layer
web-plugin - Holds the WAR HTTP layer

The realm-plugin uses a custom login module TestLoginModule that checks that 
the supplied username matches the supplied password. If the username is 
"admin", "anonymous" or "system", the username will also be used as role name. 
If not, the role name will be set to "customer". The realm-plugin also holds a 
credential store that gives the username and password for the "anonymous" and 
"system" run-as users.

The ejb-plugin has two stateless sessions beans; TestServiceEJB and 
SecureServiceEJB. Both EJBs are set to run-as "system". TestServiceEJB declares 
the roles "admin", "anonymous", "customer" and "system", and references the 
SecureServiceEJB. TestServiceEJB has three "hello" methods:

sayHello(String) - Says hello to admin, anonymous, customer and system users.
sayHello() - Says hello customer users.
secureHello(String) - Says hello to admin, customer and system users using 
SecureSeviceEJB to demonstrate run-as security.

The SecureServiceEJB declares the same roles as TestServiceEJB, but only has 
one method:

sayHello(String) - Says hello only to system components.

In other words SecureServiceEJB can only be used by callers in the "system" 
role, such as TestServiceEJB.

All of this work as expected including run-as security, at least when I use 
remote EJB to test the services directly. See RemoteEJBTest in the ejb-test 
module. The problem starts when I try to use run-as security in the web-plugin. 
This is what I want:

/welcome - WelcomeServlet says hello to the user identified by a parameter 
called "name". Set to run-as "anonymous".
/default - DefaultServlet does the same as WelcomeServlet, but does not declare 
run-as and should use the default run-as identity with is also "anonymous".
/customer - Customer servlet is only accessible by "customer" users, and does 
not use run-as.
/system - SystemServlet should run-as system because it is a secure system 
component.

Of these 4 URLs I can only get /customer to work properly. When the URL is used 
the BASIC authentication triggers and the user can log in as "test"/"test" or 
whatever they like. The username is picked up all the way down to the EJB that 
greets the customer.

The 3 other URLs generally do not work. I've tried many configuration 
combinations, such as using run-as annotations, defining security constraints 
for the "run-as" URLs, disabling the default run-as subject and only using a 
single servlet, but I can't get things to run-as anything consistently. 
Strangely I'm 99% sure I've seen the run-as security work a couple of times, at 
least after doing normal authentication first. Could there be a concurrency 
issue somewhere?

I'm attaching the sample project. Thanks a lot for looking into this, and 
please let me know if you have questions.


> jetty 7 ignores default subject settings unless authentication is set up
> 
>
> Key: GERONIMO-4756
> URL: https://issues.apache.org/jira/browse/GERONIMO-4756
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: Geronimo-4766.patch, jgs.tar.gz
>
>
> Jetty 7 should be setting up security stuff if a  is 
> definied, not only if authentication is specifically configured: this will 
> make default subjects work when no auth is configured.  Should not be a 
> problem for tomcat for some reason I found this problem there already :-)

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

[jira] Updated: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up

[Trygve Hardersen (JIRA)]

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

Trygve Hardersen updated GERONIMO-4756:
---

Attachment: jgs.tar.gz

The JGS sample project.

> jetty 7 ignores default subject settings unless authentication is set up
> 
>
> Key: GERONIMO-4756
> URL: https://issues.apache.org/jira/browse/GERONIMO-4756
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: Geronimo-4766.patch, jgs.tar.gz
>
>
> Jetty 7 should be setting up security stuff if a  is 
> definied, not only if authentication is specifically configured: this will 
> make default subjects work when no auth is configured.  Should not be a 
> problem for tomcat for some reason I found this problem there already :-)

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

[BUILD] branches/2.1: Failed for Revision: 796663

[gawor]

Geronimo Revision: 796663 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/build-0800.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 57 seconds
[INFO] Finished at: Wed Jul 22 08:46:43 EDT 2009
[INFO] Final Memory: 314M/946M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-tomcat/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.453 
sec <<< FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.695 
sec <<< FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.199 
sec <<< FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.318 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.035 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.183 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.207 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.198 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.215 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/logs-0800-jetty/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.495 
sec <<< FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.74 sec 
<<< FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec 
<<< FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.351 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.679 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.19 sec 
<<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.204 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.201 
sec <<< FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.231 
sec <<< FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090722/samples-0800.log
 
Build status: OK
 

[jira] Updated: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse

[Rodger Zhang (JIRA)]

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

Rodger Zhang updated GERONIMODEVTOOLS-198:
--

Attachment: daytrader.zip

> Daytrader deployment exception in Eclipse
> -
>
> Key: GERONIMODEVTOOLS-198
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
>Priority: Minor
> Fix For: 2.2.0
>
> Attachments: daytrader.zip
>
>
> There is a deployment exception occurring in Eclipse when deploying 
> Daytrader, although it seems to be fairly benign since Daytrader ultimately 
> does deploy and seems to function correctly. 
> Booting Geronimo Kernel (in Java 1.5.0_12)...
> Module  1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car  
>started in  1.453s
> Module  2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car 
>started in   .359s
> Module  3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car 
>started in   .875s
> Module  4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car   
>started in   .000s
> Module  5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car 
>   INFO - Configuring Service(id=Default MDB Container, type=Container, 
> provider-id=Default MDB Container)
> INFO - Configuring Service(id=Default Stateless Container, type=Container, 
> provider-id=Default Stateless Container)
> INFO - Configuring app: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Loaded Module: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Assembling app: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome)
> INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, 
> container=Default Stateless Container)
> INFO - Configuring Service(id=Default Stateful Container, type=Container, 
> provider-id=Default Stateful Container)
> INFO - Configuring Service(id=Default BMP Container, type=Container, 
> provider-id=Default BMP Container)
> INFO - Configuring Service(id=Default CMP Container, type=Container, 
> provider-id=Default CMP Container)
>  started in 11.328s
> Module  6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car 
>started in  1.782s
> Module  7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car 
>started in   .000s
> Module  8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car 
>started in   .000s
> Module  9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car 
>started in   .000s
> Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car  
>started in   .000s
> Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car 
>started in   .016s
> Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car 
>   ERROR - "Restricted listeners property file not found
>  started in  3.172s
> Module 13/31 
> org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car
> started in   .844s
> Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car   
>started in   .516s
> Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car  
>started in   .234s
> Module 16/31 
> org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car 
> started in   .172s
> Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car
>started in   .219s
> Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car 
>started in   .250s
> Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car  
>started in   .312s
> Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car   
>started in  1.672s
> Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car
>started in   .125s
> Module 22/31 org.apache.geronimo.configs/sharedlib/2.1-SNAPSHOT/car   
>started in   .015s
> Module 23/31 org.apache.geronimo.configs/tomcat6-deployer/2.1-SNAPSHOT/car
>started in   .187s
> Module 24/31 org.apache.geronimo.configs/jasper-deployer/2.1-SNAPSHOT/car 
>  

[jira] Commented: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse

[Rodger Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734051#action_12734051
 ] 

Rodger Zhang commented on GERONIMODEVTOOLS-198:
---

Are you migrate the daytrader app from maven-building-version to GEP?
If so, possibly, some configuration file (like manifest.mf, deployment plan) 
may have bot been configured  incorrectly.
I have a very daytrader app which can be deployed successfully with GEP. I'll 
attach it.
Conclusively, it is not a GEP bug, suggest to close this jira. 

> Daytrader deployment exception in Eclipse
> -
>
> Key: GERONIMODEVTOOLS-198
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
>Priority: Minor
> Fix For: 2.2.0
>
>
> There is a deployment exception occurring in Eclipse when deploying 
> Daytrader, although it seems to be fairly benign since Daytrader ultimately 
> does deploy and seems to function correctly. 
> Booting Geronimo Kernel (in Java 1.5.0_12)...
> Module  1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car  
>started in  1.453s
> Module  2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car 
>started in   .359s
> Module  3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car 
>started in   .875s
> Module  4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car   
>started in   .000s
> Module  5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car 
>   INFO - Configuring Service(id=Default MDB Container, type=Container, 
> provider-id=Default MDB Container)
> INFO - Configuring Service(id=Default Stateless Container, type=Container, 
> provider-id=Default Stateless Container)
> INFO - Configuring app: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Loaded Module: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Assembling app: 
> jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/
> INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome)
> INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, 
> container=Default Stateless Container)
> INFO - Configuring Service(id=Default Stateful Container, type=Container, 
> provider-id=Default Stateful Container)
> INFO - Configuring Service(id=Default BMP Container, type=Container, 
> provider-id=Default BMP Container)
> INFO - Configuring Service(id=Default CMP Container, type=Container, 
> provider-id=Default CMP Container)
>  started in 11.328s
> Module  6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car 
>started in  1.782s
> Module  7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car 
>started in   .000s
> Module  8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car 
>started in   .000s
> Module  9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car 
>started in   .000s
> Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car  
>started in   .000s
> Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car 
>started in   .016s
> Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car 
>   ERROR - "Restricted listeners property file not found
>  started in  3.172s
> Module 13/31 
> org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car
> started in   .844s
> Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car   
>started in   .516s
> Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car  
>started in   .234s
> Module 16/31 
> org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car 
> started in   .172s
> Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car
>started in   .219s
> Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car 
>started in   .250s
> Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car  
>started in   .312s
> Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car   
>started in  1.672s
> Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car
> 

[jira] Created: (GERONIMO-4761) MBean not found exception: agent-car-jmx

[Chi Runhua (JIRA)]

MBean not found exception: agent-car-jmx 
-

 Key: GERONIMO-4761
 URL: https://issues.apache.org/jira/browse/GERONIMO-4761
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: monitoring
Affects Versions: 2.2
 Environment: From console
Reporter: Chi Runhua


1. Log in to console and go to *Monitoring* portlet,
2. Click *Add a new server* and choose protocol as JMX
3. Fill in other fields as requested, then click *Add*

Exception thrown from command line:

{code}
java.lang.Exception: [ERROR] Required mbean not found: agent-car-jmx
at 
org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:123)
at 
org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:55)
at 
jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:271)
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 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
at 
org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
at 
org.apache.geronimo.monitoring.console.MonitoringPortlet.doEdit(MonitoringPortlet.java:412)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:253)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
at 
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
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:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at 
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at 
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
at 
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at 
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
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 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
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 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.

[BUILD] trunk: Failed for Revision: 796616

[gawor]

Geronimo Revision: 796616 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 43 minutes 27 seconds
[INFO] Finished at: Wed Jul 22 03:47:54 EDT 2009
[INFO] Final Memory: 428M/1016M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090722/logs-0300-tomcat/
 
 
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:46.915
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:20.567) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.153) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.151) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.177) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:37.696) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:48.635) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:04.843) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:01:04.628) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:50.563) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:46.657) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.760) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.624) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:35.051) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:13.708) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.704) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.669) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.296) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:55.373) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:46.333) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.493) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.916) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.022) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.154) 
[INFO] web-testsuite/test-web-forward RUNNING

[jira] Commented: (GERONIMO-4760) Started ejb module cannot be stopped

[Ivan (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734034#action_12734034
 ] 

Ivan commented on GERONIMO-4760:


Do you use the latest Geronimo-2.2 snapshot binary file?
This should be fixed a week ago.

> Started ejb module cannot be stopped
> 
>
> Key: GERONIMO-4760
> URL: https://issues.apache.org/jira/browse/GERONIMO-4760
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.2
> Environment: Linux x86
> IBM Java 6
> 2.2 snapshot build 2009.07.16-15:10:04.515-0400
>Reporter: Forrest Xia
>Priority: Critical
> Attachments: bank-ear-2.1.1.2.ear
>
>
> Steps:
> 1. deploy the attached sample app bank, which includes an EJB module
> 2. try to stop it in admin console
> 2. try to uninstall it
> Problem:
> 1. when trying to stop the app, an exception appears in system console as 
> follows:
> 2009-07-22 16:12:19,888 ERROR [GBeanInstance] Problem in doStop of 
> org.apache.geronimo.samples/bank-ear/2.1.1.2/car?J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.2/car,j2eeType=EJBModule,name=bank-ejb-2.1.1.2.jar
> java.lang.ClassCastException: 
> org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper incompatible 
> with org.apache.openejb.core.ivm.naming.IvmContext
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:897)
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:784)
>   at 
> org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428)
>   at 
> org.apache.geronimo.openejb.EjbModuleImpl.stop(EjbModuleImpl.java:127)
>   at 
> org.apache.geronimo.openejb.EjbModuleImplGBean.doStop(EjbModuleImplGBean.java:43)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:181)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:227)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:207)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:702)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:683)
>   ... more
> 2. After uninstalled it, if you want to redeploy it without restarting 
> server, you will encounter deployment error, that tells you the ejb module is 
> still running.

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

[jira] Updated: (GERONIMO-4760) Started ejb module cannot be stopped

[Forrest Xia (JIRA)]

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

Forrest Xia updated GERONIMO-4760:
--

Attachment: bank-ear-2.1.1.2.ear

sample application with ejb module

> Started ejb module cannot be stopped
> 
>
> Key: GERONIMO-4760
> URL: https://issues.apache.org/jira/browse/GERONIMO-4760
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.2
> Environment: Linux x86
> IBM Java 6
> 2.2 snapshot build 2009.07.16-15:10:04.515-0400
>Reporter: Forrest Xia
>Priority: Critical
> Attachments: bank-ear-2.1.1.2.ear
>
>
> Steps:
> 1. deploy the attached sample app bank, which includes an EJB module
> 2. try to stop it in admin console
> 2. try to uninstall it
> Problem:
> 1. when trying to stop the app, an exception appears in system console as 
> follows:
> 2009-07-22 16:12:19,888 ERROR [GBeanInstance] Problem in doStop of 
> org.apache.geronimo.samples/bank-ear/2.1.1.2/car?J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.2/car,j2eeType=EJBModule,name=bank-ejb-2.1.1.2.jar
> java.lang.ClassCastException: 
> org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper incompatible 
> with org.apache.openejb.core.ivm.naming.IvmContext
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:897)
>   at 
> org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:784)
>   at 
> org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428)
>   at 
> org.apache.geronimo.openejb.EjbModuleImpl.stop(EjbModuleImpl.java:127)
>   at 
> org.apache.geronimo.openejb.EjbModuleImplGBean.doStop(EjbModuleImplGBean.java:43)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:181)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:227)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:207)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:702)
>   at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:683)
>   ... more
> 2. After uninstalled it, if you want to redeploy it without restarting 
> server, you will encounter deployment error, that tells you the ejb module is 
> still running.

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

[jira] Created: (GERONIMO-4760) Started ejb module cannot be stopped

[Forrest Xia (JIRA)]

Started ejb module cannot be stopped


 Key: GERONIMO-4760
 URL: https://issues.apache.org/jira/browse/GERONIMO-4760
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: OpenEJB
Affects Versions: 2.2
 Environment: Linux x86
IBM Java 6
2.2 snapshot build 2009.07.16-15:10:04.515-0400
Reporter: Forrest Xia
Priority: Critical
 Attachments: bank-ear-2.1.1.2.ear

Steps:
1. deploy the attached sample app bank, which includes an EJB module
2. try to stop it in admin console
2. try to uninstall it

Problem:
1. when trying to stop the app, an exception appears in system console as 
follows:
2009-07-22 16:12:19,888 ERROR [GBeanInstance] Problem in doStop of 
org.apache.geronimo.samples/bank-ear/2.1.1.2/car?J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.2/car,j2eeType=EJBModule,name=bank-ejb-2.1.1.2.jar
java.lang.ClassCastException: 
org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper incompatible 
with org.apache.openejb.core.ivm.naming.IvmContext
at 
org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:897)
at 
org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:784)
at 
org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428)
at 
org.apache.geronimo.openejb.EjbModuleImpl.stop(EjbModuleImpl.java:127)
at 
org.apache.geronimo.openejb.EjbModuleImplGBean.doStop(EjbModuleImplGBean.java:43)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:181)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:227)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:207)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:702)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:683)
... more
2. After uninstalled it, if you want to redeploy it without restarting server, 
you will encounter deployment error, that tells you the ejb module is still 
running.

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

[jira] Created: (GERONIMO-4759) Remove repository entries via Console

[JIRA]

Remove repository entries via Console
-

 Key: GERONIMO-4759
 URL: https://issues.apache.org/jira/browse/GERONIMO-4759
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: console
Reporter: Jürgen Weber
 Fix For: 2.2


The Repository Viewer portlet should offer to remove entries that were formerly 
added by the user (that are not part of the server configuration itself).

If you can add repository entries via the console it would be consistent to 
remove them via the console, too.

On the details view for an entry there should be e.g.

"remove mysql/mysql-connector-java/3.1.14/jar"


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

[jira] Commented: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard

[JIRA]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734027#action_12734027
 ] 

Jürgen Weber commented on GERONIMO-4725:


With groupid "mysql" I got the DataSource to work, thanks.

But this should be fixed, how should users know which dependency to use?

And, if there is a fixed dependency for the driver gbean, why should the user  
choose a Driver JAR at all? It would be better if selecting a Database Type 
would show the necessary driver jars:

selecting Database Type "MySQL" would display
"this needs mysql/mysql-connector-java//jar in the repository"

> MySQL jdbc connector/driver jars don't show up in the database pool wizard
> --
>
> Key: GERONIMO-4725
> URL: https://issues.apache.org/jira/browse/GERONIMO-4725
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.4
> Environment: Geronimo 2.1.4, WindowsXP
>Reporter: Jan Snelders
>Assignee: Rex Wang
> Fix For: 2.1.4
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> MySQL connector/driver jars don't show up in the database pool wizard when 
> added to the repository even if you download the 3.x.x driver using the exact 
> same wizard.
> Steps to reproduce;
> - Start a newly installed geronimo 2.1.4. server (I only tested on WindowsXP)
> - login to the web console
> - Start adding a connection pool using the 'Geronimo database pool wizard'
> - Choose 'MySQL' for 'Database Type' and click on 'Next' to go to the next 
> step
> - The multiple select control labeled; 'Driver JAR' is empty at this time, 
> choose 'Download a driver' and install the  MySQL Connector /J 3.1.12
> - When done installing the connector the wizard refuses to show the installed 
> connector/driver
> - The problem also accures also when mannually adding the latest MySQL 
> connector to the repository (under the group "mysql")
> This bug is not present in geronimo 2.1.3 (tested on WindowsXP)

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

[jira] Commented: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up

[David Jencks (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734026#action_12734026
 ] 

David Jencks commented on GERONIMO-4756:


Actually I think the best solution is for jetty to call 
identitySolution.associate with the unauthenticated identity. need to talk 
to greg about this.

> jetty 7 ignores default subject settings unless authentication is set up
> 
>
> Key: GERONIMO-4756
> URL: https://issues.apache.org/jira/browse/GERONIMO-4756
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: Geronimo-4766.patch
>
>
> Jetty 7 should be setting up security stuff if a  is 
> definied, not only if authentication is specifically configured: this will 
> make default subjects work when no auth is configured.  Should not be a 
> problem for tomcat for some reason I found this problem there already :-)

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

[jira] Commented: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up

[David Jencks (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734020#action_12734020
 ] 

David Jencks commented on GERONIMO-4756:


In rev 796620 I modified NoneAuthenticator to return a Authentication.User 
containing the default subject, so now the default subject should get set on 
the thread.  Could you post details of how to see the problems with this, on 
the tck list if necessary?

> jetty 7 ignores default subject settings unless authentication is set up
> 
>
> Key: GERONIMO-4756
> URL: https://issues.apache.org/jira/browse/GERONIMO-4756
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: Geronimo-4766.patch
>
>
> Jetty 7 should be setting up security stuff if a  is 
> definied, not only if authentication is specifically configured: this will 
> make default subjects work when no auth is configured.  Should not be a 
> problem for tomcat for some reason I found this problem there already :-)

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