January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-36) Datasource deployer

by Jesper Pedersen (JIRA)

Datasource deployer ------------------- Key: JBJCA-36 URL: https://jira.jboss.org/jira/browse/JBJCA-36 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.0 Alpha1 We need a datasource deployer chain that can deploy -ds.xml descriptors. The chain must be able to deploy any existing datasource definitions found in JBoss Application Server 5.0. A design goal is that the chain can be deployed in a standalone mode so it can be included in other projects - such as EJB3 - without pulling in the entire JCA implementation. Sub-tasks should be created for each deployment stage (org.jboss.deployers.spi.deployer.DeploymentStage). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Deleted: (JBJCA-7) new JCA deployers

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-7?page=com.atlassian.jira.plugin... ] Jesper Pedersen deleted JBJCA-7: -------------------------------- > new JCA deployers > ----------------- > > Key: JBJCA-7 > URL: https://jira.jboss.org/jira/browse/JBJCA-7 > Project: JBoss JCA > Issue Type: Task > Reporter: Jeff Zhang > Assignee: Jeff Zhang > > JCA deployers new implement. > Including some sub-task -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Deleted: (JBJCA-10) RAR and MCF deployer implement

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-10?page=com.atlassian.jira.plugi... ] Jesper Pedersen deleted JBJCA-10: --------------------------------- > RAR and MCF deployer implement > ------------------------------ > > Key: JBJCA-10 > URL: https://jira.jboss.org/jira/browse/JBJCA-10 > Project: JBoss JCA > Issue Type: Sub-task > Reporter: Jeff Zhang > Assignee: Jeff Zhang > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Deleted: (JBJCA-11) Deployer management infomation builder

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-11?page=com.atlassian.jira.plugi... ] Jesper Pedersen deleted JBJCA-11: --------------------------------- > Deployer management infomation builder > -------------------------------------- > > Key: JBJCA-11 > URL: https://jira.jboss.org/jira/browse/JBJCA-11 > Project: JBoss JCA > Issue Type: Sub-task > Reporter: Jeff Zhang > Assignee: Jeff Zhang > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Deleted: (JBJCA-9) JCA deployers builder implement

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-9?page=com.atlassian.jira.plugin... ] Jesper Pedersen deleted JBJCA-9: -------------------------------- > JCA deployers builder implement > ------------------------------- > > Key: JBJCA-9 > URL: https://jira.jboss.org/jira/browse/JBJCA-9 > Project: JBoss JCA > Issue Type: Sub-task > Reporter: Jeff Zhang > Assignee: Jeff Zhang > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Deleted: (JBJCA-8) RAR and MCF ParserDeployer new impl

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-8?page=com.atlassian.jira.plugin... ] Jesper Pedersen deleted JBJCA-8: -------------------------------- > RAR and MCF ParserDeployer new impl > ----------------------------------- > > Key: JBJCA-8 > URL: https://jira.jboss.org/jira/browse/JBJCA-8 > Project: JBoss JCA > Issue Type: Sub-task > Reporter: Jeff Zhang > Assignee: Jeff Zhang > > use JAXB to parse and get metadata -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-879) UDP: see whether new MulticastSocket(mcast_addr, port) works on Solaris

by Bela Ban (JIRA)

UDP: see whether new MulticastSocket(mcast_addr, port) works on Solaris ----------------------------------------------------------------------- Key: JGRP-879 URL: https://jira.jboss.org/jira/browse/JGRP-879 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Optional Fix For: 2.7 In UDP, we check whether running under Linux. If so, we bind the MulticastSocket to the mcast_addr, else we don't. If this works under Solaris, we could also bind the MulticastSocket the same way. [Brian] dev12 runs Solaris 9 and dev13 runs Solaris 10. http://docs.jboss.org/process-guide/en/html/qalab.html#d0e5666 is probably somewhat out of date but at least it's right that these are solaris boxes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-881) Persistent ports: update port on graceful leave

by Bela Ban (JIRA)

Persistent ports: update port on graceful leave ----------------------------------------------- Key: JGRP-881 URL: https://jira.jboss.org/jira/browse/JGRP-881 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.6.8, 2.7 When a node has port 5000, and leaves, we remove 5000, so the next process can grab it again. This is incorrect and does not prevent reincarnation ! SOLUTION: update 5000 with the current timestamp when leaving gracefully, don't remove it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-856) Confirm that marshalling works between 32 bit and 64 bit machines

by Bela Ban (JIRA)

Confirm that marshalling works between 32 bit and 64 bit machines ----------------------------------------------------------------- Key: JGRP-856 URL: https://jira.jboss.org/jira/browse/JGRP-856 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.7 Make sure we don't have marshalling code which explicitly hard codes (for example) a word, which can be 32 bits or 64 bits -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
17
0 / 0

[JBoss JIRA] Created: (JBREM-992) Can't restart a Connector that uses SocketServerInvoker

by Brian Stansberry (JIRA)

Can't restart a Connector that uses SocketServerInvoker ------------------------------------------------------- Key: JBREM-992 URL: http://jira.jboss.com/jira/browse/JBREM-992 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.GA (Pinto) Reporter: Brian Stansberry Priority: Minor You can't take a Connector that uses SocketServerInvoker through a restart, i.e. these lifecycle steps: create/start/stop/start. You have to do a full transition to destroy and back through create. This is because SocketServerInvoker sets its maxPoolSize field to 0 as part of its cleanup work in stop(). If you then call start() you get a failure due to 0 being an invalid value for maxPoolSize: 2008-06-04 12:33:00,382 DEBUG [org.jboss.invocation.unified.server.UnifiedInvokerHA] (RMI TCP Connec tion(31)-127.0.0.1) Starting failed jboss:service=invoker,type=unifiedha,partitionName=RestartPartit ion java.lang.IllegalArgumentException: Illegal cache capacities at org.jboss.util.LRUCachePolicy.<init>(LRUCachePolicy.java:77) at org.jboss.remoting.transport.socket.LRUPool.<init>(LRUPool.java:44) at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:231) at org.jboss.invocation.unified.server.UnifiedInvoker.startService(UnifiedInvoker.java:140) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) -- 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

17 years

4
7
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 2009