Hi,
Ok - I have read the Wiki, and understand the problem a lot better now. Using the
org.jboss.mq.pm.none.PersistenceManager in place of the default JDBC/Hypersonic
combination has improved the response of the send() orders of magnitude. We can endure
lost messages so this approach might be
Hi Adrian,
Thanks for your response. I am still using the default Hypersonic persistent store, as
evidenced by the very large files in $JBOSS_HOME/server/default/data/hypersonic. This
is a surprise to me though because I explicitly set the delivery mode in the header of
the JMS message to
Hi,
I have the following setup; JBoss 3.2.3, JVM 1.4.2_04-b05 SPARC, Oracle 9.2.0.1.0. I
have configured the JMS PersistenceManager to use Oracle for persisting JMS messages
by removing the Hypersonic config file and replacing it with the Oracle one located in
the
Mea culpa. Sorry I was just getting a little frustrated - the problem appears to have
come from some example XMBean code from the 'Admin Dev Guide' that I 'enhanced' in
my own app.
A seemingly innuocuous NamingException was being thrown when trying to unbind a non
existent JNDI name when the
Hi,
The problem stems from some example XMBean code that I grafted from the 'Admin Dev
Guide' and managed to break.
The XMBean exposes its JNDI name as an attribute. The setter method for the attribute
is responsible for unbinding an existing JNDI name, before binding the new JNDI name
that
Adrian,
Thanks for the link, however if you are implying that my post constitutes either; a)
bad behaviour or b) a bad question then I am a little confused.
Regards,
Andrew
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842338#3842338
Reply to the post :
Hi,
I recently posted to this forum about a problem that I am having when I deploy XMBean
content within an EAR file. All my non XMBean content is invalidated by the Jboss
3.2.3 container. However when I deploy the XMBean SAR components separately everything
works fine. I have not had any
Hi ,
I have a few XMBean components that I have successfully been codeploying to a 3.2.3
container. Originally the XMBean components were deployed in a separate SAR, whilst
WAR, EJB and JAR content was deployed in an EAR. To simplify the deployment process I
have incorporated the SAR
Hi,
Sorry about this very basic question, but I have hit a bit of a brick wall.
I am trying to deploy the XMBean example that accompanies the JBoss 3.2.x
documentation. I have deployed a SAR file containing the JNDIMap MBean and associated
deployment descriptors. This shows up fine in the
Hi,
Ok - I have identified the problem relates to the use of the 'java.lang.Object' type
for the get() and put() operations. If these are set to java.lang.String the behaviour
is as I expected.
Thanks and regards,
Andrew
View the original post :
Hi,
I have recently migrated from JBoss 3.0.3 to jboss 3.2.3/tomcat 4.1.29. In the
previous release we were able to run multiple instances of the server by changing port
numbers as appropriate. I notice that with the 3.2.3 release that I get various other
problems, like the following for
Hi,
Further to my original post I am running the two instances using the following
invocation;
$ $JBOSS_HOME/bin/run.sh --host=`hostname`
Hence the ${jboss.bind.address} is the same for for instances
Thanks and regards,
Andrew
View the original post :
whoa brainfade on my part - didn't bother to check
$JBOSS_HOME/server/default/conf/jboss-minimal.xml
sorry for the space wastage
Regards,
AT
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831516#3831516
Reply to the post :
Hi Guys,
I am also experiencing this 'problem' with 3.2.3 and a Queue, however the bug appears
to be harmless. Can the ExceptionHandler just ignore the Exception, or should it
perform some cleanup ?
Thanks and regards,
Andrew
View the original post :
Hi,
I have JBoss 3.2.3 installed, however I have a bit of an issue with the
${jboss.bind.address} property that appears in the jboss-service.xml file. At first I
thought that this could be set using a Java system property argument to the VM (i.e.
-Djboss.bind.addres=myhost ). However this does
sorry for some reason the property did not appear in my post - I want to set
jboss.bind.address
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3827328#3827328;View
the original post/a
a
href=http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3827328Reply
to the
Hi,
CA-Ingres comes bundled with a JDBC driver that supports XA connections. There is an
informational site that provides explicit instructions for setting up
an xa-datasource/ using JBoss 3.2.x and their JDBC driver.
http://support.ca.com/techbases/ingres/TEC317590.html
When I try and set
Hi,
I notice that after my Jboss 3.2.3 instance has been running for an extended period
(hours/days) that the following 'heart-beat' appears to fail. The problem appears to
be benign, but clearly some serivce has failed? I would appreciate any tips anyone
might have.
07:06:06,665 WARN
18 matches
Mail list logo
