[jira] Commented: (GSHELL-157) Dynamically adding / removing commands does not work well
[ https://issues.apache.org/jira/browse/GSHELL-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671563#action_12671563 ] Jason Dillon commented on GSHELL-157: - Ya, a side effect of leaning on VFS to handle the storage, I notice there is a problem with setting/unsetting/setting aliases too. > Dynamically adding / removing commands does not work well > - > > Key: GSHELL-157 > URL: https://issues.apache.org/jira/browse/GSHELL-157 > Project: GShell > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 1.0-alpha-2 > > > When resolving commands, the command resolver uses a virtual file system. > Unfortunately, the data for virtual file systems is always cached, which > means that removing a command will still make it available for resolution. > The cache problem is caused by the DelegateFileObject which does not refresh > the underlying file. -- 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: 741985
Geronimo Revision: 741985 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 40 seconds
[INFO] Finished at: Sat Feb 07 21:41:41 EST 2009
[INFO] Final Memory: 629M/975M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[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:41.704
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.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:00:59.443)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.408)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.823)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.435)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:22.362)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:20.154)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:43.649)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.590)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:45.132)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:40.329)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.354)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.887)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.224)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.522)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:53.841)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:04.876)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.533)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.642)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.718) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.129)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[jira] Commented: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671551#action_12671551 ] Kan Ogawa commented on GERONIMO-4485: - Gang, My attached patches contain the defalut locale message resources only. After committing them, would you update Chinese ones for V2.1? Also we, Japan Apache Geronimo Users Group, are now working to make Japanese locale ones. > Port the GERONIMO-4474 patch for V2.1 > - > > Key: GERONIMO-4485 > URL: https://issues.apache.org/jira/browse/GERONIMO-4485 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Fix For: 2.1.4 > > Attachments: activemq-portlets.patch, console-base-portlets.patch, > console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, > mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, > plancreator-console-tomcat.patch, plancreator-portlets.patch, > plugin-portlets.patch, sysdb-portlets.patch > > > Target release should be 2.2, if you can attach the patches by Jan. 7th. > If you would like to see this in 2.1.4, then please attach additional patches > created from that branch and we'll try to get them in after we wrap up the > 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Patch Info: [Patch Available] Affects Version/s: (was: 2.2) > Port the GERONIMO-4474 patch for V2.1 > - > > Key: GERONIMO-4485 > URL: https://issues.apache.org/jira/browse/GERONIMO-4485 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Fix For: 2.1.4 > > Attachments: activemq-portlets.patch, console-base-portlets.patch, > console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, > mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, > plancreator-console-tomcat.patch, plancreator-portlets.patch, > plugin-portlets.patch, sysdb-portlets.patch > > > Target release should be 2.2, if you can attach the patches by Jan. 7th. > If you would like to see this in 2.1.4, then please attach additional patches > created from that branch and we'll try to get them in after we wrap up the > 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671549#action_12671549 ] Kan Ogawa commented on GERONIMO-4485: - Donald, Please review the attached patches and commit them to branches/2.1. > Port the GERONIMO-4474 patch for V2.1 > - > > Key: GERONIMO-4485 > URL: https://issues.apache.org/jira/browse/GERONIMO-4485 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Fix For: 2.1.4 > > Attachments: activemq-portlets.patch, console-base-portlets.patch, > console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, > mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, > plancreator-console-tomcat.patch, plancreator-portlets.patch, > plugin-portlets.patch, sysdb-portlets.patch > > > Target release should be 2.2, if you can attach the patches by Jan. 7th. > If you would like to see this in 2.1.4, then please attach additional patches > created from that branch and we'll try to get them in after we wrap up the > 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.0: Failed for Revision: 741983
Geronimo Revision: 741983 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/build-2000.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 33 seconds [INFO] Finished at: Sat Feb 07 20:37:59 EST 2009 [INFO] Final Memory: 216M/859M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/logs-2000-tomcat/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.296 sec <<< FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.279 sec <<< FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.614 sec <<< FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.284 sec <<< FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/logs-2000-jetty/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.326 sec <<< FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.331 sec <<< FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.672 sec <<< FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.314 sec <<< FAILURE!
Re: Build fails with javax.el.ELException: Function 'f:length' not found
Start with clean m2 repo.
Jarek
On Sat, Feb 7, 2009 at 7:23 PM, Jacek Laskowski wrote:
> Hi,
>
> It's been a while since I built Geronimo locally and when I had given
> it a try it failed.
>
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO]
> file:C:/oss/geronimo/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/editConnector.jsp(113,16)
> "${fn:length(connectorAttribute.value) > 0}
> " contains invalid expression(s): javax.el.ELException: Function
> 'f:length' not found
> [INFO]
>
> [INFO] Trace
> org.apache.jasper.JasperException:
> file:C:/oss/geronimo/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/editConnector.jsp(113,16)
> "${fn:length(co
> nnectorAttribute.value) > 0}" contains invalid expression(s):
> javax.el.ELException: Function 'f:length' not found
>at
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
>at
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
>at
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:198)
>at
> org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1151)
>at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:821)
>at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
>at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
>at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
>at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
>at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
>at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
>at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
>at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
>at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
>at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
>at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
>at
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
>at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
>at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
>at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
>at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2399)
>at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
>at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
>at org.apache.jasper.compiler.Validator.validate(Validator.java:1739)
>at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:166)
>at org.apache.jasper.compiler.Compiler.compile(Compiler.java:315)
>at org.apache.jasper.JspC.processFile(JspC.java:1010)
>at org.apache.jasper.JspC.execute(JspC.java:1159)
>at
> org.codehaus.mojo.jspc.compiler.tomcat6.JspCompilerImpl.compile(JspCompilerImpl.java:111)
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ java -version
> java version "1.5.0_17"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
> Java HotSpot(TM) Client VM (build 1.5.0_17-b04, mixed mode, sharing)
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ mvn -version
> Maven version: 2.0.9
> Java version: 1.5.0_17
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ uname -a
> CYGWIN_NT-5.1 work 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ echo $MAVEN_OPTS
> -Duser.language=en -Xmx512m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ echo $JAVA_OPTS
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ svn status
>
> jlaskow...@work /cygdrive/c/oss/geronimo
> $ svn up
> At revision 741984.
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>
Build fails with javax.el.ELException: Function 'f:length' not found
Hi,
It's been a while since I built Geronimo locally and when I had given
it a try it failed.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO]
file:C:/oss/geronimo/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/editConnector.jsp(113,16)
"${fn:length(connectorAttribute.value) > 0}
" contains invalid expression(s): javax.el.ELException: Function
'f:length' not found
[INFO]
[INFO] Trace
org.apache.jasper.JasperException:
file:C:/oss/geronimo/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/editConnector.jsp(113,16)
"${fn:length(co
nnectorAttribute.value) > 0}" contains invalid expression(s):
javax.el.ELException: Function 'f:length' not found
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:198)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1151)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:821)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:840)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2399)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1739)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:166)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:315)
at org.apache.jasper.JspC.processFile(JspC.java:1010)
at org.apache.jasper.JspC.execute(JspC.java:1159)
at
org.codehaus.mojo.jspc.compiler.tomcat6.JspCompilerImpl.compile(JspCompilerImpl.java:111)
jlaskow...@work /cygdrive/c/oss/geronimo
$ java -version
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Client VM (build 1.5.0_17-b04, mixed mode, sharing)
jlaskow...@work /cygdrive/c/oss/geronimo
$ mvn -version
Maven version: 2.0.9
Java version: 1.5.0_17
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
jlaskow...@work /cygdrive/c/oss/geronimo
$ uname -a
CYGWIN_NT-5.1 work 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin
jlaskow...@work /cygdrive/c/oss/geronimo
$ echo $MAVEN_OPTS
-Duser.language=en -Xmx512m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m
jlaskow...@work /cygdrive/c/oss/geronimo
$ echo $JAVA_OPTS
jlaskow...@work /cygdrive/c/oss/geronimo
$ svn status
jlaskow...@work /cygdrive/c/oss/geronimo
$ svn up
At revision 741984.
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
[jira] Commented: (GERONIMO-4529) Corba port 1050 is not released after stopping j2ee-corba-yoko configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671479#action_12671479 ] Ivan commented on GERONIMO-4529: In another JIRA, we wish to set a specific system property for the ORB, so in the method createNameService(String, int) of org.apache.geronimo.yoko.ORBConfigAdapter, we created the ORB object ourself and call the intialize method of TransientNameService. While in the past, we call the run method to start the TransientNameService. Unfortunately, in the method intialize(ORB orb), it does not save the paramter. Then when we call the destory method, the orb.destory() is not invoked. >From the javadoc of intialize method, it says "Initialize a transient name >service on a specific ORB.", it should save the ORB parameter passed. IMO, the >better way is that add one line "createdORB=orb;" in the intialize method. Or >we may create a subclass of TransientNameService in Geronimo, and do it by >ourself. Could anyone give a commet ? Thanks in advance ! > Corba port 1050 is not released after stopping j2ee-corba-yoko configuration > > > Key: GERONIMO-4529 > URL: https://issues.apache.org/jira/browse/GERONIMO-4529 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: CORBA >Affects Versions: 2.2 > Environment: Windows XP > JDK 1.5 > Geronimo 2.2 SNAPSHOT 20090202 >Reporter: Ivan > Fix For: 2.2 > > > After stopping the corba component in the console, port 1050 is not released. > Use command netstat or connect it with Eclipse Debug. Those two threads are > still running. > Yoko:Server:StartedThread. It seems it is still blocked on > ServerSocket.accept method. And I could not start the Corba service in the > admin console due to address already in use. > Thanks for any comment ! -- 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: 741847
Geronimo Revision: 741847 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 31 seconds
[INFO] Finished at: Sat Feb 07 03:43:15 EST 2009
[INFO] Final Memory: 428M/1018M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090207/logs-0300-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[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:43.952
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.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:12.401)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.351)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:36.043)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:18.513)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:21.552)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:24.035)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.304)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:46.285)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:47.643)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:40.032)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.852)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.744)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.331)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:52.131)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:43.891) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:30.012)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:28.441)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:46.770)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:41.692)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.694)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test
[jira] Commented: (GERONIMO-4523) Security Realm based Group-Role Mapping
[ https://issues.apache.org/jira/browse/GERONIMO-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671430#action_12671430 ] David Jencks commented on GERONIMO-4523: Something went wrong with my commt in rev 741679 and a lot of unintentional modifications got committed. This has been fixed in revs 741766, 741822 and 741858 I apologize for any problems this may have caused. > Security Realm based Group-Role Mapping > --- > > Key: GERONIMO-4523 > URL: https://issues.apache.org/jira/browse/GERONIMO-4523 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: security >Reporter: Jürgen Weber >Assignee: David Jencks > > For secured applications you currently need a Geronimo-specific deployment > plan which defines among others a mapping of realm groups onto JEE roles. > This goes against the spirit of EJB3 which replaces deployment descriptors > with annotations. > It would be desirable to be able to run a standard-conforming JEE application > under container security without the need for Geronimo-specific deployment > plans. > But this raises the need of another mean to specify Group-Role Mapping. I > suggest that this can be specified at the security-realm level. A realm > should be linked to a mapping (n:1 mapping, several realms should potentially > use the same mapping). There should be a default identity mapping, if you > have several thousands of users in LDAP. > Mappings should be definable via console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.0: Failed for Revision: 741844
Geronimo Revision: 741844 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/build-0200.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 57 seconds [INFO] Finished at: Sat Feb 07 02:38:17 EST 2009 [INFO] Final Memory: 216M/861M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/logs-0200-tomcat/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.274 sec <<< FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.289 sec <<< FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.609 sec <<< FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.288 sec <<< FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090207/logs-0200-jetty/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.32 sec <<< FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.326 sec <<< FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.667 sec <<< FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.306 sec <<< FAILURE!
