[Installation, Configuration & DEPLOYMENT] - Re: Configuring dependencies in Services
by Marcelo.S_
"zithuba" wrote : Isn't the mispelling of datasourc instead of datasource
Don't think so, the exception is the same, but whit an 'e' at the end ):
"jaikiran" wrote : Try this, instead of the lines marked in bold, in your jboss-service.xml:
|
| <depends>jboss.jca:service=RARDeployer</depends>
| | <depends>jboss.jca:service=LocalTxCM,name=hibernate-ds</depends>
| |
Tried it, and gives the following exception:
javax.naming.NameNotFoundException: hibernate-ds not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
| at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
| at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:414)
| at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62)
| at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
| at org.hibernate.jmx.HibernateService.buildSessionFactory(HibernateService.java:64)
| at org.hibernate.jmx.HibernateService.start(HibernateService.java:40)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
|
| ........ // lots of exception lines here
|
|
| 08:29:49,171 INFO [HibernateServiceMBean] Could not build SessionFactory using the MBean classpath - will try again using client classpath: Could not find datasource
| 08:29:49,218 INFO [SessionFactoryObjectFactory] Factory name: java:/hibernate/HibernateFactory
| 08:29:49,218 INFO [NamingHelper] JNDI InitialContext properties:{}
| 08:29:49,218 INFO [NamingHelper] Creating subcontext: hibernate
| 08:29:49,218 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: java:/hibernate/HibernateFactory
| 08:29:49,218 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
| 08:29:49,234 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=hibernate-ds' to JNDI name 'java:hibernate-ds'
| 08:29:51,609 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
| 08:29:51,718 WARN [loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.startupWarning] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.startupWarning] You have chosen to enable multiple last resources in the transaction manager. This is transactionally unsafe and should not be relied upon.
| 08:29:52,140 INFO [A] Bound to JNDI name: queue/A
|
| ...
|
|
|
>From what I could understand, it is starting the Datasource right after the service, right?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162525#4162525
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162525
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: How to authenticate to the JBoss server from a desktop (
by Marcos_APS
I changed the login module that I was using from this (my custom login module):
jaas.config
| login
| {
| br.urca.www.laboratorioinformatica.seguranca.jboss.ModuloLoginFuncionarios required;
| };
to this:
jaas.config
| login
| {
| org.jboss.security.ClientLoginModule required;
| };
Now I'm able to login 'normally' using loginContext.login(). But JBoss is now accepting any user I pass in and I suppose this is really not a good thing at the point of security. I would like to keep using my custom login module as I use in the web application, but there's the issue of the InitialContext that can't find the JNDI configuration from the client application.
Please, can someone help me with this issue, to find a solution to this. I would accept a workaround if it doesn't compromise the security of my web application, because the login module is also used by the web application. This issue is of paramount importance to me.
Thank you very much.
Marcos
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162521#4162521
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162521
17 years, 9 months