July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2176) TS: Check tests workdirs

by Ondrej Zizka (Created) (JIRA)

TS: Check tests workdirs ------------------------ Key: AS7-2176 URL: https://issues.jboss.org/browse/AS7-2176 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka Some tests (also unit tests) have work dirs in ${basedir}, which leaves garbage after running. That should change either to target/work or /tmp/... (consider what's better). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
4
0 / 0

[JBoss JIRA] (AS7-2007) Testsuite tasks (tracking)

by Ondrej Zizka (Created) (JIRA)

Testsuite tasks (tracking) -------------------------- Key: AS7-2007 URL: https://issues.jboss.org/browse/AS7-2007 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

10
28
0 / 0

[JBoss JIRA] (AS7-4090) Opimize organization and management of the Infinispan subsystem

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-4090: ---------------------------------------- Summary: Opimize organization and management of the Infinispan subsystem Key: AS7-4090 URL: https://issues.jboss.org/browse/AS7-4090 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: Paul Ferraro Fix For: 7.1.2.Final There are a number of areas where the Infinispan subsystem is organizationally deficient: - does not make use of ResourceDefinitions to (i) simplify the generation of DescriptionProviders and (ii) localize the definition of AttributeDefinitions - handlers are in some cases written from scratch rather than subclassing helper handlers such as AbstractWriteAttributeHandler, AbstractAddStepHandler, AbstractRemoveStepHandler, etc. - collections of services are defined monolithically, rather than in distinct units which makes stopping/restarting them error prone (c.f. CacheContainerAdd, CacheAdd install three or four services each with complex processing - stopping and restarting this in another handler is next to impossible) - ServiceNames are not always easy to reconstruct These issues make maintenance of the subsystem hard. These matters can be helped by: - making use of ResourceDefinitions - defining for each service X a static method installX(context, operation, model) and removeX(context, operation, model) which can be made use of in installServices(context, operation, model) and removeServices(operation, context, model) - define the static method populate(), used to populate a model from an operation, which can be reused in populateModel(), creating describe operations, as well as other contexts - define a static method installServices(context, operation, model) which can be used in performRuntime(), and in contexts where all services for a resource need to be stopped and restarted; similarly define removeServices(context, operation, model) - make sure each ServiceName can be regenerated easily (c.f. regenerating JNDI names can involve model processing) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
10
0 / 0

[JBoss JIRA] (AS7-4797) Convert resource-adapter subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4797: -------------------------------- Summary: Convert resource-adapter subsystem to ResourceDefinition Key: AS7-4797 URL: https://issues.jboss.org/browse/AS7-4797 Project: Application Server 7 Issue Type: Sub-task Components: JCA Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Jesper Pedersen Fix For: 7.2.0.Alpha1 Convert subsystem to use ResourceDefinition and AttributeDefinition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] (AS7-5133) "Once a process is reloaded, always reloaded" exception when reloading AS7

by Galder Zamarreño (JIRA)

Galder Zamarreño created AS7-5133: ------------------------------------- Summary: "Once a process is reloaded, always reloaded" exception when reloading AS7 Key: AS7-5133 URL: https://issues.jboss.org/browse/AS7-5133 Project: Application Server 7 Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Brian Stansberry In a master build, once an server started in admin mode is reloaded, it throws: {code}16:52:31,576 ERROR [org.jboss.msc.service] MSC00002: Invocation of listener "org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1@16e3a921" failed: java.lang.AssertionError: Once a process is reloaded, always reloaded! at org.jboss.as.controller.RunningModeControl.setReloaded(RunningModeControl.java:53) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432] at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:72) at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:63) at org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1.transition(ProcessReloadHandler.java:95) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] (AS7-4963) HTTPS configuration throws errors in when running domain.sh and no errors in case of standalone.sh

by Andriy Kalashnykov (JIRA)

Andriy Kalashnykov created AS7-4963: --------------------------------------- Summary: HTTPS configuration throws errors in when running domain.sh and no errors in case of standalone.sh Key: AS7-4963 URL: https://issues.jboss.org/browse/AS7-4963 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.1.Final Environment: Red Hat Linux x64 (virtual via VMWare) Reporter: Andriy Kalashnykov Assignee: Anil Saldhana Configuring SSL in "ha" profile of domain.xml: <connector name="https" protocol="HTTP/1.1" socket-binding="https" scheme="https" secure="true" enable-lookups="false"> <ssl cipher-suite="ALL" protocol="TLSv1" verify-client="false" name="https" key-alias="jboss" password="jbossjboss" certificate-key-file="/opt/jboss/jboss-as-7.1.1.Final/standalone/configuration/keystore.jks"/> </connector> Executing ./domain.sh, and in the JBoss logs there is an error: [Server:web-server-group-001] 13:55:24,152 ERROR [stderr] (pool-6-thread-1) Exception in thread "pool-6-thread-1" java.lang.IllegalStateException: java.io.IOException: Keystore was tampered with, or password was incorrect [Server:web-server-group-001] 13:55:24,157 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:113) [Server:web-server-group-001] 13:55:24,160 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.<init>(DefaultMCMPHandler.java:747) [Server:web-server-group-001] 13:55:24,165 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.add(DefaultMCMPHandler.java:183) [Server:web-server-group-001] 13:55:24,166 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.addProxy(DefaultMCMPHandler.java:179) [Server:web-server-group-001] 13:55:24,171 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl$AdvertiseListenerWorker.run(AdvertiseListenerImpl.java:443) [Server:web-server-group-001] 13:55:24,171 ERROR [stderr] (pool-6-thread-1) at java.lang.Thread.run(Thread.java:662) [Server:web-server-group-001] 13:55:24,177 ERROR [stderr] (pool-6-thread-1) Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect [Server:web-server-group-001] 13:55:24,177 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771) [Server:web-server-group-001] 13:55:24,178 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38) [Server:web-server-group-001] 13:55:24,190 ERROR [stderr] (pool-6-thread-1) at java.security.KeyStore.load(KeyStore.java:1185) [Server:web-server-group-001] 13:55:24,190 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getStore(JSSESocketFactory.java:259) [Server:web-server-group-001] 13:55:24,191 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeystore(JSSESocketFactory.java:208) [Server:web-server-group-001] 13:55:24,191 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:280) [Server:web-server-group-001] 13:55:24,202 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98) [Server:web-server-group-001] 13:55:24,202 ERROR [stderr] (pool-6-thread-1) ... 5 more [Server:web-server-group-001] 13:55:24,203 ERROR [stderr] (pool-6-thread-1) Caused by: java.security.UnrecoverableKeyException: Password verification failed [Server:web-server-group-001] 13:55:24,205 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769) [Server:web-server-group-001] 13:55:24,206 ERROR [stderr] (pool-6-thread-1) ... 11 more If mentioned above configuraion parameters copied to standalone.xml and ./standalone.sh executed - there will be no errors reported. Interestingly, as result HTTPS will be available on port 8443 in both cases... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] (AS7-2506) Domain Model Visulaization

by Pat McDonough (Created) (JIRA)

Domain Model Visulaization -------------------------- Key: AS7-2506 URL: https://issues.jboss.org/browse/AS7-2506 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Pat McDonough Assignee: Heiko Braun Provide a visual/graphic model of the current domain model. The model would visually indicate things such as: * Hosts * App Servers * JVM processes and parameters * Highlight the domain controller * Display host controller info * Active Profiles * Network interfaces * ?Clusters? Each of the components could provide additional contextual info and hyperlinked If done well, this would serve as a great landing page for console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
10
0 / 0

[JBoss JIRA] (JBRULES-3397) Support for local ltransactions ("EntityTransaction")

by Marco Rietveld (JIRA)

Marco Rietveld created JBRULES-3397: --------------------------------------- Summary: Support for local ltransactions ("EntityTransaction") Key: JBRULES-3397 URL: https://issues.jboss.org/browse/JBRULES-3397 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: 5.4.0.Beta2, 5.3.1.Final Reporter: Marco Rietveld Assignee: Marco Rietveld Fix For: 5.3.2.Final, 5.4.0.Final Support for local transactions in Drools/jBPM(JPA EntityTransactions, whatever you want to call them.. :) ). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3083) DecisionTable incorrectly parsed with 5.2.0.CR1

by Kara Melba (JIRA)

DecisionTable incorrectly parsed with 5.2.0.CR1 ----------------------------------------------- Key: JBRULES-3083 URL: https://issues.jboss.org/browse/JBRULES-3083 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.CR1 Reporter: Kara Melba Assignee: Mark Proctor 5.2.0.CR1 creates incorrect drl from decition table. With 5.1.0.M1 the drl for the same decision tables is correct. Wrong DRL from 5.2.0.CR1: rule "ProcessState" salience 65522 ruleflow-group "CompleteSubOrder" activation-group "ProcessState" when $m:ModifiedMarker(processState==null, state ==null) $s:SubOrder then $m.setIsModified(true); $s.setProcessState(ProcessState.CREATED); end Correct DRL with 5.1.0.M1: rule "ProcessState" salience 65522 ruleflow-group "CompleteSubOrder" activation-group "ProcessState" when $m:ModifiedMarker() $s:SubOrder(processState==null, state ==null) then $m.setIsModified(true); $s.setProcessState(ProcessState.CREATED); end -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
22
0 / 0

[JBoss JIRA] (AS7-4780) Incorrect status report when missing services are no longer needed

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4780: ------------------------------------- Summary: Incorrect status report when missing services are no longer needed Key: AS7-4780 URL: https://issues.jboss.org/browse/AS7-4780 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 If a service is missing, that gets recorded when detected (e.g. at boot): 16:28:50,626 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote, service jboss.ejb3.localEjbReceiver.value, service jboss.ejb3.connector, service jboss.ejb3.localEjbReceiver.reference] service jboss.remoting.server.remoting-connector (missing) dependents: [service jboss.ejb.remoting.connector.client-mapping-entry-provider-service, service jboss.ejb3.connector] But then at shutdown, when the service is no longer required, the status report says it is "(new available)" instead of the expected "(no longer required)" 16:46:06,776 INFO [org.jboss.as.controller] JBAS014774: Service status report JBAS014776: Newly corrected services: service jboss.remoting.endpoint.subsystem (new available) service jboss.remoting.server.remoting-connector (new available) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
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 July 2012