February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9092) Audit logging

by Brian Stansberry (JIRA)

Audit logging ------------- Key: JBAS-9092 URL: https://issues.jboss.org/browse/JBAS-9092 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.Beta4 All modifications through the administrative infrastructure will be audited. The administrative audit log will be tamper proof. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

5
11
0 / 0

[JBoss JIRA] (AS7-2390) Warnings ARJUNA16037, ARJUNA16038 in log file

by Robert Petermeier (Created) (JIRA)

Warnings ARJUNA16037, ARJUNA16038 in log file --------------------------------------------- Key: AS7-2390 URL: https://issues.jboss.org/browse/AS7-2390 Project: Application Server 7 Issue Type: Bug Components: Transactions Affects Versions: 7.0.1.Final Environment: Windows 7, Windows Server 2008 Reporter: Robert Petermeier Assignee: Jonathan Halliday Priority: Minor We keep seeing the following warning messages in our log files every 2m, 10s: 12:05:29,290 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac146de0:3231b1f3:4ea67b21:4acc, node_name=1, branch_uid=0:ffffac146de0:3231b1f3:4ea67b21:4ad5, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@79453076 > On another system these are intermixed with 14:41:27,440 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86a7, node_name=1, branch_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86ab, eis_name=unknown eis name > We are using JBoss 7 in standalone mode, with three datasources. One of them is an XA datasource (a H2 database with class org.h2.jdbcx.JdbcDataSource on one system, oracle.jdbc.xa.client.OracleXADataSource on another). JDBC drivers for Oracle and H2 are deployed as jars in standalone/deployments along with our app. -- 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

11 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1916) Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness

by Darran Lofthouse (JIRA)

Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness --------------------------------------------------------------------------------------------------------- Key: AS7-1916 URL: https://issues.jboss.org/browse/AS7-1916 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Can we generate a name of first boot? Possibly even separate the internal name use to link from the realm to the name presented to the end users? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
5
0 / 0

[JBoss JIRA] (JGRP-1410) globalThreadGroup not destroyed creates a classloader memory leak

by Jean-Philippe Gariepy (Created) (JIRA)

globalThreadGroup not destroyed creates a classloader memory leak ----------------------------------------------------------------- Key: JGRP-1410 URL: https://issues.jboss.org/browse/JGRP-1410 Project: JGroups Issue Type: Bug Affects Versions: 3.0.1 Environment: linux w/ java 1.6 Reporter: Jean-Philippe Gariepy Assignee: Bela Ban When all channels are closed, the globalThreadGroup is not destroyed. For a normal (i.e. non-web) application, this is not a problem since the process will exit anyway. However, for a Java Enterprise web application, this causes a classloader memory leak since the ThreadGroup object has strong references to JGroups instances having strong references to their class object having strong reference to their class loader. Since the class loader is pointed by strong references, the it cannot be garbage collected and hence a leak is created each time the web application is stopped. -- 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

11 years, 11 months

5
16
0 / 0

[JBoss JIRA] (AS7-3160) Could not find Extension-List entry ExtensionListEntry because of Java 6+ Extension Mecanism

by Cristhian Lopez (Created) (JIRA)

Could not find Extension-List entry ExtensionListEntry because of Java 6+ Extension Mecanism -------------------------------------------------------------------------------------------- Key: AS7-3160 URL: https://issues.jboss.org/browse/AS7-3160 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.0.Final Environment: JDK 1.6.0_30 b12 JBoss AS 7.1 CR1b Reporter: Cristhian Lopez Assignee: David Lloyd When deploying Liferay 6.1 I'm getting the following error {code}08:08:38,561 WARN [org.jboss.as.server.deployment.module.module-extension-list-processor] (MSC service thread 1-1) Could not find Extension-List entry ExtensionListEntry [name=javax.crypto, title=crypto] referenced from ResourceRoot [root="/D:/Development/Servers/jboss-as-7.1.0.CR1b/content/ROOT.war/WEB-INF/classes"]{code} After some debug on the JBoss 7.1 CR1b source I found that it uses the java.ext.dirs property to find the ext libs, but since java 1.6 the property returns a classpath formated string with more than one path where the extensions are located(http://docs.oracle.com/javase/tutorial/ext/basics/install.html), but on the JBoss code I found that it's trying to parse the property value as a File path directly. As you can se on the ServerEnvironment.java line 292 {code}// Java system-wide extension dirs javaExtDirs = getFilesFromProperty(JAVA_EXT_DIRS, props);{code} and line 524 {code} private File getFileFromProperty(final String name, final Properties props) { String value = props.getProperty(name, null); if (value != null) { File f = new File(value); return f; } return null; } {code} This is causing that the server can´t find the extensions and warning about it. -- 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

11 years, 11 months

6
11
0 / 0

[JBoss JIRA] (AS7-3623) mod_cluster schema 1.1

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3623: ----------------------------------- Summary: mod_cluster schema 1.1 Key: AS7-3623 URL: https://issues.jboss.org/browse/AS7-3623 Project: Application Server 7 Issue Type: Feature Request Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.0.Final TODO -- 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

11 years, 11 months

3
7
0 / 0

[JBoss JIRA] (SECURITY-638) The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or

by Tom Fonteyne (Created) (JIRA)

The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-638 URL: https://issues.jboss.org/browse/SECURITY-638 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.4.SP9 Reporter: Tom Fonteyne Assignee: Anil Saldhana Priority: Minor Fix For: JBossSecurity_2.0.4.SP9 porting https://issues.jboss.org/browse/JBPAPP-7794 to PicketBox -- 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

11 years, 11 months

7
8
0 / 0

[JBoss JIRA] (AS7-3524) HostControllerConnectionService connection timeout is not configurable

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3524: ------------------------------------- Summary: HostControllerConnectionService connection timeout is not configurable Key: AS7-3524 URL: https://issues.jboss.org/browse/AS7-3524 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Jason Greene I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. HostControllerConnectionService.java: ... ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); configuration.setEndpoint(endpointInjector.getValue()); configuration.setConnectionTimeout(15000); configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); client = ProtocolChannelClient.create(configuration); ... Exception I am getting: [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- 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

11 years, 11 months

3
9
0 / 0

[JBoss JIRA] (AS7-2177) TS: Check logging

by Ondrej Zizka (Created) (JIRA)

TS: Check logging ----------------- Key: AS7-2177 URL: https://issues.jboss.org/browse/AS7-2177 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Some tests print to System.out, and also ex.printStackTrace(). Turn it to proper logging. Also check logging config. -- 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

11 years, 11 months

3
3
0 / 0

[JBoss JIRA] (AS7-3830) Remote JNDI call does not bind stateful beans

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3830: ------------------------------------- Summary: Remote JNDI call does not bind stateful beans Key: AS7-3830 URL: https://issues.jboss.org/browse/AS7-3830 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai It seems that current ejb remote client is not able to find stateful bean. Exception is thrown instead: {code} javax.naming.NamingException: java.lang.IllegalStateException: No EJB client context is available [Root exception is java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:124) at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:70) 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) Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:91) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133) ... 7 more Caused by: java.lang.IllegalStateException: No EJB client context is available at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160) at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:89) ... 8 more {code} Please, check my test whether definition of remote context does not contain a mistake. But finding singleton and stateless beans works fine. https://github.com/ochaloup/jboss-as/blob/ejb-remote-call/testsuite/integ... -- 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

11 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012