[JBoss JIRA] Created: (AS7-1267) Can't set "append" attribute on file handlers
by Stan Silvert (JIRA)
Can't set "append" attribute on file handlers
---------------------------------------------
Key: AS7-1267
URL: https://issues.jboss.org/browse/AS7-1267
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: David Lloyd
I can't tell what is really happening here. It seems to parse the "append" attribute OK, but it doesn't show up in the CLI. I've also set it programmatically in the console code, but I never get a value back for it.
<periodic-rotating-file-handler name="FILE">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="true"/>
</periodic-rotating-file-handler>
[standalone@localhost:9999 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-resource
{
"outcome" => "success",
"result" => {
"autoflush" => true,
"encoding" => undefined,
"file" => {
"path" => "server.log",
"relative-to" => "jboss.server.log.dir"
},
"formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n",
"level" => "INFO",
"suffix" => ".yyyy-MM-dd"
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-885) Not all operations in logging subsystem have an operation-name attribute and reply-, request-properties
by Heiko Rupp (JIRA)
Not all operations in logging subsystem have an operation-name attribute and reply-,request-properties
------------------------------------------------------------------------------------------------------
Key: AS7-885
URL: https://issues.jboss.org/browse/AS7-885
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Rupp
[standalone@localhost:9999 console-handler=CONSOLE] :read-resource-description
...
"remove" => {"description" => "Remove an existing logging handler."},
"disable" => {"description" => "Disable a logging handler."},
"enable" => {"description" => "Enable a logging handler."},
While the name can be deduced from the key, it is present in many(all?) other subsystem operations and should be available here as well.
The operations listed also have no request-properties and reply-properties sections
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1983) Logger handler level should be required
by Tristan Tarrant (JIRA)
Logger handler level should be required
---------------------------------------
Key: AS7-1983
URL: https://issues.jboss.org/browse/AS7-1983
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Tristan Tarrant
Assignee: James Perkins
Priority: Minor
I believe there is a copy/paste mistake in LoggingSubsystemProviders.java in the following code:
private static void addCommonLoggerRequestProperties(final ModelNode modelNode, final ResourceBundle bundle) {
modelNode.get(REQUEST_PROPERTIES, LEVEL, TYPE).set(ModelType.STRING);
modelNode.get(REQUEST_PROPERTIES, LEVEL, DESCRIPTION).set(bundle.getString("handler.level"));
modelNode.get(REQUEST_PROPERTIES, LEVEL, REQUIRED).set(true);
modelNode.get(REQUEST_PROPERTIES, FILTER, TYPE).set(ModelType.STRING);
modelNode.get(REQUEST_PROPERTIES, FILTER, DESCRIPTION).set(bundle.getString("handler.filter"));
modelNode.get(REQUEST_PROPERTIES, LEVEL, REQUIRED).set(false);
modelNode.get(REQUEST_PROPERTIES, HANDLERS, TYPE).set(ModelType.LIST);
modelNode.get(REQUEST_PROPERTIES, HANDLERS, VALUE_TYPE).set(ModelType.STRING);
modelNode.get(REQUEST_PROPERTIES, HANDLERS, DESCRIPTION).set(bundle.getString("logger.handlers"));
modelNode.get(REQUEST_PROPERTIES, HANDLERS, REQUIRED).set(false);
}
the LEVEL property's REQUIRED flag is reset to false, instead of setting the FILTER's flag.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1792) Fix the Logging description providers for the improved validation in jboss-as-subsystem-test
by Kabir Khan (JIRA)
Fix the Logging description providers for the improved validation in jboss-as-subsystem-test
--------------------------------------------------------------------------------------------
Key: AS7-1792
URL: https://issues.jboss.org/browse/AS7-1792
Project: Application Server 7
Issue Type: Feature Request
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Kabir Khan
Assignee: James Perkins
I added a test called LoggingSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days.
To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows:
{code}
@Override
protected ValidationConfiguration getModelValidationConfiguration() {
return null;
}
@Override
protected boolean isValidateOperations() {
//TODO fix providers https://issues.jboss.org/browse/AS7-1789
return false;
}
{code}
Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples.
The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes
The above is standard text as I'm going through and creating tests. The test has been @Ignored due to a further failure once validation passes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] (AS7-2025) JSF 1.2 slot is broken (for RichFaces 3.x support)
by Karel Piwko (Created) (JIRA)
JSF 1.2 slot is broken (for RichFaces 3.x support)
--------------------------------------------------
Key: AS7-2025
URL: https://issues.jboss.org/browse/AS7-2025
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.1.0.Alpha1
Environment: 7.1.0.Alpha2 SNAPSHOT, 9a15276c2e163c196807cce5e811fd1fa672bf89
Reporter: Karel Piwko
Assignee: Stan Silvert
Priority: Critical
Following is a regression from AS 7.0.1.Final. Currently, applications which are using JSF 1.2 cannot bind any NamedObject inside of the application scope. Here's the stacktrace:
{code}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/kpiwko/devel/jbossas/jboss-as/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT
JAVA: /opt/jdk1.6.0_27/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
13:43:29,992 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA
13:43:30,184 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
13:43:30,242 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" starting
13:43:30,950 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
13:43:31,005 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
13:43:31,007 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
13:43:31,022 INFO [org.jboss.as.logging] JBAS011501: Removing bootstrap log handlers
13:43:31,047 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
13:43:31,084 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
13:43:31,156 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem
13:43:31,159 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
13:43:31,164 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem
13:43:31,177 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
13:43:31,178 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
13:43:31,201 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
13:43:31,214 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
13:43:31,384 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/jdk1.6.0_27/jre/lib/amd64/server:/opt/jdk1.6.0_27/jre/lib/amd64:/opt/jdk1.6.0_27/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
13:43:31,412 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
13:43:31,417 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
13:43:31,419 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999
13:43:31,587 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
13:43:31,662 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.4.Final)
13:43:31,702 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
13:43:31,703 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/DefaultDS]
13:43:32,353 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory /home/kpiwko/devel/jbossas/jboss-as/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/standalone/deployments
13:43:32,376 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" started in 2573ms - Started 104 of 160 services (56 services are passive or on-demand)
13:43:32,404 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "jboss-seam-jpa.war"
13:43:33,914 INFO [org.jboss.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for bookingDatabase
13:43:34,486 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "jboss-seam-jpa.war" are as follows:
java:global/jboss-seam-jpa/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:app/jboss-seam-jpa/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:global/jboss-seam-jpa/EjbSynchronizations
java:app/jboss-seam-jpa/EjbSynchronizations
java:module/EjbSynchronizations
13:43:34,486 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "jboss-seam-jpa.war" are as follows:
java:global/jboss-seam-jpa/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:app/jboss-seam-jpa/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:global/jboss-seam-jpa/TimerServiceDispatcher
java:app/jboss-seam-jpa/TimerServiceDispatcher
java:module/TimerServiceDispatcher
13:43:35,673 INFO [org.jboss.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-seam-jpa.war#bookingDatabase'
13:43:35,879 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.0.CR2}
13:43:35,893 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH00412:Hibernate Core {4.0.0.CR2}
13:43:35,894 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH00206:hibernate.properties not found
13:43:35,896 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH00021:Bytecode provider name : javassist
13:43:35,925 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH00204:Processing PersistenceUnitInfo [
name: bookingDatabase
...]
13:43:36,078 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-1) HHH00130:Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
13:43:36,268 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-1) HHH00400:Using dialect: org.hibernate.dialect.H2Dialect
13:43:36,272 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-1) HHH00431:Unable to determine H2 database version, certain features may not work
13:43:36,275 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-1) HHH00423:Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
13:43:36,281 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-1) HHH00268:Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
13:43:36,284 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-1) HHH00397:Using ASTQueryTranslatorFactory
13:43:36,328 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-1) Hibernate Validator 4.2.0.Final
13:43:36,564 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH00227:Running hbm2ddl schema export
13:43:36,569 INFO [stdout] (MSC service thread 1-1) Hibernate: alter table Booking drop constraint FK6713A039A372CD94
13:43:36,572 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH00389:Unsuccessful: alter table Booking drop constraint FK6713A039A372CD94
13:43:36,573 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) Table "BOOKING" not found; SQL statement:
alter table Booking drop constraint FK6713A039A372CD94 [42102-145]
13:43:36,573 INFO [stdout] (MSC service thread 1-1) Hibernate: alter table Booking drop constraint FK6713A0391A0D32FB
13:43:36,573 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH00389:Unsuccessful: alter table Booking drop constraint FK6713A0391A0D32FB
13:43:36,573 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) Table "BOOKING" not found; SQL statement:
alter table Booking drop constraint FK6713A0391A0D32FB [42102-145]
13:43:36,573 INFO [stdout] (MSC service thread 1-1) Hibernate: drop table Booking if exists
13:43:36,574 INFO [stdout] (MSC service thread 1-1) Hibernate: drop table Customer if exists
13:43:36,574 INFO [stdout] (MSC service thread 1-1) Hibernate: drop table Hotel if exists
13:43:36,574 INFO [stdout] (MSC service thread 1-1) Hibernate: drop table REVINFO if exists
13:43:36,574 INFO [stdout] (MSC service thread 1-1) Hibernate: drop sequence hibernate_sequence
13:43:36,574 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH00389:Unsuccessful: drop sequence hibernate_sequence
13:43:36,575 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
drop sequence hibernate_sequence [90036-145]
13:43:36,575 INFO [stdout] (MSC service thread 1-1) Hibernate: create table Booking (id bigint not null, beds integer not null, checkinDate date, checkoutDate date, creditCard varchar(255), creditCardExpiryMonth integer not null, creditCardExpiryYear integer not null, creditCardName varchar(255), smoking boolean not null, hotel_id bigint, user_username varchar(255), primary key (id))
13:43:36,578 INFO [stdout] (MSC service thread 1-1) Hibernate: create table Customer (username varchar(255) not null, name varchar(255), password varchar(255), primary key (username))
13:43:36,579 INFO [stdout] (MSC service thread 1-1) Hibernate: create table Hotel (id bigint not null, address varchar(255), city varchar(255), country varchar(255), name varchar(255), price decimal(6,2), state varchar(255), zip varchar(255), primary key (id))
13:43:36,579 INFO [stdout] (MSC service thread 1-1) Hibernate: create table REVINFO (REV integer generated by default as identity, REVTSTMP bigint, primary key (REV))
13:43:36,582 INFO [stdout] (MSC service thread 1-1) Hibernate: alter table Booking add constraint FK6713A039A372CD94 foreign key (hotel_id) references Hotel
13:43:36,590 INFO [stdout] (MSC service thread 1-1) Hibernate: alter table Booking add constraint FK6713A0391A0D32FB foreign key (user_username) references Customer
13:43:36,592 INFO [stdout] (MSC service thread 1-1) Hibernate: create sequence hibernate_sequence start with 1 increment by 1
13:43:36,598 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH00230:Schema export complete
13:43:36,599 WARN [org.hibernate.internal.SessionFactoryImpl] (MSC service thread 1-1) HHH00008:JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession()
13:43:36,687 ERROR [stderr] (MSC service thread 1-1) log4j:WARN No appenders could be found for logger (javax.servlet.ServletContextListener).
13:43:36,688 ERROR [stderr] (MSC service thread 1-1) log4j:WARN Please initialize the log4j system properly.
13:43:38,012 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Initializing Mojarra (1.2_15-20110809-SNAPSHOT) for context '/jboss-seam-jpa'
13:43:38,375 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-1) JSF1051: Service entry 'org.jboss.as.web.deployment.jsf.JsfInjectionProvider' does not extend DiscoverableInjectionProvider. Entry will be ignored.
13:43:38,376 INFO [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-1) JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
13:43:38,526 INFO [org.ajax4jsf.cache.CacheManager] (MSC service thread 1-1) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
13:43:38,526 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-1) Creating LRUMap cache instance using parameters: {facelets.DEVELOPMENT=true, javax.faces.DEFAULT_SUFFIX=.xhtml}
13:43:38,527 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-1) Creating LRUMap cache instance of default capacity
13:43:38,541 INFO [org.ajax4jsf.cache.CacheManager] (MSC service thread 1-1) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
13:43:38,541 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-1) Creating LRUMap cache instance using parameters: {facelets.DEVELOPMENT=true, javax.faces.DEFAULT_SUFFIX=.xhtml}
13:43:38,541 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (MSC service thread 1-1) Creating LRUMap cache instance of default capacity
13:43:38,555 INFO [org.jboss.web] (MSC service thread 1-1) registering web context: /jboss-seam-jpa
13:43:38,644 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "jboss-seam-jpa.war"
13:43:44,409 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jstl-fn.taglib.xml
13:43:44,417 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jstl-core.taglib.xml
13:43:44,426 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-ui.taglib.xml
13:43:44,435 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-core.taglib.xml
13:43:44,439 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/jsf-html.taglib.xml
13:43:44,445 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/jboss-seam-ui-2.2.2.Final.jar/META-INF/s.taglib.xml
13:43:44,447 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/jsp.taglib.xml
13:43:44,454 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/ajax4jsf.taglib.xml
13:43:44,475 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/richfaces.taglib.xml
13:43:44,480 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/a4j.taglib.xml
13:43:44,488 INFO [facelets.compiler] (http--127.0.0.1-8080-2) Added Library from: vfs:/content/jboss-seam-jpa.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/rich.taglib.xml
13:43:44,623 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-2) JSF1004: Cannot instantiate component of type org.jboss.seam.ui.Link
13:43:44,645 SEVERE [facelets.viewhandler] (http--127.0.0.1-8080-2) Error Rendering View[/home.xhtml]: javax.faces.FacesException: Expression Error: Named Object: org.jboss.seam.ui.Link not found.
at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:571) [jsf-impl-1.2_15-jbossorg-1.jar:1.2_15.jbossorg-1-20110810-SNAPSHOT]
at com.sun.facelets.tag.jsf.ComponentHandler.createComponent(ComponentHandler.java:243) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:139) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567) [jsf-facelets-1.1.15.B1.jar:]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) [jsf-impl-1.2_15-jbossorg-1.jar:1.2_15.jbossorg-1-20110810-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) [jsf-impl-1.2_15-jbossorg-1.jar:1.2_15.jbossorg-1-20110810-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-1.2_15-jbossorg-1.jar:1.2_15.jbossorg-1-20110810-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) [jsf-api-1.2_15-jbossorg-1.jar:1.2_15.jbossorg-1-20110810-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) [richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) [richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) [richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) [richfaces-impl-3.3.3.Final.jar:]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.2.2.Final.jar:]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam-2.2.2.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:144) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:670) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
{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
14 years, 9 months
[JBoss JIRA] (JBRULES-3244) runExamples.bat throws NoClassDefFoundError on ResourceConfiguration
by Geoffrey De Smet (Created) (JIRA)
runExamples.bat throws NoClassDefFoundError on ResourceConfiguration
--------------------------------------------------------------------
Key: JBRULES-3244
URL: https://issues.jboss.org/browse/JBRULES-3244
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.0.CR1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
"
What I did was to extract the folder examples/sources and import it as an existing maven project. When I did, the rules were full of messages, such as : cannot resolve type, mismatched token, etc. Besides of that, when tried to run any of the samples by running runExamples.bat and clicking on an example listitem I was getting this message:
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: org/drool
s/builder/ResourceConfiguration
at org.drools.examples.DroolsExamplesApp$12.actionPerformed(DroolsExampl
esApp.java:126)
I used Eclipse Indigo and m2eclipse to import.
The package I used was 5.3.0.CR1
"
--
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
14 years, 9 months
[JBoss JIRA] (AS7-2150) use-ccm flag gets over written after server started
by Andrig Miller (Created) (JIRA)
use-ccm flag gets over written after server started
---------------------------------------------------
Key: AS7-2150
URL: https://issues.jboss.org/browse/AS7-2150
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.0.Alpha1
Reporter: Andrig Miller
Assignee: Jesper Pedersen
Fix For: 7.1.0.Beta1
In doing some performance testing, I wanted to remove the Cached Connection Manager (CCM) from the data source I configured. Since you cannot edit this attribute through the console (as of yet), I hand edited the XML file to add use-ccm="false" as follows:
<datasource jndi-name="java:/MySqlDS" pool-name="MySqlDS" enabled="true" jta="true" use-java-context="true" use-ccm="false">
After starting the server, I noticed that the use-ccm value disappears when the server is running, and the above line looks like this:
<datasource jndi-name="java:/MySqlDS" pool-name="MySqlDS" enabled="true" jta="true" use-java-context="true">
After shutting down the server, I noticed that the use-ccm attribute was back, but was now true again, as follows:
<datasource jndi-name="java:/MySqlDS" pool-name="MySqlDS" enabled="true" jta="true" use-java-context="true" use-ccm="true">
So, this is obviously broken. I'm not even sure if when I set it to false, that it actually is running that way. At this point, since its missing from the configuration after startup, and is written back as true, I believe its probably running with a value of true as well, which is obviously not what I want.
--
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
14 years, 9 months