Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.1, 3.1.1, 4.0
    • Fix Version/s: 3.1_b42, 3.1.1_b06
    • Component/s: OSGi
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      This is a request to provide a way to administratively turn off the OSGi shell.

      The server-config has the following arguments to the JVM which control the OSGi
      shell:

      <jvm-options>-Dosgi.shell.telnet.port=6666</jvm-options>
      <jvm-options>-Dosgi.shell.telnet.maxconn=1</jvm-options>
      <jvm-options>-Dosgi.shell.telnet.ip=127.0.0.1</jvm-options>

      The default-config for instances does not have these arguments, but the shell is
      still started using the default values.

      From Jerome:
      I believe the org.apache.felix.scr.jar would need to be moved out of the
      modules/autostart directory.
      I might be mistaken but if there is no administrative way to turn off
      fileinstall or shell, this is not good, we need to revisit this.

      1. patch.txt
        4 kB
        Sanjeeb Sahoo

        Issue Links

          Activity

          Hide
          scatari added a comment -

          Marking it as fixed as the fix was delivered for b06.

          Show
          scatari added a comment - Marking it as fixed as the fix was delivered for b06.
          Hide
          Sanjeeb Sahoo added a comment -

          This issue is kept open until it is fixed in trunk. We are looking for a better solution in trunk, hence the delay in closing the issue in trunk. Pl. don't mark it resolved for trunk. I ave marked it as 3_1_1-scrubbed, so hopefully it won't show up in 3.1.1 outstanding buglist.

          Show
          Sanjeeb Sahoo added a comment - This issue is kept open until it is fixed in trunk. We are looking for a better solution in trunk, hence the delay in closing the issue in trunk. Pl. don't mark it resolved for trunk. I ave marked it as 3_1_1-scrubbed, so hopefully it won't show up in 3.1.1 outstanding buglist.
          Hide
          Sanjeeb Sahoo added a comment -

          This bug has been fixed in 3.1.1 as well. We are marking this bug resolved and opening a new one per 3.1.1 release manager's request. Pl. contact 3.1.1 release manager for further details about the process.

          Show
          Sanjeeb Sahoo added a comment - This bug has been fixed in 3.1.1 as well. We are marking this bug resolved and opening a new one per 3.1.1 release manager's request. Pl. contact 3.1.1 release manager for further details about the process.
          Hide
          Sanjeeb Sahoo added a comment -

          Linking with the 3.2 specific issue.

          Show
          Sanjeeb Sahoo added a comment - Linking with the 3.2 specific issue.
          Hide
          Sanjeeb Sahoo added a comment -

          I have now disabled the shell on trunk as well, since I have not found time to secure it. Will downgrade the priority of GLASSFISH-16998 now.
          Sending conf/config.properties
          Transmitting file data .
          Committed revision 48678.

          Show
          Sanjeeb Sahoo added a comment - I have now disabled the shell on trunk as well, since I have not found time to secure it. Will downgrade the priority of GLASSFISH-16998 now. Sending conf/config.properties Transmitting file data . Committed revision 48678.

            People

            • Assignee:
              Sanjeeb Sahoo
              Reporter:
              Tom Mueller
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: