I recently started a thread
(http://www.jboss.com/index.html?module=bbop=viewtopict=111382) and it seems
that my problems could be solved by forcing the (non-clustered) AS on my box to
ignore other AS's on my LAN. Is this possible? Or maybe there's a different
setting somewhere that I should
I initially posted this issue to the JNDI forum, then to the Clustering forum,
but I can't get anyone to bite. Since the Hibernate people probably have run
into this problem before, I'm resubmitting here in hopes that they have, or
that they know the people who handle these issues.
Here's the
I initially posted this issue to the JNDI forum, but didn't get a response. It
seemed to me my problem was stemming from clustering, since (as indicated
below) I'm getting a message that my local JBoss AS is trying to access a
clustered JBoss AS on my LAN. So I'm submitting to this forum in
I wasn't sure which forum to submit this to, since it covers a variety of
topics -- hibernate, JNDI, clustering, etc. So I'm picking this forum; if you
can suggest a better one, I'll repost there.
Here's the situation. We've had a web app that's been running fine on JBoss
4.0.5.GA, as the
I started getting this weird error message today when I start up
JBoss:anonymous wrote : 2007-05-13 10:26:23,078 DEBUG
[org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool:
registering pool with interval 90 old interval: 9223372036854775807
| 2007-05-13 10:26:23,078
Moderator: please blow away this thread. I'm re-posting my question.
~Pauly T.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4045304#4045304
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045304
Ok, I posted my issue on the other forum
(http://www.jboss.com/index.html?module=bbop=viewtopict=108476). It has some
new information that I didn't have yet when I posted to this forum, so you
might have a look and see if you happen to recognize the issue right off the
bat. I'm sure all that
I started a thread in the JBoss Messaging forum
(http://www.jboss.org/index.html?module=bbop=viewtopict=108276), and it was
suggested that I redirect that to this forum, being that my problem is more of
and MDB issue.
As I stated in my original post, I ran the JBoss Messaging installation
My problem initially was that my MDB was not binding, as evidenced by their
absence in the jmx-console. I deduced that it was because of the errors I was
seeing in the server log.
Well, after re-installing today, I can now see my MDB EJB in the jmx-console.
I thought it was still breaking,
I'm trying to make a MDB using JBoss 4.0.5.GA and JBoss Messaging 2.1. I
started with the JBoss Messaging 1.2 User's Guide. First I installed the 2.1
package as per Chapter 4 Download Software and Chapter 5 JBoss Messaging
Non-Clustered Installation.
At first, the validation step (5.3
anonymous wrote : jboss.mq:service=DestinationManager
| Tells me you are trying to deploy a jboss mq destination inside jboss
messaging. This won't work.
It sure would appear that way. Given that I followed the instructions in the
User's Guide and used the MDB verbatim, why isn't this
Ok, I started again from scratch. This time I did the web install of JEMS
1.2.0.GA. I selected the all option rather than the default installation.
The next window in the installation shows all the components, with checkboxes
next to each one to toggle their installation. Notably,
ejb-jar.xml is as above. jboss.xml is as in the User's Guide, Ch 7.4, p. 25.
DestinationManager appears in many files under [JBOSS_HOME], in these dir's:
[JBOSS_HOME]\docs\examples\jms*
[JBOSS_HOME]\server\default\conf
[JBOSS_HOME]\server\default\deploy
[JBOSS_HOME]\server\default\deploy\jms
I completed everything in Ch. 5, inlcuding the Queue Example (Ch. 5.3
Installation Validation), which worked like a charm. I haven't tried
anything else in Ch. 7 other than 7.4, which is the MDB EJB2.1 example that
refuses to work.
View the original post :
Well, I've ant'd release-admin.xml over a fresh install twice, and I ended up
with the same issue both times. So we can most likely rule that out.
Is there something that I could post that would help to figure this out? Right
now I'm only slightly concerned with what went wrong; but I'm more
anonymous wrote : Make sure you are using 1.2.1.SP1
|
I don't see 1.2.1.SP1, only 1.2.0.SP1, which I already have
(jboss-messaging-1.2.0.SP1.zip).
anonymous wrote :
| I - downloaded jboss-4.0.4.GA and jboss-4.0.5.GA.
|
| II - unziped jboss-4.0.4.GA
|
| III - set
In conf\jboss-service.xml there's
mbean code=org.jboss.management.j2ee.LocalJBossServerDomain
| name=jboss.management.local:j2eeType=J2EEDomain,name=Manager
| ...
| attribute
name=JMSServicejboss.mq:service=DestinationManager/attribute
| ...
In conf\login-config.xml there's!--
I went ahead and posted this to the JBoss Web Server forum
(http://www.jboss.com/index.html?module=bbop=viewtopict=99054), because I
wasn't sure if I had chosen the right forum to post this question, and I
presumed that the folks who handle these forums only handle a limited number of
them.
18 matches
Mail list logo
