]
Lukáš Fryč commented on RF-10883:
---------------------------------
Clayton, this is the version of 4.1.0.M2 which you should use in Maven: 4.1.0.20110910-M2
If it won't work, could you please create new issue (since this was already closed and
your issue seems as different one).
It would be great if you could provide sample WAR which is running on GlassFish except the
a4j:push component.
PUSH doesn't work properly on Glassfish 3.1 (JMS issue I think)
---------------------------------------------------------------
Key: RF-10883
URL:
https://issues.jboss.org/browse/RF-10883
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: Glassfish 3.1
Reporter: Pablo Martinez
Assignee: Nick Belaevski
Labels: glassfish, jms, push, richfaces, tran
Fix For: 4.1.0.Milestone1
Attachments: GF_Push_JMS0.PNG
When trying to make this PUSH example to work
(
http://in.relation.to/Bloggers/GettingStartedWithRichFaces40Push) on glassfish 3.1,
I'm getting this error:
javax.jms.JMSException: MQJMSRA_DC2001:
Unsupported:setClientID():inACC=false:connectionId=6046697373872048384
I think the problem comes from this line of code
{code:title=org.richfaces.application.push.impl.jms.MessagingContext.java|borderStyle=solid}
//TODO - review
try {
//durable subscription requires ClientID to be set
connection.setClientID(UUID.randomUUID().toString());
} catch (IllegalStateException e) {
//ignore - clientId has already been set
}
{code}
I builded richfaces 4 from scratch (only the richfaces-core-api and richfaces-core-impl)
removing that line, and the error disapeared. I setted the ClientId using the
create-jms-resource on glassfish admin console.
Now, after that, the app "works" BUT, I don't get the notifications on the
client side (web), I can only send messages to the irc and stuf, but don't see any
change on the web app (I confirm this because I use another IRC client to see what
happens).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: