December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1703) Bump core console to 2.x

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1703?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1703: ----------------------------- Fix Version/s: 9.0.0.Final > Bump core console to 2.x > ------------------------ > > Key: WFLY-1703 > URL: https://issues.jboss.org/browse/WFLY-1703 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4054) Unexpected attribute can be added to elements in Transactions Subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4054?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4054: ----------------------------- Fix Version/s: 9.0.0.Final > Unexpected attribute can be added to elements in Transactions Subsystem > ----------------------------------------------------------------------- > > Key: WFLY-4054 > URL: https://issues.jboss.org/browse/WFLY-4054 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 9.0.0.Final > > > If you add unexpected argument to element in standalone.xml then it's expected to get error of "Unexpected attribute '...' encountered" [1] when server is started. > When you add a random argument to some of the elements in transactions then no error is thrown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2760) Intermittent failure of ExternalContextBindingTestCase

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2760?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2760: ----------------------------- Fix Version/s: 9.0.0.Final > Intermittent failure of ExternalContextBindingTestCase > ------------------------------------------------------- > > Key: WFLY-2760 > URL: https://issues.jboss.org/browse/WFLY-2760 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > Fix For: 9.0.0.Final > > > The server setup task sometimes fails to start the ApacheDS server instance because for some reason, BouncyCastle security provider doesn't get registered (it is added through a maven dependency rather than added to the JDK). This leads to a "connection refused" error during the test when it is trying to connect to the LDAP instance. > It worked for us if we just programatically forced registration of the BouncyCastleProvider before the initialization of ApacheDS. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2515) JBAS014249 if a fire and forget asynchronous ejb call is made

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2515?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2515: ----------------------------- Fix Version/s: 9.0.0.Final > JBAS014249 if a fire and forget asynchronous ejb call is made > ------------------------------------------------------------- > > Key: WFLY-2515 > URL: https://issues.jboss.org/browse/WFLY-2515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Beta1, 8.0.0.CR1 > Environment: Beta2 SNAPSHOT > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Fix For: 9.0.0.Final > > > If an ejb method > @Asynchronous void fireAndForget(...) > is called remote and the client disconnect an Exception JBAS014249 will be thrown if the async method return. > {noformat} > ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014249: Error invoking method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname : java.lang.NullPointerException > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 11:30:20,242 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: org.jboss.remoting3.NotOpenException: Writes closed > at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:112) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:301) > at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:68) > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100) > ... 9 more > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1764) Web Console: Remaining @AccessControl declarations

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1764?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1764: ----------------------------- Fix Version/s: 9.0.0.Final > Web Console: Remaining @AccessControl declarations > -------------------------------------------------- > > Key: WFLY-1764 > URL: https://issues.jboss.org/browse/WFLY-1764 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 9.0.0.Final > > > These are still missing: > {noformat} > DataSourceMetricPresenter(#ds-metrics) is missing @AccessControl annotation! > EnvironmentPresenter(#environment) is missing @AccessControl annotation! > JMSMetricPresenter(#jms-metrics) is missing @AccessControl annotation! > JPAMetricPresenter(#jpa-metrics) is missing @AccessControl annotation! > JndiPresenter(#naming) is missing @AccessControl annotation! > TXLogPresenter(#tx-logs) is missing @AccessControl annotation! > TXMetricPresenter(#tx-metrics) is missing @AccessControl annotation! > OSGiConfigurationPresenter(#osgi-configuration) is missing @AccessControl annotation! > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4666) Add smoke test for jaxrs-client

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4666?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4666: ----------------------------- Fix Version/s: 9.0.0.Final > Add smoke test for jaxrs-client > -------------------------------- > > Key: WFLY-4666 > URL: https://issues.jboss.org/browse/WFLY-4666 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Katerina Novotna > Assignee: Katerina Novotna > Fix For: 9.0.0.Final > > > https://issues.jboss.org/browse/EAP7-318 is adding resteasy-client. > This test serves as basic smoke tests to be run within the testsuite. > *BasicClientTestCase*: > * creates instance of resteasy client > * sends GET, POST, PUT and DELETE requests to the server > * verifies the answer from the server -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1432) ClassCastException when JBoss LogManager is initialized before the logging subsystem expects

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1432?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1432: ----------------------------- Fix Version/s: 9.0.0.Final > ClassCastException when JBoss LogManager is initialized before the logging subsystem expects > -------------------------------------------------------------------------------------------- > > Key: WFLY-1432 > URL: https://issues.jboss.org/browse/WFLY-1432 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: Kyle Lape > Assignee: James Perkins > Fix For: 9.0.0.Final > > > When making the following modifications to put JBoss LogManager on the boot classpath to make it available to Java agents: > {noformat} > diff --git a/bin/standalone.conf b/bin/standalone.conf > index 97895a5..9517129 100644 > --- a/bin/standalone.conf > +++ b/bin/standalone.conf > -35,7 +35,7 @@ > #JAVA="" > > if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then > - JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman" > + JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,org.jboss.logmanager.config,org.jboss.logmanager.errormanager,org.jboss.logmanager.filters,org.jboss.logmanager.formatters,org.jboss.logmanager.handlers" > fi > > # Uncomment the following line to prevent manipulation of JVM options > -48,7 +48,7 @@ fi > # > if [ "$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true" > - JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" > + JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final-redhat-1.jar -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true -Dcom.sun.management.jmxremote=x -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager" > else > echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS" > fi > {noformat} > I get the following error: > {noformat} > 09:28:18,984 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "logging"), > ("console-handler" => "CONSOLE") > ]): java.lang.ClassCastException: org.jboss.logmanager.PropertyConfigurator cannot be cast to org.jboss.as.logging.logmanager.ConfigurationPersistence > at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:93) > at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:81) > at org.jboss.as.logging.LoggingOperations$LoggingOperationStepHandler.execute(LoggingOperations.java:154) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2198) Remote Naming throws the same exception for different causes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2198?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2198: ----------------------------- Fix Version/s: 9.0.0.Final > Remote Naming throws the same exception for different causes > ------------------------------------------------------------ > > Key: WFLY-2198 > URL: https://issues.jboss.org/browse/WFLY-2198 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Final > > > A generic NamingException are thrown if all of the servers specified are unreachable as well as if the user/pass are invalid and a security exception is thrown up, they both are converted into a RuntimeException and a message listing the servers it was unable to call is reported. > We should be throwing a different exception in the cases we know the cause, such as connection timeout or authentication exception. > If all the the servers specified are not not running: > -------------------------------------------------------------------------------------------- > javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447] > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213) > If one of the servers is running, but the client's username/password are incorrect > -------------------------------------------------------------------------------------------- > javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447] > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4009) Cannot externalise camel-cdi & deltaspike

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4009?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4009: ----------------------------- Fix Version/s: 9.0.0.Final > Cannot externalise camel-cdi & deltaspike > ----------------------------------------- > > Key: WFLY-4009 > URL: https://issues.jboss.org/browse/WFLY-4009 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.1.0.Final > Reporter: Thomas Diesler > Assignee: Stuart Douglas > Fix For: 9.0.0.Final > > > Currently, there is a webapp deployed as part of the camel subsystem that contains > * camel-cdi > * deltaspike-core-api > * deltaspike-core-impl > * deltaspike-cdictrl-api > Generally it seems that every webapp needs to package these in order for camel-cdi to work. We would however like to replace these embedded jars with references to the already existing modules. > GitHub Issue: https://github.com/tdiesler/wildfly-camel/issues/15 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4267) Add Archetype integration test for HTML5 archetype

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4267?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4267: ----------------------------- Fix Version/s: 9.0.0.Final > Add Archetype integration test for HTML5 archetype > -------------------------------------------------- > > Key: WFLY-4267 > URL: https://issues.jboss.org/browse/WFLY-4267 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017