October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1478) Enable CORS on the server side

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1478?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1478: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Enable CORS on the server side > ------------------------------ > > Key: WFLY-1478 > URL: https://issues.jboss.org/browse/WFLY-1478 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1592) Attempting to use eap6.1 jboss-cli.sh to connect to remote wildfly (alpha1 or 2) fails; credentials not accepted

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1592?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1592: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Attempting to use eap6.1 jboss-cli.sh to connect to remote wildfly (alpha1 or 2) fails; credentials not accepted > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1592 > URL: https://issues.jboss.org/browse/WFLY-1592 > Project: WildFly > Issue Type: Bug > Components: Remoting, Security > Affects Versions: 8.0.0.Alpha2 > Reporter: Rob Stryker > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Using eap6.1 client jars, or the jboss-cli.sh script in a local eap6.1 installation, to connect to a remote wildfly alpha1 or alpha2, seems to work but fails when provided with credentials. This is most easily replicated as follows: > 1) On remote machine start wildfly alpha1 or alpha2 > 2) on local machine, cd eap-6.1/bin > 3) on local machine: > [rob@rawbdor bin]$ ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect myhost.net > Authenticating against security realm: ManagementRealm > Username: admin > Password: > Unable to authenticate against controller at myhost.net:9999: Authentication failed: all available authentication mechanisms failed > This is an issue for tools as we need a set of jars that communicates correctly with all as7 servers. We currently have a set of jars that communicates with all 7.x / eap 6.x, which is good. If this is merely a bug on the server, then we can hopefully delay having to bundle an additional set of client jars until larger breakages occur. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1536) Hangs in mixed domain testsuite

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1536?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1536: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Hangs in mixed domain testsuite > ------------------------------- > > Key: WFLY-1536 > URL: https://issues.jboss.org/browse/WFLY-1536 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > Attachments: testsuite-hang1-server.txt, testsuite-hang2-client.txt, testsuite-hang2-server.txt > > > http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-param-pull... > https://dl.dropboxusercontent.com/u/712508/mixed-hang-debug.zip contains details. > 30805.dump is the client and shows the problem is occurring in the @After cleanup of MixedDomainDeploymentTest as it removes deployments from the domain. > "main" prio=10 tid=0xf7605c00 nid=0x7856 in Object.wait() [0xf776e000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at java.lang.Object.wait(Object.java:503) > at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192) > - locked <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266) > - locked <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.controller.client.helpers.domain.impl.DomainClientImpl.execute(DomainClientImpl.java:81) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.removeDeployment(MixedDomainDeploymentTest.java:441) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.cleanDeployments(MixedDomainDeploymentTest.java:343) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.confirmNoDeployments(MixedDomainDeploymentTest.java:163) > 31894.dump shows the master HC. management-handler-thread is blocking on the way out (after sending the commit or rollback) waiting for a final result response from the slave. > "management-handler-thread - 1" prio=10 tid=0xca0efc00 nid=0x7cdd in Object.wait() [0xc7469000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at java.lang.Object.wait(Object.java:503) > at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192) > - locked <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266) > - locked <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler.finalizeOp(DomainSlaveHandler.java:215) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler.access$000(DomainSlaveHandler.java:58) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler$1.handleResult(DomainSlaveHandler.java:179) > at org.jboss.as.controller.AbstractOperationContext$Step.handleRollback(AbstractOperationContext.java:805) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:763) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:738) > (Note that the "handleRollback" method name is a red-herring -- the method should be renamed to a "handleResult" as it now is called no matter what the result.) > 31986.dump is the slave HC. It shows it is blocking in stage DONE after having sent operationPrepared to the master, waiting for commit or rollback. > "domain-connection-threads - 1" prio=10 tid=0xc91a8400 nid=0x7d1a waiting on condition [0xc87fe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xea1fd410> (a java.util.concurrent.CountDownLatch$Sync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ProxyOperationControlProxy.operationPrepared(TransactionalProtocolOperationHandler.java:173) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:337) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.domain.controller.operations.coordination.ServerOperationsResolverHandler.execute(ServerOperationsResolverHandler.java:128) > Indication is the commit or rollback message is getting lost. There are no threads shown sending or receiving it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1588) Run CTS batch tests inside WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1588?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1588: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Run CTS batch tests inside WildFly > ---------------------------------- > > Key: WFLY-1588 > URL: https://issues.jboss.org/browse/WFLY-1588 > Project: WildFly > Issue Type: Task > Components: EE > Affects Versions: 8.0.0.Alpha4 > Reporter: Cheng Fang > Assignee: Cheng Fang > Fix For: 8.0.0.CR1 > > > Run CTS batch tests (web- and ejb-vehicle tests) inside WildFly. > Instructions for running cts7 against WildFly: > https://community.jboss.org/wiki/TCK7Guide > A related page, on how to run javax.batch standalone TCK with JBeret: > https://github.com/jberet/jsr352/wiki/Batch-TCK-with-JBeret -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1568) Cannot reliably reinstall service with same name

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1568?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1568: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Cannot reliably reinstall service with same name > ------------------------------------------------ > > Key: WFLY-1568 > URL: https://issues.jboss.org/browse/WFLY-1568 > Project: WildFly > Issue Type: Bug > Components: MSC > Reporter: Thomas Diesler > Assignee: David Lloyd > Fix For: 8.0.0.CR1 > > > There seems to be an undefined "cleanup period" needed, before a service with the same name can be installed successfully. If you do the below in the same thread it will always fail (I believe). > {code} > controller.setMode(Mode.REMOVE) > serviceTarget.addService(controller.getName(), service).install() > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1535) SSLEJBRemoteClientTestCase runs into intermittent failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1535?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1535: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > SSLEJBRemoteClientTestCase runs into intermittent failures > ---------------------------------------------------------- > > Key: WFLY-1535 > URL: https://issues.jboss.org/browse/WFLY-1535 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: jaikiran pai > Assignee: jaikiran pai > Priority: Critical > Fix For: 8.0.0.CR1 > > > SSLEJBRemoteClientTestCase runs into intermittent failures on TeamCity. To make matters worse, a failure in one test method can have a side effect on other test methods in that testcase, given the way it's written. The entire run is here http://teamcity.cafe-babe.org/viewLog.html?buildId=5251&tab=buildResultsD.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1725: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update The Wildfly High Availability Guide > ------------------------------------------- > > Key: WFLY-1725 > URL: https://issues.jboss.org/browse/WFLY-1725 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha3 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 8.0.0.CR1 > > > The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org. > Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering. > https://docs.jboss.org/author/display/WFLY8/High+Availability+Guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1702) Investigate module wiring consistency at build time

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1702?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1702: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Investigate module wiring consistency at build time > --------------------------------------------------- > > Key: WFLY-1702 > URL: https://issues.jboss.org/browse/WFLY-1702 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.CR1 > > > Due to the use of human wiring decisions it is possible that the initial modules wiring setup is incomplete/inconsistent. Various inconsistencies can occur > * There are code paths in a module that require a class load for which there is no dependency defined > * Modules define (stale) dependencies that are never used > * Modules define dependencies that are inconsistent in the class space -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1594?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1594: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Domain Management logout 'feature' not working for HTTP BASIC authentication. > ----------------------------------------------------------------------------- > > Key: WFLY-1594 > URL: https://issues.jboss.org/browse/WFLY-1594 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1825) Wildfly High Availability Guide: Infinispan write up

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1825?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1825: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Wildfly High Availability Guide: Infinispan write up > ---------------------------------------------------- > > Key: WFLY-1825 > URL: https://issues.jboss.org/browse/WFLY-1825 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY8/Infinispan+Subsystem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 October 2013