February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4355) Move deprecated DeploymentUnit methods to the DeploymentResourceSupport

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Summary: Move deprecated DeploymentUnit methods to the DeploymentResourceSupport (was: Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed) > Move deprecated DeploymentUnit methods to the DeploymentResourceSupport > ----------------------------------------------------------------------- > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4355) Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Description: WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. (was: WFCORE-542 is adding new methods and changing/clarifying the contracts for the {{DeploymentUnit.createDeploymentSubModel}} methods. For now only a warning messages will be printed. A review of subsystems that use these methods needs to happen after a core version is released and added to full.) > Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed > ------------------------------------------------------------------------ > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4355) Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Issue Type: Task (was: Enhancement) > Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed > ------------------------------------------------------------------------ > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 is adding new methods and changing/clarifying the contracts for the {{DeploymentUnit.createDeploymentSubModel}} methods. For now only a warning messages will be printed. A review of subsystems that use these methods needs to happen after a core version is released and added to full. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-546) Remove warning log from DeploymentModelUtils

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-546?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-546. -------------------------------- Resolution: Rejected The scope of WFCORE-542 changed and the methods were deprecated. No warning message will be printed. > Remove warning log from DeploymentModelUtils > -------------------------------------------- > > Key: WFCORE-546 > URL: https://issues.jboss.org/browse/WFCORE-546 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > As part of WFCORE-542 a warning was introduced if {{DeploymentUnit.createDeploymentSubModel}} was invoked on a resource that already exists. For WildFly 10 this warning can go away and the error can be thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Description: Deprecate the methods that interact with the (was: The {{DeploymentUnit.getDeploymentSubsystemModel()}} and the {{DeploymentUnit.createDeploymentSubModel()}} methods were somewhat generic the documentation. The documentation needs to be clarified and the implementation needs to conform to the clarified documentation.) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > Deprecate the methods that interact with the -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Description: Deprecate the methods that interact with the deployments subsystem resources. Create a new API attached to the deployment unit to interact with the deployments resources. (was: Deprecate the methods that interact with the ) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > Deprecate the methods that interact with the deployments subsystem resources. Create a new API attached to the deployment unit to interact with the deployments resources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Summary: Deprecate DeploymentUnit deployment resource methods and create new API (was: Clarify the JavaDoc for DeploymentUnit sub-models) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > The {{DeploymentUnit.getDeploymentSubsystemModel()}} and the {{DeploymentUnit.createDeploymentSubModel()}} methods were somewhat generic the documentation. The documentation needs to be clarified and the implementation needs to conform to the clarified documentation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4396) mod_cluster subsystem find any http server on the network

by Jose Diaz (JIRA)

Jose Diaz created WFLY-4396: ------------------------------- Summary: mod_cluster subsystem find any http server on the network Key: WFLY-4396 URL: https://issues.jboss.org/browse/WFLY-4396 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.2.0.Final Environment: Ubuntu 14.04, wildfly 8.2.0.final, apache http server 2.2.29 Reporter: Jose Diaz Assignee: Paul Ferraro Priority: Critical I configure a Load Balanced HA Standalone Cluster, in my machine however in the network there is other apache http server when I wake up the server I get the next error: MODCLUSTER000043: Failed to send INFO to 10.21.51.121/10.21.51.121:22001: java.net.NoRouteToHostException: No existe ninguna ruta hasta el «host» I configure the mod_cluster in standalone-full-ha with: <subsystem xmlns="urn:jboss:domain:modcluster:1.2"> <mod-cluster-config advertise-socket="modcluster" proxy-list="127.0.0.1:80" balancer="jdcluster" connector="ajp"> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> Then get the same error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Cheng Fang edited comment on WFLY-4390 at 2/28/15 10:54 AM: ------------------------------------------------------------ Fixed in project JBeret: https://github.com/jberet/jsr352/commit/eed55070a42bbd15240e14b638fb12ea8... Also tested with attached batch-restartable.zip test against WildFly 9 snapshot. {code} 2015-02-28 08:21:37,154 INFO [com.example.batch.UnrestartableBatchTest] (default task-1) $$$ start(): jobid: 58, status: FAILED 2015-02-28 08:21:37,156 ERROR [stderr] (default task-1) javax.batch.operations.JobRestartException: JBERET000646: The job with name: unrestartable-job, execution id: 58, is configured not restartable 2015-02-28 08:21:37,156 ERROR [stderr] (default task-1) at org.jberet.operations.JobOperatorImpl.restart(JobOperatorImpl.java:210) 2015-02-28 08:21:37,156 ERROR [stderr] (default task-1) at com.example.batch.UnrestartableBatchTest.testRestartAfterException(UnrestartableBatchTest.java:57) {code} was (Author: cfang): Fixed in project JBeret: https://github.com/jberet/jsr352/commit/eed55070a42bbd15240e14b638fb12ea8... Also tested with attached batch-restartable.zip test against WildFly 9 snapshot. > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Cheng Fang > Attachments: batch-restartable.zip > > > The batch job defined with restartable=false must not be restartable, after failed or stopped. > GlassFish 4.1 results in the following: > [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ > javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. > But WildFly tries to execute the stopped or failed job. > Please check the attached test case. > wildfly: > $ mvn clean test -P wildfly-managed (or -P wildly-remote) > glassfish: > $ glassfish4/bin/asadmin start-domain > $ mvn clean test -P glassfish-remote -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4390) restartable=false bach job can be restarted

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-4390?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-4390: ---------------------------------- Updated WildFly batch sample app to verify restartable attribute, especially restart a previously failed job execution after a WildFly restart, to make sure the decision to disallow restart in the old job execution is persisted and subsequently retrieved and honored by the restart operation. https://github.com/chengfang/wildfly-samples/tree/master/jberet/deseriali... > restartable=false bach job can be restarted > ------------------------------------------- > > Key: WFLY-4390 > URL: https://issues.jboss.org/browse/WFLY-4390 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 8.2.0.Final > Reporter: Takashi Nishigaya > Assignee: Cheng Fang > Attachments: batch-restartable.zip > > > The batch job defined with restartable=false must not be restartable, after failed or stopped. > GlassFish 4.1 results in the following: > [2015-02-26T19:56:34.860+0900] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=25 _ThreadName=Thread-9] [timeMillis: 1424948194860] [levelValue: 1000] [[ > javax.batch.operations.JobRestartException: javax.batch.operations.JobRestartException: Job Restartable attribute is false, Job cannot be restarted. > But WildFly tries to execute the stopped or failed job. > Please check the attached test case. > wildfly: > $ mvn clean test -P wildfly-managed (or -P wildly-remote) > glassfish: > $ glassfish4/bin/asadmin start-domain > $ mvn clean test -P glassfish-remote -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 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 February 2015