Unable to start my C++ client to connect to ActiveMQ

Issue

I'm encountering the following error when I start my application:

MessagingTrial.exe!decaf::internal::util::concurrent::Threading::lockThreadsLib()  Line 868 + 0x5 bytes  C++
  MessagingTrial.exe!decaf::internal::util::concurrent::Mutex::lock()  Line 116  C++
  MessagingTrial.exe!decaf::internal::util::concurrent::Lock::lock()  Line 55  C++
  MessagingTrial.exe!decaf::internal::util::concurrent::Lock::Lock(decaf::util::concurrent::Synchronizable * object, const bool initiallyLocked)  Line 34  C++
  MessagingTrial.exe!activemq::core::ActiveMQConnectionFactory::setBrokerURI(const decaf::net::URI & uri)  Line 461 + 0x17 bytes  C++
  MessagingTrial.exe!activemq::core::ActiveMQConnectionFactory::ActiveMQConnectionFactory(const
     std::basic_string<char,std::char_traits<char>,std::allocator<char> > & uri, const
     std::basic_string<char,std::char_traits<char>,std::allocator<char> > & username, const
     std::basic_string<char,std::char_traits<char>,std::allocator<char> > & password)  Line 249 + 0x3b bytes  C++
  MessagingTrial.exe!cms::ConnectionFactory::createMCSConnectionFactory(const
     std::basic_string<char,std::char_traits<char>,std::allocator<char> > & brokerURI)  Line 237 + 0x77 bytes  C++
  MessagingTrial.exe!MessagingTrial::Min_Send::connectAndSend()  Line 34 + 0xa bytes  C++
  MessagingTrial.exe!wmain(int argc, wchar_t * * argv)  Line 13  C++
  MessagingTrial.exe!__tmainCRTStartup()  Line 552 + 0x19 bytes  C
  MessagingTrial.exe!wmainCRTStartup()  Line 371  C
  kernel132.dll!769e399a()
  [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
  ntdll.dll!775d9ef2()
  ntdll.dll!775d9ec5()

The relevant lines in my application are:

void Min_Send::connectAndSend()
{
   try
   {
      ConnectionFactory* connectionFactory = ConnectionFactory::createCMSConnectionFactory(url);
   }
}

The call to createCMSConnectionFactory(url) is line 34 mentioned in the trace. Since this is the call that is failing, I don't think the connection is the issue. The A-MQ logs don't show any issues on the broker side.

What could be wrong?