Re: ActiveMQ POM
On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
I think the main problem is that users will never
download newest versions. IMHO, this would be a bad
idea.
yeah.
On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote:
Thanks Fritz!
I knew there had to be a reason that I was just not aware of. What do
you think would be the downsides of not using the special SNAPSHOT
handling that maven provides? What if we tagged our SNAPSHOT builds
with something like like DEVELOPMENT instead of SNAPSHOT.
I'm guessing that problem would go away, but what other ones would we get?
On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
This is also my experience.
If we just use the real version 4.2-SNAPSHOT
for example, it should also work and maven
should be able to change (*nearly*) all these
occurrences when using the release plugin.
I say nearly, because in ServiceMix, there are
some edge cases where this fail (when including
the version in files other than pom.xml like artifacts
resources for example).
On 11/14/06, Fritz Oconer [EMAIL PROTECTED] wrote:
Hi,
I added ${activemq-version} instead of ${project.version} basically as a
workaround for build failures due to differences in timestamp. If we use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same
timestamp
as the parent. This becomes an issue when nightly-build deploy fails after
some of the modules have been deployed causing some activemq modules to
have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
Thanks for the tip Guillaume! Fix applied! On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I think the problem comes from the fact that the xsds are not generated in their default locations (target/xbean). Changing the configuration to: schematarget/xbean/activemq.xsd/schema should work. On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: Hi Endre, Thanks for the feedback but I don't agree that this issue should hold up the release. I'm sure we can fix this in a subsequent bug fix release. BTW, if you submit a patch with the fix for this it would make getting the fix into the next release much easier :) Regards, Hiram On 11/14/06, Endre Stølsvik [EMAIL PROTECTED] wrote: Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my useless -1: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat spring.schemas http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Two things: a) where is the xsd supposed to lay? (The _proper_ URL? Not this one mentioned on this page: http://incubator.apache.org/activemq/spring-support.html http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; b) The idea behind spring.schemas is, AFAIK, that the spring-magic should kick in, and instead of going online to fetch the xsd, it will find it in the classpath. Given that the file:/Users/chirino/blahblah most definately isn't present on my machine, this will, AFAIK, result in every startup of ActiveMQ with spring-xbeans integration online access (which probably explains why all elements of the namespace-loading goes lightning, except from the activeMQ one, which stalls for some seconds). In comparison, here's the spring.schemas for spring-2.0.jar actually bundled with this ActiveMQ 4.1.0 RC2: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$ cat spring.schemas http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd Note two things: the http-URL mentioned actually return the file, but in addition, the resource specified is a classpath-resource, which exists: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$ ls -la spring-* -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd -rw-r--r-- 1 endre endre 1999 2006-09-09 23:53 spring-tool-2.0.xsd -rw-r--r-- 1 endre endre 5132 2006-09-09 23:53 spring-util-2.0.xsd This is bug AMQ-1016: https://issues.apache.org/activemq/browse/AMQ-1016 I think this should be fixed before 4.1.0 is released. Kind regards, Endre. -- Regards, Hiram Blog: http://hiramchirino.com -- Cheers, Guillaume Nodet -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Resolved: (AMQ-1016) 4.1 RC1: META-INF/spring.schemas refers to building user file:/Users/chirino/
[ https://issues.apache.org/activemq/browse/AMQ-1016?page=all ] Hiram Chirino resolved AMQ-1016. Fix Version/s: 4.1.1 4.2.0 Resolution: Fixed Assignee: Hiram Chirino Fix applied in trunk rev 474872 and in 4.1 branch rev 474876 4.1 RC1: META-INF/spring.schemas refers to building user file:/Users/chirino/ --- Key: AMQ-1016 URL: https://issues.apache.org/activemq/browse/AMQ-1016 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1.0 Environment: n/a Reporter: Endre Stølsvik Assigned To: Hiram Chirino Priority: Minor Fix For: 4.1.1, 4.2.0 Referring to the 4.1 RC1 posted by Hiram Chirino Oct 06, here: http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974 The META-INF file spring.schemas have the single line. http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Notice file:/ and Users/chirino. Referring to org.springframework.beans.factory.xml.PluggableSchemaResolver's javadoc: schema-location should also be a schema file in the classpath, and that no-one can tell what structure I will have on my fs, this must be wrong. In addition, I most probably won't have a user name chirino. PS: In addition, the doc at http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html refers as such: xmlns:amq=http://activemq.org/config/1.0; .. and .. xsi:schemaLocation=http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; Wouldn't it be nice if this was put at a better place than such a snapshot-build URI? It could be put where it will reside when 4.1 actually is out, w/o anyone being to angry about changes during the finalization period, I personally believe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1036) web-console broken (queue browsing).
[ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]
Hiram Chirino updated AMQ-1036:
---
Fix Version/s: 4.1.1
4.2.0
(was: 4.1.0)
web-console broken (queue browsing).
Key: AMQ-1036
URL: https://issues.apache.org/activemq/browse/AMQ-1036
Project: ActiveMQ
Issue Type: Bug
Affects Versions: incubation
Reporter: Dave Syer
Assigned To: Adrian Co
Fix For: 4.2.0, 4.1.1
I managed to build and launch the web-console from svn, but the queue
browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size}
that do not exist. When I hacked queue.jsp to remove references to those
properties I got another error on trying to purge a queue:
RequestURI=/activemq-web-console/purgeDestination.action
Caused by:
java.lang.IllegalArgumentException: Target bean must not be null
at org.springframework.util.Assert.notNull(Assert.java:113)
at
org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
at
org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
at
org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
at
org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
at
org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
at
org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
at
org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
at
org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-910) backoffMultiplier should be a double value
[ https://issues.apache.org/activemq/browse/AMQ-910?page=all ] Hiram Chirino updated AMQ-910: -- Fix Version/s: 4.2.0 (was: 4.0.1) backoffMultiplier should be a double value -- Key: AMQ-910 URL: https://issues.apache.org/activemq/browse/AMQ-910 Project: ActiveMQ Issue Type: Improvement Reporter: Daniel Aioanei Fix For: 4.2.0 Having org.apache.activemq.ra.ActiveMQActivationSpec.backOffMultiplier as a short value is too limiting. I think a double value would be more appropriate. For instance, I'd like to set it to about 1.1 but that's not possible at the time being. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[ https://issues.apache.org/activemq/browse/AMQ-734?page=all ] Hiram Chirino updated AMQ-734: -- Fix Version/s: 4.1.1 (was: 4.0.1) I've got a feeling that this was related to the timing issues addressed in issue: https://issues.apache.org/activemq/browse/AMQ-1044 which is now fixed. Could one you guys retest against a source build from the 4.1 branch and let me know if it resolves this issue? Network connections do not reconnect when using static: with failover=true -- Key: AMQ-734 URL: https://issues.apache.org/activemq/browse/AMQ-734 Project: ActiveMQ Issue Type: Bug Components: Connector Affects Versions: 4.0 Environment: winxp java1.5.6 Reporter: tao Assigned To: Hiram Chirino Priority: Critical Fix For: 4.2.0, 4.1.1 If I pull out RJ45 port from net card ,waiting a time ,then put RJ45 port net card .Network is resume.Other computer always throw errors and net channel can't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1046) Consolidate the ActiveMQ admin scripts to a single command line script
[ https://issues.apache.org/activemq/browse/AMQ-1046?page=all ] Hiram Chirino reassigned AMQ-1046: -- Assignee: Adrian Co (was: Fritz Oconer) Consolidate the ActiveMQ admin scripts to a single command line script -- Key: AMQ-1046 URL: https://issues.apache.org/activemq/browse/AMQ-1046 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Adrian Co Fix For: 4.2.0 Right now we have serveral command line scripts in the ActiveMQ bin directory of the binary distribution. They are used for admin purposes. They are less than ideal because some of them have very generic names and might clash with existing commands if the activemq bin directory is added to the PATH of a unix system. I think it would be more idea if we consolidated all the command so that are executed using just 1 script. Something like: $ activemq-admin list $ activemq-admin stat $ activemq-admin browse etc. etc. etc. This way only 2 executable scripts are added to the path: (1) activemq - the binary that starts up ActiveMQ (2) activemq-admin - the binary used to manage the ActiveMQ instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
[ https://issues.apache.org/activemq/browse/AMQ-1047?page=all ] Hiram Chirino updated AMQ-1047: --- Assignee: Adrian Co (was: Hiram Chirino) ActiveMQ admin scripts should hide JMX from the user as much as possible. - Key: AMQ-1047 URL: https://issues.apache.org/activemq/browse/AMQ-1047 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Adrian Co Fix For: 4.2.0 The fact that JMX is being used to access the management functions of the Broker should be hidden from the user of the admin scripts as much as possible. For example, users should not be displayed objects names of a list of subscriptions. They should be shown the subscription ids of the subscriptions. The same goes for connections and so forth. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
ActiveMQ admin scripts should hide JMX from the user as much as possible. - Key: AMQ-1047 URL: https://issues.apache.org/activemq/browse/AMQ-1047 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0 The fact that JMX is being used to access the management functions of the Broker should be hidden from the user of the admin scripts as much as possible. For example, users should not be displayed objects names of a list of subscriptions. They should be shown the subscription ids of the subscriptions. The same goes for connections and so forth. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
[I intially sent with wrong From: - sorry if double-posting] Guillaume Nodet wrote: I think the problem comes from the fact that the xsds are not generated in their default locations (target/xbean). Changing the configuration to: schematarget/xbean/activemq.xsd/schema should work. At that point they'll magically jump into some good place in the jar, being acessible in the classpath, and the spring.schemas will contain the right info? What about the actual, physical URL I mentioned? Shouldn't the xsd also actually be accessible from some nice-looking URL somewhere @ apache.com? And finally, I wonder why spring's own spring.schema fila have /actual/ URLs as reference? Spring's spring.schema file have lines like this: http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd See, given that spring's namespace-definitions look like this: http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd; While ActiveMQ's look like this: http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; One would deduce that the URL which is matched in the spring.schemas are the _latter_, not the _former_ of these URLS. PS: Just to do a fast check, I ripped the network cable out of my machine, and tried to start my application with current snapshot (where ActiveMQ is configured as suggested on http://incubator.apache.org/activemq/spring-support.html). This was the result (with full stop as result): This is fine: - 563 [main] DEBUG org.springframework.beans.factory.xml.ResourceEntityResolver - Attempting to resolve XML Schema [http://www.springframework.org/schema/aop/spring-aop-2.0.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver] This isn't: -- 578 [main] DEBUG org.springframework.beans.factory.xml.ResourceEntityResolver - Attempting to resolve XML Schema [http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver] 766 [main] WARN org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) [snip - any element using amq wouldn't parse after this, obviously..] I then inserted it again, restart, and it went fine. Kind regards, Endre
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
+1 -dain On Nov 13, 2006, at 9:07 PM, Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2- incubating-repository/org/apache/activemq/apache-activemq/4.1.0- incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my +1 -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Created: (AMQ-1049) SimpleAuthenticationBroker and AbstractConnection allow messages from a Producer that fails logon
SimpleAuthenticationBroker and AbstractConnection allow messages from a
Producer that fails logon
-
Key: AMQ-1049
URL: https://issues.apache.org/activemq/browse/AMQ-1049
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0, 4.0.1
Environment: The OS is Windows XP. The producer is running in one JVM
loaded via JNI invokation with an embedded broker and a DemandForwardingBridge
that
is connecting to the remote broker via tcp://127.0.0.1:61616. The consumer
and the BrokerService are running on the same machine but in another JVM also
loaded via JNI invokation but communicating with each other via
vm://localhost.
Reporter: Chris Hofstaedter
I was trying to set up a SimpleAuthenticationBroker programatically rather than
through the xml. I've tried with 4.0.1 and 4.1. The symptom was that,
although the broker is set as an intercepter and it detects a bad password and
emits a SecurityException, the producer is still allowed to produce messages.
I can see the producer get the bad login indication through the following log
message:
WARN org.apache.activemq.network.DemandForwardingBridge - Unexpected remote
command: ConnectionError {commandId = 2, responseRequired = false, connectionId
= null, exception = java.lang.SecurityException: User name or password is
invalid.}
But then, the next thing I know, my consumers, that have successfully logged
in, start receiving messages from this very same producer.
After some investigation, I've been able to get the behavior I want, but I had
to modify AbstractConnection.java to do it. I dont know if my modifications
are appropriate, so could someone take a look and let me know whether this is a
desirable change or not?
Specifically, I added an additional catch block after line 202 of
AbstractConnection and before the catch(Throwable). The new code is:
catch ( SecurityException e1)
{
ConnectionError ce = new ConnectionError();
ce.setException(e1);
dispatchSync(ce);
try
{
this.stop();
}
catch (Exception e2)
{
serviceLog.error(Unable to stop the connection after the
SecurityException: + e2);
}
Notice the dispatchSync versus dispatchAsync - I did this to ensure that the
client was informed off the security violation before the connection is stopped.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-644) create Java Service Wrapper for ActiveMQ
[ https://issues.apache.org/activemq/browse/AMQ-644?page=all ] Joseph Dennis Gapuz resolved AMQ-644. - Resolution: Fixed create Java Service Wrapper for ActiveMQ Key: AMQ-644 URL: https://issues.apache.org/activemq/browse/AMQ-644 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Assigned To: Joseph Dennis Gapuz Priority: Minor Fix For: 4.2.0 Attachments: wrapper.conf http://wrapper.tanukisoftware.org/doc/english/introduction.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ POM
Hi,
I think the downside here is that it will loose reference to previous
builds. Since development will not change to timestamp, then deploy will
just overwrite the existing artifacts.
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Wednesday, November 15, 2006 12:52 AM
Subject: Re: ActiveMQ POM
Thanks Fritz!
I knew there had to be a reason that I was just not aware of. What do
you think would be the downsides of not using the special SNAPSHOT
handling that maven provides? What if we tagged our SNAPSHOT builds
with something like like DEVELOPMENT instead of SNAPSHOT.
I'm guessing that problem would go away, but what other ones would we get?
On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
This is also my experience.
If we just use the real version 4.2-SNAPSHOT
for example, it should also work and maven
should be able to change (*nearly*) all these
occurrences when using the release plugin.
I say nearly, because in ServiceMix, there are
some edge cases where this fail (when including
the version in files other than pom.xml like artifacts
resources for example).
On 11/14/06, Fritz Oconer [EMAIL PROTECTED] wrote:
Hi,
I added ${activemq-version} instead of ${project.version} basically as
a
workaround for build failures due to differences in timestamp. If we
use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same
timestamp
as the parent. This becomes an issue when nightly-build deploy fails
after
some of the modules have been deployed causing some activemq modules to
have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always
deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
--
Regards,
Hiram
Blog: http://hiramchirino.com
[jira] Commented: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37445 ] Guillaume Nodet commented on SM-745: Maybe one way would be to just publish a message to a topic when a node is started. (which is what ActiveMQ does actually). The problem is mainly to discover failed nodes (and this is the main reason to use ActiveMQ advisories iirc). I was also thinking of making the jms / jca flows inherit a common base classes, as there is some commong logic in both. Allow usage of other JMS providers than ActiveMQ Key: SM-745 URL: https://issues.apache.org/activemq/browse/SM-745 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0.1 Reporter: Christian Schneider Fix For: 3.0.1 Attachments: jmsflow.patch, jmsflow.patch, jmsflow2.patch, jmsflow3.patch JMSFlow and JCA flow are too tightly bound to ActiveMQ. Instead of ActiveMQ specific classes jms Interfaces should be used where possible. I have attached a patch that replaces ActiveMQConnection and ActiveMQConnectionFactory by the jms equivalents. There is one possible issue with my patch. The getConnectionFactory now returns a ConnectionFactory instead of a ActiveMQConnectionFactory. I don´t know if any other part of the sources depends on the specific class. My patch is of course only the first step. The next could be having a specific subclass JMSFlowActiveMQ that does all stuff that is ActiveMQ specific. I will deliver a second patch for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-739) wsdl for pojos exported by jsr181 endpoint is missing complextypes from other namespaces than the service itself
[
https://issues.apache.org/activemq/browse/SM-739?page=comments#action_37446 ]
Guillaume Nodet commented on SM-739:
Could you please provide a patch with the needed classes in the test.model
package ?
I'd like to take a look at it.
wsdl for pojos exported by jsr181 endpoint is missing complextypes from other
namespaces than the service itself
Key: SM-739
URL: https://issues.apache.org/activemq/browse/SM-739
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jsr181
Affects Versions: 3.0
Reporter: Christian Schneider
Attachments: complextypetestpatch.txt, jsr181wsdlproblem..zip
I am exporting a pojo Service in namespace http://test1 that uses a Class
from namespace http://test2 as a jsr181 endpoint.
The wsdl I get from jconsole for the endpoint does not include the definition
of the Complextype Person from http://test2.
If you put the Person class in the package test1 the wsdl looks fine. The
problem does not happen when using xfire without servicemix.
Thanks to Ken Berthelot for reporting the problem on the mailing list.
http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-users/200611.mbox/browser
---
My xbean.xml
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://xbean.org/schemas/spring/1.0;
xmlns:jsr181=http://servicemix.apache.org/jsr181/1.0;
classpath
location./location
/classpath
jsr181:endpoint
pojoClass=test1.PersonServiceImpl
serviceInterface=test1.PersonService
style=wrapped
/jsr181:endpoint
/beans
---
My Classes
package test1;
import test2.Person;
public interface PersonService {
public abstract void testPerson(Person person);
}
package test1;
import test2.Person;
public class PersonServiceImpl implements PersonService {
/* (non-Javadoc)
* @see test1.PersonService#testPerson(test2.Person)
*/
public void testPerson(Person person) {
}
}
package test2;
public class Person {
String name;
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
The wsdl
?xml version=1.0 encoding=UTF-8?wsdl:definitions
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:ns1=http://test2;
xmlns:soap11=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:soap12=http://www.w3.org/2003/05/soap-envelope;
xmlns:soapenc11=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soapenc12=http://www.w3.org/2003/05/soap-encoding;
xmlns:tns=http://test1;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; targetNamespace=http://test1;
wsdl:types
xsd:schema attributeFormDefault=qualified
elementFormDefault=qualified targetNamespace=http://test1;
xsd:element name=testPerson
xsd:complexType
xsd:sequence
xsd:element maxOccurs=1 minOccurs=1 name=in0 nillable=true
type=ns1:Person/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=testPersonResponse
xsd:complexType/
/xsd:element
/xsd:schema
/wsdl:types
wsdl:message name=testPersonResponse
wsdl:part element=tns:testPersonResponse name=parameters/
/wsdl:message
wsdl:message name=testPersonRequest
wsdl:part element=tns:testPerson name=parameters/
/wsdl:message
wsdl:portType name=PersonServicePortType
wsdl:operation name=testPerson
wsdl:input message=tns:testPersonRequest name=testPersonRequest/
wsdl:output message=tns:testPersonResponse
name=testPersonResponse/
/wsdl:operation
/wsdl:portType
/wsdl:definitions
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-741) Upgrade commons-logging to 1.1 and log4j to 1.2.13 to support the log4j TRACE level
[ https://issues.apache.org/activemq/browse/SM-741?page=all ] Guillaume Nodet resolved SM-741. Resolution: Fixed Author: gnodet Date: Thu Nov 9 11:03:19 2006 New Revision: 473028 URL: http://svn.apache.org/viewvc?view=revrev=473028 Log: SM-741: Upgrade commons-logging to 1.1 and log4j to 1.2.13 Modified: incubator/servicemix/trunk/pom.xml Upgrade commons-logging to 1.1 and log4j to 1.2.13 to support the log4j TRACE level --- Key: SM-741 URL: https://issues.apache.org/activemq/browse/SM-741 Project: ServiceMix Issue Type: Task Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
unsubscribe
This message is intended only for the designated recipient(s). It may contain confidential or proprietary information. If you are not a designated recipient, you may not review, copy or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Thank you.
RE: [VOTE] Release ServiceMix 3.0.1
+1 from me -Original Message- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Wednesday, 15 November 2006 2:00 AM To: servicemix-dev@geronimo.apache.org Subject: [VOTE] Release ServiceMix 3.0.1 The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix /apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet
Re: Qustion about Broker!
I have solved the problem , thank you for your help! -- View this message in context: http://www.nabble.com/Qustion-about-%22Broker%22%21-tf2619683.html#a7333106 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
+1 :-) --jason On Nov 13, 2006, at 9:07 PM, Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2- incubating-repository/org/apache/activemq/apache-activemq/4.1.0- incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my +1 -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Assigned: (GERONIMO-1868) Calculate /console prefix dynamically for SVG, etc.
[ http://issues.apache.org/jira/browse/GERONIMO-1868?page=all ] Christopher M. Cardona reassigned GERONIMO-1868: Assignee: Christopher M. Cardona Calculate /console prefix dynamically for SVG, etc. --- Key: GERONIMO-1868 URL: http://issues.apache.org/jira/browse/GERONIMO-1868 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Reporter: Aaron Mulder Assigned To: Christopher M. Cardona Fix For: 1.2 The path to the console is hardcoded in svrInfoNormal.jsp and car/index.jsp right now. There's a method somewhere to calculate this (PortletManager?) and we should use it or something equivalent. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2552) Remove SVG usage from Admin Console
[ http://issues.apache.org/jira/browse/GERONIMO-2552?page=all ] Christopher M. Cardona reassigned GERONIMO-2552: Assignee: Christopher M. Cardona Remove SVG usage from Admin Console --- Key: GERONIMO-2552 URL: http://issues.apache.org/jira/browse/GERONIMO-2552 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.x Environment: Windows Reporter: Donald Woods Assigned To: Christopher M. Cardona Priority: Minor Fix For: 1.x Adobe is ending support for their SVG Viewer for Windows on January 1, 2008 and it is not supported in Windows Vista - http://www.adobe.com/svg/pdfs/ASV_EOL_FAQ.pdf Looking over the following site - http://wiki.svg.org/Viewer_Implementations there doesn't seem to be any free SVG Viewers available for Windows anymore. Requiring Firefox or Opera browsers should not be an option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1701) Improve the EJB Server portlet
[ http://issues.apache.org/jira/browse/GERONIMO-1701?page=all ] Christopher M. Cardona reassigned GERONIMO-1701: Assignee: Christopher M. Cardona Improve the EJB Server portlet -- Key: GERONIMO-1701 URL: http://issues.apache.org/jira/browse/GERONIMO-1701 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, OpenEJB Affects Versions: 1.1, 1.2 Reporter: Christopher M. Cardona Assigned To: Christopher M. Cardona Attachments: ejbMgrPortlet-G.patch, ejbmgrportlet-G1.1.1.patch, ejbmgrportlet-openejb-G1.1.1.patch, ejbMgrPortlet-OpenEJB.patch, ejbMgrPortlet-Snapshot.zip, viewEJBModules.jpg Improve the EJB Server portlet to do the ff.: 1. View a list of deployed EJB modules in the EJB server including basic statistics of the different EJB types. 2. View a list of deployed EJBs of an EJB module including basic statistics of the different EJB types. 3. View the deployment descriptor of an EJB module. 4. View a specific EJB to get basic configuration info Note: This portlet can still be enhanced to do other stuff. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1559) Console displays the incorrect locale
[ http://issues.apache.org/jira/browse/GERONIMO-1559?page=all ] Christopher M. Cardona reassigned GERONIMO-1559: Assignee: Christopher M. Cardona Console displays the incorrect locale - Key: GERONIMO-1559 URL: http://issues.apache.org/jira/browse/GERONIMO-1559 Project: Geronimo Issue Type: Wish Security Level: public(Regular issues) Components: console Affects Versions: 1.0 Environment: WinXP SP2 Reporter: Mihael Sedmak Assigned To: Christopher M. Cardona When listing the System Property values for the Server JVM, under the User section, the console displays user.timezone = Europe/Belgrade which is incorrect. The timezone on the machine which runs Geronimo is set to Sarajevo, Skopje, Warsaw, Zagreb -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-891) Improve the Java Mail portlet
[ http://issues.apache.org/jira/browse/GERONIMO-891?page=all ] Christopher M. Cardona reassigned GERONIMO-891: --- Assignee: Christopher M. Cardona Improve the Java Mail portlet - Key: GERONIMO-891 URL: http://issues.apache.org/jira/browse/GERONIMO-891 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Reporter: Chris Cardona Assigned To: Christopher M. Cardona Fix For: 1.2 Attachments: mailportlet-rev-348271.patch, mailportlet.patch Update and improve the Java Mail portlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-475) Deployment tool barfs with ArrayIndexOutOfBoundsException
[ http://issues.apache.org/jira/browse/GERONIMO-475?page=all ] Vamsavardhana Reddy closed GERONIMO-475. Deployment tool barfs with ArrayIndexOutOfBoundsException - Key: GERONIMO-475 URL: http://issues.apache.org/jira/browse/GERONIMO-475 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M3 Reporter: Hiram Chirino Assigned To: Aaron Mulder Fix For: 1.0-M4 Ran: java -jar bin\deployer.jar --user system --password list-modules Got: Exception in thread main java.lang.ArrayIndexOutOfBoundsException: 3 at org.apache.geronimo.deployment.cli.ServerConnection.init(ServerConnection.java:102) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:109) at org.apache.geronimo.deployment.cli.DeployTool.main(DeployTool.java:252) I know it's an invalid command, but the tool should report a better error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ POM
This is also my experience.
If we just use the real version 4.2-SNAPSHOT
for example, it should also work and maven
should be able to change (*nearly*) all these
occurrences when using the release plugin.
I say nearly, because in ServiceMix, there are
some edge cases where this fail (when including
the version in files other than pom.xml like artifacts
resources for example).
On 11/14/06, Fritz Oconer [EMAIL PROTECTED] wrote:
Hi,
I added ${activemq-version} instead of ${project.version} basically as a
workaround for build failures due to differences in timestamp. If we use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same timestamp
as the parent. This becomes an issue when nightly-build deploy fails after
some of the modules have been deployed causing some activemq modules to have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
[jira] Updated: (GERONIMO-1580) Better error message for missing WSDL file for EJB web service
[ http://issues.apache.org/jira/browse/GERONIMO-1580?page=all ] Vamsavardhana Reddy updated GERONIMO-1580: -- Fix Version/s: 1.1.2 1.2 (was: 1.1.x) Assignee: Vamsavardhana Reddy Better error message for missing WSDL file for EJB web service -- Key: GERONIMO-1580 URL: http://issues.apache.org/jira/browse/GERONIMO-1580 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, webservices Affects Versions: 1.0 Reporter: Aaron Mulder Assigned To: Vamsavardhana Reddy Priority: Critical Fix For: 1.1.2, 1.2 Attachments: SchemaInfoBuilder.patch If your webservices.xml file for a stateless session bean web service refers to a WSDL file that is not there, the error produced is java.lang.RuntimeException: Could not open stream to wsdl file It would be better if it produced a DeploymentException with a message something like: webservices.xml file for EJB JAR points to non-existant WSDL file 'META-INF/foo.wsdl' for service 'MyEJBWebService' The stack trace is 10:56:24,259 ERROR [Deployer] Deployment failed due to java.lang.RuntimeException: Could not open stream to wsdl file at org.apache.geronimo.axis.builder.SchemaInfoBuilder$JarWSDLLocator.getBaseInputSource(SchemaInfoBuilder.java:652) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.readWsdl(SchemaInfoBuilder.java:555) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.init(SchemaInfoBuilder.java:141) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.init(SchemaInfoBuilder.java:125) at org.apache.geronimo.axis.builder.WSDescriptorParser.parseWebServiceDescriptor(WSDescriptorParser.java:312) at org.apache.geronimo.axis.builder.WSDescriptorParser.parseWebServiceDescriptor(WSDescriptorParser.java:379) at org.apache.geronimo.axis.builder.AxisBuilder.parseWebServiceDescriptor(AxisBuilder.java:106) at org.apache.geronimo.axis.builder.AxisBuilder$$FastClassByCGLIB$$16a52a9a.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.WebServiceBuilder$$EnhancerByCGLIB$$493cf3fa.parseWebServiceDescriptor(generated) at org.openejb.deployment.OpenEJBModuleBuilder.addGBeans(OpenEJBModuleBuilder.java:500) at org.openejb.deployment.OpenEJBModuleBuilder$$FastClassByCGLIB$$11bd7b20.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$4ca9e4d7.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:402) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at
[jira] Resolved: (GERONIMO-1580) Better error message for missing WSDL file for EJB web service
[ http://issues.apache.org/jira/browse/GERONIMO-1580?page=all ] Vamsavardhana Reddy resolved GERONIMO-1580. --- Resolution: Fixed Thanks Manu. Patch is applied in rev 474702 (branches\1.1) and 474704 (trunk). Please verify the fix and close the JIRA. Better error message for missing WSDL file for EJB web service -- Key: GERONIMO-1580 URL: http://issues.apache.org/jira/browse/GERONIMO-1580 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, webservices Affects Versions: 1.0 Reporter: Aaron Mulder Assigned To: Vamsavardhana Reddy Priority: Critical Fix For: 1.1.2, 1.2 Attachments: SchemaInfoBuilder.patch If your webservices.xml file for a stateless session bean web service refers to a WSDL file that is not there, the error produced is java.lang.RuntimeException: Could not open stream to wsdl file It would be better if it produced a DeploymentException with a message something like: webservices.xml file for EJB JAR points to non-existant WSDL file 'META-INF/foo.wsdl' for service 'MyEJBWebService' The stack trace is 10:56:24,259 ERROR [Deployer] Deployment failed due to java.lang.RuntimeException: Could not open stream to wsdl file at org.apache.geronimo.axis.builder.SchemaInfoBuilder$JarWSDLLocator.getBaseInputSource(SchemaInfoBuilder.java:652) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.readWsdl(SchemaInfoBuilder.java:555) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.init(SchemaInfoBuilder.java:141) at org.apache.geronimo.axis.builder.SchemaInfoBuilder.init(SchemaInfoBuilder.java:125) at org.apache.geronimo.axis.builder.WSDescriptorParser.parseWebServiceDescriptor(WSDescriptorParser.java:312) at org.apache.geronimo.axis.builder.WSDescriptorParser.parseWebServiceDescriptor(WSDescriptorParser.java:379) at org.apache.geronimo.axis.builder.AxisBuilder.parseWebServiceDescriptor(AxisBuilder.java:106) at org.apache.geronimo.axis.builder.AxisBuilder$$FastClassByCGLIB$$16a52a9a.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.WebServiceBuilder$$EnhancerByCGLIB$$493cf3fa.parseWebServiceDescriptor(generated) at org.openejb.deployment.OpenEJBModuleBuilder.addGBeans(OpenEJBModuleBuilder.java:500) at org.openejb.deployment.OpenEJBModuleBuilder$$FastClassByCGLIB$$11bd7b20.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$4ca9e4d7.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:402) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at
[jira] Closed: (GERONIMO-477) Deployer should not auto-connect if not asked to
[ http://issues.apache.org/jira/browse/GERONIMO-477?page=all ] Vamsavardhana Reddy closed GERONIMO-477. Deployer should not auto-connect if not asked to Key: GERONIMO-477 URL: http://issues.apache.org/jira/browse/GERONIMO-477 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M4 Reporter: Jeremy Boynes Assigned To: Aaron Mulder Fix For: 1.0 Before dropping back to offline mode, the new deployer tries to auto-connect to a server running on the local machine. Since this feature was added I have run into a problem where it is connecting to the wrong server. For example, the Geronimo build will just hang during assembly if there is another server running in the background. There has been talk about splitting the online and offline functions into two tools; if this is done I don't think this will continue to be an issue as the online one could try and connect but the offline one which is used during the build won't. If we stick with one tool them I think we should add a --offline option that stops the deployer from trying to connect. It seems to me that one tool approach is getting confusing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-478) Deployer must not echo password when prompting
[ http://issues.apache.org/jira/browse/GERONIMO-478?page=all ] Vamsavardhana Reddy closed GERONIMO-478. Deployer must not echo password when prompting -- Key: GERONIMO-478 URL: http://issues.apache.org/jira/browse/GERONIMO-478 Project: Geronimo Issue Type: Bug Components: deployment Reporter: Jeremy Boynes Assigned To: Aaron Mulder Fix For: 1.0-M4 Attachments: geronimo-478.patch, geronimo-478.patch When no password is specified on the command line the deployer prompts the user for one. When this is being entered it is echoed onto the screen. On a windows machine the value entered is also displayed if up-arrow is pressed when being prompted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: RTC Certification Authority (CA) portlet
Paul, Thank you for reviewing the CA portlet and providing your comments. My response to your queries and comments: o On the UI, I did my best. I have tested the page navigation etc and it seems to be ok. There may be some minor issues which I am not aware of. Those will be addressed as they surface. o Copyright headers will be updated before the patch is committed. o The helper application is a reference application. In producton, ideally it should be running on HTTPS and some of the pages like, request certificate and download certificate should have restricted access based on userid, password, etc. o The helper application should be started only after completing the CA initialization part. o Regarding making this as a portlet in Console, I wanted to take advantage of the framework we already have in console UI and spend more time on the CA functionality. o Portlet title will be changed so that it won't wrap. o I will take a look at GERONIMO-2007 to take care of the BasicProxyManager warnings. Regards, VamsiOn 11/14/06, Paul McMahan [EMAIL PROTECTED] wrote: Great work!! This patch represents a tremendous amount of effort and Iam excited about seeing this new functionality in Geronimo.I am nota security expert so I'm not able to comment on some of the moretechnical aspects of this new feature.But from a high level I understand what is being provided and am in favor of it being madeavailable to Geronimo users.Here are a few questions and comments:-nice job on the UI-the copyright headers should be updated per GERONIMO-2537(I think this applies to JSPs as well but I am not sure)-the helper application does not define any security constraints inits web.xml.I think a constraint is needed since the applicationaffects the server's security -the helper application is not started by default.is that intentional?I'm not totally clear on why this feature was implemented partly as aweb application and partly as an admin portlet.Since CA activities are not core to the management of the application server per se itseems like an ideal candidate to implement entirely as a pair of webapplications that can be installed as plugins.If its possible torefactor the CA portion into a webapp without sacrificing too much time/effort then I'm highly favor of that approach.But I may be overlooking some important aspect of the design or justneed to broaden my view of what the admin console is used for.So ifthe current implementation remains as is then here are some additional comments about the CA portlet:-the portlet title in the console's navigation area wrapsCertifcation Authority.Can a non-breaking space (nbsp;) be usedin the title? if not then can it be shortened? -the CA portlet issues warnings, which I think are benign but canprobably be avoided.they look like:[BasicProxyManager] Could not load interface org.apache.geronimo.security.ca.GeronimoCertificationAuthority in provided ClassLoader for org.apache.geronimo.configs/j2ee-security/1.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-security/1.2-SNAPSHOT/car,j2eeType=CertificationAuthority,name=geronimo-ca (see GERONIMO-2007)Again, great work on this new feature and I look forward to seeing itbeing made available to Geronimo users!Best wishes,PaulOn 11/9/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hi Paul,Yes, I intend to make this available in 1.2.Please review whenever it is possible for you..Thanks,Vamsi On 11/9/06, Paul McMahan [EMAIL PROTECTED] wrote: I definitely plan to take a look at this but I have a couple of items to finish up on first.Do you intend to make this available in 1.2? Best wishes, Paul On 11/8/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: I have posted a patch to GERONIMO-2413 Add a Certification Authority (CA) portlet to Geronimo console.The patch contains CA portlet and CA Helper application.JIRA comment provides a few instructions ona minimal (end-to-end setup of CA and the helper application) task that can be performed using the portlet.Please take time to review the patch, try the CA portlet and the helper application.Thanks, vamsi PS: JIRA also has patch for branches\1.1 .This patch is only intended for those who want to try the portlet in 1.1.x.
[jira] Assigned: (GERONIMO-1704) Console security realm doesn't let you pick a JAR
[ http://issues.apache.org/jira/browse/GERONIMO-1704?page=all ] Vamsavardhana Reddy reassigned GERONIMO-1704: - Assignee: Vamsavardhana Reddy Console security realm doesn't let you pick a JAR - Key: GERONIMO-1704 URL: http://issues.apache.org/jira/browse/GERONIMO-1704 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 1.0 Reporter: Aaron Mulder Assigned To: Vamsavardhana Reddy Priority: Critical Fix For: 1.1.2, 1.2 It's not possible to use the console to deploy a custom login module because we don't let you specify a JAR that holds the login module and principal classes! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2563) Need to update Yoko version level to match what openejb is using.
Need to update Yoko version level to match what openejb is using. - Key: GERONIMO-2563 URL: http://issues.apache.org/jira/browse/GERONIMO-2563 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: CORBA Affects Versions: 1.2 Reporter: Rick McGuire Assigned To: Rick McGuire Fix For: 1.2 Yoko has updated the snapshot artifact to the M2 level, which openejb2 is now using. Geronimo needs similar updating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1044) Failed to register MBean error.
Failed to register MBean error. --- Key: AMQ-1044 URL: https://issues.apache.org/activemq/browse/AMQ-1044 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 If async error such as a inactivity IO exception is detected while a subscription is being created, then that subscription is not fully cleaned up when the connection is disposed. If the client is using failover and reconnects, then it gets a Failed to register MBean error. Since the subscription is still registered in JMX. This is also a source of a memory leak since subscriptions are are left registered in JMX. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2007) Avoid Classloader warnings generated by BasicProxyManager
[ http://issues.apache.org/jira/browse/GERONIMO-2007?page=comments#action_12449629 ] Vamsavardhana Reddy commented on GERONIMO-2007: --- Do we need to consider this JIRA for 1.2 as well and apply the patch to trunk? Avoid Classloader warnings generated by BasicProxyManager - Key: GERONIMO-2007 URL: http://issues.apache.org/jira/browse/GERONIMO-2007 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assigned To: Joe Bohn Fix For: 1.1.1 Attachments: GERONIMO-2007.patch Several views in the console create proxies for objects that implement interfaces not available in the console's classloader. The warning messages look like: 08:56:26,315 WARN [BasicProxyManager] Could not load interface org.apache.geronimo.tomcat.TomcatWebContainer in provided ClassLoader for geronimo/tomcat/1.1-SNAPSHOT/car?ServiceModule=geronimo/tomcat/1.1-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebContainer This warning message can be avoided by getting the classloader for the proxied object from the kernel and then using it to create the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-479) Root of WebApp Displays WEB-INF and META-INF Directories
[ http://issues.apache.org/jira/browse/GERONIMO-479?page=all ] Vamsavardhana Reddy closed GERONIMO-479. Root of WebApp Displays WEB-INF and META-INF Directories Key: GERONIMO-479 URL: http://issues.apache.org/jira/browse/GERONIMO-479 Project: Geronimo Issue Type: Bug Components: web Affects Versions: 1.0-M3 Environment: WinXP, JDK 1.4.2 Reporter: Seth Ladd Assigned To: Aaron Mulder Priority: Critical Fix For: 1.0-M5 Attachments: listBug.ear I deployed a simple webapp containing nothing more than a web.xml. There is no welcome.jsp configured or provided. The deploy was OK, but when I browse to http://localhost:8080/testbed I see a directory listing, with the directories WEB-INF and META-INF listed. This, itself, should not happen. When clicking on WEB-INF, I generate a StackOverflow. I would expect a nice Forbidden message, or even a 404 (or whatever the Servlet spec says). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-480) Poor Error Message on Deploy of Existing WebApp
[ http://issues.apache.org/jira/browse/GERONIMO-480?page=all ] Vamsavardhana Reddy closed GERONIMO-480. Poor Error Message on Deploy of Existing WebApp --- Key: GERONIMO-480 URL: http://issues.apache.org/jira/browse/GERONIMO-480 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M3 Environment: WinXP, JDK 1.4.2 Reporter: Seth Ladd Assigned To: Aaron Mulder Fix For: 1.0-M5 Attachments: geronimo-480.patch I successfully deployed a simple webapp using the commandline deploy tool. I attempted to deploy the webapp again, thinking it might redeploy the webapp. I received a cryptic stack trace: C:\geronimo-1.0-M3java -jar bin\deployer.jar deploy c:\eclipse\workspace\Minima lWebapp\build\minimaltest.war Username: system Password: manager Deployment failed Server reports: Unable to register configuration org.apache.geronimo.kernel.config.InvalidConfigException: Unable to register con figuration at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(Confi gurationManagerImpl.java:161) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(Confi gurationManagerImpl.java:146) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(Confi gurationManagerImpl.java:127) at org.apache.geronimo.kernel.Kernel.startConfiguration(Kernel.java:416) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) It would be nice if a helpful error message was displayed, something like Error: deployment failed. Reason: application already exists in server. Please undeploy or use the ReDeploy task. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-1036) web-console broken (queue browsing).
[ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]
james strachan reopened AMQ-1036:
-
Could you apply this fix to the 4-1 branch too please?
https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.1/
web-console broken (queue browsing).
Key: AMQ-1036
URL: https://issues.apache.org/activemq/browse/AMQ-1036
Project: ActiveMQ
Issue Type: Bug
Affects Versions: incubation
Reporter: Dave Syer
Assigned To: Adrian Co
Fix For: 4.1.0
I managed to build and launch the web-console from svn, but the queue
browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size}
that do not exist. When I hacked queue.jsp to remove references to those
properties I got another error on trying to purge a queue:
RequestURI=/activemq-web-console/purgeDestination.action
Caused by:
java.lang.IllegalArgumentException: Target bean must not be null
at org.springframework.util.Assert.notNull(Assert.java:113)
at
org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
at
org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
at
org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
at
org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
at
org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
at
org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
at
org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
at
org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my useless -1: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat spring.schemas http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Two things: a) where is the xsd supposed to lay? (The _proper_ URL? Not this one mentioned on this page: http://incubator.apache.org/activemq/spring-support.html http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; b) The idea behind spring.schemas is, AFAIK, that the spring-magic should kick in, and instead of going online to fetch the xsd, it will find it in the classpath. Given that the file:/Users/chirino/blahblah most definately isn't present on my machine, this will, AFAIK, result in every startup of ActiveMQ with spring-xbeans integration online access (which probably explains why all elements of the namespace-loading goes lightning, except from the activeMQ one, which stalls for some seconds). In comparison, here's the spring.schemas for spring-2.0.jar actually bundled with this ActiveMQ 4.1.0 RC2: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$ cat spring.schemas http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd Note two things: the http-URL mentioned actually return the file, but in addition, the resource specified is a classpath-resource, which exists: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$ ls -la spring-* -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd -rw-r--r-- 1 endre endre 1999 2006-09-09 23:53 spring-tool-2.0.xsd -rw-r--r-- 1 endre endre 5132 2006-09-09 23:53 spring-util-2.0.xsd This is bug AMQ-1016: https://issues.apache.org/activemq/browse/AMQ-1016 I think this should be fixed before 4.1.0 is released. Kind regards, Endre.
[jira] Commented: (GERONIMO-2007) Avoid Classloader warnings generated by BasicProxyManager
[ http://issues.apache.org/jira/browse/GERONIMO-2007?page=comments#action_12449666 ] Anita Kulshreshtha commented on GERONIMO-2007: -- This problem has been fixed by removing scope=provided from tomcat-deployer in webconsole-* configs. Avoid Classloader warnings generated by BasicProxyManager - Key: GERONIMO-2007 URL: http://issues.apache.org/jira/browse/GERONIMO-2007 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assigned To: Joe Bohn Fix For: 1.1.1 Attachments: GERONIMO-2007.patch Several views in the console create proxies for objects that implement interfaces not available in the console's classloader. The warning messages look like: 08:56:26,315 WARN [BasicProxyManager] Could not load interface org.apache.geronimo.tomcat.TomcatWebContainer in provided ClassLoader for geronimo/tomcat/1.1-SNAPSHOT/car?ServiceModule=geronimo/tomcat/1.1-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebContainer This warning message can be avoided by getting the classloader for the proxied object from the kernel and then using it to create the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2564) Declaration of an anonymous role in geronimo-web.xml
Declaration of an anonymous role in geronimo-web.xml Key: GERONIMO-2564 URL: http://issues.apache.org/jira/browse/GERONIMO-2564 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 1.1.1 Environment: Windows XP / Novell LDAP Reporter: Jérôme GODARD Priority: Critical I want to automate the migration of a JSF WAS6 application to Geronimo. I try to defined a anonymous role like the J2EE role EveryBody in Websphere Application Server 6. My policy is to secure all the application (all jsp files of my web folder) except the jsp in the subfolders public and login (since defining a security constraint on /* doesn't work, I declare a security rules on *.faces). To do that, I first defined my security constraints in web.xml : I use 4 roles : User, Support, Admin and Everybody security-constraint web-resource-collection web-resource-nameAllURI/web-resource-name descriptionRepresent all the application URI/description url-pattern*.faces/url-pattern url-pattern/faces/*/url-pattern url-pattern*.jsp/url-pattern url-pattern*.jsf/url-pattern /web-resource-collection auth-constraint description / role-nameUser/role-name role-nameAdmin/role-name role-nameSupport/role-name /auth-constraint user-data-constraint transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint security-constraint web-resource-collection web-resource-nameLogin/web-resource-name descriptionThe login page resource/description url-pattern/login/*/url-pattern http-methodGET/http-method http-methodPOST/http-method /web-resource-collection auth-constraint description / role-nameEveryBody/role-name /auth-constraint user-data-constraint transport-guaranteeCONFIDENTIAL/transport-guarantee /user-data-constraint /security-constraint security-constraint display-nameConstraints PUBLIC/display-name web-resource-collection web-resource-nameTheme Resources/web-resource-name description / url-pattern/templates/*/url-pattern url-pattern/index.jsp/url-pattern url-pattern/jscookmenu/*/url-pattern url-pattern//url-pattern http-methodGET/http-method /web-resource-collection web-resource-collection web-resource-namePublic Area/web-resource-name descriptionallows acces under /public//description url-pattern/public/*/url-pattern http-methodGET/http-method http-methodPOST/http-method /web-resource-collection auth-constraint description / role-nameEveryBody/role-name /auth-constraint user-data-constraint transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint !-- Define the Login Configuration for the service provider -- login-config auth-methodFORM/auth-method form-login-config form-login-page/login/login.jsp/form-login-page form-error-page/login/loginError.jsp/form-error-page /form-login-config /login-config When I deploy it on geronimo, I use the following geronimo-web.xml file : security-realm-nameapp-dev-ldap-realm/security-realm-name sec:security sec:default-principal realm-name=app-dev-ldap-realm sec:principal name=anonymous class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal / /sec:default-principal sec:role-mappings sec:role role-name=User sec:realm realm-name=app-dev-ldap-realm sec:principal name=GP-ZONE3-AXE-USER class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal designated-run-as=true
[jira] Updated: (AMQ-1018) Tomcat JVM hangs when it tried to get ConnectionFactory object
[ https://issues.apache.org/activemq/browse/AMQ-1018?page=all ] james strachan updated AMQ-1018: Fix Version/s: 4.0.3 (was: 4.0.2) Tomcat JVM hangs when it tried to get ConnectionFactory object -- Key: AMQ-1018 URL: https://issues.apache.org/activemq/browse/AMQ-1018 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.1 Environment: Tomcat 5.5.9, Activemq 4.0.1 Reporter: Suvarna Raju Madhey Priority: Critical Fix For: 4.0.3 Attachments: StackTrace I have deployed my application in Tomcat 5.5.9, which uses Activemq 4.0.1. To get ConnectionFactory I have written a method called getConnectionFactory. Following way i am tring to lookup.. Context ctx = new InitialContext(); Context ctx2= (Context) initCtx.lookup(java:comp/env); ConnectionFactory cf = (ConnectionFactory) ctx2.lookup(jms/ConnectionFactory); 3 iterations of start and stop works successfully. But when I start the application 4th time, it executes Context ctx2 = (Context)initCtx.lookup(java:comp/env); then it goes to next line. After that it never returns ConnectionFactory. After I notice that the application hangs.. Please find the stack which i got by running kill -3 tomcat-process-pid -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE] Release ServiceMix 3.0.1
The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet
amazon client supported platforms
Hi, which platforms amazon activemq client is proposed to be built on? I built it on RHEL4 Linux without any problems, then I tried to build it under Cygwin. Here are the last lines of build failure: g++ -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE _STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\amq_openwirecpp\ -DVERSION=\ 0.1.2\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_ H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 - DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -I. -I. -I. ./ -I/cygdrive/c/boost_1_33_1/ -MT TCPTransport.lo -MD -MP -MF .deps/TCPTranspor t.Tpo -c TCPTransport.cpp -DPIC -o .libs/TCPTransport.o TCPTransport.cpp: In member function `virtual void ActiveMQ::TCPTransport::conne ct()': TCPTransport.cpp:50: error: aggregate `addrinfo hints' has incomplete type and c annot be defined TCPTransport.cpp:52: error: invalid application of `sizeof' to incomplete type ` addrinfo' TCPTransport.cpp:56: error: `getaddrinfo' undeclared (first use this function) TCPTransport.cpp:56: error: (Each undeclared identifier is reported only once fo r each function it appears in.) TCPTransport.cpp:58: error: `gai_strerror' undeclared (first use this function) TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo' TCPTransport.cpp:50: error: forward declaration of `struct addrinfo' TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo' TCPTransport.cpp:50: error: forward declaration of `struct addrinfo' TCPTransport.cpp:61: error: `freeaddrinfo' undeclared (first use this function) make[1]: *** [TCPTransport.lo] Error 1 make[1]: Leaving directory `/home/motl/devel/amazon/amq_transport' make: *** [all-recursive] Error 1 ... Is Cygwin platform supported ? How can I cope with it? Thank you. -- View this message in context: http://www.nabble.com/amazon-client-supported-platforms-tf2628734.html#a7335457 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Closed: (GERONIMO-483) Security Realm Startup Errors Squashed (ClassNotFoundException)
[ http://issues.apache.org/jira/browse/GERONIMO-483?page=all ] Vamsavardhana Reddy closed GERONIMO-483. Security Realm Startup Errors Squashed (ClassNotFoundException) --- Key: GERONIMO-483 URL: http://issues.apache.org/jira/browse/GERONIMO-483 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M3 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.0-M4 If you deploy a security realm, and it has an exception during startup (refresh), the deployer gets: Deployment failed Server reports: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.security.GeronimoSecurityException (no security manager: RMI class loader disabled) java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.security.GeronimoSecurityException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at mx4j.remote.rmi.ClientInvoker.invoke(ClientInvoker.java:210) 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:324) at mx4j.remote.ClientProxy.invoke(ClientProxy.java:34) at mx4j.remote.rmi.ClientUnmarshaller.chain(ClientUnmarshaller.java:67) at mx4j.remote.rmi.ClientUnmarshaller.invoke(ClientUnmarshaller.java:56) at $Proxy0.invoke(Unknown Source) 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:324) at mx4j.remote.ClientProxy.invoke(ClientProxy.java:34) at mx4j.remote.rmi.ClientExceptionCatcher.invoke(ClientExceptionCatcher.java:42) at $Proxy0.invoke(Unknown Source) at org.apache.geronimo.gbean.jmx.JMXOperationInvoker.invoke(JMXOperationInvoker.java:54) at org.apache.geronimo.gbean.jmx.CGLibMethodInterceptor.intercept(CGLibMethodInterceptor.java:112) at org.apache.geronimo.kernel.KernelMBean$$EnhancerByCGLIB$$66f64035.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:48) at java.lang.Thread.run(Thread.java:534) Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.security.GeronimoSecurityException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) ... 23 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators:
[jira] Created: (AMQ-1043) transaction commit does not fail even though parts of transactions raised exception
transaction commit does not fail even though parts of transactions raised exception --- Key: AMQ-1043 URL: https://issues.apache.org/activemq/browse/AMQ-1043 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.1 Environment: windows, 4.0.1, transacted session, perssistent queues Reporter: Massive Boisson quoting Hiram I think we need to enhance our broker so that it keeps track of any errors that occurred that were part of a transaction and to force that transaction to fail on the commit. This problem is demonstrated in a related JIRA issue: https://issues.apache.org/activemq/browse/AMQ-1022 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Qustion about Broker!
On 11/14/06, penny_hu [EMAIL PROTECTED] wrote: I have solved the problem , thank you for your help! What was it? -- James --- http://radio.weblogs.com/0112098/
[jira] Closed: (GERONIMO-496) Multiple login module support broken
[ http://issues.apache.org/jira/browse/GERONIMO-496?page=all ] Vamsavardhana Reddy closed GERONIMO-496. Multiple login module support broken Key: GERONIMO-496 URL: http://issues.apache.org/jira/browse/GERONIMO-496 Project: Geronimo Issue Type: Bug Components: security Affects Versions: 1.0-M1, 1.0-M2, 1.0-M3 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.0-M4 If you configure a realm with multiple login modules, you get various errors (such as callback mismatches and null login domain when constructing a realm principal). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] james strachan updated AMQ-847: --- Fix Version/s: 4.0.3 (was: 4.0.2) Memory Leaks Key: AMQ-847 URL: https://issues.apache.org/activemq/browse/AMQ-847 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.0.3 1) factoryStats in the connection factory was holding on to connections even when they are closed. 2) peer BrokerInfos were never removed even when the peer disconnected. 3) messages dispatched from a Queue would retain a referece to the client connection even after they had been acked. 4) ScheduledThreadPoolExecutor does not always seem to release references to canceled tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-577) Inbound-only J2EE Connector can't be deployed
[ http://issues.apache.org/jira/browse/GERONIMO-577?page=all ] Vamsavardhana Reddy closed GERONIMO-577. Inbound-only J2EE Connector can't be deployed - Key: GERONIMO-577 URL: http://issues.apache.org/jira/browse/GERONIMO-577 Project: Geronimo Issue Type: Bug Components: connector Affects Versions: 1.0-M3 Reporter: Aaron Mulder Assigned To: David Jencks Fix For: 1.0-M4 An inbound-only J2EE connector gets a NullPointerException during deployment in ConnectorModuleBuilder.addConnectorGBeans (loading transaction settings where it assumes an outbound connector block is present) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1704) Console security realm doesn't let you pick a JAR
[ http://issues.apache.org/jira/browse/GERONIMO-1704?page=all ] Vamsavardhana Reddy closed GERONIMO-1704. - Resolution: Fixed Fixed in rev 474827 (branches\1.1) and rev 474830+474838 (trunk). Console security realm doesn't let you pick a JAR - Key: GERONIMO-1704 URL: http://issues.apache.org/jira/browse/GERONIMO-1704 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 1.0 Reporter: Aaron Mulder Assigned To: Vamsavardhana Reddy Priority: Critical Fix For: 1.1.2, 1.2 It's not possible to use the console to deploy a custom login module because we don't let you specify a JAR that holds the login module and principal classes! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release ServiceMix 3.0.1
Yes, I don't think there is anything to do at this point but not using the release plugin :( Do you think we should release by hand ? This is what I did for 3.0, but i thought using the maven release plugin would be better for build reproducibility, as it includes all the maven plugin versions used iirc. On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: [X] +1 Release ServiceMix 3.0.1 I ran the rat tool on the source and binary disto and I've attached it to this email. Lots of pom files don't have the asl header but I've got a feeling that you may have used the maven release plugin and that strips out comments from the poms. On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote: The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet -- Regards, Hiram Blog: http://hiramchirino.com -- Cheers, Guillaume Nodet
[jira] Created: (GERONIMO-2565) User confirmation on attempting to stop a web connector through WebServer portlet
User confirmation on attempting to stop a web connector through WebServer portlet - Key: GERONIMO-2565 URL: http://issues.apache.org/jira/browse/GERONIMO-2565 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Assigned To: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.2, 1.2 Stopping a web connector does not ask for user confirmation. Stopping the web connector corresponding to the port on which the Admin Console app is being accessed will make the Console app inaccessible. The user should be given a last chance before stopping the connector by providing a warning dialog. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: build error
Hello all. I didn't get that error, but I got a different one. Has the new yoko m2-snapshot been published? (I got an missing artifact error) [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \ -Dversion=1.0-incubating-M2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.configs:client-corba-yoko:car:1.2-SNAPSHOT 2) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT -- 1 required artifact is missing. I'm going to get around it by just building yoko myself though. Just to let folks know, Jay
Re: build error
I saw this when building openejb, I think. I deleted openejb from my local repo and rebuilt. Error gone. Cheers Prasad On 11/14/06, Sachin Patel [EMAIL PROTECTED] wrote: Is anyone else hitting the following? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Unable to create configuration for deployment org.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = 1053655034244747613, local class serialVersionUID = -619880406710221 -sachin
[jira] Commented: (GERONIMO-2548) GBeanInfo should exclude attributes and operations of java.lang.Object class
[ http://issues.apache.org/jira/browse/GERONIMO-2548?page=comments#action_12449654 ] Anita Kulshreshtha commented on GERONIMO-2548: -- Fixed in rev 474768. TODO - add a return type to GOperationInfo GBeanInfo should exclude attributes and operations of java.lang.Object class Key: GERONIMO-2548 URL: http://issues.apache.org/jira/browse/GERONIMO-2548 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: kernel Affects Versions: 1.2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Anita Kulshreshtha Attachments: kernel.patch, operations.jpg GBeanInfo includes 8 methods of java.lang.Object as opertaions. The 9th method of java.lang.Object getClass is added as an attribute named class in GbeanInfo. These should be excluded from GBeanInfo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1044) Failed to register MBean error.
[ https://issues.apache.org/activemq/browse/AMQ-1044?page=all ] Hiram Chirino resolved AMQ-1044. Resolution: Fixed Fixed in trunk rev 474769 and in 4.1 branch rev 474771 Failed to register MBean error. --- Key: AMQ-1044 URL: https://issues.apache.org/activemq/browse/AMQ-1044 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 If async error such as a inactivity IO exception is detected while a subscription is being created, then that subscription is not fully cleaned up when the connection is disposed. If the client is using failover and reconnects, then it gets a Failed to register MBean error. Since the subscription is still registered in JMX. This is also a source of a memory leak since subscriptions are are left registered in JMX. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-2505) GBeanInfo.getOperations() returns the operations defined on java.lang.Object. They should be filtered
[ http://issues.apache.org/jira/browse/GERONIMO-2505?page=all ] Anita Kulshreshtha resolved GERONIMO-2505. -- Resolution: Fixed GBeanInfo.getOperations() returns the operations defined on java.lang.Object. They should be filtered - Key: GERONIMO-2505 URL: http://issues.apache.org/jira/browse/GERONIMO-2505 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Affects Versions: 1.1.1 Reporter: Guillaume Nodet Assigned To: Anita Kulshreshtha Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2505) GBeanInfo.getOperations() returns the operations defined on java.lang.Object. They should be filtered
[ http://issues.apache.org/jira/browse/GERONIMO-2505?page=all ] Anita Kulshreshtha reassigned GERONIMO-2505: Assignee: Anita Kulshreshtha Fixed in rev 474768. See GERONIMO-2548 GBeanInfo.getOperations() returns the operations defined on java.lang.Object. They should be filtered - Key: GERONIMO-2505 URL: http://issues.apache.org/jira/browse/GERONIMO-2505 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Affects Versions: 1.1.1 Reporter: Guillaume Nodet Assigned To: Anita Kulshreshtha Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ POM
On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote:
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
I'd have thought so?
--
James
---
http://radio.weblogs.com/0112098/
[jira] Commented: (GERONIMO-2007) Avoid Classloader warnings generated by BasicProxyManager
[ http://issues.apache.org/jira/browse/GERONIMO-2007?page=comments#action_12449668 ] Vamsavardhana Reddy commented on GERONIMO-2007: --- I am observing these warnings when I run CA portlet (GERONIMO-2413). These warnings could be avoided by only after applying a fix similar to the one submitted by Paul. PortletManager.getManagedBeans() is the method resulting in these warnings. Avoid Classloader warnings generated by BasicProxyManager - Key: GERONIMO-2007 URL: http://issues.apache.org/jira/browse/GERONIMO-2007 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assigned To: Joe Bohn Fix For: 1.1.1 Attachments: GERONIMO-2007.patch Several views in the console create proxies for objects that implement interfaces not available in the console's classloader. The warning messages look like: 08:56:26,315 WARN [BasicProxyManager] Could not load interface org.apache.geronimo.tomcat.TomcatWebContainer in provided ClassLoader for geronimo/tomcat/1.1-SNAPSHOT/car?ServiceModule=geronimo/tomcat/1.1-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebContainer This warning message can be avoided by getting the classloader for the proxied object from the kernel and then using it to create the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: amazon client supported platforms
Not supported out of box. If you want to take a stab at doing a port, please be my guest! Patches would be welcomed! On 11/14/06, Motl [EMAIL PROTECTED] wrote: Hi, which platforms amazon activemq client is proposed to be built on? I built it on RHEL4 Linux without any problems, then I tried to build it under Cygwin. Here are the last lines of build failure: g++ -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE _STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\amq_openwirecpp\ -DVERSION=\ 0.1.2\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_ H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 - DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -I. -I. -I. ./ -I/cygdrive/c/boost_1_33_1/ -MT TCPTransport.lo -MD -MP -MF .deps/TCPTranspor t.Tpo -c TCPTransport.cpp -DPIC -o .libs/TCPTransport.o TCPTransport.cpp: In member function `virtual void ActiveMQ::TCPTransport::conne ct()': TCPTransport.cpp:50: error: aggregate `addrinfo hints' has incomplete type and c annot be defined TCPTransport.cpp:52: error: invalid application of `sizeof' to incomplete type ` addrinfo' TCPTransport.cpp:56: error: `getaddrinfo' undeclared (first use this function) TCPTransport.cpp:56: error: (Each undeclared identifier is reported only once fo r each function it appears in.) TCPTransport.cpp:58: error: `gai_strerror' undeclared (first use this function) TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo' TCPTransport.cpp:50: error: forward declaration of `struct addrinfo' TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo' TCPTransport.cpp:50: error: forward declaration of `struct addrinfo' TCPTransport.cpp:61: error: `freeaddrinfo' undeclared (first use this function) make[1]: *** [TCPTransport.lo] Error 1 make[1]: Leaving directory `/home/motl/devel/amazon/amq_transport' make: *** [all-recursive] Error 1 ... Is Cygwin platform supported ? How can I cope with it? Thank you. -- View this message in context: http://www.nabble.com/amazon-client-supported-platforms-tf2628734.html#a7335457 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Regards, Hiram Blog: http://hiramchirino.com
Re: ActiveMQ POM
Thanks Fritz!
I knew there had to be a reason that I was just not aware of. What do
you think would be the downsides of not using the special SNAPSHOT
handling that maven provides? What if we tagged our SNAPSHOT builds
with something like like DEVELOPMENT instead of SNAPSHOT.
I'm guessing that problem would go away, but what other ones would we get?
On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
This is also my experience.
If we just use the real version 4.2-SNAPSHOT
for example, it should also work and maven
should be able to change (*nearly*) all these
occurrences when using the release plugin.
I say nearly, because in ServiceMix, there are
some edge cases where this fail (when including
the version in files other than pom.xml like artifacts
resources for example).
On 11/14/06, Fritz Oconer [EMAIL PROTECTED] wrote:
Hi,
I added ${activemq-version} instead of ${project.version} basically as a
workaround for build failures due to differences in timestamp. If we use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same timestamp
as the parent. This becomes an issue when nightly-build deploy fails after
some of the modules have been deployed causing some activemq modules to have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
--
Regards,
Hiram
Blog: http://hiramchirino.com
[jira] Closed: (GERONIMO-726) Deployments can silently fail
[ http://issues.apache.org/jira/browse/GERONIMO-726?page=all ] Vamsavardhana Reddy closed GERONIMO-726. Deployments can silently fail - Key: GERONIMO-726 URL: http://issues.apache.org/jira/browse/GERONIMO-726 Project: Geronimo Issue Type: Bug Components: deployment Reporter: Dain Sundstrom Assigned To: Aaron Mulder Fix For: 1.0-M4 Sometimes when a deployment fails the deployment tool exit silently. The only way to know that a deployment failed is because the tool does not print a Deployed xxx message. Based on a little bit of debugging it looks like the fail method in CommandSupport is not working because no listeners are registered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2563) Need to update Yoko version level to match what openejb is using.
[ http://issues.apache.org/jira/browse/GERONIMO-2563?page=all ] Rick McGuire closed GERONIMO-2563. -- Resolution: Fixed Committed revision 474766. Need to update Yoko version level to match what openejb is using. - Key: GERONIMO-2563 URL: http://issues.apache.org/jira/browse/GERONIMO-2563 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: CORBA Affects Versions: 1.2 Reporter: Rick McGuire Assigned To: Rick McGuire Fix For: 1.2 Yoko has updated the snapshot artifact to the M2 level, which openejb2 is now using. Geronimo needs similar updating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
[jira] Created: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case --- Key: AMQ-1045 URL: https://issues.apache.org/activemq/browse/AMQ-1045 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Logging problems
The same can be achieved by setting DEBUG to INFO in log4j.logger.org.apache.geronimo.gbean.runtime.GBeanSingleReference=DEBUG. It was nice to be able to just add one line to debug a class, and not hunt down the threshold to change it... Though I agree that for a release the threshold should be set to INFO. Thanks Anita --- Dain Sundstrom [EMAIL PROTECTED] wrote: The log level is set to INFO: http://svn.apache.org/repos/asf/geronimo/server/trunk/assemblies/ geronimo-boilerplate-minimal/src/main/resources/var/log/server- log4j.properties -dain On Nov 10, 2006, at 6:33 PM, anita kulshreshtha wrote: The log file only contains environment info. No other information is being written. Thanks Anita __ __ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com
[jira] Resolved: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
[ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ] Hiram Chirino resolved AMQ-1045. Resolution: Fixed Fixed in trunk rev 474799 and in 4.1 branch rev 474800 PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case --- Key: AMQ-1045 URL: https://issues.apache.org/activemq/browse/AMQ-1045 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 The DefaultMessageListenerContainer has retry logic built into it. When a connection dies it tried to reconnect by getting a new connection from the ConnectionFactory. Since the PooledConenctionFactory has one Connection it, it keeps on trying to give out the Connection that died. We would like the PooledConnectionFactory to be able to evict the dead connection and create a new one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
Hi Endre, Thanks for the feedback but I don't agree that this issue should hold up the release. I'm sure we can fix this in a subsequent bug fix release. BTW, if you submit a patch with the fix for this it would make getting the fix into the next release much easier :) Regards, Hiram On 11/14/06, Endre Stølsvik [EMAIL PROTECTED] wrote: Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my useless -1: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat spring.schemas http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Two things: a) where is the xsd supposed to lay? (The _proper_ URL? Not this one mentioned on this page: http://incubator.apache.org/activemq/spring-support.html http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; b) The idea behind spring.schemas is, AFAIK, that the spring-magic should kick in, and instead of going online to fetch the xsd, it will find it in the classpath. Given that the file:/Users/chirino/blahblah most definately isn't present on my machine, this will, AFAIK, result in every startup of ActiveMQ with spring-xbeans integration online access (which probably explains why all elements of the namespace-loading goes lightning, except from the activeMQ one, which stalls for some seconds). In comparison, here's the spring.schemas for spring-2.0.jar actually bundled with this ActiveMQ 4.1.0 RC2: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$ cat spring.schemas http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd Note two things: the http-URL mentioned actually return the file, but in addition, the resource specified is a classpath-resource, which exists: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$ ls -la spring-* -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd -rw-r--r-- 1 endre endre 1999 2006-09-09 23:53 spring-tool-2.0.xsd -rw-r--r-- 1 endre endre 5132 2006-09-09 23:53 spring-util-2.0.xsd This is bug AMQ-1016: https://issues.apache.org/activemq/browse/AMQ-1016 I think this should be fixed before 4.1.0 is released. Kind regards, Endre. -- Regards, Hiram Blog: http://hiramchirino.com
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
+1 Regards, Fritz - Original Message - From: Hiram Chirino [EMAIL PROTECTED] To: activemq-dev@geronimo.apache.org; general@incubator.apache.org Sent: Tuesday, November 14, 2006 1:07 PM Subject: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2) Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my +1 -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Updated: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
[ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ] Hiram Chirino updated AMQ-1045: --- Description: The DefaultMessageListenerContainer has retry logic built into it. When a connection dies it tried to reconnect by getting a new connection from the ConnectionFactory. Since the PooledConenctionFactory has one Connection it, it keeps on trying to give out the Connection that died. We would like the PooledConnectionFactory to be able to evict the dead connection and create a new one. PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case --- Key: AMQ-1045 URL: https://issues.apache.org/activemq/browse/AMQ-1045 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0, 4.1.1 The DefaultMessageListenerContainer has retry logic built into it. When a connection dies it tried to reconnect by getting a new connection from the ConnectionFactory. Since the PooledConenctionFactory has one Connection it, it keeps on trying to give out the Connection that died. We would like the PooledConnectionFactory to be able to evict the dead connection and create a new one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: build error
I think Gianny fixed this a few days ago but you may have to delete org/apache/geronimo from your local repo and rebuild. Best wishes, Paul On 11/14/06, Sachin Patel [EMAIL PROTECTED] wrote: Is anyone else hitting the following? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Unable to create configuration for deployment org.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = 1053655034244747613, local class serialVersionUID = -619880406710221 -sachin
Re: [VOTE] Release ServiceMix 3.0.1
Here ya go! http://www.nabble.com/file/4171/rat.log rat.log http://www.nabble.com/file/4172/rat-binary.log rat-binary.log gnodet wrote: Could you please attach the output to the nabble forums ? It seems it has been removed :( On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: [X] +1 Release ServiceMix 3.0.1 I ran the rat tool on the source and binary disto and I've attached it to this email. Lots of pom files don't have the asl header but I've got a feeling that you may have used the maven release plugin and that strips out comments from the poms. On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote: The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet -- Regards, Hiram Blog: http://hiramchirino.com -- Cheers, Guillaume Nodet -- View this message in context: http://www.nabble.com/-VOTE--Release-ServiceMix-3.0.1-tf2629945s12049.html#a7340935 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (GERONIMO-2007) Avoid Classloader warnings generated by BasicProxyManager
Please see http://issues.apache.org/jira/browse/GERONIMO-2344 This might have been a temporary solution.. Thanks Anita --- Vamsavardhana Reddy (JIRA) [EMAIL PROTECTED] wrote: [ http://issues.apache.org/jira/browse/GERONIMO-2007?page=comments#action_12449668 ] Vamsavardhana Reddy commented on GERONIMO-2007: --- I am observing these warnings when I run CA portlet (GERONIMO-2413). These warnings could be avoided by only after applying a fix similar to the one submitted by Paul. PortletManager.getManagedBeans() is the method resulting in these warnings. Avoid Classloader warnings generated by BasicProxyManager - Key: GERONIMO-2007 URL: http://issues.apache.org/jira/browse/GERONIMO-2007 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assigned To: Joe Bohn Fix For: 1.1.1 Attachments: GERONIMO-2007.patch Several views in the console create proxies for objects that implement interfaces not available in the console's classloader. The warning messages look like: 08:56:26,315 WARN [BasicProxyManager] Could not load interface org.apache.geronimo.tomcat.TomcatWebContainer in provided ClassLoader for geronimo/tomcat/1.1-SNAPSHOT/car?ServiceModule=geronimo/tomcat/1.1-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebContainer This warning message can be avoided by getting the classloader for the proxied object from the kernel and then using it to create the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
build error
Is anyone else hitting the following?[INFO] [ERROR] BUILD ERROR[INFO] [INFO] Unable to create configuration for deploymentorg.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = 1053655034244747613, local class serialVersionUID = -619880406710221 -sachin
Re: [VOTE] Release ServiceMix 3.0.1
Could you please attach the output to the nabble forums ? It seems it has been removed :( On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: [X] +1 Release ServiceMix 3.0.1 I ran the rat tool on the source and binary disto and I've attached it to this email. Lots of pom files don't have the asl header but I've got a feeling that you may have used the maven release plugin and that strips out comments from the poms. On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote: The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet -- Regards, Hiram Blog: http://hiramchirino.com -- Cheers, Guillaume Nodet
Re: [VOTE] Release ServiceMix 3.0.1
[X] +1 Release ServiceMix 3.0.1 I ran the rat tool on the source and binary disto and I've attached it to this email. Lots of pom files don't have the asl header but I've got a feeling that you may have used the maven release plugin and that strips out comments from the poms. On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote: The previous vote has been put on hold due to a problem in the maven repository with an invalid pom. This problem has been solved, so I'd like to push out the release built some weeks ago now. Binaries have been uploaded on the incubating repository: http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/ [ ] +1 Release ServiceMix 3.0.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.0.1 Here's my +1 -- Cheers, Guillaume Nodet -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Closed: (GERONIMO-2565) User confirmation on attempting to stop a web connector through WebServer portlet
[ http://issues.apache.org/jira/browse/GERONIMO-2565?page=all ] Vamsavardhana Reddy closed GERONIMO-2565. - Resolution: Fixed Fixed in rev 474859 (trunk) and 474861 (branches\1.1). User confirmation on attempting to stop a web connector through WebServer portlet - Key: GERONIMO-2565 URL: http://issues.apache.org/jira/browse/GERONIMO-2565 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2, 1.1.1 Reporter: Vamsavardhana Reddy Assigned To: Vamsavardhana Reddy Priority: Minor Fix For: 1.1.2, 1.2 Stopping a web connector does not ask for user confirmation. Stopping the web connector corresponding to the port on which the Admin Console app is being accessed will make the Console app inaccessible. The user should be given a last chance before stopping the connector by providing a warning dialog. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-421) Better handling for null/empty users in default LoginModules
[ http://issues.apache.org/jira/browse/GERONIMO-421?page=all ] Vamsavardhana Reddy closed GERONIMO-421. Better handling for null/empty users in default LoginModules Key: GERONIMO-421 URL: http://issues.apache.org/jira/browse/GERONIMO-421 Project: Geronimo Issue Type: Bug Components: security Affects Versions: 1.0-M2 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.0-M4 The PropertiesFileLoginModule throws an assertion error if no username is provided. I think this should just return false (or worst case, throw a regular LoginException) instead. I expect it to be unusual that the username would be null, but if so, it's just a plain failed login, right? The SQLLoginModule doesn't seem to check at all, and would throw a NullPointerException if the user was null. Whatever we decide on the other one, we should do it here too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ POM
Hi,
I added ${activemq-version} instead of ${project.version} basically as a
workaround for build failures due to differences in timestamp. If we use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same timestamp
as the parent. This becomes an issue when nightly-build deploy fails after
some of the modules have been deployed causing some activemq modules to have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
I think the problem comes from the fact that the xsds are not generated in their default locations (target/xbean). Changing the configuration to: schematarget/xbean/activemq.xsd/schema should work. On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: Hi Endre, Thanks for the feedback but I don't agree that this issue should hold up the release. I'm sure we can fix this in a subsequent bug fix release. BTW, if you submit a patch with the fix for this it would make getting the fix into the next release much easier :) Regards, Hiram On 11/14/06, Endre Stølsvik [EMAIL PROTECTED] wrote: Hiram Chirino wrote: Hey folks, I was able to finally get around to doing a binary release candidate from the 4.1 branch. it's available here: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/ Maven 1 and Maven 2 repos for this release can be found at: http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2 Here's the wiki page for the release notes: http://incubator.apache.org/activemq/activemq-410-release.html Please vote to approve this release binary [ ] +1 Release the binary as Apache ActiveMQ 4.1.0 [ ] -1 Veto the release (provide specific comments) This vote is being cross posted to the general incubator mailing list also to expedite the voting process. Here's my useless -1: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat spring.schemas http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Two things: a) where is the xsd supposed to lay? (The _proper_ URL? Not this one mentioned on this page: http://incubator.apache.org/activemq/spring-support.html http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; b) The idea behind spring.schemas is, AFAIK, that the spring-magic should kick in, and instead of going online to fetch the xsd, it will find it in the classpath. Given that the file:/Users/chirino/blahblah most definately isn't present on my machine, this will, AFAIK, result in every startup of ActiveMQ with spring-xbeans integration online access (which probably explains why all elements of the namespace-loading goes lightning, except from the activeMQ one, which stalls for some seconds). In comparison, here's the spring.schemas for spring-2.0.jar actually bundled with this ActiveMQ 4.1.0 RC2: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$ cat spring.schemas http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd Note two things: the http-URL mentioned actually return the file, but in addition, the resource specified is a classpath-resource, which exists: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$ ls -la spring-* -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd -rw-r--r-- 1 endre endre 1999 2006-09-09 23:53 spring-tool-2.0.xsd -rw-r--r-- 1 endre endre 5132 2006-09-09 23:53 spring-util-2.0.xsd This is bug AMQ-1016: https://issues.apache.org/activemq/browse/AMQ-1016 I think this should be fixed before 4.1.0 is released. Kind regards, Endre. -- Regards, Hiram Blog: http://hiramchirino.com -- Cheers, Guillaume Nodet
[jira] Closed: (GERONIMO-422) SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant
[ http://issues.apache.org/jira/browse/GERONIMO-422?page=all ] Vamsavardhana Reddy closed GERONIMO-422. SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant --- Key: GERONIMO-422 URL: http://issues.apache.org/jira/browse/GERONIMO-422 Project: Geronimo Issue Type: Bug Components: security Affects Versions: 1.0-M2 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.0-M4 If you use a custom LoginModule with a SimpleSecurityRealm, there are two ways to provide options to the LoginModule. One is to set the options property on SimpleSecurityRealm. The other is to set the options property on the ConfiguraitonEntryRealmLocal when you deploy a JAAS configuration for the realm. It doesn't seem like we need both ways to specify options to the login module. I think we could remove the options property from SimpleSecurityRealm, and just use the options on the ConfigurationEntryRealmLocal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-427) Jetty HTTPSConnector doesn't expose necessary configuration options
[ http://issues.apache.org/jira/browse/GERONIMO-427?page=all ] Vamsavardhana Reddy closed GERONIMO-427. Jetty HTTPSConnector doesn't expose necessary configuration options --- Key: GERONIMO-427 URL: http://issues.apache.org/jira/browse/GERONIMO-427 Project: Geronimo Issue Type: Bug Components: web Affects Versions: 1.0-M2 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.0-M3 It is not possible to configure the Jetty HTTPS connector with the necesasry settings to enable HTTPS. For example: - server key - server cert - whether to require client auth - the CA cert -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-271) PetStore deployment
[ http://issues.apache.org/jira/browse/GERONIMO-271?page=all ] Vamsavardhana Reddy closed GERONIMO-271. PetStore deployment --- Key: GERONIMO-271 URL: http://issues.apache.org/jira/browse/GERONIMO-271 Project: Geronimo Issue Type: Task Components: sample apps Affects Versions: 1.0-M4 Reporter: Jacek Laskowski Assigned To: Jacek Laskowski Priority: Minor Fix For: 1.0 It's finally the time to see PetStore running on Geronimo. This task is to track the progress. Instruction available at http://wiki.apache.org/geronimo/PetStore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: build error
After getting past the previous one, I'm hitting this now as well.On Nov 14, 2006, at 11:32 AM, Jay D. McHugh wrote:Hello all.I didn't get that error, but I got a different one.Has the new yoko m2-snapshot been published?(I got an missing artifact error)[INFO] Failed to resolve artifact.Missing:--1) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \ -Dversion=1.0-incubating-M2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.configs:client-corba-yoko:car:1.2-SNAPSHOT 2) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT--1 required artifact is missing.I'm going to get around it by just building yoko myself though.Just to let folks know,Jay -sachin
Re: build error
Jay, I got the same error and worked around it in the manner you suggested, i.e. by building yoko locally. Best wishes, Paul On 11/14/06, Jay D. McHugh [EMAIL PROTECTED] wrote: Hello all. I didn't get that error, but I got a different one. Has the new yoko m2-snapshot been published? (I got an missing artifact error) [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \ -Dversion=1.0-incubating-M2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.configs:client-corba-yoko:car:1.2-SNAPSHOT 2) org.apache.yoko:yoko-core:jar:1.0-incubating-M2-SNAPSHOT -- 1 required artifact is missing. I'm going to get around it by just building yoko myself though. Just to let folks know, Jay
Re: ActiveMQ POM
I think the main problem is that users will never
download newest versions. IMHO, this would be a bad
idea.
On 11/14/06, Hiram Chirino [EMAIL PROTECTED] wrote:
Thanks Fritz!
I knew there had to be a reason that I was just not aware of. What do
you think would be the downsides of not using the special SNAPSHOT
handling that maven provides? What if we tagged our SNAPSHOT builds
with something like like DEVELOPMENT instead of SNAPSHOT.
I'm guessing that problem would go away, but what other ones would we get?
On 11/14/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
This is also my experience.
If we just use the real version 4.2-SNAPSHOT
for example, it should also work and maven
should be able to change (*nearly*) all these
occurrences when using the release plugin.
I say nearly, because in ServiceMix, there are
some edge cases where this fail (when including
the version in files other than pom.xml like artifacts
resources for example).
On 11/14/06, Fritz Oconer [EMAIL PROTECTED] wrote:
Hi,
I added ${activemq-version} instead of ${project.version} basically as a
workaround for build failures due to differences in timestamp. If we use
${project.version} then it will require all activemq type artifacts
(specified as dependency in the parent pom.xml) to have the same timestamp
as the parent. This becomes an issue when nightly-build deploy fails after
some of the modules have been deployed causing some activemq modules to have
different timestamp as the parent. We can change this back to using
project.version but we need to make sure that nightly-build always deploys
successfully or I wonder if there is another workaround for this?
https://issues.apache.org/activemq/browse/AMQ-956
Regards,
Fritz
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM
Howdy,
I was wondering if anybody knows why we are using
${activemq-version} instead of ${project.version} in our ActiveMQ
poms?? When doing a release build, it's easy to forget that you need
to updated the version in to places. Can't we just use the
${project.version} variable??
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
Cheers,
Guillaume Nodet
[jira] Resolved: (SM-736) JcaConsumerProcessor.start() fails after subsequent stop()
[ https://issues.apache.org/activemq/browse/SM-736?page=all ] Guillaume Nodet resolved SM-736. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Tue Nov 14 09:01:05 2006 New Revision: 474869 URL: http://svn.apache.org/viewvc?view=revrev=474869 Log: SM-376: JcaConsumerProcessor.start() fails after subsequent stop() Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaConsumerProcessor.java JcaConsumerProcessor.start() fails after subsequent stop() -- Key: SM-736 URL: https://issues.apache.org/activemq/browse/SM-736 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.1 Environment: Windows XP, JBoss 4.0.4 GA Reporter: Frank Trietsch Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: JcaConsumerProcessor.java When a JMS-SU ist stopped and reactivated then the start() method fails with the following exception: java.lang.IllegalArgumentException: resourceAdapter not set at org.apache.servicemix.jms.jca.JcaConsumerProcessor.start(JcaConsumerProcessor.java:92) This due to a wrong check in the start() method. A fixed version is attached. Regards, Frank -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DAYTRADER-24) Clean up plan files in 1.2 branch
[ http://issues.apache.org/jira/browse/DAYTRADER-24?page=all ] Christopher James Blythe updated DAYTRADER-24: -- Attachment: daytrader-24.patch I removed the existing files from the plans directory, moved over the jetty and tomcat plans from the 1.1 branch, and made the following modificatoins: - Updated the password field to passwd in the AccountProfileEJB definition - Removed the dependency on the pre-built derby database - Set the create db flag on the Derby data source to true - Increased the data source max pool size to 30 - Removed the GBean to copy the pre-built derby database If any of these changes are not warrented, let me know... The associated patch file is attached. As a side note, I applied the patch to another workig copy of the repository and noticed that the patch program did not remove the old files. Instead, it merely made them 0 byte files. Is that expected? Chris Clean up plan files in 1.2 branch - Key: DAYTRADER-24 URL: http://issues.apache.org/jira/browse/DAYTRADER-24 Project: DayTrader Issue Type: Bug Affects Versions: 1.2 Reporter: Christopher James Blythe Priority: Minor Attachments: daytrader-24.patch The plan files in the 1.2 branch are are based on Geronimo 1.0 and need to be updated (similar to what is in the Daytrader 1.1 branch). It would also be nice if we could add plan files for Oracle and DB2 data sources. However, it looks like we do not include the necessary Tranql rars in Geronimo to support this out of the box. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DAYTRADER-22) Set publichQuotePriceChange to true in ejb-jar.xml so that MDBs get accessed during Daytrader scenario runs
[ http://issues.apache.org/jira/browse/DAYTRADER-22?page=comments#action_12449715 ] Christopher James Blythe commented on DAYTRADER-22: --- All... Since my involvement with Daytrader (and Trade), we've never been all that concerned with the Async 1-phase mode. Here is the lay of the land to my understanding... Sync mode - Uses JMS topics and TradeTopicMDB to publish changes to the quote prices - There is flag in the DDs to disable this but it doesn't seem to apply to direct mode (only EJB mode) Async 2-phase mode - This mode uses a JMS queue and the TradeBroker to handle order processing - Specifically, the buy and sell operations call a queueOrder method to place a message on the queue - The queueOrder is part of an XA transaction because two resource managers (JMS and database) are involved to create the order in the databse and place a message on the queue - The MDB starts a new transaction when the message is read from the queue. The MDB then executes the completeOrder method which updates the order in the database inside the original MDB transaction context Async 1-phase mode - Does the same as above, but does not involve an UserTransaction to provide XA - Since the MDB is container-managed, TradeEJB is used to complete the order and create a new transaction (avoiding XA) My guess is that the Async 1-phase mode was added to messure the overhead associated with handling the XA transaction. I think Andrew Spyker was partly responsible for adding this... so, let me see if I can track him down to get more details. Regardless, I have never found that much value in Async 1-phase mode. If you are using two different resources as part of a logical transaction, you should always use XA to ensure proper rollback handling. Honestly, I see very little need to keep it around... However, there might be some possiblities I have not considered. Removing this option (and associated dependency) would also make it easier to decouple the app as suggested in Daytrader-23. I like the idea of splitting up the modes by category and doing a little renaming to make them more descriptive. Persistence Run-time Modes (one has to be selected) 1) Direct (or JDBC) 2) Stateless Session Bean to Direct 3) Full EJB (Stateless Session Bean to Entity Beans) JMS Support Enablement (any can be selected) - Publish Quote Updates (Publish quote price changes to a JMS topic) - Process Buy/Sell Orders using XA (Asychronously process buy/sell orders by placing them on a JMS queue. An MDB is then responsible for reading a message form the queue and completing the order) Thoughts? Set publichQuotePriceChange to true in ejb-jar.xml so that MDBs get accessed during Daytrader scenario runs --- Key: DAYTRADER-22 URL: http://issues.apache.org/jira/browse/DAYTRADER-22 Project: DayTrader Issue Type: Bug Components: EJB Tier Affects Versions: 1.2 Reporter: Piyush Agarwal Assigned To: Matt Hogstrom Fix For: 1.2 Attachments: Daytrader-22.patch Currently the publishQuotePriceChange is set to False in the ejb-jar.xml and this causes the TradeStreamerMDB to NOT be accessed during the Daytrader trading runs. The TradeStreamerMDB listens to the JMS messages and invokes the logging code to log the debug and trace messages during the runs. Updating the flag to true enables this functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DAYTRADER-14) Include sql script in the ear and use a gbean to create tables etc
[ http://issues.apache.org/jira/browse/DAYTRADER-14?page=comments#action_12449738 ] Christopher James Blythe commented on DAYTRADER-14: --- Piyush... I really like what you have here... It's clean, simple, and makes working with the default derby database so much easier. We no long have to run and external sql script or provide a pre-built derby database. Actually, I went ahead and changed the deployment plans in Daytrader-24 to create the derby db by default. Just a few more comments... - I like how feedback is written to the page while created the db. How do you feel about writing out the status for each sql command that is executed instead of waiting for all of them to complete. If for some reason, one were to fail it would be nice to see it in the browser screen. That way we don't have to dig through the logs to see what happened. - Looks like there might be a type of two in your trace/error statements... In TradeDirect.java - thrown on executing the [foll] sql command: - We need to sync up the ddl files - specifically, the indexes. I will create another JIRA to address this. Chris Include sql script in the ear and use a gbean to create tables etc -- Key: DAYTRADER-14 URL: http://issues.apache.org/jira/browse/DAYTRADER-14 Project: DayTrader Issue Type: Improvement Components: EJB Tier Affects Versions: 1.2 Reporter: David Jencks Attachments: d-j-plan.xml, DAYTRADER-14.patch, daytrader-14.patch.1019 You can use the DatabaseIntitializationGBean (GERONIMO-2396) in a g. plan and include the sql script in the ejb module so the database will get created if not already present. This is way better than the previous hack of including a pre-built database in the car file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DAYTRADER-25) Update decimal precision and indexes in ddl
Update decimal precision and indexes in ddl --- Key: DAYTRADER-25 URL: http://issues.apache.org/jira/browse/DAYTRADER-25 Project: DayTrader Issue Type: Improvement Reporter: Christopher James Blythe Priority: Minor While working with previous versions of Trade, I found that the monetary values stored in the database could overrun the decimal precision defined in the schema (10,2) if allowed to run for an extended period of time. This would result in SQL exceptions related to data conversion. To prevent this we increased the decimal presion to (14,2) We also found that some of the indexs were not necessary and that others should be added. In addition to the primary keys, here are the indexes we found to be the most useful... CREATE INDEX a.profile_userid on accountejb(profile_userid); CREATE INDEX h.account_accountid on holdingejb(account_accountid); CREATE INDEX o.account_accountid on orderejb(account_accountid); CREATE INDEX o.holding_holdingid on orderejb(holding_holdingid); CREATE INDEX o.closed_orders on orderejb(account_accountid,orderstatus); Will wait to submit a patch until the fate of Daytrader-14 is determined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2106) Document the modules included in each assembly on our Wiki
[ http://issues.apache.org/jira/browse/GERONIMO-2106?page=all ] Matt Hogstrom updated GERONIMO-2106: Fix Version/s: Wish List (was: 1.2) This is not tied to a specific release so I'm moving it to wish list. Document the modules included in each assembly on our Wiki -- Key: GERONIMO-2106 URL: http://issues.apache.org/jira/browse/GERONIMO-2106 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 1.1 Reporter: Donald Woods Assigned To: Donald Woods Priority: Trivial Fix For: Wish List Attachments: Geronimo1.1-Config-20060512.ppt Info needed inorder to enable upgrades from minimal-server to j2ee-server - If you get a chance, could you look at project.xml for the J2EE assemblies vs. the minimal assemblies and make a list of all the Geronimo modules in the two? Such as: module J2EE minimal system yes yes unavailable-webservices-deployer no yes ... We can use a list like that to create the plugin metadata to upgrade minimal to full J2EE. Thanks, Aaron -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1420) HTTP Status 500 message should refer to geronimo logs
[ http://issues.apache.org/jira/browse/GERONIMO-1420?page=all ] Matt Hogstrom updated GERONIMO-1420: Fix Version/s: Wish List (was: 1.2) Not tied to 1.2. If someone wants to fix this issue please assign it to yourself and a release. HTTP Status 500 message should refer to geronimo logs - Key: GERONIMO-1420 URL: http://issues.apache.org/jira/browse/GERONIMO-1420 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 1.0 Environment: All Reporter: Anita Kulshreshtha Priority: Trivial Fix For: Wish List When an exception trace is produced by a web app, the message refers to Apache Tomcat/5.5.12 logs. This might be a hard coded message given by tomcat. See if it can be easily changed. HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.apache.geronimo.stats.JSR77Servlet.doGet(JSR77Servlet.java:78) javax.servlet.http.HttpServlet.service(HttpServlet.java:595) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.12 logs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1356) Clean up distributionDirectory element in project.xml files as it contains 'incubator'
[ http://issues.apache.org/jira/browse/GERONIMO-1356?page=all ] Matt Hogstrom closed GERONIMO-1356. --- Resolution: Invalid Not applicable to new build environment. Clean up distributionDirectory element in project.xml files as it contains 'incubator' Key: GERONIMO-1356 URL: http://issues.apache.org/jira/browse/GERONIMO-1356 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: buildsystem Reporter: John Sisson Priority: Trivial Fix For: 1.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1078) org.openejb.client.ServerMetadata does not handle IPv6 addresses
[ http://issues.apache.org/jira/browse/GERONIMO-1078?page=all ] Matt Hogstrom updated GERONIMO-1078: Fix Version/s: Wish List (was: 1.2) For future consideration. org.openejb.client.ServerMetadata does not handle IPv6 addresses Key: GERONIMO-1078 URL: http://issues.apache.org/jira/browse/GERONIMO-1078 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 1.0-M5 Reporter: John Sisson Priority: Trivial Fix For: Wish List Noticed that readExternal(..) and writeExternal(..) ServerMetadata class only handles IPv4 addresses. Need to consider compatibility with existing OpenEJB clients when fixing this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1792) Ant Tasks Mirror of Maven Plugins
[ http://issues.apache.org/jira/browse/GERONIMO-1792?page=all ] Matt Hogstrom updated GERONIMO-1792: Fix Version/s: Wish List (was: 1.2) Moving to a future release. Ant Tasks Mirror of Maven Plugins - Key: GERONIMO-1792 URL: http://issues.apache.org/jira/browse/GERONIMO-1792 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, startup/shutdown Affects Versions: 1.0 Environment: Ant Reporter: Heinie Barnard Assigned To: Donald Woods Priority: Minor Fix For: Wish List Attachments: GeronimoAntTasks.zip This are Ant Tasks mirrors of the Maven Plugin * StartServer * StopServer * StartRemoteServer * StopRemoteServer * UndeployModule * StopModule * StartModule * DistributeModule -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
