January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-568) Adds metrics support for RHQ plugin

by Lin Gao (JIRA)

Adds metrics support for RHQ plugin ----------------------------------- Key: JBJCA-568 URL: https://issues.jboss.org/browse/JBJCA-568 Project: IronJacamar Issue Type: Task Components: Management Reporter: Lin Gao Assignee: Lin Gao -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBJCA-562) Add operation support for RHQ plugin

by Lin Gao (JIRA)

Add operation support for RHQ plugin ------------------------------------ Key: JBJCA-562 URL: https://issues.jboss.org/browse/JBJCA-562 Project: IronJacamar Issue Type: Task Components: Management Reporter: Lin Gao Assignee: Lin Gao -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3368) CompositeClassLoader.getResources(String) should never return null

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3368: ------------------------------------- Summary: CompositeClassLoader.getResources(String) should never return null Key: JBRULES-3368 URL: https://issues.jboss.org/browse/JBRULES-3368 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.4.0.Beta3 If getResources() has no results it should return an empty enumeration,not null. Some JDK plugin code around ImageIO depends upon this behaviour. -- 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

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] (AS7-3191) CacheFactoryResourceDefinition registers read-only configuration attributes

by Brian Stansberry (Created) (JIRA)

CacheFactoryResourceDefinition registers read-only configuration attributes --------------------------------------------------------------------------- Key: AS7-3191 URL: https://issues.jboss.org/browse/AS7-3191 Project: Application Server 7 Issue Type: Bug Components: Domain Management, EJB Affects Versions: 7.1.0.CR1b Reporter: Brian Stansberry Assignee: Paul Ferraro Fix For: 7.1.0.Final @Override public void registerAttributes(ManagementResourceRegistration resourceRegistration) { for (AttributeDefinition attribute: ATTRIBUTES) { resourceRegistration.registerReadOnlyAttribute(attribute, null); } } That means the configuration cannot be changed without editing the xml. Needs to be a registerReadWriteAttribute(). If the change cannot immediately be applied to the relevant runtime service, register ReloadRequiredWriteAttributeHandler as the write-attribute handler. The definitions of PASSIVATION_STORE and ALIASES would need update as they say Flags.RESTART_NONE which implies any change will be applied to runtime services. -- 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

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] (JBJCA-737) XAResourceRecoveryImpl does not consider the possibility that wrapXAResource may be null

by Stuart Douglas (JIRA)

Stuart Douglas created JBJCA-737: ------------------------------------ Summary: XAResourceRecoveryImpl does not consider the possibility that wrapXAResource may be null Key: JBJCA-737 URL: https://issues.jboss.org/browse/JBJCA-737 Project: IronJacamar Issue Type: Bug Reporter: Stuart Douglas Assignee: Jesper Pedersen This results in a potential problem when deploying XML datasources in AS7 without an xa-pool: 14:17:30,697 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.NullPointerException at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:187) at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:52) [jbossjts-integration-4.16.1.Final.jar:] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:462) [jbossjts-4.16.1.Final.jar:] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:385) [jbossjts-4.16.1.Final.jar:] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:166) [jbossjts-4.16.1.Final.jar:] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-4.16.1.Final.jar:] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-4.16.1.Final.jar:] I am just going to work around this in AS7 for now, but I think this should still be fixed in IJ. -- 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

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-3460) FLUSH dominates MSC service start, and never returns

by Jason Greene (JIRA)

Jason Greene created AS7-3460: --------------------------------- Summary: FLUSH dominates MSC service start, and never returns Key: AS7-3460 URL: https://issues.jboss.org/browse/AS7-3460 Project: Application Server 7 Issue Type: Bug Reporter: Jason Greene "MSC service thread 1-6" prio=10 tid=0x00007f207c038000 nid=0x23be waiting on condition [0x00007f209d475000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000000e1539140> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2116) at org.jgroups.util.Promise.doWait(Promise.java:116) at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:72) at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:41) at org.jgroups.util.Promise.getResult(Promise.java:103) at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:137) at org.jgroups.protocols.pbcast.ClientGmsImpl.joinWithStateTransfer(ClientGmsImpl.java:42) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:921) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FRAG2.down(FRAG2.java:147) at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:238) at org.jgroups.protocols.pbcast.FLUSH.handleConnect(FLUSH.java:300) at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:265) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1033) at org.jgroups.JChannel.down(JChannel.java:732) at org.jgroups.JChannel.connect(JChannel.java:347) - locked <0x00000000e1537880> (a org.jboss.as.clustering.jgroups.MuxChannel) at org.jgroups.JChannel.connect(JChannel.java:305) - locked <0x00000000e1537880> (a org.jboss.as.clustering.jgroups.MuxChannel) at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:38) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) 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) Log: 12:46:12,235 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:15,240 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:17,242 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:20,244 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:22,248 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:25,252 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:27,256 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:30,261 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:32,263 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:35,266 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:37,268 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message 12:46:40,269 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying 12:46:42,270 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message (repeats) -- 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

12 years, 8 months

4
20
0 / 0

[JBoss JIRA] (AS7-3316) stanalonde.xml, xa-datasource/security, <user-name> cannot be parametrised

by ivan khoosty (JIRA)

ivan khoosty created AS7-3316: --------------------------------- Summary: stanalonde.xml, xa-datasource/security, <user-name> cannot be parametrised Key: AS7-3316 URL: https://issues.jboss.org/browse/AS7-3316 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.CR1b Reporter: ivan khoosty Assignee: Jesper Pedersen Priority: Minor in standalone.xml, i've got a system property declared <system-properties> <property name="sql.user" value="sa"/> ... </system-properties> it does not get resolved further down in datasource declaration, ... <security> <user-name>${sql.user}</user-name> ... </security> interestingly, all other properties resolve no problem, ie password, server etc. there is a workaround (hardcode the username value!), thus setting the bug priority to minor. -- 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

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (AS7-1917) Supporting URIEncoding and useBodyEncodingForURI in Connector

by Marek Smigielski (JIRA)

Supporting URIEncoding and useBodyEncodingForURI in Connector ------------------------------------------------------------- Key: AS7-1917 URL: https://issues.jboss.org/browse/AS7-1917 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.0.1.Final Reporter: Marek Smigielski Assignee: Remy Maucherat I need to set URIEncoding and useBodyEncodingForURI in jbossas7 but I didn't find any way of doing it. The way it can be done in previous versions can't be applied because server will not start up properly. It would be great if you could configure connector like that: <Connector name="http" protocol="HTTP/1.1" socket-binding="http" scheme="http" URIEncoding="UTF-8" useBodyEncodingForURI="true"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

8
7
0 / 0

[JBoss JIRA] Created: (JBAS-8827) Deal with expression values in all operation handlers

by Brian Stansberry (JIRA)

Deal with expression values in all operation handlers ----------------------------------------------------- Key: JBAS-8827 URL: https://issues.jboss.org/browse/JBAS-8827 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta1 Pretty much any simple value in a detyped operation can be of type ModelType.EXPRESSION instead something an OperationHandler might expect, like ModelType.STRING or ModelType.INT. All handlers need to deal with this fact. There are two main aspects to this: 1) Any parameter validation that goes on needs to account for the presence of expression values. Basically that means a) accept the expression for storage in the model b) call resolve() on the operation and use the resolved version for application to the runtime. c) re-validation of the resolved value may be necessary -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
7
0 / 0

[JBoss JIRA] (AS7-3182) Admin console: standalone server doesn't require distinct socket binding groups

by Jan Martiska (Created) (JIRA)

Admin console: standalone server doesn't require distinct socket binding groups ------------------------------------------------------------------------------- Key: AS7-3182 URL: https://issues.jboss.org/browse/AS7-3182 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Priority: Minor see screenshot. In standalone mode, a standalone server does not support defining multiple socket binding groups, there can be only one, by default it is named 'standard-sockets' (at least I understand it this way, it is specified in jboss-as-config_1.1 xml schema). Therefore the checkbox for picking one of socket binding groups is irrelevant, because it cannot provide any choices. By the way, it could be useful to have the possibility to change the name 'standard-sockets' using admin console. -- 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

12 years, 8 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012