December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-272) isPassive in FTP EPR?

by Mark Little (JIRA)

isPassive in FTP EPR? --------------------- Key: JBESB-272 URL: http://jira.jboss.com/jira/browse/JBESB-272 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Priority: Optional Fix For: 5.0 Should isPassive be part of the EPR or the configuration information? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1939) MBean getAttribute() launch NotSerializableException when invoked from a remote client

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1939?page=all ] Dimitris Andreadis updated JBAS-1939: ------------------------------------- Fix Version/s: JBoss-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > MBean getAttribute() launch NotSerializableException when invoked from a remote client > -------------------------------------------------------------------------------------- > > Key: JBAS-1939 > URL: http://jira.jboss.com/jira/browse/JBAS-1939 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.2 Final > Environment: jmx, twiddle > Reporter: Fabiano C. de Oliveira > Assigned To: Clebert Suconic > Priority: Minor > Fix For: JBoss-4.2.1.CR1 > > > when executing twiddle to get attribute from some MBeans a NotSerializableException java.io.NotSerializableException is launched. > To reproduce this just type: > D:\jboss-4.0.2\bin>twiddle.bat get "jboss.web:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,name=//localhost/" logger > How can this can be fixed ? Ignoring the Non serializable attributes, returning null to Nonserializable attributes, become invisible all non-serializable attribute ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1908) listMessageCounter issue with JMS subscriptions containing certain message selector characters

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1908?page=all ] Dimitris Andreadis updated JBAS-1908: ------------------------------------- Fix Version/s: JBoss-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) reschedule > listMessageCounter issue with JMS subscriptions containing certain message selector characters > ---------------------------------------------------------------------------------------------- > > Key: JBAS-1908 > URL: http://jira.jboss.com/jira/browse/JBAS-1908 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.2 Final > Environment: Windows XP Professional, JDK1.4.2_06, JBoss 4.0.2 > Reporter: Jaco Joubert > Priority: Minor > Fix For: JBoss-4.2.1.CR1 > > Attachments: DestinationManager.txt, DestinationMBeanSupport.txt, listCounter.jar, MessageCounter.txt, test-topic-service.xml > > > When the message selector query for a subscription to a JMS topic looks someting like "field in ('A', 'B', 'C')", two failures occur on JMS MBeans: > 1. The listMessageCounter operation on jboss.mq:service=DestinationManager fails with a NumberFormatException: > Caused by: java.lang.NumberFormatException: For input string: " 'ghi'" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:468) > at java.lang.Integer.parseInt(Integer.java:518) > at org.jboss.mq.server.jmx.DestinationManager.listMessageCounter(DestinationManager.java:477) > 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > ... 44 more > This is because the getCounterAsString() method is used on the MessageCounter to get the details and then traversed with > a StringTokenizer tokenizing on commas, but the subscription name also contains commas in this case. > 2. The listMessageCounter operation on jboss.mq.destination:name=[topicName],service=Topic works, but the resulting HTML > table has some of the selector values populating the counter columns. The problem is because of the same issue as above. > > This can be reproduced by following these steps: > 1. Startup a JBoss4.0.2 with default configuration. > 2. Deploy the attached 'test-topic-service.xml'. This will create a JMS topic called 'counterTestTopic'. > 3. Run the attached client (source included in jar). The only jar needed on classpath is the 'jbossall-client.jar': > java -cp "[path]\jbossall-client.jar;.\listCounter.jar" za.co.jdj.jbossmq.testcounter.TestListCounter > This will do the following: > 3.1. Connect to the JMS server running locally. > 3.2. Create a publisher and durable subscriber on the 'counterTestTopic' already deployed. > The subscriber has a message selector in the format already described > 3.3. Invoke the listMessageCounter operation on jboss.mq:service=DestinationManager, printing the error. > 3.4. Wait for the client to look at the html table created by the topic in a browser. > 3.5. Remove the subscription and exit. > > Suggested fixes for the problem includes: > 1. Add a getDestinationTypeDescription() method to org.jboss.mq.server.MessageCounter. (See MessageCounter.txt attached) > 2. Change the listMessageCounter method on org.jboss.mq.server.jmx.DestinationManager to not use the getCounterAsString() method > on org.jboss.mq.server.MessageCounter, but rather extract the values itself for the html table. > (See the DestinationManager.txt file attached). > 3. Change the listMessageCounter method on org.jboss.mq.server.jmx.DestinationMBeanSupport to do the same as above. > (See the DestinationMBeanSupport.txt file 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-464) LDAP implementation of UserModule and RoleModule

by Boleslaw Dawidowicz (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-464?page=all ] Boleslaw Dawidowicz resolved JBPORTAL-464. ------------------------------------------ Resolution: Duplicate Issue Assignee: Boleslaw Dawidowicz Duplicated with issue http://jira.jboss.com/jira/browse/JBPORTAL-1048 This issue contains attached implementation against MSAD that can be used with JBP 2.2 > LDAP implementation of UserModule and RoleModule > ------------------------------------------------ > > Key: JBPORTAL-464 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-464 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Identity > Affects Versions: 2.2 Final, 2.0 Final > Reporter: Julien Viet > Assigned To: Boleslaw Dawidowicz > Fix For: 2.6.Alpha1 > > Attachments: MSADLoginModule.zip, org.zip > > Original Estimate: 1 week > Time Spent: 1 week > Remaining Estimate: 0 minutes > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-218) Add 'forall' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-218?page=comments#action_12348421 ] Edson Tirelli commented on JBRULES-218: --------------------------------------- $ svn log -r 8226 -v ------------------------------------------------------------------------ r8226 | tirelli | 2006-12-11 11:39:38 -0300 (Mon, 11 Dec 2006) | 1 line Changed paths: M /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_OrWithBindings.drl M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/GroupElement.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/LogicTransformer.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/rule/LogicTransformerTest.java M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_processTree1.dat M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_transform1.dat JBRULES-218: modifying logical transformations to ensure element order is kept over transformations ------------------------------------------------------------------------ > Add 'forall' Conditional Element > -------------------------------- > > Key: JBRULES-218 > URL: http://jira.jboss.com/jira/browse/JBRULES-218 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > > Add 'forall' Conditional Element -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-370) Implement flushing for service views in Multiplexer

by Bela Ban (JIRA)

Implement flushing for service views in Multiplexer --------------------------------------------------- Key: JGRP-370 URL: http://jira.jboss.com/jira/browse/JGRP-370 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.4.1 -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-365) RpcDispatcher without registered membership listener is causing BLOCK timeout

by Vladimir Blagojevic (JIRA)

RpcDispatcher without registered membership listener is causing BLOCK timeout ----------------------------------------------------------------------------- Key: JGRP-365 URL: http://jira.jboss.com/jira/browse/JGRP-365 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic If RpcDispatcher is used *and* membership listener used to construct RpcDispatcher is null then BLOCK event will always timeout whenever FLUSH protocol is in stack. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBRULES-218) Add 'forall' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-218?page=comments#action_12348413 ] Edson Tirelli commented on JBRULES-218: --------------------------------------- $ svn log -r 8218 -v ------------------------------------------------------------------------ r8218 | tirelli | 2006-12-11 08:57:51 -0300 (Mon, 11 Dec 2006) | 1 line Changed paths: M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/semantics/java/RuleBuilder.java M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/compiler/PackageBuilderTest.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/ReteooBuilder.java D /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/And.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Column.java D /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Exists.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/GroupElement.java A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/GroupElementFactory.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/LogicTransformer.java D /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Not.java D /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Or.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Rule.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/examples/manners/BaseMannersTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/rule/GroupElementTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/rule/LogicTransformerTest.java M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_processTree1.dat M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_transform1.dat JBRULES-218: refactoring logical transformation to allow future development of forall > Add 'forall' Conditional Element > -------------------------------- > > Key: JBRULES-218 > URL: http://jira.jboss.com/jira/browse/JBRULES-218 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > > Add 'forall' Conditional Element -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-718) Expose monitoring informations for JBoss ON

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-718?page=comments#action_12348411 ] Thomas Heute commented on JBPORTAL-718: --------------------------------------- Metrics are exposed on JBoss Portal side, now JBoss ON needs to use those values. > Expose monitoring informations for JBoss ON > ------------------------------------------- > > Key: JBPORTAL-718 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-718 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.6 Final > Reporter: Julien Viet > Assigned To: Thomas Heute > Fix For: 2.6.Alpha1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-718) Expose monitoring informations for JBoss ON

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-718?page=all ] Thomas Heute reassigned JBPORTAL-718: ------------------------------------- Assignee: Thomas Heute > Expose monitoring informations for JBoss ON > ------------------------------------------- > > Key: JBPORTAL-718 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-718 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.6 Final > Reporter: Julien Viet > Assigned To: Thomas Heute > Fix For: 2.6.Alpha1 > > -- 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, 7 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 December 2006