[JBoss JIRA] Created: (AS7-1870) Error creating XA Datasource
by Heiko Braun (JIRA)
Error creating XA Datasource
----------------------------
Key: AS7-1870
URL: https://issues.jboss.org/browse/AS7-1870
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.0.Alpha1
When creating a XA DS through the console (standalone server), I get this:
{noformat}
11:25:15,297 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 8) Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("xa-data-source" => "mysql")
]): java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:100) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:251) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.as.connector.subsystems.datasources.DataSourceModelNodeUtil.xaFrom(DataSourceModelNodeUtil.java:208)
at org.jboss.as.connector.subsystems.datasources.XaDataSourceAdd.startConfigAndAddDependency(XaDataSourceAdd.java:64)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (AS7-1861) Detect Proxied HTTP requests within Digest authenticator.
by Darran Lofthouse (JIRA)
Detect Proxied HTTP requests within Digest authenticator.
---------------------------------------------------------
Key: AS7-1861
URL: https://issues.jboss.org/browse/AS7-1861
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Requests coming over a proxy may use a HTTP Keep-Alive connection between the server and the proxy, this connection could be shared by multiple clients so connection based caching should be disabled for proxy requests.
>From w3.org: -
{quote}
The Via general-header field MUST be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server on requests, and between the origin server and the client on responses.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Updated: (AS7-1858) Cannot start OSGi subsystem in domain mode
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-1858?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-1858:
--------------------------------
Component/s: OSGi
> Cannot start OSGi subsystem in domain mode
> ------------------------------------------
>
> Key: AS7-1858
> URL: https://issues.jboss.org/browse/AS7-1858
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Peter Penzov
> Assignee: Thomas Diesler
> Fix For: 7.1.0.Beta1
>
>
> {code}
> rcbandit@rcbandit-laptop:~/Desktop/jboss-as-7.0.1.Final/bin$ ./domain.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/rcbandit/Desktop/jboss-as-7.0.1.Final
> JAVA: 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
> =========================================================================
> 12:15:40,780 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
> 12:15:41,026 INFO [org.jboss.as.process.Host Controller.status] (main) Starting process 'Host Controller'
> [Host Controller] 12:15:41,588 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
> [Host Controller] 12:15:41,981 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
> [Host Controller] 12:15:42,532 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.Beta2
> [Host Controller] 12:15:42,590 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3
> [Host Controller] 12:15:42,651 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.Beta3
> [Host Controller] 12:15:44,055 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for native management service, all access will be unrestricted.
> [Host Controller] 12:15:44,062 INFO [org.jboss.as] (Controller Boot Thread) creating http management service using network interface (management) port (9990)
> [Host Controller] 12:15:44,064 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for http management service, all access will be unrestricted.
> [Host Controller] 12:15:44,198 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-one
> [Host Controller] 12:15:44,208 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999
> 12:15:44,277 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) Starting process 'Server:server-one'
> [Host Controller] 12:15:44,390 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-two
> 12:15:44,454 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) Starting process 'Server:server-two'
> [Server:server-two] 12:15:45,097 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
> [Server:server-one] 12:15:45,099 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
> [Server:server-two] 12:15:45,762 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
> [Server:server-one] 12:15:45,802 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
> [Server:server-two] 12:15:45,901 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
> [Server:server-one] 12:15:45,969 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
> [Server:server-two] 12:15:47,114 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
> [Server:server-two] 12:15:47,263 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8230
> [Server:server-one] 12:15:47,331 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: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
> [Server:server-one] 12:15:47,466 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
> [Server:server-two] 12:15:47,480 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
> [Server:server-two] 12:15:47,524 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12324: Start RecoveryActivators
> [Server:server-two] 12:15:47,578 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
> [Server:server-two] 12:15:47,620 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Tue, 30 Aug 2011 12:15:47
> [Server:server-two] 12:15:47,679 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
> [Server:server-two] 12:15:47,686 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32013: Starting transaction recovery manager
> [Server:server-two] 12:15:47,707 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
> [Server:server-two] 12:15:47,721 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2
> [Server:server-two] 12:15:47,730 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
> [Server:server-two] 12:15:47,797 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
> [Server:server-one] 12:15:47,799 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
> [Server:server-two] 12:15:47,889 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
> [Server:server-two] 12:15:47,898 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
> [Server:server-two] 12:15:47,950 INFO [org.jboss.as.naming] (MSC service thread 1-1) Starting Naming Service
> [Server:server-two] 12:15:47,986 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
> [Server:server-one] 12:15:47,892 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12324: Start RecoveryActivators
> [Server:server-one] 12:15:48,049 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
> [Server:server-one] 12:15:48,053 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Tue, 30 Aug 2011 12:15:48
> [Server:server-one] 12:15:48,108 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
> [Server:server-one] 12:15:48,111 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32013: Starting transaction recovery manager
> [Server:server-one] 12:15:48,151 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
> [Server:server-one] 12:15:48,204 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
> [Server:server-one] 12:15:48,231 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2
> [Server:server-one] 12:15:48,276 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
> [Server:server-one] 12:15:48,286 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
> [Server:server-one] 12:15:48,339 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
> [Server:server-one] 12:15:48,341 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
> [Server:server-one] 12:15:48,437 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-3) Starting remote JMX connector
> [Server:server-two] 12:15:48,610 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) JBossOSGi Framework Core - 1.0.0.CR8
> [Server:server-one] 12:15:48,666 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) JBossOSGi Framework Core - 1.0.0.CR8
> [Server:server-two] 12:15:48,746 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
> [Server:server-two] 12:15:48,782 INFO [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
> [Server:server-two] 12:15:48,938 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: system.bundle:0.0.0
> [Server:server-one] 12:15:49,178 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
> [Host Controller] 12:15:49,200 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-two] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@13d5f21]
> [Host Controller] 12:15:49,256 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-two
> [Server:server-one] 12:15:49,302 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
> [Server:server-two] 12:15:49,351 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
> [Server:server-one] 12:15:49,454 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: system.bundle:0.0.0
> [Server:server-two] 12:15:49,550 INFO [org.jboss.as.logging] (MSC service thread 1-1) Removing bootstrap log handlers
> [Host Controller] 12:15:49,648 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-one] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@9c2192]
> [Host Controller] 12:15:49,663 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-one
> [Server:server-one] 12:15:49,797 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
> [Server:server-two] 12:15:49,758 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]
> [Server:server-two] 12:15:49,837 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: javaee.api:0.0.0
> [Server:server-one] 12:15:49,952 INFO [org.jboss.as.logging] (MSC service thread 1-1) Removing bootstrap log handlers
> [Server:server-one] 12:15:50,428 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-osgi-jmx:1.0.10
> [Server:server-one] 12:15:50,554 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.metatype:1.0.4
> [Server:server-one] 12:15:50,659 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8
> [Server:server-one] 12:15:50,704 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.aries.util:0.3.0
> [Server:server-one] 12:15:50,711 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.log:1.0.0
> [Server:server-one] 12:15:50,741 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: javaee.api:0.0.0
> [Server:server-one] 12:15:50,855 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-two] 12:15:51,289 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.eventadmin:1.2.6
> [Server:server-one] 12:15:51,363 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-blueprint:1.0.2
> [Server:server-two] 12:15:51,512 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-osgi-xerces:2.9.1.SP7
> [Server:server-two] 12:15:51,597 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-two] 12:15:51,891 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.aries.jmx:0.3.0
> [Server:server-two] 12:15:51,930 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.webconsole:3.1.6.SP1
> [Server:server-two] 12:15:52,168 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.metatype:1.0.4
> [Server:server-two] 12:15:52,242 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jboss-osgi-logging:1.0.0
> [Server:server-one] 12:15:52,258 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.aries.jmx:0.3.0
> [Server:server-one] 12:15:52,285 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.eventadmin:1.2.6
> [Server:server-one] 12:15:52,316 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.jboss.logging:3.0.0
> [Server:server-two] 12:15:52,542 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
> [Server:server-two] 12:15:52,550 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.aries.util:0.3.0
> [Server:server-two] 12:15:52,617 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jbosgi-webconsole:1.0.6
> [Server:server-one] 12:15:52,823 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-http:1.0.3
> [Server:server-one] 12:15:52,891 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-webconsole:1.0.6
> [Server:server-two] 12:15:52,952 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-webapp:1.0.2
> [Server:server-two] 12:15:52,982 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8
> [Server:server-one] 12:15:53,039 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
> [Server:server-one] 12:15:53,052 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-logging:1.0.0
> [Server:server-two] 12:15:53,111 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-jmx:1.0.10
> [Server:server-two] 12:15:53,123 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: osgi.cmpn:4.2.0.200908310645
> [Server:server-two] 12:15:53,137 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.jboss.logging:3.0.0
> [Server:server-two] 12:15:53,238 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.log:1.0.0
> [Server:server-two] 12:15:53,318 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jbosgi-blueprint:1.0.2
> [Server:server-one] 12:15:53,322 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jbosgi-webapp:1.0.2
> [Server:server-one] 12:15:53,329 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 12:15:53,335 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-osgi-xerces:2.9.1.SP7
> [Server:server-two] 12:15:53,390 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-osgi-http:1.0.3
> [Server:server-two] 12:15:53,442 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-2) Starting bundles for start level: 1
> [Server:server-one] 12:15:53,673 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.cmpn:4.2.0.200908310645
> [Server:server-one] 12:15:53,684 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.webconsole:3.1.6.SP1
> [Server:server-two] 12:15:53,684 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: org.apache.felix.configadmin:1.2.8
> [Server:server-two] 12:15:53,749 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: org.apache.felix.log:1.0.0
> [Server:server-one] 12:15:53,752 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-1) Starting bundles for start level: 1
> [Server:server-two] 12:15:53,786 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: jboss-osgi-logging:1.0.0
> [Server:server-two] 12:15:53,789 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-2) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.1.Final]
> [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
> [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-two] Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.1.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.1.Final]] package; (package=org.jboss.as.osgi.service)
> [Server:server-two] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
> [Server:server-two] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
> [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
> [Server:server-two] ... 10 more
> [Server:server-two]
> [Server:server-two] 12:15:53,797 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-2) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-two]
> [Server:server-two] 12:15:53,802 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-2) OSGi Framework started
> [Server:server-two] 12:15:53,826 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 9218ms - Started 89 of 139 services (50 services are passive or on-demand)
> [Server:server-two] 12:15:53,827 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.1.Final]
> [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
> [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-two] Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.1.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.1.Final]] package; (package=org.jboss.as.osgi.service)
> [Server:server-two] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
> [Server:server-two] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
> [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
> [Server:server-two] ... 10 more
> [Server:server-two]
> [Server:server-two] 12:15:53,835 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
> [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-two]
> [Server:server-one] 12:15:53,891 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.felix.configadmin:1.2.8
> [Server:server-one] 12:15:53,925 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.felix.log:1.0.0
> [Server:server-one] 12:15:53,946 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: jboss-osgi-logging:1.0.0
> [Server:server-one] 12:15:53,950 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-1) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.1.Final]
> [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
> [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-one] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-one] Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.1.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.1.Final]] package; (package=org.jboss.as.osgi.service)
> [Server:server-one] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
> [Server:server-one] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
> [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
> [Server:server-one] ... 10 more
> [Server:server-one]
> [Server:server-one] 12:15:53,963 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-1) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-one] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-one]
> [Server:server-one] 12:15:53,968 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-1) OSGi Framework started
> [Server:server-one] 12:15:53,968 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.1.Final]
> [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
> [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-one] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-one] Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.1.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.1.Final]] package; (package=org.jboss.as.osgi.service)
> [Server:server-one] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
> [Server:server-one] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
> [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
> [Server:server-one] ... 10 more
> [Server:server-one]
> [Server:server-one] 12:15:53,978 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.1.Final
> [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
> [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
> [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257)
> [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
> [Server:server-one] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> [Server:server-one]
> [Server:server-one] 12:15:53,995 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 9386ms - Started 89 of 139 services (50 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
12 years, 9 months
[JBoss JIRA] Created: (AS7-1854) Better support for resource and operations descriptions
by Brian Stansberry (JIRA)
Better support for resource and operations descriptions
-------------------------------------------------------
Key: AS7-1854
URL: https://issues.jboss.org/browse/AS7-1854
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.0.Alpha1
It's too much work generating resource and operation descriptions. The AttributeDefinition class hierarchy introduced in 7.0.1 is helpful, but is poorly integrated with the ManagementResourceRegistration. And there is no good support for making use of the ManagementResourceRegistration data in creating resource descriptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Commented: (AS7-1485) Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/AS7-1485?page=com.atlassian.jira.plugin.s... ]
Marek Novotny commented on AS7-1485:
------------------------------------
This fix (patched JSF) also affects seam 2.3.x on AS7 like it does for AS5 :
{noformat}
20:29:23,454 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1004: Cannot instantiate component of type org.jboss.seam.ui.Link
20:29:23,461 SEVERE [facelets.viewhandler] (http--127.0.0.1-8080-1) 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.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:83) [jboss-seam.jar:]
at org.jboss.seam.web.IdentityFilter.doFilter(org.jboss.seam.web.IdentityFilter:40) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.web.MultipartFilter.doFilter(org.jboss.seam.web.MultipartFilter:90) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.web.ExceptionFilter.doFilter(org.jboss.seam.web.ExceptionFilter:64) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.web.RedirectFilter.doFilter(org.jboss.seam.web.RedirectFilter:45) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.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(org.jboss.seam.web.Ajax4jsfFilter:56) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.web.LoggingFilter.doFilter(org.jboss.seam.web.LoggingFilter:60) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.web.HotDeployFilter.doFilter(org.jboss.seam.web.HotDeployFilter:53) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(org.jboss.seam.servlet.SeamFilter:69) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamFilter.doFilter(org.jboss.seam.servlet.SeamFilter:158) [jboss-seam.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
{noformat}
> Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
> -------------------------------------------------------------------------
>
> Key: AS7-1485
> URL: https://issues.jboss.org/browse/AS7-1485
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: Open To Community
>
>
> Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost]. (main) Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
> java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory
> at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:702)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:674)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:648)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:156)
> at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:60)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389)
> at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:321)
> at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145)
> at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
> at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (JBRULES-3116) Performance Regression due to mvel ParserContext now set, resulting in CompositeClassLoader loads
by Fabian Lange (JIRA)
Performance Regression due to mvel ParserContext now set, resulting in CompositeClassLoader loads
-------------------------------------------------------------------------------------------------
Key: JBRULES-3116
URL: https://issues.jboss.org/browse/JBRULES-3116
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.2.0.Final
Reporter: Fabian Lange
Assignee: Mark Proctor
I observed this issue already with 5.1, but now had time to verify it with 5.2.
Initial compilation time has exploded with those versions.
I have with the same test cases with 5.2 this:
org.drools.util.CompositeClassLoader$CachingLoader.load taking a total of 42 seconds
With 5.0 (where this Caching was not yet implemented)
I had a total time of less than 5 seconds spend in the ClassLoading.
The reason for this took me a while to find, but now I do have it:
org.mvel2.compiler.AbstractParser.createPropertyToken
is invoking hasImports() and getImport() on the ParseContext if not null.
Those in turn are invoking org.mvel2.ParserConfiguration.checkForDynamicImport
which invokes org.drools.util.CompositeClassLoader.loadClass
This is invoked on my table for expressions like this: "age >= 16"
So the org.drools.util.CompositeClassLoader$CachingLoader.load
will look for a class called "age" and a class called "16". Because the class not exists null/false are returned from the callchain.
However neither the CachingLoader, nor the Map in AbstractParser will cache the negative result. Causing this to happen for each row in my decisiontable.
And in 5.0 the whole part of the callgraph is not there.
I figured out, that in 5.0 versions, the AbstractParser never had a parse context in createPropertyToken
This might be because of the inconsistent usage of
protected static ThreadLocal<ParserContext> parserContext;
protected ParserContext pCtx;
So where does us leave this?
A possible easy solution would be to add the "negative" lookups to the CachingLoader.
However I would like to have doublechecked if the change in Abstract Parser was intentional and is now working correctly. Thus invoking the checkDynamicImports a lot is correct. Is it really the case that the parser needs to check for each literal this dynamic import thing? it obviously didnt do before.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months