April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9319) jdbc deployment on domain fail

by Stefano Maestri (JIRA)

jdbc deployment on domain fail ------------------------------ Key: JBAS-9319 URL: https://issues.jboss.org/browse/JBAS-9319 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.Beta3 [org.jboss.as.server.deployment] (pool-2-thread-10) Content added at location /dati/project/RH/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/domain/content/47/95cc29338b5049e238941231b36b3946952991/content [Host Controller] 17:26:15,936 ERROR [org.jboss.as.controller] (pool-2-thread-26) operation ("deploy") failed - address: ([("deployment" => "mysql-connector-java-5.1.15.jar")]): java.lang.IllegalStateException: No handler for deploy at address [("deployment" => "mysql-connector-java-5.1.15.jar")] [Host Controller] at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:256) [Host Controller] at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:218) [Host Controller] at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:79) [Host Controller] at org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousOperationSupport.java:88) [Host Controller] at org.jboss.as.domain.controller.DomainModelImpl.executeForDomain(DomainModelImpl.java:348) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl$LocalDomainModelAdapter.execute(DomainControllerImpl.java:917) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl.executeOnHost(DomainControllerImpl.java:816) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl.access$000(DomainControllerImpl.java:111) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl$2.call(DomainControllerImpl.java:602) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl$2.call(DomainControllerImpl.java:596) [Host Controller] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_24] [Host Controller] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_24] [Host Controller] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24] [Host Controller] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [:1.6.0_24] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] [Host Controller] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [Host Controller] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JASSIST-140) javassist-3.14.0-GA - Problm in default initializer of class variables when they are deleted and created using removeField and addField, CtField.make

by Pawan Kumar (JIRA)

javassist-3.14.0-GA - Problm in default initializer of class variables when they are deleted and created using removeField and addField, CtField.make ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JASSIST-140 URL: https://issues.jboss.org/browse/JASSIST-140 Project: Javassist Issue Type: Bug Affects Versions: 3.14.0.GA Environment: jre 1.7 32bit on windows 7 64bit Reporter: Pawan Kumar Assignee: Shigeru Chiba The default initializer doesn't change in case of an already existing field is removed and then added with different initializer. If we have a class with some member variables with default initializer e.g. class A { public int x = 9; } And if we delete the memeber variable x using removeField and then add similar member variable with another default initializer but with same name say public int x = 2; CtField f = CtField.make("public int x= 2;", evalClass); evalClass.addField(f); I checked that the default value of x remains the same that is 9. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8680) More robust handling of previous versions of the configuration files

by Brian Stansberry (JIRA)

More robust handling of previous versions of the configuration files -------------------------------------------------------------------- Key: JBAS-8680 URL: https://jira.jboss.org/browse/JBAS-8680 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta1 Currently when an update is made to the configuration, we copy the config file to ".lastknowngood" and write a new version. We need something more sophisticated than that. 1) The original version of present on server start should be saved as .original. 2) We should keep a proper versioned history (standalone.xml.v1, standalone.xml.v2 etc) 3) Keep a standalone.xml.last which is the same as the current standalone.xml. This can be used to detect (via file timestamps) changes to standalone.xml made while the server is offline -- such change results in a new .original. 4) We need to create proper semantics for the ".lastknowngood" notion, or scrap it. Right now it's just the previous version of the file, which may or may not have been "good". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9163) "auto-start" not set for newly created sever-configs

by Heiko Braun (JIRA)

"auto-start" not set for newly created sever-configs ---------------------------------------------------- Key: JBAS-9163 URL: https://issues.jboss.org/browse/JBAS-9163 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Braun -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9322) Exception in FileSystemDeploymentService when ".isdeployed" file is created

by Wolfgang Knauf (JIRA)

Exception in FileSystemDeploymentService when ".isdeployed" file is created --------------------------------------------------------------------------- Key: JBAS-9322 URL: https://issues.jboss.org/browse/JBAS-9322 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Wolfgang Knauf Priority: Minor This happens in AS7 pulled from GIT on 2011-04-12. 1) Download this sample app: http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stat... 2) Rename to "Stateless.ear" 3) Deploy it to "standalone\deployments". This will result in a "Stateless.ear.failed" file. 4) Be nasty and add a file "Stateless.ear.isdeployed". Now you will see this exception in the server console: 21:13:13,828 ERROR [org.jboss.as.deployment] (DeplooymentScanner-threads - 2) Scan of C:\temp\jboss-7.0.0.Beta3-SNAPSHOT\standalone\deployments threw Exception: java.lang.NullPointerException at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentMarker.access$1000(FileSystemDeploymentService.java:1008) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scanDirectory(FileSystemDeploymentService.java:415) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:288) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$1.run(FileSystemDeploymentService.java:134) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Though this should not really when a user knows what to do, it is at least an "outside event" which should not "confuse" the deployment services. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBRULES-46) Prolog Style Query Based Backward Chaining

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/JBRULES-46?page=com.atlassian.jira.plugin... ] Mark Proctor commented on JBRULES-46: ------------------------------------- I'm not sure what backward chaining has to do with sequential mode? Drools already provides a sequential mode that works similar to other major vendors. > Prolog Style Query Based Backward Chaining > ------------------------------------------ > > Key: JBRULES-46 > URL: https://issues.jboss.org/browse/JBRULES-46 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > > Forward Chaining means that facts are asserted and propgated forward throughout the network, during forward propagation matching takes place which results in rules being fired - the rules are event based, in that they are fired in response to changed in the working memory. > Backward chaining is query based. Rules attempt to fire first but do not have the necessary matched facts, so facts are pulled in from an external source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9100) Flesh out management representation of sockets

by Brian Stansberry (JIRA)

Flesh out management representation of sockets ---------------------------------------------- Key: JBAS-9100 URL: https://issues.jboss.org/browse/JBAS-9100 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta3 Expose the runtime information from the SocketBindingManager service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9038) Remoting ConnectorAdd drops generic properties

by Brian Stansberry (JIRA)

Remoting ConnectorAdd drops generic properties ---------------------------------------------- Key: JBAS-9038 URL: https://issues.jboss.org/browse/JBAS-9038 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta3 The xsd supports a "properties" element and the parser parses it, but the add just discards the data. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-9325) Update OSGi Framework to use MSC services for plugins and bundles

by Thomas Diesler (JIRA)

Update OSGi Framework to use MSC services for plugins and bundles ----------------------------------------------------------------- Key: JBAS-9325 URL: https://issues.jboss.org/browse/JBAS-9325 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.Beta3 Major service based rearchitecture of the framework - Migrate all Plugins to Services - Migrate framework and user bundles to services There is a three layer approach to bundles/framework BundleState represents the internal state of a bundle. A client never holds a direct reference to a BundleState. Various BundleServices represent the lifecycle states of the bundle. BundleServices operate on BundleStates. The client is given a BundleProxy which interacts with the BundleService. The integration with AS7 is designed to be based on services. AS services may create dependencies on well defined Framework state services. Although UserBundles are currently also modelled as services, only the INSTALLED state is available as a service and may be used as a dependency. Later, we can create additional services that represent the RESOLVED, ACTIVE state of a bundle. Currently there may still be failures in the umbrella projects and some TCK regression. Hopefully I can address these over the next couple of days. This is a big step towards more parallel code paths with well defined dependency points and much better AS7 integration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9311) Error when an existing slave re-registers at the DC

by Heiko Rupp (JIRA)

Error when an existing slave re-registers at the DC --------------------------------------------------- Key: JBAS-9311 URL: https://issues.jboss.org/browse/JBAS-9311 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta2 Reporter: Heiko Rupp Start the DC, start a slave (pintsize). Slave connects. All ok. Shutdown slave, re-connect again [Host Controller] 20:50:24,691 INFO [org.jboss.domain] (pool-1-thread-5) register host pintsize [Host Controller] 20:50:24,692 ERROR [org.jboss.as.host.controller] (pool-1-thread-5) java.lang.IllegalArgumentException: There is already a host named 'pintsize' ^C on slave again , then restart slave [Host Controller] 21:05:54,764 INFO [org.jboss.domain] (pool-1-thread-26) register host pintsize [Host Controller] 21:05:54,764 ERROR [org.jboss.as.host.controller] (pool-1-thread-26) java.lang.IllegalArgumentException: There is already a host named 'pintsize' I don't know if this error is spurious or if it prevents some logic from happening. It should not be thrown when a known domain slave connects to the DC. Duplicate slaves should be prevented ( JBAS-9186 ) as they create issues. In RHQ we also have a hub-spoke architecture where the agents exchange a token with the server, that allows them to identify itself. Talk to mazz if you need more info. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
4
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 April 2011