March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6655) binding subcontexts with <lookup> does not work

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-6655?page=com.atlassian.jira.plugin.s... ] Eduardo Martins commented on AS7-6655: -------------------------------------- Please note, the fix allows this use case to go through, yet it does not introduce any change wrt msc dependencies, which are globally under discussion in the context of AS7-6787 > binding subcontexts with <lookup> does not work > ----------------------------------------------- > > Key: AS7-6655 > URL: https://issues.jboss.org/browse/AS7-6655 > Project: Application Server 7 > Issue Type: Bug > Components: Naming > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Eduardo Martins > > If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. > To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ > In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. > As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3837) Fix or remove WebSecurityCERTTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-3837?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reopened AS7-3837: ------------------------------ Assignee: Tomaz Cerar (was: Stefan Guilhen) I have fix for this test case on my undertow integration branch > Fix or remove WebSecurityCERTTestCase > ------------------------------------- > > Key: AS7-3837 > URL: https://issues.jboss.org/browse/AS7-3837 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Final > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Labels: as7-ignored > Fix For: 7.1.2.Final (EAP) > > > This has an @Ignore on it from ages ago noting that it is waiting for Arquillian beta2 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3837) Fix or remove WebSecurityCERTTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-3837?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-3837: ----------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.1.2.Final (EAP)) > Fix or remove WebSecurityCERTTestCase > ------------------------------------- > > Key: AS7-3837 > URL: https://issues.jboss.org/browse/AS7-3837 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Final > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Labels: as7-ignored > Fix For: 8.0.0.Alpha1 > > > This has an @Ignore on it from ages ago noting that it is waiting for Arquillian beta2 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6811) Fix & re-enable ignored XCAML tests

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6811: -------------------------------- Summary: Fix & re-enable ignored XCAML tests Key: AS7-6811 URL: https://issues.jboss.org/browse/AS7-6811 Project: Application Server 7 Issue Type: Sub-task Components: Security, Web Affects Versions: 8.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Darran Lofthouse Currently ignore tests: {noformat} WebXACMLAuthorizationModuleTestCase {noformat} -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6810) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Kabir Khan (JIRA)

Kabir Khan created AS7-6810: ------------------------------- Summary: Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> Key: AS7-6810 URL: https://issues.jboss.org/browse/AS7-6810 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Alpha1 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6809) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by Kabir Khan (JIRA)

Kabir Khan created AS7-6809: ------------------------------- Summary: Avoid running out of threads when connecting to the DC from a slave to pull down missing data Key: AS7-6809 URL: https://issues.jboss.org/browse/AS7-6809 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Alpha1 For AS7-6808 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6605) Replicating JNDI tree to another server

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6605?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-6605: ----------------------------- Priority: Major (was: Critical) > Replicating JNDI tree to another server > ---------------------------------------- > > Key: AS7-6605 > URL: https://issues.jboss.org/browse/AS7-6605 > Project: Application Server 7 > Issue Type: Feature Request > Components: Naming > Affects Versions: 7.1.2.Final (EAP) > Reporter: Miroslav Novak > Assignee: Eduardo Martins > > Description of problem: > This use case is taken from one of our user which we were able to handle using HA-JNDI in EAP 5: > 1. JMS Client will create Context with two URL (node1, node2) (java.naming.provider.url property) > 2. For some reason client is connected to node2 first which will have no JMS admin objects registered in JNDI (this happens when this node is configured as HornetQ backup) > 3. Node2 has replicated JNDI tree from node1. So connection factory will connect client to node1 and queue/topics are deployed on node1. > Can be this functionality provided in EAP 6, please? -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6808) Auto ignore domain resources on a slave HC which do not affect its servers

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/AS7-6808?page=com.atlassian.jira.plugin.s... ] Kabir Khan updated AS7-6808: ---------------------------- Assignee: Kabir Khan Fix Version/s: 8.0.0.Alpha1 Component/s: Domain Management > Auto ignore domain resources on a slave HC which do not affect its servers > -------------------------------------------------------------------------- > > Key: AS7-6808 > URL: https://issues.jboss.org/browse/AS7-6808 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > Currently to avoid receiving resources and ops for parts of the domain model which do not work on an older slave we use <ignored-resources> in the slave host.xml to ignore them. > Instead we should only pull in parts of the domain model that is actually required on the slave for its servers to start. Once started we need to be able to update the slave with domain information as the config changes > The main things which can change affecting the data required are: > 1) A domain's server-group, where the profile (and thus extensions) and the socket-binding group can be changed. > 2) A host's server-config, where the server-group and the socket-binding-group override might be changed. > For 1) we can piggy-back missing data to the slave. > For 2) the slave needs to connect back to the DC, attempt to get the DC lock and pull down the required data. If the lock cannot be obtained, the operation should fail fast. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6779) AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/AS7-6779?page=com.atlassian.jira.plugin.s... ] Rob Stryker updated AS7-6779: ----------------------------- Attachment: AS7-6779.out2.txt When run with eap6.1 jars against as7.0.1, I do not get a 'freeze', but I do get a lot of stack traces in the output and a failure of the tests. I also get a connection reset. Attaching sysout + syserr. > AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang > --------------------------------------------------------------------- > > Key: AS7-6779 > URL: https://issues.jboss.org/browse/AS7-6779 > Project: Application Server 7 > Issue Type: Bug > Components: Remoting > Reporter: Rob Stryker > Assignee: Emanuel Muckenhuber > Priority: Blocker > Attachments: AS7-6779.out2.txt, AS7-6779.stack.txt, out.zip > > > Somewhere along the line recently, EAP6.1 / AS 7.2 has a regression in remoting or xnio somehow, and this is causing blocking problems for tools. > Recall: > 1) JBossTools bundles a set of jars capable of communicating with a running application server > 2) This single set of jars must be capable of communicating with all servers in the 7.x stream > 3) Bundling a second set of jars is not easily accomplished, but could be possible > And: > 4) Using the as7.1.0 jars against eap6.1 in a specific unit test causes eclipse to hang > The basic code of our test case (once we get rid of the jbt stuff wrapped around it) is basically as follows: > {code} > this.client = ModelControllerClient.Factory.create(details.getHost(), details.getManagementPort(), > getCallbackHandler()); > this.manager = ServerDeploymentManager.Factory.create(client); > DeploymentPlanBuilder builder = manager.newDeploymentPlan().replace(name, file); > try { > DeploymentAction action = builder.getLastAction(); > Future<ServerDeploymentPlanResult> planResult = manager.execute(builder.build()); > // FREEZE HERE > // This is "DeploymentOperationResult.getStatus() in the stack trace > ServerDeploymentActionResult actionResult = planResult.get().getDeploymentActionResult(action.getId()); > IStatus status = createStatus(action.getDeploymentUnitUniqueName(), action.getType().name(), actionResult); > } catch (Exception e) { > throw new JBoss7ManangerException(e); > } > {code} > The actual stack trace is: > {code} > Thread [main] (Suspended) > owns: RunnableLock (id=461) > waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=462) > Object.wait(long) line: not available [native method] > ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503 > ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192 > ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266 > AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 363 > AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 317 > ServerDeploymentPlanResultFuture.get() line: 76 > ServerDeploymentPlanResultFuture.get() line: 42 > DeploymentOperationResult.getStatus() line: 52 > AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93 > AS7ManagerIntegrationTest.canReplaceWar() line: 129 > {code} > The list of jars we are using to communicate with the server are: > {code} > jboss-as-controller-client-7.1.0.Final.jar > jboss-as-protocol-7.1.0.Final.jar > jboss-dmr-1.1.1.Final.jar > jboss-logging-3.1.0.GA.jar > jboss-marshalling-1.3.9.GA.jar > jboss-remoting-3.2.7.GA.jar > jboss-sasl-1.0.0.Final.jar > jboss-threads-2.0.0.GA.jar > xnio-api-3.0.3.GA.jar > xnio-nio-3.0.3.GA.jar > {code} > It was suggested in irc by ctomc that we simply replace the following jars with new jars from jboss-as 7.2 / eap6.1: > {code} > jboss-remoting-3.2.7.GA.jar -> 3.2.15.GA > xnio-api-3.0.3.GA.jar -> 3.0.7 > xnio-nio-3.0.3.GA.jar -> 3.0.7 > {code} > This approach also failed, with the following stack trace: > {code} > java.lang.NoClassDefFoundError: org/xnio/Cancellable > (sic) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:59) > at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:211) > at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:173) > {code} > So it is obvious that jboss-as-controller jar from as-7.1 requires classes that are no longer present in xnio. If this is the case, it would indicate that xnio has REMOVED classes from its jar during an incremental version from 3.0.3 to 3.0.7, which would constitute an API breakage. > So clearly for us, updating only remoting and xnio does not work. The next possible solution would be to update ALL jars, however, this led to a similar situation when using AS7.2 / Eap 6.1 jars to communicate with an AS 7.0.0 server. Again, similar to what was mentioned above, all tests passed EXCEPT the test above. The test above failed with an almost identical stack trace: > {code} > Thread [main] (Suspended) > owns: RunnableLock (id=160) > waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=161) > Object.wait(long) line: not available [native method] > ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503 > ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192 > ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266 > AbstractModelControllerClient$DelegatingCancellableAsyncFuture(AbstractDelegatingAsyncFuture<T>).get() line: 100 > ServerDeploymentPlanResultFuture.get() line: 76 > ServerDeploymentPlanResultFuture.get() line: 42 > DeploymentOperationResult.getStatus() line: 52 > AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93 > AS7ManagerTestUtils.quietlyUndeploy(String, AS71Manager) line: 76 > AS7ManagerIntegrationTest.canReplaceWar() line: 135 > {code} > No matter how you look at it, the contract has been broken. JBossTools now is looking for a specific set of jars which care capable of communicating with AS7.0, 7.1, 7.2, eap6.0, 6.1, jpp6.0, etc. Without a set of jars that can communicate with all of these servers, our tools will need to implement drastic workarounds or bundle several versions of the app server's jars within it. > It's interesting to me that the as7.1 jars work against everything except eap6.1, and yet, the eap6.1 jars work against everything except as7.0.0. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6808) Auto ignore domain resources on a slave HC which do not affect its servers

by Kabir Khan (JIRA)

Kabir Khan created AS7-6808: ------------------------------- Summary: Auto ignore domain resources on a slave HC which do not affect its servers Key: AS7-6808 URL: https://issues.jboss.org/browse/AS7-6808 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Currently to avoid receiving resources and ops for parts of the domain model which do not work on an older slave we use <ignored-resources> in the slave host.xml to ignore them. Instead we should only pull in parts of the domain model that is actually required on the slave for its servers to start. Once started we need to be able to update the slave with domain information as the config changes The main things which can change affecting the data required are: 1) A domain's server-group, where the profile (and thus extensions) and the socket-binding group can be changed. 2) A host's server-config, where the server-group and the socket-binding-group override might be changed. For 1) we can piggy-back missing data to the slave. For 2) the slave needs to connect back to the DC, attempt to get the DC lock and pull down the required data. If the lock cannot be obtained, the operation should fail fast. -- 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

13 years, 1 month

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 March 2013