SDK Perf Util vs Solace Client Code

sateesh · April 2, 2020, 3:38am

Hi All,
Went through our Solace Client code (JNDI + JMS Based) multiple times and it is based on

github.com/SolaceSamples/solace-samples-jms

src/main/java/com/solace/samples/QueueConsumerJNDI.java

master

/**
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */

/**

This file has been truncated. show original

except that we create each Consumer in it’s own thread and it used it’s own dedicated JMS Connection, Session and Message Consumer.
I was using solace jars from version 10.1.1 all these days and switched them to 10.8.0 and it seems i am no longer seeing the Naming Exception or SocketTimeoutExceptions i was seeing earlier.

Thanks
Sateesh

Topic		Replies	Views
Problem with performance of our solace consumer PubSub+ Event Broker	25	4750	February 26, 2020
JMS Sliding Window acknowledgement PubSub+ Event Broker	0	75	January 22, 2024
Solace Client running out of memory with multiple consumers PubSub+ Event Broker jms	1	974	November 25, 2019
Excuting sdkperf in windows PubSub+ Event Broker	3	167	January 19, 2024
Solace PubSub+ APIs (JMS/JCSMP, C, .NET) are released PubSub+ Event Broker	17	36300	September 16, 2022

SDK Perf Util vs Solace Client Code

Related topics