March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9053) cli: buffer index in the command completer needs correction

by Alexey Loubyansky (JIRA)

cli: buffer index in the command completer needs correction ----------------------------------------------------------- Key: JBAS-9053 URL: https://issues.jboss.org/browse/JBAS-9053 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta2 It's a minor issue. In case of leading whitespaces before the command part, pressing tab will remove the leading whitespaces and the chunk (or completed command) will appear at the beginning of the line. This could be fixed by correcting the returned buffer index by the command completer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8837) Clean up the max-threads attribute in managment socket config

by Brian Stansberry (JIRA)

Clean up the max-threads attribute in managment socket config ------------------------------------------------------------- Key: JBAS-8837 URL: https://issues.jboss.org/browse/JBAS-8837 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Priority: Minor Fix For: 7.0.0.Beta1 There is a max-threads field in the dc/host/server management socket config. It's not in the schema and AFAICT it's not used. Either use it and add to the schema, or remove it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8825) Default interface for a socket binding should come via SocketBindingManagerService

by Brian Stansberry (JIRA)

Default interface for a socket binding should come via SocketBindingManagerService ---------------------------------------------------------------------------------- Key: JBAS-8825 URL: https://issues.jboss.org/browse/JBAS-8825 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta1 The default interface used for socket bindings comes from an attribute on the socket-binding-group element. The XML parser tracks the value and then adds it to the operation to create a socket-binding if the <socket-binding> element doesn't declare an interface. This parser-based approach isn't sufficient as it only works for the parsing use case. Applying it elsewhere forces operations on child model resources (socket-bindings) to find out information stored in parent resources, which we want to avoid. Better IMO is to make the "interface" field on the model representation of a socket binding nullable; the parser should just pass through what the XML says. The SocketBindingManagerService should store the default interface, like it currently stores the port offset. SocketBinding.getAddress() can then ask for the default address from SocketBindingManagerService if its own networkInterface field is null. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8826) No way to apply a socket binding port offset to a standalone server

by Brian Stansberry (JIRA)

No way to apply a socket binding port offset to a standalone server ------------------------------------------------------------------- Key: JBAS-8826 URL: https://issues.jboss.org/browse/JBAS-8826 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta1 There is no place to store the SocketBindingManagerService's port-offset in standalone.xml. Currently it gets passed in as a special value by the HostController, which only works in the domain mode use case. I think the most intuitive thing to do is to add a port-offset attribute to standalone-socket-binding-groupType. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8801) Undeployment leaks root deployment service

by Thomas Diesler (JIRA)

Undeployment leaks root deployment service ------------------------------------------ Key: JBAS-8801 URL: https://issues.jboss.org/browse/JBAS-8801 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler To reproduce #1 do a hot-deploy #2 do a hot-undeploy #3 use jconsole to check the installed services. you should see jboss.deployment.yourdeployment As a result redeploy fails with Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to mount deployment content at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:69) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:85) ... 4 more Caused by: java.io.IOException: Filsystem already mounted at mount point ""/content/example-simple.jar"" at org.jboss.vfs.VFS.mount(VFS.java:159) at org.jboss.vfs.VFS.doMount(VFS.java:379) at org.jboss.vfs.VFS.mountZip(VFS.java:405) at org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:78) at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:65) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8513) Managed bean @Resource injection is premature

by Brian Stansberry (JIRA)

Managed bean @Resource injection is premature --------------------------------------------- Key: JBAS-8513 URL: https://jira.jboss.org/browse/JBAS-8513 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Reporter: Brian Stansberry Fix For: 7.0.0.M1 The way this works now, for a given managed bean type T, the ManagedBeanService<T> would have an instance of each @Resource bean injected as part of start(). Thereafter whenever ManagedBeanContainer.createInstance() is invoked, the same bean instance would be injected into the newly created bean. AIUI what should happen is createInstance() should result in a new naming lookup for each @Resource bean, which in turn would trigger creation of a new instance of that bean. This also causes classloading problems, since doing the injection during the MSC StartTask results in the ManagedBeanObjectFactory not being visible. See forum thread for effect of this. -- 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

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9065) Invoked without a tx, transaction scoped entity mananger managed entities should be detached at end of EntityManager call

by Scott Marlow (JIRA)

Invoked without a tx, transaction scoped entity mananger managed entities should be detached at end of EntityManager call ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9065 URL: https://issues.jboss.org/browse/JBAS-9065 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBADMCON-161) Jboss 6 Admin Console(1.4.0.SP2) Issue : Cannot update Datasource Configurations

by Abdul Jaleel C (JIRA)

Jboss 6 Admin Console(1.4.0.SP2) Issue : Cannot update Datasource Configurations -------------------------------------------------------------------------------- Key: JBADMCON-161 URL: https://issues.jboss.org/browse/JBADMCON-161 Project: JBoss Admin Console Issue Type: Bug Reporter: Abdul Jaleel C Hi All, I am a newbee in Jboss(Using version 6). I am facing a problem when i enter the Datasource Configurations using Admin Console. The modifications are not getting reflected.I have to make modifications in xml file directly. As my organization need more than 50 different datasources running in the application server , we certainly need an interface to manage these configurations. Please help.. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8960) Use TransactionSynchronizationRegistry instead of TransactionLocalDelegate

by Scott Marlow (JIRA)

Use TransactionSynchronizationRegistry instead of TransactionLocalDelegate -------------------------------------------------------------------------- Key: JBAS-8960 URL: https://issues.jboss.org/browse/JBAS-8960 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

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBJCA-528) correct ConfigProperty merging about ConfigProperty16Impl

by Jeff Zhang (JIRA)

correct ConfigProperty merging about ConfigProperty16Impl ---------------------------------------------------------- Key: JBJCA-528 URL: https://issues.jboss.org/browse/JBJCA-528 Project: IronJacamar Issue Type: Task Components: Core Affects Versions: 1.0.0.Beta4 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta5 common/src/main/java/org/jboss/jca/common/metadata/merge/Merger.java ConfigProperty16 newProp = new ConfigProperty16Impl(c.getDescriptions(), c.getConfigPropertyName(), - c.getConfigPropertyName(), newValue, + c.getConfigPropertyType(), newValue, c16.getConfigPropertyIgnore(), c16.getConfigPropertySupportsDynamicUpdates(), c16.getConfigPropertyConfidential(), c.getId()); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 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 March 2011