Re: [JBoss-user] JBossMQ broken?
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 currently have an issue with is the queue name. In the jboss.xml file
>(attached), the destination JNDI name is
> "/com/hrnexus/CustSetupQueue". If it was just "com/hrnexus/CustSetupQueue", the
>"com" gets dropped.
> And why is "queue" being prepended to the JNDI name. For the Servlets/EJB's to
>access these queues, they must look up
> "queue/com/hrnexus/CustSetupQueue". If this is desired behaviour, than this needs
>to be documented in BOLD. Otherwise, newbies like me are going
> to get tripped up many times.
>
> Thanks,
> Steve
I would say that this is pretty well documented in the free JMS doc on
jboss.org. This was the most common quetsion before, but has in
principal ;-) vanished as a beginners question.
Please, in the future, use the JMS forum on JBoss to ask your questions.
//Peter
>
>
> <==Begin log excerpt===>
> 12:31:56,674 INFO [STDOUT] QConnectionManager.init: Username/password =
>'hrnexus/hrnexus'
> 12:31:56,675 INFO [XAConnectionManager] Got a subject: null
> 12:31:56,681 DEBUG [JBossMQProvider] no provider url; connecting to local JNDI
> 12:31:56,682 DEBUG [JBossMQProvider] created context:
>javax.naming.InitialContext@2bb373
> 12:31:56,683 DEBUG [ConnectionFactoryHelper] using connection factory:
>org.jboss.mq.SpyXAConnectionFactory@21447f
> 12:31:56,684 DEBUG [ConnectionFactoryHelper] using username/password: hrnexus/hrnexus
> 12:31:56,686 DEBUG [GenericConnectionFactory] Handing out ClientIL:
>org.jboss.mq.il.jvm.JVMClientILService
> 12:31:56,686 DEBUG [ConnectionFactoryHelper] created XAQueueConnection:
>org.jboss.mq.SpyXAConnection@127624
> 12:31:56,687 DEBUG [JmsManagedConnection] created connection:
>org.jboss.mq.SpyXAConnection@127624
> 12:31:56,689 DEBUG [JmsManagedConnection] xaQueueSession:
>org.jboss.mq.SpyQueueSession@a44a6
> 12:31:56,689 DEBUG [JmsManagedConnection] queueSession:
>org.jboss.mq.SpyQueueSession@a44a6
> 12:31:56,690 DEBUG [JmsManagedConnection] transacted: true
> 12:31:56,690 DEBUG [JmsManagedConnection] ack mode: 1
> 12:31:56,691 DEBUG [JmsManagedConnection] Leaving out XAResource
> 12:31:56,692 DEBUG [JmsManagedConnection] ConnectionEvent listener added:
>org.jboss.resource.connectionmanager.BaseConnectionManager$XAListener@15435a
> 12:31:56,715 DEBUG [SpyDestinationObjectFactory]
>SpyDestinationObjectFactory->getObjectInstance()
> 12:31:56,716 INFO [STDOUT] QConnectionManager.init: ConnectionFactory
> 12:31:56,717 INFO [STDOUT]
>org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl@61373f
> 12:31:56,717 INFO [STDOUT] QConnectionManager.init: Connection
> 12:31:56,718 INFO [STDOUT]
>org.jboss.resource.adapter.jms.JmsSessionFactoryImpl@31a519
> 12:31:56,718 INFO [STDOUT] QConnectionManager.init: Session
> 12:31:56,719 INFO [STDOUT] org.jboss.resource.adapter.jms.JmsSession@790581
> 12:31:56,720 INFO [STDOUT] QConnectionManager.init: Sucessfully Connected to
>queue/com/hrnexus/RFPReleaseQueue
> 12:31:56,720 INFO [STDOUT] QConnectionManager.init: Details are
> 12:31:56,721 INFO [STDOUT] QUEUE.com/hrnexus/RFPReleaseQueue
> 12:31:57,077 WARN [Jetty] WARNING: CustomerStatusMgmtServlet: HRXFeatureServlet
>IOException
> java.rmi.ServerException: null
> Embedded Exception
> This method is not applicatable in JMS resource adapter; nested exception is:
> javax.ejb.EJBException: null
> Embedded Exception
> This method is not applicatable in JMS resource adapter
> javax.ejb.EJBException: null
> Embedded Exception
> This method is not applicatable in JMS resource adapter
> at
>org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:653)
> at
>org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77)
>
> 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 password hrnexus is in
> > jboss-state.xml. It should look something like this (from
> > server/default/conf in current build):
> >
> >
> >
> >
> >john
> >needle
> >DurableSubscriberExample
> >
> >
> >guest
> >guest
> >
> >
> >nobody
> >nobody
> >
> >
> >dynsub
> >dynsub
> >
> >
> >
> >user
> >hrnexus
> >
> >
> >
> > Depending on your restrictions on the destinations the user must bel
Re: [JBoss-user] JBossMQ broken?
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 > 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): > [snip to save bandwidth] -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ broken?
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 name. In the jboss.xml file
(attached), the destination JNDI name is
"/com/hrnexus/CustSetupQueue". If it was just "com/hrnexus/CustSetupQueue", the "com"
gets dropped.
And why is "queue" being prepended to the JNDI name. For the Servlets/EJB's to access
these queues, they must look up
"queue/com/hrnexus/CustSetupQueue". If this is desired behaviour, than this needs to
be documented in BOLD. Otherwise, newbies like me are going
to get tripped up many times.
Thanks,
Steve
<==Begin log excerpt===>
12:31:56,674 INFO [STDOUT] QConnectionManager.init: Username/password =
'hrnexus/hrnexus'
12:31:56,675 INFO [XAConnectionManager] Got a subject: null
12:31:56,681 DEBUG [JBossMQProvider] no provider url; connecting to local JNDI
12:31:56,682 DEBUG [JBossMQProvider] created context:
javax.naming.InitialContext@2bb373
12:31:56,683 DEBUG [ConnectionFactoryHelper] using connection factory:
org.jboss.mq.SpyXAConnectionFactory@21447f
12:31:56,684 DEBUG [ConnectionFactoryHelper] using username/password: hrnexus/hrnexus
12:31:56,686 DEBUG [GenericConnectionFactory] Handing out ClientIL:
org.jboss.mq.il.jvm.JVMClientILService
12:31:56,686 DEBUG [ConnectionFactoryHelper] created XAQueueConnection:
org.jboss.mq.SpyXAConnection@127624
12:31:56,687 DEBUG [JmsManagedConnection] created connection:
org.jboss.mq.SpyXAConnection@127624
12:31:56,689 DEBUG [JmsManagedConnection] xaQueueSession:
org.jboss.mq.SpyQueueSession@a44a6
12:31:56,689 DEBUG [JmsManagedConnection] queueSession:
org.jboss.mq.SpyQueueSession@a44a6
12:31:56,690 DEBUG [JmsManagedConnection] transacted: true
12:31:56,690 DEBUG [JmsManagedConnection] ack mode: 1
12:31:56,691 DEBUG [JmsManagedConnection] Leaving out XAResource
12:31:56,692 DEBUG [JmsManagedConnection] ConnectionEvent listener added:
org.jboss.resource.connectionmanager.BaseConnectionManager$XAListener@15435a
12:31:56,715 DEBUG [SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
12:31:56,716 INFO [STDOUT] QConnectionManager.init: ConnectionFactory
12:31:56,717 INFO [STDOUT]
org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl@61373f
12:31:56,717 INFO [STDOUT] QConnectionManager.init: Connection
12:31:56,718 INFO [STDOUT] org.jboss.resource.adapter.jms.JmsSessionFactoryImpl@31a519
12:31:56,718 INFO [STDOUT] QConnectionManager.init: Session
12:31:56,719 INFO [STDOUT] org.jboss.resource.adapter.jms.JmsSession@790581
12:31:56,720 INFO [STDOUT] QConnectionManager.init: Sucessfully Connected to
queue/com/hrnexus/RFPReleaseQueue
12:31:56,720 INFO [STDOUT] QConnectionManager.init: Details are
12:31:56,721 INFO [STDOUT] QUEUE.com/hrnexus/RFPReleaseQueue
12:31:57,077 WARN [Jetty] WARNING: CustomerStatusMgmtServlet: HRXFeatureServlet
IOException
java.rmi.ServerException: null
Embedded Exception
This method is not applicatable in JMS resource adapter; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
This method is not applicatable in JMS resource adapter
javax.ejb.EJBException: null
Embedded Exception
This method is not applicatable in JMS resource adapter
at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:653)
at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77)
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 password hrnexus is in
> jboss-state.xml. It should look something like this (from
> server/default/conf in current build):
>
>
>
>
> john
> needle
> DurableSubscriberExample
>
>
> guest
> guest
>
>
> nobody
> nobody
>
>
> dynsub
> dynsub
>
>
>
> user
> hrnexus
>
>
>
> Depending on your restrictions on the destinations the user must belongs
> to a role having the correct access rights to the destination. By
> default guest have read and write access:
>
>
>
> guest
> john
>
> user
>
>
> If you have reconfigured the security domian jbossmq in auth.conf to use
> your own user storage you will have to check that all setups are really
> done correct.
>
Re: [JBoss-user] JBossMQ broken?
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 password hrnexus is in > jboss-state.xml. It should look something like this (from > server/default/conf in current build): > > > > > john > needle > DurableSubscriberExample > > > guest > guest > > > nobody > nobody > > > dynsub > dynsub > > > > user > hrnexus > > > > Depending on your restrictions on the destinations the user must belongs > to a role having the correct access rights to the destination. By > default guest have read and write access: > > > > guest > john > > user > > > If you have reconfigured the security domian jbossmq in auth.conf to use > your own user storage you will have to check that all setups are really > done correct. > > Remember that it is now actually possible to dynamically manage users > and roles from the HTML Mbean interface to the DynamicStateManager > (remember to invoke saveConf() to persist the changes. > -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ broken?
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):
john
needle
DurableSubscriberExample
guest
guest
nobody
nobody
dynsub
dynsub
user
hrnexus
Depending on your restrictions on the destinations the user must belongs
to a role having the correct access rights to the destination. By
default guest have read and write access:
guest
john
user
If you have reconfigured the security domian jbossmq in auth.conf to use
your own user storage you will have to check that all setups are really
done correct.
Remember that it is now actually possible to dynamically manage users
and roles from the HTML Mbean interface to the DynamicStateManager
(remember to invoke saveConf() to persist the changes.
//Peter
On 13 Mar, Stephen Davidson wrote:
> 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, String queueName, ParameterProcessor
> params )
> throws NamingException, JMSException
> {
> // if ( DEBUG )
> // getQueuesTopics( (InitialContext) ctx );
> //This currently sets password = "hrnexus"
> final String password = params.get(WEB_USER_PASSWORD);
>
> //SPDBUG: Factory has been moved
> // qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
> qconFactory = (QueueConnectionFactory) ctx.lookup("java:/JmsXA");
> qcon = qconFactory.createQueueConnection(USER, password);
> qsession = qcon.createQueueSession(transacted,
> Session.CLIENT_ACKNOWLEDGE);
> queue = (Queue) ctx.lookup( queueName );
> if ( DEBUG )
> {
>System.out.print("QConnectionManager.init: ConnectionFactory ");
>System.out.println(qconFactory.toString());
>System.out.print("QConnectionManager.init: Connection ");
>System.out.println(qcon.toString());
>System.out.print("QConnectionManager.init: Session ");
>System.out.println(qsession.toString());
>
>if ( queue == null )
> System.out.println( "Connection Failed.");
>else
>{
> System.out.println( "QConnectionManager.init: Sucessfully
> Connected to " + queueName );
> System.out.println( "QConnectionManager.init: Details are" );
> System.out.println( queue.toString() );
>}
> }
> qsender = qsession.createSender(queue);
> qcon.start();
> }
>
> <===Begin Stack Trace===>
> 05:46:31,958 INFO [XAConnectionManager] Got a subject: null
> 05:46:31,970 DEBUG [JBossMQProvider] no provider url; connecting to local JNDI
> 05:46:31,971 DEBUG [JBossMQProvider] created context:
>javax.naming.InitialContext@478000
> 05:46:31,973 DEBUG [ConnectionFactoryHelper] using connection factory:
>org.jboss.mq.SpyXAConnectionFactory@711507
> 05:46:31,974 DEBUG [ConnectionFactoryHelper] using username/password: user/hrnexus
> 05:46:31,976 DEBUG [DynamicLoginModule] Bad password for username=user
> 05:46:31,979 DEBUG [jbossmq] Login failure
> javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> at
>org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:146)
> at org.jboss.mq.sm.file.DynamicLoginModule.login(DynamicLoginModule.java:72)
> at java.lang.reflect.Method.invoke(Native Method)
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:664)
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:599)
> at java.security.AccessController.doPrivileged(Native Method)
> at
>javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:596)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:523)
> at
>org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:3
Re: [JBoss-user] JBossMQ broken?
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, String queueName, ParameterProcessor
params )
throws NamingException, JMSException
{
// if ( DEBUG )
// getQueuesTopics( (InitialContext) ctx );
//This currently sets password = "hrnexus"
final String password = params.get(WEB_USER_PASSWORD);
//SPDBUG: Factory has been moved
// qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
qconFactory = (QueueConnectionFactory) ctx.lookup("java:/JmsXA");
qcon = qconFactory.createQueueConnection(USER, password);
qsession = qcon.createQueueSession(transacted,
Session.CLIENT_ACKNOWLEDGE);
queue = (Queue) ctx.lookup( queueName );
if ( DEBUG )
{
System.out.print("QConnectionManager.init: ConnectionFactory ");
System.out.println(qconFactory.toString());
System.out.print("QConnectionManager.init: Connection ");
System.out.println(qcon.toString());
System.out.print("QConnectionManager.init: Session ");
System.out.println(qsession.toString());
if ( queue == null )
System.out.println( "Connection Failed.");
else
{
System.out.println( "QConnectionManager.init: Sucessfully
Connected to " + queueName );
System.out.println( "QConnectionManager.init: Details are" );
System.out.println( queue.toString() );
}
}
qsender = qsession.createSender(queue);
qcon.start();
}
<===Begin Stack Trace===>
05:46:31,958 INFO [XAConnectionManager] Got a subject: null
05:46:31,970 DEBUG [JBossMQProvider] no provider url; connecting to local JNDI
05:46:31,971 DEBUG [JBossMQProvider] created context:
javax.naming.InitialContext@478000
05:46:31,973 DEBUG [ConnectionFactoryHelper] using connection factory:
org.jboss.mq.SpyXAConnectionFactory@711507
05:46:31,974 DEBUG [ConnectionFactoryHelper] using username/password: user/hrnexus
05:46:31,976 DEBUG [DynamicLoginModule] Bad password for username=user
05:46:31,979 DEBUG [jbossmq] Login failure
javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
at
org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:146)
at org.jboss.mq.sm.file.DynamicLoginModule.login(DynamicLoginModule.java:72)
at java.lang.reflect.Method.invoke(Native Method)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:664)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:599)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:596)
at javax.security.auth.login.LoginContext.login(LoginContext.java:523)
at
org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:394)
at
org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:361)
at
org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:217)
at
org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:153)
at
org.jboss.mq.security.ServerSecurityInvoker.authenticate(ServerSecurityInvoker.java:40)
at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:301)
at org.jboss.mq.Connection.authenticate(Connection.java:758)
at org.jboss.mq.Connection.(Connection.java:232)
at org.jboss.mq.SpyConnection.(SpyConnection.java:47)
at org.jboss.mq.SpyXAConnection.(SpyXAConnection.java:37)
at
org.jboss.mq.SpyXAConnectionFactory.createXAQueueConnection(SpyXAConnectionFactory.java:111)
at
org.jboss.jms.ConnectionFactoryHelper.createQueueConnection(ConnectionFactoryHelper.java:67)
at
org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:581)
at
org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162)
at
org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84)
at
org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97)
at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013)
at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672)
at
org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95)
Re: [JBoss-user] JBossMQ broken?
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, ParameterProcessor
params )
throws NamingException, JMSException
{
// if ( DEBUG )
// getQueuesTopics( (InitialContext) ctx );
//This currently sets password = "hrnexus"
final String password = params.get(WEB_USER_PASSWORD);
//SPDBUG: Factory has been moved
// qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
qconFactory = (QueueConnectionFactory) ctx.lookup("java:/JmsXA");
qcon = qconFactory.createQueueConnection(USER, password);
qsession = qcon.createQueueSession(transacted,
Session.CLIENT_ACKNOWLEDGE);
queue = (Queue) ctx.lookup( queueName );
if ( DEBUG )
{
System.out.print("QConnectionManager.init: ConnectionFactory ");
System.out.println(qconFactory.toString());
System.out.print("QConnectionManager.init: Connection ");
System.out.println(qcon.toString());
System.out.print("QConnectionManager.init: Session ");
System.out.println(qsession.toString());
if ( queue == null )
System.out.println( "Connection Failed.");
else
{
System.out.println( "QConnectionManager.init: Sucessfully
Connected to " + queueName );
System.out.println( "QConnectionManager.init: Details are" );
System.out.println( queue.toString() );
}
}
qsender = qsession.createSender(queue);
qcon.start();
}
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. 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, Stephen Davidson wrote:
>
>>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
>>
>>[EMAIL PROTECTED] wrote:
>>
>>>On 6 Mar, Stephen Davidson wrote:
>>>
--
Stephen Davidson
Java Consultant
Delphi Consultants, LLC
http://www.delphis.com
Phone: 214-696-6224 x208
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ broken?
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 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, Stephen Davidson wrote: >> >>>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 >>> >>>[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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this >application needs, so the SLSBs have to do their own. This means that there is >no Authentication for the Container to do, so I had not been using Container >Authentication/Security. This means that the only subjects/contexts available >would be from the container or application directly. I have not been generating >them in the past, as they had not been needed on the other application servers. > >Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much >simpler), but right now I am trying to get the current framework ported from >Orion to JBoss. And w/o having to rewrite how security is handled. > > > I don't know about that. From the JMS client perspective nothing has changed. You loogin via the connection, it is on the JMS server side that JAAS are used. As far as I can see it the subject will not be magically propagated. So the bottom line is this: why do your user not get authenticated. - Have you configured jmsra to use a specific user? - Do you have special destinations for wich that user do not belong to the correct role. - Did you happen to refresh you copy in the middle of my commit - perhaps missing the auth.conf commit, which is verry important. I have tested this a million times...it would be typical if the first that happend to use it stumble om something unexpected. //Peter >Thanks, >Steve > > > >[EMAIL PROTECTED] wrote: > > >>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 the Exceptions and StackTraces are NOT being propagated back to the >>>servlet... >>> >>>Suggestions as to what the unauthenticated User is all about? And how to deal >with it? >>>It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS >>>was still in its initial Draft stage when the security model was >created/implemented). >>> >>>-Steve >>> >>><==Begin Excerpt from log===> >>>12:40:58,348 INFO [XAConnectionManager] Got a subject: null >>>12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: >>>javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is >NOT authenticated >>> >>> >>> >>> >>Are you using the latest CVS HEAD version of JBossMQ, I mean from just >>an hour ago? Then the complete security architecture has changed for >>JBossMQ. How are you authenticating in the jmsra stuff? >> >>//Peter >> >> >> >>>at >>> >>> >>> >>org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) >> >> >> >>> at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) >>> at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) >>> at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) >>> at org.jboss.pool.ObjectPool.createNewObje
Re: [JBoss-user] JBossMQ broken?
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. 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, Stephen Davidson wrote: > >>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 >> >>[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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container Authentication/Security. This means that the only subjects/contexts available >would be from the container or application directly. I have not been generating them in the past, as they had not been needed on the other application servers. Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. >>>I don't know about that. From the JMS client perspective nothing has >>>changed. You loogin via the connection, it is on the JMS server side >>>that JAAS are used. As far as I can see it the subject will not be >>>magically propagated. So the bottom line is this: why do your user not >>>get authenticated. >>> >>>- Have you configured jmsra to use a specific user? >>>- Do you have special destinations for wich that user do not belong to >>> the correct role. >>>- Did you happen to refresh you copy in the middle of my commit - >>> perhaps missing the auth.conf commit, which is verry important. >>> >>>I have tested this a million times...it would be typical if the first >>>that happend to use it stumble om something unexpected. >>> >>>//Peter >>> >>> Thanks, Steve [EMAIL PROTECTED] wrote: >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 the Exceptions and StackTraces are NOT being propagated back to the >>servlet... >> >>Suggestions as to what the unauthenticated User is all about? And how to deal >with it? >>It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS >>was still in its initial Draft stage when the security model was >created/implemented). >> >>-Steve >> >><==Begin Excerpt from log===> >>12:40:58,348 INFO [XAConnectionManager] Got a subject: null >>12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: >>javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is >NOT authenticated >> >> >> >> >Are you using the latest CVS HEAD version of JBossMQ, I mean from just >an hour ago? Then the complete security architecture has changed for >JBossMQ. How are you authenticating in the jmsra stuff? > >//Peter > > > >>at >> >> >> >org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) > > > >> at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) >> at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) >> at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) >> at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) >> at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) >> at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.
Re: [JBoss-user] JBossMQ broken?
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, Stephen Davidson wrote: > 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 > > [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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this >>>application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container >>>Authentication/Security. This means that the only subjects/contexts available >would be from the container or application directly. I have not been generating >>>them in the past, as they had not been needed on the other application servers. >>> >>>Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much >>>simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. >>> >>> >> >> I don't know about that. From the JMS client perspective nothing has >> changed. You loogin via the connection, it is on the JMS server side >> that JAAS are used. As far as I can see it the subject will not be >> magically propagated. So the bottom line is this: why do your user not >> get authenticated. >> >> - Have you configured jmsra to use a specific user? >> - Do you have special destinations for wich that user do not belong to >> the correct role. >> - Did you happen to refresh you copy in the middle of my commit - >> perhaps missing the auth.conf commit, which is verry important. >> >> I have tested this a million times...it would be typical if the first >> that happend to use it stumble om something unexpected. >> >> //Peter >> >>>Thanks, >>>Steve >>> >>> >>> >>>[EMAIL PROTECTED] wrote: >>> 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 the Exceptions and StackTraces are NOT being propagated back to the >servlet... > >Suggestions as to what the unauthenticated User is all about? And how to deal >with it? >It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS >was still in its initial Draft stage when the security model was >created/implemented). > >-Steve > ><==Begin Excerpt from log===> >12:40:58,348 INFO [XAConnectionManager] Got a subject: null >12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: >javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is >NOT authenticated > > > Are you using the latest CVS HEAD version of JBossMQ, I mean from just an hour ago? Then the complete security architecture has changed for JBossMQ. How are you authenticating in the jmsra stuff? //Peter >at > > org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) >at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) >at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) >at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) >at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) >at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) >at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) >at >org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) >at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) >at >com.hrnexus.common.shared.QConnectionMan
Re: [JBoss-user] JBossMQ broken?
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 [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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this >>application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container >>Authentication/Security. This means that the only subjects/contexts available would >be from the container or application directly. I have not been generating >>them in the past, as they had not been needed on the other application servers. >> >>Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much >>simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. >> >> > > I don't know about that. From the JMS client perspective nothing has > changed. You loogin via the connection, it is on the JMS server side > that JAAS are used. As far as I can see it the subject will not be > magically propagated. So the bottom line is this: why do your user not > get authenticated. > > - Have you configured jmsra to use a specific user? > - Do you have special destinations for wich that user do not belong to > the correct role. > - Did you happen to refresh you copy in the middle of my commit - > perhaps missing the auth.conf commit, which is verry important. > > I have tested this a million times...it would be typical if the first > that happend to use it stumble om something unexpected. > > //Peter > >>Thanks, >>Steve >> >> >> >>[EMAIL PROTECTED] wrote: >> >>>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 the Exceptions and StackTraces are NOT being propagated back to the servlet... Suggestions as to what the unauthenticated User is all about? And how to deal >with it? It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS was still in its initial Draft stage when the security model was >created/implemented). -Steve <==Begin Excerpt from log===> 12:40:58,348 INFO [XAConnectionManager] Got a subject: null 12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is >NOT authenticated >>>Are you using the latest CVS HEAD version of JBossMQ, I mean from just >>>an hour ago? Then the complete security architecture has changed for >>>JBossMQ. How are you authenticating in the jmsra stuff? >>> >>>//Peter >>> >>> at >>>org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) >>> >>> at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) at >org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) at >com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) at >com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) at
Re: [JBoss-user] JBossMQ broken?
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 be? -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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this >>application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container >>Authentication/Security. This means that the only subjects/contexts available would >be from the container or application directly. I have not been generating >>them in the past, as they had not been needed on the other application servers. >> >>Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much >>simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. >> >> > > I don't know about that. From the JMS client perspective nothing has > changed. You loogin via the connection, it is on the JMS server side > that JAAS are used. As far as I can see it the subject will not be > magically propagated. So the bottom line is this: why do your user not > get authenticated. > > - Have you configured jmsra to use a specific user? > - Do you have special destinations for wich that user do not belong to > the correct role. > - Did you happen to refresh you copy in the middle of my commit - > perhaps missing the auth.conf commit, which is verry important. > > I have tested this a million times...it would be typical if the first > that happend to use it stumble om something unexpected. > > //Peter > > -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ broken?
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 to access the function requested. Btw, the current JAAS >specifications do not currently support the security archictecutre that this >>application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container >>Authentication/Security. This means that the only subjects/contexts available would >be from the container or application directly. I have not been generating >>them in the past, as they had not been needed on the other application servers. >> >>Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much >>simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. >> >> > > I don't know about that. From the JMS client perspective nothing has > changed. You loogin via the connection, it is on the JMS server side > that JAAS are used. As far as I can see it the subject will not be > magically propagated. So the bottom line is this: why do your user not > get authenticated. Application authenticates & manages user, not Appserver such as JBoss. So no subject ever created. Does application need to create a User for JMS Server? > > - Have you configured jmsra to use a specific user? Probably not. How do I do so? > - Do you have special destinations for wich that user do not belong to > the correct role. No users configured, and definately no roles configured, as not using JAAS, or Role based security, for that matter. > - Did you happen to refresh you copy in the middle of my commit - > perhaps missing the auth.conf commit, which is verry important. > I was updating when you asked earlier. I checked CVS, and the only thing that was out of date was the messaging/build.sh file and number of files from the Test directory. > I have tested this a million times...it would be typical if the first > that happend to use it stumble om something unexpected. I have this habit of not doing things the way that code was tested for. If I can help come up with testcases, feel free to ask! > > //Peter > >>Thanks, >>Steve >> >> >> -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ broken?
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 specifications do not currently support the security archictecutre that this application needs, so the SLSBs have to do their own. This means that there is no Authentication for the Container to do, so I had not been using Container Authentication/Security. This means that the only subjects/contexts available would be from the container or application directly. I have not been generating them in the past, as they had not been needed on the other application servers. Btw, the new JBoss security modules may advanced enough that I will be able to integrate the application's security handling into JBoss (would make life much simpler), but right now I am trying to get the current framework ported from Orion to JBoss. And w/o having to rewrite how security is handled. Thanks, Steve [EMAIL PROTECTED] wrote: > 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 the Exceptions and StackTraces are NOT being propagated back to the >>servlet... >> >>Suggestions as to what the unauthenticated User is all about? And how to deal with >it? >>It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS >>was still in its initial Draft stage when the security model was >created/implemented). >> >>-Steve >> >><==Begin Excerpt from log===> >>12:40:58,348 INFO [XAConnectionManager] Got a subject: null >>12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: >>javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is NOT >authenticated >> >> > > Are you using the latest CVS HEAD version of JBossMQ, I mean from just > an hour ago? Then the complete security architecture has changed for > JBossMQ. How are you authenticating in the jmsra stuff? > > //Peter > >>at >> > >org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) > >> at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) >> at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) >> at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) >> at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) >> at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) >> at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) >> at >org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) >> at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) >> at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) >> at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) >> at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) >> at >com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) >> at >com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) >> at java.lang.reflect.Method.invoke(Native Method) >> at >org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:642) >> at >org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) >> at >org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) >> at >org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) >> at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) >> at >org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127) >> at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) >> at >org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:308) >> at org.jboss.ejb.Container.invoke(Container.java:668) >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >> at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:92) >> at >org.jboss.invocation.jrmp.interf
Re: [JBoss-user] JBossMQ broken?
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 >specifications do not currently support the security archictecutre that this > application needs, so the SLSBs have to do their own. This means that there is no >Authentication for the Container to do, so I had not been using Container > Authentication/Security. This means that the only subjects/contexts available would >be from the container or application directly. I have not been generating > them in the past, as they had not been needed on the other application servers. > > Btw, the new JBoss security modules may advanced enough that I will be able to >integrate the application's security handling into JBoss (would make life much > simpler), but right now I am trying to get the current framework ported from Orion >to JBoss. And w/o having to rewrite how security is handled. > I don't know about that. From the JMS client perspective nothing has changed. You loogin via the connection, it is on the JMS server side that JAAS are used. As far as I can see it the subject will not be magically propagated. So the bottom line is this: why do your user not get authenticated. - Have you configured jmsra to use a specific user? - Do you have special destinations for wich that user do not belong to the correct role. - Did you happen to refresh you copy in the middle of my commit - perhaps missing the auth.conf commit, which is verry important. I have tested this a million times...it would be typical if the first that happend to use it stumble om something unexpected. //Peter > Thanks, > Steve > > > > [EMAIL PROTECTED] wrote: >> 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 the Exceptions and StackTraces are NOT being propagated back to the >>>servlet... >>> >>>Suggestions as to what the unauthenticated User is all about? And how to deal with >it? >>>It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS >>>was still in its initial Draft stage when the security model was >created/implemented). >>> >>>-Steve >>> >>><==Begin Excerpt from log===> >>>12:40:58,348 INFO [XAConnectionManager] Got a subject: null >>>12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: >>>javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is NOT >authenticated >>> >>> >> >> Are you using the latest CVS HEAD version of JBossMQ, I mean from just >> an hour ago? Then the complete security architecture has changed for >> JBossMQ. How are you authenticating in the jmsra stuff? >> >> //Peter >> >>>at >>> >> >org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) >> >>> at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) >>> at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) >>> at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) >>> at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) >>> at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) >>> at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) >>> at >org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) >>> at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) >>> at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) >>> at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) >>> at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) >>> at >com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) >>> at >com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) >>> at java.lang.reflect.Method.invoke(Native Method) >>> at >org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:642) >>> at >org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) >>> at >org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) >>>
Re: [JBoss-user] JBossMQ broken?
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 the Exceptions and StackTraces are NOT being propagated back to the > servlet... > > Suggestions as to what the unauthenticated User is all about? And how to deal with >it? > It may be relevant to note that the application is handling user >authentication/permissions due to some unusual security requirements (and the fact >that JAAS > was still in its initial Draft stage when the security model was >created/implemented). > > -Steve > > <==Begin Excerpt from log===> > 12:40:58,348 INFO [XAConnectionManager] Got a subject: null > 12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: > javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is NOT >authenticated > Are you using the latest CVS HEAD version of JBossMQ, I mean from just an hour ago? Then the complete security architecture has changed for JBossMQ. How are you authenticating in the jmsra stuff? //Peter >at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) > at >org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) > at >org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) > at >org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) > at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) > at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) > at >org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) > at >org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) > at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) > at >com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) > at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) > at >com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) > at >com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) > at >com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) > at java.lang.reflect.Method.invoke(Native Method) > at >org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:642) > at >org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) > at >org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) > at >org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) > at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) > at >org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) > at >org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:308) > at org.jboss.ejb.Container.invoke(Container.java:668) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:92) > at >org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:150) > at org.jboss.proxy.ejb.GenericProxy.invoke(GenericProxy.java:182) > at >org.jboss.proxy.ejb.StatelessSessionProxy.invoke(StatelessSessionProxy.java:111) > at $Proxy176.releaseRFP(Unknown Source) > at >com.hrnexus.broker.servlet.BrokerRFPServlet.releaseRFP(BrokerRFPServlet.java:341) > at >com.hrnexus.broker.servlet.BrokerRFPServlet.doFunction(BrokerRFPServlet.java:175) > at >com.hrnexus.common.servlet.HRXFeatureServlet.doPost(HRXFeatureServlet.java:178) > at >com.hrnexus.common.servlet.HRXFeatureServlet.doGet(HRXFeatureServlet.java:153) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:570) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1354) > at org.mortbay.http.HttpContext.handle
Re: [JBoss-user] JBossMQ broken?
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 being propagated back to the servlet... Suggestions as to what the unauthenticated User is all about? And how to deal with it? It may be relevant to note that the application is handling user authentication/permissions due to some unusual security requirements (and the fact that JAAS was still in its initial Draft stage when the security model was created/implemented). -Steve <==Begin Excerpt from log===> 12:40:58,348 INFO [XAConnectionManager] Got a subject: null 12:40:58,777 ERROR [JmsXA] Unable to create ManagedConnection: javax.resource.spi.CommException: javax.jms.JMSSecurityException: User: user is NOT authenticated at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) at org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) at org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) at com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) at com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) at com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) at com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) at com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) at com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:642) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:308) at org.jboss.ejb.Container.invoke(Container.java:668) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:92) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:150) at org.jboss.proxy.ejb.GenericProxy.invoke(GenericProxy.java:182) at org.jboss.proxy.ejb.StatelessSessionProxy.invoke(StatelessSessionProxy.java:111) at $Proxy176.releaseRFP(Unknown Source) at com.hrnexus.broker.servlet.BrokerRFPServlet.releaseRFP(BrokerRFPServlet.java:341) at com.hrnexus.broker.servlet.BrokerRFPServlet.doFunction(BrokerRFPServlet.java:175) at com.hrnexus.common.servlet.HRXFeatureServlet.doPost(HRXFeatureServlet.java:178) at com.hrnexus.common.servlet.HRXFeatureServlet.doGet(HRXFeatureServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:570) at org.mortbay.http.HttpContext.handle(HttpContext.java:1354) at org.mortbay.http.HttpContext.handle(HttpContext.java:1308) at org.mortbay.http.HttpServer.service(HttpServer.java:743) at org.jboss.jetty.Jetty.service(Jetty.java:540) at org.mortbay.http.HttpConnection.service(HttpConnection.java:748) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:921) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:763)
Re: [JBoss-user] JBossMQ broken?
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: javax.resource.spi.CommException: org.jboss.mq.SpyJMSException: Cannot get a client ID at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:162) at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:84) at org.jboss.resource.connectionmanager.ManagedConnectionPoolFactory.createObject(ManagedConnectionPoolFactory.java:97) at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1013) at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:672) at org.jboss.resource.connectionmanager.XAConnectionManager.allocateConnection(XAConnectionManager.java:95) at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:119) at com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:92) at com.hrnexus.common.shared.QConnectionManager.init(QConnectionManager.java:62) at com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:46) at com.hrnexus.common.shared.QConnectionManager.(QConnectionManager.java:40) at com.hrnexus.broker.ejb.BrokerRFPService.releaseRFP(BrokerRFPService.java:286) at com.hrnexus.broker.ejb.BrokerRFPSessionEJB.releaseRFP(BrokerRFPSessionEJB.java:228) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:642) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:308) at org.jboss.ejb.Container.invoke(Container.java:668) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:92) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:150) at org.jboss.proxy.ejb.GenericProxy.invoke(GenericProxy.java:182) at org.jboss.proxy.ejb.StatelessSessionProxy.invoke(StatelessSessionProxy.java:111) at $Proxy175.releaseRFP(Unknown Source) at com.hrnexus.broker.servlet.BrokerRFPServlet.releaseRFP(BrokerRFPServlet.java:341) at com.hrnexus.broker.servlet.BrokerRFPServlet.doFunction(BrokerRFPServlet.java:175) at com.hrnexus.common.servlet.HRXFeatureServlet.doPost(HRXFeatureServlet.java:178) at com.hrnexus.common.servlet.HRXFeatureServlet.doGet(HRXFeatureServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:570) at org.mortbay.http.HttpContext.handle(HttpContext.java:1354) at org.mortbay.http.HttpContext.handle(HttpContext.java:1308) at org.mortbay.http.HttpServer.service(HttpServer.java:743) at org.jboss.jetty.Jetty.service(Jetty.java:540) at org.mortbay.http.HttpConnection.service(HttpConnection.java:748) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:921) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:763) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) at java.lang.Thread.run(Thread.java:484) 09:47:00,283 ERROR [JmsXA] Unable to create ManagedConnection: javax.resource.spi.CommException: org.jboss.mq.SpyJMSException: Cannot get a client ID at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:617) at org.jboss.resource.adapter.jms.J
Re: [JBoss-user] JBossMQ broken?
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: david jencks > > -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 > 16:11:33,521 ERROR [SARDeployer] operation failed > java.lang.ClassNotFoundException: org.jboss.resource.ConnectionFactoryLoader > at org.jboss.system.ServiceLibraries.loadClass(ServiceLibraries.java:422) > at org.jboss.system.MBeanClassLoader.loadClass(MBeanClassLoader.java:83) > at org.jboss.system.MBeanClassLoader.loadClass(MBeanClassLoader.java:90) > at >com.sun.management.jmx.MBeanServerImpl.findClass(MBeanServerImpl.java:2466) > at >com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:751) > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:98) > at org.jboss.system.ServiceController.install(ServiceController.java:153) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) > at $Proxy3.install(Unknown Source) > at org.jboss.deployment.SARDeployer.create(SARDeployer.java:227) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:585) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:454) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) > at $Proxy2.deploy(Unknown Source) > at >org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:295) > at >org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:466) > at >org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:356) > at >org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:228) > at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at >org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:314) > at org.jboss.system.ServiceController.start(ServiceController.java:331) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:326) > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:208) > at org.jboss.Main.boot(Main.java:127) > at org.jboss.Main$1.run(Main.java:355) > at java.lang.Thread.run(Thread.java:484) > 16:11:33,532 ERROR [MainDeployer] could not create deployment > >:file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/default/deploy/jms-service.xml > > -- > Stephen Davidson > Java Consultant > Delphi Consultants, LLC > http://www.delphis.com > Phone: 214-696-6224 x208 > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBossMQ broken?
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 16:11:33,521 ERROR [SARDeployer] operation failed java.lang.ClassNotFoundException: org.jboss.resource.ConnectionFactoryLoader at org.jboss.system.ServiceLibraries.loadClass(ServiceLibraries.java:422) at org.jboss.system.MBeanClassLoader.loadClass(MBeanClassLoader.java:83) at org.jboss.system.MBeanClassLoader.loadClass(MBeanClassLoader.java:90) at com.sun.management.jmx.MBeanServerImpl.findClass(MBeanServerImpl.java:2466) at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:751) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:98) at org.jboss.system.ServiceController.install(ServiceController.java:153) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:227) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:585) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:454) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy2.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:295) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:466) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:356) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:228) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:314) at org.jboss.system.ServiceController.start(ServiceController.java:331) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:326) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:208) at org.jboss.Main.boot(Main.java:127) at org.jboss.Main$1.run(Main.java:355) at java.lang.Thread.run(Thread.java:484) 16:11:33,532 ERROR [MainDeployer] could not create deployment :file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/default/deploy/jms-service.xml -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
