[JBoss JIRA] Updated: (JBMESSAGING-275) Move Selector processing IN the Channel
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ]
Ovidiu Feodorov updated JBMESSAGING-275:
----------------------------------------
Fix Version/s: 1.2.0.Alpha2
(was: 1.2.0.Alpha1)
> Move Selector processing IN the Channel
> ---------------------------------------
>
> Key: JBMESSAGING-275
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275
> Project: JBoss Messaging
> Issue Type: Task
> Components: Messaging Core
> Reporter: Ovidiu Feodorov
> Assigned To: Tim Fox
> Priority: Critical
> Fix For: 1.2.0.Alpha2
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector.
> This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers.
> A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor.
--
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, 8 months
[JBoss JIRA] Commented: (EJBTHREE-402) Remoting proxies are not declaring serialVersionUIDs
by Andrew Rubinger (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-402?page=comments#action_12344246 ]
Andrew Rubinger commented on EJBTHREE-402:
------------------------------------------
Ignore above comments; wrong version patched and checked.
> Remoting proxies are not declaring serialVersionUIDs
> ----------------------------------------------------
>
> Key: EJBTHREE-402
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-402
> Project: EJB 3.0
> Issue Type: Bug
> Affects Versions: EJB 3.0 RC3
> Reporter: Scott M Stark
> Priority: Critical
> Fix For: EJB 3.0 RC10 - FD
>
>
> Same old lack of explicit serialVersionUIDs causing major incompatibilities across releases:
> java: org.jnp.interfaces.NamingContext@bd0108
> Looking up RemoteCalculator
> javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126]
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at trail.client.RemoteCalculatorClient.main(RemoteCalculatorClient.java:38)
> Caused by: java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
> at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
> at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:57)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:637)
--
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, 8 months
[JBoss JIRA] Created: (JBAS-3454) Unable to set negative values for MBean attributes using Twiddle command
by Sakthi Samabsivam (JIRA)
Unable to set negative values for MBean attributes using Twiddle command
--------------------------------------------------------------------------
Key: JBAS-3454
URL: http://jira.jboss.com/jira/browse/JBAS-3454
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.3 SP1
Reporter: Sakthi Samabsivam
Priority: Minor
When a customer tries to execute twiddle to set a negative value for one of the attributes, it throws the exception.
For example when I try to set a Scheduler MBean InitialRepitions value to -1, it fails.
Command: twiddle set "jboss:service=Scheduler" "InitialRepetitions" "-1".
Possible problem might be, GetOpt class used in the org.jboss.console.twiddle.SetCommand Class is not accepting the -ve values.It consider the -ve numbers as
an invalid option.
--
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, 8 months
[JBoss JIRA] Resolved: (JBPORTAL-823) Access to Portlet Action Request in LayoutStragegy
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-823?page=all ]
Roy Russo resolved JBPORTAL-823.
--------------------------------
Fix Version/s: 2.4.1 Final
2.6.Alpha1
Resolution: Won't Fix
Assignee: Roy Russo
> Access to Portlet Action Request in LayoutStragegy
> --------------------------------------------------
>
> Key: JBPORTAL-823
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-823
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal Theme
> Affects Versions: 2.2 Final
> Environment: Any
> Reporter: patrickdalla
> Assigned To: Roy Russo
> Fix For: 2.4.1 Final, 2.6.Alpha1
>
>
> I want to maximize a portlet when the user clicks in the edit button.
> I've made this using the layoutStrategy to chage the WindowState if strategyContext.getTargetPortlet().getPortletMode() is equal Mode.EDIT.
> But, after the portlet is in edit mode, I cannot chage his WindowState.
> I would like a way to change the windowstate when the user clicks the edit button but after in edit mode he could minimize the portlet or change the window state.
> Maybe if I could access de ActionRequest in LayoutStrategy.
--
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, 8 months
[JBoss JIRA] Created: (JBPORTAL-956) "no selection" for Theme Leads to Null Pointer Exception
by Richard Mitchell (JIRA)
"no selection" for Theme Leads to Null Pointer Exception
--------------------------------------------------------
Key: JBPORTAL-956
URL: http://jira.jboss.com/jira/browse/JBPORTAL-956
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Environment: Fedora Core 5
Reporter: Richard Mitchell
I was experimenting with theme selection in 2.4.0-CR1. I tried each of the four defined ones which each worked great. I then tried "no selection" to see how that behaved. I received an HTTP 500 error with a Null Pointer Exception whenever I went to a page from that point forward.
I hadn't really "customized" much yet so that, after suggested in the user forum, I blew away the database. All is fine now. I am avoiding that "no selection" entry though.
--
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, 8 months