Hi Peter.
Ok, I have figured this part of it out. Btw, the queue connection did not like the
qcon.start() call in the snippet (see stack trace). I guess
that is an Orion specific thing. I now have the Message Queue working, finally {{{;-).
What I currently have an issue with is the queue
Hi Peter.
Me again. Are you tired of hearing from me yet?
Are there supposed to be TWO jbossmq-state.xml files? There is one in the deploy
directory as well as the one in the conf directory.
-Steve
Peter Antman wrote:
Hi, if you have done no other changes to the JBoss setup this would
On 14 Mar, Stephen Davidson wrote:
Hi Peter.
Ok, I have figured this part of it out. Btw, the queue connection did not like the
qcon.start() call in the snippet (see stack trace). I guess
that is an Orion specific thing. I now have the Message Queue working, finally
{{{;-).
What I
Hi Peter.
Ok, I have figure out how to turn on tracing and debugging. Attached is
the code I am using to get the connection, plus the log with trace debug
turned on.
Suggetions on where to look or what needs to be set?
-Steve
private void init( Context ctx, String queueName,
Hi Peter.
Ok, I have figure out how to turn on tracing and debugging. Attached is the code I am
using to get the connection, plus the log with trace debug
turned on.
Suggetions on where to look or what needs to be set?
-Steve
===Begin Code Snippet===
private void init( Context ctx,
Hi, if you have done no other changes to the JBoss setup this would
require that the user named user with the password hrnexus is in
jboss-state.xml. It should look something like this (from
server/default/conf in current build):
StateManager
Users
User
Hi Peter.
How do I set the user I am trying to connect as?
Is this something set in the properties for the Initial Context?
If so, what parameter?
Thanks,
Steve
Peter Antman wrote:
Hi, if you have done no other changes to the JBoss setup this would
require that the user named user with the
Hi Peter.
How do I turn on Trace Debug?
I have not changed the default supplied ra.xml or jms-service.xml files.
Is this an issue?
-Steve
Peter Antman wrote:
Hi,
start by turning on trace and debug to track your problem down. You get,
somehow a user named user that is not authenticated.
On 12 Mar, Stephen Davidson wrote:
Hi Peter.
How do I turn on Trace Debug?
Look into log4j.xml or log4j.properties
//Peter
I have not changed the default supplied ra.xml or jms-service.xml files.
Is this an issue?
-Steve
Peter Antman wrote:
Hi,
start by turning on trace and
Hi Peter.
Ok, this has now become my #1 priority to solve.
As the APPLICATION is handling all users security services, there is no
security context generated for the users.
As the Users do not have security contexts, do you know a quick way to go
and generate one for the application?
-Steve
Hi,
start by turning on trace and debug to track your problem down. You get,
somehow a user named user that is not authenticated. Where does that
user come from. Verry strange, specially since the subject is reported
as null. How do your ra.xml look, and your jms-service.xml.
//Peter
On 11 Mar,
Hi David.
Thanks. JBossMQ now deploys on startup. But when I try to send a message to an MDB,
I get the following stack Trace...
-Steve
09:46:55,229 INFO [XAConnectionManager] Got a subject: null
09:46:55,271 ERROR [JmsXA] Unable to create ManagedConnection:
Ok, just updated, and now I get the attached stack-trace. What is happening is that a
servlet is calling an SLSB, and that SLSB is trying to pop a message on a
queue (as well as do some other operations). What is really disconcerting is the fact
that the Exceptions and StackTraces are NOT
On 6 Mar, Stephen Davidson wrote:
Ok, just updated, and now I get the attached stack-trace. What is happening is that
a servlet is calling an SLSB, and that SLSB is trying to pop a message on a
queue (as well as do some other operations). What is really disconcerting is the
fact that
On 6 Mar, Stephen Davidson wrote:
Hi Peter.
The Application had been checking the information stored in the httpSession to see
if the user had been authenticated. Then the SLSB was checking to see if the
user was allowed to access the function requested. Btw, the current JAAS
Hi Peter.
Responses inlined.
-Steve
[EMAIL PROTECTED] wrote:
On 6 Mar, Stephen Davidson wrote:
Hi Peter.
The Application had been checking the information stored in the httpSession to see
if the user had been authenticated. Then the SLSB was checking to see if the
user was allowed
Hi Peter.
Something I just noticed;
In the jboss.xml file, and in the calling code, the Queue is referenced as;
com/hrnexus/RFPReleaseQueue
However, in the JNDI viewer, it is listed as
queue/hrnexus/RFPReleaseQueue
I know that we have not made it to the point where this is an issue, but will it
Greetings.
A fresh co of JBoss3.0Beta2 (Head Revision). On startup, I get the following errors.
Suggestions or tips?
-Steve
16:11:32,361 INFO [MainDeployer] Starting deployment of package:
file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/default/deploy/jms-service.xml
On 2002.03.05 17:51:46 -0500 Stephen Davidson wrote:
Greetings.
A fresh co of JBoss3.0Beta2 (Head Revision). On startup, I get the
following errors.
Suggestions or tips?
Try adding this to jms-service.xml:
classpath codebase=. archives=jbosscx.sar/
david jencks
-Steve
19 matches
Mail list logo
