June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-892) ConnectionMap.createServerSocket(): throw an exception if socket cannot be created

by Bela Ban (JIRA)

ConnectionMap.createServerSocket(): throw an exception if socket cannot be created ---------------------------------------------------------------------------------- Key: JGRP-892 URL: https://jira.jboss.org/jira/browse/JGRP-892 Project: JGroups Issue Type: Task Affects Versions: 2.6.7 Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.6.8, 2.8 Currently, this method returns null, and unless the caller checks for null, we'll have an NPE later. SOLUTION: throw an exception if the socket cannot be created. TODO: check Util.createServerSocket()/createSocket()/createDatagramSocket() as well and see whether we need to throw an exception there, too. -- 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

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] (AS7-4788) Convert code to use ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4788: -------------------------------- Summary: Convert code to use ResourceDefinition Key: AS7-4788 URL: https://issues.jboss.org/browse/AS7-4788 Project: Application Server 7 Issue Type: Task Reporter: Tomaz Cerar Assignee: Tomaz Cerar All subsystems should use ResourceDefinition and AttributeDefinition for defining management model This is tracking issue for all issues related to them, for every subsystem / module it there should be separate issue. -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-4975) XA datasources memory leak

by Marcel Å ebek (JIRA)

Marcel Å ebek created AS7-4975: ---------------------------------- Summary: XA datasources memory leak Key: AS7-4975 URL: https://issues.jboss.org/browse/AS7-4975 Project: Application Server 7 Issue Type: Bug Components: Transactions Affects Versions: 7.1.1.Final Environment: Debian stable Postgres version: 8.4.11 jdbc driver version: 9.1-902.jdbc4 database is assumed to contain a schema named test. datasource definition: <xa-datasource jndi-name="java:/jdbc/test" pool-name="test" enabled="true" use-ccm="false"> <xa-datasource-property name="PortNumber"> 5432 </xa-datasource-property> <xa-datasource-property name="DatabaseName"> ${db.name} </xa-datasource-property> <xa-datasource-property name="ServerName"> 127.0.0.1 </xa-datasource-property> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class> <driver>postgresql-9.1-902.jdbc4.jar</driver> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <xa-pool> <is-same-rm-override>false</is-same-rm-override> <interleaving>false</interleaving> <pad-xid>false</pad-xid> <wrap-xa-resource>false</wrap-xa-resource> </xa-pool> <security> <user-name>${db.name}_test</user-name> <password>${db.name}_test</password> </security> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> </validation> <statement> <share-prepared-statements>false</share-prepared-statements> </statement> </xa-datasource> Reporter: Marcel Å ebek Assignee: Jason Greene I'm experiencing problems with XA datasources on jboss 7 and postgres database. The test application periodically (each 5 seconds) performs several JPA queries. I use @Schedule facility on @Singleton @Startup bean. However, after a few days, the server runs out of memory. Switching to local tx datasources seems to fix the problem. Analysis of heap dump using visualvm gives the following: Heap is quite full (~490 MB from 512MB), most space is taken by byte[] (40%, 200MB) and HashMap.Entry (16%, 80MB) objects, so that gives no much information. Computing retained sizes shows that most space (but just ~16MB) is taken by com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule#1. Further analysis shows that XARecoveryModule._xidScans contains ~8000 entries. The size continuously grows. When the dump is taken before the OOM conditions starts, eg. when the heap is 50% full, the size of this hashmap is ~4000, so it looks like it grows continuously. I will attach my example test case. -- 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

13 years, 10 months

4
6
0 / 0

[JBoss JIRA] (AS7-5031) Allow for local authentication to be the only supported mechanism

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5031: ------------------------------------- Summary: Allow for local authentication to be the only supported mechanism Key: AS7-5031 URL: https://issues.jboss.org/browse/AS7-5031 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 It should be possible for a realm to be defined where the local mechanism is the only supported mechanism. For HTTP this would mean no access can occur (unless we find a way to implement local for HTTP clients) and for Native any remaining clients would need to be able to support the local mechanism. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-837) CLONE - Transaction isolation level attribute doesn't accept integer values

by Tyronne Wickramarathne (JIRA)

Tyronne Wickramarathne created JBJCA-837: -------------------------------------------- Summary: CLONE - Transaction isolation level attribute doesn't accept integer values Key: JBJCA-837 URL: https://issues.jboss.org/browse/JBJCA-837 Project: IronJacamar Issue Type: Feature Request Components: Common Affects Versions: 1.0.11.Final Environment: IronJacamar 1.0.11 Reporter: Tyronne Wickramarathne Assignee: Jesper Pedersen Fix For: 1.0.12.Final It is not possible to specify an integer value for the Transaction Isolation Level attribute. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-4794) Convert AppClient subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4794: -------------------------------- Summary: Convert AppClient subsystem to ResourceDefinition Key: AS7-4794 URL: https://issues.jboss.org/browse/AS7-4794 Project: Application Server 7 Issue Type: Sub-task Components: Application Client Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Stuart Douglas Fix For: 7.2.0.Alpha1 Convert subsystem to use ResourceDefinition and AttributeDefinition -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-4979) Issue in Interactive mode on cygwin not working.

by Peter Cadman (JIRA)

Peter Cadman created AS7-4979: --------------------------------- Summary: Issue in Interactive mode on cygwin not working. Key: AS7-4979 URL: https://issues.jboss.org/browse/AS7-4979 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.1.Final Environment: Windows 7, Cygwin 1.7.15 Reporter: Peter Cadman Assignee: Alexey Loubyansky Priority: Minor After connecting to standalone server on localhost, Cgywin doesn't response to input. -- 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

13 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBASPECT-38) While starting the getting error

by shrishail chinnannavar (JIRA)

shrishail chinnannavar created JBASPECT-38: ---------------------------------------------- Summary: While starting the getting error Key: JBASPECT-38 URL: https://issues.jboss.org/browse/JBASPECT-38 Project: JBoss Aspects Issue Type: Bug Components: test Reporter: shrishail chinnannavar Assignee: Andrew Rubinger Hi, i am using jboss 7.1 and i deployed liferay 6.1 in in jboss ,after that while starting the jboss(standalone.sh) i am getting below error dule: deployment.ROOT.war:main at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] Caused by: org.jboss.modules.ModuleNotFoundException: Module system:main is not found in local module loader @76ab2f (roots: /Users/shrishail/Desktop/EAI/14jun12/liferayportal/jboss-as-7.1.1.Final/modules) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:233) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:246) at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:160) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.modules.Module.addPaths(Module.java:841) at org.jboss.modules.Module.link(Module.java:1181) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more Regards Shrishail -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5029) Invalid wait for ConfigurationAdmin service

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5029: ----------------------------------- Summary: Invalid wait for ConfigurationAdmin service Key: AS7-5029 URL: https://issues.jboss.org/browse/AS7-5029 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.Alpha1 {code} 09:15:00,892 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011011: Starting bundles for start level: 1 09:15:00,938 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0 09:15:01,025 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.0 09:15:01,222 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999 09:15:01,228 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447 09:15:01,258 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/deployments 09:15:11,065 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT 09:15:11,101 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8 09:15:11,103 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011000: OSGi Framework started {code} Note the delay between 09:15:01 and 09:15:11 This is very likely caused by {code} ConfigurationAdmin osgiConfigAdminService = (ConfigurationAdmin) osgiConfigAdminServiceTracker.waitForService(10000); {code} -- 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

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] (AS7-4879) Objects implementing javax.naming.Referenceable are not bound to jndi correctly

by Michael Gronau (JIRA)

Michael Gronau created AS7-4879: ----------------------------------- Summary: Objects implementing javax.naming.Referenceable are not bound to jndi correctly Key: AS7-4879 URL: https://issues.jboss.org/browse/AS7-4879 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.2.Final (EAP) Reporter: Michael Gronau Assignee: John Bailey Normally when those object are to be bound to the jndi its getReference() method is called and this reference is then bound. When looking up this reference from a remote client it is resolved and instantiated with the ObjectFactory class stored in this Reference object. All this corrently does not work (the invocation of getReference() and the instantiation of the object). One little workaround is only to bind the Reference object directly, i.e. create the Referenceable object, call the getReference() and bind this reference to the jndi. But the instantiation only works with local clients (inside jboss jvm), not with remote clients. -- 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

13 years, 10 months

4
5
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 June 2012