[jira] [Commented] (AMQ-4428) Don't swallow errors in IntrospectionSupport.setProperty
[
https://issues.apache.org/jira/browse/AMQ-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621998#comment-13621998
]
Christoffer Sawicki commented on AMQ-4428:
--
(I've found that a couple of those assertions are missing, but I've filed
another issue for that (AMQ-4433). I believe there is a problem even assuming
all assertions are in place.)
In the context of setProperty, properties/parameters can be invalid in two ways:
1. The property is missing on the target object. This situation happens a lot
during normal initialization and works fine as is.
2. The property does exist but calling the setter throws an exception. This is
the situation I believe is exceptional and should be logged. With working
assertions the property/parameter will be flagged as invalid, but the
exception—which contains information about why the property value is invalid—is
hidden from the user, making troubleshooting harder.
For reference:
https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/util/IntrospectionSupport.java#L160
I'll do some more research with the unit tests and get back to you.
Thanks for your time!
Don't swallow errors in IntrospectionSupport.setProperty
Key: AMQ-4428
URL: https://issues.apache.org/jira/browse/AMQ-4428
Project: ActiveMQ
Issue Type: Bug
Reporter: Christoffer Sawicki
Priority: Minor
Attachments: 0001-Log-errors-in-IntrospectionSupport.setProperty.patch
`setProperty` currently ends with `… catch (Throwable ignore) \{ return
false; \}`. This is really evil since it can make ActiveMQ ignore invalid
configuration completely silently. I think that errors should at least be
logged. (Is there any case when this isn't wanted?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4428) Don't swallow errors in IntrospectionSupport.setProperty
[
https://issues.apache.org/jira/browse/AMQ-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoffer Sawicki updated AMQ-4428:
-
Description: `setProperty` currently ends with `… catch (Throwable ignore)
\{ return false; \}`. This can make troubleshooting invalid configuration much
harder since the exception (that contains detailed information) is hidden from
the user. (was: `setProperty` currently ends with `… catch (Throwable ignore)
\{ return false; \}`. This is really evil since it can make ActiveMQ ignore
invalid configuration completely silently. I think that errors should at least
be logged. (Is there any case when this isn't wanted?))
Don't swallow errors in IntrospectionSupport.setProperty
Key: AMQ-4428
URL: https://issues.apache.org/jira/browse/AMQ-4428
Project: ActiveMQ
Issue Type: Bug
Reporter: Christoffer Sawicki
Priority: Minor
Attachments: 0001-Log-errors-in-IntrospectionSupport.setProperty.patch
`setProperty` currently ends with `… catch (Throwable ignore) \{ return
false; \}`. This can make troubleshooting invalid configuration much harder
since the exception (that contains detailed information) is hidden from the
user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4435) ActiveMQConnectionFatory should populate consumerFailoverRedeliveryWaitPeriod
Daniel Guggi created AMQ-4435:
-
Summary: ActiveMQConnectionFatory should populate
consumerFailoverRedeliveryWaitPeriod
Key: AMQ-4435
URL: https://issues.apache.org/jira/browse/AMQ-4435
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Daniel Guggi
Priority: Trivial
ActiveMQConnectionFactory contains consumerFailoverRedeliveryWaitPeriod to be
applied to the connection created - however method populateProperties()
ignores this property.
The following should be added to populateProperties() method
{code}
props.setProperty(consumerFailoverRedeliveryWaitPeriod,
Long.toString(consumerFailoverRedeliveryWaitPeriod));
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is unstable: ActiveMQ-Java7 #173
See https://builds.apache.org/job/ActiveMQ-Java7/173/changes
[jira] [Created] (AMQ-4436) LevelDB compilation warnings
Lionel Cons created AMQ-4436:
Summary: LevelDB compilation warnings
Key: AMQ-4436
URL: https://issues.apache.org/jira/browse/AMQ-4436
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[INFO] --- scala-maven-plugin:3.1.0:compile (default) @ activemq-leveldb-store
---
[INFO] ~activemq/activemq-leveldb-store/src/main/java:-1: info: compiling
[INFO] ~activemq/activemq-leveldb-store/target/generated-sources/proto:-1:
info: compiling
[INFO] ~activemq/activemq-leveldb-store/src/main/scala:-1: info: compiling
[INFO] Compiling 21 source files to
~activemq/activemq-leveldb-store/target/classes at 1365083049736
[INFO] compiler plugin:
BasicArtifact(org.fusesource.jvmassert,jvmassert,1.4,null)
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/DBManager.scala:255:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) =
[WARNING] ^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1103:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1124:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1167:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING] warning: there were 6 feature warnings; re-run with -feature for
details
[WARNING] 5 warnings found
{quote}
This is probably something that is worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4437) JUnit deprecation warnings
Lionel Cons created AMQ-4437:
Summary: JUnit deprecation warnings
Key: AMQ-4437
URL: https://issues.apache.org/jira/browse/AMQ-4437
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[31,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[133,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[192,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[30,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[19,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[73,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[84,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[98,2]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[216,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[251,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[112,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[115,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[37,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQFailoverIssue.java:[95,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[114,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[165,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[217,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-unit-tests/src/test/java/org/apache/activemq/network/NetworkLoopBackTest.java:[26,29]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[57,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[68,8]
[deprecation] Assert in junit.framework has been deprecated
{quote}
This is probably something worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-4436) LevelDB compilation warnings
[
https://issues.apache.org/jira/browse/AMQ-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-4436.
-
Resolution: Duplicate
Patches welcomed, can be attached to previous issue.
LevelDB compilation warnings
Key: AMQ-4436
URL: https://issues.apache.org/jira/browse/AMQ-4436
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[INFO] --- scala-maven-plugin:3.1.0:compile (default) @
activemq-leveldb-store ---
[INFO] ~activemq/activemq-leveldb-store/src/main/java:-1: info: compiling
[INFO] ~activemq/activemq-leveldb-store/target/generated-sources/proto:-1:
info: compiling
[INFO] ~activemq/activemq-leveldb-store/src/main/scala:-1: info: compiling
[INFO] Compiling 21 source files to
~activemq/activemq-leveldb-store/target/classes at 1365083049736
[INFO] compiler plugin:
BasicArtifact(org.fusesource.jvmassert,jvmassert,1.4,null)
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/DBManager.scala:255:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) =
[WARNING] ^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1103:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1124:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING]
~activemq/activemq-leveldb-store/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1167:
warning: non-variable type argument Long in type pattern (Long, Int) is
unchecked since it is eliminated by erasure
[WARNING] case x:(Long, Int) = x
[WARNING]^
[WARNING] warning: there were 6 feature warnings; re-run with -feature for
details
[WARNING] 5 warnings found
{quote}
This is probably something that is worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4435) ActiveMQConnectionFatory should populate consumerFailoverRedeliveryWaitPeriod
[
https://issues.apache.org/jira/browse/AMQ-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4435.
---
Resolution: Fixed
Fix Version/s: 5.9.0
ActiveMQConnectionFatory should populate
consumerFailoverRedeliveryWaitPeriod
---
Key: AMQ-4435
URL: https://issues.apache.org/jira/browse/AMQ-4435
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Daniel Guggi
Priority: Trivial
Fix For: 5.9.0
ActiveMQConnectionFactory contains consumerFailoverRedeliveryWaitPeriod to
be applied to the connection created - however method populateProperties()
ignores this property.
The following should be added to populateProperties() method
{code}
props.setProperty(consumerFailoverRedeliveryWaitPeriod,
Long.toString(consumerFailoverRedeliveryWaitPeriod));
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4437) JUnit deprecation warnings
[
https://issues.apache.org/jira/browse/AMQ-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4437.
---
Resolution: Fixed
Fixed the warnings.
JUnit deprecation warnings
--
Key: AMQ-4437
URL: https://issues.apache.org/jira/browse/AMQ-4437
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel Cons
When compiling the ActiveMQ trunk using Java 7, I get:
{quote}
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[31,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[133,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompVirtualTopicTest.java:[192,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[30,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[19,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[73,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[84,3]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionTest.java:[98,2]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[216,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryTest.java:[251,20]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[112,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-pool/src/test/java/org/apache/activemq/pool/PooledConnectionFactoryMaximumActiveTest.java:[115,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[37,22]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQFailoverIssue.java:[95,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[114,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[165,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-spring/src/test/java/org/apache/activemq/usecases/AMQDeadlockTest3.java:[217,12]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-unit-tests/src/test/java/org/apache/activemq/network/NetworkLoopBackTest.java:[26,29]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[57,8]
[deprecation] Assert in junit.framework has been deprecated
[WARNING]
~activemq/activemq-fileserver/src/test/java/org/apache/activemq/util/HttpBlobTest.java:[68,8]
[deprecation] Assert in junit.framework has been deprecated
{quote}
This is probably something worth fixing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4109) Negative queue counters
[
https://issues.apache.org/jira/browse/AMQ-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622446#comment-13622446
]
mauro rappa commented on AMQ-4109:
--
This issue is still present in AMQ 5.8
Negative queue counters
---
Key: AMQ-4109
URL: https://issues.apache.org/jira/browse/AMQ-4109
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.7.0
Reporter: Markus Hahn
http://{server}:8161/admin/queues.jsp
I get negative numbers in the Number Of Pending Messages. Running a simple
PTP scenario, but am purging the queue right in the middle of the action.
Below's the experiment. 5.7.0 was run out of the box on a CentOS 6.3 with
Java 6.
_
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.DeliveryMode;
import javax.jms.Destination;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageProducer;
import javax.jms.Session;
import javax.jms.TextMessage;
import org.apache.activemq.ActiveMQConnection;
import org.apache.activemq.ActiveMQConnectionFactory;
public class PTPTest {
//static String _url = failover://tcp://activemqtest:61616;
static String _url = ActiveMQConnection.DEFAULT_BROKER_URL;
public void enqueue() throws Exception {
Connection connection = null;
try
{
System.out.println(enqueuing...);
ConnectionFactory connectionFactory =
new ActiveMQConnectionFactory(_url);
connection = connectionFactory.createConnection();
connection.start();
Session s = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
//Session s = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
Destination dest = s.createQueue(Q2);
MessageProducer mp = s.createProducer(dest);
mp.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
for(int num = 1; num = 100;num++) {
String txt = this is message # + num;
TextMessage tmsg = s.createTextMessage(txt);
mp.send(tmsg);
Thread.sleep(10);
//System.out.printf( %s\n, txt);
}
}
finally {
if (null != connection) {
connection.close();
}
}
}
public void dequeue(int id) throws Exception {
Connection connection = null;
try {
ConnectionFactory connectionFactory = new
ActiveMQConnectionFactory(_url);
connection = connectionFactory.createConnection();
connection.start();
Session session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
Destination destination = session.createQueue(Q2);
MessageConsumer consumer =
session.createConsumer(destination);
for(;;) {
Message msg = consumer.receive();
TextMessage tmsg = (TextMessage)msg;
String txt = tmsg.getText();
System.out.printf( [%d] '%s', %s, %s\n,
id, txt,
tmsg.getJMSMessageID(),
tmsg.getJMSDestination());
Thread.sleep(1000);
}
}
finally {
connection.close();
}
}
public void exec() throws Exception {
Thread ethrd, dthrds[];
ethrd = new Thread() {
public void run() {
try {
enqueue();
}
catch (Exception e) {
e.printStackTrace();
}
}
};
ethrd.start();
Thread.sleep(1000);
final int D_COUNT = 4;
dthrds = new Thread[D_COUNT];
for (int i = 0; i dthrds.length; i++) {
final int ii = i;
dthrds[i] = new Thread() {
public void run() {
try {
[jira] [Updated] (AMQ-4356) unsubcribes DurableSuscriber does not work well with Virtual Topics
[ https://issues.apache.org/jira/browse/AMQ-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-4356: -- Fix Version/s: 5.9.0 unsubcribes DurableSuscriber does not work well with Virtual Topics - Key: AMQ-4356 URL: https://issues.apache.org/jira/browse/AMQ-4356 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: With kahaDb store Reporter: Federico Weisse Fix For: 5.9.0 We have a Virtual Topic with 2 consumers then we use a DurableSubscriber to the topic (to use it as a normal topic) when we call session.unsubscribe the methods ends ok and the DurableSubscribers disappears(from the webConsole) but the storePercentUsage does't decrements and when we restart the broker durableSuscribers are there again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4356) unsubcribes DurableSuscriber does not work well with Virtual Topics
[ https://issues.apache.org/jira/browse/AMQ-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622697#comment-13622697 ] Timothy Bish commented on AMQ-4356: --- I have a test case that can reproduce this now. unsubcribes DurableSuscriber does not work well with Virtual Topics - Key: AMQ-4356 URL: https://issues.apache.org/jira/browse/AMQ-4356 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: With kahaDb store Reporter: Federico Weisse Fix For: 5.9.0 We have a Virtual Topic with 2 consumers then we use a DurableSubscriber to the topic (to use it as a normal topic) when we call session.unsubscribe the methods ends ok and the DurableSubscribers disappears(from the webConsole) but the storePercentUsage does't decrements and when we restart the broker durableSuscribers are there again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4439) Stomp 1.1 connections ignore persistent
Trey Hyde created AMQ-4439: -- Summary: Stomp 1.1 connections ignore persistent Key: AMQ-4439 URL: https://issues.apache.org/jira/browse/AMQ-4439 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.7.0 Reporter: Trey Hyde -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4356) unsubcribes DurableSuscriber does not work well with Virtual Topics
[ https://issues.apache.org/jira/browse/AMQ-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4356. --- Resolution: Fixed Fix and test added on trunk, should appear in the next nightly 5.9 unsubcribes DurableSuscriber does not work well with Virtual Topics - Key: AMQ-4356 URL: https://issues.apache.org/jira/browse/AMQ-4356 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: With kahaDb store Reporter: Federico Weisse Assignee: Timothy Bish Fix For: 5.9.0 We have a Virtual Topic with 2 consumers then we use a DurableSubscriber to the topic (to use it as a normal topic) when we call session.unsubscribe the methods ends ok and the DurableSubscribers disappears(from the webConsole) but the storePercentUsage does't decrements and when we restart the broker durableSuscribers are there again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4439) Stomp 1.1 connections ignore persistent option
[ https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trey Hyde updated AMQ-4439: --- Description: Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option on the send call is ignored. Set accept-version to 1.0 and messages get get set as persistent appropriately. Summary: Stomp 1.1 connections ignore persistent option (was: Stomp 1.1 connections ignore persistent) Stomp 1.1 connections ignore persistent option Key: AMQ-4439 URL: https://issues.apache.org/jira/browse/AMQ-4439 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.7.0 Reporter: Trey Hyde Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option on the send call is ignored. Set accept-version to 1.0 and messages get get set as persistent appropriately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4439) Stomp 1.1 connections ignore persistent option
[ https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622749#comment-13622749 ] Timothy Bish commented on AMQ-4439: --- Please create a test case. Stomp 1.1 connections ignore persistent option Key: AMQ-4439 URL: https://issues.apache.org/jira/browse/AMQ-4439 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.7.0 Reporter: Trey Hyde Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option on the send call is ignored. Set accept-version to 1.0 and messages get get set as persistent appropriately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-4417) Unbalanced usage Exception in Valve.decrement
[ https://issues.apache.org/jira/browse/AMQ-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4417. - Resolution: Cannot Reproduce No test case provided, code rewritten in later releases. Unbalanced usage Exception in Valve.decrement - Key: AMQ-4417 URL: https://issues.apache.org/jira/browse/AMQ-4417 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.4.2 Reporter: Vincent Baudry One of our production node running ActiveMQ shows a permanent error log every milisecond : Exception in thread VMTransport java.lang.IllegalStateException: Unbalanced usage: -274090111 at org.apache.activemq.thread.Valve.decrement(Valve.java:113) at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:210) at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) at java.lang.Thread.run(Thread.java:811) The value behind unbalanced usage keeping moving but globally getting decremented over time. We are for now unable to see the side effect on the app, which is still running, except the CPU usage going through the roof, probably because of this constant logging. As the log doesn't have a root in our code, it's hard to understand what's gone wrong initially, and if it might be linked to our usage of ActiveMQ. I've read the source code but can't understand why the valve usage int has gone initially negative. But it seems to me that when it has gone once negative, the only way to have the broker work fine again is to restart the server to reinitialize this value (as all subsequent iterate() / increment() calls will throw/catch an exception due to usage negative value and finally hit the decrement() method ). As we don't have a scenario to reproduce the bug, I don't expect you to find a solution to it right now, but I wanted to file it in case anyone encounter the same bug and has the way to reproduce it. And also I would be glad to have answers to the following questions, if possible : - Do you have any clues concerning this issue ? Things I could investigate further ? - Doest it seem normal to you that my exception log starts in a Thread.run() then plugged to the PooledTaskRunner mechanism ? - What kind of ActiveMQ tasks run using this PooledTaskRunner / VmTransport.iterate() mechanism ? All AMQ tasks ? Only enqueueing/dequeueing tasks ? Internal tasks ? - Is it possible that some enqueueing/dequeueing tasks still work fine when in this state ? Is this faulty valve not shared by all producers connecting to the broker via vm:// ? To give you a little technical context, we use this broker with a spring producer using Spring JmsTemplate through vm://transport -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4438) Add uptime to bstat output
[ https://issues.apache.org/jira/browse/AMQ-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4438. --- Resolution: Fixed Assignee: Timothy Bish added on trunk. Add uptime to bstat output -- Key: AMQ-4438 URL: https://issues.apache.org/jira/browse/AMQ-4438 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.8.0 Reporter: Gary Tully Assignee: Timothy Bish Fix For: 5.9.0 bstat command would benefit from displaying the new uptime attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (AMQ-4318) activemq-broker throws KahaDB error
[ https://issues.apache.org/jira/browse/AMQ-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jesb reopened AMQ-4318: --- activemq-broker throws KahaDB error --- Key: AMQ-4318 URL: https://issues.apache.org/jira/browse/AMQ-4318 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: jesb I just tried updating to 2.8.0 using the new activemq-broker and activemq-client modules instead of the previous activemq-core and get a KahaDB exception (see below). Using activemq-all works. Just naively trying add the latest kahadb to my pom didn't correct the issue. I'm making the following calls: ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory(vm://localhost); connection = connectionFactory.createConnection(); connection.start(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); 364 [main] ERROR org.apache.activemq.broker.BrokerService - Failed to start Apache ActiveMQ (localhost, null). Reason: ava.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter java.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39) at org.apache.activemq.broker.BrokerService.createPersistenceAdapter(BrokerService.java:2215) at org.apache.activemq.broker.BrokerService.getPersistenceAdapter(BrokerService.java:) at org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:592) at org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:587) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:552) at org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:124) at org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:54) at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64) at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:250) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:265) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:238) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:184) at com.boeing.uclass.mcs.comm.UclassJMSCommManager.start(UclassJMSCommManager.java:100) at com.boeing.uclass.uclass.inttest.CommListenerTest.SenderListenerTest(CommListenerTest.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[jira] [Closed] (AMQ-4318) activemq-broker throws KahaDB error
[ https://issues.apache.org/jira/browse/AMQ-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jesb closed AMQ-4318. - Resolution: Not A Problem activemq-broker throws KahaDB error --- Key: AMQ-4318 URL: https://issues.apache.org/jira/browse/AMQ-4318 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: jesb I just tried updating to 2.8.0 using the new activemq-broker and activemq-client modules instead of the previous activemq-core and get a KahaDB exception (see below). Using activemq-all works. Just naively trying add the latest kahadb to my pom didn't correct the issue. I'm making the following calls: ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory(vm://localhost); connection = connectionFactory.createConnection(); connection.start(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); 364 [main] ERROR org.apache.activemq.broker.BrokerService - Failed to start Apache ActiveMQ (localhost, null). Reason: ava.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter java.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39) at org.apache.activemq.broker.BrokerService.createPersistenceAdapter(BrokerService.java:2215) at org.apache.activemq.broker.BrokerService.getPersistenceAdapter(BrokerService.java:) at org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:592) at org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:587) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:552) at org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:124) at org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:54) at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64) at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:250) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:265) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:238) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at
[jira] [Updated] (AMQ-4318) activemq-broker throws KahaDB error
[ https://issues.apache.org/jira/browse/AMQ-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jesb updated AMQ-4318: -- Description: I just tried updating to 2.8.0 using the new activemq-broker and activemq-client modules instead of the previous activemq-core and get a KahaDB exception (see below). Using activemq-all works. Just naively trying add the latest kahadb to my pom didn't correct the issue. I'm making the following calls: ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory(vm://localhost); connection = connectionFactory.createConnection(); connection.start(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); 364 [main] ERROR org.apache.activemq.broker.BrokerService - Failed to start Apache ActiveMQ (localhost, null). Reason: ava.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter java.io.IOException: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39) at org.apache.activemq.broker.BrokerService.createPersistenceAdapter(BrokerService.java:2215) at org.apache.activemq.broker.BrokerService.getPersistenceAdapter(BrokerService.java:) at org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:592) at org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:587) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:552) at org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:124) at org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:54) at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64) at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:250) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:265) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:238) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) Caused by:
Build failed in Jenkins: ActiveMQ-Java7 » ActiveMQ :: Broker #174
See https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-broker/174/changes Changes: [tabish] fix and test for: https://issues.apache.org/jira/browse/AMQ-4356 The actual Durable subscription wasn't getting removed from the Store so on restart they were recovered. -- [INFO] Downloading: http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom [WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 [INFO] [INFO] Building ActiveMQ :: Broker 5.9-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-broker --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-broker --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-broker --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-broker --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 7 resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-broker --- [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-broker --- [INFO] Compiling 383 source files to https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-broker/ws/target/classes [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-broker --- [INFO] [INFO] Compiling 9 source files to https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-broker/ws/target/test-classes [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-broker --- [INFO] [INFO] Surefire report directory: https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-broker/ws/target/surefire-reports --- T E S T S --- --- T E S T S --- [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-broker --- Running org.apache.activemq.JmsQueueTransactionTest Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.829 sec Results : Tests run: 18, Failures: 0, Errors: 0, Skipped: 0
Build failed in Jenkins: ActiveMQ-Java7 #174
See https://builds.apache.org/job/ActiveMQ-Java7/174/changes Changes: [tabish] fix for: https://issues.apache.org/jira/browse/AMQ-4438 [tabish] fix and test for: https://issues.apache.org/jira/browse/AMQ-4356 The actual Durable subscription wasn't getting removed from the Store so on restart they were recovered. [tabish] fix junit warnings. https://issues.apache.org/jira/browse/AMQ-4437 [tabish] fix for: https://issues.apache.org/jira/browse/AMQ-4435 [gtully] add validation of ws tranpsort in karaf -- [...truncated 5722 lines...] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-blueprint --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ activemq-blueprint --- [WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT : Instructions in Export-Package that are never used: org\.apache\.activemq.*.* Classpath: Jar:.,Jar:org.apache.aries.blueprint,Jar:xbean-blueprint,Jar:commons-jexl,Jar:pax-logging-api [WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT : Superfluous export-package instructions: [org.apache.activemq**] [INFO] [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ activemq-blueprint --- [INFO] [INFO] Checking legal files in: activemq-blueprint-5.9-SNAPSHOT.jar [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ activemq-blueprint --- [INFO] [INFO] Installing https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-blueprint/target/activemq-blueprint-5.9-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-blueprint/5.9-SNAPSHOT/activemq-blueprint-5.9-SNAPSHOT.jar [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ activemq-blueprint --- [INFO] Installing https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-blueprint/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-blueprint/5.9-SNAPSHOT/activemq-blueprint-5.9-SNAPSHOT.pom [INFO] [INFO] --- maven-bundle-plugin:2.3.7:install (default-install) @ activemq-blueprint --- [INFO] Installing org/apache/activemq/activemq-blueprint/5.9-SNAPSHOT/activemq-blueprint-5.9-SNAPSHOT.jar [INFO] Writing OBR metadata [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-blueprint --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-blueprint --- Apr 04, 2013 9:51:31 PM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [INFO] Building jar: https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-blueprint/target/activemq-blueprint-5.9-SNAPSHOT-sources.jar [INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-blueprint --- [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web Demo [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web Console [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Karaf Integration Tests [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1 [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Assembly [INFO] This project has been banned
[jira] [Commented] (AMQ-4439) Stomp 1.1 connections ignore persistent option
[ https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622985#comment-13622985 ] Trey Hyde commented on AMQ-4439: Sorry, I'm having some challenges with that. I don't see an example of another test using ActiveMQQueueBrowser. Is there some other way I should be inspecting the data store in tests to assert messages have the appropriate properties? Stomp 1.1 connections ignore persistent option Key: AMQ-4439 URL: https://issues.apache.org/jira/browse/AMQ-4439 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.7.0 Reporter: Trey Hyde Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option on the send call is ignored. Set accept-version to 1.0 and messages get get set as persistent appropriately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
