May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-811) release-admin.xml breaks during messaging configuration creation while trying to install JBossTS

by Ovidiu Feodorov (JIRA)

release-admin.xml breaks during messaging configuration creation while trying to install JBossTS ------------------------------------------------------------------------------------------------ Key: JBMESSAGING-811 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-811 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.CR1 -- 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

19 years, 2 months

4
9
0 / 0

[JBoss JIRA] Resolved: (JBAS-2315) Create an automated test for JBAS-2314

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2315?page=all ] Hany Mesha resolved JBAS-2315. ------------------------------ Resolution: Done Added test method to both clustered and single server single sign on test cases to test JBAS-2314 > Create an automated test for JBAS-2314 > -------------------------------------- > > Key: JBAS-2315 > URL: http://jira.jboss.com/jira/browse/JBAS-2315 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > I currently test the JBAS-2314 fix manually; need to automate. Basically need to add a war to web-sso.ear that has secured resources but no authenticator configured. Test should access the normal sso test war on one server, then the other, and then on the 2nd server access the war w/o authenticator, confirming that no 403 is seen. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-750) 3.1-M1: java.lang.VerifyError: Shadow Fact problem?

by Michael Anstis (JIRA)

3.1-M1: java.lang.VerifyError: Shadow Fact problem? --------------------------------------------------- Key: JBRULES-750 URL: http://jira.jboss.com/jira/browse/JBRULES-750 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Environment: Windows XP SP2, JVM1.4 Reporter: Michael Anstis Assigned To: Mark Proctor Attachments: jira-750.jar Given a very simple rule:- package drools.debug rule "Test1" when $m : Machine ( ) then System.out.println("--> DEBUG!"); end Throws a very unfriendly error:- Exception in thread "main" java.lang.VerifyError: (class: drools/debug/MachineShadowProxy, method: setProperty signature: (Ljava/lang/String;JLjava/lang/String;)V) Register 3 contains wrong type at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.getConstructor(Unknown Source) at org.drools.base.ClassObjectType.getShadow(ClassObjectType.java:123) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:148) at org.drools.reteoo.Rete.assertObject(Rete.java:121) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:196) at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:68) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:724) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:543) at drools.debug.Setup.main(Setup.java:42) The Machine Class does extend another that has assessors for a Class that has lots and lots of constructors... Complete re-producible JAR attached. -- 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

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-14) Replace SecurityAssociation with Security SPI

by Anil Saldhana (JIRA)

Replace SecurityAssociation with Security SPI --------------------------------------------- Key: SECURITY-14 URL: http://jira.jboss.com/jira/browse/SECURITY-14 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 There is a need to move the legacy SecurityAssociation context to the Security SPI. -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-13) Authorization Framework should work off of the roles in the Security Context

by Anil Saldhana (JIRA)

Authorization Framework should work off of the roles in the Security Context ---------------------------------------------------------------------------- Key: SECURITY-13 URL: http://jira.jboss.com/jira/browse/SECURITY-13 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 There has been a discussion going on with reference to a Security Context in JBossSX. Refer to the forum thread As it stands, the Security Context is populated with the roles for the authenticated user, but the access checks that are happening (mainly for the jacc layer) needs to move away from the reliance on the role-group placed as a principal in the authenticated subject, but to use the roles in the Security Context. -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-946) JmsXA should behave the same way as JBossMQ

by Clebert Suconic (JIRA)

JmsXA should behave the same way as JBossMQ ------------------------------------------- Key: JBMESSAGING-946 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-946 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.SP1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2, 1.0.1.SP5 This is the same issue as JBMESSAGING-410 -- 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

19 years, 2 months

2
9
0 / 0

[JBoss JIRA] Resolved: (JGRP-158) Make TUNNEL a subclass of TP

by Vladimir Blagojevic (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-158?page=all ] Vladimir Blagojevic resolved JGRP-158. -------------------------------------- Fix Version/s: 2.5 (was: 2.x) Resolution: Done Resolved in 2.5. Affected file: TUNNEL.java 1.37 -> 1.38 > Make TUNNEL a subclass of TP > ---------------------------- > > Key: JGRP-158 > URL: http://jira.jboss.com/jira/browse/JGRP-158 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Priority: Minor > Fix For: 2.5 > > > Then properties such a bundling and version checking will be available in TUNNEL 'for free' -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-489) Out-of-memory with Tunnel and Isolating Nodes

by sampangi apparao (JIRA)

Out-of-memory with Tunnel and Isolating Nodes --------------------------------------------- Key: JGRP-489 URL: http://jira.jboss.com/jira/browse/JGRP-489 Project: JGroups Issue Type: Task Environment: Windows & Linux- JGroups2.5.0-beta-1 version, JDK1.5 Reporter: sampangi apparao Assigned To: Bela Ban I am new bee to the JGroups. I am trying to run demo program Draw by using TUNNEL protocol stack i.e tunnel.xml. I had two different subnets 172.x.x.x and 10.x.x.x and the GossipRouter running on 172.x.x.x. In the begining the two Draw instance are identifying each other and I can able to see drawing reflections on both nodes. After couple of minutes the two instances were isolating and another issue was identified that if we run multiple instances running on the same machine also reflecting same problem. The following error was observed during execution time And Gossip routger arguments...-bind_addr 172.16.2.49 -port 5556 336512 [TRACE] GossipRouter.mainLoop(): - REGISTER(DrawGroupDemo, 172.16.2.49:2238) 10.0.6.2:55214 closed connection; removing it from routing table 364342 [TRACE] GossipRouter.route(): - cannot find 10.0.6.2:33155 in the routing table, routing table= GROUP: 'DrawGroupDemo' logical addr=172.16.2.49:2238 (172.16.2.49:2239), 7829 ms old logical addr=10.0.6.2:33156 (10.0.6.2:52123), 9985 ms old logical addr=172.16.2.49:2329 (172.16.2.49:2330), 4907 ms old logical addr=172.16.2.49:2249 (172.16.2.49:2250), 3047 ms old ... ... 372373 [TRACE] GossipRouter.mainLoop(): - CONNECT(DrawGroupDemo, 10.0.6.2:33155) 372983 [TRACE] GossipRouter.mainLoop(): - REGISTER(DrawGroupDemo, 10.0.6.2:33155) 375280 [ERROR] Util$1.uncaughtException(): - uncaught exception in Thread[SocketThread 12,5,JGroups] (thread group=org.jgroups.util.Util$1[name=JGroups,maxpri=10] ) java.lang.OutOfMemoryError: Java heap space 375717 [TRACE] GossipRouter$SocketThread.run(): - ENGG-RAOS.us.packetmotion.com:2239 closed connection; removing it from routing table -- 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

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Closed: (JBRULES-272) "in" keyword in column constraints

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-272?page=all ] Mark Proctor closed JBRULES-272. -------------------------------- Fix Version/s: 4.0.0.MR2 (was: 4.0.0.MR3) Resolution: Duplicate Issue > "in" keyword in column constraints > ---------------------------------- > > Key: JBRULES-272 > URL: http://jira.jboss.com/jira/browse/JBRULES-272 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.0-rc3 > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 4.0.0.MR2 > > > So we can support things like > Person(status in [1,2,3]) > where it creates a set from the right hand operand and checks for existence of the left. > May be tricky with literals versus bound vars, but should be possible. Parser will need to be able to pass an array I think. > This means the Descrs will need to be modified - or is it only literals supported? -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBRULES-37) non DSL based NLP for simple predicates

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-37?page=all ] Mark Proctor closed JBRULES-37. ------------------------------- Fix Version/s: 4.0.0.MR2 (was: 4.0.0.MR3) Resolution: Out of Date > non DSL based NLP for simple predicates > --------------------------------------- > > Key: JBRULES-37 > URL: http://jira.jboss.com/jira/browse/JBRULES-37 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rule Assemply/SPI > Affects Versions: 3.0-beta1 > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 4.0.0.MR2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Should be based on a config file, which spels out what possesive strings are, conjunctions etc, what are redundant > So we can do: > The Dog's name is fido and its age is less than 2 > Dog(name=="fido", age < 2) > ['s] is possesive, [is] is the operator, [its] references the Fact, The is stripped out etc. > basic format of > {fact, field, opr, arg} conjuntion {repeat} > [08:54] <bob> if default lang could do cheesy reflection name-based stuff, perhaps? > [08:54] <bob> turning verbs into methods by reflection? > [08:54] <bob> w/o any specific mappings? > [08:54] <bob> <-- cluefree > [08:55] <bob> import com.myco.pets.* > [08:56] <bob> ... > [08:56] <bob> dog name is "Ted" > [08:56] <bob> Dog( name='Ted' ) > [08:56] <bob> etc > [08:56] <bob> purely very basic by default > [08:56] <bob> or am I thinking about it wrong? > [08:56] <bob> mic! > [08:56] <bob> stop perving > [08:56] <bob> start IRCing! > [08:58] <mic> bob: yeah can do that to > [08:58] <mic> started working on something like that, but on the back burner for the moment > [08:58] <mic> of course, need to know that it is a Dog object to do reflection etc... > [08:58] <mic> but thats more of a 3.1 thing > [08:59] <mic> would be a seperate expander > [09:00] <bob> yah, string[0] is a noun, search imports for class named string[0] > [09:00] <bob> 'k > [09:00] <bob> noun attribute operator value > [09:00] <bob> filter out throw-away words like "a" "the" etc -- 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

19 years, 2 months

1
0
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 May 2007