May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (AS7-666) deploy command in domain mode

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-666?page=com.atlassian.jira.plugin.sy... ] Alexey Loubyansky resolved AS7-666. ----------------------------------- Resolution: Done Merged. http://community.jboss.org/wiki/DeployAndUndeployWithTheCLI > deploy command in domain mode > ----------------------------- > > Key: AS7-666 > URL: https://issues.jboss.org/browse/AS7-666 > Project: Application Server 7 > Issue Type: Sub-task > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 7.0.0.CR1 > > > deploy command currently works only for standalone. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1857) Request on reconnection behavior

by Roger Hui (JIRA)

Request on reconnection behavior -------------------------------- Key: JBMESSAGING-1857 URL: https://issues.jboss.org/browse/JBMESSAGING-1857 Project: JBoss Messaging Issue Type: Feature Request Reporter: Roger Hui When a fail-over occurs (local or remote disaster recovery) the JMS clients connections must automatically re-connect to the active JMS server. Under no circumstances will the JMS clients need to re-create JMS objects (Connections, Sessions, Producers, and Consumers). Though exceptions can be thrown on edge conditions, the expectation is that operations on the JMS Producer and Consumer objects will blocked while the re-connection is complete. Once the connection enters "reconnect mode", it should block until the configured reconnect-retry-attempts are exhausted. The Exception listener should only invoked if re-connect has failed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-9312) JBossAsManagedContainer prematurely thinks the AS is started

by Brian Stansberry (JIRA)

JBossAsManagedContainer prematurely thinks the AS is started ------------------------------------------------------------ Key: JBAS-9312 URL: https://issues.jboss.org/browse/JBAS-9312 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: 7.0.0.Beta2 Reporter: Brian Stansberry Assignee: Shelly McGowan It starts and then loops until it can connect to the JMX server. That's premature. It should wait until it can connect to the management socket and query the management layer for server state. The server will need to add an operation to expose the state. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-680) Add BinderService dependency for infinispan hibernate 2LC

by Paul Ferraro (JIRA)

Add BinderService dependency for infinispan hibernate 2LC --------------------------------------------------------- Key: AS7-680 URL: https://issues.jboss.org/browse/AS7-680 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Affects Versions: 7.0.0.Beta3 Reporter: Paul Ferraro Assignee: Scott Marlow Fix For: 7.0.0.Beta4 To make sure the cache manager specified by the hibernate.cache.infinispan.cachemanager persistence.xml property is started, the deployer needs to specify a dependency on the appropriate BinderService. i.e. with ServiceName: org.jboss.as.naming.deployment.ContextNames.JAVA_CONTEXT_SERVICE_NAME.append(value) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Assigned: (AS7-351) Implement the HttpService ontop of JBossWeb

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry reassigned AS7-351: ------------------------------------ Assignee: (was: Emanuel Muckenhuber) Thomas, I'm unassigning Emanuel from this; he's not part of the core JBoss Web team and needs to focus on domain management tasks, not subsystem implementations. Please check with Remy to see what resources are available. > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: Web > Reporter: Thomas Diesler > Fix For: 7.0.0.CR1 > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9344) Update to console Beta8

by Heiko Braun (JIRA)

Update to console Beta8 ----------------------- Key: JBAS-9344 URL: https://issues.jboss.org/browse/JBAS-9344 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-681) Upgrade to JBossWS-CXF 4.0.0.Alpha5

by Alessio Soldano (JIRA)

Upgrade to JBossWS-CXF 4.0.0.Alpha5 ----------------------------------- Key: AS7-681 URL: https://issues.jboss.org/browse/AS7-681 Project: Application Server 7 Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.Beta4 Move to JBossWS-CXF 4.0.0.Alpha5, including its dependencies' updates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9278) JPA support for Clustering

by Scott Marlow (JIRA)

JPA support for Clustering -------------------------- Key: JBAS-9278 URL: https://issues.jboss.org/browse/JBAS-9278 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott Marlow -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
7
0 / 0

[JBoss JIRA] Created: (JBAS-9382) HA-JNDI processes requests before fully initialized

by Dennis Reed (JIRA)

HA-JNDI processes requests before fully initialized --------------------------------------------------- Key: JBAS-9382 URL: https://issues.jboss.org/browse/JBAS-9382 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.GA Reporter: Dennis Reed Assignee: Paul Ferraro HAJNDI starts processing requests before it has fully initialized itself. This can cause those requests to fail with: java.lang.NullPointerException at org.jboss.ha.jndi.impl.jbc.JBossCacheDistributedTreeManager.lookup(JBossCacheDistributedTreeManager.java:313) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ha.framework.server.HARMIServerImpl.invoke(HARMIServerImpl.java:209) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011