May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9193) Tighten up the ServerEnvironment and HostControllerEnvironment contracts

by Brian Stansberry (JIRA)

Tighten up the ServerEnvironment and HostControllerEnvironment contracts ------------------------------------------------------------------------ Key: JBAS-9193 URL: https://issues.jboss.org/browse/JBAS-9193 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Right now the contract/usage of these classes is a bit of a mishmash. The idea was to store state that's read from Main(). But if there's anything in these that can be overridden from standalone.xml, either we should restrict access to that data or make sure that it has the correct value if a change is made via the management API. For example, the server name can come from standalone.xml if the 'name' attribute is set and for sure will come from the HostController in domain mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9113) Verify consistent handling of default values and resolved expressions when populating the domain model.

by Darran Lofthouse (JIRA)

Verify consistent handling of default values and resolved expressions when populating the domain model. ------------------------------------------------------------------------------------------------------- Key: JBAS-9113 URL: https://issues.jboss.org/browse/JBAS-9113 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Darran Lofthouse Fix For: 7.0.0.CR1 On reading the descriptors and executing the operations care needs to be taken to ensure either default values or resolved expressions are not transferred into the domain model - the consequence of this is that when the descriptors are re-written if these values are present in the model they are written as is loosing any default handling / expression resolving. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

7
7
0 / 0

[JBoss JIRA] Created: (JBAS-9098) Identify operations that require restart as part of the operation/attribute description

by Brian Stansberry (JIRA)

Identify operations that require restart as part of the operation/attribute description --------------------------------------------------------------------------------------- Key: JBAS-9098 URL: https://issues.jboss.org/browse/JBAS-9098 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 The implications of an operation with respect to whether invoking it will require a restart (or reload) to take effect should be part of the metadata description of the operation. This makes it possible for things like the console to advise users of the implications of their actions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2293) Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal

by Steve Ronderos (JIRA)

Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal ------------------------------------------------------------------------------------------------ Key: JBRULES-2293 URL: https://jira.jboss.org/jira/browse/JBRULES-2293 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Environment: Windows XP Java 5 Running in Oracle OC4J 10.1.3.2 Reporter: Steve Ronderos Assignee: Mark Proctor I encountered an issue today with my KnowledgeAgent removing resources from its RuleBase shortly after creating it. I have the ResourceChangeScanner running in my application. I tracked the issue back to the scan() method in ResourceChangeScannerImpl. It appears that the method is trying to identify resources that are no longer available and remove them from both the RuleBase and future scans. To do this it is checking lastModified on the resource and on a result of 0 removing the resource. The resources that I configured in my change-set definitely still exist, but due to URL handler implementation provided by my classloader, getLastModified always returns 0. (The resource I'm retrieving is coming from a jar that is in my application's classpath and the URL handler implementation is oracle.classloader.SharedCodeSourceURL) Full Email Group trail: http://www.nabble.com/Issue-with-ResourceChangeScanner-td25792358.html Michael recommends to never scan classpath resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
13
0 / 0

[JBoss JIRA] Created: (JBAS-9349) Server startup message on console goes missing if a deployment fails during server startup

by jaikiran pai (JIRA)

Server startup message on console goes missing if a deployment fails during server startup ------------------------------------------------------------------------------------------ Key: JBAS-9349 URL: https://issues.jboss.org/browse/JBAS-9349 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: AS7 upstream dated April 19 2011 Reporter: jaikiran pai Priority: Minor Fix For: 7.0.0.Beta3 I placed a failing deployment (picked the .ear from JBAS-9261) in the standalone/deployments folder and started the standalone server. The server picked up the deployment during startup and threw a service missing dependency error but *did not* show the usual server started in xxx ms message. Here's the entire log: {code} 14:02:49,540 INFO [org.jboss.as.deployment] (MSC service thread 1-4) Started FileSystemDeploymentService for directory /NotBackedUp/jpai/business/jboss/wc/jbossas/as7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/deployments 14:02:49,592 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector 14:02:49,633 INFO [org.jboss.as.server.deployment] (DeploymentScanner-threads - 1) Content added at location /NotBackedUp/jpai/business/jboss/wc/jbossas/as7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/data/content/43/79aa12f1960aa376bf9cb259576498616f5a7c/content 14:02:49,636 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.1.0.Beta2 14:02:49,712 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/Java/SunJava-6/jdk1.6.0_21/jre/lib/i386/server:/opt/Java/SunJava-6/jdk1.6.0_21/jre/lib/i386:/opt/Java/SunJava-6/jdk1.6.0_21/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib 14:02:49,879 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "Stateless.ear" 14:02:49,883 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) live server is starting.. 14:02:49,980 WARN [org.jboss.vfs] (MSC service thread 1-1) VFS was unable to set the URLStreamHandlerFactory. This will have unpredictable results 14:02:50,022 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080 14:02:50,114 INFO [org.jboss.as.connector] (MSC service thread 1-4) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.Beta5) 14:02:50,123 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "StatelessWeb.war" 14:02:50,132 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "StatelessEJB.jar" 14:02:50,134 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "StatelessClient.jar" 14:02:50,145 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry StatelessEJB.jar in "/content/Stateless.ear/StatelessClient.jar" does not point to a valid jar for a Class-Path reference. 14:02:50,221 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound JDBC Data-source [java:/H2DS] 14:02:50,435 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455 for CORE protocol 14:02:50,436 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE protocol 14:02:50,438 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.1.2.Final (Colmeia, 120) started 14:02:50,480 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL: Failed to process phase INSTALL of subdeployment "StatelessWeb.war" of deployment "Stateless.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: java.lang.IllegalArgumentException: Cannot find source service for lookup name: KeksLocal at org.jboss.as.ee.component.LookupBindingSourceDescription.<init>(LookupBindingSourceDescription.java:73) at org.jboss.as.ejb3.deployment.processors.EjbRefProcessor.processDescriptorEntries(EjbRefProcessor.java:99) at org.jboss.as.ee.component.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:57) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more 14:02:50,661 INFO [org.jboss.as.server] (MSC service thread 1-1) Service status report New missing/unsatisfied dependencies: service jboss.naming.context.java.module.Stateless.StatelessWeb (missing) Services which failed to start: service jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL: Failed to process phase INSTALL of subdeployment "StatelessWeb.war" of deployment "Stateless.ear" {code} Removing the failing deployment and restarting the server shows the server startup message: {code} 14:08:33,603 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" started in 3328ms - Started 99 of 123 services (24 services are passive or on-demand) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8985) Filter javax.api

by David Lloyd (JIRA)

Filter javax.api ---------------- Key: JBAS-8985 URL: https://issues.jboss.org/browse/JBAS-8985 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8984) Filter javaee.api

by David Lloyd (JIRA)

Filter javaee.api ----------------- Key: JBAS-8984 URL: https://issues.jboss.org/browse/JBAS-8984 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-9172) Allow simplified high-level stack configuration

by Paul Ferraro (JIRA)

Allow simplified high-level stack configuration ----------------------------------------------- Key: JBAS-9172 URL: https://issues.jboss.org/browse/JBAS-9172 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9171) Simplify definition of inherited jgroups stacks, e.g. udp-sync, udp-async, etc.

by Paul Ferraro (JIRA)

Simplify definition of inherited jgroups stacks, e.g. udp-sync, udp-async, etc. ------------------------------------------------------------------------------- Key: JBAS-9171 URL: https://issues.jboss.org/browse/JBAS-9171 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-809) Convert modules to use JBoss Logging and message bundles

by James Perkins (JIRA)

Convert modules to use JBoss Logging and message bundles -------------------------------------------------------- Key: AS7-809 URL: https://issues.jboss.org/browse/AS7-809 Project: Application Server 7 Issue Type: Task Reporter: James Perkins Assignee: James Perkins Fix For: 7.0.0.CR1 Use JBoss Logging 3 to create annotated interfaces for messages and logging. Also include the tooling to generate the concrete classes at compile time for the interfaces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
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 May 2011