[Installation, Configuration & DEPLOYMENT] - Re: Error Upgrading JBossAS from 4.0.3SP1 to 4.0.4.GA
by tuxetuxe
Have anyone solved this?
I'm getting this too...
2007-11-07 17:26:35,543 DEBUG [org.hibernate.util.JDBCExceptionReporter] - <SQL Warning>
java.sql.SQLWarning: Database has transactions
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
at com.informix.jdbc.IfxSqliConnect.a(IfxSqliConnect.java:1923)
at com.informix.jdbc.IfxSqliConnect.t(IfxSqliConnect.java:4144)
at com.informix.jdbc.IfxSqliConnect.b(IfxSqliConnect.java:2746)
at com.informix.jdbc.IfxSqliConnect.a(IfxSqliConnect.java:2620)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:2615)
at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1800)
at com.informix.jdbc.IfxSqliConnect.(IfxSqliConnect.java:1327)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:254)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:291)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:277)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:259)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:240)
at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:81)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:50)
at $Proxy7.getTransactionIsolation(Unknown Source)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnectionForTransaction(DataSourceUtils.java:173)
at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:457)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:350)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:124)
at com.audaxys.af.security.bll.support.AcegiSecurityUserDetailsServiceImpl.loadUserByUsername(AcegiSecurityUserDetailsServiceImpl.java:75)
at org.acegisecurity.providers.dao.DaoAuthenticationProvider.retrieveUser(DaoAuthenticationProvider.java:86)
at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:115)
at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:188)
at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45)
at org.acegisecurity.providers.rcp.RemoteAuthenticationManagerImpl.attemptAuthentication(RemoteAuthenticationManagerImpl.java:53)
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:324)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy115.attemptAuthentication(Unknown Source)
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:324)
at org.springframework.remoting.support.RemoteInvocation.invoke(RemoteInvocation.java:205)
at org.acegisecurity.context.rmi.ContextPropagatingRemoteInvocation.invoke(ContextPropagatingRemoteInvocation.java:103)
at org.springframework.remoting.support.DefaultRemoteInvocationExecutor.invoke(DefaultRemoteInvocationExecutor.java:38)
at org.springframework.remoting.support.RemoteInvocationBasedExporter.invoke(RemoteInvocationBasedExporter.java:76)
at org.springframework.remoting.rmi.RmiBasedExporter.invoke(RmiBasedExporter.java:72)
at org.springframework.remoting.rmi.RmiInvocationWrapper.invoke(RmiInvocationWrapper.java:72)
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:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:534)
2007-11-07 17:26:35,543 WARN [org.hibernate.util.JDBCExceptionReporter] - <SQL Warning: 0, SQLState: 01I01>
2007-11-07 17:26:35,543 WARN [org.hibernate.util.JDBCExceptionReporter] - <Database has transactions>
2007-11-07 17:26:35,543 WARN [org.hibernate.util.JDBCExceptionReporter] - <SQL Warning: 0, SQLState: 01I04>
2007-11-07 17:26:35,543 WARN [org.hibernate.util.JDBCExceptionReporter] - <Database selected>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102638#4102638
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102638
18 years, 6 months
[Security & JAAS/JBoss] - How to get security domain info?
by whafrog
Hi, I have my security domain information in jboss-web.xml:
<security-domain>java:/jaas/ldap-security</security-domain>
And the application policy set up in login-config.xml:
<application-policy name="ldap-security">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required" >
| <module-option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</module-option>
| <module-option name="java.naming.provider.url">ldap://someurl:389/</module-option>
| ...etc...
| </login-module>
| </authentication>
| </application-policy>
Unfortunately our ldap setup isn't that friendly and I need to requery the ldap server in code to get additional information. We have a custom .jar that been in production use since jdk1.3, and all I need to do is pass it the provider URL. I thought it would be simplest to get it from the application policy. Is there a way I can get that information in code? I'm using Seam to trigger an authenticator class.
Thanks,
Jon
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102637#4102637
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102637
18 years, 6 months
[Installation, Configuration & DEPLOYMENT] - Re: JBoss debugging problem
by jaikiran
"jaikiran" wrote :
| Strange. I wasn't aware that the positioning matters. I still find it hard to believe that this was the reason why it was failing.
|
OK, i now know why you were seeing the exception earlier. It has got nothing to do with the order in which you pass the "server" and "address" parameters.
Here's what your parameters were when you were seeing the exception:
"tttito" wrote :
|
| JAVA_OPTS: -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787, server=y, suspend=n -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djmx.invoke.getters=true
Observer closely, there's a space after the comma following 8787 (before the server parameter).
To reproduce this issue on my local setup (which was working fine for debugging so far), i added a space between the comma separated parameters, and i too started seeing the same exception on startup
anonymous wrote : ERROR: transport error 202: connect failed: Connection refused ["transport.c",L41]
| ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
| JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initializ
| ed, jvmtiError=JVMTI_ERROR_INTERNAL(113)
| Press any key to continue . . .
|
Once i removed the space between the comma separated parameters, and restarted the server, everything started smoothly.
There should not be any space between before or after (any of) those comma separated parameters.
So, if you go back to the original order that was present in the run.bat file and remove those spaces, i bet you too will get it working. This is how the JDPA options line should look like in your run.bat file:
set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102629#4102629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102629
18 years, 6 months