January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3616) failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase

by Dimitris Andreadis (JIRA)

failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase ----------------------------------------------------------- Key: JBAS-3616 URL: http://jira.jboss.com/jira/browse/JBAS-3616 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testMBeanInfoMarshalling Failure Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL junit.framework.AssertionFailedError: Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL at org.jboss.test.jmx.test.RMIAdaptorUnitTestCase.testMBeanInfoMarshalling(RMIAdaptorUnitTestCase.java:72) -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-353) Add hibernate support for Messaging Store

by Mark Little (JIRA)

Add hibernate support for Messaging Store ----------------------------------------- Key: JBESB-353 URL: http://jira.jboss.com/jira/browse/JBESB-353 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Daniel Brum Fix For: 5.0 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1955) XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis closed JBAS-1955. ------------------------------------ Resolution: Done I've used the patch as a starting point to create an interceptor with plugable polices: org.jboss.jmx.connector.invoker.SerializableInterceptor org.jboss.jmx.connector.invoker.SerializablePolicy The default policy converts ModelMBeanInfo returned by getMBeanInfo into plain MBeanInfo, striping away the ModelMBeanAttribute infos that contain the non-serializable Descriptors that cause the trouble: org.jboss.jmx.connector.invoker.serializablepolicy.StripModelMBeanInfoPolicy This essentially emulates the behaviour we have with jboss 4.0.x when used with jdk1.4. I.e. you are able to read remotely over the jmx adapter MBeanInfo for all registered mbeans. Howerver, if you try to read non-serializable fields you still get a NonSerializableException. A different policy could be created to deal with this scenario, if necessary. The interceptor is enabled by default in deploy/jmx-invoker-service.xml: <interceptor code="org.jboss.jmx.connector.invoker.SerializableInterceptor" policyClass="StripModelMBeanInfoPolicy"/> Kudos to Fabiano for the original patch. > XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions > ----------------------------------------------------------------------------------- > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Feature Request > 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: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1 > > Attachments: JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1955) XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis updated JBAS-1955: ------------------------------------- Fix Version/s: JBossAS-4.2.0.CR1 JBossAS-5.0.0.Beta2 Description: This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. The interception have 3 types of action: Invisible, Null and Wrapper. In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. In the null mode NonSerializable fields are visible but always return Null. The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. was: This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. See http://jira.jboss.com/jira/browse/JBAS-1939 and The interception have 3 types of action: Invisible, Null and Wrapper. In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. In the null mode NonSerializable fields are visible but always return Null. The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. Issue Type: Feature Request (was: Patch) Summary: XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions (was: New Interceptor to InvokerAdaptorService that prevent NonSerializableException) Complexity: Medium Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Documentation (Ref Guide, User Guide, etc.)]) Priority: Major (was: Minor) > XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions > ----------------------------------------------------------------------------------- > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Feature Request > 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: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2 > > Attachments: JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1955) New Interceptor to InvokerAdaptorService that prevent NonSerializableException

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis updated JBAS-1955: ------------------------------------- Attachment: (was: JBAS-1955a.zip) > New Interceptor to InvokerAdaptorService that prevent NonSerializableException > ------------------------------------------------------------------------------ > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Patch > 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: Dimitris Andreadis > Priority: Minor > Attachments: JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. See http://jira.jboss.com/jira/browse/JBAS-1939 and > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1955) New Interceptor to InvokerAdaptorService that prevent NonSerializableException

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis updated JBAS-1955: ------------------------------------- Attachment: (was: JBAS-1955.zip) > New Interceptor to InvokerAdaptorService that prevent NonSerializableException > ------------------------------------------------------------------------------ > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Patch > 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: Dimitris Andreadis > Priority: Minor > Attachments: JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. See http://jira.jboss.com/jira/browse/JBAS-1939 and > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1955) New Interceptor to InvokerAdaptorService that prevent NonSerializableException

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis reassigned JBAS-1955: ---------------------------------------- Assignee: Dimitris Andreadis > New Interceptor to InvokerAdaptorService that prevent NonSerializableException > ------------------------------------------------------------------------------ > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Patch > 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: Dimitris Andreadis > Priority: Minor > Attachments: JBAS-1955.zip, JBAS-1955a.zip, JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. See http://jira.jboss.com/jira/browse/JBAS-1939 and > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-424) Add check of the jboss.partition.name to the @Clustered annotation

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-424?page=comments#action_12349832 ] Brian Stansberry commented on EJBTHREE-424: ------------------------------------------- This has been ported to trunk. There are unit test failures in BeanUnitTestCase testStatefulBeanFailover and testStatefulBeanCounterFailover that may or may not be related -- I'll close this once those are fixed or proven unrelated. > Add check of the jboss.partition.name to the @Clustered annotation > ------------------------------------------------------------------ > > Key: EJBTHREE-424 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-424 > Project: EJB 3.0 > Issue Type: Feature Request > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: EJB 3.0 RC10 - FD > > > The @Clustered annotation defaults to "DefaultPartition" rather than the value of system property jboss.partition.name. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-257) Optimisation for deliveries immediately returned as done

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-257?page=all ] Ovidiu Feodorov reopened JBMESSAGING-257: ----------------------------------------- > Optimisation for deliveries immediately returned as done > -------------------------------------------------------- > > Key: JBMESSAGING-257 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-257 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: 1.2.0.Beta2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Optimisation: If a delivery is returned as done. There is no need to first store the reference in the channel state as is currently the case. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-257) Optimisation for deliveries immediately returned as done

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-257?page=all ] Ovidiu Feodorov closed JBMESSAGING-257. --------------------------------------- Fix Version/s: 1.2.0.Beta2 Resolution: Won't Fix Fix Version/s: (was: 1.2.1) > Optimisation for deliveries immediately returned as done > -------------------------------------------------------- > > Key: JBMESSAGING-257 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-257 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: 1.2.0.Beta2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Optimisation: If a delivery is returned as done. There is no need to first store the reference in the channel state as is currently the case. -- 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, 4 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 January 2007