[jira] Updated: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4474:
---

Attachment: jsp-localization-fix.patch

> Pull out the text in the JSP files to resource bundle files
> ---
>
> Key: GERONIMO-4474
> URL: https://issues.apache.org/jira/browse/GERONIMO-4474
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Donald Woods
>Priority: Minor
> Fix For: 2.2
>
> Attachments: jsp-localization-activemq.patch, 
> jsp-localization-console.patch, jsp-localization-console_v2.patch, 
> jsp-localization-debugview.patch, jsp-localization-debugview_v2.patch, 
> jsp-localization-fix.patch, jsp-localization-monitoring.patch, 
> jsp-localization-monitoring_v2.patch, jsp-localization-openejb.patch, 
> jsp-localization-plancreator.patch, jsp-localization-plancreator_v2.patch, 
> jsp-localization-plugin.patch, jsp-localization-plugin_v2.patch, 
> jsp-localization-sysdb.patch
>
>
> Currently in the admin console, some text are hard coded in the JSP files.
> We need to pull them out to the resource bundle files, so that we could 
> deliver multi-language versions in the future.

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

[jira] Updated: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4474:
---

Attachment: (was: jsp-localization-fix.patch)

> Pull out the text in the JSP files to resource bundle files
> ---
>
> Key: GERONIMO-4474
> URL: https://issues.apache.org/jira/browse/GERONIMO-4474
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Donald Woods
>Priority: Minor
> Fix For: 2.2
>
> Attachments: jsp-localization-activemq.patch, 
> jsp-localization-console.patch, jsp-localization-console_v2.patch, 
> jsp-localization-debugview.patch, jsp-localization-debugview_v2.patch, 
> jsp-localization-fix.patch, jsp-localization-monitoring.patch, 
> jsp-localization-monitoring_v2.patch, jsp-localization-openejb.patch, 
> jsp-localization-plancreator.patch, jsp-localization-plancreator_v2.patch, 
> jsp-localization-plugin.patch, jsp-localization-plugin_v2.patch, 
> jsp-localization-sysdb.patch
>
>
> Currently in the admin console, some text are hard coded in the JSP files.
> We need to pull them out to the resource bundle files, so that we could 
> deliver multi-language versions in the future.

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

[jira] Commented: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files

[Gang Yin (JIRA)]

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

Gang Yin commented on GERONIMO-4474:


Hi, Donald,
please commint this patch, thanks.

> Pull out the text in the JSP files to resource bundle files
> ---
>
> Key: GERONIMO-4474
> URL: https://issues.apache.org/jira/browse/GERONIMO-4474
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Donald Woods
>Priority: Minor
> Fix For: 2.2
>
> Attachments: jsp-localization-activemq.patch, 
> jsp-localization-console.patch, jsp-localization-console_v2.patch, 
> jsp-localization-debugview.patch, jsp-localization-debugview_v2.patch, 
> jsp-localization-fix.patch, jsp-localization-monitoring.patch, 
> jsp-localization-monitoring_v2.patch, jsp-localization-openejb.patch, 
> jsp-localization-plancreator.patch, jsp-localization-plancreator_v2.patch, 
> jsp-localization-plugin.patch, jsp-localization-plugin_v2.patch, 
> jsp-localization-sysdb.patch
>
>
> Currently in the admin console, some text are hard coded in the JSP files.
> We need to pull them out to the resource bundle files, so that we could 
> deliver multi-language versions in the future.

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

[jira] Updated: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4474:
---

Attachment: jsp-localization-fix.patch

fix some minor defects

> Pull out the text in the JSP files to resource bundle files
> ---
>
> Key: GERONIMO-4474
> URL: https://issues.apache.org/jira/browse/GERONIMO-4474
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Donald Woods
>Priority: Minor
> Fix For: 2.2
>
> Attachments: jsp-localization-activemq.patch, 
> jsp-localization-console.patch, jsp-localization-console_v2.patch, 
> jsp-localization-debugview.patch, jsp-localization-debugview_v2.patch, 
> jsp-localization-fix.patch, jsp-localization-monitoring.patch, 
> jsp-localization-monitoring_v2.patch, jsp-localization-openejb.patch, 
> jsp-localization-plancreator.patch, jsp-localization-plancreator_v2.patch, 
> jsp-localization-plugin.patch, jsp-localization-plugin_v2.patch, 
> jsp-localization-sysdb.patch
>
>
> Currently in the admin console, some text are hard coded in the JSP files.
> We need to pull them out to the resource bundle files, so that we could 
> deliver multi-language versions in the future.

-- 
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: 732590

[gawor]

Geronimo Revision: 732590 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 6 seconds
[INFO] Finished at: Wed Jan 07 21:44:09 EST 2009
[INFO] Final Memory: 638M/1010M
[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/20090107/logs-2100-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[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.201
[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 35 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:00:59.742) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:27.960) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:33.044) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.900) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:24.406) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:18.887) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:41.880) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:46.600) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:46.921) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:40.099) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:28.878) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.379) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:30.484) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.140) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:41.681) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.166) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.375) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:49.050) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:36.089) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web

[jira] Commented: (GERONIMO-4486) Custom server assembly portlet doesn't filter specific word

[Lin Sun (JIRA)]

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

Lin Sun commented on GERONIMO-4486:
---

Hi Janet, what browser/OS are you using?   I assume you didn't use double 
quotes around console, right?

Thanks

Lin

> Custom server assembly portlet doesn't filter specific word
> ---
>
> Key: GERONIMO-4486
> URL: https://issues.apache.org/jira/browse/GERONIMO-4486
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - IBM SDK 1.6
> - Windows XP SP2 English
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Critical
> Fix For: 2.2
>
>
> In Custom server assebmly portlet,  the function "Filter by category and 
> name" seems stop working when I type "console", but it works well on other 
> words like "tomcat", "dojo", etc.  I test in both IE 7 and firefox 3.0.4.

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

[jira] Closed: (GERONIMO-4488) Framework assembly can not be stopped successfully

[Lin Sun (JIRA)]

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

Lin Sun closed GERONIMO-4488.
-


close the jira as it is reported as fixed.

> Framework assembly can not be stopped successfully
> --
>
> Key: GERONIMO-4488
> URL: https://issues.apache.org/jira/browse/GERONIMO-4488
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - Windows XP SP2 English + IBM SDK 1.6.0
> - Windows XP SP2 Simplified Chinese + Sun JDK 1.5.0-16
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: gshell.log, gshell_20090105.log
>
>
> Assemble a custom server with following steps:
> - start geronimo server (either jetty or tomcat version)
> - login admin console
> - start server assembly by selecting function centric
> - select only Framework group, and complete the assembly following portlet 
> instruction
> - stop geronimo server 
> - start custom server just created with start-server.bat (custom server can 
> be started successfully)
> - stop custom server with stop-server.bat or shutdown.bat, exception msg 
> occurs in command window, and the custom server is still up.
> I tried in both 20081229 and 20081230 build, and log file will be attached.

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

[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan commented on GERONIMO-4475:


I will update the portlet according to the G-4484, so remove the old patch.

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-activemq-broker.patch, 
> G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

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

[jira] Updated: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4475:
---

Attachment: (was: G4475-activemq-portlet.patch)

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-activemq-broker.patch, 
> G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

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

[jira] Updated: (GERONIMO-4502) Warning msg occurs when stopping custom server (Framework + Web Services Axis2)

[Han Hong Fang (JIRA)]

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

Han Hong Fang updated GERONIMO-4502:


Attachment: gshell.log

Log file is attached.

> Warning msg occurs when stopping custom server (Framework + Web Services 
> Axis2)
> ---
>
> Key: GERONIMO-4502
> URL: https://issues.apache.org/jira/browse/GERONIMO-4502
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - Windows XP SP2 English + IBM SDK 1.6.0
> - Geronimo build: 20090107_1500
>Reporter: Han Hong Fang
>Priority: Minor
> Attachments: gshell.log
>
>
> Reproduce steps:
> - Assemble a custom server using Function centric method, and select 
> Framework + Web Services Axis2
> - Start assembled server, and then stop it.
> Custom server can be stopped, but following warning message occurs. And seems 
> that only tomcat build has this problem, but jetty doesn't.
> 09:19:23,890 WARN  [geronimo-commands:start-server] Exception in thread 
> "Multica
> st Discovery Agent Notifier" java.lang.NoClassDefFoundError: 
> org.apache.openejb.
> server.DiscoveryRegistry$ServiceRemovedTask
> 09:19:23,890 WARN  [geronimo-commands:start-server] at 
> org.apache.openejb.se
> rver.DiscoveryRegistry.serviceRemoved(DiscoveryRegistry.java:129)
> 09:19:23,890 WARN  [geronimo-commands:start-server] at 
> org.apache.openejb.se
> rver.discovery.MulticastDiscoveryAgent$Listener$2.run(MulticastDiscoveryAgent.ja
> va:418)
> 09:19:23,890 WARN  [geronimo-commands:start-server] at 
> java.util.concurrent.
> ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:896)
> 09:19:23,890 WARN  [geronimo-commands:start-server] at 
> java.util.concurrent.
> ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 09:19:23,890 WARN  [geronimo-commands:start-server] at 
> java.lang.Thread.run(
> Thread.java:735)
> 09:19:23,890 WARN  [geronimo-commands:start-server] Caused by: 
> java.lang.ClassNo
> tFoundException: 
> org.apache.openejb.server.DiscoveryRegistry$ServiceRemovedTask
> in classloader org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car
> 09:19:23,906 WARN  [geronimo-commands:start-server] at 
> java.lang.Throwable.<
> init>(Throwable.java:80)
> 09:19:23,906 WARN  [geronimo-commands:start-server] at 
> java.lang.ClassNotFou
> ndException.(ClassNotFoundException.java:76)
> 09:19:23,906 WARN  [geronimo-commands:start-server] at 
> org.apache.geronimo.k
> ernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.ja
> va:413)
> 09:19:23,906 WARN  [geronimo-commands:start-server] at 
> org.apache.geronimo.k
> ernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:255)
> 09:19:23,906 WARN  [geronimo-commands:start-server] at 
> java.lang.ClassLoader
> .loadClass(ClassLoader.java:609)
> 09:19:23,906 WARN  [geronimo-commands:start-server] ... 5 more
> Shutting down...

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

[jira] Created: (GERONIMO-4502) Warning msg occurs when stopping custom server (Framework + Web Services Axis2)

[Han Hong Fang (JIRA)]

Warning msg occurs when stopping custom server (Framework + Web Services Axis2)
---

 Key: GERONIMO-4502
 URL: https://issues.apache.org/jira/browse/GERONIMO-4502
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: general
Affects Versions: 2.2
 Environment: - Windows XP SP2 English + IBM SDK 1.6.0
- Geronimo build: 20090107_1500
Reporter: Han Hong Fang
Priority: Minor


Reproduce steps:
- Assemble a custom server using Function centric method, and select Framework 
+ Web Services Axis2
- Start assembled server, and then stop it.

Custom server can be stopped, but following warning message occurs. And seems 
that only tomcat build has this problem, but jetty doesn't.

09:19:23,890 WARN  [geronimo-commands:start-server] Exception in thread "Multica
st Discovery Agent Notifier" java.lang.NoClassDefFoundError: org.apache.openejb.
server.DiscoveryRegistry$ServiceRemovedTask
09:19:23,890 WARN  [geronimo-commands:start-server] at org.apache.openejb.se
rver.DiscoveryRegistry.serviceRemoved(DiscoveryRegistry.java:129)
09:19:23,890 WARN  [geronimo-commands:start-server] at org.apache.openejb.se
rver.discovery.MulticastDiscoveryAgent$Listener$2.run(MulticastDiscoveryAgent.ja
va:418)
09:19:23,890 WARN  [geronimo-commands:start-server] at java.util.concurrent.
ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:896)
09:19:23,890 WARN  [geronimo-commands:start-server] at java.util.concurrent.
ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
09:19:23,890 WARN  [geronimo-commands:start-server] at java.lang.Thread.run(
Thread.java:735)
09:19:23,890 WARN  [geronimo-commands:start-server] Caused by: java.lang.ClassNo
tFoundException: org.apache.openejb.server.DiscoveryRegistry$ServiceRemovedTask
in classloader org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car
09:19:23,906 WARN  [geronimo-commands:start-server] at java.lang.Throwable.<
init>(Throwable.java:80)
09:19:23,906 WARN  [geronimo-commands:start-server] at java.lang.ClassNotFou
ndException.(ClassNotFoundException.java:76)
09:19:23,906 WARN  [geronimo-commands:start-server] at org.apache.geronimo.k
ernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.ja
va:413)
09:19:23,906 WARN  [geronimo-commands:start-server] at org.apache.geronimo.k
ernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:255)
09:19:23,906 WARN  [geronimo-commands:start-server] at java.lang.ClassLoader
.loadClass(ClassLoader.java:609)
09:19:23,906 WARN  [geronimo-commands:start-server] ... 5 more
Shutting down...

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

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin commented on GERONIMO-4484:


Hi Donald,
Thanks a lot for applying all these patches. The needed images are 
submitted. There are 5 all together. And they should be located under 
plugins\console\console-portal-driver\src\main\webapp\images.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Updated: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4484:
---

Attachment: arrow_collapsed.gif

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Updated: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4484:
---

Attachment: arrow_expanded.gif

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Updated: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4484:
---

Attachment: msg_error.gif

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Updated: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4484:
---

Attachment: msg_info.gif

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Updated: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin updated GERONIMO-4484:
---

Attachment: msg_warn.gif

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
> common-message-activemq.patch, common-message-base.patch, 
> common-message-core.patch, common-message-debugviews.patch, 
> common-message-monotor.patch, common-message-openejb.patch, 
> common-message-plancreator.patch, common-message-plugin.patch, 
> common-message-sysdb.patch, err_abbr.jpg, err_detail.jpg, info.jpg, 
> msg_error.gif, msg_info.gif, msg_warn.gif
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4488) Framework assembly can not be stopped successfully

[Han Hong Fang (JIRA)]

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

Han Hong Fang commented on GERONIMO-4488:
-

Verified again in build 20090107_1500 (both tomcat and jetty). The problem is 
fixed. Thanks!

> Framework assembly can not be stopped successfully
> --
>
> Key: GERONIMO-4488
> URL: https://issues.apache.org/jira/browse/GERONIMO-4488
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - Windows XP SP2 English + IBM SDK 1.6.0
> - Windows XP SP2 Simplified Chinese + Sun JDK 1.5.0-16
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: gshell.log, gshell_20090105.log
>
>
> Assemble a custom server with following steps:
> - start geronimo server (either jetty or tomcat version)
> - login admin console
> - start server assembly by selecting function centric
> - select only Framework group, and complete the assembly following portlet 
> instruction
> - stop geronimo server 
> - start custom server just created with start-server.bat (custom server can 
> be started successfully)
> - stop custom server with stop-server.bat or shutdown.bat, exception msg 
> occurs in command window, and the custom server is still up.
> I tried in both 20081229 and 20081230 build, and log file will be attached.

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

[jira] Commented: (GERONIMO-4486) Custom server assembly portlet doesn't filter specific word

[Han Hong Fang (JIRA)]

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

Han Hong Fang commented on GERONIMO-4486:
-

Verified again in build 20090107_1500, filter works well on other words but 
failed on "console".

Janet

> Custom server assembly portlet doesn't filter specific word
> ---
>
> Key: GERONIMO-4486
> URL: https://issues.apache.org/jira/browse/GERONIMO-4486
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - IBM SDK 1.6
> - Windows XP SP2 English
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Critical
> Fix For: 2.2
>
>
> In Custom server assebmly portlet,  the function "Filter by category and 
> name" seems stop working when I type "console", but it works well on other 
> words like "tomcat", "dojo", etc.  I test in both IE 7 and firefox 3.0.4.

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

[jira] Commented: (GERONIMODEVTOOLS-532) Surface the publish timeout time in the server properties tab like all the other publishing attributes (e.g., publishing interval)

[Delos Dai (JIRA)]

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

Delos Dai commented on GERONIMODEVTOOLS-532:


OK. Thanks a lot! 

> Surface the publish timeout time in the server properties tab like all the 
> other publishing attributes (e.g., publishing interval)
> --
>
> Key: GERONIMODEVTOOLS-532
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-532
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 532.patch
>
>


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

[jira] Commented: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[David Jencks (JIRA)]

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

David Jencks commented on GERONIMO-4499:


I knew about the property-placeholder and (so far) rejected it because AFAICT 
it requires reading the properties from a file rather than letting geronimo 
inject a properties object into the spring application context.  I don't know 
anything about the context schema.  Maybe we could write an injectable 
properties placeholder spring bean??

> can't use PortOffset in var\config\config-substitutions.properties to start 
> two geronimo instance at the same machine.
> --
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to 
> start two geronimo instance at the same machine.
> 1, install two geronimo server  serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0 
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*:  Both serverA and serverB could be started without 
> problems.
> *actual result*: serverA started, but server B failed to start with a 
> exception below in log:
> -
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
> Message Broker. Reason: java.io.IOException: Transport Connector could not be 
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX: 
> Failed to bind to server socket: tcp://localhost:61616 due to: 
> java.net.BindException: Address already in use: JVM_Bind
>   at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>   at 
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
>   at 
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
>   at 
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Closed: (GERONIMODEVTOOLS-518) Update GEP code with new Devtools URL

[Ted Kirby (JIRA)]

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

Ted Kirby closed GERONIMODEVTOOLS-518.
--

Resolution: Fixed

> Update GEP code with new Devtools URL
> -
>
> Key: GERONIMODEVTOOLS-518
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-518
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 2.1.3, 2.2.0
>Reporter: Ted Kirby
>Assignee: Ted Kirby
> Fix For: 2.2.0
>
>
> Recently, the devtools sub-project homepage was changed from 
> http://geronimo.apache.org/development-tools.html to 
> http://cwiki.apache.org/GMOxDOC21/apache-geronimo-development-tools-project.html.
> I have just found some references in the code to the old page that need to be 
> updated.

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

[jira] Closed: (GERONIMODEVTOOLS-344) Cannot utilize the xpp3-1.1.3.4.O jar in GEP

[Tim McConnell (JIRA)]

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

Tim McConnell closed GERONIMODEVTOOLS-344.
--

Resolution: Fixed

Closing since XStream causes other problems with Java 1.6, so would rather have 
a working custom solution that supports both Java 1.5 and 1.6

> Cannot utilize the xpp3-1.1.3.4.O jar in GEP 
> -
>
> Key: GERONIMODEVTOOLS-344
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.0
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.2.0
>
> Attachments: GERONIMODEVTOOLS-344.patch
>
>
> During the release of the GEP 2.1.0 we encountered problems with the 
> xpp3-1.1.3.4.O.jar file when trying to create a new dynamic web problem 
> (i.e., unhandled event condition). Need to investigate and understand why so 
> that we can use the same version of this artifact that the server is using. 

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

[jira] Closed: (GERONIMODEVTOOLS-232) Allow short directory names for installed geronimo servers

[Tim McConnell (JIRA)]

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

Tim McConnell closed GERONIMODEVTOOLS-232.
--

Resolution: Invalid

"Download and Install" no longer supported from the GEP, so testcase is now 
invalid

> Allow short directory names for installed geronimo servers
> --
>
> Key: GERONIMODEVTOOLS-232
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-232
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>Affects Versions: 2.0.0, 2.0.2, 2.0.x, 2.1.0, 2.1.3
>Reporter: Ted Kirby
>Assignee: Tim McConnell
>
> Recent user and dev list issues reminded me that on windows, GERONIMO_HOME, 
> the server installation directory, should have as small a name as possible, 
> like C:\g, to avoid issues on windows with too long path names.
> I think we should allow the eclipse plugin user to install a server in such a 
> named directory.  Currently, on the "Download and Install" screen, the user 
> specifies a directory, but the server is actually installed in a 
> geronimo-tomcat6-jee5-2.0.1 or geronimo-jetty6-jee5-2.0.1subdirectory of that 
> server.  I think we should look at using the directory specified as the 
> installation directory directly, and eliminate this subdirectory.  This may 
> well be related to the server packaging itself.  It seems the server zip file 
> is packaged starting with the geronimo-{jetty,tomcat}6-jee5-2.0.1 parent 
> directory itself.
> The manual workaround would be to extract the geronimo.zip file to your root, 
> rename the directory to g, and point to that directory when defining the 
> installable runtime.  It would be nice to have this done automatically with 
> one click, or not require the "extra" steps.

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

[jira] Closed: (GERONIMO-4495) Invoking stop method on a gbean whose instancestate is destoryed caused that gbean in the stopping state

[Donald Woods (JIRA)]

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

Donald Woods closed GERONIMO-4495.
--

Resolution: Fixed

Applied patch to trunk (2.2-SNAPSHOT) as Rev732537 and to branches/2.1 
(2.1.4-SNAPSHOT) as Rev732538.

> Invoking stop method on a gbean whose instancestate is destoryed caused that 
> gbean in the stopping state
> 
>
> Key: GERONIMO-4495
> URL: https://issues.apache.org/jira/browse/GERONIMO-4495
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.3, 2.2
>Reporter: Ivan
>Assignee: Donald Woods
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4495.patch
>
>
> If one gbean's instancestate is in the destoryed state and its gbeanstate is 
> in the failed state. Then we invoke the stop method on that gbean, then the 
> gbean will in the stopping state.
> So, we never could start it by calling the startRecursive() method.
> Shall the stop method returns directly when the gbean state is in failed 
> state ?
> Thanks for giving a 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: 732462

[gawor]

Geronimo Revision: 732462 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 40 minutes 18 seconds
[INFO] Finished at: Wed Jan 07 15:44:37 EST 2009
[INFO] Final Memory: 392M/1012M
[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/20090107/logs-1500-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[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:46.507
[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 35 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:13.729) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:30.085) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:36.368) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.310) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:12.691) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.141) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:45.845) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:45.858) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:53.839) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:45.136) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:30.144) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.733) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:29.415) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.870) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:40.225) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:47.980) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.192) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:51.449) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite

[jira] Closed: (GERONIMODEVTOOLS-514) Utility project testsuite

[Tim McConnell (JIRA)]

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

Tim McConnell closed GERONIMODEVTOOLS-514.
--

Resolution: Invalid

Utility projects are no longer supported by GEP

> Utility project testsuite
> -
>
> Key: GERONIMODEVTOOLS-514
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-514
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>Reporter: Tim McConnell
>Assignee: Tim McConnell
>


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

[jira] Closed: (GERONIMODEVTOOLS-433) Tasklist for Ganymede-specific problems

[Tim McConnell (JIRA)]

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

Tim McConnell closed GERONIMODEVTOOLS-433.
--

Resolution: Fixed

All tasks now closed, so closing the tasklist

> Tasklist for Ganymede-specific problems 
> 
>
> Key: GERONIMODEVTOOLS-433
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-433
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.2.0
>
>


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

[jira] Updated: (GERONIMODEVTOOLS-419) NullPointerException when defining new Geronimo server using the 2.2-SNAPSHOT version of geronimo-deploy-jsr88.jar

[Tim McConnell (JIRA)]

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

Tim McConnell updated GERONIMODEVTOOLS-419:
---

Fix Version/s: (was: 1.2.1)
   2.1.3

> NullPointerException when defining new Geronimo server using the 2.2-SNAPSHOT 
> version of  geronimo-deploy-jsr88.jar
> ---
>
> Key: GERONIMODEVTOOLS-419
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-419
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.3
>
>
> Configuration location:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/
> Configuration file:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/config.ini
>  loaded
> Install location:
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/
> Framework located:
> 
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/plugins/org.eclipse.osgi_3.4.0.v20080605-1900.jar
> Framework classpath:
> 
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/plugins/org.eclipse.osgi_3.4.0.v20080605-1900.jar
> Splash location:
> 
> C:\ECLIPSE\GEP_TRUNK_IMPORTED\plugins\org.eclipse.platform_3.3.100.v200806172000\splash.bmp
> Debug options:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/.options
>  loaded
> Time to load bundles: 31
> Starting application: 3375
> Application Started: 7860
> org.eclipse.wst.server.core FINEST07/07/08 17:23.47.437 Loading temporary 
> directory information
> java.io.FileNotFoundException: 
> C:\ECLIPSE\_WORKSPACES\runtime-New_configuration\.metadata\.plugins\org.eclipse.wst.server.core\tmp-data.xml
>  (The system cannot find the file specified)
> org.eclipse.wst.server.core WARNING   07/07/08 17:23.47.437 Could not load 
> temporary directory information
>   at java.io.FileInputStream.open(Native Method)
>   at java.io.FileInputStream.(Unknown Source)
>   at java.io.FileInputStream.(Unknown Source)
>   at 
> org.eclipse.wst.server.core.internal.XMLMemento.loadMemento(XMLMemento.java:254)
>   at 
> org.eclipse.wst.server.core.internal.ServerPlugin.loadTempDirInfo(ServerPlugin.java:205)
>   at 
> org.eclipse.wst.server.core.internal.ServerPlugin.start(ServerPlugin.java:275)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
>   at 
> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
>   at 
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
>   at 
> org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>   at java.lang.Class.getDeclaredConstructors0(Native Method)
>   at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>   at java.lang.Class.getConstructor0(Unknown Source)
>   at java.lang.Class.newInstance0(Unknown Source)
>   at java.lang.Class.newInstance(Unknown Source)
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
>   at 
> org.eclipse.osgi.framework.internal.core.Bun

[jira] Closed: (GERONIMODEVTOOLS-419) NullPointerException when defining new Geronimo server using the 2.2-SNAPSHOT version of geronimo-deploy-jsr88.jar

[Tim McConnell (JIRA)]

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

Tim McConnell closed GERONIMODEVTOOLS-419.
--

   Resolution: Invalid
Fix Version/s: (was: 2.2.0)
   1.2.1

> NullPointerException when defining new Geronimo server using the 2.2-SNAPSHOT 
> version of  geronimo-deploy-jsr88.jar
> ---
>
> Key: GERONIMODEVTOOLS-419
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-419
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 1.2.1
>
>
> Configuration location:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/
> Configuration file:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/config.ini
>  loaded
> Install location:
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/
> Framework located:
> 
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/plugins/org.eclipse.osgi_3.4.0.v20080605-1900.jar
> Framework classpath:
> 
> file:/C:/ECLIPSE/GEP_TRUNK_IMPORTED/plugins/org.eclipse.osgi_3.4.0.v20080605-1900.jar
> Splash location:
> 
> C:\ECLIPSE\GEP_TRUNK_IMPORTED\plugins\org.eclipse.platform_3.3.100.v200806172000\splash.bmp
> Debug options:
> 
> file:/C:/ECLIPSE/_WORKSPACES/GEP_TRUNK_IMPORTED/.metadata/.plugins/org.eclipse.pde.core/New_configuration/.options
>  loaded
> Time to load bundles: 31
> Starting application: 3375
> Application Started: 7860
> org.eclipse.wst.server.core FINEST07/07/08 17:23.47.437 Loading temporary 
> directory information
> java.io.FileNotFoundException: 
> C:\ECLIPSE\_WORKSPACES\runtime-New_configuration\.metadata\.plugins\org.eclipse.wst.server.core\tmp-data.xml
>  (The system cannot find the file specified)
> org.eclipse.wst.server.core WARNING   07/07/08 17:23.47.437 Could not load 
> temporary directory information
>   at java.io.FileInputStream.open(Native Method)
>   at java.io.FileInputStream.(Unknown Source)
>   at java.io.FileInputStream.(Unknown Source)
>   at 
> org.eclipse.wst.server.core.internal.XMLMemento.loadMemento(XMLMemento.java:254)
>   at 
> org.eclipse.wst.server.core.internal.ServerPlugin.loadTempDirInfo(ServerPlugin.java:205)
>   at 
> org.eclipse.wst.server.core.internal.ServerPlugin.start(ServerPlugin.java:275)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
>   at 
> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
>   at 
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
>   at 
> org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>   at java.lang.Class.getDeclaredConstructors0(Native Method)
>   at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>   at java.lang.Class.getConstructor0(Unknown Source)
>   at java.lang.Class.newInstance0(Unknown Source)
>   at java.lang.Class.newInstance(Unknown Source)
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
>   at 
> org.eclipse.osgi.fr

Re: svn commit: r732486 - /geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java

[Tim McConnell]

Hi Jarek, I originally had named it "notFoundResources" and probably should have 
left it at that. I'll change it to something less confusing. Thanks for reviewing


Jarek Gawor wrote:

Can we maybe change the variable name to something else, e.g.
unknownResources? Calling it "knownResources" for resources that are
not found is a little confusing.

Jarek

On Wed, Jan 7, 2009 at 3:56 PM,   wrote:

Author: mcconne
Date: Wed Jan  7 12:56:39 2009
New Revision: 732486

URL: http://svn.apache.org/viewvc?rev=732486&view=rev
Log:
GERONIMO-4497 Change to prevent repetitive searches for the same (not found) 
resource

Modified:
   
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java

Modified: 
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java?rev=732486&r1=732485&r2=732486&view=diff
==
--- 
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
 (original)
+++ 
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
 Wed Jan  7 12:56:39 2009
@@ -60,6 +60,7 @@
private final ClassLoader[] parents;
private final ClassLoadingRules classLoadingRules;
private boolean destroyed = false;
+private Set knownResources = new HashSet();

// I used this pattern as its temporary and with the static final we get 
compile time
// optimizations.
@@ -514,7 +515,7 @@
}

public URL getResource(String name) {
-if (isDestroyed()) {
+if (isDestroyed() || knownResources.contains(name)) {
return null;
}

@@ -548,7 +549,17 @@
// resource, so we can override now
if (!isDestroyed()) {
// parents didn't have the resource; attempt to load it from my urls
-return findResource(name);
+URL url = findResource(name);
+if (url != null) {
+return url;
+}
+}
+
+//
+// Resource not found -- no need to search for it again
+//
+if (!knownResources.contains(name)) {
+knownResources.add(name);
}

return null;

[jira] Commented: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4499:


Found the following in the Spring Reference PDF.  Maybe we can inject our 
config-substitutions.properties into the AMQ config and then use the 
${portOffset} in the XML?

A.2.8. The context schema 
The context tags deal with ApplicationContext configuration that relates to 
plumbing - that is, not usually 
beans that are important to an end-user but rather beans that do a lot of grunt 
work in Spring, such as 
BeanfactoryPostProcessors. The following snippet references the correct schema 
so that the tags in the 
context namespace are available to you. 
 
http://www.springframework.org/schema/beans"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:context="http://www.springframework.org/schema/context"; 
xsi:schemaLocation=" 
http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd 
http://www.springframework.org/schema/context 
http://www.springframework.org/schema/context/spring-context-2.5.x 
 
 
Note 
The context schema was only introduced in Spring 2.5. 

A.2.8.1.  
This element activates the replacement of ${...} placeholders, resolved against 
the specified properties file (as 
a Spring resource location). This element is a convenience mechanism that sets 
up a 
PropertyPlaceholderConfigurer for you; if you need more control over the 
PropertyPlaceholderConfigurer, just define one yourself explicitly. 



> can't use PortOffset in var\config\config-substitutions.properties to start 
> two geronimo instance at the same machine.
> --
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to 
> start two geronimo instance at the same machine.
> 1, install two geronimo server  serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0 
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*:  Both serverA and serverB could be started without 
> problems.
> *actual result*: serverA started, but server B failed to start with a 
> exception below in log:
> -
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
> Message Broker. Reason: java.io.IOException: Transport Connector could not be 
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX: 
> Failed to bind to server socket: tcp://localhost:61616 due to: 
> java.net.BindException: Address already in use: JVM_Bind
>   at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>   at 
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
>   at 
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
>   at 
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Commented: (GERONIMO-4497) Searching for resources in MultiParentClassLoader is not fully optimized

[Tim McConnell (JIRA)]

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

Tim McConnell commented on GERONIMO-4497:
-

Hi Jeff, this change to MultiParentClassLoader improves the performance of 
Geronimo 2.1.4 for the BIRT reporting engine scenario to be almost identical to 
the performance in Geronimo 1.1.1 (where the xercesImpl.jar and 
xmlParserAPIs.jar files were located in the endorsed lib directory, and thus 
were immediately found). Could you download the latest Geronimo 2.1.4 snapshot 
and rerun your test without utilizing the endorsed lib directory ?? 

> Searching for resources in MultiParentClassLoader is not fully optimized
> 
>
> Key: GERONIMO-4497
> URL: https://issues.apache.org/jira/browse/GERONIMO-4497
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.4, 2.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.4, 2.2
>
>
> In one failing scenario, the BIRT reporting engine is invoked with an XML 
> data file to generate a PDF report file. MultiParentClassLoader.getResource() 
> is invoked many times to search for various XML resources (e.g., 
> DocumentBuilderFactory). MultiParentClassLoader searches through the current 
> classloader and all the parent classloaders, which it should, but this can 
> take a considerable amount of time if the resource is never found. It seems 
> that once a resource has been searched for and not found, there is no need to 
> search for it again in the same classloader hierarchy. 

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

Re: svn commit: r732486 - /geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java

[Jarek Gawor]

Can we maybe change the variable name to something else, e.g.
unknownResources? Calling it "knownResources" for resources that are
not found is a little confusing.

Jarek

On Wed, Jan 7, 2009 at 3:56 PM,   wrote:
> Author: mcconne
> Date: Wed Jan  7 12:56:39 2009
> New Revision: 732486
>
> URL: http://svn.apache.org/viewvc?rev=732486&view=rev
> Log:
> GERONIMO-4497 Change to prevent repetitive searches for the same (not found) 
> resource
>
> Modified:
>
> geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
>
> Modified: 
> geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
> URL: 
> http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java?rev=732486&r1=732485&r2=732486&view=diff
> ==
> --- 
> geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
>  (original)
> +++ 
> geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/MultiParentClassLoader.java
>  Wed Jan  7 12:56:39 2009
> @@ -60,6 +60,7 @@
> private final ClassLoader[] parents;
> private final ClassLoadingRules classLoadingRules;
> private boolean destroyed = false;
> +private Set knownResources = new HashSet();
>
> // I used this pattern as its temporary and with the static final we get 
> compile time
> // optimizations.
> @@ -514,7 +515,7 @@
> }
>
> public URL getResource(String name) {
> -if (isDestroyed()) {
> +if (isDestroyed() || knownResources.contains(name)) {
> return null;
> }
>
> @@ -548,7 +549,17 @@
> // resource, so we can override now
> if (!isDestroyed()) {
> // parents didn't have the resource; attempt to load it from my 
> urls
> -return findResource(name);
> +URL url = findResource(name);
> +if (url != null) {
> +return url;
> +}
> +}
> +
> +//
> +// Resource not found -- no need to search for it again
> +//
> +if (!knownResources.contains(name)) {
> +knownResources.add(name);
> }
>
> return null;
>
>
>

[jira] Resolved: (GERONIMO-4497) Searching for resources in MultiParentClassLoader is not fully optimized

[Tim McConnell (JIRA)]

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

Tim McConnell resolved GERONIMO-4497.
-

Resolution: Fixed

Changed MultiParentClassLoader to use a HashSet to maintain of list of those 
resources which have already been searched for, but not found, and thus 
preventing multiple searches for the same "not found" resources. This 
dramatically improves the performance when "not found" resources are searched 
for multiple times (e.g., by the BIRT reporting engine) especially when many 
parent classloaders are involved, and would otherwise have to be searched 
again. 

> Searching for resources in MultiParentClassLoader is not fully optimized
> 
>
> Key: GERONIMO-4497
> URL: https://issues.apache.org/jira/browse/GERONIMO-4497
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.4, 2.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.4, 2.2
>
>
> In one failing scenario, the BIRT reporting engine is invoked with an XML 
> data file to generate a PDF report file. MultiParentClassLoader.getResource() 
> is invoked many times to search for various XML resources (e.g., 
> DocumentBuilderFactory). MultiParentClassLoader searches through the current 
> classloader and all the parent classloaders, which it should, but this can 
> take a considerable amount of time if the resource is never found. It seems 
> that once a resource has been searched for and not found, there is no need to 
> search for it again in the same classloader hierarchy. 

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

[jira] Updated: (GERONIMO-4495) Invoking stop method on a gbean whose instancestate is destoryed caused that gbean in the stopping state

[Donald Woods (JIRA)]

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

Donald Woods updated GERONIMO-4495:
---

   Patch Info: [Patch Available]
Affects Version/s: 2.1.3
Fix Version/s: 2.2
   2.1.4
 Assignee: Donald Woods

> Invoking stop method on a gbean whose instancestate is destoryed caused that 
> gbean in the stopping state
> 
>
> Key: GERONIMO-4495
> URL: https://issues.apache.org/jira/browse/GERONIMO-4495
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.3, 2.2
>Reporter: Ivan
>Assignee: Donald Woods
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4495.patch
>
>
> If one gbean's instancestate is in the destoryed state and its gbeanstate is 
> in the failed state. Then we invoke the stop method on that gbean, then the 
> gbean will in the stopping state.
> So, we never could start it by calling the startRecursive() method.
> Shall the stop method returns directly when the gbean state is in failed 
> state ?
> Thanks for giving a comment !

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

[jira] Assigned: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods reassigned GERONIMO-4484:
--

Assignee: Gang Yin  (was: Donald Woods)

While testing, I noticed that there are some image files missing for displayed 
messages, like:
/console/images/msg_error.gif
/console/images/msg_info.gif

Can you attach the binaries to this JIRA, so we can close out this JIRA?
Thanks.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Gang Yin
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4484:


Applied common-message-openejb.patch, common-message-activemq.patch, 
common-message-debugviews.patch, common-message-plancreator.patch and 
common-message-sysdb.patch from Gang Yin to trunk (2.2-SNAPSHOT) as Rev732459.
Also updated 2 console-testsuite DB tests to match modified message strings.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4303) Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no classloader option

[B.J. Reed (JIRA)]

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

B.J. Reed commented on GERONIMO-4303:
-

I've reviewed the 3rd link and it looks pretty good to me.  My only suggestion 
is that maybe have all the above pages reference another page that explains 
plugin groups (and maybe even what plugins are currently in each group, but 
that may be a bit much to maintain as things change).

> Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no 
> classloader option
> 
>
> Key: GERONIMO-4303
> URL: https://issues.apache.org/jira/browse/GERONIMO-4303
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.2
>Reporter: Donald Woods
>Assignee: Lin Sun
> Fix For: 2.2
>
>
> Need to make sure this new pluginGroup attribute and no plan behavior gets 
> added to the 2.2 Docs.  We should also document what pluginprofiles we will 
> be providing in 2.2 (along with adding some info to the GMOxDEV wiki, as we 
> want these to be portable between releases) and what each one provides.

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

[jira] Commented: (GERONIMODEVTOOLS-547) code cleanup on Server Plugin Manager

[B.J. Reed (JIRA)]

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

B.J. Reed commented on GERONIMODEVTOOLS-547:


Sorry Delos, but I'm still not getting a pluginInstaller from the following 
line:
  pluginInstaller = 
kernel.getGBean(PluginInstallerGBean.class);
If I change the serverChanged method to catch a Throwable instead of an 
Exception, I still get the above error.

The PluginManager does come up (Custom Server Assembly does not), but after 
going through a few pages of it, I get a null pointer caused by pluginInstaller 
being null.  Did you have to update the manifest.mf or plugin.xml to get it to 
work?

> code cleanup on Server Plugin Manager
> -
>
> Key: GERONIMODEVTOOLS-547
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-547
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: B.J. Reed
>Assignee: B.J. Reed
>Priority: Minor
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 547.patch, 547_updated.patch
>
>
> From the initial version of the Server Plugin Manager, there are several 
> things that can be streamlined.
> 1. use geronimo-system.jar file instead of the jaxbmodels 
> (org.apache.geronimo.jee.plugin).  When I tried to use the .jar file, I kept 
> get exceptions that ObjectFactory could not be found.  As it is now, the 
> org.apache.geronimo.jee.plugin classes are exact duplicates of what is in the 
> geronimo-system.jar file
> 2. GeronimoServerPluginManager.java should use PluginInstallerGbean.  This 
> will cut down on a lot of methods that were duplicated into this class.
> 3. Other methods in GeronimoServerPluginManager.java can probably make other 
> calls to the jar files that we already are bringing into the GEP.
> All of this will make the code much slimmer and re-use a lot of good code.

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

[jira] Commented: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[David Jencks (JIRA)]

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

David Jencks commented on GERONIMO-4499:


we should probably be using the vm transport for the connectors.

It would be great if we could put in some substitutions into the spring config 
file.  I looked around a bit and didn't see any way to supply spring with 
substitutions in code.  I'd like it to work by giving spring the substitutions 
before it looks at the config file.  Do you see a way to do this?  The only way 
to use substitutions I saw was to include a component in the config file that 
e.g. looked up a properties file itself.

> can't use PortOffset in var\config\config-substitutions.properties to start 
> two geronimo instance at the same machine.
> --
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to 
> start two geronimo instance at the same machine.
> 1, install two geronimo server  serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0 
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*:  Both serverA and serverB could be started without 
> problems.
> *actual result*: serverA started, but server B failed to start with a 
> exception below in log:
> -
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
> Message Broker. Reason: java.io.IOException: Transport Connector could not be 
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX: 
> Failed to bind to server socket: tcp://localhost:61616 due to: 
> java.net.BindException: Address already in use: JVM_Bind
>   at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>   at 
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
>   at 
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
>   at 
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4484:


Applied common-message-monotor.patch from Gang Yin to trunk (2.2-SNAPSHOT) as 
Rev732432.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4484:


Applied common-message-plugin.patch to trunk (2.2-SNAPSHOT) as Rev732412 and 
fixed an incorrect depend (pointed out by Jarek) introduced in the prior commit.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

Re: svn commit: r732398 [1/3] - in /geronimo/server/trunk/plugins/console: console-base-portlets/src/main/java/org/apache/geronimo/console/ca/ console-base-portlets/src/main/java/org/apache/geronimo/c

[Donald Woods]

Thanks for catching it.  I fixed it in Rev732412.


-Donald

Jarek Gawor wrote:

These should not be necessary are we have our own

Jarek

--- 
geronimo/server/trunk/plugins/console/console-jetty/src/main/history/dependencies.xml
(original)
+++ 
geronimo/server/trunk/plugins/console/console-jetty/src/main/history/dependencies.xml
Wed Jan  7 09:03:41 2009
@@ -46,4 +46,19 @@
console-core
jar

+
+org.apache.tomcat
+jsp-api
+jar
+
+
+org.apache.tomcat
+el-api
+jar
+
+
+org.apache.tomcat
+servlet-api
+jar
+

Re: svn commit: r732398 [1/3] - in /geronimo/server/trunk/plugins/console: console-base-portlets/src/main/java/org/apache/geronimo/console/ca/ console-base-portlets/src/main/java/org/apache/geronimo/c

[Jarek Gawor]

These should not be necessary are we have our own

Jarek

--- 
geronimo/server/trunk/plugins/console/console-jetty/src/main/history/dependencies.xml
(original)
+++ 
geronimo/server/trunk/plugins/console/console-jetty/src/main/history/dependencies.xml
Wed Jan  7 09:03:41 2009
@@ -46,4 +46,19 @@
console-core
jar

+
+org.apache.tomcat
+jsp-api
+jar
+
+
+org.apache.tomcat
+el-api
+jar
+
+
+org.apache.tomcat
+servlet-api
+jar
+

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4484:


Had to fix the location of the call to CommonMsg in 
console-base-portlets/src/main/webapp/WEB-INF/view/configmanager/normal.jsp and 
then the testsuite passed again.
Also had to update the dependencies.xml files for tomcat/jetty cars, due to the 
added depend on jsp-api in console-core/pom.xml.
Applied common-message-base.patch and common-message-core.patch to trunk 
(2.2-SNAPSHOT) as Rev732398.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4500) Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration

[Daniel Kulp (JIRA)]

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

Daniel Kulp commented on GERONIMO-4500:
---


This seems to be a bug at the oasis web site.  

http://www.oasis-open.org/committees/entity/release/

only shows the files for the 1.0 release.   The 1.1 release files are not 
there.If you switch to the 1.0 DTD, it probably will work.

> Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration
> ---
>
> Key: GERONIMO-4500
> URL: https://issues.apache.org/jira/browse/GERONIMO-4500
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
> Environment: Geronimo 2.2-SNAPSHOT, Jetty/CXF assembly
>Reporter: Janko Heilgeist
> Attachments: geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar, 
> geronimo-wsdllocation-jetty_cxf.tar.gz
>
>
> I've built an EJB-JAR packaging a web service. The JAR contains all classes, 
> SEI and service stub generated from an existing WSDL (which is also inside 
> this JAR). Additionally, it contains the actual EJB implementing the web 
> service.
> I tried to annotate the web service implementation with
> {code:java}
> @WebService( ..., wsdlLocation="http://example.com/myservice.wsdl";)
> {code}
> and add a META-INF/jax-ws-catalog.xml:
> {code:xml}
> 
>  "http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd";>
> 
>  systemId="http://example.com/myservice.wsdl";
>   uri="wsdl/myservice.wsdl"/>
> 
> {code}
> During deployment, the following exception is thrown:
> {noformat}
> 2009-01-07 17:33:53,087 WARN  [OASISCatalogManager] Error loading 
> META-INF/jax-ws-catalog.xml catalog files
> java.io.FileNotFoundException: 
> http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd
> at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:905)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:872)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:282)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at 
> org.apache.xml.resolver.readers.SAXCatalogReader.readCatalog(SAXCatalogReader.java:251)
> at org.apache.xml.resolver.Catalog.parseCatalog(Catalog.java:681)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadCatalogs(OASISCatalogManager.java:108)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:93)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:89)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.register(OASISCatalogManager.java:81)
> ...
> {noformat}
> As a workaround the DOCTYPE declaration can be removed. Without the 
> declaration the exception is gone and the wsdlLocation URL is correctly 
> resolved.

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

[jira] Created: (GERONIMO-4501) Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs

[Janko Heilgeist (JIRA)]

Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs


 Key: GERONIMO-4501
 URL: https://issues.apache.org/jira/browse/GERONIMO-4501
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2
 Environment: Geronimo 2.2-SNAPSHOT, Tomcat/Axis
Reporter: Janko Heilgeist


The problem description's context is identical to GERONIMO-4500 for the 
Jetty/CXF assembly. This time the catalog is completely ignored while resolving 
the wsdlLocation URL. The exception is:

{noformat}
2009-01-07 17:45:17,701 ERROR [GBeanInstanceState] Error while starting; GBean 
is now in the FAILED state: 
abstractName="default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car?EJBModule=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car,J2EEApplication=null,StatelessSessionBean=HelloWorldServiceEJB,j2eeType=WSLink,name=HelloWorldServiceEJB"
java.io.FileNotFoundException: http://example.com/HelloWorld.wsdl
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at java.net.URL.openStream(URL.java:1007)
at 
org.apache.geronimo.axis2.AxisServiceGenerator.readWSDL(AxisServiceGenerator.java:302)
at 
org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:141)
at 
org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:145)
at 
org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:56)
at 
org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:70)
...
{noformat}

The workaround that helped in the case of the Jetty/CXF assembly does not work 
with Tomcat/Axis.

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

[jira] Updated: (GERONIMO-4500) Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration

[Janko Heilgeist (JIRA)]

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

Janko Heilgeist updated GERONIMO-4500:
--

Attachment: geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar
geronimo-wsdllocation-jetty_cxf.tar.gz

Simple example project and the deployable EJB-JAR to reproduce the exception

> Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration
> ---
>
> Key: GERONIMO-4500
> URL: https://issues.apache.org/jira/browse/GERONIMO-4500
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
> Environment: Geronimo 2.2-SNAPSHOT, Jetty/CXF assembly
>Reporter: Janko Heilgeist
> Attachments: geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar, 
> geronimo-wsdllocation-jetty_cxf.tar.gz
>
>
> I've built an EJB-JAR packaging a web service. The JAR contains all classes, 
> SEI and service stub generated from an existing WSDL (which is also inside 
> this JAR). Additionally, it contains the actual EJB implementing the web 
> service.
> I tried to annotate the web service implementation with
> {code:java}
> @WebService( ..., wsdlLocation="http://example.com/myservice.wsdl";)
> {code}
> and add a META-INF/jax-ws-catalog.xml:
> {code:xml}
> 
>  "http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd";>
> 
>  systemId="http://example.com/myservice.wsdl";
>   uri="wsdl/myservice.wsdl"/>
> 
> {code}
> During deployment, the following exception is thrown:
> {noformat}
> 2009-01-07 17:33:53,087 WARN  [OASISCatalogManager] Error loading 
> META-INF/jax-ws-catalog.xml catalog files
> java.io.FileNotFoundException: 
> http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd
> at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:905)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:872)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:282)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at 
> org.apache.xml.resolver.readers.SAXCatalogReader.readCatalog(SAXCatalogReader.java:251)
> at org.apache.xml.resolver.Catalog.parseCatalog(Catalog.java:681)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadCatalogs(OASISCatalogManager.java:108)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:93)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:89)
> at 
> org.apache.cxf.catalog.OASISCatalogManager.register(OASISCatalogManager.java:81)
> ...
> {noformat}
> As a workaround the DOCTYPE declaration can be removed. Without the 
> declaration the exception is gone and the wsdlLocation URL is correctly 
> resolved.

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

[jira] Created: (GERONIMO-4500) Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration

[Janko Heilgeist (JIRA)]

Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration
---

 Key: GERONIMO-4500
 URL: https://issues.apache.org/jira/browse/GERONIMO-4500
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2
 Environment: Geronimo 2.2-SNAPSHOT, Jetty/CXF assembly
Reporter: Janko Heilgeist


I've built an EJB-JAR packaging a web service. The JAR contains all classes, 
SEI and service stub generated from an existing WSDL (which is also inside this 
JAR). Additionally, it contains the actual EJB implementing the web service.

I tried to annotate the web service implementation with

{code:java}
@WebService( ..., wsdlLocation="http://example.com/myservice.wsdl";)
{code}

and add a META-INF/jax-ws-catalog.xml:

{code:xml}

http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd";>

http://example.com/myservice.wsdl";
uri="wsdl/myservice.wsdl"/>

{code}

During deployment, the following exception is thrown:

{noformat}
2009-01-07 17:33:53,087 WARN  [OASISCatalogManager] Error loading 
META-INF/jax-ws-catalog.xml catalog files
java.io.FileNotFoundException: 
http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:905)
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:872)
at 
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:282)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at 
org.apache.xml.resolver.readers.SAXCatalogReader.readCatalog(SAXCatalogReader.java:251)
at org.apache.xml.resolver.Catalog.parseCatalog(Catalog.java:681)
at 
org.apache.cxf.catalog.OASISCatalogManager.loadCatalogs(OASISCatalogManager.java:108)
at 
org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:93)
at 
org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:89)
at 
org.apache.cxf.catalog.OASISCatalogManager.register(OASISCatalogManager.java:81)
...
{noformat}

As a workaround the DOCTYPE declaration can be removed. Without the declaration 
the exception is gone and the wsdlLocation URL is correctly resolved.

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

[jira] Resolved: (GERONIMODEVTOOLS-532) Surface the publish timeout time in the server properties tab like all the other publishing attributes (e.g., publishing interval)

[B.J. Reed (JIRA)]

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

B.J. Reed resolved GERONIMODEVTOOLS-532.


Resolution: Fixed

fixed with r732383.  Thanks Delos Dai for the patch.  Unfortunately, we had to 
go with option 1 to fix this.  Your patch created a second Server Overview page 
and we couldn't find a way to get rid of the first page.

There were a few things I noticed in the files you created.  Try not to use 
tabs, use 4 spaces instead.  Copy the license header from another file to put 
at the top of any new file.  Also put the following in a comment so that 
versions will be kept track of:
@version $Rev$ $Date$

Thanks again.

> Surface the publish timeout time in the server properties tab like all the 
> other publishing attributes (e.g., publishing interval)
> --
>
> Key: GERONIMODEVTOOLS-532
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-532
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 532.patch
>
>


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

[jira] Assigned: (GERONIMODEVTOOLS-532) Surface the publish timeout time in the server properties tab like all the other publishing attributes (e.g., publishing interval)

[B.J. Reed (JIRA)]

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

B.J. Reed reassigned GERONIMODEVTOOLS-532:
--

Assignee: B.J. Reed  (was: Tim McConnell)

> Surface the publish timeout time in the server properties tab like all the 
> other publishing attributes (e.g., publishing interval)
> --
>
> Key: GERONIMODEVTOOLS-532
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-532
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: Tim McConnell
>Assignee: B.J. Reed
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 532.patch
>
>


-- 
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: 732347

[gawor]

Geronimo Revision: 732347 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 39 minutes 29 seconds
[INFO] Finished at: Wed Jan 07 09:50:46 EST 2009
[INFO] Final Memory: 390M/1014M
[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/20090107/logs-0900-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[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:47.144
[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 35 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:12.437) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:30.355) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:37.575) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.667) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:13.425) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:22.950) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:45.330) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:45.512) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:51.254) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:46.481) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:30.375) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.724) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:29.419) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:45.989) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:40.464) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.119) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.959) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:50.791) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4484:


Only applied console-message-base and console-message-core locally and am 
running into a testsuite failure for testNewJMSResource due to a confirmation 
prompt for uninstall in the JEE Connector not being displayed.  Also the 
resulting JEE Connector portlet display becomes corrupt after the uninstall

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMO-4497) Searching for resources in MultiParentClassLoader is not fully optimized

[Jeff Lu (JIRA)]

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

Jeff Lu commented on GERONIMO-4497:
---

By copying xercesImpl and xmlParserAPIs into the lib\endorsed directory, the 
performance is up to par as it is in Geronimo 1.1.1.  It almost would make 
sense to be able to copy the required jars into the application.ear\lib 
directory.

> Searching for resources in MultiParentClassLoader is not fully optimized
> 
>
> Key: GERONIMO-4497
> URL: https://issues.apache.org/jira/browse/GERONIMO-4497
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.4, 2.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.4, 2.2
>
>
> In one failing scenario, the BIRT reporting engine is invoked with an XML 
> data file to generate a PDF report file. MultiParentClassLoader.getResource() 
> is invoked many times to search for various XML resources (e.g., 
> DocumentBuilderFactory). MultiParentClassLoader searches through the current 
> classloader and all the parent classloaders, which it should, but this can 
> take a considerable amount of time if the resource is never found. It seems 
> that once a resource has been searched for and not found, there is no need to 
> search for it again in the same classloader hierarchy. 

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

[jira] Commented: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[Ivan (JIRA)]

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

Ivan commented on GERONIMO-4499:


To support the Port offset in the activemq.xml may not be very difficult, but 
the question is that the port number 61616 also exists in the activemq-ra, and 
it is serialized in the config.ser. Not sure whether there is a proper way to 
handler it.


> can't use PortOffset in var\config\config-substitutions.properties to start 
> two geronimo instance at the same machine.
> --
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to 
> start two geronimo instance at the same machine.
> 1, install two geronimo server  serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0 
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*:  Both serverA and serverB could be started without 
> problems.
> *actual result*: serverA started, but server B failed to start with a 
> exception below in log:
> -
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
> Message Broker. Reason: java.io.IOException: Transport Connector could not be 
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX: 
> Failed to bind to server socket: tcp://localhost:61616 due to: 
> java.net.BindException: Address already in use: JVM_Bind
>   at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>   at 
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
>   at 
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
>   at 
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Updated: (GERONIMO-4495) Invoking stop method on a gbean whose instancestate is destoryed caused that gbean in the stopping state

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4495:
---

Attachment: Geronimo-4495.patch

I have run the unit testcases for geronimo-kernel, all passed.
Please help to review it, thanks !

> Invoking stop method on a gbean whose instancestate is destoryed caused that 
> gbean in the stopping state
> 
>
> Key: GERONIMO-4495
> URL: https://issues.apache.org/jira/browse/GERONIMO-4495
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.2
>Reporter: Ivan
> Attachments: Geronimo-4495.patch
>
>
> If one gbean's instancestate is in the destoryed state and its gbeanstate is 
> in the failed state. Then we invoke the stop method on that gbean, then the 
> gbean will in the stopping state.
> So, we never could start it by calling the startRecursive() method.
> Shall the stop method returns directly when the gbean state is in failed 
> state ?
> Thanks for giving a comment !

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

[jira] Commented: (GERONIMO-4303) Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no classloader option

[Lin Sun (JIRA)]

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

Lin Sun commented on GERONIMO-4303:
---

Hi Jeff,

Thanks for producing these pages.  I quickly looked at the first two links and 
here are my comments so far -

for the 1st link -

1. you can mention that framework is pre-selected for you by default.

2. the 3rd bullet under "Identifying the functional components required by our 
server.", I wonder if it is necessary, because the Datasource pool plugin 
should have a depedency on system-database.  Also, if the app client has 
dependency on either the console/dbpool/jdbc_userds/1.0/car plugin or 
default/StatelessSessionEJB/1.0/car, or both, then you don't need to select the 
ones that the app client depends on.   The plugin installer will install the 
plugin and all its dependencies for you automatically.

3. you might want to update the screen shot for No. 7 to display exactly what 
you closed earlier.

4. you might want to give desps to your plugins, such as the app client and 
default/StatelessSessionEJB/1.0/car.  It will make things look nicer on the 
screen shot for No. 7 and 8.

for the 2nd link -

1. for gshell, you'll have to select the framework plugin group manually.   I'd 
suggest us showing an example with framework selected.

For both links -

1. you might want to demonstrate the assemblies server after it is build.  For 
example, cd to the directory and list the directory structure... able to start 
the server, list configurations - should contain at list what you selected 
earlier on to build the custom server.

Thanks again

Lin



> Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no 
> classloader option
> 
>
> Key: GERONIMO-4303
> URL: https://issues.apache.org/jira/browse/GERONIMO-4303
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.2
>Reporter: Donald Woods
>Assignee: Lin Sun
> Fix For: 2.2
>
>
> Need to make sure this new pluginGroup attribute and no plan behavior gets 
> added to the 2.2 Docs.  We should also document what pluginprofiles we will 
> be providing in 2.2 (along with adding some info to the GMOxDEV wiki, as we 
> want these to be portable between releases) and what each one provides.

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

[jira] Commented: (GERONIMO-4303) Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no classloader option

[Donald Woods (JIRA)]

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

Donald Woods commented on GERONIMO-4303:


Looking good.  Some comments so far:
#1 - No longer have to manually choose Framework for Function centric 
assemblies (check with Lin on her recent changes)
#2 - No longer have to choose Boilerplate or Framework for Application/Function 
centric assemblies (check with Lin on her recent changes)
#3 - I'll defer to Tim/BJ/Ted for review
#4 - Needs to be completed

> Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no 
> classloader option
> 
>
> Key: GERONIMO-4303
> URL: https://issues.apache.org/jira/browse/GERONIMO-4303
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.2
>Reporter: Donald Woods
>Assignee: Lin Sun
> Fix For: 2.2
>
>
> Need to make sure this new pluginGroup attribute and no plan behavior gets 
> added to the 2.2 Docs.  We should also document what pluginprofiles we will 
> be providing in 2.2 (along with adding some info to the GMOxDEV wiki, as we 
> want these to be portable between releases) and what each one provides.

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

[jira] Commented: (GERONIMO-4486) Custom server assembly portlet doesn't filter specific word

[Lin Sun (JIRA)]

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

Lin Sun commented on GERONIMO-4486:
---

There are quite a few builds yesterday and I don't think the change (rev 
732029) went into the build you used.   Can you please try a today's build 
(1/7)?Thanks

Lin

> Custom server assembly portlet doesn't filter specific word
> ---
>
> Key: GERONIMO-4486
> URL: https://issues.apache.org/jira/browse/GERONIMO-4486
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - IBM SDK 1.6
> - Windows XP SP2 English
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Critical
> Fix For: 2.2
>
>
> In Custom server assebmly portlet,  the function "Filter by category and 
> name" seems stop working when I type "console", but it works well on other 
> words like "tomcat", "dojo", etc.  I test in both IE 7 and firefox 3.0.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-4488) Framework assembly can not be stopped successfully

[Lin Sun (JIRA)]

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

Lin Sun commented on GERONIMO-4488:
---

There are quite a few builds yesterday and I don't think the change (rev 
732119) went into the build you used.   Can you please try a today's build 
(1/7)?   You should be able to see ServerHostName set to 0.0.0.0 in 
var/config/config-substituion.properties in the framework server.   Thanks

Lin

> Framework assembly can not be stopped successfully
> --
>
> Key: GERONIMO-4488
> URL: https://issues.apache.org/jira/browse/GERONIMO-4488
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - Windows XP SP2 English + IBM SDK 1.6.0
> - Windows XP SP2 Simplified Chinese + Sun JDK 1.5.0-16
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: gshell.log, gshell_20090105.log
>
>
> Assemble a custom server with following steps:
> - start geronimo server (either jetty or tomcat version)
> - login admin console
> - start server assembly by selecting function centric
> - select only Framework group, and complete the assembly following portlet 
> instruction
> - stop geronimo server 
> - start custom server just created with start-server.bat (custom server can 
> be started successfully)
> - stop custom server with stop-server.bat or shutdown.bat, exception msg 
> occurs in command window, and the custom server is still up.
> I tried in both 20081229 and 20081230 build, and log file will be attached.

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

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets

[Gang Yin (JIRA)]

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

Gang Yin commented on GERONIMO-4484:


Hi, Donald,
All needed patches are submitted, please help to review them, thanks.

> Extraction, localization and display of messages generated in portlets
> --
>
> Key: GERONIMO-4484
> URL: https://issues.apache.org/jira/browse/GERONIMO-4484
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Gang Yin
>Assignee: Donald Woods
> Fix For: 2.2
>
> Attachments: common-message-activemq.patch, 
> common-message-base.patch, common-message-core.patch, 
> common-message-debugviews.patch, common-message-monotor.patch, 
> common-message-openejb.patch, common-message-plancreator.patch, 
> common-message-plugin.patch, common-message-sysdb.patch, err_abbr.jpg, 
> err_detail.jpg, info.jpg
>
>
> Currently in admin console, the messages generated from portlets are 
> hard-coded and thus cannot be localized, moreover, their manner of display in 
> the admin console differs from each other.
> I am trying to extract all the hard coded messages from the portlets to 
> resource bundle and work on a unified way to display these messages in admin 
> console. The styles of the messages are according to their types: error 
> messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMODEVTOOLS-547) code cleanup on Server Plugin Manager

[Delos Dai (JIRA)]

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

Delos Dai commented on GERONIMODEVTOOLS-547:


Sorry for the inconvenience!

I think the wizard can be launched with 547_updated.patch this time.

Thanks very much for your help!

> code cleanup on Server Plugin Manager
> -
>
> Key: GERONIMODEVTOOLS-547
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-547
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: B.J. Reed
>Assignee: B.J. Reed
>Priority: Minor
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 547.patch, 547_updated.patch
>
>
> From the initial version of the Server Plugin Manager, there are several 
> things that can be streamlined.
> 1. use geronimo-system.jar file instead of the jaxbmodels 
> (org.apache.geronimo.jee.plugin).  When I tried to use the .jar file, I kept 
> get exceptions that ObjectFactory could not be found.  As it is now, the 
> org.apache.geronimo.jee.plugin classes are exact duplicates of what is in the 
> geronimo-system.jar file
> 2. GeronimoServerPluginManager.java should use PluginInstallerGbean.  This 
> will cut down on a lot of methods that were duplicated into this class.
> 3. Other methods in GeronimoServerPluginManager.java can probably make other 
> calls to the jar files that we already are bringing into the GEP.
> All of this will make the code much slimmer and re-use a lot of good code.

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

[jira] Updated: (GERONIMODEVTOOLS-547) code cleanup on Server Plugin Manager

[Delos Dai (JIRA)]

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

Delos Dai updated GERONIMODEVTOOLS-547:
---

Attachment: 547_updated.patch

Since previous patch generated exception, update the code and attach the new 
patch

> code cleanup on Server Plugin Manager
> -
>
> Key: GERONIMODEVTOOLS-547
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-547
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.2.0, 2.1.4
>Reporter: B.J. Reed
>Assignee: B.J. Reed
>Priority: Minor
> Fix For: 2.2.0, 2.1.4
>
> Attachments: 547.patch, 547_updated.patch
>
>
> From the initial version of the Server Plugin Manager, there are several 
> things that can be streamlined.
> 1. use geronimo-system.jar file instead of the jaxbmodels 
> (org.apache.geronimo.jee.plugin).  When I tried to use the .jar file, I kept 
> get exceptions that ObjectFactory could not be found.  As it is now, the 
> org.apache.geronimo.jee.plugin classes are exact duplicates of what is in the 
> geronimo-system.jar file
> 2. GeronimoServerPluginManager.java should use PluginInstallerGbean.  This 
> will cut down on a lot of methods that were duplicated into this class.
> 3. Other methods in GeronimoServerPluginManager.java can probably make other 
> calls to the jar files that we already are bringing into the GEP.
> All of this will make the code much slimmer and re-use a lot of good code.

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

[jira] Closed: (GERONIMO-4491) Can not assemble application centric custom server if there is deployed application, which is not converted into plugin

[Donald Woods (JIRA)]

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

Donald Woods closed GERONIMO-4491.
--


Verified by Han Hong Fang

> Can not assemble application centric custom server if there is deployed 
> application, which is not converted into plugin
> ---
>
> Key: GERONIMO-4491
> URL: https://issues.apache.org/jira/browse/GERONIMO-4491
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.6.0
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Critical
> Fix For: 2.2
>
> Attachments: screenshot-1.jpg
>
>
> I tested the following scenario in geronimo-tomcat6-javaee5-2.2-SNAPSHOT 
> (build 20081229).
> 1. start geronimo server
> 2. install two sample applications in admin console: cviewer.war and 
> servlet-examples.war
> 3. I turn servlet-examples.war into plugin, and intend to assemble a custom 
> server for this application
> 4. cd geronimo-home/bin
> 5. gsh.bat
> 6. deploy/assemble
> 7. select 2 for application centric, and type group/artifact name
> Then I get the following error msg: 
> Listing application plugins from the local Geronimo server
> ERROR IllegalStateException: No configuration found for 
> 'com.ibm.wasce.samples/cviewer/2.1.1.1/car'
> I intent to create custom server for sample application named 
> servlet-examples, so I didn't turn cviewer into plugin. But I was blocked by 
> cviewer.

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

Re: [CONF] Apache Geronimo: SideNav Subprojects (page edited)

[Donald Woods]

It's on my ToDo list  Wanted to finish the copyright date updates 
and get some TCK buckets running before I switch back.



-Donald


Jason Dillon wrote:
Why aren't these links?  Its pointless IMO to add items to nav pages 
which are not links of some sort.


--jason


On Jan 6, 2009, at 10:38 PM, conflue...@apache.org 
 wrote:


Page Edited : GMOxSITE 
 : SideNav 
Subprojects 



SideNav Subprojects 
 has 
been edited by Donald Woods 
 (Jan 06, 2009).


(View changes) 



Content:

Development Tools^ 
Sample Applications^ 
GBuild^ 
GShell^ 
XBean^ 
Yoko^ 
Java EE Specs
Components
Plugins

Powered by Atlassian Confluence 
 (Version: 
2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request 



Unsubscribe or edit your notifications preferences 

Re: [GSHELL] Timeframe ?

[Guillaume Nodet]

We are planning a release of ServiceMix Kernel in the near future.
What are the missing bits to release GShell soon ?

On Fri, Oct 17, 2008 at 08:25, Jason Dillon  wrote:
> The GShell APIs are getting closer and closer to stability.  The major
> changes have all been committed, and I don't have any plans to make any
> other significant changes to the core APIs.  What I am doing now is trying
> to slim down the core dependencies and speed up the boot time... and sorting
> out some of the many HACK/TODO comments which I've littered the codebase
> with.
>
> As for an alpha-2 release, I imagine that will be on the horizon soon.  I
> don't plan on having all of the little things fixed before that, though I
> hope to sort out a few of the more significant ones before releasing.  If I
> had to guess I'd say that the codebase should be in a position to be
> released in 2-4 weeks at present change velocity.
>
> --jason
>
>
> On Oct 16, 2008, at 2:23 PM, Guillaume Nodet wrote:
>
>> In ServiceMix, we are considering upgrading to the latest trunk of
>> GShell and I've already done the bigger part of the upgrade locally on
>> my HD.  Btw, I've committed a few small changes for that yesterday.
>> However, I'm worried about the stability of gshell.  We currently use
>> an old and unreleased version of gshell, but I'd like to avoid such
>> issue and having to rewrite this integration once more.
>> Jason, what's your feeling about gshell's stability (in terms of APIs)
>> and a possible ETA for a new release (be it alpha-2 or whatever) ?
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> 
>> Blog: http://gnodet.blogspot.com/
>> 
>> Open Source SOA
>> http://fusesource.com
>
>



-- 
Cheers,
Guillaume Nodet

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

Open Source SOA
http://fusesource.com

[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan commented on GERONIMO-4475:


I divided the patch for three parts, for we could see clearly which parts are 
changed.

activemq-portlet
a. jsp files ( broker editing in the "server" folder and jms resource in 
the "jmswizard" folder )
b. java files ( broker editing and jms resource to support multiple brokers 
)
c. resource property files

geronimo-management
a. add two methods to the jmsmanager interface ( addbroker and removebroker 
)

activemq-broker
a. add a activemq-template file
b. change the activemq.xml file, use system property placeholder 
${activemq.brokerName}
c. do some modification about the plan.xml
d. change the pom file to copy the template file to the conf/template folder

geronimo-activemq
a. add a new attribute ( broker name ) for the Broker GBean 

Currently, the patch provide a simple way to add the broker. When the user 
clicks the add broker link, a big edit box will show on the page, and a 
template configuraiton file will be loaded. So that the user can directly edit 
the configuration in that edit box. When the save button is clicked, some 
actions will be done :
a. save the xml file to /var/activemq/conf/${brokerName}.xml
b. set the data folder to /var/activemq/data/${brokerName}
c. A broker gbean is added to the activemq-broker configuration

For the user could configure the connectors in the broker configuration file, 
so I removed the add connector links (actually, no implementations for it exist 
 in the current source repository).

Please help to giving any comment , thanks !

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-activemq-broker.patch, 
> G4475-activemq-portlet.patch, G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

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

[jira] Updated: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4475:
---

Attachment: G4475-activemq-portlet.patch

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-activemq-broker.patch, 
> G4475-activemq-portlet.patch, G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

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

[jira] Updated: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4475:
---

Attachment: G4475-activemq-broker.patch

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-activemq-broker.patch, 
> G4475-activemq-portlet.patch, G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

-- 
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: 732265

[gawor]

Geronimo Revision: 732265 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090107
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 3 seconds
[INFO] Finished at: Wed Jan 07 03:47:17 EST 2009
[INFO] Final Memory: 427M/972M
[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/20090107/logs-0300-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[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:47.145
[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 35 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:13.963) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:29.784) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:35.607) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.601) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:16.664) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:40.749) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:47.124) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:43.894) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:55.683) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:45.176) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:31.189) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.543) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:30.725) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.868) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:40.048) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.971) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.674) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:51.645) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test

[jira] Updated: (GERONIMO-4475) Improve JMS portlet for Borker configuration

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4475:
---

Attachment: G4475-geronimo-management.patch

> Improve JMS portlet for Borker configuration
> 
>
> Key: GERONIMO-4475
> URL: https://issues.apache.org/jira/browse/GERONIMO-4475
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2
>
> Attachments: G4475-geronimo-management.patch
>
>
> Currently in the administrator console, the users could not add another embed 
> broker. Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit 
> the spring XML file in it. Shall we give the user a more friendly interface, 
> so that they do not need the edit the XML file directly. I am not sure how it 
> should look like.
> 3. Update the connector port let,  so that while creating a new connector, 
> the user could specify the broker that it belongs to.
> Please help to give some comments !

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

[jira] Commented: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[Shawn Jiang (JIRA)]

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

Shawn Jiang commented on GERONIMO-4499:
---

I'm quite sure this is caused by  the same activeMQ port setting in 

var\activemq\conf\activemq.xml

{code:xml}
   



{code}

Is there a way to also use the variables defined in 
config-substitutions.properties in this xml ?

> can't use PortOffset in var\config\config-substitutions.properties to start 
> two geronimo instance at the same machine.
> --
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to 
> start two geronimo instance at the same machine.
> 1, install two geronimo server  serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0 
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*:  Both serverA and serverB could be started without 
> problems.
> *actual result*: serverA started, but server B failed to start with a 
> exception below in log:
> -
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
> Message Broker. Reason: java.io.IOException: Transport Connector could not be 
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX: 
> Failed to bind to server socket: tcp://localhost:61616 due to: 
> java.net.BindException: Address already in use: JVM_Bind
>   at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>   at 
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
>   at 
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
>   at 
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Created: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.

[Shawn Jiang (JIRA)]

can't use PortOffset in var\config\config-substitutions.properties to start two 
geronimo instance at the same machine.
--

 Key: GERONIMO-4499
 URL: https://issues.apache.org/jira/browse/GERONIMO-4499
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: ActiveMQ
Affects Versions: 2.2
 Environment: Windows XP SP 2 + IBM SDK 1.5.0
Reporter: Shawn Jiang
Priority: Minor


I'm trying to use PortOffset in var\config\config-substitutions.properties to 
start two geronimo instance at the same machine.

1, install two geronimo server  serverA, serverB.

2, update the PortOffset in var\config\config-substitutions.properties from 0 
to 10 for serverB.

3, start serverA.

4, start serverB.

*expected result*:  Both serverA and serverB could be started without problems.

*actual result*: serverA started, but server B failed to start with a exception 
below in log:


-
2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS 
Message Broker. Reason: java.io.IOException: Transport Connector could not be 
registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due 
to: java.net.BindException: Address already in use: JVM_Bind
java.io.IOException: Transport Connector could not be registered in JMX: Failed 
to bind to server socket: tcp://localhost:61616 due to: java.net.BindException: 
Address already in use: JVM_Bind
at 
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
at 
org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
at 
org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
at 
org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
at 
org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)

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

[jira] Commented: (GERONIMO-4303) Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no classloader option

[Chi Runhua (JIRA)]

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

Chi Runhua commented on GERONIMO-4303:
--

So far we have the following list of topics to be updated upon plugin profiles 
in GMOxDOC22.

1. 
http://cwiki.apache.org/confluence/display/GMOxDOC22/Assembling+a+server+via+Console
2.  
http://cwiki.apache.org/confluence/display/GMOxDOC22/Assembling+a+server+via+command+line
 
3.  
http://cwiki.apache.org/confluence/display/GMOxDOC22/Assembling+a+server+via+GEP
4.  http://cwiki.apache.org/GMOxDOC22/plugin-groups.html


Any other topics, please add


Jeff C

> Document new 2.2 Plugin features - plugingroups, pluginGroup attribute and no 
> classloader option
> 
>
> Key: GERONIMO-4303
> URL: https://issues.apache.org/jira/browse/GERONIMO-4303
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.2
>Reporter: Donald Woods
>Assignee: Lin Sun
> Fix For: 2.2
>
>
> Need to make sure this new pluginGroup attribute and no plan behavior gets 
> added to the 2.2 Docs.  We should also document what pluginprofiles we will 
> be providing in 2.2 (along with adding some info to the GMOxDEV wiki, as we 
> want these to be portable between releases) and what each one provides.

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

[jira] Updated: (GERONIMO-4498) ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when farming geronimo using Deployment

[Shawn Jiang (JIRA)]

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

Shawn Jiang updated GERONIMO-4498:
--

Attachment: G4498_shawn.patch

This is the patch to restore the BasicExtendedJMXConnectorInfoEditor class.   
I'm not sure why it was deleted,  Can anyone help review it ?  Thanks.


> ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when 
> farming geronimo using Deployment
> ---
>
> Key: GERONIMO-4498
> URL: https://issues.apache.org/jira/browse/GERONIMO-4498
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: G4498_shawn.patch
>
>
> I'm trying to farm geronimo using deployment according to 
> http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html.
> 1, install the latest trunk 2.2-snapshot build as nodeA
> 2, update the var\config\config.xml with following farming config info:
>   {code:xml}
>  load="false">
> 
> ${clusterNodeName}
> 
> 
> ${clusterName}
> 
>name="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=NodeInfo,name=NodeInfoB"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> 9.123.237.58
> 1109
> JMXConnector
> false
>   
> 
> 
> {code}
> 3, start the server.
> 4, use {noformat}deploy.bat --user system --password manager start 
> org.apache.geronimo.configs/farming//car {noformat} to start the farming 
> config.
> *expected result*:   the farming config could be started without problem.
> *actual result*:the farming config could not be started up with 
> exceptions in log. the log is:
> __
> 2009-01-07 16:37:56,453 ERROR [GBeanInstanceState] Error while starting; 
> GBean is now in the FAILED state: 
> abstractName="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car"
> java.lang.IllegalStateException: Cannot load property editor 
> [org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor]
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.loadPropertyEditor(GBeanOverride.java:423)
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.getValue(GBeanOverride.java:399)
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.applyOverrides(GBeanOverride.java:359)
>   at 
> org.apache.geronimo.system.configuration.LocalAttributeManager.setAttributes(LocalAttributeManager.java:228)
>   at 
> org.apache.geronimo.system.configuration.LocalAttributeManager.applyOverrides(LocalAttributeManager.java:197)
>   at 
> org.apache.geronimo.kernel.config.Configuration.(Configuration.java:292)
>   at sun.reflect.GeneratedConstructorAccessor23.newInstance(Unknown 
> Source)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>   at 
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:882)
>   at 
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:272)
>   at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>   at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:910)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:359)
>   at 
> 

asm shading

[Jacek Laskowski]

Hi,

DMB did asm shading for openejb 3.1 so people working with Hibernate
won't run into any issues (cf.
https://issues.apache.org/jira/browse/OPENEJB-892). Instead of his
doing in OpenEJB it'd be great if xbean provided a shaded asm itself.
Is this a correct approach? I've attempted to fix it and created a new
module - xbean-asm-shaded with the following part of its pom.xml:



org.apache.maven.plugins
maven-shade-plugin


package

shade




org.objectweb.asm

org.apache.xbean.asm








It broke the tests in xbean-reflect and I don't know why. I don't know
why reader.accept(visitor, false); in AsmParameterNameLoader used
boolean input param as ClassReader doesn't provide such a method -
http://asm.objectweb.org/current/doc/javadoc/user/org/objectweb/asm/ClassReader.html.
Am I doing it wrong? Help appreciated. I'd like to get it fixed in
XBean 3.5 if it won't last too long (say 2-3 days)

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

Re: xbean 3.5 release?

[Jacek Laskowski]

On Tue, Jan 6, 2009 at 4:16 PM, Joe Bohn  wrote:
>
> So can somebody push a release for 3.5?  Are there active issues that need to
> be resolved prior to a 3.5 release (I've seen some Geronimo JIRAs that might
> be xbean issues)?

Wait a bit until I get the asm shading issue sorted out. It's not been
reported yet, and am doing it now how to work it around.

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

[jira] Created: (GERONIMO-4498) ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when farming geronimo using Deployment

[Shawn Jiang (JIRA)]

ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when 
farming geronimo using Deployment
---

 Key: GERONIMO-4498
 URL: https://issues.apache.org/jira/browse/GERONIMO-4498
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Clustering
Affects Versions: 2.2
 Environment: Windows XP SP 2 + IBM SDK 1.5.0
Reporter: Shawn Jiang
Priority: Blocker
 Fix For: 2.2


I'm trying to farm geronimo using deployment according to 
http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html.

1, install the latest trunk 2.2-snapshot build as nodeA

2, update the var\config\config.xml with following farming config info:
  {code:xml}


${clusterNodeName}


${clusterName}


NODE-B

http://geronimo.apache.org/xml/ns/attributes-1.2"; 
xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
system
manager
rmi
9.123.237.58
1109
JMXConnector
false
  


{code}

3, start the server.

4, use {noformat}deploy.bat --user system --password manager start 
org.apache.geronimo.configs/farming//car {noformat} to start the farming config.

*expected result*:   the farming config could be started without problem.

*actual result*:the farming config could not be started up with exceptions 
in log. the log is:
__
2009-01-07 16:37:56,453 ERROR [GBeanInstanceState] Error while starting; GBean 
is now in the FAILED state: 
abstractName="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car"
java.lang.IllegalStateException: Cannot load property editor 
[org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor]
at 
org.apache.geronimo.system.configuration.GBeanOverride.loadPropertyEditor(GBeanOverride.java:423)
at 
org.apache.geronimo.system.configuration.GBeanOverride.getValue(GBeanOverride.java:399)
at 
org.apache.geronimo.system.configuration.GBeanOverride.applyOverrides(GBeanOverride.java:359)
at 
org.apache.geronimo.system.configuration.LocalAttributeManager.setAttributes(LocalAttributeManager.java:228)
at 
org.apache.geronimo.system.configuration.LocalAttributeManager.applyOverrides(LocalAttributeManager.java:197)
at 
org.apache.geronimo.kernel.config.Configuration.(Configuration.java:292)
at sun.reflect.GeneratedConstructorAccessor23.newInstance(Unknown 
Source)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at 
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:882)
at 
org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:272)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:910)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524)
at 
org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:359)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:163)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:312)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
at 
org.apache.geroni

[jira] Commented: (GERONIMO-4486) Custom server assembly portlet doesn't filter specific word

[Han Hong Fang (JIRA)]

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

Han Hong Fang commented on GERONIMO-4486:
-

Filter still doesn't work on "console", but works well on "ejb", "tomcat" etc. 
Verified in build 20090106 both tomcat and jetty.

> Custom server assembly portlet doesn't filter specific word
> ---
>
> Key: GERONIMO-4486
> URL: https://issues.apache.org/jira/browse/GERONIMO-4486
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - IBM SDK 1.6
> - Windows XP SP2 English
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Critical
> Fix For: 2.2
>
>
> In Custom server assebmly portlet,  the function "Filter by category and 
> name" seems stop working when I type "console", but it works well on other 
> words like "tomcat", "dojo", etc.  I test in both IE 7 and firefox 3.0.4.

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

[About WebBeans Integration]

[Gurkan Erdogdu]

Hi folks,

We are developing the implementation of the JSR-299 WebBeans specification as 
an incubator, OpenWebBeans. In the last specification, it says that this 
functionality must be integrated into the Java EE 6.0 Servers. Currently, 
OpenWebBeans is working as a plugin (i.e configure in the web.xml via 
ServletCotnextListener, Filter etc.).

Do you have any plan to integrate this stuff into the Geronimo runtime? If so, 
how could we collaborate on this to start rolling the ball?

/Gurkan
Incubator OpenWebBeans Project Lead



  

[jira] Commented: (GERONIMO-4488) Framework assembly can not be stopped successfully

[Han Hong Fang (JIRA)]

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

Han Hong Fang commented on GERONIMO-4488:
-

The problem still exists in build 20090106 (both tomcat and jetty downloaded 
from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090106/)

I tried following server assembly.
- Framework only
- Framework + webservice axis2

Same exception occurs when try to stop the custom server: (9.123.237.24 is ip 
of my machine, where I tested the fix.)

org.apache.geronimo.common.DeploymentException: Unable to connect to server at d
eployer:geronimo:jmx://localhost:1099 -- Connection refused to host: 
9.123.237.24; 
nested exception is:
java.net.ConnectException: Connection refused: connect
at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(Serv
erConnection.java:154)

> Framework assembly can not be stopped successfully
> --
>
> Key: GERONIMO-4488
> URL: https://issues.apache.org/jira/browse/GERONIMO-4488
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.2
> Environment: - Windows XP SP2 English + IBM SDK 1.6.0
> - Windows XP SP2 Simplified Chinese + Sun JDK 1.5.0-16
>Reporter: Han Hong Fang
>Assignee: Lin Sun
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: gshell.log, gshell_20090105.log
>
>
> Assemble a custom server with following steps:
> - start geronimo server (either jetty or tomcat version)
> - login admin console
> - start server assembly by selecting function centric
> - select only Framework group, and complete the assembly following portlet 
> instruction
> - stop geronimo server 
> - start custom server just created with start-server.bat (custom server can 
> be started successfully)
> - stop custom server with stop-server.bat or shutdown.bat, exception msg 
> occurs in command window, and the custom server is still up.
> I tried in both 20081229 and 20081230 build, and log file will be attached.

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