September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3791) Allow deployment initialization to have read-access to portions of the model

by ofbiz brazil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ] ofbiz brazil commented on WFLY-3791: ------------------------------------ Hi guys, any news about it? Thanks a lot! > Allow deployment initialization to have read-access to portions of the model > ---------------------------------------------------------------------------- > > Key: WFLY-3791 > URL: https://issues.jboss.org/browse/WFLY-3791 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Environment: Java 7 > Reporter: ofbiz brazil > Fix For: Awaiting Volunteers > > > Hello, > When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine. > Java Code: > {code:java} > final ModelNode request = new ModelNode(); > request.get(ClientConstants.OP).set("read-resource"); > request.get("recursive").set(true); > request.get(ClientConstants.OP_ADDR).add("subsystem", "security"); > final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999); > final ModelNode response = client.execute(new OperationBuilder(request).build()); > final String section = response.get(ClientConstants.RESULT).get("security-domain") > .get("pw_MSSQL_CAS_DS") > {code} > Result: > --------- > {code} > { > "outcome" => "failed", > "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found", > "rolled-back" => true > } > {code} > Cheers, -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-109) New line characters are written incorrectly to the properties configuration file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-109?page=com.atlassian.jira.plugin... ] James Perkins closed LOGMGR-109. -------------------------------- Resolution: Rejected This wasn't really a bug in the logmanager. > New line characters are written incorrectly to the properties configuration file > -------------------------------------------------------------------------------- > > Key: LOGMGR-109 > URL: https://issues.jboss.org/browse/LOGMGR-109 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > If a value of {{\n}} is used for a property on a handler, the value is written as {{\\n}} to the {{logging.properties}} file. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-83) EAR deployment overlay did not work if there is no related resource included in the ear

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-83?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved WFLY-3673 to WFCORE-83: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-83 (was: WFLY-3673) > EAR deployment overlay did not work if there is no related resource included in the ear > --------------------------------------------------------------------------------------- > > Key: WFCORE-83 > URL: https://issues.jboss.org/browse/WFCORE-83 > Project: WildFly Core > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Attachments: reproducer.zip > > > It is possible to overlay WEB-inf/lib/xy.jar without having xy.jar included in the war file. > If an EAR file is used a module in the lib directory can not be added in the same way. But overlay is working if the lib/xy.jar is available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-2) Implement feature pack filtering

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-2?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFBUILD-2: -------------------------------------- This should be specified in the provisioning file when you specify the feature packs you want. For for example you can effective say 'give me wildfly-web, plus the JCA subsytem from wildfly-full'. Something like: {code} <feature-packs> <artifact groupId="org.wildfly" artifactId="wildfly-web" version="${project.version}"/> <artifact groupId="org.wildfly" artifactId="wildfly-feature-pack" version="${project.version}"> <subsystems> <subsystem name="jca" /> </subsytems> </artifact> </feature-packs> {code} > Implement feature pack filtering > -------------------------------- > > Key: WFBUILD-2 > URL: https://issues.jboss.org/browse/WFBUILD-2 > Project: WildFly Build Tools > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Eduardo Martins > > It should be possible to provision a server with only a subset of the modules required by a feature pack. For instance a user may wish to take the wildfly-web feature pack, and then add just the JPA component of the full server. It should be possible to specify this in the provisioning file, and all transient dependencies should also be included. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-2) Implement feature pack filtering

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-2?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFBUILD-2: ------------------------------------ Assignee: Eduardo Martins (was: Stuart Douglas) > Implement feature pack filtering > -------------------------------- > > Key: WFBUILD-2 > URL: https://issues.jboss.org/browse/WFBUILD-2 > Project: WildFly Build Tools > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Eduardo Martins > > It should be possible to provision a server with only a subset of the modules required by a feature pack. For instance a user may wish to take the wildfly-web feature pack, and then add just the JPA component of the full server. It should be possible to specify this in the provisioning file, and all transient dependencies should also be included. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3809) JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows

by Jesse Jaggars (JIRA)

Jesse Jaggars created WFLY-3809: ----------------------------------- Summary: JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows Key: WFLY-3809 URL: https://issues.jboss.org/browse/WFLY-3809 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: JDR Environment: All modes on Windows Reporter: Jesse Jaggars Assignee: Jesse Jaggars JDR replaces $JBOSS_HOME with the text `JBOSS_HOME` in the generated zipfile. On windows the path is improperly constructed. For example if JBOSS_HOME=/foo/bar/baz, when the file /foo/bar/baz/example.txt is copied into the JDR archive the path will be: JBOSS_HOMEz/example.txt It should be: JBOSS_HOME/example.txt -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3023) JDR CommandLineMain defaults to port 9999

by Jesse Jaggars (JIRA)

[ https://issues.jboss.org/browse/WFLY-3023?page=com.atlassian.jira.plugin.... ] Jesse Jaggars resolved WFLY-3023. --------------------------------- Resolution: Done > JDR CommandLineMain defaults to port 9999 > ----------------------------------------- > > Key: WFLY-3023 > URL: https://issues.jboss.org/browse/WFLY-3023 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JDR > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Jesse Jaggars > > If the user doesn't provide a port, CommandLineMain defaults to 9999, but with protocol http-remoting. That combo won't work. It should use 9990 since that will be the default management port. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3808) PartitionPlan.getThreads() returning zero value causes batch job not be started

by Ari Silvan (JIRA)

Ari Silvan created WFLY-3808: -------------------------------- Summary: PartitionPlan.getThreads() returning zero value causes batch job not be started Key: WFLY-3808 URL: https://issues.jboss.org/browse/WFLY-3808 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Batch Affects Versions: 8.1.0.Final Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly 8.1.0 Final Reporter: Ari Silvan Assignee: Jason Greene If you define a batch job to be divided to multiple partitions and write a PartitionMapper returning a PartitionPlanImpl object but don't override getThreads method, which means getThreads returns zero meaning thread count should be equal to partition count, but the batch job doesn't start. See http://docs.oracle.com/javaee/7/api/javax/batch/api/partition/PartitionPl... In GlassFish this works as expected: if getThreads is not overridden (thus returning zero), batch job is started in as many threads as there are partitions. See steps to reproduce for further details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1402) Too Many Dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1402: ----------------------------------------------- Jay SenSharma <jsenshar(a)redhat.com> changed the Status of [bug 1136956|https://bugzilla.redhat.com/show_bug.cgi?id=1136956] from NEW to POST > Too Many Dependencies > --------------------- > > Key: WFLY-1402 > URL: https://issues.jboss.org/browse/WFLY-1402 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Alpha1 > Environment: W7 64 bit > Reporter: Michael McGovern > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha2 > > > Large app ~ 1000 SLSB gets > Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383) > at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1878) Multicast discovery does not work on JDK8

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1878?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1878: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1076015 > Multicast discovery does not work on JDK8 > ----------------------------------------- > > Key: JGRP-1878 > URL: https://issues.jboss.org/browse/JGRP-1878 > Project: JGroups > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.2.12, 3.5 > Environment: OpenJDK8, OracleJDK8u40 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Blocker > Fix For: 3.2.14 > > > Multicast discovery does not work on JDK8 when using different bind IP addresses. This blocks EAP certification on JDK8. > Steps to reproduce with draw, switch to JDK8: > {noformat} > export IP_ADDR=127.0.0.1 > ./draw.sh > export IP_ADDR=192.168.1.10 > ./draw.sh > {noformat} > Everything works when binding to the same IP address or using JDK 6 or 7. Possibly a JDK8 bug.. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 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 September 2014