[JBoss JIRA] (WFLY-145) User insn't properly informed that APR is used
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-145?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-145:
------------------------------
Fix Version/s: 8.0.0.Final
> User insn't properly informed that APR is used
> ----------------------------------------------
>
> Key: WFLY-145
> URL: https://issues.jboss.org/browse/WFLY-145
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Reporter: Rostislav Svoboda
> Assignee: Remy Maucherat
> Fix For: 8.0.0.CR1, 8.0.0.Final
>
>
> AS7 log doesn't show sufficient information that APR is used or not. Currently the only clue is that org.apache.coyote.http11.Http11AprProtocol is used instead of org.apache.coyote.http11.Http11Protocol. But it's implementation details and many users can miss that.
> Add log message to inform users if APR is used or not!
> For example APR affect https connector definition which must use openssl based keys and not keystore. And if users do not know APR is used they can be easily confused and blame AS7 as broken.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-399) mod_cluster subsystem: convert operation handlers to use OperationDefinition
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-399?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-399:
------------------------------
Fix Version/s: (was: 8.0.0.CR1)
> mod_cluster subsystem: convert operation handlers to use OperationDefinition
> ----------------------------------------------------------------------------
>
> Key: WFLY-399
> URL: https://issues.jboss.org/browse/WFLY-399
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 8.0.0.Final
>
>
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/LoadMetricDefinition.java:[59,59] warning: [deprecation] PropertiesAttributeDefinition(java.lang.String,java.lang.String,boolean) in org.jboss.as.controller.PropertiesAttributeDefinition has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[277,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[280,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[283,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[286,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterSubsystemAdd.java:[160,19] warning: [deprecation] setProxyList(java.lang.String) in org.jboss.modcluster.config.impl.ModClusterConfig has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterSubsystemAdd.java:[166,15] warning: [deprecation] setExcludedContexts(java.lang.String) in org.jboss.modcluster.config.impl.ModClusterConfig has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[100,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[103,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[106,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[110,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[113,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[117,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[120,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[124,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[127,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[130,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[134,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[137,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[140,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-143) Improve testing of Infinispan subsystem management features
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-143?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-143:
------------------------------
Fix Version/s: 8.0.0.Final
> Improve testing of Infinispan subsystem management features
> -----------------------------------------------------------
>
> Key: WFLY-143
> URL: https://issues.jboss.org/browse/WFLY-143
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering, Domain Management
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.CR1, 8.0.0.Final
>
>
> We current use InfinispanSubsystemTest to test the integrity of the Infinispan subsystem implementation.
> From the documentation:
> {noformat}
> Tests the ability to create a model from an xml configuration, marshal the model back to xml, re-read that marshalled model
> into a new model that matches the first one, execute a "describe" operation for the model, create yet another model
> from executing the results of that describe operation, and compare that model to first model.
> {noformat}
> Over and above these tests, we need more specific tests which cover use cases such as:
> - every attribute can be read/written as required and that the subsequent reload-required state is as expected
> - operation sequences such as add/remove/add, add/add give expected results for all resources in the subsystem
> - validating that the XML configuration specified gets translated into the desired Infinispan configuration
> - and many others
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-156:
------------------------------
Fix Version/s: 8.0.0.Final
> Unable to start jboss AS on windows if installed on path containig non-ascii characters
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-156
> URL: https://issues.jboss.org/browse/WFLY-156
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Environment: windows 2008 x64
> Reporter: Ales Kolenc
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: 8.0.0.CR1, 8.0.0.Final
>
>
> 1.) Install jboss into a folder containing non-ascii characters. (i.e. "C:\Testチ").
> 2.) run standalone.bat
> C:\Test?\jboss-as-7.1.1.Final\bin>set JAVA_HOME=C:\Program Files\Java\jre7
> C:\Test?\jboss-as-7.1.1.Final\bin>standalone.bat
> Calling "C:\Test?\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\Test?\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Error: Unable to access jarfile C:\Test?\jboss-as-7.1.1.Final\jboss-modules.jar
> Press any key to continue . . .
> C:\Test?\jboss-as-7.1.1.Final\bin>
> 3.) pleas note that: "Testチ" used in path -> 'チ' does not bellong to system locale code page. E.g.: char 'チ' is in CP 932, system locale code page used 437/1252,..
> 4.) i would also like to add that jboss does not start if it installed in "normal" folder, but JBOSS_CONFIG_DIR && JBOSS_LOG_DIR are set to folder with non-ascii characters:
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_LOG_DIR=c:\Test?
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_CONFIG_DIR=c:\Test?\configuration
> c:\test\jboss-as-7.1.1.Final\bin>dir %JBOSS_CONFIG_DIR%
> Volume in drive C has no label.
> Volume Serial Number is 2C2F-FA6F
> Directory of c:\Test?\configuration
> 01/04/2013 02:34 AM <DIR> .
> 01/04/2013 02:34 AM <DIR> ..
> 01/04/2013 01:42 AM 634 application-roles.properties
> 01/04/2013 01:42 AM 812 application-users.properties
> 01/04/2013 01:42 AM 2,042 logging.properties
> 01/04/2013 01:42 AM 836 mgmt-users.properties
> 01/04/2013 01:42 AM 27,024 standalone-full-ha.xml
> 01/04/2013 01:42 AM 20,794 standalone-full.xml
> 01/04/2013 01:42 AM 20,358 standalone-ha.xml
> 01/04/2013 01:42 AM 15,372 standalone.xml
> 01/04/2013 02:34 AM <DIR> standalone_xml_history
> 8 File(s) 87,872 bytes
> 3 Dir(s) 20,185,866,240 bytes free
> c:\test\jboss-as-7.1.1.Final\bin>standalone.bat -Djboss.server.config.dir=%JBOSS_CONFIG_DIR%
> Calling "c:\test\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: c:\test\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Unable to read the logging configuration from 'file:c:\Test?\configuration/logging.properties' (java.io.FileNotFoundException: c:\Test?\configuration\logging.properties (The filename, directory name, or volume label syntax is incorrect))
> java.lang.IllegalStateException: JBAS018701: Configuration directory does not exist: c:\Test?\configuration
> at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:371)
> at org.jboss.as.server.Main.determineEnvironment(Main.java:242)
> at org.jboss.as.server.Main.main(Main.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:260)
> at org.jboss.modules.Main.main(Main.java:291)
> Press any key to continue . . .
> c:\test\jboss-as-7.1.1.Final\bin>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-146) "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-146?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-146:
------------------------------
Fix Version/s: 8.0.0.Final
> "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-146
> URL: https://issues.jboss.org/browse/WFLY-146
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Radoslav Husar
> Fix For: 8.0.0.CR1, 8.0.0.Final
>
> Attachments: server.log
>
>
> Just saw this when I was closely looking through clustering testsuite logs.
> Affected version: master 8a6aac3c8eb6bc94b7eddfa4d090c9ac05c7e37b
> Seems like the connection pool closes earlier than the entiti manager shutdown?
> {code}15:09:34,473 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 54) HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-168]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at org.h2.message.DbException.get(DbException.java:135)
> at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1384)
> at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1359)
> at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:403)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:880)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1589)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:298)
> at org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:54)
> at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:367)
> at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:318)
> at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:314)
> at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1386)
> at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:194)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2.run(PersistenceUnitServiceImpl.java:124)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122){code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months