I am not using network of brokers.I have a scenario in which if my running
broker fails or get shutdown what is going to happen with the messages.Also
if broker shutdown where my application will send the message in order to
restore them once the borker will start again. Also how the restarted
On 1/2/07, garima015 [EMAIL PROTECTED] wrote:
I am not using network of brokers.I have a scenario in which if my running
broker fails or get shutdown what is going to happen with the messages.
If they are sent using persistent message delivery they will be on
disk / in the database and
[
https://issues.apache.org/activemq/browse/AMQCPP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-35.
Resolution: Fixed
Fixed in trunk
Added more unit testing on this so that we catch more on the
[
https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégoire A. updated SM-795:
---
Attachment: SM-795.patch
HTTP headers attached as properties may cause requests to fail
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461684
]
Shiva Kumar H R commented on GERONIMO-2577:
---
Hello Kaoru,
I started looking into this and could
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461686
]
Shiva Kumar H R commented on GERONIMO-2577:
---
Also edit line 70 of new-config.xml :-)
Thx,
Shiva
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMO-2577:
--
Attachment: new-config.xml
Geronimo cluster (Tomcat Version)cannot continue the
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMO-2577:
--
Attachment: geronimo-web-hostlevel.xml
Geronimo cluster (Tomcat Version)cannot
[
http://issues.apache.org/jira/browse/GERONIMO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-438:
-
Attachment: g-438-11x-option2.patch
Deployer.deploy arguments inconsistent
[
http://issues.apache.org/jira/browse/GERONIMO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461708
]
Vamsavardhana Reddy commented on GERONIMO-438:
--
g-438-11x-option2.patch:
Patch for branches\1.1 as
[
http://issues.apache.org/jira/browse/GERONIMO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461709
]
Vamsavardhana Reddy commented on GERONIMO-438:
--
To make sure that PackageBuilder.invokeDeployer() is
Aaron,
Can you look at the comments I posted to the JIRA and check if we can
conclude the hunt?
Thanks,
Vamsi
On 1/2/07, Vamsavardhana Reddy (JIRA) [EMAIL PROTECTED] wrote:
[
Multiple versions of org.codehaus.wadi.wadi-tribes listed in
server/trunk/pom.xml
-
Key: GERONIMO-2683
URL: http://issues.apache.org/jira/browse/GERONIMO-2683
Project:
[
http://issues.apache.org/jira/browse/GERONIMO-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2683:
---
Attachment: G2683-server-2.0.patch
Multiple versions of org.codehaus.wadi.wadi-tribes
Yes I think that is correct. Look at the other examples where I have
added those methods, does it contain the tag? If so, add it.
On Dec 20, 2006, at 1:05 PM, Shiva Kumar H R wrote:
Hi Sachin,
Need your help in a certain thing.
I have added a new section in Naming page to enable the users
Upgrade server trunk (2.0) to use the latest released geronimo-spec versions
Key: GERONIMO-2684
URL: http://issues.apache.org/jira/browse/GERONIMO-2684
Project: Geronimo
On Dec 31, 2006, at 7:25 AM, Glen Mazza wrote:
I'm not a team member (and am basically providing a filler answer
until you can get an immediate work suggestion), but I would scroll
through the JIRA list[1] (perhaps in the databases category) and
look for bugs you can fix.
Do you have
[
http://issues.apache.org/jira/browse/GERONIMO-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461736
]
Anita Kulshreshtha commented on GERONIMO-2683:
--
Maven quietly uses the first definition, but the
[
http://issues.apache.org/jira/browse/GERONIMO-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461738
]
Anita Kulshreshtha commented on GERONIMO-2675:
--
Fixed in branches/1.2 rev 491800
Fix geronimo
Anita,
I noticed you updated the Java EE 5.0 Report card to mark Java EE Mgmt
1.1 as available in 2.0-M1. Is the geronimo work complete for this
specification?
Chris, Is there any other required work that you were tracking before
marking this as complete on the roadmap?
Thanks
-Dave-
Dave,
The J2ee-management-1.1 (that's still the official name!) is
available in the same capacity as j2ee-management-1.0 is available in
1.2-beta. There are some minor bug fixes/enhancements pending. IIUC,
the work on providing proper Deployment Descriptor in the presence of
annotations will be
[
http://issues.apache.org/jira/browse/GERONIMO-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461746
]
Anita Kulshreshtha commented on GERONIMO-2683:
--
patch applied to trunk rev 491817, Thanks Donald!
[
http://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2455:
---
Attachment: mx4j-remote-3.0.2-bundle.jar
mx4j-jmx-3.0.2-bundle.jar
[
http://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2455:
---
Attachment: mx4j-tools-3.0.2-bundle.jar
Upgrade to new MX4J service release
[
http://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461755
]
Donald Woods commented on GERONIMO-2455:
Try the 4 attached jars, which I built from your jar contents at
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin Patel updated GERONIMODEVTOOLS-112:
--
Patch Info: (was: [Patch Available])
Loading deployment plan
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin Patel updated GERONIMODEVTOOLS-112:
--
Patch Info: [Patch Available]
Loading deployment plan editor on
You can create a settings.xml in the default user/.m2 directory to point
to an alternate local repo dir, like -
?xml version=1.0 encoding=UTF-8?
settings
localRepository${LOCAL_GERONIMO_M2_REPO}/localRepository
/settings
But the downside, is you're leaving it up to each developer to
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin Patel reassigned GERONIMODEVTOOLS-119:
-
Assignee: Sachin Patel
import simple hello.war results
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin Patel closed GERONIMODEVTOOLS-119.
-
Resolution: Fixed
Patch applied thanks!
import simple hello.war
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461764
]
Sachin Patel commented on GERONIMODEVTOOLS-126:
---
Changing the port doesn't change the port of
[
http://issues.apache.org/jira/browse/GERONIMO-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461768
]
Donald Woods commented on GERONIMO-1786:
G2637 was used to remove the peer transport setup from the JMS
[
http://issues.apache.org/jira/browse/GERONIMO-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved GERONIMO-2683.
Resolution: Fixed
Patch applied by Anita. Thanks.
Multiple versions of
Dave,
There are no other changes needed for J2EE Management for JEE 5
compliance except for providing a full deployment descriptor which
includes deployment annotations. IIUC this work should be done in our
JSR 88 - Java EE application deployment implementation. I spoke to Anita
regarding
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461784
]
Sachin Patel commented on GERONIMODEVTOOLS-123:
---
In the patch, on lines 187 and 198 why did
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461791
]
Sachin Patel commented on GERONIMODEVTOOLS-123:
---
Also, in each of your groups in the screen
database pool type emty in pool creation wizard - Jetty
---
Key: GERONIMO-2685
URL: http://issues.apache.org/jira/browse/GERONIMO-2685
Project: Geronimo
Issue Type: Bug
Security
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461793
]
Sachin Patel commented on GERONIMODEVTOOLS-123:
---
Another small thing... The name of the
[
http://issues.apache.org/jira/browse/GERONIMO-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461802
]
Paul McMahan commented on GERONIMO-2685:
looks like when configs/webconsole-jetty6 was moved from sandbox
[
http://issues.apache.org/jira/browse/GERONIMO-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461814
]
Jacek Laskowski commented on GERONIMO-2684:
---
If there're a patch for it, it'd surely be committed. Would
I am using NON PERSISTENT message delivery ...
Please suggest me something to avoid any loss of message
James.Strachan wrote:
On 1/2/07, garima015 [EMAIL PROTECTED] wrote:
I am not using network of brokers.I have a scenario in which if my
running
broker fails or get shutdown what is
[
http://issues.apache.org/jira/browse/GERONIMO-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461834
]
David Jencks commented on GERONIMO-1747:
HTTP extension methods are supported in jacc-1.1 which is
[
http://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461843
]
Aaron Mulder commented on GERONIMO-1930:
Right now you can't add new login module types to the console
database creation pool wizzard fails to deploy
--
Key: GERONIMO-2686
URL: http://issues.apache.org/jira/browse/GERONIMO-2686
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
You will need to switch to persistent messages to avoid any loss on
broker restart as mentioned below.
garima015 wrote:
I am using NON PERSISTENT message delivery ...
Please suggest me something to avoid any loss of message
James.Strachan wrote:
On 1/2/07, garima015 [EMAIL PROTECTED]
All default Subjects should be obtained by logging in to a realm, not
constructed explicitly
--
Key: GERONIMO-2687
URL: http://issues.apache.org/jira/browse/GERONIMO-2687
Hey All, back and catching up.
As I mentioned in the first specs vote that I proposed I've done the
work to fix some of our spec jars so they are compliant and would
like us to start releasing them and removing snapshot references from
our builds. I've since started abbreviating that to
You don't need to add this to settings.xml, you can simply:
mvn -Dmaven.repo.local=some/path
But you are right, to make this work, we need those native scripts to
bootstrap the build again and set the correct value for the repo.
--jason
On Jan 2, 2007, at 8:32 AM, Donald Woods wrote:
no-pool and xa-transaction with no caching result in connections being closed
before the tx ends.
-
Key: GERONIMO-2688
URL:
On Jan 2, 2007, at 5:19 PM, David Blevins wrote:
Hey All, back and catching up.
As I mentioned in the first specs vote that I proposed I've done
the work to fix some of our spec jars so they are compliant and
would like us to start releasing them and removing snapshot
references from
Hi David, thanks for kicking off this discussion and I agree with most of your
steps
below. However, since it seems that annotations are now pervasive in many of
the JSR
specifications (i.e., JSRs 77, 88, 175, 181, 220, 250 and probably even more
that I
personally haven't uncovered) it seems
Numerous problems have been reported with building 'assemblies' and
with the server resulting from these assemblies. Here are some of them:
Oct 19 -
http://www.nabble.com/Assembly-is-caching-old-junk-p6907158.html
Oct 31 -
http://www.nabble.com/More-car-maven-plugin-changes...-p7107517.html
On Jan 2, 2007, at 8:11 PM, anita kulshreshtha wrote:
After each report an attempt was made to fix the car plugin! These
fixes tried to treat the symptoms and not the root cause of the
problem.
No, there were some real problems with the car plugin, probably a few
more too.
I believe the
ActiveMQ Queue management- How to kill a queue?
---
Key: AMQ-1114
URL: https://issues.apache.org/activemq/browse/AMQ-1114
Project: ActiveMQ
Issue Type: Bug
Components: Broker, JCA
Servicemix NOT passing Custom defined Exceptions
Key: SM-799
URL: https://issues.apache.org/activemq/browse/SM-799
Project: ServiceMix
Issue Type: Bug
Components:
[
https://issues.apache.org/activemq/browse/SM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37813
]
Guillaume Nodet commented on SM-799:
Could you please detail the step to reproduce the problem and post the stack
56 matches
Mail list logo
