[ANNOUNCE] Apache Qpid for Java 6.1.6 released

[Alex Rudyy]

The Apache Qpid (https://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid for Java 6.1.6.

This release addresses defects and enhancements in Qpid Broker-J
(previously known as Qpid Broker for Java).

The release is available now from our website:
https://qpid.apache.org/releases/qpid-java-6.1.6/index.html

Binaries are also available via Maven Central:
https://qpid.apache.org/maven.html

Release notes can be found at:
https://qpid.apache.org/releases/qpid-java-6.1.6/release-notes.html

Thanks to all involved,
Alex

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

[ANNOUNCE] Apache Qpid Broker-J 7.0.3 released

[Alex Rudyy]

The Apache Qpid (http://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Broker-J 7.0.3.

This release addresses defects and enhancements in Qpid Broker-J

The release is available now from our website:
https://qpid.apache.org/download.html

Release notes can be found at:
https://qpid.apache.org/releases/qpid-broker-j-7.0.3/release-notes.html

Qpid Broker-J 7.0.3 release page can be found here:
https://qpid.apache.org/releases/qpid-broker-j-7.0.3/index.html

Thanks to all involved,
Alex

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

Re: Qpid Dispatch Router release (1.1.0)

[Ted Ross]

On Tue, Apr 3, 2018 at 12:24 PM, Ted Ross  wrote:
> Since the release of Qpid Proton 0.22.0, Qpid Dispatch Router's tests
> fail against the latest released Proton because of the removal of the
> deprecated Messenger API.  We are planning to push some of the
> in-progress Jiras to the next release so we can produce version 1.1.0
> soon.
>
> Please look for a release candidate for 1.1.0 this week.

This will not arrive until next week.  We haven't yet closed out all the issues.

>
> -Ted

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

Re: Proton C source reorg and removal of deprecated or obsolete code

[Alan Conway]

Well done, what a monster! Now to weed out the last of the messenger code...

On Thu, Apr 5, 2018 at 3:40 PM, Justin Ross  wrote:

> Just a note to everyone that the Proton C source reorg has now landed on
> master.  Please let me know if you have any trouble.
>
> https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=tree;h=HEAD
>
> On Wed, Mar 14, 2018 at 5:40 AM, Alan Conway  wrote:
>
> > On Mon, Mar 12, 2018 at 12:14 PM, Justin Ross 
> > wrote:
> >
> > > > src/messenger still there - oversight, or do we need to hold onto
> this?
> > > >
> > >
> > > It's still used by one of the test tools.
> > >
> > >
> > We can replace msgr-send.c and msgr-recv.c by copying from
> > examples/c/[send.c, send-ssl.c, receive.c] and adding options (ssl
> config,
> > container name, prefetch etc.) IMO a  day or two of work. The examples
> > already have the required code, just need to parameterize it with command
> > line options. Not required for the initial re-org, but something to do
> > shortly after.
> >
>

Re: Build QPID C++ Using Visual Studio 2013 on Windows 10

[Chuck Rolke]

Hi Michael,

Replies in line.

-Chuck

- Original Message -
> From: "Michael Arnold" 
> To: users@qpid.apache.org
> Sent: Thursday, April 5, 2018 10:17:04 AM
> Subject: Re: Build QPID C++ Using Visual Studio 2013 on Windows 10
> 
> Thanks Chuck,
> 
> Downgrading python from 3.6.1 (python 3) to 2.7.17 (python 2), allowed
> cmake to generate the build files.  I did not encouter QPID-8155.
> 
> On the build side, 3 types of errors:
> 1. QPID-7926 as you describe.
> 
> 2. Link errors of the form: error LNK1104: cannot open file
> 'Debug\qpidcommond.lib'
> C:\Users\myk32\Documents\Development\qpid-bin\src\LINK
> --> the *.lib files don't appear to exist.  Any pointers?

The QPID-7926 prevents building qpidcommon.lib/dll. From there on all the
other components fail as everything needs qpidcommon. I'm not sure
exactly how to fix this but the issue has been known for six months.

> 
> 3. Link errors of the form: error C1083: Cannot open include file:
> 'proton/engine.h': No such file or directory
> --> I assume this is because I have not run a 'make install' in the proton
> build directory, but not sure how to do this on windows.  Any pointers?

The best approach is to have projects qpid-proton (qpid-cpp needs this for
AMQP 1.0 support) and qpid-cpp share the same install directory. Build
qpid-proton 'install' project first and that populates the install area
with the include files and libraries that qpid-cpp needs.

For example:
1) In directory D:\git clone qpid-proton and qpid-cpp. Then you have
  D:\git\qpid-proton
  D:\git\qpid-cpp
2) From qpid-proton\build launch a proton build with something like:
  cmake -G "Visual Studio 15 2017 Win64" 
-DCMAKE_INSTALL_PREFIX=D:\git\qpid-cpp\install_2017_x64 ..
  devenv proton.sln /build "Debug|x64"  /project INSTALL
3) Then from qpid-cpp\build
  CMake -G "Visual Studio 15 2017 Win64" 
-DCMAKE_INSTALL_PREFIX=D:\git\qpid-cpp\install_2017_x64" 
 "-DBoost_COMPILER=-vc141" 
"-DBOOST_ROOT=D:\boost\boost-win-1.65-64bit-vs2017" D:git\qpid-cpp
  devenv qpid-cpp.sln /build "Debug|x64"  /project INSTALL

I used to maintain some scripts to help me with managing multiple visual studio 
versions
and the boost dependencies in 
https://github.com/ChugR/qpid-proton-tools/tree/master/bat
Files build_proton.bat and build-qpid-cpp.bat took care of steps 2 and 3 shown 
above. 

> 
> On Thu, Apr 5, 2018 at 4:12 AM, Chuck Rolke  wrote:
> 
> > I tried a build of the qpid-cpp latest master upstream today using:
> >
> > Windows Server 2012 R2
> > Visual Studio 2013 x64
> > boost 1_58_0
> > cmake version 3.9.4
> > Python 2.7.10
> > ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
> >
> > Note that I did not include qpid-proton in this build. Also I am not on
> > Windows 10 and have widely different tool versions.
> >
> > I ran into the following issues that 'break the build':
> >
> > * https://issues.apache.org/jira/browse/QPID-8155 - cmake flags issues.
> > ** Work around by reverting as described in the jira
> >
> > * https://issues.apache.org/jira/browse/QPID-7926 - PODmutex is not a POD
> > ** No workaround available
> >
> > So I can't build on windows Visual Studio 2013 either.
> > However, I do not hit the same problems you have.
> >
> > Here is a transcript of my CMake. Maybe it will give you a hint.
> >
> > -Chuck
> >
> >
> > Running CMake in D:\Users\chug\git\qpid-cpp\build_2013_x64 : CMake -G
> > "Visual Studio 12 2013 Win64" "-DBUILD_DOCS=No" "-DCMAKE_INSTALL_PREFIX=D:\
> > Users\chug\git\qpid-cpp\install_2013_x64" "-DBoost_
> > COMPILER=-vc120" "-DBOOST_ROOT=D:\boost\boost_1_58_0"
> > "-DINSTALL_QMFGEN=No" D:\Users\chug\git\qpid-cpp
> > -- The C compiler identification is MSVC 18.0.40629.0
> > -- The CXX compiler identification is MSVC 18.0.40629.0
> > -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
> > Studio 12.0/VC/bin/x86_amd64/cl.exe
> > -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
> > Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
> > Studio 12.0/VC/bin/x86_amd64/cl.exe
> > -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
> > Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
> > -- Detecting CXX compiler ABI info
> > -- Detecting CXX compiler ABI info - done
> > -- Detecting CXX compile features
> > -- Detecting CXX compile features - done
> > -- Build types are Debug;Release;MinSizeRel;RelWithDebInfo
> > -- Found PythonInterp: C:/Python27/python.exe (found suitable version
> > "2.7.10", minimum required is "2.7")
> > CMake Deprecation Warning at CMakeLists.txt:138 (cmake_policy):
> >   The OLD behavior for policy CMP0022 will be removed from a future version
> >   of CMake.
> >
> >   The cmake-policies(7) manual explains that the OLD behaviors of all
> >   policies are deprecated 

Re: Proton C source reorg and removal of deprecated or obsolete code

[Justin Ross]

Just a note to everyone that the Proton C source reorg has now landed on
master.  Please let me know if you have any trouble.

https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=tree;h=HEAD

On Wed, Mar 14, 2018 at 5:40 AM, Alan Conway  wrote:

> On Mon, Mar 12, 2018 at 12:14 PM, Justin Ross 
> wrote:
>
> > > src/messenger still there - oversight, or do we need to hold onto this?
> > >
> >
> > It's still used by one of the test tools.
> >
> >
> We can replace msgr-send.c and msgr-recv.c by copying from
> examples/c/[send.c, send-ssl.c, receive.c] and adding options (ssl config,
> container name, prefetch etc.) IMO a  day or two of work. The examples
> already have the required code, just need to parameterize it with command
> line options. Not required for the initial re-org, but something to do
> shortly after.
>

[ruby] bug in Container#schedule in proton-0.22

[Alan Conway]

Sadly the 0.22 ruby library has a new feature Container#schedule that does
not work properly (scheduled code sometimes doesn't run) - it's very likely
users will run into this if they use the feature.

I have fixed this properly for 0.23 and there's a small monkey patch to
work around it on 0.22, see the description of https://issues.apache.org/
jira/browse/PROTON-1820

Re: Build QPID C++ Using Visual Studio 2013 on Windows 10

[Michael Arnold]

Thanks Chuck,

Downgrading python from 3.6.1 (python 3) to 2.7.17 (python 2), allowed
cmake to generate the build files.  I did not encouter QPID-8155.

On the build side, 3 types of errors:
1. QPID-7926 as you describe.

2. Link errors of the form: error LNK1104: cannot open file
'Debug\qpidcommond.lib'
C:\Users\myk32\Documents\Development\qpid-bin\src\LINK
--> the *.lib files don't appear to exist.  Any pointers?

3. Link errors of the form: error C1083: Cannot open include file:
'proton/engine.h': No such file or directory
--> I assume this is because I have not run a 'make install' in the proton
build directory, but not sure how to do this on windows.  Any pointers?

On Thu, Apr 5, 2018 at 4:12 AM, Chuck Rolke  wrote:

> I tried a build of the qpid-cpp latest master upstream today using:
>
> Windows Server 2012 R2
> Visual Studio 2013 x64
> boost 1_58_0
> cmake version 3.9.4
> Python 2.7.10
> ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
>
> Note that I did not include qpid-proton in this build. Also I am not on
> Windows 10 and have widely different tool versions.
>
> I ran into the following issues that 'break the build':
>
> * https://issues.apache.org/jira/browse/QPID-8155 - cmake flags issues.
> ** Work around by reverting as described in the jira
>
> * https://issues.apache.org/jira/browse/QPID-7926 - PODmutex is not a POD
> ** No workaround available
>
> So I can't build on windows Visual Studio 2013 either.
> However, I do not hit the same problems you have.
>
> Here is a transcript of my CMake. Maybe it will give you a hint.
>
> -Chuck
>
>
> Running CMake in D:\Users\chug\git\qpid-cpp\build_2013_x64 : CMake -G
> "Visual Studio 12 2013 Win64" "-DBUILD_DOCS=No" "-DCMAKE_INSTALL_PREFIX=D:\
> Users\chug\git\qpid-cpp\install_2013_x64" "-DBoost_
> COMPILER=-vc120" "-DBOOST_ROOT=D:\boost\boost_1_58_0"
> "-DINSTALL_QMFGEN=No" D:\Users\chug\git\qpid-cpp
> -- The C compiler identification is MSVC 18.0.40629.0
> -- The CXX compiler identification is MSVC 18.0.40629.0
> -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
> Studio 12.0/VC/bin/x86_amd64/cl.exe
> -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
> Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
> Studio 12.0/VC/bin/x86_amd64/cl.exe
> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
> Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Build types are Debug;Release;MinSizeRel;RelWithDebInfo
> -- Found PythonInterp: C:/Python27/python.exe (found suitable version
> "2.7.10", minimum required is "2.7")
> CMake Deprecation Warning at CMakeLists.txt:138 (cmake_policy):
>   The OLD behavior for policy CMP0022 will be removed from a future version
>   of CMake.
>
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
>
>
> -- Found PythonInterp: C:/Python27/python.exe (found version "2.7.10")
> -- Skipping installing qmf-gen and qmf python site-packages
> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
> -- Could NOT find Ruby (missing: RUBY_LIBRARY) (found version "1.8.6")
> -- Found Doxygen: C:/Program Files (x86)/doxygen/bin/doxygen.exe (found
> version "1.6.3") found components:  doxygen missing components:  dot
> -- Could NOT find VALGRIND (missing: VALGRIND_EXECUTABLE)
> -- Could NOT find CyrusSASL (missing: CYRUS_SASL_LIBRARY
> CYRUS_SASL_INCLUDE_DIR)
> -- Regenerating AMQP protocol sources
> -- D:/Users/chug/git/qpid-cpp/src/qpid/broker/management-schema.xml is
> newer
> -- D:/Users/chug/git/qpid-cpp/src/qpid/acl/management-schema.xml is newer
> -- D:/Users/chug/git/qpid-cpp/src/qpid/ha/management-schema.xml is newer
> -- D:/Users/chug/git/qpid-cpp/src/qpid/legacystore/management-schema.xml
> is newer
> -- D:/Users/chug/git/qpid-cpp/src/qpid/linearstore/management-schema.xml
> is newer
> -- Regenerating Qpid Management Framework sources
> -- Looking for pthread.h
> -- Looking for pthread.h - not found
> -- Found Threads: TRUE
> -- Boost version: 1.58.0
> -- Found the following Boost libraries:
> --   program_options
> --   date_time
> --   thread
> --   system
> --   chrono
> --   atomic
> -- Looking for uuid_generate
> -- Looking for uuid_generate - not found
> -- Looking for uuid_generate in uuid
> -- Looking for uuid_generate in uuid - not found
> -- Looking for uuid_create
> -- Looking for uuid_create - not found
> -- Looking for UuidToString
> -- Looking for UuidToString - found
> -- Check for size_t
> 

[Java Broker] Temporary queues ACLs for multiple users

[Vavricka]

Hi, 

I am trying to get working temporary queues on Java Broker. Each user should
have access only to queue which he created.

ACL rights:

ACL ALLOW-LOG user1 ACCESS VIRTUALHOST
ACL ALLOW-LOG user1 CREATE QUEUE temporary="true" owner="user1"
ACL ALLOW-LOG user1 CONSUME QUEUE temporary="true" owner="user1"

ACL ALLOW-LOG user2 ACCESS VIRTUALHOST
ACL ALLOW-LOG user2 CREATE QUEUE temporary="true" owner="user2"
ACL ALLOW-LOG user2 CONSUME QUEUE temporary="true" owner="user2"

I successfully create temporary queue by JMS method "TemporaryQueue
temporaryQueue = session.createTemporaryQueue()", queue is correctly created
on broker, but owner is not set in webgui (however createdBy and
lastUpdatedBy in JSON is correctly set to corresponding user).

When I try to create consumer by "MessageConsumer consumer =
session.createConsumer(temporaryQueue)", I get "Permission CREATE is denied
for : Consumer ...". When owner is not set in CONSUME ACL I can create
consumer without error, but both users can consume same queue. Is there any
different way to distinguish temporary queues, so one user cannot read other
user messages? 

Another issue is I cannot sent messages directly to temporary queue. When I
try to send message I get error "Permission PERFORM_ACTION(publish) is
denied for : Queue 'TempQueueba2f889e-f95c-49d4-8c15-023e62666320'". We
could utilize sending messages directly to queue, because we cannot
dynamically create exchange binding by REST API. Or is there any way to set
bindings by JMS?

Java Broker 7.0.3
Qpid JMS client 0.31.0

Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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