Remko:

JMS is not built-in the JRE, do you have JMS in your configuration for
this test? If you do, then you'd need the JMS API and a provider as
dependencies.

Gary

On Tue, Dec 21, 2021 at 7:37 AM Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> Hmmm. This is not what I was expecting. If it didn’t work I would have 
> expected bad class version exceptions.
>
> Ralph
>
> > On Dec 21, 2021, at 4:28 AM, Remko Popma <remko.po...@gmail.com> wrote:
> >
> > -1 it does not work...
> >
> > Problem running a simple pipecleaning test on Java 6 with 2.3.1...
> > My pipecleaning program is something simple like this
> >
> > public class Pipecleaning {
> >    public static void main(String[] args) {
> >        org.apache.logging.log4j.LogManager.getLogger().info("HELLO
> > USER ${sys:user.name}");
> >
> > I only have 2 jars in the classpath, log4j-api-2.3.1 and 
> > log4j-core-2.3.1.The
> > problem is that Log4j configuration fails...
> >
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > javax/jms/JMSException
> >    at java.lang.Class.getDeclaredMethods0(Native Method)
> >    at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
> >    at java.lang.Class.getDeclaredMethods(Class.java:1793)
> >    at 
> > org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.createBuilder(PluginBuilder.java:154)
> >    at 
> > org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:120)
> >    at 
> > org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:781)
> >
> >
> >> On Tue, Dec 21, 2021 at 2:18 PM Ralph Goers <ralph.go...@dslextreme.com>
> >> wrote:
> >>
> >> This is a vote to release Log4j 2.3.1, a security release for Java 6 users.
> >>
> >> Please download, test, and cast your votes on the log4j developers list.
> >> [] +1, release the artifacts
> >> [] -1, don't release because...
> >>
> >> The vote will remain open for as short amount as time as required to vet
> >> the release. All votes are welcome and we encourage everyone to test the
> >> release, but only Logging PMC votes are “officially” counted. As always, at
> >> least 3 +1 votes and more positive than negative votes are required.
> >>
> >> Changes in this version include:
> >>
> >>
> >> New features:
> >> *  LOG4J2-3198:  Pattern layout no longer enables lookups within message
> >> text.
> >>
> >> Fixed Bugs:
> >> *  LOG4J2-3242:  Limit JNDI to the java protocol only. JNDI will remain
> >> disabled by default. Rename JNDI enablement property from
> >>        'log4j2.enableJndi' to 'log4j2.enableJndiLookup',
> >> 'log4j2.enableJndiJms', and 'log4j2.enableJndiContextSelector’.
> >> *  LOG4J2-3230:  Fix string substitution recursion.
> >>
> >> Tag:
> >> a)  for a new copy do "git clone
> >> https://github.com/apache/logging-log4j2.git"; and then "git checkout
> >> tags/log4j-2.3.1-rc1”  or just "git clone -b log4j-2.3.1-rc1
> >> https://github.com/apache/logging-log4j2.git";
> >> b) for an existing working copy to “git pull” and then “git checkout
> >> tags/log4j-2.12.3-rc1”
> >>
> >> Web Site:  https://logging.staged.apache.org/log4j/log4j-2.3.1/index.html
> >>
> >> Maven Artifacts:
> >> https://repository.apache.org/content/repositories/orgapachelogging-1076
> >>
> >> Distribution archives:
> >> https://dist.apache.org/repos/dist/dev/logging/log4j/
> >>
> >> You may download all the Maven artifacts by executing:
> >> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >> https://repository.apache.org/content/repositories/orgapachelogging-1076/org/apache/logging/log4j/
> >> .
>
>

Reply via email to