Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates
 209.85.128.48 as permitted sender)
Message-ID: <52A0654D.4040800@gmail.com>
Date: Thu, 05 Dec 2013 06:36:45 -0500
From: Timothy Bish <tabish121@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Re: ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization
References: 
 <CAAhPa9J0cxAaOwwhRU1FDxT73k7SF4dmXWyAsBYvHRT7Ljjc8A@mail.gmail.com>
In-Reply-To: 
 <CAAhPa9J0cxAaOwwhRU1FDxT73k7SF4dmXWyAsBYvHRT7Ljjc8A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/05/2013 02:57 AM, Nikolaus Klimek wrote:
> Hello,
>
> because our previous SLES Version does not support required apr-version, we
> used the ActiveMQ C++ Client 2.2.6, which was compiled to a shared
> object/library and called by a cobol application (via CALL). This
> combination
> works fine.
>
> Actually we updated our SLES (to 11.2) and a higher apr-version now is
> supported. So we tried to use a higher-version of the ActiveMQ C++ Client
> (e.g. 3.0, ... , 3.8.1), which we compiled to a shared object for calling
> via a cobol application, too. Calling the new version now causes a
> segmentation fault, the ActiveMQ shared object crashes on initialization,
> before any command is executed. We think it deals with loading/initialising
> the activemq library (activemq::library; ActiveMQCPP::initializeLibrary()),
> because it is new since version 3.0.0.
> Another point is we reduced our ActiveMQ shared object to only print a
> line. This certainly works. Adding the command activemq::library;
> ActiveMQCPP::initializeLibrary() causes the identicall segfault. Bizarrely
> calling the identical shared object from a C++ application works.
>
> We don't understand why calling the ActiveMQ shared object doens't work
> from cobol, however it works calling from a C++ application. With a release
> <=2.2.6 both call variations working.
>
> We hope you have any ideas for let us understand this issue or to give us
> some advice for solving this problem.
>
> Thanks in regards!
> Niko
>
Well the CMS libraries are not tested under this sort of scenario so I 
can't really offer much help without more information.  You should do 
some debugging and try and figure out what the stack trace is at the 
time of the segmentation fault.

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