January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-720) Generate JAR with test-sources in picketbox-ldap project

by Marek Posolda (JIRA)

Marek Posolda created SECURITY-720: -------------------------------------- Summary: Generate JAR with test-sources in picketbox-ldap project Key: SECURITY-720 URL: https://issues.jboss.org/browse/SECURITY-720 Project: PicketBox Issue Type: Enhancement Security Level: Public (Everyone can see) Components: PicketBox Environment: Affects version: picketbox-ldap 1.0.2.Final Fixed version: picketbox-ldap 1.0.3.Final Reporter: Marek Posolda Assignee: Anil Saldhana Priority: Minor It would be useful if JAR with test-sources will be attached under https://repository.jboss.org/nexus/content/groups/public/org/picketbox/pi... because currently test sources are not seen from dependent projects (like source of class org.picketbox.test.ldap.AbstractLDAPTest is not automatically seen from picketlink) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1317) BisocketClientInvoker waits for failed clients

by Doug Grove (JIRA)

[ https://issues.jboss.org/browse/JBREM-1317?page=com.atlassian.jira.plugin... ] Doug Grove commented on JBREM-1317: ----------------------------------- Hi Ron, The negative consequence is that the client blocks waiting for BisocketClientInvoker.createSocket() to timeout. > BisocketClientInvoker waits for failed clients > ---------------------------------------------- > > Key: JBREM-1317 > URL: https://issues.jboss.org/browse/JBREM-1317 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: callbacks > Affects Versions: 2.5.4.SP3 > Environment: JBoss EAP 5.1.2 > Reporter: Doug Grove > Assignee: Ron Sigal > Priority: Minor > > When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: > (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe > The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. > This is ignored, however, and the ode carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. > This results in the code waiting for the full duration of the configured timeout. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1317) BisocketClientInvoker waits for failed clients

by Doug Grove (JIRA)

[ https://issues.jboss.org/browse/JBREM-1317?page=com.atlassian.jira.plugin... ] Doug Grove updated JBREM-1317: ------------------------------ Description: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. This is ignored, however, and the code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. was: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. This is ignored, however, and the ode carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. > BisocketClientInvoker waits for failed clients > ---------------------------------------------- > > Key: JBREM-1317 > URL: https://issues.jboss.org/browse/JBREM-1317 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: callbacks > Affects Versions: 2.5.4.SP3 > Environment: JBoss EAP 5.1.2 > Reporter: Doug Grove > Assignee: Ron Sigal > Priority: Minor > > When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: > (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe > The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. > This is ignored, however, and the code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. > This results in the code waiting for the full duration of the configured timeout. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-1311) Provide the ability to view server logs through the web interface

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-1311?page=com.atlassian.jira.plugin.s... ] Harald Pehl reassigned AS7-1311: -------------------------------- Assignee: Harald Pehl (was: Heiko Braun) > Provide the ability to view server logs through the web interface > ----------------------------------------------------------------- > > Key: AS7-1311 > URL: https://issues.jboss.org/browse/AS7-1311 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 7.3.0.Alpha1 > > > Due to popular demand, we've raised the priority -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3715) when using BigDecimal Comparing to 0 only works for a certain number of time

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3715?page=com.atlassian.jira.plug... ] Mario Fusco resolved JBRULES-3715. ---------------------------------- Resolution: Done We decided that the mvel comparison semantic fits better the drools needs, so I made also the jitted constraints to behave accordingly. > when using BigDecimal Comparing to 0 only works for a certain number of time > ---------------------------------------------------------------------------- > > Key: JBRULES-3715 > URL: https://issues.jboss.org/browse/JBRULES-3715 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: All > Affects Versions: 5.4.0.Final > Environment: Jdk1.6; Drools 5.5 > Reporter: Nicolas Heron > Assignee: Mario Fusco > Attachments: BugBigDecimalDrools.zip > > > in a rule like this : > rule "Hello World" > dialect "mvel" > no-loop > when > $c : Contract( aValue == 0.0B ) > then > $c.setDone("OK"); > update($c); > end > when called a certain number of times, the comparaison does not work -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6332) Anonymize IP's used for analytics

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6332?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-6332. ------------------------------ Resolution: Done > Anonymize IP's used for analytics > --------------------------------- > > Key: AS7-6332 > URL: https://issues.jboss.org/browse/AS7-6332 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.3.0.Alpha1 > > > See http://support.google.com/analytics/bin/answer.py?hl=en&answer=2763052 -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6331) LoggingDeploymentUnitProcessor doesn't check for existing LOG_CONTEXT_KEY

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/AS7-6331?page=com.atlassian.jira.plugin.s... ] Ales Justin updated AS7-6331: ----------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/3879 > LoggingDeploymentUnitProcessor doesn't check for existing LOG_CONTEXT_KEY > ------------------------------------------------------------------------- > > Key: AS7-6331 > URL: https://issues.jboss.org/browse/AS7-6331 > Project: Application Server 7 > Issue Type: Feature Request > Components: Logging > Reporter: Ales Justin > Assignee: James Perkins > > There used to be a check for LOG_CONTEXT_KEY attachment, > which meant that LogContext was setup elsewhere. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6332) Anonymize IP's used for analytics

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6332?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6332: ----------------------------- Summary: Anonymize IP's used for analytics (was: Anonymize IP's use for analytics) > Anonymize IP's used for analytics > --------------------------------- > > Key: AS7-6332 > URL: https://issues.jboss.org/browse/AS7-6332 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.3.0.Alpha1 > > > See http://support.google.com/analytics/bin/answer.py?hl=en&answer=2763052 -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6332) Anonymize IP's use for analytics

by Heiko Braun (JIRA)

Heiko Braun created AS7-6332: -------------------------------- Summary: Anonymize IP's use for analytics Key: AS7-6332 URL: https://issues.jboss.org/browse/AS7-6332 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.3.0.Alpha1 See http://support.google.com/analytics/bin/answer.py?hl=en&answer=2763052 -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6331) LoggingDeploymentUnitProcessor doesn't check for existing LOG_CONTEXT_KEY

by Ales Justin (JIRA)

Ales Justin created AS7-6331: -------------------------------- Summary: LoggingDeploymentUnitProcessor doesn't check for existing LOG_CONTEXT_KEY Key: AS7-6331 URL: https://issues.jboss.org/browse/AS7-6331 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: Ales Justin Assignee: James Perkins There used to be a check for LOG_CONTEXT_KEY attachment, which meant that LogContext was setup elsewhere. -- 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

13 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 January 2013