Alfresco / alfresco-sdk

The Alfresco In-Process SDK is based on Apache Maven, includes support for rapid and standard development, testing, packaging, versioning and release of your Alfresco integration and extension projects
Apache License 2.0
185 stars 113 forks source link

Receiving Error on new SDK build #620

Closed ESWBitto closed 3 years ago

ESWBitto commented 3 years ago

I'm submitting a ... (check one with "x")

[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request

Expected Behavior

When I run ./run.sh build_start it should build the project and I should be able to go to http://my.ip:8080/share nothing happens.

Current Behavior

Receiving Error Message.

Possible Solution

Steps to Reproduce (for bugs)

1. 2. 3. 4. 5.

Context

Your Environment

Additional information

alfresco-dev-upgrade-acs_1 | 27-Apr-2021 20:40:15.435 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] alfresco-dev-upgrade-acs_1 | 27-Apr-2021 20:40:15.451 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [47960] milliseconds alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:15,552 INFO [management.subsystems.ChildApplicationContextFactory] [http-nio-8080-exec-1] Starting 'Search' subsystem, ID: [Search, managed, solr6] alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:15,862 INFO [management.subsystems.ChildApplicationContextFactory] [http-nio-8080-exec-1] Startup of 'Search' subsystem, ID: [Search, managed, solr6] complete alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:20,115 ERROR [component.jms.DefaultJmsMessageListenerContainer] [Camel (alfrescoCamelContext) thread #0 - JmsConsumer[acs-repo-transform-request]] Could not refresh JMS Connection for destination 'acs-repo-transform-request' - retrying using FixedBackOff{interval=5000, currentAttempts=2, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [vm] alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:20,136 ERROR [component.jms.DefaultJmsMessageListenerContainer] [Camel (alfrescoCamelContext) thread #1 - JmsConsumer[acs-repo-rendition-events]] Could not refresh JMS Connection for destination 'acs-repo-rendition-events' - retrying using FixedBackOff{interval=5000, currentAttempts=2, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [vm] alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:25,120 ERROR [component.jms.DefaultJmsMessageListenerContainer] [Camel (alfrescoCamelContext) thread #0 - JmsConsumer[acs-repo-transform-request]] Could not refresh JMS Connection for destination 'acs-repo-transform-request' - retrying using FixedBackOff{interval=5000, currentAttempts=3, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [vm] alfresco-dev-upgrade-acs_1 | 2021-04-27 20:40:25,145 ERROR [component.jms.DefaultJmsMessageListenerContainer] [Camel (alfrescoCamelContext) thread #1 - JmsConsumer[acs-repo-rendition-events]] Could not refresh JMS Connection for destination 'acs-repo-rendition-events' - retrying using FixedBackOff{interval=5000, currentAttempts=3, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Transport scheme NOT recognized: [vm]

Fikili commented 3 years ago

Well, I can access Repo and Share but I see the same error messages in log file even with Jeff's suggestion (messaging.subsystem.autoStart=false) mentioned in https://github.com/Alfresco/alfresco-sdk/issues/616. Anyone working on that?

Scouil commented 3 years ago

Independently of the error in the logs, the issue initially reported is probably because he tries to access share on port 8080 (http://my.ip:8080/share ) while it should now be accessed on port 8180

ecarbenay commented 3 years ago

I had the same issue and Jeff's suggestion in #616 did not solve it neither. The way I solved this was to comment the scope in the following activemq-all dependency in the pom.xml of the project, like this :

        <dependency>
            <groupId>org.apache.activemq</groupId>
            <artifactId>activemq-all</artifactId>
            <version>${activemq.version}</version>
            <!-- not only to be available for test scope - need to be available also for run -->
            <!-- <scope>test</scope> -->
        </dependency>
andrea-ligios commented 3 years ago

Thank you @ecarbenay , the scope is now compile by default on master and future releases