[
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
[
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
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
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
[
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
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
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
[
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
[
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
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:
[
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
[
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
[
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
[
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
[
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
[
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
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
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
[
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
[
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
[
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
[
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
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
[
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:
[
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
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
[
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
[
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
--
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
[
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
[
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
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
32 matches
Mail list logo
