RE: [jira] Created: (AMQ-899) mvn test fails with com.thoughtworks.qdox.parser.ParseException: syntax error @[90,25] in file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConnect
The following helped me to fix my local build:
[EMAIL PROTECTED]:/workplace/fateev/activemq-head/trunk svn diff
Index: pom.xml
===
--- pom.xml (revision 437779)
+++ pom.xml (working copy)
@@ -495,17 +495,20 @@
dependency
groupIdxmlbeans/groupId
artifactIdxbean/artifactId
-version${xmlbeans-version}/version
+!--version${xmlbeans-version}/version--
+version2.0.0-beta1/version
/dependency
dependency
groupIdxmlbeans/groupId
artifactIdxmlpublic/artifactId
-version${xmlbeans-version}/version
+version2.0.0-beta1/version
+!--version${xmlbeans-version}/version--
/dependency
dependency
groupIdxmlbeans/groupId
artifactIdxbean_xpath/artifactId
-version${xmlbeans-version}/version
+version2.0.0-beta1/version
+!--version${xmlbeans-version}/version--
/dependency
!-- For Stax --
[EMAIL PROTECTED]:/workplace/fateev/activemq-head/trunk
-Original Message-
From: Sepand M [mailto:[EMAIL PROTECTED]
Sent: Monday, August 28, 2006 12:22 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: [jira] Created: (AMQ-899) mvn test fails with
com.thoughtworks.qdox.parser.ParseException: syntax error @[90,25] in
file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConnector.java
I'm getting the same thing on a clean checkout (as well as every other checkout
I have).
Anyone know what's going on?
On 8/28/06, Maxim Fateev (JIRA) [EMAIL PROTECTED] wrote:
mvn test fails with com.thoughtworks.qdox.parser.ParseException:
syntax error @[90,25] in
file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/J
msConnector.java
--
--
-
Key: AMQ-899
URL: https://issues.apache.org/activemq/browse/AMQ-899
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.x
Environment: Linux (RHEL3) and Windows XP
Reporter: Maxim Fateev
svn co https://svn.apache.org/repos/asf/incubator/activemq/trunk
Atrunk/README.txt
U trunk
Checked out revision 437779.
[EMAIL PROTECTED]:/workplace/fateev/activemq-head ls trunk/
[EMAIL PROTECTED]:/workplace/fateev/activemq-head cd trunk/activemq-core
[EMAIL PROTECTED]:/workplace/fateev/activemq-head/trunk/activemq-core mvn
test [INFO] Scanning for projects...
[INFO]
--
--
[INFO] Building ActiveMQ :: Core
[INFO]task-segment: [test]
[INFO]
--
-- [INFO] artifact
org.apache.maven.plugins:maven-resources-plugin: checking for updates
from apache-snapshots [INFO] snapshot
org.apache.maven.plugins:maven-resources-plugin:2.3-SNAPSHOT: checking for
updates from apache-snapshots ...
...
...
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/activemq
/maven-gram-plugin/4.1-incubator-SNAPSHOT/maven-gram-plugin-4.1-incuba
tor-20060803.174437-6.jar
6K downloaded
[WARNING] While downloading javacc:javacc:3.2
This artifact has been relocated to net.java.dev.javacc:javacc:3.2.
[INFO] [javacc:javacc {execution: default}] Java Compiler Compiler
Version 3.2 (Parser Generator) (type javacc with no arguments for
help) Reading from file
/workplace/fateev/activemq-head/trunk/activemq-core/src/main/grammar/SelectorParser.jj
. . .
Note: UNICODE_INPUT option is specified. Please make sure you create the
parser/lexer usig a Reader with the correct character encoding.
File TokenMgrError.java does not exist. Will create one.
File ParseException.java does not exist. Will create one.
File Token.java does not exist. Will create one.
File SimpleCharStream.java does not exist. Will create one.
Parser generated successfully.
Downloading:
http://people.apache.org/maven-snapshot-repository/qdox/qdox/1.6/qdox-
1.6.pom [WARNING] Unable to get resource from repository
apache-snapshots (http://people.apache.org/maven-snapshot-repository)
Downloading: http://repository.codehaus.org/qdox/qdox/1.6/qdox-1.6.pom
[WARNING] Unable to get resource from repository codehaus
(http://repository.codehaus.org)
Downloading:
http://dse.amazon.com:8081/proximity/repository/qdox/qdox/1.6/qdox-1.6
.pom
4K downloaded
[INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: checking
for updates from apache-snapshots [INFO] snapshot
org.apache.xbean:xbean-spring:2.6-SNAPSHOT: checking
Issue for 4.x version is not being looked at
I've submitted a patch at Friday against 4.x: http://issues.apache.org/activemq/browse/AMQ-877 But it doesn't show up in the list of outstanding issues for 4.x (https://issues.apache.org/activemq/secure/IssueNavigator.jspa?mode=hiderequestId=11102). Should I resubmit it against 4.1 to get it looked at? Thanks, Maxim.
RE: Pulling consumer design
James, I'm looking into your change (430445) and don't understand how it solves problem of slow consumer. It is essentially still a push model as Queue.dispatch actively pushes messages to subscriptions. Subscriptions store unconsumed messages in pending list. So slow consumer still will get its share of messages. I think temporary workaround could be sharing pending list between all consumers that have same message selector. Maxim. -Original Message- From: James Strachan [mailto:[EMAIL PROTECTED] Sent: Friday, August 11, 2006 1:00 AM To: activemq-dev@geronimo.apache.org Subject: Re: Pulling consumer design Sorry about that, I'd forgotten to run the mvn gram:gram command. Its now in SVN On 8/11/06, Vadim Pesochinsky [EMAIL PROTECTED] wrote: There is a little problem with MessagePullMarshaller not generated / added to svn. I tried to run generator, but withouth much luck. Found this instructions, but I could not find the maven-gram-plugin. Thanks. cd maven-gram-plugin/ mvn install cd ../activemq-openwire-generator/ mvn install cd ../activemq-core mvn gram:gram javax.jms.JMSException: Unknown data type: 20 at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58) at org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1130) at org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1649) at org.apache.activemq.ActiveMQMessageConsumer.sendPullCommand(ActiveMQMessageConsumer.java:605) at org.apache.activemq.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:463) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.runSingleQueue(SingleMessageMultiQueueReceiver.java:185) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.doRun(SingleMessageMultiQueueReceiver.java:141) at com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.run(SingleMessageMultiQueueReceiver.java:124) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Unknown data type: 20 at org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:231) at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:108) at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:142) at org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:82) at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:86) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:45) at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:59) at org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1128) ... 7 more -- View this message in context: http://www.nabble.com/Pulling-consumer-design-tf2086371.html#a5757354 Sent from the ActiveMQ - Dev forum at Nabble.com. -- James --- http://radio.weblogs.com/0112098/
Proposed refactoring to allow alternative persistence mechanisms
Hi,
We were looking at alternate message persistence mechanisms that can
co-exist in current ActiveMQ code base and we are thinking of a mechanism that
is somewhat incompatible with the current MessageStore and PersistenceAdapter
APIs. Unfortunately, the current ActiveMQ broker doesn't allow for such a
change as the PersistenceAdapter and MessageStore interfaces are referenced
directly by the RegionBroker and by both the Queue and Topic region
implementations. Therefore, we are proposing a relatively small backwards
compatible refactoring of the broker code that would eliminate all dependencies
on the PersistenceAdapter and MessageStore interfaces from those classes that
do not use them directly. This refactoring would also allow creation of a
custom Destination implementation that may use an alternative persistence
mechanism on a destination by destination basis (which is exactly what we need
to do).
The main idea behind the refactoring is to replace many references to
PersistenceAdapter with a new interface: DestinationFactory:
public abstract class DestinationFactory {
abstract public Destination createDestination(ConnectionContext
context, ActiveMQDestination destination, DestinationStatistics
destinationStatistics) throws Exception;
abstract public Set getDestinations();
abstract public SubscriptionInfo[]
getAllDurableSubscriptions(ActiveMQTopic topic) throws IOException;
abstract public long getLastMessageBrokerSequenceId() throws
IOException;
abstract public void setRegionBroker(RegionBroker regionBroker);
}
Note that DestinationFactory doesn't mandate any specific persistence
mechanism. The classes that would reference it instead of PersistenceAdapter
are: RegionBroker, AbstractRegion, QueueRegion, and TopicRegion. Also, the
AbstractRegion.createDestination method would be changed from abstract to an
implementation that uses DestinationFactory to create a destination.
BrokerService could be changed to use DestinationFactory if one is
provided. If none is provided, it will create a DestinationFactory
implementation that instantiates Queue and Topic using PersistenceAdapter as it
does currently. Hence, full backwards compatibility will be maintained.
We have a preliminary implementation on local workspace. We can provide
full patch for review. Appreciate your thoughts.
Thanks
Maxim Fateev.
