[JBoss Messaging] - Re: Can only send one message in XA transaction
by orankelly
"timfox" wrote : Yes please let's take Spring out of the equation. If you can demonstrate an issue using an MDB we can investigate further...
Famous last words indeed.
The root cause is some oddness with Spring's listener interacting with the tx manager. So the sending side was working but the listener was not getting all of the messages. As yet I have no idea why but if I stop populating the DefaultMessageListenerContainer's transactionManager property, all the messages are received.
When I deployed the simple MDB (identical code to that SimpleListener I posted earlier), all the messages were received correctly. I noticed some very odd behaviour with this new conf though, whereby my original listener, which I still had deployed, occasionally saw more than one message delivered - but never got all 3 and usually only got the first one.
Anyhoo - not a JBM issue!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191777#4191777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191777
17 years, 7 months
[JBoss jBPM] - Re: jBPM 3.3.0GA and Oracle causing StaleObjectStateExceptio
by xnejp03
I'll re-open the JIRA, thanks. I tried to put back in the flush() into thetrunk code but getting this exception:
14:57:10,318 ERROR [GraphElement] action threw exception: collection [org.jbpm.bytes.ByteArray.byteBlocks] was not processed by flush()
| org.hibernate.AssertionFailure: collection [org.jbpm.bytes.ByteArray.byteBlocks] was not processed by flush()
| at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:205)
| at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(AbstractFlushingEventListener.java:333)
| at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:28)
| at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
| at org.jbpm.graph.node.Join.execute(Join.java:121)
| at org.jbpm.graph.def.Node.enter(Node.java:314)
| 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:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
| at org.jbpm.graph.def.Node_$$_javassist_179.enter(Node_$$_javassist_179.java)
| at org.jbpm.graph.def.Transition.take(Transition.java:151)
| at org.jbpm.graph.def.Node.leave(Node.java:389)
| at org.jbpm.graph.exe.Token.signal(Token.java:192)
| at org.jbpm.graph.exe.Token.signal(Token.java:140)
| at uk.co.ondemand.portal.workflow.actions.AbstractNodeActionHandler.execute(AbstractNodeActionHandler.java:50)
| at org.jbpm.graph.def.Action.execute(Action.java:129)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)........
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191775#4191775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191775
17 years, 7 months
[Microcontainer] - Re: BeanMetaData and management
by alesj
"bob.mcwhirter" wrote :
| My "already installed" error occurs when I get the @JMX annotation on the correct class, but give my object a bogus MC bean name (in this case "jboss.rails:name=oddthesis").
|
This is the code that creates the name:
- http://anonsvn.jboss.org/repos/jbossas/trunk/system-jmx/src/main/org/jbos...
If your bean name contains ':' it's gonna be used.
"bob.mcwhirter" wrote :
| The error I was getting is here, in case you're interested. "Already installed" was somewhat confusing of an error to get.
|
| http://oddthesis.pastebin.com/f46537bdf
|
You have duplicated name.
Your bean and mbean are named the same, hence MC Controller complained.
Thinking about how we create the name, it's not very good.
I'll raise an issue about this.
"bob.mcwhirter" wrote :
| I see I can set the 'name' parameter on @JMX, but is there another way to dynamically set the JMX object-name (to include some bit of unit.getSimpleName() perhaps) like I think the @ManagementObjectID annotation supports on that side of things? Ultimately, I think I'd like to end up with "jboss.rails:name=#{unit.getSimpleName()}" or similar.
|
The problem here is that when @JMX interceptor kicks in,
you don't have access to DeploymentUnit, since you might even not have any DU.
e.g. programmatic ControllerContext installation
But I'll check what can be done,
to make name creation as configurable as possible.
e.g. pulling some info from CC's MetaData
"bob.mcwhirter" wrote :
| Or should I give up, admit JMX is dead, and move on?
|
It depends how much work is there.
For now I would still use it.
But as soon as you see some lively movement in jopr/embedded wrt PS,
I would change to ManagedObject.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191766#4191766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191766
17 years, 7 months