May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4374) failing org.jboss.test.cluster.test.StateTransferTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.cluster.test.StateTransferTestCase --------------------------------------------------------- Key: JBAS-4374 URL: http://jira.jboss.com/jira/browse/JBAS-4374 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.CR2 Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.GA We have 6 more testcase failures (essentially one) after the fix in JBAS-4373. testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(BuddyReplEnabled-TCP) testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(BuddyReplEnabled-UDP) testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(Default-TCP) testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(Default-UDP) testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(SyncModeNUseJvm-TCP) testActivationInactivation org.jboss.test.cluster.test.StateTransferTestCase(SyncModeNUseJvm-UDP) http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.... Brian can you look at it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
23
0 / 0

[JBoss JIRA] Commented: (JBRULES-360) Add support for nested properties in rules

by Venkat Garlapati (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-360?page=comments#action_12361058 ] Venkat Garlapati commented on JBRULES-360: ------------------------------------------ any body able to find the solution for this, even I am looking for the solution, but not able to get the solution > Add support for nested properties in rules > ------------------------------------------ > > Key: JBRULES-360 > URL: http://jira.jboss.com/jira/browse/JBRULES-360 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Reporter: Jacek Olszak > Assigned To: Mark Proctor > > Add support for nested properties in rules: > for example: > class Person { > private Room room; > ... > } > class Room { > private String name > ... > } > rule "some rule" { > when > Person(room.name="asdasdasd") > then > . ... > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-818) Please read the description below

by Venkat Garlapati (JIRA)

Please read the description below --------------------------------- Key: JBRULES-818 URL: http://jira.jboss.com/jira/browse/JBRULES-818 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.6 Environment: Oc4j server Reporter: Venkat Garlapati Assigned To: Mark Proctor RuleExecutionSetProvider ruleExecutionSetProvider; RuleExecutionSet ruleExecutionSet = ruleExecutionSetProvider.createRuleExecutionSet(source.toString(), null); I am passing my drl file which is in the jar file to the method call at that time it is giving the following error. 07/04/24 19:56:45 CharScanner; panic: ClassNotFoundException: org.antlr.stringtemplate.language.ChunkToken I have following version of antlr.jars in the class path antlr2.7.6.jar antlr3.0-ea8.jar stringtemplate-2.3b6.jar It is giving me a error even after changing the antlr2.7.6.jar to antlr2.7.7.jar and I have even got the new Stringtemplate.jar but still is giving the same error. I have trying to load the rule set file as part of initialization of the application. Please provide me some input so that I can resolve this issue, it is taking lot of time for me to resolve. Thanks a lot Venkat Garlapati -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1262) Look into optimizing the memory usage during the upload archive usecase.

by Sohil Shah (JIRA)

Look into optimizing the memory usage during the upload archive usecase. ------------------------------------------------------------------------- Key: JBPORTAL-1262 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1262 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6 Final Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6 Final This is particularly when uploading big archives 50MB or more. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-1268) DescriptorSupport does not validate its serializable fields adequately

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1268?page=comments#action_12361034 ] Dimitris Andreadis commented on JBAS-1268: ------------------------------------------ You are most probably using jdk5. > DescriptorSupport does not validate its serializable fields adequately > ---------------------------------------------------------------------- > > Key: JBAS-1268 > URL: http://jira.jboss.com/jira/browse/JBAS-1268 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Although the javax.management.modelmbean.DescriptorSupport does attempt to validate whether its fields are Serializable, it does not validate all of the values references. This causes failures when accessing mbeans over rmi as shown in this twiddle example: > [starksm@banshee9100 bin]$ twiddle.sh -s lamia:1099 invoke "jboss.web:service=WebServer" stopConnectors > 21:49:02,437 ERROR [Twiddle] Exec failed > java.lang.reflect.UndeclaredThrowableException > at $Proxy0.getMBeanInfo(Unknown Source) > at org.jboss.console.twiddle.command.InvokeCommand.invoke(InvokeCommand.java:173) > at org.jboss.console.twiddle.command.InvokeCommand.execute(InvokeCommand.java:277) > at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:288) > Caused by: java.io.NotSerializableException: org.jboss.mx.util.MBeanProxyExt > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) > at java.util.HashMap.writeObject(HashMap.java:978) > at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > at java.io.ObjectOutputStream.access$100(ObjectOutputStream.java:122) > at java.io.ObjectOutputStream$PutFieldImpl.writeFields(ObjectOutputStream.java:1475) > at java.io.ObjectOutputStream.writeFields(ObjectOutputStream.java:405) > at javax.management.modelmbean.DescriptorSupport.writeObject(DescriptorSupport.java:559) > at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > at java.io.ObjectOutputStream.access$100(ObjectOutputStream.java:122) > at java.io.ObjectOutputStream$PutFieldImpl.writeFields(ObjectOutputStream.java:1475) > at java.io.ObjectOutputStream.writeFields(ObjectOutputStream.java:405) > at javax.management.modelmbean.ModelMBeanAttributeInfo.writeObject(ModelMBeanAttributeInfo.java:312) > at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) > at java.rmi.MarshalledObject.<init>(MarshalledObject.java:92) > at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:364) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) > at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:135) > at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:163) > at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:103) > at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:60) > at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:55) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:91) > ... 4 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1193) Do-not-modify-URL-option for URLs in the WYSIWYG editor

by Nils Kassube (JIRA)

Do-not-modify-URL-option for URLs in the WYSIWYG editor ------------------------------------------------------- Key: JBPORTAL-1193 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1193 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final, 2.6.DR1 Reporter: Nils Kassube Assigned To: Roy Russo I'd like to have a "Do not modify URL" checkbox. So the URL is not munged in any way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1212) Fine Grained CMS permissions not accurately enforced in a clustered environment

by Sohil Shah (JIRA)

Fine Grained CMS permissions not accurately enforced in a clustered environment ------------------------------------------------------------------------------- Key: JBPORTAL-1212 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1212 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 Problem Explanation: Due to issues with JackRabbit internal caching, the PortalCMS Service is setup as a HA-Singleton service in a clustered environment. One side effect is that, when PortalCMS calls are made from nodes other than the singleton node, the User Principal is not propagated through the Singleton Proxy. Hence, the call is treated as an "Anoymous" user call instead of the currently "Logged In" User. Note: This is not an issue in a non-clustered environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-947) Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address

by Jay Howell (JIRA)

Clustered messaging throws exceptions when failover happens in the clustered postoffice - cannot find node ID for address ------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-947 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-947 Project: JBoss Messaging Issue Type: Bug Environment: Clusterd Messaging using Remoting 2.2.0 SP1 Reporter: Jay Howell Assigned To: Tim Fox The scenario is: - 172.26.101.67 starts messaging - 172.26.101.71 starts messaging and joins the cluster. The postoffices are now in a clustered state - Messaging on 172.26.101.71 is stopped. This causes the stack trace on 172.26.101.67 2007-04-19 15:58:46,675 DEBUG [org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179]: 172.26.101.67:52432 left 2007-04-19 15:58:46,675 ERROR [org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice] Caught Exception in MembershipListener java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address 172.26.101.67:52432 at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) at java.lang.Thread.run(Thread.java:595) 2007-04-19 15:58:46,675 ERROR [STDERR] Exception in thread "Thread-28" 2007-04-19 15:58:46,675 ERROR [STDERR] java.lang.IllegalStateException: ClusteredPostOffice[0:Clustered JMS:172.26.101.71:54179] cannot find node ID for address 172.26.101.67:52432 2007-04-19 15:58:46,675 ERROR [STDERR] at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.nodeLeft(DefaultClusteredPostOffice.java:1998) 2007-04-19 15:58:46,675 ERROR [STDERR] at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.access$1800(DefaultClusteredPostOffice.java:98) 2007-04-19 15:58:46,675 ERROR [STDERR] at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$HandleViewAcceptedRunnable.run(DefaultClusteredPostOffice.java:2400) 2007-04-19 15:58:46,675 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) 2007-04-19 15:58:46,675 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 2007-04-19 15:59:06,096 INFO [org.jboss.cache.TreeCache] viewAccepted(): [lonrs00341:54163|2] [lonrs00341:54163] 2007-04-19 15:59:07,046 WARN [org.jgroups.protocols.FD] ping_dest is null: members=[lonrs00337:52426 (additional data: 19 bytes), lonrs00341:5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
16
0 / 0

[JBoss JIRA] Created: (JBOSGI-17) Add permissions to the ClassLoadingSystem

by Adrian Brock (JIRA)

Add permissions to the ClassLoadingSystem ----------------------------------------- Key: JBOSGI-17 URL: http://jira.jboss.com/jira/browse/JBOSGI-17 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock The ClassLoadingSystem (and maybe others) needs permissions on at least who can define domains and register classloaders. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-16) Test the new ClassLoader with a SecurityManager enabled

by Adrian Brock (JIRA)

Test the new ClassLoader with a SecurityManager enabled ------------------------------------------------------- Key: JBOSGI-16 URL: http://jira.jboss.com/jira/browse/JBOSGI-16 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock The new ClassLoader needs to be tested with a security manager enabled and add Privileged blocks where appropriate. e.g. when getting resources from imports/delegates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007