[jira] [Created] (OPENWIRE-6) Fix build on JDK 8

[Christopher L. Shannon (JIRA)]

Christopher L. Shannon created OPENWIRE-6:
-

 Summary: Fix build on JDK  8
 Key: OPENWIRE-6
 URL: https://issues.apache.org/jira/browse/OPENWIRE-6
 Project: ActiveMQ OpenWire
  Issue Type: Bug
Reporter: Christopher L. Shannon


Currently there are some incompactible dependencies with scalate and scala 
causing the build to fail on JDK 8 update 60.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OPENWIRE-6) Fix build on JDK 8

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/OPENWIRE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969772#comment-14969772
 ] 

ASF subversion and git services commented on OPENWIRE-6:


Commit 682c03ac5b8a53868dfabc19fa13435ff6ff16e3 in activemq-openwire's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-openwire.git;h=682c03a ]

https://issues.apache.org/jira/browse/OPENWIRE-6

Upgrading dependencies and scala maven plugin to be compatible
with JDK 8.


> Fix build on JDK  8
> ---
>
> Key: OPENWIRE-6
> URL: https://issues.apache.org/jira/browse/OPENWIRE-6
> Project: ActiveMQ OpenWire
>  Issue Type: Bug
>Reporter: Christopher L. Shannon
>
> Currently there are some incompactible dependencies with scalate and scala 
> causing the build to fail on JDK 8 update 60.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-239) Verify Stomp Heart-beating against StompJMS

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969589#comment-14969589
 ] 

ASF GitHub Bot commented on ARTEMIS-239:


Github user clebertsuconic commented on the pull request:

https://github.com/apache/activemq-artemis/pull/208#issuecomment-150313180
  
there is some tests changes I have to do for this...

I will keep this open for now


> Verify Stomp Heart-beating against StompJMS
> ---
>
> Key: ARTEMIS-239
> URL: https://issues.apache.org/jira/browse/ARTEMIS-239
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 1.1.1
>
>
> https://github.com/fusesource/stompjms/issues/26



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5981) Update to Karaf 4

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AMQ-5981:
--

Commit ef6b1e107bd7d8bdd8280a9b46adbe450598b1d6 in activemq's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=ef6b1e1 ]

https://issues.apache.org/jira/browse/AMQ-5981

Updating to Karaf 4.0.2


> Update to Karaf 4
> -
>
> Key: AMQ-5981
> URL: https://issues.apache.org/jira/browse/AMQ-5981
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Affects Versions: 5.12.0
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> We need to update to Karaf 4 to support Jetty 9.2.x



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OPENWIRE-7) Add OpenWire v11

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/OPENWIRE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969887#comment-14969887
 ] 

ASF subversion and git services commented on OPENWIRE-7:


Commit 45ecbaf563e3c44e1c459e65dfeb07c283f0c03a in activemq-openwire's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-openwire.git;h=45ecbaf ]

OPENWIRE-7 Add the single v11 feild addition for subscription info.
Marshallers still need to be generated for this update.

> Add OpenWire v11 
> -
>
> Key: OPENWIRE-7
> URL: https://issues.apache.org/jira/browse/OPENWIRE-7
> Project: ActiveMQ OpenWire
>  Issue Type: Task
>Reporter: Timothy Bish
> Fix For: 1.0
>
>
> ActiveMQ 5 Broker version went to v11, we should capture that here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMQ-6017) Make ioBufferSize configurable for nio transport

[Dejan Bosanac (JIRA)]

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

Dejan Bosanac resolved AMQ-6017.

Resolution: Fixed

Fixed on master

> Make ioBufferSize configurable for nio transport
> 
>
> Key: AMQ-6017
> URL: https://issues.apache.org/jira/browse/AMQ-6017
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.12.0
>Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.13.0
>
>
> Buffer size can be configured for tcp transport with 
> transport.ioBufferSize=xxx property. In nio case it's hard coded to 8k 
> (default for tcp case as well). We need to be bale to tune this in nio case 
> as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-238) Expand legacy support to clients and improve existing ClientProtocolManager

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969234#comment-14969234
 ] 

ASF GitHub Bot commented on ARTEMIS-238:


Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/212


> Expand legacy support to clients and improve existing ClientProtocolManager
> ---
>
> Key: ARTEMIS-238
> URL: https://issues.apache.org/jira/browse/ARTEMIS-238
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 1.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-236) Improve Legacy support on older migrating clients

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969233#comment-14969233
 ] 

ASF subversion and git services commented on ARTEMIS-236:
-

Commit bc828c0017c474164b2f46cdd84ae93d5bf8c682 in activemq-artemis's branch 
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=bc828c0 ]

ARTEMIS-238 and ARTEMIS-236 Moving HQClient to its own module avoiding 
uncessary server's dependencies


> Improve Legacy support on older migrating clients
> -
>
> Key: ARTEMIS-236
> URL: https://issues.apache.org/jira/browse/ARTEMIS-236
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Howard Nguyen
>Assignee: clebert suconic
> Fix For: 1.1.1
>
>
> On connect,
> Client repeatedly log  (ip is removed)
> {code}
> 2015-09-29 17:20:35,750 WARN  
> [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] (Thread-36 
> (HornetQ-client-global-threads-1087057800)) Connection failure has been 
> detected: Did not receive data from server for 
> org.hornetq.core.remoting.impl.netty.NettyConnection@2a864afa[local= 
> /x.x.x.x:53907, remote=/y.y.y.y:5445] [code=3]
> {code}
> Server repeatedly log
> {code}
> 17:12:07,012 WARNING [io.netty.channel.DefaultChannelPipeline] An 
> exceptionCaught() event was fired, and it reached at the tail of the 
> pipeline. It usually means the last handler in the pipeline did not handle 
> the exception.: io.netty.handler.codec.DecoderException: 
> java.lang.NullPointerException
> at 
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:358)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:230)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:117)
>  [artemis-server-1.1.0.jar:1.1.0]
> at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) 
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) 
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) 
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:162)
>  [artemis-server-1.1.0.jar:1.1.0]
> at 
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:327)
>  [netty-all-4.0.30.Final.jar:4.0.30.Final]
> ... 12 more
> {code}
> broker.xml
> {code}
>  name="hornetq">tcp://0.0.0.0:5445?protocols=HORNETQ,STOMP
> {code}
> Single client using hornetq 2.2.16.FINAL, and single artemis 1.1.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ARTEMIS-274) Make ActiveMQThreadFactory instantiation running within doPrivileged block

[clebert suconic (JIRA)]

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

clebert suconic closed ARTEMIS-274.
---
Resolution: Fixed

> Make ActiveMQThreadFactory instantiation running within doPrivileged block
> --
>
> Key: ARTEMIS-274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-274
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Ivo Studensky
> Fix For: 1.2.0, 1.1.1
>
>
> At the moment, ActiveMQThreadFactory caches AccessControlContext inside of 
> its constructor and uses it later in newThread() method invocation to create 
> a thread inside of doPrivileged block. This leads to not enough permissions 
> issue when a client is trying to create a new connection on a factory taken 
> from JNDI, see https://issues.jboss.org/browse/WFLY-5166.
> To fix it all the invocations of the factory constructor should run within a 
> privileged block to get a privileged ACC to the factory. This change should 
> be similar to how it works in WildFly right now. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-238) Expand legacy support to clients and improve existing ClientProtocolManager

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969203#comment-14969203
 ] 

ASF GitHub Bot commented on ARTEMIS-238:


GitHub user clebertsuconic opened a pull request:

https://github.com/apache/activemq-artemis/pull/212

ARTEMIS-238 and ARTEMIS-236 Moving HQClient to its own module avoiding 
uncessary server's dependencies



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/clebertsuconic/activemq-artemis hqclient

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/212.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #212


commit 44c5b673e61773488603b53d61183a6a1d884234
Author: Clebert Suconic 
Date:   2015-10-22T14:05:58Z

ARTEMIS-238 and ARTEMIS-236 Moving HQClient to its own module avoiding 
uncessary server's dependencies




> Expand legacy support to clients and improve existing ClientProtocolManager
> ---
>
> Key: ARTEMIS-238
> URL: https://issues.apache.org/jira/browse/ARTEMIS-238
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 1.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-4361) Deadlock during close while publishing to flow-controlled queue

[Gary Tully (JIRA)]

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

Gary Tully commented on AMQ-4361:
-

[~shendley] thanks, sorted that IllegalMonitorStateException

> Deadlock during close while publishing to flow-controlled queue
> ---
>
> Key: AMQ-4361
> URL: https://issues.apache.org/jira/browse/AMQ-4361
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.6.0, 5.8.0
> Environment: Windows, Linux, JDK 1.6
>Reporter: Sam hendley
>Assignee: Timothy Bish
> Fix For: 5.9.0
>
>
> TestCase on github: 
> https://github.com/samhendley/activemq-close-deadlock-bug
> The deadlock occurs when we are using TcpTransport to a flow-controlled queue 
> and we then try to gracefully shutdown the application. The close operation 
> hangs forever because it is trying to send a "close packet" to the server. It 
> never gets the chance to send that request because the socket is blocked by 
> the publishing thread. This stops my publisher from shutting down and causes 
> us to orphan threads during shutdown.
> I have verified this bug occurs on atleast activemq 5.6.0 and 5.8.0 and on 
> linux and windows using JDK 1.6.
> I don't need a fix for the bug necessarily, just a way to gracefully shutdown 
> my publisher if I get into this state.
> Partial Stack Trace During failure
> "ClosingThread" prio=6 tid=0x045ce000 nid=0xa84 waiting on condition 
> [0x04ddf000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x23fc52d8> (a 
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
> at 
> java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186)
> at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262)
> at 
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)
> at 
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at 
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1304)
> at 
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1298)
> at 
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1901)
> at 
> org.apache.activemq.ActiveMQMessageProducer.close(ActiveMQMessageProducer.java:173)
> at 
> org.activemq.bug.DeadlockDuringCloseTest$2.run(DeadlockDuringCloseTest.java:83)
> at java.lang.Thread.run(Thread.java:662)
> "PublishingThread" prio=6 tid=0x045cd800 nid=0xb84 runnable [0x04d8f000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at 
> org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
> at java.io.DataOutputStream.flush(DataOutputStream.java:106)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:176)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.doOnewaySend(AbstractInactivityMonitor.java:322)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.oneway(AbstractInactivityMonitor.java:304)
> at 
> org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
> at 
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
> at 
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at 
> org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1304)
> at 
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1298)
> at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1782)
> - locked <0x23faa7d8> (a java.lang.Object)
> at 
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
> at 
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
> at 
> 

[jira] [Commented] (AMQ-6019) TheListIndex is not loaded exception under heavier load

[Octavian (JIRA)]

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

Octavian commented on AMQ-6019:
---

Yes. I was not able to reproduce this yet. Looks like it was fixed. I think we 
can close this issue.

> TheListIndex is not loaded exception under heavier load
> ---
>
> Key: AMQ-6019
> URL: https://issues.apache.org/jira/browse/AMQ-6019
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, KahaDB
>Affects Versions: 5.10.0
> Environment: AcitveMQ 5.10.0 on Windows Server 2012R2 DataCenter
>Reporter: Octavian
>
> Hello,
> I'm trying to run the performance test with posting 1,000,000 messages from 4 
> producers to ActiveMQ. Many times I'm getting the following exception in 
> ActiveMQ Broker logs and it looks like the broker is not accepting any more 
> messages:
> 2015-10-22 09:30:45,314 | WARN  | Async error occurred:  | 
> org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: 
> tcp:///10.80.35.179:56140@20039
> java.lang.RuntimeException: java.lang.IllegalStateException: TheListIndex is 
> not loaded
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:244)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.addMessageLast(FilePendingMessageCursor.java:207)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1855)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:939)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.send(Queue.java:733)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:424)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:147)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:152)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:496)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:756)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)[activemq-client-5.10.0.jar:5.10.0]
>   at java.lang.Thread.run(Unknown Source)[:1.8.0_11]
> For example I'm getting 131191 messages out of 1000,000 on the queue and the 
> performance test is freezing.
> I'm running the test with the following command:
> mvn activemq-perf:producer -Dfactory.brokerURL=tcp://hostname:20039 
> -DsysTest.numClients=4 -Dproducer.destName=queue://test 
> -Dproducer.deliveryMode=persistent -Dfactory.useAsyncSend=true
> I've changed the activemq.xml persistenceAdapter as shown:
> 
>  enableJournalDiskSyncs="false" indexWriteBatchSize="1" 
> indexCacheSize="1000"/>
> 
> Thanks,
> Octavian



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AMQ-6019) TheListIndex is not loaded exception under heavier load

[Timothy Bish (JIRA)]

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

Timothy Bish closed AMQ-6019.
-
Resolution: Cannot Reproduce

Reported as not reproducible on a newer broker.

> TheListIndex is not loaded exception under heavier load
> ---
>
> Key: AMQ-6019
> URL: https://issues.apache.org/jira/browse/AMQ-6019
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, KahaDB
>Affects Versions: 5.10.0
> Environment: AcitveMQ 5.10.0 on Windows Server 2012R2 DataCenter
>Reporter: Octavian
>
> Hello,
> I'm trying to run the performance test with posting 1,000,000 messages from 4 
> producers to ActiveMQ. Many times I'm getting the following exception in 
> ActiveMQ Broker logs and it looks like the broker is not accepting any more 
> messages:
> 2015-10-22 09:30:45,314 | WARN  | Async error occurred:  | 
> org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: 
> tcp:///10.80.35.179:56140@20039
> java.lang.RuntimeException: java.lang.IllegalStateException: TheListIndex is 
> not loaded
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:244)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.addMessageLast(FilePendingMessageCursor.java:207)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1855)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:939)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.send(Queue.java:733)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:424)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:147)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:152)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:496)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:756)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)[activemq-client-5.10.0.jar:5.10.0]
>   at java.lang.Thread.run(Unknown Source)[:1.8.0_11]
> For example I'm getting 131191 messages out of 1000,000 on the queue and the 
> performance test is freezing.
> I'm running the test with the following command:
> mvn activemq-perf:producer -Dfactory.brokerURL=tcp://hostname:20039 
> -DsysTest.numClients=4 -Dproducer.destName=queue://test 
> -Dproducer.deliveryMode=persistent -Dfactory.useAsyncSend=true
> I've changed the activemq.xml persistenceAdapter as shown:
> 
>  enableJournalDiskSyncs="false" indexWriteBatchSize="1" 
> indexCacheSize="1000"/>
> 
> Thanks,
> Octavian



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ARTEMIS-274) Make ActiveMQThreadFactory instantiation running within doPrivileged block

[Ivo Studensky (JIRA)]

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

Ivo Studensky updated ARTEMIS-274:
--
Fix Version/s: 1.2.0

> Make ActiveMQThreadFactory instantiation running within doPrivileged block
> --
>
> Key: ARTEMIS-274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-274
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Ivo Studensky
> Fix For: 1.2.0, 1.1.1
>
>
> At the moment, ActiveMQThreadFactory caches AccessControlContext inside of 
> its constructor and uses it later in newThread() method invocation to create 
> a thread inside of doPrivileged block. This leads to not enough permissions 
> issue when a client is trying to create a new connection on a factory taken 
> from JNDI, see https://issues.jboss.org/browse/WFLY-5166.
> To fix it all the invocations of the factory constructor should run within a 
> privileged block to get a privileged ACC to the factory. This change should 
> be similar to how it works in WildFly right now. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-265) Description for lauching Artemis broker on background is wrong

[Frantisek Reznicek (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969138#comment-14969138
 ] 

Frantisek Reznicek commented on ARTEMIS-265:


Thanks for fix, now it looks much better.

> Description for lauching Artemis broker on background is wrong
> --
>
> Key: ARTEMIS-265
> URL: https://issues.apache.org/jira/browse/ARTEMIS-265
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.1
> Environment: apache-artemis-1.1.1-20151020.030137-16-bin.zip on a 
> RHEL 6.7 x86_64 machine
>Reporter: Frantisek Reznicek
>Priority: Minor
>
> Description for lauching Artemis broker on background is wrong see below the 
> transcript:
> {noformat}
> [artemis@dhcp-x-y-z apache-activemq-artemis-1]$ bin/artemis create 
> --user=artemis --password artemis --allow-anonymous 
> /opt/apache-activemq-artemis-1-i0
> Creating ActiveMQ Artemis instance at: /opt/apache-activemq-artemis-1-i0
> Auto tuning journal ...
> done! Your system can make 0,12 writes per millisecond, your 
> journal-buffer-timeout will be 8364000
> You can now start the broker by executing:
>"/opt/apache-activemq-artemis-1-i0/bin/artemis" run
> Or you can setup the broker as system service and run it in the background:
> /opt/apache-activemq-artemis-1-i0/bin/artemis-service
>/etc/init.d/artemis-service start
> [artemis@dhcp-x-y-z apache-activemq-artemis-1]$ 
> /opt/apache-activemq-artemis-1-i0/bin/artemis-service 
> /etc/init.d/artemis-service start
> Usage: /opt/apache-activemq-artemis-1-i0/bin/artemis-service 
> {start|stop|restart|force-stop|status}
> [artemis@dhcp-x-y-z apache-activemq-artemis-1]$ 
> /opt/apache-activemq-artemis-1-i0/bin/artemis-service start
> Starting artemis-service
> artemis-service is now running (9939)
> {noformat}
> Note that 
> Or you can setup the broker as system service and run it in the background:
> /opt/apache-activemq-artemis-1-i0/bin/artemis-service
>/etc/init.d/artemis-service start
> is wrong and should be:
>  * /opt/apache-activemq-artemis-1-i0/bin/artemis-service start
>  * on one line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-266) Artemis creating instance concept of --aio switch is not flexible enough

[Frantisek Reznicek (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969139#comment-14969139
 ] 

Frantisek Reznicek commented on ARTEMIS-266:


Thanks, works well.

> Artemis creating instance concept of --aio switch is not flexible enough
> 
>
> Key: ARTEMIS-266
> URL: https://issues.apache.org/jira/browse/ARTEMIS-266
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 1.1.1
> Environment: apache-artemis-1.1.1-20151020.030137-16-bin.zip on a 
> RHEL 6.7 x86_64 machine
>Reporter: Frantisek Reznicek
>Priority: Minor
>
> Artemis creating instance concept of --aio switch is not flexible enough.
> The functionality of forcing configuration to use AIO with --aio switch is 
> not flexible enough.
> We have three states there:
>  * autodetection
>  * force AIO with --aio
>  * force to not use AIO
> I'd recomment to change to be able to force third option as well (this is in 
> particular handy for QE).
> Thus I propose two options:
> a] keep --aio or change to --aio-cfg which would get additional argument 
> (AUTO, AIO, NOAIO), where AUTO is default
> b] keep --aio as is and introduce --no-aio for forcing the third case (this 
> is a bit awkward from command-line switch point of view, but keeps full 
> backward compatibility)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-274) Make ActiveMQThreadFactory instantiation running within doPrivileged block

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969156#comment-14969156
 ] 

ASF GitHub Bot commented on ARTEMIS-274:


Github user clebertsuconic commented on the pull request:

https://github.com/apache/activemq-artemis/pull/211#issuecomment-150224242
  
I will merge this, but i will first ammend the checkstyle issue, and the 
change I asked here...

I will run the entire testsuite first.. so it will take me 1 hour before I 
can merge this.


> Make ActiveMQThreadFactory instantiation running within doPrivileged block
> --
>
> Key: ARTEMIS-274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-274
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Ivo Studensky
> Fix For: 1.2.0, 1.1.1
>
>
> At the moment, ActiveMQThreadFactory caches AccessControlContext inside of 
> its constructor and uses it later in newThread() method invocation to create 
> a thread inside of doPrivileged block. This leads to not enough permissions 
> issue when a client is trying to create a new connection on a factory taken 
> from JNDI, see https://issues.jboss.org/browse/WFLY-5166.
> To fix it all the invocations of the factory constructor should run within a 
> privileged block to get a privileged ACC to the factory. This change should 
> be similar to how it works in WildFly right now. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-4361) Deadlock during close while publishing to flow-controlled queue

[Sam hendley (JIRA)]

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

Sam hendley commented on AMQ-4361:
--

We recently updated to 5.12.0 and a test I had put in place to track the 
"higher level" shutdown started failing occasionally. I still haven't worked 
out the cause of that but I did try enabling ProducerWindowSize to verify the 
fix to this bug. So technically it closes quickly but it is throwing an 
IllegalMonitorStateException. There is a bug in the waitForSpace method where 
we don't relock the readLock if the waitForSpaceCondition throws.

{{
java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked 
by current thread
at 
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:447)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:431)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1340)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:883)
at 
org.apache.activemq.usage.MemoryUsage.waitForSpace(MemoryUsage.java:87)
at 
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:282)
at 
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:223)
at 
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:269)
at 
org.springframework.jms.connection.CachedMessageProducer.send(CachedMessageProducer.java:181)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:636)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:607)
at 
org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:572)
at 
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:494)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:569)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:560)
at 
com.sms.jms.FastInterruptibleSingleDestinationJmsOutClient.send(FastInterruptibleSingleDestinationJmsOutClient.java:77)
at 
com.sms.jms.FastInterruptibleSingleDestinationJmsOutClient.publishAsBytesMessage(FastInterruptibleSingleDestinationJmsOutClient.java:68)
at 
com.sms.jms.FastInterruptibleSingleDestinationJmsOutClientTest$2.run(FastInterruptibleSingleDestinationJmsOutClientTest.java:83)
at java.lang.Thread.run(Thread.java:744)
}}

{code}
public boolean waitForSpace(long timeout) throws InterruptedException {
if (parent != null) {
if (!parent.waitForSpace(timeout)) {
return false;
}
}
usageLock.readLock().lock();
try {
if (percentUsage >= 100) {
usageLock.readLock().unlock();
usageLock.writeLock().lock();
try {
while (percentUsage >= 100 ) {
waitForSpaceCondition.await(timeout, 
TimeUnit.MILLISECONDS);
}
// I believe this relocking needs to be in the finally 
block.
usageLock.readLock().lock();
} finally {
usageLock.writeLock().unlock();
}
}

return percentUsage < 100;
} finally {
usageLock.readLock().unlock();
}
}
{code}

> Deadlock during close while publishing to flow-controlled queue
> ---
>
> Key: AMQ-4361
> URL: https://issues.apache.org/jira/browse/AMQ-4361
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.6.0, 5.8.0
> Environment: Windows, Linux, JDK 1.6
>Reporter: Sam hendley
>Assignee: Timothy Bish
> Fix For: 5.9.0
>
>
> TestCase on github: 
> https://github.com/samhendley/activemq-close-deadlock-bug
> The deadlock occurs when we are using TcpTransport to a flow-controlled queue 
> and we then try to gracefully shutdown the application. The close operation 
> hangs forever because it is trying to send a "close packet" to the server. It 
> never gets the chance to send that request because the socket is blocked by 
> the publishing thread. This stops my publisher from shutting down and causes 
> us to orphan threads during shutdown.
> I have verified this bug occurs on atleast activemq 5.6.0 and 5.8.0 and on 
> linux and windows using JDK 1.6.
> I don't need a fix for the bug necessarily, just a way to gracefully shutdown 
> my publisher if I get into this state.
> Partial Stack Trace During failure
> "ClosingThread" prio=6 

[jira] [Commented] (ARTEMIS-274) Make ActiveMQThreadFactory instantiation running within doPrivileged block

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969086#comment-14969086
 ] 

ASF GitHub Bot commented on ARTEMIS-274:


GitHub user istudens opened a pull request:

https://github.com/apache/activemq-artemis/pull/211

ARTEMIS-274 ActiveMQThreadFactory has to be constructed within doPriv…

…ileged block

https://issues.apache.org/jira/browse/ARTEMIS-274

This fix is related to 
https://issues.jboss.org/browse/WFLY-5166
https://issues.jboss.org/browse/JBEAP-814

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/istudens/activemq-artemis JBEAP-814

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/211.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #211


commit 32834634e436410004c2453b3b020ff86d9996db
Author: Ivo Studensky 
Date:   2015-10-22T12:22:41Z

ARTEMIS-274 ActiveMQThreadFactory has to be constructed within doPrivileged 
block




> Make ActiveMQThreadFactory instantiation running within doPrivileged block
> --
>
> Key: ARTEMIS-274
> URL: https://issues.apache.org/jira/browse/ARTEMIS-274
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Ivo Studensky
> Fix For: 1.2.0, 1.1.1
>
>
> At the moment, ActiveMQThreadFactory caches AccessControlContext inside of 
> its constructor and uses it later in newThread() method invocation to create 
> a thread inside of doPrivileged block. This leads to not enough permissions 
> issue when a client is trying to create a new connection on a factory taken 
> from JNDI, see https://issues.jboss.org/browse/WFLY-5166.
> To fix it all the invocations of the factory constructor should run within a 
> privileged block to get a privileged ACC to the factory. This change should 
> be similar to how it works in WildFly right now. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-269) restart-backup attribute should be true by default

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969147#comment-14969147
 ] 

ASF subversion and git services commented on ARTEMIS-269:
-

Commit 31f23893439541ddebc35fec193ee372d0d62aaa in activemq-artemis's branch 
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=31f2389 ]

ARTEMIS-269 - sett restartBackup to true by default

https://issues.apache.org/jira/browse/ARTEMIS-269


> restart-backup attribute should be true by default
> --
>
> Key: ARTEMIS-269
> URL: https://issues.apache.org/jira/browse/ARTEMIS-269
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.0
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> it makes sense for the default to be true so a backup restarts by default 
> instead of going down



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ARTEMIS-275) Artemis creating instance request for switch which disables persistance

[Frantisek Reznicek (JIRA)]

Frantisek Reznicek created ARTEMIS-275:
--

 Summary: Artemis creating instance request for switch which 
disables persistance
 Key: ARTEMIS-275
 URL: https://issues.apache.org/jira/browse/ARTEMIS-275
 Project: ActiveMQ Artemis
  Issue Type: Improvement
Reporter: Frantisek Reznicek
Priority: Minor


I'd like to request new switch for disabling persistence on create instance 
interface.
I understand that create instance is not going to cover all configuration 
possibilities, but switch like --no-persistance would be good to have there 
(influencing persistence-enabled xml value).




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-6018) Web console should not export any OSGi packages

[Christian Schneider (JIRA)]

Christian Schneider created AMQ-6018:


 Summary: Web console should not export any OSGi packages
 Key: AMQ-6018
 URL: https://issues.apache.org/jira/browse/AMQ-6018
 Project: ActiveMQ
  Issue Type: Bug
  Components: webconsole
Affects Versions: 5.11.2
Reporter: Christian Schneider
 Fix For: 5.11.3


The ActiveMQ web console exports all packages it embeds.
This has the effect that e.g. ActiveMQConnectionFactory is exported in the same 
version by multiple bundles (activemq and activemq web console) which can lead 
to class cast exceptions.

I suggest to remove the exports from the activemq web console war.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6018) Web console should not export any OSGi packages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on AMQ-6018:
-

GitHub user cschneider opened a pull request:

https://github.com/apache/activemq/pull/152

[AMQ-6018] Web console should not export any OSGi packages



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cschneider/activemq AMQ-6018

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/152.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #152


commit 901ebe629a99939b2f35c3c847ea9227102526fc
Author: Christian Schneider 
Date:   2015-10-22T15:25:31Z

[AMQ-6018] Web console should not export any OSGi packages




> Web console should not export any OSGi packages
> ---
>
> Key: AMQ-6018
> URL: https://issues.apache.org/jira/browse/AMQ-6018
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.2
>Reporter: Christian Schneider
> Fix For: 5.11.3
>
>
> The ActiveMQ web console exports all packages it embeds.
> This has the effect that e.g. ActiveMQConnectionFactory is exported in the 
> same version by multiple bundles (activemq and activemq web console) which 
> can lead to class cast exceptions.
> I suggest to remove the exports from the activemq web console war.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-6019) TheListIndex is not loaded exception under heavier load

[Octavian (JIRA)]

Octavian created AMQ-6019:
-

 Summary: TheListIndex is not loaded exception under heavier load
 Key: AMQ-6019
 URL: https://issues.apache.org/jira/browse/AMQ-6019
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker, KahaDB
Affects Versions: 5.10.0
 Environment: AcitveMQ 5.10.0 on Windows Server 2012R2 DataCenter
Reporter: Octavian


Hello,

I'm trying to run the performance test with posting 1,000,000 messages from 4 
producers to ActiveMQ. Many times I'm getting the following exception in 
ActiveMQ Broker logs and it looks like the broker is not accepting any more 
messages:

2015-10-22 09:30:45,314 | WARN  | Async error occurred:  | 
org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: 
tcp:///10.80.35.179:56140@20039
java.lang.RuntimeException: java.lang.IllegalStateException: TheListIndex is 
not loaded
at 
org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:244)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.addMessageLast(FilePendingMessageCursor.java:207)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1855)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:939)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.Queue.send(Queue.java:733)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:424)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:147)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:152)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:496)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:756)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)[activemq-broker-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)[activemq-client-5.10.0.jar:5.10.0]
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)[activemq-client-5.10.0.jar:5.10.0]
at java.lang.Thread.run(Unknown Source)[:1.8.0_11]



For example I'm getting 131191 messages out of 1000,000 on the queue and the 
performance test is freezing.

I'm running the test with the following command:
mvn activemq-perf:producer -Dfactory.brokerURL=tcp://hostname:20039 
-DsysTest.numClients=4 -Dproducer.destName=queue://test 
-Dproducer.deliveryMode=persistent -Dfactory.useAsyncSend=true

I've changed the activemq.xml persistenceAdapter as shown:




Thanks,
Octavian





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6019) TheListIndex is not loaded exception under heavier load

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-6019:
---

Have you tested with the latest release v5.12.1 ?

> TheListIndex is not loaded exception under heavier load
> ---
>
> Key: AMQ-6019
> URL: https://issues.apache.org/jira/browse/AMQ-6019
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, KahaDB
>Affects Versions: 5.10.0
> Environment: AcitveMQ 5.10.0 on Windows Server 2012R2 DataCenter
>Reporter: Octavian
>
> Hello,
> I'm trying to run the performance test with posting 1,000,000 messages from 4 
> producers to ActiveMQ. Many times I'm getting the following exception in 
> ActiveMQ Broker logs and it looks like the broker is not accepting any more 
> messages:
> 2015-10-22 09:30:45,314 | WARN  | Async error occurred:  | 
> org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: 
> tcp:///10.80.35.179:56140@20039
> java.lang.RuntimeException: java.lang.IllegalStateException: TheListIndex is 
> not loaded
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:244)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.addMessageLast(FilePendingMessageCursor.java:207)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1855)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:939)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.send(Queue.java:733)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:424)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:147)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:152)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:496)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:756)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)[activemq-client-5.10.0.jar:5.10.0]
>   at java.lang.Thread.run(Unknown Source)[:1.8.0_11]
> For example I'm getting 131191 messages out of 1000,000 on the queue and the 
> performance test is freezing.
> I'm running the test with the following command:
> mvn activemq-perf:producer -Dfactory.brokerURL=tcp://hostname:20039 
> -DsysTest.numClients=4 -Dproducer.destName=queue://test 
> -Dproducer.deliveryMode=persistent -Dfactory.useAsyncSend=true
> I've changed the activemq.xml persistenceAdapter as shown:
> 
>  enableJournalDiskSyncs="false" indexWriteBatchSize="1" 
> indexCacheSize="1000"/>
> 
> Thanks,
> Octavian



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6019) TheListIndex is not loaded exception under heavier load

[Octavian (JIRA)]

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

Octavian commented on AMQ-6019:
---

I was looking at AMQ-4239 and indeed - I am doing PURGEs between tests from 
frontend. So it might be related to the Purge. I will try to test with 5.12.1

> TheListIndex is not loaded exception under heavier load
> ---
>
> Key: AMQ-6019
> URL: https://issues.apache.org/jira/browse/AMQ-6019
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, KahaDB
>Affects Versions: 5.10.0
> Environment: AcitveMQ 5.10.0 on Windows Server 2012R2 DataCenter
>Reporter: Octavian
>
> Hello,
> I'm trying to run the performance test with posting 1,000,000 messages from 4 
> producers to ActiveMQ. Many times I'm getting the following exception in 
> ActiveMQ Broker logs and it looks like the broker is not accepting any more 
> messages:
> 2015-10-22 09:30:45,314 | WARN  | Async error occurred:  | 
> org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: 
> tcp:///10.80.35.179:56140@20039
> java.lang.RuntimeException: java.lang.IllegalStateException: TheListIndex is 
> not loaded
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:244)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.addMessageLast(FilePendingMessageCursor.java:207)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1855)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:939)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.Queue.send(Queue.java:733)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:424)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:147)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:152)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:496)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:756)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)[activemq-broker-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)[activemq-client-5.10.0.jar:5.10.0]
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)[activemq-client-5.10.0.jar:5.10.0]
>   at java.lang.Thread.run(Unknown Source)[:1.8.0_11]
> For example I'm getting 131191 messages out of 1000,000 on the queue and the 
> performance test is freezing.
> I'm running the test with the following command:
> mvn activemq-perf:producer -Dfactory.brokerURL=tcp://hostname:20039 
> -DsysTest.numClients=4 -Dproducer.destName=queue://test 
> -Dproducer.deliveryMode=persistent -Dfactory.useAsyncSend=true
> I've changed the activemq.xml persistenceAdapter as shown:
> 
>  enableJournalDiskSyncs="false" indexWriteBatchSize="1" 
> indexCacheSize="1000"/>
> 
> Thanks,
> Octavian



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)