Commons Logging
  1. Commons Logging
  2. LOGGING-74

Commons logging jar files causes weblogic to throw errors

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.3
    • Fix Version/s: 1.0.4
    • Labels:
      None
    • Environment:

      Operating System: other
      Platform: Sun

      Description

      Hi I get StringIndexOutOfBounds Exception when I place commons-logging.jar and
      commons-logging-api.jar in the WEB-INF/lib folder of my weblogic 6.1
      application.

        Activity

        Hide
        Vinay Agarwal added a comment -

        This happens for commons logging 1.0.3

        Show
        Vinay Agarwal added a comment - This happens for commons logging 1.0.3
        Hide
        Craig McClanahan added a comment -

        It's pretty much impossible for anyone to help you with this, unless you can
        post a stack trace, details of how you're configuring commons-logging, and (best
        of all) a small webapp that illustrates the problem.

        Without those, this bug report is likely to get closed with no action.

        Show
        Craig McClanahan added a comment - It's pretty much impossible for anyone to help you with this, unless you can post a stack trace, details of how you're configuring commons-logging, and (best of all) a small webapp that illustrates the problem. Without those, this bug report is likely to get closed with no action.
        Hide
        Vinay Agarwal added a comment -

        Please refer Bug# 19108. Seems this bug is not yet fixed and reappears for
        commons logging 1.0.3

        Show
        Vinay Agarwal added a comment - Please refer Bug# 19108. Seems this bug is not yet fixed and reappears for commons logging 1.0.3
        Hide
        Mohan Kishore added a comment -

        Can you try using the jar from the nightly build. The message stack seem to
        indicate that the problem was due to presence of log4j.jar entry in commons-
        logging.jar's manifest file.

        That has been fixed on Apr 17, Rev1.4 (after the 1.0.3 release - Rev1.3)

        Show
        Mohan Kishore added a comment - Can you try using the jar from the nightly build. The message stack seem to indicate that the problem was due to presence of log4j.jar entry in commons- logging.jar's manifest file. That has been fixed on Apr 17, Rev1.4 (after the 1.0.3 release - Rev1.3)
        Hide
        Craig McClanahan added a comment -

        The classpath entry in the JAR file has been removed, so I am presuming that
        this is no longer an issue. Please re-open the report (with a stack trace) if
        that is not the case.

        Show
        Craig McClanahan added a comment - The classpath entry in the JAR file has been removed, so I am presuming that this is no longer an issue. Please re-open the report (with a stack trace) if that is not the case.

          People

          • Assignee:
            Unassigned
            Reporter:
            Vinay Agarwal
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development