September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-109) BBCode support for standalone version

by Ryszard Kozmik (JIRA)

BBCode support for standalone version ------------------------------------- Key: JBFORUMS-109 URL: http://jira.jboss.com/jira/browse/JBFORUMS-109 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.0.0 Alpha BBCode parser is now working only in portal environment. We need make it work as a standalone too. -- 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

1 month

4
5
0 / 0

[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 months, 3 weeks

2
3
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- 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

8 months, 2 weeks

3
10
0 / 0

[JBoss JIRA] (WFLY-5366) Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5366?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-5366: --------------------------------- Assignee: (was: Tomaz Cerar) > Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently. > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-5366 > URL: https://issues.jboss.org/browse/WFLY-5366 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 10.0.0.CR1 > Environment: Linux/Debian > Reporter: Thorsten Moeller > Fix For: Awaiting Volunteers > > > If the property `jboss.server.base.dir` and the environment variable `JBOSS_HOME` point to different directories (which we do, for instance, to start multiple JBoss/Wildfly instances, each with its own standalone directory) then the startup success detection mechanism implemented by the script <WILDFLY_HOME>/bin/init.d/wildfly-init-debian.sh wrongly reports startup as failed even if it actually succeeded. > Tracing it down, I found that since Wildly 10 the startup script searches for the file `<JBOSS_HOME>/standalone/tmp/startup-marker`. However, that file is actually written to `jboss.server.base.dir/tmp/startup-marker`; hence, it is not found if the directories are not the same. > I don't see a way how to fix this. As far as I can seen, it's not possible to access the jboss.server.base.dir property within the startup script. But the use case of having separate directories should be supported and it should work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5366) Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5366?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-5366: ------------------------------ Fix Version/s: Awaiting Volunteers > Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently. > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-5366 > URL: https://issues.jboss.org/browse/WFLY-5366 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 10.0.0.CR1 > Environment: Linux/Debian > Reporter: Thorsten Moeller > Fix For: Awaiting Volunteers > > > If the property `jboss.server.base.dir` and the environment variable `JBOSS_HOME` point to different directories (which we do, for instance, to start multiple JBoss/Wildfly instances, each with its own standalone directory) then the startup success detection mechanism implemented by the script <WILDFLY_HOME>/bin/init.d/wildfly-init-debian.sh wrongly reports startup as failed even if it actually succeeded. > Tracing it down, I found that since Wildly 10 the startup script searches for the file `<JBOSS_HOME>/standalone/tmp/startup-marker`. However, that file is actually written to `jboss.server.base.dir/tmp/startup-marker`; hence, it is not found if the directories are not the same. > I don't see a way how to fix this. As far as I can seen, it's not possible to access the jboss.server.base.dir property within the startup script. But the use case of having separate directories should be supported and it should work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5415) wildfly-init-debian.sh overwrites previous log

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5415?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-5415. ----------------------------- Resolution: Rejected Configure logging in logging subsystem to log to server.log only and not also to console. This way you wont lose anything and it will also perform better. > wildfly-init-debian.sh overwrites previous log > ---------------------------------------------- > > Key: WFLY-5415 > URL: https://issues.jboss.org/browse/WFLY-5415 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 9.0.1.Final > Environment: Wildfly 9.0.1 Final on Ubuntu 14.04 LTS running the Zanata (zanata.org) translations platform. > Reporter: Elizabeth K. Joseph > Assignee: Tomaz Cerar > Priority: Minor > > We had to restart Wildfly on our Ubuntu 14.04 LTS server due to some issues with the application on top of it, and during the restart the init script wiped out our old logs and replaced them with the new logs, leaving us with none of the debugging information needed to track down our problem. > It looks like this line is to blame in bin/init.d/wildfly-init-debian.sh: > cat /dev/null > "$JBOSS_CONSOLE_LOG" > Currently using wildfly-9.0.1.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-78) Requirement to ser JBOSS_HOME as soon as commands are executed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-78?page=com.atlassian.jira.plugin.... ] James Perkins reassigned JBASMP-78: ----------------------------------- Assignee: (was: James Perkins) > Requirement to ser JBOSS_HOME as soon as commands are executed > -------------------------------------------------------------- > > Key: JBASMP-78 > URL: https://issues.jboss.org/browse/JBASMP-78 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: common > Affects Versions: 7.7.Final > Environment: This at least happens on Windows Machines, Haven't tried on Linux/Unix based machines. > Reporter: Christofer Dutz > > If I run jboss-as:run without any configuration and no JBoss installed, the plugin correctly downloads JBoss and unpacks it in my ear projects target directory. It also correctly starts the server and tries to deploy the application. Unfortunately I need to do some configuration first, so I added some "before-deployment" commands. Now the build fails with a message, that the JBOSS_HOME variable isn't set. As soon as I set it to the "target/jboss-as-run/jboss-as-7.1.1.Final" it is able to continue. Would be good however if the plugin could already ensure the variable from being set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-666) Log file validation should check if a path is absolute if a relative-to is defined

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-666?page=com.atlassian.jira.plugin... ] James Perkins reopened WFCORE-666: ---------------------------------- Wrong issue closed. > Log file validation should check if a path is absolute if a relative-to is defined > ---------------------------------------------------------------------------------- > > Key: WFCORE-666 > URL: https://issues.jboss.org/browse/WFCORE-666 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The {{path}} attribute on a file should be validated to not be absolute if a {{relative-to}} attribute was also defined. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-478) log4j ConsoleAppender won't display messages with per-deployment logging

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-478?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-478. -------------------------------- Resolution: Out of Date This was fixed at some point likely with the of org.jboss.logmanager:log4j-jboss-logmanager:1.1.2.Final. > log4j ConsoleAppender won't display messages with per-deployment logging > ------------------------------------------------------------------------ > > Key: WFCORE-478 > URL: https://issues.jboss.org/browse/WFCORE-478 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Add the following log4j.properties file to a deployment and try to log. > {code} > # Root logger option > log4j.rootLogger=INFO, stdout > # Direct log messages to stdout > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > log4j.appender.stdout.Target=System.out > log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-666) Log file validation should check if a path is absolute if a relative-to is defined

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-666?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-666. -------------------------------- Resolution: Out of Date This was fixed at some point likely with the of org.jboss.logmanager:log4j-jboss-logmanager:1.1.2.Final. > Log file validation should check if a path is absolute if a relative-to is defined > ---------------------------------------------------------------------------------- > > Key: WFCORE-666 > URL: https://issues.jboss.org/browse/WFCORE-666 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The {{path}} attribute on a file should be validated to not be absolute if a {{relative-to}} attribute was also defined. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2015