August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2978) Provide resource adapter metrics within console

by Heiko Braun (Created) (JIRA)

Provide resource adapter metrics within console ----------------------------------------------- Key: AS7-2978 URL: https://issues.jboss.org/browse/AS7-2978 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] (AS7-2462) Form errors in disclosure panels are not visible

by Heiko Braun (Created) (JIRA)

Form errors in disclosure panels are not visible ------------------------------------------------ Key: AS7-2462 URL: https://issues.jboss.org/browse/AS7-2462 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Priority: Critical Fix For: 7.1.0.CR1 It prevents the "save" operation, but the actual error is not visible. The disclosure panels should open up on demand -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5379) CLONE - Stale data received with SYNC on failover

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5379?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-5379: ------------------------------------- I ll try to pick this up for testing ASAP. > CLONE - Stale data received with SYNC on failover > ------------------------------------------------- > > Key: AS7-5379 > URL: https://issues.jboss.org/browse/AS7-5379 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Environment: affected 6.0.0 DR CI build > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Blocker > Labels: as713tracking > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > After verifying fix for JBPAPP-8937 I am instead seeing stale data received when using DIST SYNC replication. > REPL SYNC: On a failover after the application has been gracefully undeployed, a request can be getting data older by cca 40 seconds: > {noformat} > 2012/08/14 15:12:53:327 EDT [WARN ][Runner - 1295] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} > DIST SYNC: On server crash stale data can be received: > {noformat} > 2012/08/04 05:13:49:714 EDT [WARN ][Runner - 8] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5397) Support for expression in JGroups property element

by Jochen Cordes (JIRA)

Jochen Cordes created AS7-5397: ---------------------------------- Summary: Support for expression in JGroups property element Key: AS7-5397 URL: https://issues.jboss.org/browse/AS7-5397 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Server Affects Versions: 7.1.2.Final (EAP) Reporter: Jochen Cordes Assignee: Paul Ferraro When trying to set a property for the protocol TCPPING like this: <protocol type="TCPPING" socket-binding="jgroups-tcpping"> <property name=”initial_hosts”>${initial_hosts}</property> </protocol> we get a parser error on startup (${initial_hosts} is set in a property file we have specified with -P). Doing a :read-resource-attributes via CLI reveals that the property element doesn't support expressions. Are there plans to support this in the future or is there a specific reason why this isn't supported for this specific element? -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3608) Grouped accessors for nested objects

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3608: ------------------------------------ Summary: Grouped accessors for nested objects Key: JBRULES-3608 URL: https://issues.jboss.org/browse/JBRULES-3608 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Implement grouped accessors for nested objects as described here: https://community.jboss.org/wiki/Drools60#Grouped_Accessors_for_Nested_Ob... -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-4245) Implement mail inflow

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4245: -------------------------------- Summary: Implement mail inflow Key: AS7-4245 URL: https://issues.jboss.org/browse/AS7-4245 Project: Application Server 7 Issue Type: Feature Request Components: EE Affects Versions: 7.1.1.Final Reporter: Tomaz Cerar Assignee: Tomaz Cerar in previous versions of as we had mail-ra resource adapter that added functionality of handling inflow mails. there is implementation of this ironjacamar so the code could be reused. Resource addapter could/should be added the same way hornetq addapter is added in messaging subsystem. code and documentation from ironjacamer https://svn.jboss.org/repos/jbossas/projects/jboss-jca/trunk/adapters/src... http://docs.jboss.org/ironjacamar/userguide/1.1/en-US/html/introduction.h... -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8517) Add support for two phase bundle deployments

by Thomas Diesler (JIRA)

Add support for two phase bundle deployments -------------------------------------------- Key: JBAS-8517 URL: https://jira.jboss.org/browse/JBAS-8517 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Fix For: 7.0.0.M1 In one deploy cycle, bundles must first get installed and then started. It generally needs to be discussed how multiple phase deployments should be handled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
24
0 / 0

[JBoss JIRA] (AS7-5379) CLONE - Stale data received with SYNC on failover

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-5379?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-5379: ----------------------------------- Nevermind - I found the problem. > CLONE - Stale data received with SYNC on failover > ------------------------------------------------- > > Key: AS7-5379 > URL: https://issues.jboss.org/browse/AS7-5379 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Environment: affected 6.0.0 DR CI build > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Blocker > Labels: as713tracking > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > After verifying fix for JBPAPP-8937 I am instead seeing stale data received when using DIST SYNC replication. > REPL SYNC: On a failover after the application has been gracefully undeployed, a request can be getting data older by cca 40 seconds: > {noformat} > 2012/08/14 15:12:53:327 EDT [WARN ][Runner - 1295] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} > DIST SYNC: On server crash stale data can be received: > {noformat} > 2012/08/04 05:13:49:714 EDT [WARN ][Runner - 8] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5379) CLONE - Stale data received with SYNC on failover

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5379?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5379: --------------------------------------- How will you know? > CLONE - Stale data received with SYNC on failover > ------------------------------------------------- > > Key: AS7-5379 > URL: https://issues.jboss.org/browse/AS7-5379 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Environment: affected 6.0.0 DR CI build > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Blocker > Labels: as713tracking > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > After verifying fix for JBPAPP-8937 I am instead seeing stale data received when using DIST SYNC replication. > REPL SYNC: On a failover after the application has been gracefully undeployed, a request can be getting data older by cca 40 seconds: > {noformat} > 2012/08/14 15:12:53:327 EDT [WARN ][Runner - 1295] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} > DIST SYNC: On server crash stale data can be received: > {noformat} > 2012/08/04 05:13:49:714 EDT [WARN ][Runner - 8] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8 > at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) > at java.lang.Thread.run(Thread.java:662) > {noformat} -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5383) Update JSF based on Mojarra 2.1.12 and include patch for AS7-5373

by Stan Silvert (JIRA)

Stan Silvert created AS7-5383: --------------------------------- Summary: Update JSF based on Mojarra 2.1.12 and include patch for AS7-5373 Key: AS7-5383 URL: https://issues.jboss.org/browse/AS7-5383 Project: Application Server 7 Issue Type: Feature Request Components: JSF Affects Versions: 7.2.0.Alpha1 Reporter: Stan Silvert Assignee: Stan Silvert -- 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

13 years, 9 months

1
2
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 August 2012