users-unsubscribe@

2018-04-23 Thread Hickerson (US), David A

Re: qpid-jms-client --> 0.31.0, Azure Service Bus - Cannot allocate more handles to the current session or connection. The maximum number of handles allowed is 4999.

2018-04-23 Thread Timothy Bish 

On 04/23/2018 05:45 PM, Abhishek Kumar wrote:

HI Team,

I am using "qpid-jms-client --> 0.31.0" for sending message to Azure 
Service Bus. I am sending 10K msgs. While sending 10k messages only 5k 
messages successfully sent. After sending 5k messages, i am 
continuously getting error" Cannot allocate more handles to the 
current session or connection.The maximum number of handles allowed is 
4999. Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded] (javax.jms.ResourceAllocationException) "


I opened "jvisualvm" and found that lot of "JmsSession Completion 
Dispatcher" thread are open. Please find attached screen shot.  I did 
a lot R but i could not find any solution to solve this issue.




This would suggest that you are creating a number of JMS Sessions in 
your application and those are not being closed.  The completion thread 
is generally not created unless you are doing JMS 2.0 style asynchronous 
sends so you could start by reviewing that area of your code to see if 
you have a resource leak which would be my first suspicion given the 
error that you are receiving.


Could you please suggest any solution to solve this issue. Please find 
below code snippet and error details



*_Error Stack Trace_*
*_
_*

Message               : Cannot allocate more handles to the current 
session or connection. The maximum number of handles allowed is 4999. 
Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded] (javax.jms.ResourceAllocationException)

JMS Code              : null
Element               : /servicebusConnector @ app:test-mule-jms.xml:19

Root Exception stack trace:
javax.jms.ResourceAllocationException: Cannot allocate more handles to 
the current session or connection. The maximum number of handles 
allowed is 4999. Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded]
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:145)
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
at 
org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:262)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:973)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:104)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:831)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)



*_Connection CODE_*
Hashtable hashtable = new Hashtable<>();
hashtable.put("connectionfactory.SBCF","failover:(amqps://" + host + 
")?failover.reconnectDelay=2000=20=true=3=10");

hashtable.put("queue.QUEUE", "iptest2");

hashtable.put(Context.INITIAL_CONTEXT_FACTORY, 
QPID_CONNECTION_FACTORY_CLASS);


Context context = new InitialContext(hashtable);

ConnectionFactory connectionFactory = (ConnectionFactory) 
context.lookup("SBCF");


destination = (Destination) context.lookup("QUEUE");

// Create Connection
Connection connection = connectionFactory.createConnection(username, 
password);


connection.setExceptionListener(this);
connection.start();

Session session = connection.createSession(false, 
Session.CLIENT_ACKNOWLEDGE);

MessageProducer producer = session.createProducer(destination);

this.setJmsSession(session);
this.setMessageProducer(producer);
this.setDestination(destination);
this.setConnection(connection);


*_Sender - Parallel 16 threads are running to send_*
/               producer.send(jmsMessage);/

Regards,
Abhishek Kumar




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/

qpid-jms-client --> 0.31.0, Azure Service Bus - Cannot allocate more handles to the current session or connection. The maximum number of handles allowed is 4999.

2018-04-23 Thread Abhishek Kumar 
HI Team,

I am using "qpid-jms-client --> 0.31.0" for sending message to Azure
Service Bus. I am sending 10K msgs. While sending 10k messages only 5k
messages successfully sent. After sending 5k messages, i am continuously
getting error " Cannot allocate more handles to the current session or
connection. The maximum number of handles allowed is 4999. Please free up
resources and try again. [condition = amqp:resource-limit-exceeded]
(javax.jms.ResourceAllocationException) "

I opened "jvisualvm" and found that lot of "JmsSession Completion
Dispatcher" thread are open. Please find attached screen shot.  I did a lot
R but i could not find any solution to solve this issue.

Could you please suggest any solution to solve this issue. Please find
below code snippet and error details


*Error Stack Trace*


Message   : Cannot allocate more handles to the current session
or connection. The maximum number of handles allowed is 4999. Please free
up resources and try again. [condition = amqp:resource-limit-exceeded]
(javax.jms.ResourceAllocationException)
JMS Code  : null
Element   : /servicebusConnector @ app:test-mule-jms.xml:19

Root Exception stack trace:
javax.jms.ResourceAllocationException: Cannot allocate more handles to the
current session or connection. The maximum number of handles allowed is
4999. Please free up resources and try again. [condition =
amqp:resource-limit-exceeded]
at
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:145)
at
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
at
org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:262)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:973)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:104)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:831)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)



*Connection CODE*
Hashtable hashtable = new Hashtable<>();
hashtable.put("connectionfactory.SBCF", "failover:(amqps://" + host +
")?failover.reconnectDelay=2000=20=true=3=10");
hashtable.put("queue.QUEUE", "iptest2");

hashtable.put(Context.INITIAL_CONTEXT_FACTORY,
QPID_CONNECTION_FACTORY_CLASS);

Context context = new InitialContext(hashtable);

ConnectionFactory connectionFactory = (ConnectionFactory)
context.lookup("SBCF");

destination = (Destination) context.lookup("QUEUE");

// Create Connection
Connection connection = connectionFactory.createConnection(username,
password);

connection.setExceptionListener(this);
connection.start();

Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(destination);

this.setJmsSession(session);
this.setMessageProducer(producer);
this.setDestination(destination);
this.setConnection(connection);


*Sender - Parallel 16 threads are running to send*
*   producer.send(jmsMessage);*

Regards,
Abhishek Kumar

Re: qpid-proton cpp windows : Crash

2018-04-23 Thread Alan Conway 
On Mon, Apr 23, 2018 at 5:37 AM, Baptiste Robert  wrote:

> Hello,
>
> I'm encountering a crash in the proton library. What I'm doing ? Just
> creating a proton::container, listening locally on 0.0.0.0:5672 and then
> call stop() on the container and getting outside of the scope (object is
> then destroy) => the crash happen.
>
> Where does it crash ? In *win_iocp.c*, the line in red
>
> void pn_proactor_free(pn_proactor_t *p) {
>   *DeleteTimerQueueEx(p->timer_queue, INVALID_HANDLE_VALUE);*
>   DeleteCriticalSection(>timer_lock);
>   DeleteCriticalSection(>bind_lock);
>   proactor_shutdown(p);
>
>   delete p->reaper;
>   WSACleanup();
>   pn_collector_free(p->collector);
>   free(p);
> }
>
>
> Proton version : 0.21
> Windows 7 - 64 bits
> Visual studio 2010
>
> Does any one have a clue ? It remind me this issue on the dispatch router:
> https://issues.apache.org/jira/browse/DISPATCH-945
>
>
Sounds like a bug. Can you raise a JIRA and attach your code to reproduce?
The dispatch issue is not quite the same (dispatch has 2 server loops, one
for AMQP and one for HTTP) but I believe we did fix a similar issue in the
epoll proactor a while back.

-- 

> Baptiste Robert
>

Re: [Proton Python binding] Heads Up: Removing support for python versions before 2.6

2018-04-23 Thread Ken Giusti 
No objection here.

Thanks,


On Fri, Apr 20, 2018 at 5:57 PM, Andrew Stitcher  wrote:
> I've been doing some work on the proton python code recently and I've
> noticed we're carrying around code to support python 2.5 and perhaps
> even 2.4.
>
> The only Python 2 version that is still maintained by python.org is
> 2.7. But RHEL 6/CentOS 6 still support Python 2.6.
>
> So I've started removing the support for the earlier versions of
> python. This simplifies the code somewhat and moves the python code
> much closer to conventional python.
>
> Given that Python 2 stops being maintained at all in a couple of years
> and "everyone" is migrating to Python 3, I think this should be
> uncontroversial - any opposition?
>
> Andrew
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>



-- 
-K

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

qpid-proton cpp windows : Crash

2018-04-23 Thread Baptiste Robert 
Hello,

I'm encountering a crash in the proton library. What I'm doing ? Just
creating a proton::container, listening locally on 0.0.0.0:5672 and then
call stop() on the container and getting outside of the scope (object is
then destroy) => the crash happen.

Where does it crash ? In *win_iocp.c*, the line in red

void pn_proactor_free(pn_proactor_t *p) {
  *DeleteTimerQueueEx(p->timer_queue, INVALID_HANDLE_VALUE);*
  DeleteCriticalSection(>timer_lock);
  DeleteCriticalSection(>bind_lock);
  proactor_shutdown(p);

  delete p->reaper;
  WSACleanup();
  pn_collector_free(p->collector);
  free(p);
}


Proton version : 0.21
Windows 7 - 64 bits
Visual studio 2010

Does any one have a clue ? It remind me this issue on the dispatch router:
https://issues.apache.org/jira/browse/DISPATCH-945

-- 
Baptiste Robert