June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-473) Minimize usage of NetworkInterface.getNetworkInterfaces()

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-473?page=com.atlassian.jira.plugin... ] Tomaz Cerar closed WFCORE-473. ------------------------------ Fix Version/s: 1.0.0.Final Resolution: Done > Minimize usage of NetworkInterface.getNetworkInterfaces() > --------------------------------------------------------- > > Key: WFCORE-473 > URL: https://issues.jboss.org/browse/WFCORE-473 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 1.0.0.Final > > > this calls are extra expensive so we should minimize its usage during boot time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3918) Cannot disable ConsoleRedirectService

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3918?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3918: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/7678 > Cannot disable ConsoleRedirectService > ------------------------------------- > > Key: WFLY-3918 > URL: https://issues.jboss.org/browse/WFLY-3918 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Graham Johnson > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha5 > > > Wildfly Undertow (via org.wildfly.extension.undertow.HostAdd and org.wildfly.extension.undertow.ConsoleRedirectService) redirects all /console/... URL requests (on port 8080/8443) to /console on port 9990. > This prevents developing or porting applications that themselves need to serve /console/... URLs. > There needs to be a way to disable (in the undertow subsystem configuration) the adding of ConsoleRedirectService by HostAdd. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3918) Cannot disable ConsoleRedirectService

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3918?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3918: ------------------------------ Fix Version/s: 10.0.0.Alpha5 > Cannot disable ConsoleRedirectService > ------------------------------------- > > Key: WFLY-3918 > URL: https://issues.jboss.org/browse/WFLY-3918 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Graham Johnson > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha5 > > > Wildfly Undertow (via org.wildfly.extension.undertow.HostAdd and org.wildfly.extension.undertow.ConsoleRedirectService) redirects all /console/... URL requests (on port 8080/8443) to /console on port 9990. > This prevents developing or porting applications that themselves need to serve /console/... URLs. > There needs to be a way to disable (in the undertow subsystem configuration) the adding of ConsoleRedirectService by HostAdd. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4840) Deprecated element cluster-passivation-store from ejb subsystem does not work

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4840?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4840: --------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Deprecated element cluster-passivation-store from ejb subsystem does not work > ----------------------------------------------------------------------------- > > Key: WFLY-4840 > URL: https://issues.jboss.org/browse/WFLY-4840 > Project: WildFly > Issue Type: Bug > Components: Domain Management, EJB > Reporter: Ondřej Chaloupka > Assignee: Paul Ferraro > > There is a mismatch in behaviour of deprecated element {{cluster-passivation-store}} under {{ejb}} subsystem. > When element is deprecated still it should work and only prints warning that it's deprecated. > {code} > [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-resource() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"ejb3\"), > (\"cluster-passivation-store\" => \"infinispan\") > ]' not found", > "rolled-back" => true > } > {code} > but > {code} > [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered", > "rolled-back" => true > } > {code} > _A note:_ the element {{cluster-passivation-store}} was replaced by {{passivation-store}} which works fine -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4645) access log rotates even when rotation is disabled by "rotate" attribute

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4645?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4645: ------------------------------ Fix Version/s: 10.0.0.Alpha5 > access log rotates even when rotation is disabled by "rotate" attribute > ----------------------------------------------------------------------- > > Key: WFLY-4645 > URL: https://issues.jboss.org/browse/WFLY-4645 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha5 > > > When I disable access log rotation by setting "rotate" attribute to false: > {code} > /subsystem=undertow/server=default-server/host=default-host/setting=access-log/:write-attribute(name=rotate,value=false) > {code} > The logfile keeps rotating - how tested in "Steps to Reproduce" section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4290) Datasource template operation

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-4290?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-4290: ------------------------------------- Labels: open_to_community (was: ) Assignee: (was: Stefano Maestri) > Datasource template operation > ----------------------------- > > Key: WFLY-4290 > URL: https://issues.jboss.org/browse/WFLY-4290 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Labels: open_to_community > > {noformat} > /subsystem=datasources/datasource=<datasource-name>:add(type=”postgresql”, url=””, driver=””) > {noformat} > Could have an optional capacity profile -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1366) @DataSourceDefinition incorrectly requires other properties than name and class-name

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1366?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-1366: --------------------------------------- The linked PR has the test I used to check the issue. > @DataSourceDefinition incorrectly requires other properties than name and class-name > ------------------------------------------------------------------------------------ > > Key: WFLY-1366 > URL: https://issues.jboss.org/browse/WFLY-1366 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 8.0.0.Alpha1 > Reporter: arjan tijms > Assignee: Eduardo Martins > Labels: spec, validation > > When using the <data-source> element in e.g. web.xml or application.xml JBoss EAP 6.0.1/JBoss AS 7.1.3 does not accept a configuration without properties other than {{name}} and {{class-name}}. For instance: > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MyDS</class-name> > </data-source> > {code} > With such configuration, the following exception is thrown: > {noformat} > Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.validate(XADataSourceImpl.java:385) > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.<init>(XADataSourceImpl.java:116) > at org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl.<init>(XADataSourceImpl.java:76) > at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:373) > at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:70) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:116) > {noformat} > At the point where the exception is thrown, the code checks if there are any properties at all: > {code} > if (this.xaDataSourceProperty.isEmpty()) > throw new ValidateException( > bundle.requiredElementMissing( > Tag.XA_DATASOURCE_PROPERTY.getLocalName(), > this.getClass().getCanonicalName())); > {code} > I don't understand why this check is there. If I'm not mistaken the spec (e.g. JSR 250 section 2.13 and JSR 316 section EE.5.17) does not seem to mandate properties to be present and the corresponding annotation only requires {{name}} and {{className}} to be specified. > A workaround is to subclass the data source class and provide a dummy property, e.g. > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MySubDS</class-name> > <property> > <name>dummy</name> > <value>dummy</value> > </property> > </data-source> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1366) @DataSourceDefinition incorrectly requires other properties than name and class-name

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1366?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-1366: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/7676 > @DataSourceDefinition incorrectly requires other properties than name and class-name > ------------------------------------------------------------------------------------ > > Key: WFLY-1366 > URL: https://issues.jboss.org/browse/WFLY-1366 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 8.0.0.Alpha1 > Reporter: arjan tijms > Assignee: Eduardo Martins > Labels: spec, validation > > When using the <data-source> element in e.g. web.xml or application.xml JBoss EAP 6.0.1/JBoss AS 7.1.3 does not accept a configuration without properties other than {{name}} and {{class-name}}. For instance: > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MyDS</class-name> > </data-source> > {code} > With such configuration, the following exception is thrown: > {noformat} > Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.validate(XADataSourceImpl.java:385) > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.<init>(XADataSourceImpl.java:116) > at org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl.<init>(XADataSourceImpl.java:76) > at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:373) > at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:70) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:116) > {noformat} > At the point where the exception is thrown, the code checks if there are any properties at all: > {code} > if (this.xaDataSourceProperty.isEmpty()) > throw new ValidateException( > bundle.requiredElementMissing( > Tag.XA_DATASOURCE_PROPERTY.getLocalName(), > this.getClass().getCanonicalName())); > {code} > I don't understand why this check is there. If I'm not mistaken the spec (e.g. JSR 250 section 2.13 and JSR 316 section EE.5.17) does not seem to mandate properties to be present and the corresponding annotation only requires {{name}} and {{className}} to be specified. > A workaround is to subclass the data source class and provide a dummy property, e.g. > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MySubDS</class-name> > <property> > <name>dummy</name> > <value>dummy</value> > </property> > </data-source> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1366) @DataSourceDefinition incorrectly requires other properties than name and class-name

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1366?page=com.atlassian.jira.plugin.... ] Eduardo Martins resolved WFLY-1366. ----------------------------------- Resolution: Out of Date The issue is out of date, checked master and 8.2.0.Final, it probably was fixed when I reworked resource definitions. > @DataSourceDefinition incorrectly requires other properties than name and class-name > ------------------------------------------------------------------------------------ > > Key: WFLY-1366 > URL: https://issues.jboss.org/browse/WFLY-1366 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 8.0.0.Alpha1 > Reporter: arjan tijms > Assignee: Eduardo Martins > Labels: spec, validation > > When using the <data-source> element in e.g. web.xml or application.xml JBoss EAP 6.0.1/JBoss AS 7.1.3 does not accept a configuration without properties other than {{name}} and {{class-name}}. For instance: > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MyDS</class-name> > </data-source> > {code} > With such configuration, the following exception is thrown: > {noformat} > Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.validate(XADataSourceImpl.java:385) > at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.<init>(XADataSourceImpl.java:116) > at org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl.<init>(XADataSourceImpl.java:76) > at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:373) > at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:70) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:116) > {noformat} > At the point where the exception is thrown, the code checks if there are any properties at all: > {code} > if (this.xaDataSourceProperty.isEmpty()) > throw new ValidateException( > bundle.requiredElementMissing( > Tag.XA_DATASOURCE_PROPERTY.getLocalName(), > this.getClass().getCanonicalName())); > {code} > I don't understand why this check is there. If I'm not mistaken the spec (e.g. JSR 250 section 2.13 and JSR 316 section EE.5.17) does not seem to mandate properties to be present and the corresponding annotation only requires {{name}} and {{className}} to be specified. > A workaround is to subclass the data source class and provide a dummy property, e.g. > {code:xml} > <data-source> > <name>java:app/myDS</name> > <class-name>com.example.MySubDS</class-name> > <property> > <name>dummy</name> > <value>dummy</value> > </property> > </data-source> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-160) jboss-transaction-api OSGi bundle requiring optional packages

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBEE-160?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned JBEE-160: -------------------------------- Assignee: Scott Marlow (was: Tomaz Cerar) > jboss-transaction-api OSGi bundle requiring optional packages > ------------------------------------------------------------- > > Key: JBEE-160 > URL: https://issues.jboss.org/browse/JBEE-160 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Scott Marlow > > The jboss-transaction-api_1.2_spec OSGi bundle requires the 'javax.enterprise.context'. Instead, that should be optional, right? cdi-api shouldn't be required to simply use jta. Thanks! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015