"[EMAIL PROTECTED]" wrote : Better than a cookie, a bug report:
| http://jira.jboss.com/jira/browse/JBAS-2973
We are using Jboss 3.2.8 SP1 and are seeing these errors throughout the system
when using JMS queues. Is there a workaround in the 3.2.8 system or something
we can include into our be
Please Ignore this post and view the next one with the same name - this
contains the stakc trace of the error - this posting is too big...sorry
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929986#3929986
Reply to the post :
http://www.jboss.com/ind
"dfantham" wrote : Please Ignore this post and view the next one - this
contains the stakc trace of the error - this posting is too big...sorry
I am having a very bad night - this posting contains the stack trace, and the
previous posting is incorrect - I wish there was a way to
Please Ignore this post and view the next one - this contains the stakc trace
of the error - this posting is too big...sorry
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929984#3929984
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
I am trying to upgrade from jboss 3.2.3 to Jboss 3.2.8SP1 and I am getting RMI
authentication errors whenever the JAAS cache times out. See the following
below for am example(using the TRACE log settings for JAAS):
NOte: sorry about the length
| 17:47:03,338 INFO [AuthTilesRequestP
I am not sure what the do then??? The output you see is exactly what is
thrown, so I am now at a loss to explain.
A couple of observations from our testing here that may help (or not!):
1. We are using JDK 1.5.0_06 from Sun. We backed this back to 1.4.2_06
(Jrockit From Bea) and tested again
Scott,
here is the trace results from the "null" Principal exception. It seems to
coincide with the "other" exception I am seeing which relates to getting around
transactions failing on EJB and DAO querries against the DB (a Trace of these
types of errors is also below (sorry about the length)
We have recently upgrade from Jboss 3.2.3 to 4.0.3SP1 along with going from
Postgres 7.3.2 to 8.1.2. We are having two makor issues that are dramatically
affecting out site, that until a few days ago was rock solid on the old
platform for 1 year:
The two issues are in these postings:
http://
We have recently upgrade from Jboss 3.2.3 to 4.0.3SP1 along with going from
Postgres 7.3.2 to 8.1.2. We are having two makor issues that are dramatically
affecting out site, that until a few days ago was rock solid on the old
platform for 1 year:
The two issues are in these postings:
http://
We have been Jboss 3.2.3 and Postgres 7.4.2 for sometime and have recently been
going through an upgrade to Jboss 4.0.3SP1 and Postgres 8.1.2, using Postgres
JDBC driver postgresql-8.1-404.jdbc3.jar.
Under the old environment, we have a very solid deployment, with no downtime
(other than for re
We have been Jboss 3.2.3 and Postgres 7.4.2 for sometime and have recently been
going through an upgrade to Jboss 4.0.3SP1 and Postgres 8.1.2, using Postgres
JDBC driver postgresql-8.1-404.jdbc3.jar.
Under the old environment, we have a very solid deployment, with no downtime
(other than for re
11 matches
Mail list logo
