After I fixed this, I had a few messages being paged on management, and I had a few small bugs around the executors and depaging (which I'm fixing now).
But now there is another issue regarding management destinations. (as noted on this user thread also):
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248264#4248264
Mangement address and temporary addresses shouldn't go into page mode IMO.
I thought the management address won't have a queue, if there are no consumers.. what would mean messages are dropped on that case. (Right?)
And we shouldn't probably page temporary queues. As when the connection is dead.. the data should be deleted.. right? An user should aways have a consumer on a temporary queue?
This should be an easy change If there is an easy way to determine if an address is management or temporary. (if we all agree with the change).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248265#4248265
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248265
In EE6 ValidatorFactory and Validator are services available to:
- other services like JCA, JPA, JSF 2 (typically available before these)
- the user application via JNDI and @Resource injection
What's the way to get that integrated?
The typical use case is one VF per application deployed. But we are discussing with Sun and the idea of one VF per module could have to be implemented (ie like JSR-299 and beans.xml)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248240#4248240
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248240
Hi all,anonymous wrote :
|
| I have followed the instructions on the quick start post and I get this message:
|
| this is the new DLL
| | Running process on Windows 6064
| | JBoss Tracer: Enabling Exceptions/Errors
| | ERROR: JVMPI, an experimental interface, is no longer supported.
| | Please use the supported interface: the JVM Tool Interface (JVM TI).
| | dpInspector> error in obtaining jvmpi interface pointer
| | Error occurred during initialization of VM
| | -Xrun library failed to init: jbossInspector
| |
| | I am running Java 1.6.0_13 and jboss-5.1.0.GA and attempting to also use the JVMTI memory inspector.
| |
| | Is there any work around?
| |
| | Thanks!
| |
| |
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248228#4248228
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248228
Hi Tom,
the CEO of my company has asked me for a brief explanation of what it means to contribute this code - from a legal point of view - to JBPM.
I know that we will be releasing the code under the terms of the LGPL. Are there any other considerations I should be aware of? I looked on the JBoss site but I couldn't find any FAQ or other document that explained this. Is it possible for me to provide him with a copy of the Contributor agreement (I will be using the Corporate agreement type)?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248202#4248202
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248202
When you have size > globalMaxSize, routing is aways routing at least one message before it enters into page mode.
We shouldn't messages being routed when size > globalMaxSize. Page should send the messages to a file on this situation, and the current code is aways sending a few messages before it enters into this situation.
I need to investigate a little bit more. I will post an update shortly.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248199#4248199
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248199