April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-733) Expose tatletale management operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-733?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-733: ---------------------------------- Assignee: (was: Brian Stansberry) > Expose tatletale management operations > -------------------------------------- > > Key: WFLY-733 > URL: https://issues.jboss.org/browse/WFLY-733 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Fix For: Awaiting Volunteers > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-724) Provide the ability to invoke datasource operations on a server level (domain mode)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-724?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-724: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Provide the ability to invoke datasource operations on a server level (domain mode) > ----------------------------------------------------------------------------------- > > Key: WFLY-724 > URL: https://issues.jboss.org/browse/WFLY-724 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: No Release > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-734) Deadlock detection for Entity beans

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-734?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-734: ---------------------------------- Assignee: (was: Brian Stansberry) > Deadlock detection for Entity beans > ----------------------------------- > > Key: WFLY-734 > URL: https://issues.jboss.org/browse/WFLY-734 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: Windows 7 64 bit, Java 1.7.0 64 bit > Reporter: Christian Inzko > Fix For: Awaiting Volunteers > > > Deadlock detection with EJB 2.1 entity beans and pessimistic locking does not work. > We are migrating our application from Jboss 4.05 where we used entity beans. This jboss version was able to detect deadlock situations and throw a org.jboss.util.deadlock.ApplicationDeadlockException. This mechanism does no longer work - instead of that both transactions just hang until a transaction timeout is reached. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-723) Wildcard operations that span multiple processes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-723?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-723: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFLY-723 > URL: https://issues.jboss.org/browse/WFLY-723 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Labels: as7-ignored > Fix For: Awaiting Volunteers > > > Handle host=* and host=y,server=* type operations. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-701) Complete interface management from the console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-701?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-701: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Complete interface management from the console > ---------------------------------------------- > > Key: WFLY-701 > URL: https://issues.jboss.org/browse/WFLY-701 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: No Release > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-713) Ability to specify a delay between URL round-robin attempts in HA datasource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-713?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-713: ---------------------------------- Assignee: (was: Brian Stansberry) > Ability to specify a delay between URL round-robin attempts in HA datasource > ---------------------------------------------------------------------------- > > Key: WFLY-713 > URL: https://issues.jboss.org/browse/WFLY-713 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Daniel Marchese > Fix For: Awaiting Volunteers > > > We have a configuration with Oracle RAC One Node (1 active database, 1 standby database) and we are testing HA possibilities. > In one test, if we try to obtain a connection during the starting of the standby database after the active database crash, we get an ORA-12514 error because the standby instance is not ready to respond. > Besides the fact that Oracle should not return an error but wait for the standby database to be ready to respond, it would be interesting if it was possible to specify a delay between URL round-roubin attempts in the HA datasource (ex: url-retry-wait-millis). > This way, it would be possible to ask JBoss to wait before it tries the next URL in the list, giving the standby database the time to start. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-703) Valve configuration for EJB3 Webservice Endpoints

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-703?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-703: ---------------------------------- Assignee: (was: Brian Stansberry) > Valve configuration for EJB3 Webservice Endpoints > ------------------------------------------------- > > Key: WFLY-703 > URL: https://issues.jboss.org/browse/WFLY-703 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Reporter: Sebastian Maurer > Fix For: Awaiting Volunteers > > > Please add a way to configure valves for EJB3 endpoints packaged in an ejb-jar. > At the moment theres no option in any of the ejb deployment descriptors and of course it isn't possible to configure valves globally. > The only way to configure valves is in the jboss-web.xml which is only available for web archives. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-706) Change the default object store of JBoss transactions to use the hornetq object store

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-706?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-706: ---------------------------------- Assignee: (was: Brian Stansberry) > Change the default object store of JBoss transactions to use the hornetq object store > ------------------------------------------------------------------------------------- > > Key: WFLY-706 > URL: https://issues.jboss.org/browse/WFLY-706 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Tom Jenkinson > Fix For: Awaiting Volunteers > > > This would provide a performance boost, however it is not supportable until AS7-925 is complete as the object store cannot be manipulated on the filesystem to resolve heuristics, tooling is necessary. > PS Do not implement this feature without tooling or discussing with me, I will add this after tooling is added. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-687) .deployed sticks around

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-687?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-687: ---------------------------------- Assignee: (was: Brian Stansberry) > .deployed sticks around > ----------------------- > > Key: WFLY-687 > URL: https://issues.jboss.org/browse/WFLY-687 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Jesper Pedersen > Fix For: Awaiting Volunteers > > > Steps: > 1) cp successful.rar /path/to/jbossas7/standalone/deployments > 2) touch /path/to/jbossas7/standalone/deployments/successful.rar.dodeploy > .rar deploys with issues => .deployed > 3) Ctrl+C > The .deployed file is still there -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-677) AS fails to boot if hostname is not pingable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-677?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-677. ----------------------------------- Assignee: Brian Stansberry (was: Daniel Bevenius) Fix Version/s: 8.0.0.Alpha1 (was: Awaiting Volunteers) Resolution: Out of Date > AS fails to boot if hostname is not pingable > -------------------------------------------- > > Key: WFLY-677 > URL: https://issues.jboss.org/browse/WFLY-677 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: Awaiting Volunteers > Environment: Fedora 15 > Reporter: Misty Stanley-Jones > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > If hostname is not pingable (such as a made-up value like "cheezel" or a FQDN like "dhcp-111-bne.redhat.com"), the AS fails to start in domain mode, with a bindException. If I change the hostname to "localhost", the AS starts fine. > AS starts in standalone mode regardless. > {noformat} > [mstanley@dhcp-1-111 bin]$ ./domain.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/mstanley/git/jboss-as/build/target/jboss-7.0.0.Beta4-SNAPSHOT > JAVA: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64//bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman > ========================================================================= > 09:47:32,049 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.CR3 > Exception in thread "main" java.net.BindException: Cannot assign requested address > at java.net.PlainSocketImpl.socketBind(Native Method) > at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:353) > at java.net.ServerSocket.bind(ServerSocket.java:336) > at org.jboss.as.protocol.ProtocolServer.start(ProtocolServer.java:121) > at org.jboss.as.process.ProcessController.<init>(ProcessController.java:77) > at org.jboss.as.process.Main.start(Main.java:150) > at org.jboss.as.process.Main.main(Main.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:313) > {noformat} -- 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, 2 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 April 2013