I have an MDB attached to a JBoss JMS queue. The MDB uses a custom
invoker-proxy-binding as well as a custom container-configuration.
The invoker-proxy-binding has the following settings:
|
| 1
| 1
The container-configuration has the following settings:
|
|
| 100
| 1
Sorry for the confusion on my part. I was distracted by the jira link you
posted that was referring to two MDBs in different jars with the same name.
Adding to the jboss.xml as you described, got rid of the
random number on the JMX service name.
|
| InvokerMDB
|
Thanks for the info. However, non of my MDB share the same names.
Here the are in 3.2.4:
binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB
|
binding=workflow-invoker-light-weight-mdb,jndiName=local/InvokerLWMDB,plugin=invoker,service=EJB
|
In upgrading from 3.2.4 to 3.2.7 and have discovered that the JMX service names
for MDBs have changed.
In 3.2.4 it was:
jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB
In 3.2.7 it is:
jboss.j2ee:binding=workflow-invoker-heavy-weight
You need to make sure your Sybase stored procedure is set to "Any" mode.
For example: EXEC sp_procxmode '','anymode'
This will allow the transaction for the stored procedure to be controlled by external
clients (ie the JBoss container). It will also work with local clients as well, thus
the "A
One detail I forgot to include is that I'm using custom invoker-proxy-bindings and
container-configs that are deployed with my MDBs. The default invoker-proxy-bindings
that ship with JBoss haven't been touched.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=
If the JMS_JBOSS_REDELIVERY_LIMIT in the JMS message header is set to a value higher
then the MaxTimesRedelivered setting of the DLQConfig in the invoker-proxy-binding
used by the MDB, the MDB will retry 1+ the MaxTimesRelivered max value, and then drop
the message instead of forwarding it to th
You are using local transactions which is exactly why you are getting the warning.
This has been discussed many different times on this forum.
RequiresNew will not prevent the warning you are seeing either. You are branching the
local transaction and as such, your database operations will not
If you are using Jetty, you need to set the following System property ..
-Dorg.mortbay.http.HttpRequest.maxFormContentSize={max num bytes}
Jetty has a small default limit on form posts as a safety precaution.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3
I'm not as worried about being database portable since where I work is Sybase IQ (data
warehouse) centric and probably will be for quite sometime to come.
Plus, what I'm doing with the Sybase JDBC driver IS portable to any Java application
be it an app server or standalone as long as what comes
I'm posting this as an FYI for those migrating from prior 3.2.x version to the latest
3.2.4 version of JBoss.
The ResultSet class returned from a Statement.executeQuery() (and any other JDBC call)
call is now a org.jboss.resource.adapter.jdbc.WrappedResultSet class type and not the
ResultSet cl
Thanks for the feedback, but I'm not sure what you say is correct in this case.
In 3.2.3, the jmx.managed-parameter name attribute was just the name that would be
displayed above the input field on the jmx-console gui. It had nothing to do with the
actual name of the parameter being passed i
In migrating from 3.2.3 to 3.2.4, I found that spaces in the XDoclet managed-parameter
name attribute of an XMBean no longer work. For example:
* @jmx.managed-parameter name="Some Name" type="java.lang.String" description="Some
Description"
When the resulting SAR is deployed, JBoss 3.2.4 thr
Sorry, the xml got stripped off in the previous post.
| 1
| 1
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834494#3834494
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834494
You also need to set the following in your invoker-proxy-binding as well.
1
1
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834493#3834493
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834493
I would add to that the 3 series has a much better organized and understandable
configuration and directory structure layout. All services are nicely split out in to
various configuration files (some even have their own sub directories) unlike the 2
series where you had a very monolithic single
JBoss 3.2.3, W2K, Sun JVM 1.4.2-b28
On the server side, I have multiple JMS queues that have EJBs posting messages to
various queues using a ConnectionFactory obtained via "java:/JmsXA". I also have
MDBs attached to some of the queues firing into the EJB tier. Everything is CMT.
On the clien
You can also lookup the "OriginatingQ" property in the message header to see what
Queue the message came from prior to being put on the DLQ. JBoss does populate this
properly, and I presume that all other JMS providers do as well.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=382577
First, go to http://localhost:8080/jmx-console, find your queue name and click on it.
There you will find all the parameters you can tweak including a way to flush the
queue of any messages it contains.
As far as pushing message back on to a queue from the DLQ there is no JMX based
solution fo
Slight correction:
This line:
* @jmx.managed-parameter name="key" type="java.lang.String" description=“Key of
Task”
should read:
* @jmx.managed-parameter name="key" type="java.lang.String" description="Key of Task";
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825398#3825398";
If you use XDoclet (and if you don't, you should), it's pretty simple to create the
Model XMBean for JBoss with param annotations.
For example:
/**
* @jmx:mbean name="MyApplication:service=MyJMX"
* @jboss.service servicefile="jboss"
* @jboss.xmbean
*/
public class MyJMX implements MyJMXMBean
On my P4 1.7ghz W2K box with 512mg of RAM, the default JBoss target starts in about 1
minute. The All target is slightly longer because it deploys more services then
default does.
This, of course, will change as you add or take away services from your own custom
target.
http://www.jboss.org
Can't help with the Oracle integration, but I can with where to configure your MDB
pools.
There are two basic ways to accomplish this.
If you wish to use the JBoss defaults and just tweak the settings, then go to the
server//conf/standardjboss.xml file and look at both the proxy-binding-confi
.. and obviously I have downloaded it and used it. :)
I noticed that Hypersonic isn't LGPL either. But that's a different topic for a
different thread.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824951#3824951";>View
the original post
http://www.jboss.org/index.html?module=b
For more info: http://www.mckoi.com
McKoi's license is GPL.
I don't know if it is worth the effort or not. McKoi does have transaction isolation
but does not have XA support (at least any that I could find). I am currently using
McKoi as an embedded test database via a -ds.xml file, but not f
I keep seeing posts like the one above that say that using Hypersonic for JMS JDBC
persistence is not recommended. While I probably wouldn't argue with that point, I do
not understand then why it is still, after all these years, included as a default in
JBoss then.
Certainly there are other
Is there a way in JBoss 3.2.3 (or higher) to programmatically create and delete MDBs
with a specific message selectors at run-time? Also, if these dynamically created
MDBs could also remain deployed (until programmatically deleted) even in the event of
a server bounce, that would be desireable
27 matches
Mail list logo
