Hi,
My database is sybaseASE12.5,and I use the activemq4.1.0.
The following is the series of messages when I start broker:
- ActiveMQ 4.1.0-incubator JMS Message Broker (xuke) is starting
- For help or more information please see:
http://incubator.apache.org/activemq/
- Database driver
[
http://issues.apache.org/jira/browse/GERONIMO-1642?page=comments#action_12459220
]
David Jencks commented on GERONIMO-1642:
I'm really not sure this is still a problem. For instance JettyModuleBuilder
AFAICT throws an exception
[ http://issues.apache.org/jira/browse/GERONIMO-1642?page=all ]
Rakesh Midha updated GERONIMO-1642:
---
Attachment: namespace1642.patch
I tried this and found following results
-
for
[ http://issues.apache.org/jira/browse/GERONIMO-1642?page=all ]
Rakesh Midha updated GERONIMO-1642:
---
Patch Info: [Patch Available]
Fix Version/s: 2.0
(was: 1.1.x)
Assignee: (was: Rakesh Midha)
Hello David
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm satisfied
with the results. All modes of operation functioned well (SLSB,
Direct, EJB and JPA). I toned all the logs down to
I will be out of the office starting 12/18/2006 and will not return until
01/02/2007.
I'm on vacation.
Are we not including J2EE Management 1.1 in this list because of
JSR77.3.5.0.1 - deploymentDescriptor?
Thanks
Anita
--- [EMAIL PROTECTED] wrote:
Author: hogstrom
Date: Sun Dec 17 21:53:00 2006
New Revision: 488131
URL: http://svn.apache.org/viewvc?view=revrev=488131
Log:
Added
Re: Bug in ScritpComponent when using script attribute
Key: SM-781
URL: https://issues.apache.org/activemq/browse/SM-781
Project: ServiceMix
Issue Type: Bug
Components:
[ https://issues.apache.org/activemq/browse/SM-781?page=all ]
Andrea Zoppello updated SM-781:
---
Attachment: ScriptComponent.java.diff
The file attached is the patch proposed to resolve the problem described
Re: Bug in ScritpComponent when using script
[ http://issues.apache.org/jira/browse/GERONIMO-2669?page=all ]
Gianny Damour closed GERONIMO-2669.
---
Fix Version/s: 2.0-M2
(was: 2.0)
Resolution: Fixed
Thanks for having fixed the build and opened this JIRA David.
I have
Looks good. +1.
On Dec 18, 2006, at 3:57 AM, Matt Hogstrom wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work
was done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm
satisfied with the results. All modes of operation
On Dec 18, 2006, at 3:57 AM, Matt Hogstrom wrote:
Please review and cast your vote early. The faster we determine
this build is good or if there is an issue the better.
Thanks in advance for all your help in this effort.
This vote will conclude at 0400 ET on Dec 21 (unless all you PMC
+1
Matt Hogstrom wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm satisfied
with the results. All modes of operation functioned well (SLSB, Direct,
EJB and JPA). I
I tried tomcat6-jee5:
-- The log file is empty.
-- Is it necessary to change all the log levels from WARN to ERROR (rev
488143)?
Thanks
Anita
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of
Which log is empty?
anita kulshreshtha wrote:
I tried tomcat6-jee5:
-- The log file is empty.
-- Is it necessary to change all the log levels from WARN to ERROR (rev
488143)?
Thanks
Anita
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
All,
I have prepared 2.0-M1 for release. Of
Hi All,
I have two basic comments/questions.
1- I see a bunch of INFO messages in both Tomcat and Jetty at startup, not a
show stopper for this release.
2- Deployment on Jetty is not behaving exactly as I expected. Not sure if I
messed up the dep plans given the new specs, however this same
+1
I tried all 4 assemblies and deployed a simple web application to each.
All went as expected. As already mentioned, there are some info
messages (more with tomcat than jetty).
Joe
Matt Hogstrom wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done
geronimo.log is empty on both Jetty and Tomcat
Cheers!
Hernan
Jeff Genender wrote:
Which log is empty?
anita kulshreshtha wrote:
I tried tomcat6-jee5:
-- The log file is empty.
-- Is it necessary to change all the log levels from WARN to ERROR (rev
488143)?
Thanks
Anita
--- Matt
If you want more extensive debugging you can crank the log level up.
for M2 I want to look at the log in a bit more detail as a user I
would expect some server started messages and the like and I think we
need to tweak the server to get that level of usability.
The log does work which is
All,
I opened this thread for general comments and questions about the
release. Let's have the discussions here and leave the vote thread
for +/- voting only so it will be easier to process
Thanks.
Matt Hogstrom
[EMAIL PROTECTED]
It would be nice if this was included in 2.0-M1. It will allow clean
shutdown of the server without changing all the log levels from WARN to
ERROR.
Thanks
Anita
--- [EMAIL PROTECTED] wrote:
Author: dims
Date: Sun Dec 17 19:18:42 2006
New Revision: 488106
URL:
On Dec 18, 2006, at 9:49 AM, Kevan Miller wrote:
There's a source file missing a license header. Not sure if it was
added after my last scan of the code or if I just missed it.
Anyway, it needs to be fixed.
All servers start. I'm getting some [info] log messages sent to
STDOUT, but I
+1
Best wishes,
Paul
On 12/18/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm satisfied
with the results. All modes of operation
Schemas generated by xbean are sometimes invalid (xs:any conflict)
--
Key: XBEAN-66
URL: http://issues.apache.org/jira/browse/XBEAN-66
Project: XBean
Issue Type: Bug
[ http://issues.apache.org/jira/browse/XBEAN-66?page=all ]
Guillaume Nodet closed XBEAN-66.
Resolution: Fixed
Fixed as part of XBEAN-65
Schemas generated by xbean are sometimes invalid (xs:any conflict)
When an xbean tag is mispelled, a CNFE is thrown instead of a more explicit
exception
-
Key: XBEAN-67
URL: http://issues.apache.org/jira/browse/XBEAN-67
Project:
[ http://issues.apache.org/jira/browse/XBEAN-67?page=all ]
Guillaume Nodet closed XBEAN-67.
Resolution: Fixed
Author: gnodet
Date: Mon Dec 18 07:57:04 2006
New Revision: 488309
URL: http://svn.apache.org/viewvc?view=revrev=488309
Log:
XBEAN-67: When an
Geronimo - Monday, December 18, 2006
5 Patches in RTC
[GERONIMO-2638] Improve ModuleBuilder and ConfigurationBuilder interfaces
to replace use of JarFile
- Assignee: Sachin Patel
- Reporter: Sachin Patel
- Created: Thu Dec 07 23:41:31 GMT 2006
- Updated: Mon Dec
Upgrade to QDox 1.6.1 for better java 5 support
Key: XBEAN-68
URL: http://issues.apache.org/jira/browse/XBEAN-68
Project: XBean
Issue Type: Improvement
Components: maven-plugin,
[ http://issues.apache.org/jira/browse/XBEAN-68?page=all ]
Guillaume Nodet closed XBEAN-68.
Resolution: Fixed
Author: gnodet
Date: Mon Dec 18 08:01:55 2006
New Revision: 488310
URL: http://svn.apache.org/viewvc?view=revrev=488310
Log:
Remove exclusions
[
http://issues.apache.org/jira/browse/XBEAN-68?page=comments#action_12459397 ]
Guillaume Nodet commented on XBEAN-68:
--
Oops, wrong revision. The following is the correct one:
Author: gnodet
Date: Mon Dec 18 08:13:55 2006
New Revision:
The geronimo.log is empty. It does not contain system information.
Thanks
Anita
--- Jeff Genender [EMAIL PROTECTED] wrote:
Which log is empty?
anita kulshreshtha wrote:
I tried tomcat6-jee5:
-- The log file is empty.
-- Is it necessary to change all the log levels from WARN to
Problem when compiling vs2005-activemq project with unsafe method call
--
Key: AMQ-1101
URL: https://issues.apache.org/activemq/browse/AMQ-1101
Project: ActiveMQ
Issue
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important enough to deserver a new
release (the generated schemas can not be validated).
[ ] +1 Start xbean 2.8 release
+1
On 12/18/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important enough to deserver a new
release (the generated schemas
anita,
If I turn logging up to INFO in var/log/server-log4j.properties I get
information in the log.
On Dec 18, 2006, at 10:37 AM, Matt Hogstrom wrote:
All,
I opened this thread for general comments and questions about the
release. Let's have the discussions here and leave the vote
Streaming API for XML and JAXB integration
--
Key: GERONIMO-2671
URL: http://issues.apache.org/jira/browse/GERONIMO-2671
Project: Geronimo
Issue Type: New Feature
Security Level: public (Regular
[ http://issues.apache.org/jira/browse/GERONIMO-2671?page=all ]
Jarek Gawor updated GERONIMO-2671:
--
Attachment: stax-jaxb.patch
Streaming API for XML and JAXB integration
--
Key: GERONIMO-2671
[ http://issues.apache.org/jira/browse/GERONIMO-2667?page=all ]
Jarek Gawor closed GERONIMO-2667.
-
Resolution: Duplicate
https://issues.apache.org/jira/browse/GERONIMO-2671 contains updated patch with
JAXB support.
Streaming API for XML integration
+1
On 12/18/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important enough to deserver a new
release (the generated schemas
Found no show-stopping issues for a milestone.
+1
Cheers
Prasad
On 12/18/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm satisfied
with
On Dec 18, 2006, at 10:46 AM, Matt Hogstrom wrote:
On Dec 18, 2006, at 9:49 AM, Kevan Miller wrote:
There's a source file missing a license header. Not sure if it was
added after my last scan of the code or if I just missed it.
Anyway, it needs to be fixed.
All servers start. I'm
Matt,
I had to change the following lines in server-log4j.properties to
get system information logged:
log4j.rootLogger=INFO, CONSOLE, FILE
log4j.appender.FILE.Threshold=INFO
In addition I see the following stack trace during shutdown. A fix
for this is already available in rev 488106:
I think its a preference. At this point I think M1 is what it is and
we'll update the Wiki with known issues.
On Dec 18, 2006, at 12:49 PM, anita kulshreshtha wrote:
Matt,
I had to change the following lines in server-log4j.properties to
get system information logged:
Thanks for finding this Kevan.
I reposted the source, there are no modules.
Updated source is in:
http://people.apache.org/~hogstrom/2.0-M1/
Thanks for finding this.
On Dec 18, 2006, at 12:36 PM, Kevan Miller wrote:
On Dec 18, 2006, at 10:46 AM, Matt Hogstrom wrote:
On Dec 18, 2006, at
On Dec 18, 2006, at 11:25 AM, Guillaume Nodet wrote:
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important enough to deserver a new
release (the generated schemas
With the addition of a license header to geronimo/server/tags/2.0-M1/
testsuite/deployment-testsuite/manifestcp/manifestcp-ejb/src/main/
resources/META-INF/ejb-jar.xml, I'm +1.
--kevan
On 12/18/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 18, 2006, at 11:25 AM, Guillaume Nodet wrote:
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important
I am facing a really bad performance of ActiveMq on linux box.
When running on windows 1000 transactions are taking 2 seconds and when
running on Linux same are taking 40 sec.
Please if anybody can tell me solution to performance issue.
Here is the code i am using to send and receive the
On Dec 18, 2006, at 1:31 PM, Guillaume Nodet wrote:
On 12/18/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 18, 2006, at 11:25 AM, Guillaume Nodet wrote:
I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the
Is 4.1 released? If not, what is rlelease plans?
-Sileshi
Hiram Chirino wrote:
On 10/4/06, yaussy [EMAIL PROTECTED] wrote:
Sorry about that. I'd forgotten about the wireformat stuff. Looks like
you
can set AMQ 4.1 minimum wire format to 1 and then it will connect to AMQ
4.0.2 (still
4.1 has been released.
-Brian
On Dec 18, 2006, at 11:40 AM, sileshi wrote:
Is 4.1 released? If not, what is rlelease plans?
-Sileshi
Hiram Chirino wrote:
On 10/4/06, yaussy [EMAIL PROTECTED] wrote:
Sorry about that. I'd forgotten about the wireformat stuff.
Looks like
you
can set
Re-deploy with In-Only Mep
--
Key: SM-782
URL: https://issues.apache.org/activemq/browse/SM-782
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jms
Affects Versions: 3.1
Environment:
I've fixed the missing / bad ASF headers and use the new maven
plugin to generate LICENSE/NOTICE file.
On 12/18/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 18, 2006, at 1:31 PM, Guillaume Nodet wrote:
On 12/18/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 18, 2006, at 11:25 AM,
Ugh... this is why I don't like all that moving of branches to tags...
A tag or label should never be modified... its a point in time,
not indented (or expected) to be changed.
I believe that we would be doing ourselves a major favor by following
some SCM best practices... moving branches
+1
I don't think we should spend too much time on this release. Lets
just note the issues we run into and try to fix them for M2, possibly
implementing more build support to help us avoid more legal-related
issues, which seem to be the bulk of problems we run into.
--jason
On Dec 18,
Rerouting to this thread from [VOTE] 2.0-M1 Release
Hi All,
I have two basic comments/questions.
1- I see a bunch of INFO messages in both Tomcat and Jetty at startup, not a
show stopper for this release.
2- Deployment on Jetty is not behaving exactly as I expected. Not sure if I
messed up
[ http://issues.apache.org/jira/browse/GERONIMO-2648?page=all ]
Tim McConnell closed GERONIMO-2648.
---
Resolution: Fixed
Integrated into 2.0-M1 build
Integrate JSF 1.2 into 2.0-M1
-
Key: GERONIMO-2648
On Dec 18, 2006, at 3:44 PM, Guillaume Nodet wrote:
I've fixed the missing / bad ASF headers and use the new maven
plugin to generate LICENSE/NOTICE file.
Looks like the following still needs some attention:
xbean-spring-v1/pom.xml
These all have old style license headers. Sorry, I didn't
On Dec 18, 2006, at 3:45 PM, Jason Dillon wrote:
Ugh... this is why I don't like all that moving of branches to tags...
A tag or label should never be modified... its a point in time,
not indented (or expected) to be changed.
I believe that we would be doing ourselves a major favor by
I'm trying to build the OpenEJB 2.2 release so that I can continue
working on Geronimo CTS/TCK automation... but the openejb-2.2 release
tag is not buildable in a clean environment:
snip
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]
Infinite loop from broker's network connector when using multiple durable
subscribers (topics) with msg selector.
-
Key: AMQ-1102
URL:
however, binary seems to execute fine.
--
(x86 linux - FC5, sun jdk 1.6.0,
apache-servicemix-3.0-incubating-src.tar.gz)
mvn -Dmaven.test.skip=true -Dprofile=step2 install
...
[INFO]
[ https://issues.apache.org/activemq/browse/SM-521?page=all ]
Guillaume Nodet closed SM-521.
--
Resolution: Duplicate
Thread pools can be configured with the ExecutorFactory on the jbi container.
Throttling should be configurable on a per endpoint basis.
[ https://issues.apache.org/activemq/browse/SM-745?page=all ]
Guillaume Nodet updated SM-745:
---
Fix Version/s: (was: 3.1)
Allow usage of other JMS providers than ActiveMQ
Key: SM-745
It seems we use an older version of jsr223.
It has just gone final a few days ago, and there are lots
of changes from the version we currently use.
Could you please raise a JIRA for that ?
On 12/18/06, timbo [EMAIL PROTECTED] wrote:
however, binary seems to execute fine.
Done :)
On 12/18/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 18, 2006, at 3:44 PM, Guillaume Nodet wrote:
I've fixed the missing / bad ASF headers and use the new maven
plugin to generate LICENSE/NOTICE file.
Looks like the following still needs some attention:
[
https://issues.apache.org/activemq/browse/SM-782?page=comments#action_37723 ]
Guillaume Nodet commented on SM-782:
I think the problem comes from the fact that the endpoint is re-deployed.
In such a case, another instance of the endpoint
On Dec 18, 2006, at 3:45 PM, Jason Dillon wrote:
Ugh... this is why I don't like all that moving of branches to tags...
I agree
A tag or label should never be modified... its a point in time,
not indented (or expected) to be changed.
I believe that we would be doing ourselves a major
[ https://issues.apache.org/activemq/browse/SM-749?page=all ]
Guillaume Nodet updated SM-749:
---
Fix Version/s: (was: incubation)
JSR181 component does not generate WSDL types for JAXB2-annotated classes
[ https://issues.apache.org/activemq/browse/SM-704?page=all ]
Guillaume Nodet resolved SM-704.
Resolution: Fixed
Assignee: Guillaume Nodet
FTPPoller Improvements
--
Key: SM-704
URL:
build fails under java 6
-
Key: SM-783
URL: https://issues.apache.org/activemq/browse/SM-783
Project: ServiceMix
Issue Type: Bug
Components: servicemix-components
Affects Versions: 3.0
On Dec 18, 2006, at 1:49 PM, Kevan Miller wrote:
A tag or label should never be modified... its a point in
time, not indented (or expected) to be changed.
I'm sympathetic to your concern. However, we don't (to my
knowledge) have a documented release process for our projects. So,
we're
On Dec 18, 2006, at 2:59 PM, Matt Hogstrom wrote:
Dain ran into a similar problem where while releasing he had an
issue that a utility as part of the release process caused him to
make a change to source because of a variable name.
Was this before or after the release tag was made? Can you
+1
-David
On Dec 18, 2006, at 12:57 AM, Matt Hogstrom wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work
was done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm
satisfied with the results. All modes of operation functioned
On Dec 18, 2006, at 2:59 PM, Matt Hogstrom wrote:
Process of branching and tagging (we already have a plethora of
discussion...I think this needs to get on a Wiki)
- includes tags and modifications
Discussion, proposal, resolution and final vote.
On Dec 18, 2006, at 1:51 PM, Jason Dillon wrote:
I'm trying to build the OpenEJB 2.2 release so that I can continue
working on Geronimo CTS/TCK automation... but the openejb-2.2
release tag is not buildable in a clean environment:
[...]
I am not sure that this is a priority for many folks,
For the M1 release I would have said close enough and made the final
release from trunk.
But changing the tag is harmful by itself by setting precedence...
something which should not be followed, yet unless people understand
why, they will just continue along those bad practices.
And
On Dec 18, 2006, at 5:15 PM, David Blevins wrote:
On Dec 18, 2006, at 1:51 PM, Jason Dillon wrote:
I'm trying to build the OpenEJB 2.2 release so that I can continue
working on Geronimo CTS/TCK automation... but the openejb-2.2
release tag is not buildable in a clean environment:
[...]
I
I will be out of the office starting 16/12/2006 and will not return until
02/01/2007.
I will respond to your message when I return.
--- Davanum Srinivas [EMAIL PROTECTED] wrote:
Anita,
Anyone who builds geronimo from scratch is likely to into into
problem. We can't really tell people they can't use the jars they
build themselves on their boxes and have to use the published
SNAPSHOT
jars.
We do not tell people
On Dec 18, 2006, at 10:37 PM, Jason Dillon wrote:
For the M1 release I would have said close enough and made the
final release from trunk.
But changing the tag is harmful by itself by setting precedence...
something which should not be followed, yet unless people
understand why, they
A note, please do not add headers to the following:
==package-info.java (./xbean-finder/src/test/java/org/acme/foo/
package-info.java)
==java.io.InputStream (./xbean-finder/src/test/resources/META-INF/
java.io.InputStream)
==java.io.OutputStream (./xbean-finder/src/test/resources/META-INF/
Improving the Deployment schema documentation -geronimo-application.xsd
---
Key: GERONIMO-2672
URL: http://issues.apache.org/jira/browse/GERONIMO-2672
Project: Geronimo
+1
Jacek
On 12/18/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
All,
I have prepared 2.0-M1 for release. Of course all the hard work was
done by the lot of y'all :)
I have tested DayTrader 2.0-SNAPSHOT on this build and I'm satisfied
with the results. All modes of operation functioned well
85 matches
Mail list logo
