ActiveMQ and Fedora competing for port 61616

455 views
Skip to first unread message

Josh

unread,
Feb 17, 2021, 1:29:08 PM2/17/21
to islandora
Hi folks. We've been working through a manual install of Islandora 8 (https://islandora.github.io/documentation/installation/manual/introduction/) and have most of the parts working, but I'm running into a problem where when we start Tomcat, Fedora (fcrepo) is seemingly trying to start ActiveMQ even though we did the manual install of ActiveMQ as specified in the install instructions. 

If ActiveMQ is already running, Fedora will give the following error and fail to start:

ERROR 13:15:04.925 (BrokerService) Failed to start Apache ActiveMQ
java.io.IOException: Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket: tcp://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600 due to: java.net.BindException: Address already in use (Bind failed)

If I stop ActiveMQ first then Fedora will start, but we can't start ActiveMQ because the port is already in use.

Is it normal for Fedora to launch ActiveMQ? If so, do we just uninstall the standalone version of ActiveMQ and let fedora handle it? I can't figure out where in the Fedora config it is creating this connection, but maybe if I could stop this it would let me start Fedora and ActiveMQ at the same time?

Some additional info:
- We are using Debian
- ActiveMQ is 5.16.1
- Fedora is 5.1.1
- When I try running things using the Fedora version of ActiveMQ I don't get errors, but nothing seems to be entered into the Fedora database.

Thanks

Josh

Jared Whiklo

unread,
Feb 18, 2021, 10:34:37 AM2/18/21
to isla...@googlegroups.com
Hey Josh,

What you probably want to do is to bridge Fedora's internal ActiveMQ
instance to your external one.

To do that you need to create a custom ActiveMQ configuration and give
Fedora a different JMS port.

You can specify the port using the JVM property fcrepo.dynamic.jms.port
and set it to something other that 61616, ie.
-Dfcrepo.dynamic.jms.port=61617

Then create an ActiveMQ configuration to bridge Fedora to your other
broker. Something like

---

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:amq="http://activemq.apache.org/schema/core"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
    http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
    http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd">

  <amq:broker id="broker" useShutdownHook="false">

    <amq:managementContext>
      <amq:managementContext connectorPort="1093" createConnector="false"/>
    </amq:managementContext>

    <!-- Your remote broker, configured with failover -->
    <amq:networkConnectors>
      <amq:networkConnector name="fedorabridge" dynamicOnly="true"
uri="static:(failover:(tcp://localhost:61616))"/>
    </amq:networkConnectors>

    <!-- The directory where Fedora will store the ActiveMQ data -->
    <amq:persistenceAdapter>
            <amq:kahaDB directory="/<some place that is not where the
other ActiveMQ writes>/kahadb/data"/>
    </amq:persistenceAdapter>
  </amq:broker>

  <!-- Set this to prevent objects from being serialized when
       passed along to your embedded broker;  saves some overhead
processing -->
  <bean id="jmsConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
     <property name="objectMessageSerializationDefered" value="false"/>
  </bean>
</beans>

---

Then you also add the JVM property fcrepo.activemq.configuration
pointing to this file, you'll need to use the file:// schema. So
something like

-Dfcrepo.activemq.configuration=file:///path/to/your/fedora/activemq.xml

Then when Fedora starts it should start on a separate port and instead
forward its messages to your broker. If you don't care about the Fedora
messages, you can skip the custom ActiveMQ configuration and just change
the ports. As long as your Fedora is configured to use a JMS topic then
the messages will just get sent to the ether.

cheers,
jared
> --
> For more information about using this group, please read our Listserv
> Guidelines: http://islandora.ca/content/welcome-islandora-listserv
> <http://islandora.ca/content/welcome-islandora-listserv>
> ---
> You received this message because you are subscribed to the Google
> Groups "islandora" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to islandora+...@googlegroups.com
> <mailto:islandora+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/islandora/5f639cc0-45da-42ed-8403-08b803d98440n%40googlegroups.com
> <https://groups.google.com/d/msgid/islandora/5f639cc0-45da-42ed-8403-08b803d98440n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Jared Whiklo
jwh...@gmail.com


OpenPGP_signature

Josh

unread,
Feb 22, 2021, 12:09:28 PM2/22/21
to islandora
Hi Jared,

Thanks so much for your help. I'm now able to get ActiveMQ and Fedora running at the same time (I also had to change fcrepo.dynamic.stomp.port to something else as well since it was using 61613 which ActiveMQ also wanted).

My content does not seem to be finding its way into Fedora still. It's saving in Drupal and Solr, but my Fedora repo is empty. Do you think this is related the my ActiveMQ issues? I am seeing the following in the ActiveMQ logs when I save a repository item in Drupal:

2021-02-22 12:42:43,705 | DEBUG | Stomp Connect heartbeat conf RW[0,0] | org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,705 | DEBUG | Setting up new connection id: ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29, address: tcp://0:0:0:0:0:0:0:1:47894, info: ConnectionInfo {commandId = 0, responseRequired = true, connectionId = ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29, clientId = ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29, clientIp = null, userName = null, password = *****, brokerPath = null, brokerMasterConnector = false, manageable = false, clientMaster = true, faultTolerant = false, failoverReconnect = false} | org.apache.activemq.broker.TransportConnection | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,706 | DEBUG | Publishing: stomp://server-address:61613 for broker transport URI: stomp://server-address:61613?maximumConnections=1000 | org.apache.activemq.broker.TransportConnector | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,706 | DEBUG | Publishing: stomp://server-address:61613 for broker transport URI: stomp://server-address:61613?maximumConnections=1000 | org.apache.activemq.broker.TransportConnector | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,755 | DEBUG | commit: TX:ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29:1 syncCount: 1 | org.apache.activemq.transaction.LocalTransaction | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,759 | DEBUG | localhost Message ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29:-1:1:1 sent to queue://islandora-indexing-fcrepo-content | org.apache.activemq.broker.region.Queue | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,760 | DEBUG | queue://islandora-indexing-fcrepo-content, subscriptions=0, memory=0%, size=11, pending=0 toPageIn: 1, force:false, Inflight: 0, pagedInMessages.size 10, pagedInPendingDispatch.size 10, enqueueCount: 11, dequeueCount: 0, memUsage:27712, maxPageSize:200 | org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost] Task-1620
2021-02-22 12:42:43,811 | DEBUG | commit: TX:ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29:2 syncCount: 1 | org.apache.activemq.transaction.LocalTransaction | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,815 | DEBUG | localhost Message ID:server-address-XXXXX-XXXXXXXXXXXXXXX-X:29:-1:1:2 sent to queue://islandora-indexing-triplestore-index | org.apache.activemq.broker.region.Queue | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
2021-02-22 12:42:43,816 | DEBUG | queue://islandora-indexing-triplestore-index, subscriptions=0, memory=0%, size=15, pending=0 toPageIn: 1, force:false, Inflight: 0, pagedInMessages.size 14, pagedInPendingDispatch.size 14, enqueueCount: 15, dequeueCount: 0, memUsage:39066, maxPageSize:200 | org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost] Task-1620
2021-02-22 12:42:44,437 | DEBUG | Transport Connection to: tcp://0:0:0:0:0:0:0:1:47894 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///0:0:0:0:0:0:0:1:47894@61613
java.io.EOFException
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:272)
at org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:194)
at org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:187)
at org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:220)
at org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:132)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
at java.base/java.lang.Thread.run(Thread.java:834)

Thanks again

Josh

Jared Whiklo

unread,
Feb 22, 2021, 12:55:32 PM2/22/21
to isla...@googlegroups.com
Hi Josh,

Probably not, but it is possible. When you create a node in Drupal it is
published to the ActiveMQ broker configured inside the Islandora
configuration (in Drupal). Then the Alpaca islandora-indexing-fcrepo
route should do the work of using that message to grab the content from
Drupal and storing it in Fedora.

So if you broker is working now then I would check the
/var/log/islandora/milliner.log first and see what types of messages you
are getting there.

cheers,
jared
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/context/spring-context-3.0.xsd
> http://activemq.apache.org/schema/core/activemq-core.xsd
> <https://islandora.github.io/documentation/installation/manual/introduction/>)
>
> > and have most of the parts working, but I'm running into a problem
> > where when we start Tomcat, Fedora (fcrepo) is seemingly trying to
> > start ActiveMQ even though we did the manual install of ActiveMQ as
> > specified in the install instructions.
> >
> > If ActiveMQ is already running, Fedora will give the following
> error
> > and fail to start:
> >
> > ERROR 13:15:04.925 (BrokerService) Failed to start Apache ActiveMQ
> > java.io.IOException: Transport Connector could not be registered in
> > JMX: java.io.IOException: Failed to bind to server socket:
> >
> tcp://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600
> <http://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600>
> <https://groups.google.com/d/msgid/islandora/5f639cc0-45da-42ed-8403-08b803d98440n%40googlegroups.com?utm_medium=email&utm_source=footer
> --
> For more information about using this group, please read our Listserv
> Guidelines: http://islandora.ca/content/welcome-islandora-listserv
> <http://islandora.ca/content/welcome-islandora-listserv>
> ---
> You received this message because you are subscribed to the Google
> Groups "islandora" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to islandora+...@googlegroups.com
> <mailto:islandora+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/islandora/4843c554-153b-4c5b-947f-1342dbd2c2e8n%40googlegroups.com
> <https://groups.google.com/d/msgid/islandora/4843c554-153b-4c5b-947f-1342dbd2c2e8n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Jared Whiklo
jwh...@gmail.com


OpenPGP_signature

Josh

unread,
Mar 3, 2021, 2:23:23 PM3/3/21
to islandora
Hi again,

I've been poking around and it looks like Milliner is not getting used by Islandora at all. I've set all my Crayfish components' log levels to DEBUG, and the only log that was created was for Gemini. If I manually curl http://localhost/milliner it creates a log entry, but there was nothing there from Islandora.

It also doesn't seem to be creating any derivatives for my images (possibly unrelated) and there is nothing in the Gemini database besides an empty table called Gemini and a table called gemini_migrations with a version number in there.

It seems like none of these Crayfish components are working which makes me think the issue is with Drupal or ActiveMQ not being able to send the data to Crayfish. Do you have any other ideas of where I should look?

Thanks again

Josh

Jonathan Hunt

unread,
Mar 3, 2021, 3:09:23 PM3/3/21
to isla...@googlegroups.com
Hi Josh

Some ideas:

a. check the ActiveMQ Admin UI to see if the count of dequeued messages to houdini matches the enqueued; if messages aren't being dequeued then their is a failure at the microservice layer.

b. check Drupal watchdog especially for JWT errors

c. check the houdini log

d. check the apache error log since HTTP 500s etc. for a failed Crayfish microservice will end up there. Also access denied messages if the microservice is unable to fetch the original file.

e. Start tracking the karaf.log when issuing microservice requests (e.g. requesting a derivative).

/J
> To unsubscribe from this group and stop receiving emails from it, send an email to islandora+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/64af6349-0e24-4167-b411-8534ae458003n%40googlegroups.com.

p: +64 3 963 3733 x7802
Catalyst IT - Expert Open Source Solutions
https://catalyst.net.nz/

signature.asc

Josh

unread,
Mar 8, 2021, 3:16:37 PM3/8/21
to islandora
Thanks for the reply. I checked out your suggestions and found the following:

a. In the ActiveMQ console I can see messages being enqueued but not dequeued. The queues say 0 under number of consumers, so maybe that's why they are not being dequeued. I went back and checked Karaf and I'm having some failures with the Islandora and fcrepo features. We had some issues installing Karaf (https://groups.google.com/g/islandora/c/yXaGAIG6RuU/m/oTnoCEHwAQAJ) and I think maybe these features had not properly installed the first time around.

I have tried removing and reinstalling the features listed at https://islandora.github.io/documentation/installation/manual/installing_karaf_and_alpaca/#installing-the-required-karaf-features and I can't seem to get it to work. The first one to fail is fcrepo-service-activemq and I'm getting the following errors:

2021-03-08T15:59:54,359 | WARN  | features-3-thread-1 | XBeanNamespaceHandler            | 348 - org.apache.xbean.blueprint - 4.17.0 | Could not load class: org.apache.activemq.camel.component.CamelEndpointLoader due to org/apache/camel/component/jms/JmsComponent
2021-03-08T15:59:54,691 | WARN  | features-3-thread-1 | BeanRecipe                       | 52 - org.apache.aries.blueprint.core - 1.10.2 | Object to be destroyed is not an instance of UnwrapperedBeanHolder, type: null
2021-03-08T15:59:54,828 | WARN  | fileinstall-/opt/karaf/deploy | fileinstall                      | 10 - org.apache.felix.fileinstall - 3.6.8 | Error while starting bundle: blueprint:file:/opt/karaf/deploy/ca.islandora.alpaca.connector.ocr.blueprint.xml
2021-03-08T15:59:54,829 | WARN  | fileinstall-/opt/karaf/deploy | fileinstall                      | 10 - org.apache.felix.fileinstall - 3.6.8 | Error while starting bundle: blueprint:file:/opt/karaf/deploy/ca.islandora.alpaca.connector.houdini.blueprint.xml
2021-03-08T15:59:54,831 | WARN  | fileinstall-/opt/karaf/deploy | fileinstall                      | 10 - org.apache.felix.fileinstall - 3.6.8 | Error while starting bundle: blueprint:file:/opt/karaf/deploy/ca.islandora.alpaca.connector.fits.blueprint.xml
2021-03-08T15:59:54,832 | WARN  | fileinstall-/opt/karaf/deploy | fileinstall                      | 10 - org.apache.felix.fileinstall - 3.6.8 | Error while starting bundle: blueprint:file:/opt/karaf/deploy/ca.islandora.alpaca.connector.homarus.blueprint.xml

After this happens I see the feature but it says Failure instead of Active:
karaf@root()> la | grep fcrepo
443 │ Active    │  50 │ 5.0.0                               │ fcrepo-camel
444 │ Active    │  50 │ 0.4.0                               │ fcrepo-java-client
456 │ Active    │  80 │ 5.0.0                               │ fcrepo-service-camel
478 │ Failure   │  80 │ 5.0.0                               │ fcrepo-service-activemq


b. Nothing in the drupal logs other than repository item and media added messages

c. There is no houdini log, even though I have set it to DEBUG

d. Nothing in the apache error logs that looks related

e. I am not getting anything in the karaf logs when I add a new repository item or add media to it.

Thanks again

Josh

Josh

unread,
Mar 9, 2021, 3:23:37 PM3/9/21
to islandora
I think I've narrowed it down a bit. I tried removing Karaf from the Vagrant version of Islandora 8 and redoing the installation steps. It did the same things with warnings and timing out the client, but there were no "failures" up until "feature:install islandora-indexing-triplestore". After I ran that one it timed out and when I went back into the client there were 4 failures that were not there before:

karaf@root()> la | grep Failure
 43 x Failure     x  30 x 4.3.0                               x Apache Karaf :: Shell :: Core, Fragments: 171
263 x Failure     x  80 x 5.0.0                               x fcrepo-service-activemq
287 x Failure     x  80 x 5.0.0                               x fcrepo-service-camel
288 x Failure     x  80 x 1.0.4                               x islandora-http-client

I have attached the karaf log starting with the feature:install islandora-indexing-triplestore command

Thanks

Josh
karaf-log.txt

Jared Whiklo

unread,
Mar 10, 2021, 8:44:18 AM3/10/21
to isla...@googlegroups.com
Hey Josh,

This is a bit of a guess, but could you try downgrading your Karaf version to something in the 4.2.* range?

OSGI and Karaf features in particular are a bit like a magic 8 ball. When they work it's magic, when they don't it's just blue dyed water and plastic bits.

Depending on whether you want the Fedora triplestore indexer running. You could just skip that one entirely. 

The failure of the Karaf core feature is a little concerning though and is why I'm suggesting a down-grade.

Cheers,
Jared


Josh

unread,
Mar 10, 2021, 1:17:33 PM3/10/21
to islandora
I used Karaf 4.2.10 and it seemed to work. There were still some errors in the log when I added islandora-indexing-triplestore, but it didn't deactivate anything and now it's all showing as Active. The documentation says "It’s recommended to get the most recent version of Karaf 4.x" so maybe we should change it to "It’s recommended to get the most recent version of Karaf 4.2.x"? I will create a pull request for this shortly.

It still doesn't seem to be registering the consumers on my ActiveMQ queues though. When I look at the admin interface I see no consumers, and I added a repository item to test it which made some pending messages that are enqueued but not dequeued. Is there something else I need to do here or should Karaf have handled this for me?

Thanks

Josh

Jared Whiklo

unread,
Mar 10, 2021, 4:27:55 PM3/10/21
to isla...@googlegroups.com
Ok,

Based on what has worked so far, let me ask what version of ActiveMQ you
are running?

Also can you check that the fcrepo-service-activemq feature is installed
and running?

cheers,
jared
> <https://groups.google.com/g/islandora/c/yXaGAIG6RuU/m/oTnoCEHwAQAJ>)
> <http://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600
> <https://groups.google.com/d/msgid/islandora/4843c554-153b-4c5b-947f-1342dbd2c2e8n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/islandora/4843c554-153b-4c5b-947f-1342dbd2c2e8n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > --
> > Jared Whiklo
> > jwh...@gmail.com
> >
> >
> >
> > --
> > For more information about using this group, please
> read our Listserv Guidelines:
> http://islandora.ca/content/welcome-islandora-listserv
> <http://islandora.ca/content/welcome-islandora-listserv>
> > ---
> > You received this message because you are subscribed
> to the Google Groups "islandora" group.
> > To unsubscribe from this group and stop receiving
> emails from it, send an email to
> islandora+...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/islandora/64af6349-0e24-4167-b411-8534ae458003n%40googlegroups.com
> <https://groups.google.com/d/msgid/islandora/64af6349-0e24-4167-b411-8534ae458003n%40googlegroups.com>.
>
>
> p: +64 3 963 3733 x7802 <tel:+64%203-963%203733>
> Catalyst IT - Expert Open Source Solutions
> https://catalyst.net.nz/ <https://catalyst.net.nz/>
>
> --
> For more information about using this group, please read our
> Listserv Guidelines:
> http://islandora.ca/content/welcome-islandora-listserv
> <http://islandora.ca/content/welcome-islandora-listserv>
> ---
> You received this message because you are subscribed to the
> Google Groups "islandora" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to islandora+...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/islandora/67a6f179-1aab-48de-b51b-94af7fc57d34n%40googlegroups.com
> <https://groups.google.com/d/msgid/islandora/67a6f179-1aab-48de-b51b-94af7fc57d34n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> For more information about using this group, please read our Listserv
> Guidelines: http://islandora.ca/content/welcome-islandora-listserv
> <http://islandora.ca/content/welcome-islandora-listserv>
> ---
> You received this message because you are subscribed to the Google
> Groups "islandora" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to islandora+...@googlegroups.com
> <mailto:islandora+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/islandora/8cd44cc6-d917-4325-ae41-63000376f5a0n%40googlegroups.com
> <https://groups.google.com/d/msgid/islandora/8cd44cc6-d917-4325-ae41-63000376f5a0n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Jared Whiklo
jwh...@gmail.com


OpenPGP_signature

Josh

unread,
Mar 11, 2021, 7:37:23 AM3/11/21
to islandora
Hi Jared,

I have been testing this on the islandora-playbook vagrant box which is running ActiveMQ 5.14.5 and it was working correctly before I removed and reinstalled Karaf. I removed Karaf and reinstalled Karaf 4.3 from scratch, which didn't work, then I removed it again and tried 4.2.10 which seems to be working but didn't register any consumers to my ActiveMQ queues.

That feature is installed. Here is the output of la | grep fcrepo:
karaf@root()> la | grep fcrepo
203 x Active   x  80 x 5.0.0                               x fcrepo-service-activemq
221 x Active   x  50 x 5.0.0                               x fcrepo-camel
222 x Active   x  50 x 0.4.0                               x fcrepo-java-client
226 x Active   x  80 x 5.0.0                               x fcrepo-indexing-triplestore
227 x Active   x  80 x 5.0.0                               x fcrepo-indexing-triplestore-blueprint
228 x Active   x  80 x 5.0.0                               x fcrepo-service-camel
244 x Active   x  80 x 1.0.4                               x islandora-indexing-fcrepo

Thanks

Josh

Josh

unread,
Mar 11, 2021, 1:15:27 PM3/11/21
to islandora
I just compared the xml files in the deploy directory on a fresh playbook install with the ones in the manual install instructions and the playbook has port numbers for the Crayfish URLs. I thought this might be the issue so I tried adding the port numbers in the vagrant box I'm playing around in but it didn't seem to help.

The lines in the playbook XML looked like : <cm:property name="derivative.service.url" value="http://127.0.0.1:8000/houdini/convert"/>
And the manual install looked like: <cm:property name="derivative.service.url" value="http://localhost/houdini/convert"/>


Now that I'm getting fewer errors I'm hoping we're getting closer to the problem. I'm getting a few now that look like the below error, which looks like it might be causing my issue: 
2021-03-11T17:17:19,652 | ERROR | Blueprint Extender: 2 | BlueprintContainerImpl           | 51 - org.apache.aries.blueprint.core - 1.10.3 | Unable to start container for blueprint bundle ca.islandora.alpaca.islandora-indexing-fcrepo/1.0.4 due to unresolved dependencies [(&(osgi.jndi.service.name=fcrepo/Broker)(objectClass=org.apache.camel.Component))]

I am attaching the full feature list from the vagrant box that is working (where I didn't modify anything) and the one that's not working (where I deleted and replaced Karaf with 4.2.10 following the manual install instructions). It looks like there is the same set of features with fcrepo, camel, and islandora in the titles. Maybe someone can see something I'm missing?

Thanks

Josh
working.txt
not-working.txt

Josh

unread,
Mar 15, 2021, 3:19:48 PM3/15/21
to islandora
I've got it working now. I had to use the repo versions listed in the manual install instructions as most recent "at the time of writing". 

The manual instructions say:
  • ACTIVEMQ_KARAF_VERSION: The latest version of ActiveMQ Karaf 5.x.x; you can find this listed at the activemq-karaf repository page (e.g., 5.15.11 at the time of writing)
  • APACHE_CAMEL_VERSION: The latest version of Apache Camel 2.x.x; you can find this listed at the apache-camel repository page (e.g., 2.25.0 at the time of writing)
  • JENA_OSGI_VERSION: The latest version of the Apache Jena OSGi features; you can find this listed at the jena-osgi-features repository page (e.g., 3.14.0 at the time of writing)
But the latest versions didn't work. Once I used the exact versions specified in the parentheses my ActiveMQ queues had consumers listed and things started working. 

Reply all
Reply to author
Forward
0 new messages