October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-101) GSSAPI failures on Windows

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-101?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-101: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/73 > GSSAPI failures on Windows > -------------------------- > > Key: ELY-101 > URL: https://issues.jboss.org/browse/ELY-101 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Environment: Windows > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The following GSSAPI tests fail on Windows for reasons unknown (probably not character encoding though): > * BasicAuthTest.testAuth > * BasicConfidenceTest.testAuthConf > * BasicIntegrityTest.testAuthInt > * NoServerAuthTest.testAuth > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-101) GSSAPI failures on Windows

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-101?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-101: -------------------------------- Prepared pull request which solve this: https://github.com/wildfly-security/wildfly-elytron/pull/73 > GSSAPI failures on Windows > -------------------------- > > Key: ELY-101 > URL: https://issues.jboss.org/browse/ELY-101 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Environment: Windows > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The following GSSAPI tests fail on Windows for reasons unknown (probably not character encoding though): > * BasicAuthTest.testAuth > * BasicConfidenceTest.testAuthConf > * BasicIntegrityTest.testAuthInt > * NoServerAuthTest.testAuth > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3903) IORSecConfigMetaDataService is not used by the CSIv2IORInterceptor

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3903?page=com.atlassian.jira.plugin.... ] Stefan Guilhen reassigned WFLY-3903: ------------------------------------ Assignee: Stefan Guilhen (was: Tomasz Adamski) > IORSecConfigMetaDataService is not used by the CSIv2IORInterceptor > ------------------------------------------------------------------- > > Key: WFLY-3903 > URL: https://issues.jboss.org/browse/WFLY-3903 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Stefan Guilhen > > IORSecConfigMetaDataService is not used by the CSIv2IORInterceptor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-101) GSSAPI failures on Windows

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-101?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-101: -------------------------------- There is problem with mocking of Random. Initial seed of new Random objects probably depends on platform. I have now working prototype, pull request will be prepared soon. > GSSAPI failures on Windows > -------------------------- > > Key: ELY-101 > URL: https://issues.jboss.org/browse/ELY-101 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Environment: Windows > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The following GSSAPI tests fail on Windows for reasons unknown (probably not character encoding though): > * BasicAuthTest.testAuth > * BasicConfidenceTest.testAuthConf > * BasicIntegrityTest.testAuthInt > * NoServerAuthTest.testAuth > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBAS-7427) AS won't boot with sun jmx enabled

by Oz Slater (JIRA)

[ https://issues.jboss.org/browse/JBAS-7427?page=com.atlassian.jira.plugin.... ] Oz Slater commented on JBAS-7427: --------------------------------- Same issue as Paul Sideleau on JBoss 6.1.0.Final, {jboss.boot.server.log.dir} is not resolving and JBoss literally creating a "${jboss.boot.server.log.dir}" directory to save boot.log. No problem with {jboss.server.log.dir} though. > AS won't boot with sun jmx enabled > ---------------------------------- > > Key: JBAS-7427 > URL: https://issues.jboss.org/browse/JBAS-7427 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Logging > Environment: sun jdk6, fedora, AS trunk r96005 > Reporter: Jonathan Halliday > Assignee: David Lloyd > Fix For: 6.0.0.M2 > > > [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" > [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT > JAVA: /usr/local/jdk1.6.0_16/bin/java > JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.net.preferIPv4Stack=true > CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar > ========================================================================= > Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@214a55f2, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > ... > Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@5c1ae90c, cause: java.lang.AbstractMethodError -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4023) javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4023?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-4023: ---------------------------------- [~pgarner] Do you have a reproducer app that you can share? > javax.el.ImportHandler#importClass & #importPackage doesn't import WEB-INF/classes > ---------------------------------------------------------------------------------- > > Key: WFLY-4023 > URL: https://issues.jboss.org/browse/WFLY-4023 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.1.0.Final > Environment: Win7, Wildfly 8.1.0.Final > Reporter: Patrick Garner > Assignee: Farah Juma > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > ImportHandler is not importing classes in WEB-INF/classes and, thus, developers are unable to import classes into the EL evaluation environment per EL 3.0 spec. section 1.22.2 "Imports of Packages, Classes, and Static Fields" > Here's the ImportHandler relevant code (https://github.com/jboss/jboss-el-api_spec/blob/master/src/main/java/java...) > {code:java} > private Class<?> getClassFor(String className) { > if (!notAClass.contains(className)) { > try { > return Class.forName(className, false, getClass().getClassLoader()); > } catch (ClassNotFoundException ex) { > notAClass.add(className); > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-306) Add support for TLS 1.1 and 1.2 to Apr

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-306?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWEB-306: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1158184 > Add support for TLS 1.1 and 1.2 to Apr > -------------------------------------- > > Key: JBWEB-306 > URL: https://issues.jboss.org/browse/JBWEB-306 > Project: JBoss Web > Issue Type: Enhancement > Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA > Environment: JBoss Enterprise Application Platform (EAP) 6.3 > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > Just as with Tomcat 7 (https://issues.apache.org/bugzilla/show_bug.cgi?id=53952), JBossWeb does not support TLS 1.1 and 1.2 for APR connectors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-306) Add support for TLS 1.1 and 1.2 to Apr

by Aaron Ogburn (JIRA)

Aaron Ogburn created JBWEB-306: ---------------------------------- Summary: Add support for TLS 1.1 and 1.2 to Apr Key: JBWEB-306 URL: https://issues.jboss.org/browse/JBWEB-306 Project: JBoss Web Issue Type: Enhancement Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA Environment: JBoss Enterprise Application Platform (EAP) 6.3 Reporter: Aaron Ogburn Assignee: Remy Maucherat Just as with Tomcat 7 (https://issues.apache.org/bugzilla/show_bug.cgi?id=53952), JBossWeb does not support TLS 1.1 and 1.2 for APR connectors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-604) Problems in code generation and parsing when a method is called from Guided Rules Editor

by Abel Marrero Santos (JIRA)

[ https://issues.jboss.org/browse/DROOLS-604?page=com.atlassian.jira.plugin... ] Abel Marrero Santos updated DROOLS-604: --------------------------------------- Affects Version/s: 6.2.0.Beta3 > Problems in code generation and parsing when a method is called from Guided Rules Editor > ---------------------------------------------------------------------------------------- > > Key: DROOLS-604 > URL: https://issues.jboss.org/browse/DROOLS-604 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.Beta1, 6.2.0.Beta2, 6.2.0.Beta3 > Reporter: Abel Marrero Santos > Assignee: Mark Proctor > Priority: Critical > Attachments: model-base-0.0.1-SNAPSHOT.jar > > > I have found a problem in code generation when we use the feature "call a method on <variable>" from the Guided Rule Editor. An InvocationTargetException caused by a ClassCastException is thrown in RuleModelDRLPersistenceImpl.generateSetMethodCallsMethod method. > I have found other issues that I think are related and that I will try to mention in the comments. I can also provide you with the maven artifact that I'm using. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3683) ScheduledFuture#cancel(boolean) failing to cancel tasks on bean PreDestroy

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3683?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-3683: ---------------------------------- Comment: was deleted (was: EE Concurrency RI issue: https://java.net/jira/browse/CU_JAVAEE-6) > ScheduledFuture#cancel(boolean) failing to cancel tasks on bean PreDestroy > -------------------------------------------------------------------------- > > Key: WFLY-3683 > URL: https://issues.jboss.org/browse/WFLY-3683 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 8.1.0.Final > Reporter: Aaron Cordova > Assignee: Eduardo Martins > > Calls to ScheduledFuture#cancel on bean cleanup are failing to cancel subsequent tasks. > *NOTE* This only occurs when using the Trigger functionality. I tested the same code with scheduleAtFixedRate, and it works as expected. > The following bean demonstrates the bug: > {code:title=Executor.java|borderStyle=solid} > import java.util.ArrayList; > import java.util.Collections; > import java.util.Date; > import java.util.Iterator; > import java.util.List; > import java.util.concurrent.ScheduledFuture; > import java.util.concurrent.TimeUnit; > import javax.annotation.PostConstruct; > import javax.annotation.PreDestroy; > import javax.annotation.Resource; > import javax.ejb.Singleton; > import javax.ejb.Startup; > import javax.enterprise.concurrent.LastExecution; > import javax.enterprise.concurrent.ManagedScheduledExecutorService; > import javax.enterprise.concurrent.Trigger; > import org.slf4j.Logger; > import org.slf4j.LoggerFactory; > /** > * Session Bean implementation class DataRecorderManagerBean > */ > @Singleton > @Startup > public class ExecutorBug { > private static final Logger LOGGER = LoggerFactory.getLogger(ExecutorBug.class); > @Resource > private ManagedScheduledExecutorService executorService; > private List<ScheduledFuture<?>> scheduledTasks; > /** > * Default constructor. > */ > public ExecutorBug() { > } > @PostConstruct > void intialize() { > this.scheduledTasks = Collections.synchronizedList(new ArrayList<ScheduledFuture<?>>()); > // Schedule the device task. > PeriodicTrigger trigger = new PeriodicTrigger(0, 10, TimeUnit.SECONDS); > ScheduledFuture<?> future = this.executorService.schedule(new LogRunner(), trigger); > // Create the scheduled task and add it to the map. > this.scheduledTasks.add(future); > } > @PreDestroy > void cleanup() { > // Cancel any scheduled tasks, ensuring that the map is locked. > synchronized (this.scheduledTasks) { > Iterator<ScheduledFuture<?>> i = this.scheduledTasks.iterator(); > while (i.hasNext()) { > ScheduledFuture<?> future = i.next(); > // Cancel the task. > future.cancel(true); > } > } > this.scheduledTasks.clear(); > this.scheduledTasks = null; > } > private class LogRunner implements Runnable { > public LogRunner() { > } > @Override > public void run() { > LOGGER.info("I am running"); > } > } > private class PeriodicTrigger implements Trigger { > private final long periodMillis; > private Date startTime; > /** > * Creates and executes a periodic action that becomes enabled first after the given initial delay, and subsequently with the given period; that is executions will commence after initialDelay > * then initialDelay+period, then initialDelay + 2 * period, and so on. > * > * @param initialDelay the time to delay first execution > * @param period the period between successive executions > * @param unit the time unit of the initialDelay and period parameters > */ > public PeriodicTrigger(final long initialDelay, final long period, final TimeUnit unit) { > this.periodMillis = TimeUnit.MILLISECONDS.convert(period, unit); > // Calculate the start time. > Date now = new Date(); > long millis = TimeUnit.MILLISECONDS.convert(initialDelay, unit); > this.startTime = new Date(now.getTime() + millis); > } > @Override > public Date getNextRunTime(final LastExecution lastExecutionInfo, final Date taskScheduledTime) { > if (lastExecutionInfo == null) { > return this.startTime; > } > else { > return new Date(lastExecutionInfo.getScheduledStart().getTime() + this.periodMillis); > } > } > @Override > public boolean skipRun(final LastExecution lastExecutionInfo, final Date scheduledRunTime) { > return false; > } > } > } > {code} > Steps: > * Deploy bean in Wildfly 8.1.0-Final using maven deploy goal. > * Verify log statement is output. > * Un-deploy bean from admin console. > *Expected* > Log statement is no longer called > *Actual* > Log statement continues to output after bean is destroyed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014