February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6990) PooledInvokerUnitTestCase failure

by Scott Marlow (JIRA)

PooledInvokerUnitTestCase failure ---------------------------------- Key: JBAS-6990 URL: https://jira.jboss.org/jira/browse/JBAS-6990 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-6.0.0.Alpha1 Reporter: Scott Marlow Assignee: Scott M Stark Fix For: JBossAS-6.0.0.Alpha1 To see the failure, do this: 1. cd testsuite 2. ./build.sh -Dtest=org.jboss.test.naming.test.PooledInvokerUnitTestCase one-test You will see: [junit] Running org.jboss.test.naming.test.PooledInvokerUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Test org.jboss.test.naming.test.PooledInvokerUnitTestCase FAILED (timeout) Also, if you try to access the jndi naming service via the jmx console, you will also see faliures (after running the PooledInvokerUnitTestCase). -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7642) ManagedDeployment problem with deploy-hasingleton-jboss-beans.xml

by Brian Stansberry (JIRA)

ManagedDeployment problem with deploy-hasingleton-jboss-beans.xml ----------------------------------------------------------------- Key: JBAS-7642 URL: https://jira.jboss.org/jira/browse/JBAS-7642 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Management services Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 Following is logged during start of the admin-console (i.e. after first request): 18:10:50,203 WARN [org.jboss.profileservice.management.ManagementViewImpl] Failed to create ManagedDeployment for: vfsfile:/home/bes/dev/jboss/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/all/deploy/cluster/deploy-hasingleton-jboss-beans.xml: java.lang.IllegalArgumentException: Can only get ref from simple value: CompositeValueSupport: metaType=[MutableCompositeMetaType{org.jboss.profileservice.spi.ProfileKey items=[name=defaultKey type=boolean], [name=domain type=java.lang.String], [name=name type=java.lang.String], [name=server type=java.lang.String]}] items=[defaultKey=SimpleMetaType:boolean:false,domain=SimpleMetaType:java.lang.String:default,name=SimpleMetaType:java.lang.String:deploy-hasingleton,server=SimpleMetaType:java.lang.String:default] at org.jboss.profileservice.management.ManagementViewImpl.getRefName(ManagementViewImpl.java:871) at org.jboss.profileservice.management.ManagementViewImpl.processManagedObject(ManagementViewImpl.java:782) at org.jboss.profileservice.management.ManagementViewImpl.processManagedDeployment(ManagementViewImpl.java:625) at org.jboss.profileservice.management.ManagementViewImpl.processRootManagedDeployment(ManagementViewImpl.java:597) at org.jboss.profileservice.management.ManagementViewImpl.loadProfiles(ManagementViewImpl.java:509) at org.jboss.profileservice.management.ManagementViewImpl.load(ManagementViewImpl.java:258) at org.rhq.plugins.jbossas5.connection.AbstractProfileServiceConnection.init(AbstractProfileServiceConnection.java:47) at org.rhq.plugins.jbossas5.connection.AbstractProfileServiceConnectionProvider.connect(AbstractProfileServiceConnectionProvider.java:43) at org.rhq.plugins.jbossas5.InProcessJBossASDiscovery.discoverInProcessJBossAS(InProcessJBossASDiscovery.java:71) at org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent.discoverInProcessJBossAS(ApplicationServerDiscoveryComponent.java:255) at org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent.discoverResources(ApplicationServerDiscoveryComponent.java:104) at sun.reflect.GeneratedMethodAccessor410.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:266) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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:619) -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7694) Port JBPAPP-3026 to AS trunk

by jaikiran pai (JIRA)

Port JBPAPP-3026 to AS trunk ---------------------------- Key: JBAS-7694 URL: https://jira.jboss.org/jira/browse/JBAS-7694 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (JBoss Messaging) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M2 JBPAPP-3026 fixed a bug where hierarchical queue *names* were leading to a deployment exception like: Deployment "vfszip:/home/hudson/workspace/JBoss-AS-6.x-tests-ejb3/ejb3home/testsuite/target/test-lib/ejbthree987.jar/" is in error due to the following reason(s): java.lang.IllegalStateException: The queue name should not contain forward slash: queue/ejbthree987 This fix needs to be ported to AS trunk (EJB3 testsuite shows a failure because of this missing fix). -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6442) Response truncated in the presence of special character

by Juan Manuel Medina Apodaca (JIRA)

Response truncated in the presence of special character ------------------------------------------------------- Key: JBAS-6442 URL: https://jira.jboss.org/jira/browse/JBAS-6442 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.GA Environment: Windows XP, JDK 1.6.0_11 Reporter: Juan Manuel Medina Apodaca Assignee: Remy Maucherat When a servlet puts a session attribute containing a collection of strings, one of the strings contains a special character (for example: ...) and this string is displayed in a JSP, the resulting page is truncated before the special character. For example, in a servlet: ArrayList optionList = new ArrayList(); ... optionList.add("Any string 1"); optionList.add("Any string 2"); optionList.add("Any string 3"); optionList.add("Any string 4"); optionList.add("A string with ... character"); optionList.add("Any string 6"); optionList.add("Any string 7"); optionList.add("Any string 8"); ... request.getSession(false).setAttribute("myList", optionList); In the JSP: <c:forEach var="currentOption" items="${myList}"> ${currentOption} </c:forEach> The resulting page gets truncated before the 5th line. In JBoss 4.0.0 the page shows complete, with a ? sign in the place of the special character. -- 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

15 years, 9 months

6
10
0 / 0

[JBoss JIRA] Closed: (JBAS-7102) Problem sending large files via farm service

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7102?page=com.atlassian.jira.plug... ] Brian Stansberry closed JBAS-7102. ---------------------------------- Resolution: Done > Problem sending large files via farm service > -------------------------------------------- > > Key: JBAS-7102 > URL: https://jira.jboss.org/jira/browse/JBAS-7102 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering, ProfileService > Affects Versions: JBossAS-5.1.0.GA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: JBossAS-6.0.0.M2 > > > Users have reported issues sending large files over the AS 5.1 farming service; see forum thread. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2421) org.drools.RuntimeDroolsException: unable to determine ValueType for Class [class MyClass] on IBM JVM with JIT enabled

by Tihomir Surdilovic (JIRA)

org.drools.RuntimeDroolsException: unable to determine ValueType for Class [class MyClass] on IBM JVM with JIT enabled ---------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2421 URL: https://jira.jboss.org/jira/browse/JBRULES-2421 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Tihomir Surdilovic Assignee: Mark Proctor On IBM JVM with JIT enabled using Drools 4.0.7 often the following exception occurs: org.drools.RuntimeDroolsException: unable to determine ValueType for Class [class MyClass] at org.drools.base.ValueType.determineValueType(ValueType.java:222) at org.drools.base.ClassObjectType.<init>(ClassObjectType.java:56) at org.drools.reteoo.Rete$ClassObjectTypeConf.<init>(Rete.java:442) at org.drools.reteoo.Rete.assertObject(Rete.java:152) ... We have determined that in the IBM JVN with JIT enabled, the expression "XXXX instanceof Object" fails sometimes. On the other hand expression "XXXX isAssignableFrom(YYYYYY) ... " works as expected. The code change required here is in org.drools.base.ValueType change: ... } else if ( clazz instanceof Object ) { return ValueType.OBJECT_TYPE; ... to ... else if ( Object.class.isAssignableFrom( clazz ) ) { return ValueType.OBJECT_TYPE; ... -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2003) Upgrade to 1.0.0-alpha-4 of nointerface component

by jaikiran pai (JIRA)

Upgrade to 1.0.0-alpha-4 of nointerface component ------------------------------------------------- Key: EJBTHREE-2003 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2003 Project: EJB 3.0 Issue Type: Thirdparty Change Components: ejb3_1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.3 1.0.0-alpha-4 of nointerface component has been released. It contains a bug fix related to jndi binding https://jira.jboss.org/jira/browse/EJBTHREE-2002. Upgrade ejb3_1 to include this newly released version. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7011) Jboss high memory leak in SMP kernel 2.6.9-78.0.13.ELsmp but not in Non-SMP kernel 2.6.9-78.0.13.EL

by Mathiyalagan Gopal (JIRA)

Jboss high memory leak in SMP kernel 2.6.9-78.0.13.ELsmp but not in Non-SMP kernel 2.6.9-78.0.13.EL --------------------------------------------------------------------------------------------------- Key: JBAS-7011 URL: https://jira.jboss.org/jira/browse/JBAS-7011 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: HP DL380 G4 with 4 GB RAM and Duel Core CPU with 3.60 GHz, Linux AS 4 64-bit 2.6.9-78.0.13.ELsmp. Reporter: Mathiyalagan Gopal Priority: Critical Hello All, We are the GE AssetIntelligence running our J2EE based web application in the famous combination of apache + Jboss servers. Our site was running now almost 2 yrs...after deep JVM memory investigation I found there is huge memory leak in the SMP kernel Linux Jboss systems. When I switched the same machine to run on Non-SMP kernel (i,e EL rather then ELsmp) the memory management handeled very well. When we run our Jboss application server in SMP kernel we have to bounce our jboss instance minimum 2 times a day to reset the JVM Heap, but with non-SMP kernel its running fine and we dont have to do anything. Is anybody out here facing the same issue? Note : For JVM heap diagnosis we used JProbe as well as Java inbuilt "jmap" utility to generate the report every hour for heap size and live objects. I am running following versions of servers, Hardware :HP DL 380 G4 ( 4 GB RAM , 2 Duel Core CPU 3.60 GHz) Server 1 : Apache-2.2.11 Server 2,3 & 4 : Jboss-4.0.5.GA Using apache-2.2.x (mod_loadbalancer) module to connect back end servers. My JAVA_OPTS vales are JAVA_OPTS="-Xms3096m -Xmx3096m -XX:MaxPermSize=256m -Djavax.xml.ws.spi.Provider=org.apache.cxf.jaxws.spi.ProviderImpl -Dorg.apache.cxf.bus.factory=org.apache.cxf.bus.CXFBusFactory -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.partition.name=vip-production-lpap03XXXX -Dtsf.environment=PRD -Dnodename=XXXXXXXX" Any help will be appreciated!! -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2470) user name containing underscore breaks the UsersActivityStatsService

by Gary Hu (JIRA)

user name containing underscore breaks the UsersActivityStatsService -------------------------------------------------------------------- Key: JBPORTAL-2470 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2470 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Hu If a user name contains underscore, for example "john_dow", it breaks the UsersActivityStatsService MBean sevice. This is the code from UsersActivityStatsServiceImpl: public void registerActivity(final UserActivity userActivity) { try { Notification notification = new Notification(Integer.toString(userActivity.getType()), this.getServiceName(), userActivity.getTimestamp(), userActivity.getTimestamp(), userActivity.getId() + "_" + userActivity.getSessionId()); .... And here is the code from UserActivity: public UserActivity(Notification notification) { if (notification.getMessage() == null) { throw new IllegalArgumentException("Id (notification message) cannot be null"); } this.id = notification.getMessage().substring(0, notification.getMessage().indexOf("_")); this.sessionId = notification.getMessage().substring(notification.getMessage().indexOf("_")); this.timestamp = notification.getTimeStamp(); this.type = Integer.parseInt(notification.getType()); } -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7691) Reduce the jbm-data JGroups MPING.timeout config

by Brian Stansberry (JIRA)

Reduce the jbm-data JGroups MPING.timeout config ------------------------------------------------ Key: JBAS-7691 URL: https://jira.jboss.org/jira/browse/JBAS-7691 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M2 It's 5000 instead of the 2000 used for discovery timeouts everywhere else. This will cut 'all' config startup time by 3 seconds. -- 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

15 years, 9 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2010