[jira] Commented: (GERONIMO-3902) start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell
[ https://issues.apache.org/jira/browse/GERONIMO-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580244#action_12580244 ] Jason Dillon commented on GERONIMO-3902: Seems reasonable for now, we can make it fancier later for individual option overrides if needed. start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell --- Key: GERONIMO-3902 URL: https://issues.apache.org/jira/browse/GERONIMO-3902 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jason Warner Assignee: Jason Warner Fix For: 2.1.1, 2.2 Attachments: Geronimo-3902-IncludesStartClient.patch, Geronimo-3902.patch The start-server, default.groovy file is included in etc/rc.d directory and contains a command to set the max heap size for geronimo when starting through gshell. This file overrides any max heap size values that are set via the command line causing issues when starting the server with non-default max heap values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580261#action_12580261 ] Shiva Kumar H R commented on GERONIMO-3843: --- Thanks Donald. Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1, 2.1.1, 2.2 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1, 2.2 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3931) Unable to delete a datasource from administrative console
Unable to delete a datasource from administrative console - Key: GERONIMO-3931 URL: https://issues.apache.org/jira/browse/GERONIMO-3931 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: databases Affects Versions: 2.1 Environment: Windows XP, AG2.1 Reporter: Ashish Jain While trying to delete a datasource from Administrative console I get the following error in the command prompt 13:01:47,000 ERROR [DatabasePoolPortlet] Undeployment unsuccessful! In geronimo.log I get the following error 13:02:09,343 ERROR [DatabasePoolPortlet] Undeployment unsuccessful! 13:02:10,359 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: '/system-database.DBWizard!1134683811|0' Steps to recreate the issue 1) Create a DerbyEmbedded database pool. 2) Delete the pool Workaround is to manually remove the entries from config.xml and repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2; environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment tomcat-clustering-wadi/ -- this is the correct element name to use for tomcat. /web-app Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The deployment plan I am using is: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment clustering-wadi/ /web-app
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: JMSResource_portlet_1.1.patch Thanks Vamsi for the comments.I have tried to correct all of them in the attached patch JMSResource_portlet_1.1.patch .Let me know incase I have missed out anything. There were two exceptions in the trace you have given.I could reproduce both the issues: I was putting some activemq text messages in session to show its contents.You get the exception when trying to stop the server while the session has some messages in it.Geronimo tries to serialise and save these non-serializable messages and results in the exception. I have corrected this one by creating my own serializable object to hold the necessary message info. The other exception is generated after sending a non-persistent messages to activemq queues/topics. This is a defect in activemq.I have reported the same in the following JIRA https://issues.apache.org/jira/browse/GERONIMO-3928 Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Fix For: 2.1.1, 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hello Vamsi, I verified on G Jetty 2.1 with Safari... Based on your previous problem description (black boxes instead of numbered ones), I inferred that somehow your browser was not propagating a session cookie to the server. So, I decided to give a shot with FireFox and interestingly I was able to identify the problem. In the standard DD, the demo application used to declare this: context-param param-nameorg.mortbay.jetty.servlet.SessionPath/param-name param-value/wadi/param-value /context-param This instructs Jetty to set the session cookie path to /wadi. As the demo application is deployed to /wadi-webapp, your browser or FireFox do not send to the server the cookies for the path /wadi; hence, the problem. So, I dropped the above xml fragment from the DD, tested with FireFox and deployed another snapshot: http:// snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war Thanks for giving it a try and your patience. Thanks, Gianny On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment tomcat-clustering-wadi/ -- this is the correct element name to use for tomcat. /web-app Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The deployment plan I am using is: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment clustering-wadi/ /web-app
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Thanks Gianny. The sample works now. ++Vamsi On Wed, Mar 19, 2008 at 4:50 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello Vamsi, I verified on G Jetty 2.1 with Safari... Based on your previous problem description (black boxes instead of numbered ones), I inferred that somehow your browser was not propagating a session cookie to the server. So, I decided to give a shot with FireFox and interestingly I was able to identify the problem. In the standard DD, the demo application used to declare this: context-param param-nameorg.mortbay.jetty.servlet.SessionPath/param-name param-value/wadi/param-value /context-param This instructs Jetty to set the session cookie path to /wadi. As the demo application is deployed to /wadi-webapp, your browser or FireFox do not send to the server the cookies for the path /wadi; hence, the problem. So, I dropped the above xml fragment from the DD, tested with FireFox and deployed another snapshot: http:// snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war Thanks for giving it a try and your patience. Thanks, Gianny On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment tomcat-clustering-wadi/ -- this is the correct element name to use for tomcat. /web-app Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The deployment plan I am using is: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type
[jira] Updated: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George updated GERONIMO-3806:
Attachment: GERONIMO-3806_r638814.patch
I am attaching a patch which I feel solves the problem better. Tested it out
with an application. Toby If you can test it with yours and verify that it
doesn't break your app it will be good.
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.2, 2.1, 2.1.1, 2.2
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Manu T George
Priority: Minor
Fix For: 2.1.1, 2.2
Attachments: bug3806-patch.txt, GERONIMO-3806_r638814.patch
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George reassigned GERONIMO-3806:
---
Assignee: toby cabot (was: Manu T George)
Toby can you check if my fix works for you
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.2, 2.1, 2.1.1, 2.2
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: toby cabot
Priority: Minor
Fix For: 2.1.1, 2.2
Attachments: bug3806-patch.txt, GERONIMO-3806_r638814.patch
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, With G Tomcat 2.1 clustering, I sometimes see an error message like the following: 18:25:46,203 ERROR [StandardManager] Could not acquire session [31ECCD48F5DEB00E A4289FBEEC7FDA8A] What is wrong? ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2; environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment tomcat-clustering-wadi/ -- this is the correct element name to use for tomcat. /web-app Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The deployment plan I am using is: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment clustering-wadi/ /web-app
[jira] Updated: (GERONIMO-3811) EjbServer portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3811: --- Fix Version/s: (was: 2.1.1) removed fix version of 2.1.1 based upon comments from Manu EjbServer portlet - Key: GERONIMO-3811 URL: https://issues.apache.org/jira/browse/GERONIMO-3811 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: OpenEJB Environment: All Reporter: Manu T George Fix For: 2.2 Attachments: g3811_r632068.patch, g3811_r634213.patch, openejb.zip, screenshot-1.jpg, screenshot-2.jpg A portlet to show information about the OpenEJB container integrated in Geronimo. It should also allow configuration of some parameters like pool size etc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-23) Command pipe-lines
[
https://issues.apache.org/jira/browse/GSHELL-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580371#action_12580371
]
Guillaume Nodet commented on GSHELL-23:
---
Author: gnodet
Date: Wed Mar 19 06:30:40 2008
Support for | in the command line.
Redirections are not supported yet though.
New Revision: 638824
URL: http://svn.apache.org/viewvc?rev=638824view=rev
Log:
GSHELL-23: command pipelines
Modified:
geronimo/gshell/trunk/gshell-command-api/src/main/java/org/apache/geronimo/gshell/command/CommandExecutor.java
geronimo/gshell/trunk/gshell-core/src/main/java/org/apache/geronimo/gshell/DefaultCommandExecutor.java
geronimo/gshell/trunk/gshell-core/src/main/java/org/apache/geronimo/gshell/DefaultShell.java
geronimo/gshell/trunk/gshell-core/src/main/java/org/apache/geronimo/gshell/ExecutingVisitor.java
geronimo/gshell/trunk/gshell-core/src/main/java/org/apache/geronimo/gshell/GShell.java
geronimo/gshell/trunk/gshell-core/src/main/java/org/apache/geronimo/gshell/LoggingVisitor.java
geronimo/gshell/trunk/gshell-parser/src/main/grammar/CommandLineParser.jjt
geronimo/gshell/trunk/gshell-parser/src/test/java/org/apache/geronimo/gshell/parser/CommandLineParserTest.java
geronimo/gshell/trunk/gshell-parser/src/test/java/org/apache/geronimo/gshell/parser/CommandLineParserVisitorTest.java
geronimo/gshell/trunk/gshell-remote/gshell-remote-client/src/main/java/org/apache/geronimo/gshell/remote/client/RshClient.java
geronimo/gshell/trunk/gshell-remote/gshell-remote-client/src/main/java/org/apache/geronimo/gshell/remote/client/proxy/RemoteShellProxy.java
geronimo/gshell/trunk/gshell-remote/gshell-remote-common/src/main/java/org/apache/geronimo/gshell/remote/message/ExecuteMessage.java
geronimo/gshell/trunk/gshell-remote/gshell-remote-server/src/main/java/org/apache/geronimo/gshell/remote/server/DefaultRemoteShell.java
Command pipe-lines
--
Key: GSHELL-23
URL: https://issues.apache.org/jira/browse/GSHELL-23
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Core, Parser
Reporter: Jason Dillon
Assignee: Erik B. Craig
Fix For: 1.0-alpha-3
Add support for piping the output of one command into another, as in:
{noformat}
echo hi | cat /tmp/foo
{noformat}
This should write hi to the /tmp/foo file.
Follow zsh style, allowing | to concat both stdout+stderr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3902) start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell
[ https://issues.apache.org/jira/browse/GERONIMO-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-3902: -- Assignee: Joe Bohn (was: Jason Warner) start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell --- Key: GERONIMO-3902 URL: https://issues.apache.org/jira/browse/GERONIMO-3902 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jason Warner Assignee: Joe Bohn Fix For: 2.1.1, 2.2 Attachments: Geronimo-3902-IncludesStartClient.patch, Geronimo-3902.patch The start-server, default.groovy file is included in etc/rc.d directory and contains a command to set the max heap size for geronimo when starting through gshell. This file overrides any max heap size values that are set via the command line causing issues when starting the server with non-default max heap values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3902) start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell
[ https://issues.apache.org/jira/browse/GERONIMO-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3902: --- Patch Info: [Patch Available] start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell --- Key: GERONIMO-3902 URL: https://issues.apache.org/jira/browse/GERONIMO-3902 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jason Warner Assignee: Jason Warner Fix For: 2.1.1, 2.2 Attachments: Geronimo-3902-IncludesStartClient.patch, Geronimo-3902.patch The start-server, default.groovy file is included in etc/rc.d directory and contains a command to set the max heap size for geronimo when starting through gshell. This file overrides any max heap size values that are set via the command line causing issues when starting the server with non-default max heap values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3856) Assemble a Server Confirmation Page
[ https://issues.apache.org/jira/browse/GERONIMO-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3856. --- Resolution: Fixed Fix Version/s: 2.2 2.1.1 Committed the patch with some minor changes to trunk (revision 638831) and branches/2.1 (revision 638843). Also, changed layout of the Assemble and Cancel buttons and added a default assembly version. Assemble a Server Confirmation Page --- Key: GERONIMO-3856 URL: https://issues.apache.org/jira/browse/GERONIMO-3856 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Jarek Gawor Priority: Minor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3856.patch Improvements for the Assemble a Server Confirmation Page 1) At minimum the user should provide an artifact id otherwise assembly named --bin.tar.gz will be created. The portlet should check for empty artifact id. 2) If no plugins are selected and 'assemble' button is pressed a nasty exception will be displayed. The portlet should check if at least one plugin was selected. 3) On the confirmation screen and on Windows the server path location will contain / and \. For example c:\geronimo/var/temp/foo.tar.gz. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3856) Assemble a Server Confirmation Page
[ https://issues.apache.org/jira/browse/GERONIMO-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580388#action_12580388 ] Jarek Gawor commented on GERONIMO-3856: --- And I forgot to mention - thanks for the patch Joe! Assemble a Server Confirmation Page --- Key: GERONIMO-3856 URL: https://issues.apache.org/jira/browse/GERONIMO-3856 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Jarek Gawor Priority: Minor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3856.patch Improvements for the Assemble a Server Confirmation Page 1) At minimum the user should provide an artifact id otherwise assembly named --bin.tar.gz will be created. The portlet should check for empty artifact id. 2) If no plugins are selected and 'assemble' button is pressed a nasty exception will be displayed. The portlet should check if at least one plugin was selected. 3) On the confirmation screen and on Windows the server path location will contain / and \. For example c:\geronimo/var/temp/foo.tar.gz. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hi Gianny, I observe that the sample application does not run as expected when I try the clustering scenario on FedoraCore. Application running on each node displays its own set of numbers starting from 1 with the background color of the squares being the node.name set at startup. I observed the same behavior with G Jetty 2.1 and G Tomcat 2.1 distros. What is to be done differently on Linux? ++Vamsi On Wed, Mar 19, 2008 at 4:50 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello Vamsi, I verified on G Jetty 2.1 with Safari... Based on your previous problem description (black boxes instead of numbered ones), I inferred that somehow your browser was not propagating a session cookie to the server. So, I decided to give a shot with FireFox and interestingly I was able to identify the problem. In the standard DD, the demo application used to declare this: context-param param-nameorg.mortbay.jetty.servlet.SessionPath/param-name param-value/wadi/param-value /context-param This instructs Jetty to set the session cookie path to /wadi. As the demo application is deployed to /wadi-webapp, your browser or FireFox do not send to the server the cookies for the path /wadi; hence, the problem. So, I dropped the above xml fragment from the DD, tested with FireFox and deployed another snapshot: http:// snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war Thanks for giving it a try and your patience. Thanks, Gianny On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour [EMAIL PROTECTED] wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2 environment moduleId groupIdorg.codehaus.wadi/groupId artifactIdwadi-webapp/artifactId version2.0M3-SNAPSHOT/version typewar/type /moduleId /environment tomcat-clustering-wadi/ -- this is the correct element name to use for tomcat. /web-app Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The
[jira] Created: (GERONIMO-3932) several enhancements to the async container client sample app
several enhancements to the async container client sample app - Key: GERONIMO-3932 URL: https://issues.apache.org/jira/browse/GERONIMO-3932 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 2.2 Reporter: Sangjin Lee Assignee: Jason Warner Priority: Minor Attachments: GERONIMO-3932.patch I made a few enhancements and bug fixes in the async client sample app. The changes include - calls HttpServletResponse.flushBuffer() to address a Tomcat NPE - added a dump query that dumps some stats - made Callback thread safe using an AtomicBoolean - wrote Utils to be a little more efficient - and so on Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3932) several enhancements to the async container client sample app
[ https://issues.apache.org/jira/browse/GERONIMO-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3932: -- Attachment: GERONIMO-3932.patch several enhancements to the async container client sample app - Key: GERONIMO-3932 URL: https://issues.apache.org/jira/browse/GERONIMO-3932 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.2 Reporter: Sangjin Lee Assignee: Jason Warner Priority: Minor Attachments: GERONIMO-3932.patch I made a few enhancements and bug fixes in the async client sample app. The changes include - calls HttpServletResponse.flushBuffer() to address a Tomcat NPE - added a dump query that dumps some stats - made Callback thread safe using an AtomicBoolean - wrote Utils to be a little more efficient - and so on Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3906) start-server uses hard-coded credentials that cannot be overridden
[ https://issues.apache.org/jira/browse/GERONIMO-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3906. --- Resolution: Fixed Modified the gshell command to accept username, password, and rmi naming port as command line options. Changes committed to trunk (revision 638944) and branches/2.1 (revision 638948). start-server uses hard-coded credentials that cannot be overridden -- Key: GERONIMO-3906 URL: https://issues.apache.org/jira/browse/GERONIMO-3906 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3902) start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell
[ https://issues.apache.org/jira/browse/GERONIMO-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3902. Resolution: Fixed start-server, default.groovy in etc/rc.d overrides -Xmx value when starting server using gshell --- Key: GERONIMO-3902 URL: https://issues.apache.org/jira/browse/GERONIMO-3902 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jason Warner Assignee: Joe Bohn Fix For: 2.1.1, 2.2 Attachments: Geronimo-3902-IncludesStartClient.patch, Geronimo-3902.patch The start-server, default.groovy file is included in etc/rc.d directory and contains a command to set the max heap size for geronimo when starting through gshell. This file overrides any max heap size values that are set via the command line causing issues when starting the server with non-default max heap values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3916) proxy connection does not capture the successful connection events
[ https://issues.apache.org/jira/browse/GERONIMO-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-3916. Resolution: Fixed Committed revision 638972. proxy connection does not capture the successful connection events -- Key: GERONIMO-3916 URL: https://issues.apache.org/jira/browse/GERONIMO-3916 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Assignee: Rick McGuire Priority: Minor Attachments: GERONIMO-3916.patch AsyncHttpClient emits monitoring events, and CONNECTION_SUCCESSFUL is emitted when we have a connected session. However, the CONNECTION_SUCCESSFUL event is not emitted for a proxied connection. See ProxyFutureListener.operationComplete()... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
timeout for geronimo/start-server
The geronimo/start-server command has a timeout option: -t (--timeout) N Specify the timeout for the server process in seconds. What is this timeout for exactly? The time in which the server must start up in (that is, the command fails if the server does not start in X seconds) or the time for long to run the server (that is, run the server for x seconds, and after x seconds shut it down)? Jarek
[jira] Updated: (GERONIMO-3392) CA Helper App - Unable to find HTTPS Connector configured for ClientAuth
[ https://issues.apache.org/jira/browse/GERONIMO-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-3392: -- Affects Version/s: 2.2 2.0.x Fix Version/s: (was: 2.1.1) 2.2 Assignee: (was: Vamsavardhana Reddy) CA Helper App - Unable to find HTTPS Connector configured for ClientAuth Key: GERONIMO-3392 URL: https://issues.apache.org/jira/browse/GERONIMO-3392 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0, 2.0.x, 2.2 Environment: G 2.0 Tomcat Reporter: Vamsavardhana Reddy Fix For: 2.0.x, 2.2 The CA Helper application is unable to find HTTPS Connector configured for ClientAuth. This is because the new Tomcat HTTPS Connector GBeans no longer implement TomcatSecureConnector and so AbstractNameQuery(SecureConnector.class.getName()) will not help fetch Tomcat SSL Connectors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3879) Web Access Log Viewer problems in multiple server instances scenario
[ https://issues.apache.org/jira/browse/GERONIMO-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy closed GERONIMO-3879. - Resolution: Fixed Completed: At revision: 638985 in trunk. Completed: At revision: 638994 in branches\2.1 Web Access Log Viewer problems in multiple server instances scenario Key: GERONIMO-3879 URL: https://issues.apache.org/jira/browse/GERONIMO-3879 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.2 Environment: G 2.1 Tomcat Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.1.1, 2.2 I am noticing this with G 2.1 Tomcat. May be applicable to G 2.1 Jetty distribution too. I have created a second server instance with name *i1* by copying the var directory to g_home/*i1*. While tomcat is logging to g_home/*i1*/var/catalina/logs, Web Access Log Viewer for this instance is still displaying log entries from the base server (i.e. from g_home/var/catalina/logs)!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 638952
Geronimo Revision: 638952 built with tests included See the full build-1400.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080319/build-1400.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/2.1/20080319 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 35 minutes 1 second [INFO] Finished at: Wed Mar 19 15:11:16 EDT 2008 [INFO] Final Memory: 306M/1014M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080319/logs-1400-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080319/logs-1400-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.783 sec FAILURE! Samples: branches/2.1 = Log: http://geronimo.apache.org/maven/server/binaries/2.1/20080319/samples-1400.log Build status: FAILED
[jira] Updated: (GSHELL-101) Implement command context
[ https://issues.apache.org/jira/browse/GSHELL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GSHELL-101: Summary: Implement command context (was: Inplement command context) Implement command context - Key: GSHELL-101 URL: https://issues.apache.org/jira/browse/GSHELL-101 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support - CLP Affects Versions: 1.0-alpha-2, 1.0-alpha-3 Reporter: Jason Warner Assignee: Jason Warner Fix For: 1.0-alpha-2, 1.0-alpha-3 Gshell current lacks the ability to change the context from which a command is run. All commands default to running from a root directory. To be able to launch a command without fully qualifying (i.e; /bsf/script), the command search path must be used. It would be nice if we could also changed the context such that we can run any bsf command (or other command group commands) without having to modify the command search path. This will also allow us to use relative command paths (../ and ./). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-23) Command pipe-lines
[
https://issues.apache.org/jira/browse/GSHELL-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580662#action_12580662
]
Jason Dillon commented on GSHELL-23:
Cool
Command pipe-lines
--
Key: GSHELL-23
URL: https://issues.apache.org/jira/browse/GSHELL-23
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Core, Parser
Reporter: Jason Dillon
Assignee: Erik B. Craig
Fix For: 1.0-alpha-3
Add support for piping the output of one command into another, as in:
{noformat}
echo hi | cat /tmp/foo
{noformat}
This should write hi to the /tmp/foo file.
Follow zsh style, allowing | to concat both stdout+stderr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: start-server command and default user credentials
The only data I was envisioning was a simple text status string, similar to what you get when you telnet to a sendmail port. --jason On Mar 19, 2008, at 1:55 AM, Donald Woods wrote: I like the more secure option of requiring a uid/pwd, than potential exposing unwanted data to attackers -Donald Jarek Gawor wrote: Anymore more thoughts on this issue? If not, I guess I'll just add options for specifying the username, password and port number as a temporary solution to get this fixed for the 2.1.1 release. Jarek On Mon, Mar 17, 2008 at 11:01 AM, Jarek Gawor [EMAIL PROTECTED] wrote: On Sat, Mar 15, 2008 at 12:28 AM, Jason Dillon [EMAIL PROTECTED] wrote: On Mar 15, 2008, at 12:34 AM, Donald Woods wrote: Jarek Gawor wrote: Jason, I thought TCK was using the maven plugin to start the server. I'm not proposing to change that. But even if start-server command is used by TCK, I don't think that alone should dictate how the command should behave. I'm thinking what happens if you start any command in the background in a regular shell or even use geronimo.sh run or The --background option is not intended to behave like a shells operator... and some daemons do fork right away and return while the child continues, but other more robust daemons fork, then wait for the child to become booted, then return, so that any error status can be returned to the invoking shell for handling. IMO this is how Geronimo should behave... Adding a --wait or --nowait option might be useful, though I'd really like to solve the username/passwd problem... I think we need any anonymous way to query the status... Whether to poll and how to poll are two separate issues to me. I agree that we do need a way to anonymously query the status but I don't think we need to query the status in the normal/default case in the first place. When executing a script we'll need to know the status of the server and polling will be necessary but when starting the server in foreground polling is unnecessary. Jarek
[jira] Assigned: (GERONIMO-3858) start-server.bat fails to start server if there is a space in the path
[ https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GERONIMO-3858: -- Assignee: Jason Dillon start-server.bat fails to start server if there is a space in the path -- Key: GERONIMO-3858 URL: https://issues.apache.org/jira/browse/GERONIMO-3858 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Environment: Windows XP Reporter: YunFeng Ma Assignee: Jason Dillon start-server.bat fails to start server if there is a space in the install path, but startup.bat works fine. Looks like it's an Ant bug. H:\myf\Apache Geronimo\binstart-server.bat --- constituent[0]: file:/H:/myf/Apache Geronimo/etc/ constituent[1]: file:/H:/myf/Apache Geronimo/lib/gshell/geronimo-commands-2.1-SN APSHOT.jar constituent[2]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant/1.7.0 /ant-1.7.0.jar constituent[3]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant-launc her/1.7.0/ant-launcher-1.7.0.jar constituent[4]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-cli/1.0-alpha-1-SNAPSHOT/gshell-cli-1.0-alpha-1-SNAPSHOT.jar constituent[5]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-embeddable/1.0-alpha-1-SNAPSHOT/gshell-embeddable-1.0-alpha-1-SNAPSHOT .jar constituent[6]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-client/1.0-alpha-1-SNAPSHOT/gshell-remote-client-1.0-alp ha-1-SNAPSHOT.jar constituent[7]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-common/1.0-alpha-1-SNAPSHOT/gshell-remote-common-1.0-alp ha-1-SNAPSHOT.jar constituent[8]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-server/1.0-alpha-1-SNAPSHOT/gshell-remote-server-1.0-alp ha-1-SNAPSHOT.jar constituent[9]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-whisper/1.0-alpha-1-SNAPSHOT/gshell-whisper-1.0-alpha-1-SNAPSHOT.jar constituent[10]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-co re/1.1.2/mina-core-1.1.2.jar constituent[11]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-fi lter-ssl/1.1.2/mina-filter-ssl-1.1.2.jar constituent[12]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/groovy/gro ovy-all/1.1-rc-1/groovy-all-1.1-rc-1.jar constituent[13]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/slf4j-log4j12 /1.4.3/slf4j-log4j12-1.4.3.jar constituent[14]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/jcl104-over-s lf4j/1.4.3/jcl104-over-slf4j-1.4.3.jar constituent[15]: file:/H:/myf/Apache Geronimo/lib/geronimo-kernel-2.1-SNAPSHOT.j ar constituent[16]: file:/H:/myf/Apache Geronimo/lib/log4j-1.2.14.jar constituent[17]: file:/H:/myf/Apache Geronimo/lib/cglib-nodep-2.1_3.jar constituent[18]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/spe cs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_ spec-1.0.jar constituent[19]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-cli/2.1-SNAPSHOT/geronimo-cli-2.1-SNAPSHOT.jar constituent[20]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-config/2.1-SNAPSHOT/geronimo-deploy-config-2.1-SNAPSHOT.jar constituent[21]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-jsr88/2.1-SNAPSHOT/geronimo-deploy-jsr88-2.1-SNAPSHOT.jar constituent[22]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-tool/2.1-SNAPSHOT/geronimo-deploy-tool-2.1-SNAPSHOT.jar constituent[23]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-system/2.1-SNAPSHOT/geronimo-system-2.1-SNAPSHOT.jar constituent[24]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-plugin/2.1-SNAPSHOT/geronimo-plugin-2.1-SNAPSHOT.jar constituent[25]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-common/2.1-SNAPSHOT/geronimo-common-2.1-SNAPSHOT.jar constituent[26]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar constituent[27]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-utils/1.4.1/plexus-utils-1.4.1.jar --- java.lang.IllegalArgumentException at java.net.URI.create(URI.java:842) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
[jira] Commented: (GERONIMO-3858) start-server.bat fails to start server if there is a space in the path
[ https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580667#action_12580667 ] Jason Dillon commented on GERONIMO-3858: I've already patched this bug in the groovy-maven-plugin bits, I'll see about getting it included into the server. start-server.bat fails to start server if there is a space in the path -- Key: GERONIMO-3858 URL: https://issues.apache.org/jira/browse/GERONIMO-3858 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Environment: Windows XP Reporter: YunFeng Ma Assignee: Jason Dillon start-server.bat fails to start server if there is a space in the install path, but startup.bat works fine. Looks like it's an Ant bug. H:\myf\Apache Geronimo\binstart-server.bat --- constituent[0]: file:/H:/myf/Apache Geronimo/etc/ constituent[1]: file:/H:/myf/Apache Geronimo/lib/gshell/geronimo-commands-2.1-SN APSHOT.jar constituent[2]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant/1.7.0 /ant-1.7.0.jar constituent[3]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant-launc her/1.7.0/ant-launcher-1.7.0.jar constituent[4]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-cli/1.0-alpha-1-SNAPSHOT/gshell-cli-1.0-alpha-1-SNAPSHOT.jar constituent[5]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-embeddable/1.0-alpha-1-SNAPSHOT/gshell-embeddable-1.0-alpha-1-SNAPSHOT .jar constituent[6]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-client/1.0-alpha-1-SNAPSHOT/gshell-remote-client-1.0-alp ha-1-SNAPSHOT.jar constituent[7]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-common/1.0-alpha-1-SNAPSHOT/gshell-remote-common-1.0-alp ha-1-SNAPSHOT.jar constituent[8]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-server/1.0-alpha-1-SNAPSHOT/gshell-remote-server-1.0-alp ha-1-SNAPSHOT.jar constituent[9]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-whisper/1.0-alpha-1-SNAPSHOT/gshell-whisper-1.0-alpha-1-SNAPSHOT.jar constituent[10]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-co re/1.1.2/mina-core-1.1.2.jar constituent[11]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-fi lter-ssl/1.1.2/mina-filter-ssl-1.1.2.jar constituent[12]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/groovy/gro ovy-all/1.1-rc-1/groovy-all-1.1-rc-1.jar constituent[13]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/slf4j-log4j12 /1.4.3/slf4j-log4j12-1.4.3.jar constituent[14]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/jcl104-over-s lf4j/1.4.3/jcl104-over-slf4j-1.4.3.jar constituent[15]: file:/H:/myf/Apache Geronimo/lib/geronimo-kernel-2.1-SNAPSHOT.j ar constituent[16]: file:/H:/myf/Apache Geronimo/lib/log4j-1.2.14.jar constituent[17]: file:/H:/myf/Apache Geronimo/lib/cglib-nodep-2.1_3.jar constituent[18]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/spe cs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_ spec-1.0.jar constituent[19]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-cli/2.1-SNAPSHOT/geronimo-cli-2.1-SNAPSHOT.jar constituent[20]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-config/2.1-SNAPSHOT/geronimo-deploy-config-2.1-SNAPSHOT.jar constituent[21]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-jsr88/2.1-SNAPSHOT/geronimo-deploy-jsr88-2.1-SNAPSHOT.jar constituent[22]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-tool/2.1-SNAPSHOT/geronimo-deploy-tool-2.1-SNAPSHOT.jar constituent[23]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-system/2.1-SNAPSHOT/geronimo-system-2.1-SNAPSHOT.jar constituent[24]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-plugin/2.1-SNAPSHOT/geronimo-plugin-2.1-SNAPSHOT.jar constituent[25]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-common/2.1-SNAPSHOT/geronimo-common-2.1-SNAPSHOT.jar constituent[26]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar constituent[27]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-utils/1.4.1/plexus-utils-1.4.1.jar ---
Re: timeout for geronimo/start-server
Its the time the server must have started up, when using the -- background option. --jason On Mar 20, 2008, at 1:58 AM, Jarek Gawor wrote: The geronimo/start-server command has a timeout option: -t (--timeout) N Specify the timeout for the server process in seconds. What is this timeout for exactly? The time in which the server must start up in (that is, the command fails if the server does not start in X seconds) or the time for long to run the server (that is, run the server for x seconds, and after x seconds shut it down)? Jarek
