Hi,
Thanks for the info.
The mbeans for key generation are certainly fine, the security related one
I don't know enough about to comment on, however I don't think you need the
bean with the jndi name of the datasource. I apologize for not being able
to give you the exact syntax, but (normally)
At 12:00 AM 7/30/2001, David Jencks wrote:
>Out of curiousity, what is the relationship between the ejbs and the
>mbeans?
One of the MBean(s) is a incrementing key generator for the primary keys of
entity beans. One is instantiated for each table. The other two act as a
central place to stick
Hi,
Glad it worked.
If you want to see an example of a junit test for mbean functionality, see
jbosstest/src/main/org/jboss/test/jmx/test/ConnectionFactoryTest.java.
There is something odd going on if your stopService method isn't logging
properly. I'd try throwing an exception or something to
Jim, David, thank you. I think you are both correct about the
jboss-auto.jcml file. Delete it and no duplicate messages. I guess I
should probably put the rebind in there in case the server gets restarted
and the jboss-auto.jcml file has still references.
My configuration is JBoss 2.2.1 wit
Yes, if you are running a jboss version that reads jboss-auto.jcml, delete
it (jboss-auto) frequently.
This could perhaps cause apparent persistence of jndi bindings also.
david jencks
On 2001.07.29 14:15:13 -0400 Jim Brownfield wrote:
> This is probably not relavent, but I thought I'd throw it
This is probably not relavent, but I thought I'd throw it in.
I had a similar problem, and it turned out to be that somehow my MBean ended
up being put into jboss-auto.jcml twice without me knowing it. What was
happening was two of my MBeans were trying to start at the same time, and
the second
I'm highly confused by trying to guess what you might be doing. What
configuration are you running? What do you mean by "the second time a
server comes up?" Are you running any non-jboss mbean servers or jndis?
My impression was that jboss jndi was 100% non persistent, when you stop
your jboss