[jira] [Created] (AMQ-4612) Include clientidprefix in the consumer id

2013-07-01 Thread J CHEN (JIRA) 
J CHEN created AMQ-4612:
---

 Summary: Include clientidprefix in the consumer id
 Key: AMQ-4612
 URL: https://issues.apache.org/jira/browse/AMQ-4612
 Project: ActiveMQ
  Issue Type: Wish
Reporter: J CHEN


Currently clientIdPrefix is only part of the client id.  However, it would be 
very useful to be able to have clientidprefix as part of the consumer id to 
quickly link client and consumers...

--
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

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #811

2013-07-01 Thread Apache Jenkins Server 
See 

Changes:

[chirino] Improve the replicated leveldb behavior when the number of nodes in 
the cluster falls below the required minimum.  The master node will switch to 
electing mode.  The master store startup will now also block until it syncs up 
with slaves so that we don't accept connections the master is fully online.

[tabish] fix: https://issues.apache.org/jira/browse/AMQ-4604

--
[...truncated 11142 lines...]
[INFO] ActiveMQ :: Web ... SKIPPED
[INFO] ActiveMQ :: OSGi bundle ... SKIPPED
[INFO] ActiveMQ :: Blueprint . SUCCESS [8.913s]
[INFO] ActiveMQ :: Web Demo .. SKIPPED
[INFO] ActiveMQ :: Web Console ... SKIPPED
[INFO] ActiveMQ :: Karaf Integration Tests ... SKIPPED
[INFO] ActiveMQ :: Integration Test :: Spring 3.1  SKIPPED
[INFO] ActiveMQ :: Assembly .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3:09.744s
[INFO] Finished at: Tue Jul 02 03:17:33 UTC 2013
[INFO] Final Memory: 81M/964M
[INFO] 
[JENKINS] Archiving 
 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-parent/builds/2013-07-02_03-14-03/archive/org.apache.activemq/activemq-parent/5.9-SNAPSHOT/activemq-parent-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-07-02_03-14-04/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-07-02_03-14-04/archive/org.apache.activemq/activemq-client/5.9-20130702.031540-83/activemq-client-5.9-20130702.031540-83.jar
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-07-02_03-14-04/archive/org.apache.activemq/activemq-client/5.9-20130702.031540-83/activemq-client-5.9-20130702.031540-83-sources.jar
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-07-02_03-14-04/archive/org.apache.activemq/activemq-client/5.9-20130702.031540-83/activemq-client-5.9-20130702.031540-83-javadoc.jar
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$apache-activemq/builds/2013-07-02_03-14-07/archive/org.apache.activemq/apache-activemq/5.9-SNAPSHOT/apache-activemq-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-camel/builds/2013-07-02_03-14-05/archive/org.apache.activemq/activemq-camel/5.9-SNAPSHOT/activemq-camel-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq.tooling$activemq-tooling/builds/2013-07-02_03-14-06/archive/org.apache.activemq.tooling/activemq-tooling/5.9-SNAPSHOT/activemq-tooling-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-pool/builds/2013-07-02_03-14-06/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-karaf-itest/builds/2013-07-02_03-14-07/archive/org.apache.activemq/activemq-karaf-itest/5.9-SNAPSHOT/activemq-karaf-itest-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/Act

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Blueprint #811

2013-07-01 Thread Apache Jenkins Server 
See

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: KahaDB Store #811

2013-07-01 Thread Apache Jenkins Server 
See 


--
[...truncated 146 lines...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: JDBC Store #811

2013-07-01 Thread Apache Jenkins Server 
See 


--
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: JDBC Store 5.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-jdbc-store 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-jdbc-store 
---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-jdbc-store ---
Jul 2, 2013 3:17:05 AM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (default-cli) @ activemq-jdbc-store ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-jdbc-store 
---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-jdbc-store ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
activemq-jdbc-store ---
[debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 22 resources
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-jdbc-store ---
[INFO] [INFO] Compiling 37 source files to 


[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-jdbc-store ---
[INFO] [debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-jdbc-store ---
[INFO] [INFO] No sources to compile

[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-jdbc-store ---
[INFO] [INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-jdbc-store 
---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-jdbc-store ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
activemq-jdbc-store ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-jdbc-store 
---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-jdbc-store ---
Jul 2, 2013 3:17:08 AM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ activemq-jdbc-store 
---
[WARNING] Artifact 
org.apache.activemq:activemq-jdbc-store:java-source:sources:5.9-SNAPSHOT 
already attached to project, ignoring duplicate
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (attach-javadocs) @ 
activemq-jdbc-store ---
[INFO] 
Loading source files for package org.apache.activemq.store.jdbc...
Loading source files for package org.apache.activemq.store.jdbc.adapter...
Loading source files for package org.apache.activemq.store.journal...
Loading source files for package org.apache.activemq.util...
Constructing Javadoc information...
Standard Doclet version 1.6.0_45
Building tree for all the packages and classes...
Generating 

Generating 

Generating 

Generating

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Openwire Generator #811

2013-07-01 Thread Apache Jenkins Server 
See

[jira] [Resolved] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQCPP-494.
-

   Resolution: Fixed
Fix Version/s: 3.8.0
   3.7.1

Fixed on trunk and 3.7.x fixes branch

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Critical
> Fix For: 3.7.1, 3.8.0
>
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
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-4611) Network Failure Issue in Embedded Broker using setStaticBridge=true

2013-07-01 Thread Murtaza (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697203#comment-13697203
 ] 

Murtaza commented on AMQ-4611:
--

Please urgently reply on this very very urgent and critical bug in Active MQ. 
It has been a blocker for the entire community from using this product. 

> Network Failure Issue in Embedded Broker using setStaticBridge=true
> ---
>
> Key: AMQ-4611
> URL: https://issues.apache.org/jira/browse/AMQ-4611
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.8.0
> Environment: Production
>Reporter: Murtaza
>Priority: Blocker
>  Labels: AMQ_EMBEDDED_BROKER_WITH_STATIC_BRIDGE
>
> Hi,
> I have an embedded broker connecting to my remote server broker using network 
> connector and setStaticBridge=true and static list of destinations. When 
> producer produces the message connecting to my local embedded broker, it 
> successfully forwards to remote broker and stick it to pending messages. 
> Issue comes during network failure when embedded broker is unable to 
> communicate to remote broker and producer keep on producing messages. 
> Producer messages will be stored in KahaDB as a part of persistence setting. 
> When network comes up, I am not able to see old messages produced by producer 
> in the pending message of the remote broker and it doesn't forward any new 
> messages produced by the producer to remote broker thereafter. Only temporary 
> solution is to restart embedded broker. Please help in this urgent issue. My 
> code are as below -
> 1. Embedded Broker
> public final class EmbeddedBroker {
> public static Destination destination;
> public static String subject = "TOOL.DEFAULT";
> public static boolean topic;
> public static boolean transacted;
> private EmbeddedBroker() {
> }
> public static void main(String[] args) throws Exception {
> BrokerService broker = new BrokerService();
> broker.setUseJmx(true);
> broker.setBrokerName("storeforward");
> broker.addConnector("tcp://localhost:61616");
> broker.setPersistent(true);
> NetworkConnector connector1 = 
> broker.addNetworkConnector("static:failover:"+"tcp://172.16.102.153:61616");
> connector1.setDuplex(true);
> connector1.setStaticBridge(true);
> ActiveMQConnectionFactory connectionFactory = new 
> ActiveMQConnectionFactory(null, null, "failover:tcp://172.16.102.153:61616");
> Connection connection = connectionFactory.createConnection();
> System.out.println("test");
> connection.start();
> Session session = connection.createSession(transacted, 
> Session.AUTO_ACKNOWLEDGE);
> if (topic) {
> destination = session.createTopic(subject);
> } else {
> destination = session.createQueue(subject);
> }
> 
> List lst = new ArrayList();
> lst.add(destination);
> connector1.setBridgeTempDestinations(true);
> connector1.setAdvisoryForFailedForward(true);
> connector1.setStaticallyIncludedDestinations(lst);
> 
> broker.start();
> // now lets wait forever to avoid the JVM terminating immediately
> Object lock = new Object();
> synchronized (lock) {
> lock.wait();
> }
> }
> }
> 2. Producer
> public class ProducerTool extends Thread {
> private Destination destination;
> private int messageCount = 10;
> private long sleepTime;
> private boolean verbose = true;
> private int messageSize = 255;
> private static int parallelThreads = 1;
> private long timeToLive;
> /*private String user = ActiveMQConnection.DEFAULT_USER;
> private String password = ActiveMQConnection.DEFAULT_PASSWORD;
> */
> private String user = null;
> private String password = null;
> 
> private String url = "failover:tcp://172.16.102.153:61616";
> private String subject = "TOOL.DEFAULT";
> private boolean topic;
> private boolean transacted;
> private boolean persistent = true;
> private static Object lockResults = new Object();
> public static void main(String[] args) throws Exception {
> 
> ArrayList threads = new ArrayList();
> ProducerTool producerTool = new ProducerTool();
> String[] unknown = CommandLineSupport.setOptions(producerTool, args);
> if (unknown.length > 0) {
> System.out.println("Unknown options: " + 
> Arrays.toString(unknown));
> System.exit(-1);
> }
> producerTool.showParameters();
> for (int threadCount = 1; threadCount <= parallelThreads; 
> threadCount++) {
> producerTool

[jira] [Resolved] (AMQCPP-498) Client doesn't work on Linux Red Hat 6.4 systems, fails when setting thread priority

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQCPP-498.
-

   Resolution: Fixed
Fix Version/s: 3.8.0
   3.7.1

Fixed on trunk and 3.7.x branch.

> Client doesn't work on Linux Red Hat 6.4 systems, fails when setting thread 
> priority
> 
>
> Key: AMQCPP-498
> URL: https://issues.apache.org/jira/browse/AMQCPP-498
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Decaf
>Affects Versions: 3.5.0
> Environment: Linux Red Hat 6.4
>Reporter: John Rocha
>Assignee: Timothy Bish
>Priority: Critical
>  Labels: decaf, priority, pthreads, scheduling, thread
> Fix For: 3.7.1, 3.8.0
>
> Attachments: patch.TBD
>
>
> Client doesn't work on Linux Red Hat 6.4 systems. It fails throwing the 
> exception {panel}Failed to set new Therad priority to value: 18{panel}
> This is coming from the file
> {{{color:brown}src/main/decaf/internal/util/concurrent/unix/PlatformThread.cpp{color}}}
> when it's creating a new thread.
> We encountered this problem when we started running our code on a new 
> operating system. It worked fine on Redhat 5.8 and SuSE SLES10, but then it 
> started failing on Redhat 6.4.
> I did some digging and found a defect logged against the _+pthread+_ library 
> at: http://sourceware.org/bugzilla/show_bug.cgi?id=10828.
> {panel}(This problem was found by analyzing a failure of LSB distribution 
> compliance test, lsb-runtime, v. 4.0.2.)
> A relatively new change in $GITROOT/glibc/nptl/pthread_attr_setschedparam.c 
> (2009-04-23 according to git) adds a check to pthread_attr_setschedparam() 
> call whether the priority being set is compatible with the scheduling policy 
> already set in the structure; if the priority is not in the prescribed range, 
> it fails, generating the EINVAL error.
> This check, although well intended, has a side effect that can break existing 
> code (at least the LSB tests): it makes the process of initializing a 
> pthread_attr structure order-dependent on Linux.
> As Linux does not use the numeric priority for SCHED_OTHER, which is the 
> default, and sched_get_priority_min() and sched_priority_max() return 0. 
> Therefore:
> If a programmer calls pthread_attr_init(), then pthread_attr_setschedpolicy() 
> to set SCHED_RR or SCHED_FIFO, and then pthread_attr_setschedparam(), it 
> works. But if the other way around (priority first, then scheduling policy), 
> it fails for "no apparent reason".{panel}
> I did some debugging in the code and found that {{unix/PlatformThread.cpp}}'s 
> method {{createNewThread()}} sets the scheduling priority but doesn't set the 
> scheduling policy. And the default value for the scheduling policy is 
> SCHED_OTHER(0) which only supports a priority value of 0.
> I have a proposed patch which:
> # validates the return values of all pthread calls and
> # only sets the priority iff the policy is sset to SCHED_FIFO or SCHED_RR
> Granted, we never set the policy so one could argue that we should just 
> remove setting of the priority. However, I suspect that the true desire is to 
> inherit the current threads scheduling value and set the priority based on 
> that. So I anticipate tha future changes may actually set the policy. I 
> didn't do this though.

--
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

Regarding AMQ-4181 - JMS queue browser returns only page size number of messages

2013-07-01 Thread binita.bharati 
Hi , 

I downloaded ActiveMQ 5.8 from
http://activemq.apache.org/activemq-580-release.html
The https://issues.apache.org/jira/browse/AMQ-4181 says that this issue is
fixed in 5.8 version, but, I still see the same problem happening. 

What could be the problem ?

Thanks



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Regarding-AMQ-4181-JMS-queue-browser-returns-only-page-size-number-of-messages-tp4668723.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Resolved] (AMQCPP-497) Compilation of 3.7.0 fails for Linux systems (Redhat 5.8 and SuSE SLES 10)

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQCPP-497.
-

   Resolution: Fixed
Fix Version/s: 3.8.0
   3.7.1

Fix on trunk and the 3.7.x branch

> Compilation of 3.7.0 fails for Linux systems (Redhat 5.8 and SuSE SLES 10)
> --
>
> Key: AMQCPP-497
> URL: https://issues.apache.org/jira/browse/AMQCPP-497
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Decaf
>Affects Versions: 3.7.0
> Environment: Linux Red Hat 5.8 and Linux SuSE SLES10
>Reporter: John Rocha
>Assignee: Timothy Bish
>  Labels: compile-error, linux
> Fix For: 3.7.1, 3.8.0
>
> Attachments: patch003.TBD
>
>
> Compilation of 3.7.0 fails for Linux systems (RedHat 5.8 and SuSE SLES 10)
> I found that even after applying the patch for AMQCPP-483, compilation of the 
> 3.7.0 source base on Linux systems would still fail. I reproduced this 
> problem on two diffent flavors of Linux. RedHat 5.8 and SuSE SLES10.
> The failures are as follows:
> {panel}
> libtool: compile:  g\+\+ \-DHAVE\_CONFIG\_H \-I. \-I../.. \-ansi \-pedantic 
> \-DLINUX=2 \-D\_REENTRANT \-D\_GNU\_SOURCE \-D\_LARGEFILE64\_SOURCE 
> \-I/views/LU\-7.2\-AMQ\-3.7.1/server/gpl/apr\-1.4.2\-src/BUILD\_DIR\_RhatFive0206\-i686\-gnu0401/include/apr\-1
>  \-I/usr/kerberos/include \-W \-Wall \-Wextra \-Wconversion \-fPIC 
> \-fstrict\-aliasing \-Wstrict\-aliasing=2 \-Wno\-long\-long \-g \-O2 
> \-pthread \-MT decaf/internal/util/libactivemq\_cpp\_la\-HexStringParser.lo 
> \-MD \-MP \-MF 
> decaf/internal/util/.deps/libactivemq\_cpp\_la\-HexStringParser.Tpo \-c 
> decaf/internal/util/HexStringParser.cpp  \-fPIC \-DPIC \-o 
> decaf/internal/util/.libs/libactivemq\_cpp\_la\-HexStringParser.o
> decaf/internal/util/HexStringParser.cpp:28:26: error: apr\_strmatch.h: No 
> such file or directory
> make\[3]: \*\*\* 
> \[decaf/internal/util/libactivemq\_cpp\_la\-HexStringParser.lo] Error 1
> make\[2]: \*\*\* \[all\-recursive] Error 1
> make\[1]: \*\*\* \[all] Error 2
> make: \*\*\* \[os\_release] Error 2
> {panel}
> and
> {panel}
> libtool: compile:  g\+\+ \-DHAVE\_CONFIG\_H \-I. \-I../.. \-ansi \-pedantic 
> \-DLINUX=2 \-D\_REENTRANT \-D\_GNU\_SOURCE \-D\_LARGEFILE64\_SOURCE 
> \-I/views/LU\-7.2\-AMQ\-3.7.1/server/gpl/apr\-1.4.2\-src/BUILD\_DIR\_RhatFive0206\-i686\-gnu0401/include/apr\-1
>  \-I/usr/kerberos/include \-W \-Wall \-Wextra \-Wconversion \-fPIC 
> \-fstrict\-aliasing \-Wstrict\-aliasing=2 \-Wno\-long\-long \-g \-O2 
> \-pthread \-MT decaf/util/libactivemq\_cpp\_la\-UUID.lo \-MD \-MP \-MF 
> decaf/util/.deps/libactivemq\_cpp\_la\-UUID.Tpo \-c decaf/util/UUID.cpp  
> \-fPIC \-DPIC \-o decaf/util/.libs/libactivemq\_cpp\_la\-UUID.o
> decaf/util/UUID.cpp:112: error: integer constant is too large for 'long' type
> decaf/util/UUID.cpp: In copy constructor 'decaf::util::UUID::UUID(const 
> decaf::util::UUID&)':
> decaf/util/UUID.cpp:151: warning: base class 'class 
> decaf::lang::Comparable' should be explicitly initialized 
> in the copy constructor
> make\[3]: \*\*\* \[decaf/util/libactivemq\_cpp\_la\-UUID.lo] Error 1
> make\[2]: \*\*\* \[all\-recursive] Error 1
> make\[1]: \*\*\* \[all] Error 2
> make: \*\*\* \[os\_release] Error 2
> {panel}
> I've attached a patch file for what I think might be the fixes.
> For the first I removed the inclusion of the file {{apr_strmatch.h}} as it 
> comes from apr\-util which according to 
> [AMQCPP\-469|https://issues.apache.org/jira/browse/AMQCPP\-469] is no longer 
> needed. Moreover, compilation works even with it's removal.
> For the second I changed the casting from L to LL.

--
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] (AMQCPP-496) Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish updated AMQCPP-496:


Priority: Minor  (was: Major)

> Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h
> 
>
> Key: AMQCPP-496
> URL: https://issues.apache.org/jira/browse/AMQCPP-496
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>  Components: CMS Impl
>Affects Versions: 3.6.0
> Environment: All
>Reporter: Kevin Urciolo
>Assignee: Timothy Bish
>Priority: Minor
>
> #define DECAF_MAX_TLS_SLOTS 256 in ThreadTypes.h seems to impose a limit of 
> 51 connections for a CMS client on our systems because of its use with 
> threading.  We would like to request this number be increased a larger value, 
> such as 1536, to allow a client to maintain additional connections.

--
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] (AMQCPP-496) Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h

2013-07-01 Thread Timothy Bish (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQCPP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696949#comment-13696949
 ] 

Timothy Bish commented on AMQCPP-496:
-

Setting it this big could waste a bit of space for clients that don't need that 
many.  It would be preferable to enhance the current code to dynamically 
allocate a set of slots and then extend the threads with more when there is a 
call to do so.  

> Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h
> 
>
> Key: AMQCPP-496
> URL: https://issues.apache.org/jira/browse/AMQCPP-496
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>  Components: CMS Impl
>Affects Versions: 3.6.0
> Environment: All
>Reporter: Kevin Urciolo
>Assignee: Timothy Bish
>
> #define DECAF_MAX_TLS_SLOTS 256 in ThreadTypes.h seems to impose a limit of 
> 51 connections for a CMS client on our systems because of its use with 
> threading.  We would like to request this number be increased a larger value, 
> such as 1536, to allow a client to maintain additional connections.

--
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

Fwd: ASF Board Report - Initial Reminder for Jul 2013

2013-07-01 Thread Hiram Chirino 
FYI


-- Forwarded message --
From: ASF Board 
Date: Mon, Jul 1, 2013 at 11:11 AM
Subject: ASF Board Report - Initial Reminder for Jul 2013
To: Hiram Chirino 




This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder to give you plenty of time to prepare the report.

The meeting is scheduled for Wed, 17 July 2013, 10:30:00:00 PST and
the deadline for
submitting your report is 1 full week prior to that (Wed, Jul 10th)!

According to board records, you are listed as the chair of at least one
committee that is due to submit a report this month. [1] [2]

Details on which project reports are due and how to submit a report
are enclosed below.

Please submit your report with sufficient time to allow the board members
to review and digest. Again, the very latest you should submit your report
is 1 full week (7days) prior to the board meeting (Wed, Jul 10th).

If you feel that an error has been made, please consult [1] and if there
is still an issue then contact the board directly.

As always, PMC chairs are welcome to attend the board meeting.

Thanks,
The ASF Board

[1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt
[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt
[3] - https://svn.apache.org/repos/private/committers/board/templates


Submitting your Report
--

Full details about the process and schedule are in [1].

The report should be committed to the meeting agenda in the board directory
in the foundation repository, trying to keep a similar format to the others.
This can be found at:

  https://svn.apache.org/repos/private/foundation/board

Your report should also be sent in plain-text format to bo...@apache.org
with a Subject line that follows the below format:

Subject: [REPORT] Project Name

Cutting and pasting directly from a Wiki is not acceptable due to formatting
issues. Line lengths should be limited to 77 characters.


Resolutions
---

There are several templates for use for various Board resolutions.
They can be found in [3] and you are encouraged to use them. It is
strongly recommended that if you have a resolution before the board,
you are encouraged to attend that board meeting.


ASF Board Reports
-

Reports are due from you for the following committees:

 - ActiveMQ


--
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

[jira] [Closed] (AMQCPP-492) Seg fault in decaf::util::concurrent::Mutex::Mutex MutexProperties (memcpy)

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish closed AMQCPP-492.
---

Resolution: Incomplete

No test case or thread dump to pursue this at the moment. 

> Seg fault in decaf::util::concurrent::Mutex::Mutex MutexProperties (memcpy)
> ---
>
> Key: AMQCPP-492
> URL: https://issues.apache.org/jira/browse/AMQCPP-492
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Decaf
>Affects Versions: 3.5.0
> Environment: $ cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 6.3 (Santiago)
> $ cat /proc/version
> Linux version 2.6.32-279.el6.x86_64 (mockbu...@x86-008.build.bos.redhat.com) 
> (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Wed Jun 13 
> 18:24:36 EDT 2012
>Reporter: Josh Schwartz
>Assignee: Timothy Bish
>
> This happened during a failover test so it's likely that there were 
> non-nominal things occurring such as connections being terminated abruptly.
> I looked at the release notes for 3.6.0 and 3.7.0 and I don't see a fix for 
> this issue.
> Program terminated with signal 11, Segmentation fault.
> #0  0x003eec888ea3 in memcpy () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install 
> apr-util-1.3.9-3.el6_0.1.x86_64 cyrus-sasl-lib-2.1.23-13.el6.x86_64 
> db4-4.7.25-17.el6.x86_64 expat-2.0.1-11.el6_2.x86_64 
> glibc-2.12-1.80.el6.x86_64 keyutils-libs-1.4-4.el6.x86_64 
> krb5-libs-1.9-33.el6.x86_64 libcom_err-1.41.12-12.el6.x86_64 
> libgcc-4.4.6-4.el6.x86_64 libselinux-2.0.94-5.3.el6.x86_64 
> libstdc++-4.4.6-4.el6.x86_64 libuuid-2.17.2-12.7.el6.x86_64 
> nspr-devel-4.9-1.el6.x86_64 nss-3.13.3-6.el6.x86_64 
> nss-softokn-freebl-3.12.9-11.el6.x86_64 nss-util-3.13.3-2.el6.x86_64 
> openssl-1.0.0-20.el6_2.5.x86_64 zlib-1.2.3-27.el6.x86_64
> (gdb) where
> #0  0x003eec888ea3 in memcpy () from /lib64/libc.so.6
> #1  0x003ef489d1c6 in std::basic_string, 
> std::allocator >::_Rep::_M_clone(std::allocator const&, unsigned 
> long) () from /usr/lib64/libstdc++.so.6
> #2  0x003ef489d26c in std::basic_string, 
> std::allocator >::basic_string(std::basic_string std::char_traits, std::allocator > const&) ()
>from /usr/lib64/libstdc++.so.6
> #3  0x0041d75a in std::basic_string, 
> std::allocator > std::operator+, 
> std::allocator >(std::basic_string, 
> std::allocator > const&, std::basic_string std::char_traits, std::allocator > const&) ()
> #4  0x7f04aeb66a0b in MutexProperties (this=) at 
> decaf/util/concurrent/Mutex.cpp:48
> #5  decaf::util::concurrent::Mutex::Mutex (this=) at 
> decaf/util/concurrent/Mutex.cpp:72
> #6  0x7f04ae7db9e0 in AbstractCollection (this=0x7f0398002530) at 
> ./decaf/util/AbstractCollection.h:65
> #7  AbstractList (this=0x7f0398002530) at ./decaf/util/AbstractList.h:341
> #8  ArrayList (this=0x7f0398002530) at ./decaf/util/ArrayList.h:49
> #9  activemq::commands::ActiveMQDestination::ActiveMQDestination 
> (this=0x7f0398002530)
> at activemq/commands/ActiveMQDestination.cpp:74
> #10 0x7f04ae827d49 in activemq::commands::ActiveMQTopic::ActiveMQTopic 
> (this=0x7f0398002530)
> at activemq/commands/ActiveMQTopic.cpp:26
> #11 0x7f04aea7a15a in 
> activemq::wireformat::openwire::marshal::generated::ActiveMQTopicMarshaller::createObject
>  (this=)
> at 
> activemq/wireformat/openwire/marshal/generated/ActiveMQTopicMarshaller.cpp:45
> #12 0x7f04aea64c8b in 
> activemq::wireformat::openwire::OpenWireFormat::tightUnmarshalNestedObject (
> this=0x109ccf0, dis=0x109d0e0, bs=0x7f03aaf11b50) at 
> activemq/wireformat/openwire/OpenWireFormat.cpp:400
> #13 0x7f04aea6bccc in 
> activemq::wireformat::openwire::marshal::BaseDataStreamMarshaller::tightUnmarshalCachedObject
>  (this=, wireFormat=, dataIn= optimized out>,
> bs=) at 
> activemq/wireformat/openwire/marshal/BaseDataStreamMarshaller.cpp:51
> #14 0x7f04aea99c16 in 
> activemq::wireformat::openwire::marshal::generated::MessageDispatchMarshaller::tightUnmarshal
>  (this=0x1140910, wireFormat=0x109ccf0, dataStructure=, 
> dataIn=0x109d0e0,
> bs=0x7f03aaf11b50) at 
> activemq/wireformat/openwire/marshal/generated/MessageDispatchMarshaller.cpp:65
> #15 0x7f04aea65bb1 in 
> activemq::wireformat::openwire::OpenWireFormat::doUnmarshal (this=0x109ccf0,
> dis=0x109d0e0) at activemq/wireformat/openwire/OpenWireFormat.cpp:295
> #16 0x7f04aea65fb7 in 
> activemq::wireformat::openwire::OpenWireFormat::unmarshal (this=0x109ccf0,
> transport=, dis=0x109d0e0) at 
> activemq/wireformat/openwire/OpenWireFormat.cpp:230
> #17 0x7f04ae9c8350 in activemq::transport::IOTransport::run 
> (this=0xf6d6f0)
> at activemq/transport/IOTransport.cpp:247
> #18 0x7f04aeafa84f in (anonymous namespace)::runCal

[jira] [Resolved] (AMQ-4604) Update QPID Client version to 0.22

2013-07-01 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQ-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-4604.
---

   Resolution: Fixed
Fix Version/s: 5.9.0
 Assignee: Timothy Bish

fixed, thanks.

> Update QPID Client version to 0.22
> --
>
> Key: AMQ-4604
> URL: https://issues.apache.org/jira/browse/AMQ-4604
> Project: ActiveMQ
>  Issue Type: Bug
>Reporter: Kevin Earls
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 5.9.0
>
> Attachments: AMQ-4604.patch
>
>
> 0.22 is the latest released version. 

--
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-4611) Network Failure Issue in Embedded Broker using setStaticBridge=true

2013-07-01 Thread Murtaza (JIRA) 
Murtaza created AMQ-4611:


 Summary: Network Failure Issue in Embedded Broker using 
setStaticBridge=true
 Key: AMQ-4611
 URL: https://issues.apache.org/jira/browse/AMQ-4611
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.8.0
 Environment: Production
Reporter: Murtaza
Priority: Blocker


Hi,

I have an embedded broker connecting to my remote server broker using network 
connector and setStaticBridge=true and static list of destinations. When 
producer produces the message connecting to my local embedded broker, it 
successfully forwards to remote broker and stick it to pending messages. Issue 
comes during network failure when embedded broker is unable to communicate to 
remote broker and producer keep on producing messages. Producer messages will 
be stored in KahaDB as a part of persistence setting. When network comes up, I 
am not able to see old messages produced by producer in the pending message of 
the remote broker and it doesn't forward any new messages produced by the 
producer to remote broker thereafter. Only temporary solution is to restart 
embedded broker. Please help in this urgent issue. My code are as below -

1. Embedded Broker

public final class EmbeddedBroker {
public static Destination destination;
public static String subject = "TOOL.DEFAULT";
public static boolean topic;
public static boolean transacted;

private EmbeddedBroker() {
}

public static void main(String[] args) throws Exception {
BrokerService broker = new BrokerService();
broker.setUseJmx(true);
broker.setBrokerName("storeforward");
broker.addConnector("tcp://localhost:61616");
broker.setPersistent(true);
NetworkConnector connector1 = 
broker.addNetworkConnector("static:failover:"+"tcp://172.16.102.153:61616");
connector1.setDuplex(true);
connector1.setStaticBridge(true);

ActiveMQConnectionFactory connectionFactory = new 
ActiveMQConnectionFactory(null, null, "failover:tcp://172.16.102.153:61616");
Connection connection = connectionFactory.createConnection();
System.out.println("test");
connection.start();
Session session = connection.createSession(transacted, 
Session.AUTO_ACKNOWLEDGE);
if (topic) {
destination = session.createTopic(subject);
} else {
destination = session.createQueue(subject);
}

List lst = new ArrayList();
lst.add(destination);
connector1.setBridgeTempDestinations(true);
connector1.setAdvisoryForFailedForward(true);
connector1.setStaticallyIncludedDestinations(lst);

broker.start();

// now lets wait forever to avoid the JVM terminating immediately
Object lock = new Object();
synchronized (lock) {
lock.wait();
}
}
}


2. Producer

public class ProducerTool extends Thread {

private Destination destination;
private int messageCount = 10;
private long sleepTime;
private boolean verbose = true;
private int messageSize = 255;
private static int parallelThreads = 1;
private long timeToLive;
/*private String user = ActiveMQConnection.DEFAULT_USER;
private String password = ActiveMQConnection.DEFAULT_PASSWORD;
*/
private String user = null;
private String password = null;

private String url = "failover:tcp://172.16.102.153:61616";
private String subject = "TOOL.DEFAULT";
private boolean topic;
private boolean transacted;
private boolean persistent = true;
private static Object lockResults = new Object();

public static void main(String[] args) throws Exception {

ArrayList threads = new ArrayList();
ProducerTool producerTool = new ProducerTool();
String[] unknown = CommandLineSupport.setOptions(producerTool, args);
if (unknown.length > 0) {
System.out.println("Unknown options: " + Arrays.toString(unknown));
System.exit(-1);
}
producerTool.showParameters();
for (int threadCount = 1; threadCount <= parallelThreads; 
threadCount++) {
producerTool = new ProducerTool();
CommandLineSupport.setOptions(producerTool, args);
producerTool.start();
threads.add(producerTool);
}

while (true) {
Iterator itr = threads.iterator();
int running = 0;
while (itr.hasNext()) {
ProducerTool thread = itr.next();
if (thread.isAlive()) {
running++;
}
}
if (running <= 0) {
System.out.println("All threads completed their work");
break;
}
try {
Thread.sleep(1

Re: Building activemq-cpp-library using stlport without streams

2013-07-01 Thread Timothy Bish 

On 06/27/2013 06:18 AM, atarutin wrote:

Is there any way to use (build) activemq-cpp-library without stl streams? I
use stlport without streams, so maybe somebody has already met the same
problem. Is there any solution?
Thanks in advance.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Building-activemq-cpp-library-using-stlport-without-streams-tp4668640.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


Don't think so, internally stream are used in some places

--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

www.camelone.org : The open source integration conference:

[jira] [Commented] (AMQCPP-469) Remove linkage to APR-Util

2013-07-01 Thread Timothy Bish (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQCPP-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696796#comment-13696796
 ] 

Timothy Bish commented on AMQCPP-469:
-

Pull from the svn branch 3.7.x and this is fixed. 

> Remove linkage to APR-Util
> --
>
> Key: AMQCPP-469
> URL: https://issues.apache.org/jira/browse/AMQCPP-469
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>  Components: Decaf
>Affects Versions: 3.6.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 3.7.0
>
>
> Next release won't need APR-Util, update the scripts and dev projects to 
> remove the linkage. 

--
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-4610) ActiveMQ shows icon in Dock on MacOSX (with solution)

2013-07-01 Thread Erik van Oosten (JIRA) 
Erik van Oosten created AMQ-4610:


 Summary: ActiveMQ shows icon in Dock on MacOSX (with solution)
 Key: AMQ-4610
 URL: https://issues.apache.org/jira/browse/AMQ-4610
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Erik van Oosten


On Mac activemq shows an really annoying icon in the doc.

Please add the following options to the startup script to get rid of it:

{noformat}
-Djava.awt.headless=true
{noformat}

--
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] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

2013-07-01 Thread Andrei Gheorghe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQCPP-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Gheorghe updated AMQCPP-494:
---

Priority: Critical  (was: Minor)

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Critical
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
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