[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 weeks, 4 days
[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on WFLY-156:
----------------------------------
error it results in is:
{noformat}
=================================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\wildfly-script-tests\target\wildfly-tmp\wildflyチ
JBOSS_BASE_DIR: C:\wildfly-script-tests\target\wildfly-tmp\wildflyチ\standalone
JAVA: C:\development\tools\jdk\jdk1.8.0_25\bin\java
JAVA_OPTS: -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.pkg
s=org.jboss.byteman
JBOSS_MODULEPATH: C:\wildfly-script-tests\target\wildfly-tmp\wildflyチ\modules
=================================================================================
java.exe : Error: Unable to access jarfile C:\wildfly-script-tests\target\wildfly-tmp\wildfly?\jboss-modules.jar
{noformat}
where last error is completly java's fault.
> 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
> Components: Server
> Environment: windows 2008 x64
> Reporter: Ales Kolenc
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: Awaiting Volunteers
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on WFLY-156:
----------------------------------
as part of WFCORE-25 we created a testsuite to make sure also this kind of paths are supported.
But, there are also bad news.
With fixes to our scripts, this still fails but not because of script problem, but because of java bug http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4488646 that doesn't support unicode values in system properties / starting jars with unicode chars in path.
> 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
> Components: Server
> Environment: windows 2008 x64
> Reporter: Ales Kolenc
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: Awaiting Volunteers
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (WFLY-4571) Merge the wildfly BOMs into a single BOM
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4571?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4571:
-----------------------------------
Also guys keep in mind that this is *wildfly* bom not arquillian/testing/quickstart bom.
not everyone uses arquillian & friends for testing.
and wildfly boms should focus on providing GAVs for what are user accessible APIs.
wildfly-arquillian adapter is not part of wildfly it is its add-on. as such should also be part of separate bom not a main one.
> Merge the wildfly BOMs into a single BOM
> ----------------------------------------
>
> Key: WFLY-4571
> URL: https://issues.jboss.org/browse/WFLY-4571
> Project: WildFly
> Issue Type: Enhancement
> Reporter: Paul Gier
> Assignee: Paul Gier
>
> We had some discussion on the jbossdeveloper list [1] about merging the current wildfly/eap boms into a single one instead of a separate bom for each use case.
> The only problematic BOM might be the hibernate3 bom because this includes dependencies which conflict with the hibernate 4 bom. So the hibernate 3 bom will probably need to remain separate.
> [1]http://lists.jboss.org/pipermail/jbossdeveloper/2015-April/000347.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months