Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: openengsb-3.0.0.M2
    • Component/s: framework
    • Labels:
      None

      Description

      The problem here is that activemqweb starts but it does not work if you point your browser to it. In 1.2.x it still works?!

      This might not be a blocker for M4, but definitely is one for the 1.3.0 final release

        Gliffy Diagrams

        Error rendering 'com.meetme.plugins.jira.gerrit-plugin:gerritreviewsmodule'. Please contact your JIRA administrators.

          Activity

          Hide
          Felix Mayerhuber added a comment -

          sorted it out. If aries jndi bundle is started, the activemq web console doesn't work. I try if the EDB can run without it.

          Show
          Felix Mayerhuber added a comment - sorted it out. If aries jndi bundle is started, the activemq web console doesn't work. I try if the EDB can run without it.
          Hide
          Andreas Pieber added a comment -

          is this a problem with some double exports? I'm afraid that we'll have other problems (e.g. jpa) which is relying on the jndi bundle... mhm...

          Show
          Andreas Pieber added a comment - is this a problem with some double exports? I'm afraid that we'll have other problems (e.g. jpa) which is relying on the jndi bundle... mhm...
          Hide
          Felix Mayerhuber added a comment -

          I don't know exactly whats the problem is. But we can't remove the bundle because jpa doesn't work without it

          Show
          Felix Mayerhuber added a comment - I don't know exactly whats the problem is. But we can't remove the bundle because jpa doesn't work without it
          Hide
          Andreas Pieber added a comment -

          I was afraid of this... can we produce a VERY minimal example? I would like to point the right ppl on this but for that I'll need a simple example. Would this be possible?

          Show
          Andreas Pieber added a comment - I was afraid of this... can we produce a VERY minimal example? I would like to point the right ppl on this but for that I'll need a simple example. Would this be possible?
          Hide
          Felix Mayerhuber added a comment -

          you mean a little example project?

          Show
          Felix Mayerhuber added a comment - you mean a little example project?
          Hide
          Andreas Pieber added a comment -

          yep; best something very simple without openengsb context; there don't need to be JPA in the context; it's enough if the amq libs and the JNDI lib

          Show
          Andreas Pieber added a comment - yep; best something very simple without openengsb context; there don't need to be JPA in the context; it's enough if the amq libs and the JNDI lib
          Hide
          Felix Mayerhuber added a comment -

          wouldn't it be sufficient to take the aries jpa example and add the amq libs there? or is that too big?

          Show
          Felix Mayerhuber added a comment - wouldn't it be sufficient to take the aries jpa example and add the amq libs there? or is that too big?
          Hide
          Andreas Pieber added a comment -

          would be perfect if it works

          Show
          Andreas Pieber added a comment - would be perfect if it works
          Hide
          Felix Mayerhuber added a comment -

          looks like this problem is already known

          https://issues.apache.org/jira/browse/ARIES-554

          but there is no information when this will be fixed in the aries jndi bundle

          Show
          Felix Mayerhuber added a comment - looks like this problem is already known https://issues.apache.org/jira/browse/ARIES-554 but there is no information when this will be fixed in the aries jndi bundle
          Hide
          Felix Mayerhuber added a comment -

          the problem is already fixed in the github repo. I will ask when the release of the next JNDI bundle version is planned

          Show
          Felix Mayerhuber added a comment - the problem is already fixed in the github repo. I will ask when the release of the next JNDI bundle version is planned
          Hide
          Andreas Pieber added a comment -

          good to know I think this is a candidate for the known issue page on the HP (once it is in place). Till those aries packages are in karaf we cant do anything. Thanks for finding the problem.

          Show
          Andreas Pieber added a comment - good to know I think this is a candidate for the known issue page on the HP (once it is in place). Till those aries packages are in karaf we cant do anything. Thanks for finding the problem.
          Hide
          Andreas Pieber added a comment -

          we're still waiting for the JNDI bundle release...

          Show
          Andreas Pieber added a comment - we're still waiting for the JNDI bundle release...
          Hide
          Felix Mayerhuber added a comment -

          there is now a new JNDI bundle version available (now under vote and not released to central). The tests has been started for that. Problem here is that Karaf itself has a JNDI bundle started, which has the previous version. We have to wait for the next Karaf release for that. Tests with Karaf and the new JNDI bundle are now in progress.

          Show
          Felix Mayerhuber added a comment - there is now a new JNDI bundle version available (now under vote and not released to central). The tests has been started for that. Problem here is that Karaf itself has a JNDI bundle started, which has the previous version. We have to wait for the next Karaf release for that. Tests with Karaf and the new JNDI bundle are now in progress.
          Hide
          Andreas Pieber added a comment -

          We cant do this without karaf 3

          Show
          Andreas Pieber added a comment - We cant do this without karaf 3
          Hide
          Andreas Pieber added a comment -

          Because of a required karaf upgrade or some major internal/api changes of the OEB we cannot fix those issues now and therefore delegate them to 2.4.3

          Show
          Andreas Pieber added a comment - Because of a required karaf upgrade or some major internal/api changes of the OEB we cannot fix those issues now and therefore delegate them to 2.4.3
          Hide
          Andreas Pieber added a comment -

          ah OK... I think this should work already again after the upgrade to karaf-RC1.

          Show
          Andreas Pieber added a comment - ah OK... I think this should work already again after the upgrade to karaf-RC1.
          Hide
          Kristof Meixner added a comment -

          Changed feature definition and version range there.

          Show
          Kristof Meixner added a comment - Changed feature definition and version range there.

            People

            • Assignee:
              Kristof Meixner
              Reporter:
              Andreas Pieber
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: