Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2674

artemis-service.exe start is not working with cygwin

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Minor
    • None
    • AMQ 7.4.0.CR2
    • broker-core
    • Compatibility/Configuration, User Experience
    • Hide
      1. Create 7.4.0 CR2 instance
      2. Install service
      3. Try to start broker via artemis-service.exe start
      4. Check instance>/log/artemis-service* - logs are not created - no idea what is the problem
      Show
      Create 7.4.0 CR2 instance Install service Try to start broker via artemis-service.exe start Check instance>/log/artemis-service* - logs are not created - no idea what is the problem

    Description

      It seems like this is a problem when using cygwin. On the other hand, it used to work with 7.3.0 and prior versions of brokers.

      After creation of instance of amq 7.4.0 cr2, bin/artemis-service.exe can't operate broker.
      There is no response from start action.
      Also, some log/artemis-service*logs should be created but nothing is created. Basically this is not working at all.

      On the plus side, artemis.cmd can successfully start broker without any problems. There seems to be some problem with artemis-service (+ xml?) file.

      Also, looking at https://issues.jboss.org/browse/ENTMQBR-522 (this was supposed to change artemis-service.xml file) -> this last PR was not present in 7.4.0 CR2. There are no start|stoparugment in artemis-service.xml on windows platform.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2567 Broker cannot start on Windows

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-522 Broker running on windows write problems with remove temp files when shutting down

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gaohoward Howard Gao
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: