January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3230) Provide a GUI for the CLI

by Stan Silvert (Created) (JIRA)

Provide a GUI for the CLI ------------------------- Key: AS7-3230 URL: https://issues.jboss.org/browse/AS7-3230 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.0.CR1b Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.1.0.Final See http://community.jboss.org/wiki/AGUIForTheCommandLineInterface -- 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

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-783) Deployment scanner service should use a separate operation for each deployment

by Brian Stansberry (JIRA)

Deployment scanner service should use a separate operation for each deployment ------------------------------------------------------------------------------ Key: AS7-783 URL: https://issues.jboss.org/browse/AS7-783 Project: Application Server 7 Issue Type: Task Components: Console Reporter: Brian Stansberry Fix For: 7.0.0.CR1 The scanner is creating a single composite op for all deployments encountered in a scan, rather than individual ops. The effect is failures in on deployment results in rolling back the others. This makes some sense when users change things after startup, since multiple changes within one scan are probably related to each other. But it's not the correct behavior at startup, since multiple apps may not be interrelated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

8
8
0 / 0

[JBoss JIRA] (AS7-3336) Values set in OSGi ConfigAdmin do not get written to standalone.xml

by David Bosschaert (JIRA)

David Bosschaert created AS7-3336: ------------------------------------- Summary: Values set in OSGi ConfigAdmin do not get written to standalone.xml Key: AS7-3336 URL: https://issues.jboss.org/browse/AS7-3336 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Thomas Diesler When a configuration value gets set in the OSGi Configuration Admin Service this value should get persisted in the configadmin section of standalone.xml. The ConfigurationAdminTestCase (in as7 testsuite/integration/basic) contains this code: {noformat} Configuration config = configAdmin.getConfiguration(ConfiguredService.SERVICE_PID); assertNotNull("Config not null", config); try { Dictionary<String, String> configProps = new Hashtable<String, String>(); configProps.put("foo", "bar"); config.update(configProps);{noformat} When running this test case with AS7 running I can see that it is run in the server. I was expecting the foo=bar configuration to appear in the configadmin section of standalone.xml, but it doesn't appear there. -- 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

12 years, 5 months

2
5
0 / 0

[JBoss JIRA] (AS7-3334) failed to resolve interface management

by Rafael Soares (JIRA)

[ https://issues.jboss.org/browse/AS7-3334?page=com.atlassian.jira.plugin.s... ] Rafael Soares deleted AS7-3334: ------------------------------- > failed to resolve interface management > -------------------------------------- > > Key: AS7-3334 > URL: https://issues.jboss.org/browse/AS7-3334 > Project: Application Server 7 > Issue Type: Bug > Environment: RHEL 6.2 > Open JDK 1.6_20 > Reporter: Rafael Soares > Assignee: Brian Stansberry > Labels: domain, scripts > > When you try to start a domain using > ./domain.sh -bmanagement=x.x.x.x > as described in domain.sh help > -b <value> JBAS012053: Set system property > jboss.bind.address to the given value > -b<interface>=<value> JBAS012054: Set system property > jboss.bind.address.<interface> to the > given value > The domain fails with the following error > 12:08:29,895 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6 > 12:08:30,183 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' > [Host Controller] 12:08:30,804 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6 > [Host Controller] 12:08:31,705 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA > [Host Controller] 12:08:31,819 INFO [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.1.0.CR1b "Flux Capacitor" starting > [Host Controller] 12:08:32,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management > [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] > [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] > [Host Controller] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] > [Host Controller] > [Host Controller] 12:08:32,934 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report > [Host Controller] JBAS014777: Services which failed to start: service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management > [Host Controller] > [Host Controller] 12:08:32,954 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.CR7 > [Host Controller] 12:08:33,871 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.CR7 > [Host Controller] 12:08:34,035 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.CR8 > ^C12:08:56,655 INFO [org.jboss.as.process] (Shutdown thread) JBAS012016: Shutting down process controller > 12:08:56,664 INFO [org.jboss.as.process.Host Controller.status] (Shutdown thread) JBAS012018: Stopping process 'Host Controller' > [Host Controller] 12:08:56,703 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.1.0.CR1b "Flux Capacitor" stopped in 43ms > 12:08:56,753 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 130 > 12:08:56,763 INFO [org.jboss.as.process] (Shutdown thread) JBAS012015: All processes finished; exiting -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3350) Declared Beans and Enums can't be initialized using other declared Beans and/or Enums

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3350: --------------------------------------- Summary: Declared Beans and Enums can't be initialized using other declared Beans and/or Enums Key: JBRULES-3350 URL: https://issues.jboss.org/browse/JBRULES-3350 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Davide Sottara Assignee: Mark Proctor Field initialization is done using MVEL, which does not use the CompositeClassLoader, where declared classes are loaded. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3335) JPA after_completion Synchronization expects to be able to TransactionSynchronizationRegistry::putResource on a committed (i.e. inactive) transaction

by Tom Jenkinson (JIRA)

Tom Jenkinson created AS7-3335: ---------------------------------- Summary: JPA after_completion Synchronization expects to be able to TransactionSynchronizationRegistry::putResource on a committed (i.e. inactive) transaction Key: AS7-3335 URL: https://issues.jboss.org/browse/AS7-3335 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Reporter: Tom Jenkinson Assignee: Scott Marlow The JPA has registered an after_completion which incorrectly attempts to call putResource on the TransactionSynchronizationRegistry as the transaction is committed (therefore inactive). Offending code is in the jboss-as-jpa module: org.jboss.as.jpa.transaction.TransactionUtil.SessionSynchronization.afterCompletion getInstance().putEntityManagerInTransactionRegistry(scopedPuName, null); This is incorrect according to the specification as the transaction is now inactive: http://jcp.org/aboutJava/communityprocess/maintenance/jsr907/907ChangeLog... Note, this was allowed in version 4.16.0.Final (and likely below) of JBoss Transactions, though it is now being fixed - sorry! -- 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

12 years, 5 months

2
2
0 / 0

[JBoss JIRA] (AS7-3340) NPE during stop of service jboss.jacorb.poa-service.rootpoa

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3340?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-7947 to AS7-3340: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3340 (was: JBPAPP-7947) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.CR1b (was: EAP 6.0.0 DR 10) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > NPE during stop of service jboss.jacorb.poa-service.rootpoa > ----------------------------------------------------------- > > Key: AS7-3340 > URL: https://issues.jboss.org/browse/AS7-3340 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Priority: Critical > > There is randomly occured NPE when stopping EAP a bit quickly after it started. > {code} > 15:55:17,151 ERROR [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started (with errors) in 8066ms - Started 132 of 222 services (20 services failed or missing dependencies, 68 services are passive or on-demand) > ^C15:55:19,867 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/queue/test > 15:55:19,870 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011921: Stopping OSGi Framework > 15:55:19,876 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory > 15:55:19,878 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 15:55:19,888 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers > 15:55:19,897 INFO [jacorb.poa] POA IRPOA destroyed > 15:55:19,898 INFO [jacorb.poa] POA Naming destroyed > 15:55:19,906 WARN [org.jboss.msc.service.fail] MSC000004: Failure during stop of service jboss.jacorb.poa-service.rootpoa: java.lang.NullPointerException > at org.jacorb.poa.POA.destroy(Unknown Source) > at org.jboss.as.jacorb.service.CorbaPOAService.stop(CorbaPOAService.java:187) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] > 15:55:19,910 INFO [jacorb.orb] prepare ORB for shutdown... > {code} > As you can see above, I hit Ctrl-C in two seconds after start is done. NPE isn't occurred every time and I didn't see it anytime when EAP was running for a longer time (let say 10 seconds and more). -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3339) Provide a file listing of archive deployments via JDR

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-3339: ---------------------------------- Summary: Provide a file listing of archive deployments via JDR Key: AS7-3339 URL: https://issues.jboss.org/browse/AS7-3339 Project: Application Server 7 Issue Type: Enhancement Components: JDR Affects Versions: 7.1.0.CR1b Reporter: Jesse Jaggars Assignee: Jesse Jaggars JDR should capture a file listing of deployed archives such as .war and .ear files. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3327) remove ant dependency from AS7 (JPA)

by Scott Marlow (JIRA)

Scott Marlow created AS7-3327: --------------------------------- Summary: remove ant dependency from AS7 (JPA) Key: AS7-3327 URL: https://issues.jboss.org/browse/AS7-3327 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Final -- 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

12 years, 5 months

1
4
0 / 0

[JBoss JIRA] (AS7-3334) failed to resolve interface management

by Rafael Soares (JIRA)

Rafael Soares created AS7-3334: ---------------------------------- Summary: failed to resolve interface management Key: AS7-3334 URL: https://issues.jboss.org/browse/AS7-3334 Project: Application Server 7 Issue Type: Bug Components: Scripts Affects Versions: 7.1.0.CR1b Environment: RHEL 6.2 Open JDK 1.6_20 Reporter: Rafael Soares Assignee: Brian Stansberry When you try to start a domain using ./domain.sh -bmanagement=x.x.x.x as described in domain.sh help -b <value> JBAS012053: Set system property jboss.bind.address to the given value -b<interface>=<value> JBAS012054: Set system property jboss.bind.address.<interface> to the given value The domain fails with the following error 12:08:29,895 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6 12:08:30,183 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' [Host Controller] 12:08:30,804 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.0.CR6 [Host Controller] 12:08:31,705 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA [Host Controller] 12:08:31,819 INFO [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.1.0.CR1b "Flux Capacitor" starting [Host Controller] 12:08:32,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] [Host Controller] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] [Host Controller] [Host Controller] 12:08:32,934 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report [Host Controller] JBAS014777: Services which failed to start: service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management [Host Controller] [Host Controller] 12:08:32,954 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.CR7 [Host Controller] 12:08:33,871 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.CR7 [Host Controller] 12:08:34,035 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.CR8 ^C12:08:56,655 INFO [org.jboss.as.process] (Shutdown thread) JBAS012016: Shutting down process controller 12:08:56,664 INFO [org.jboss.as.process.Host Controller.status] (Shutdown thread) JBAS012018: Stopping process 'Host Controller' [Host Controller] 12:08:56,703 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.1.0.CR1b "Flux Capacitor" stopped in 43ms 12:08:56,753 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 130 12:08:56,763 INFO [org.jboss.as.process] (Shutdown thread) JBAS012015: All processes finished; exiting -- 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

12 years, 5 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 January 2012