[JBoss Portal] - LDAP support issue
by NapSteros
Hi everybody,
I am working on JBoss Portal [2.7.1] integration with LDAP (Redhat Directory).
I tried to integrate LDAP authentication module into my portal.
I followed the "Reference Guide Jan. 2009" but each time, the deployment fails and I receive this exception:
anonymous wrote : ERROR [AbstractKernelController] Error installing to Configured: name=portal:identity=Datasource,type=LDAP state=Instantiated
| org.jboss.joinpoint.spi.JoinpointException: Property ldap1 not found for AbstractBeanInfo(a)f45223{name=org.jboss.portal.identity.ldap.LDAPConnectionContext classInfo= properties=[port, pr
| otocol, host, poolingDebug, class, contextFactory, externalContextJndiName, jNDIName, adminDN, pooling, environment, poolingInitsize, poolingPrefsize, adminPassword, jndiBinder, authenti
| cation, name, poolingProtocol, identityContext, poolingTimeout, poolingMaxsize] methods=[, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
| , , , , , ] constructors=[] events=}
I'll be so grateful for any help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223689#4223689
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223689
17 years
[JCA/JBoss] - Re: jboss connectionpooling by subject, connection closed/no
by adrian＠jboss.org
"gjeudy" wrote :
| I'm considering adding a check-valid-connection-sql config something like:
| SELECT * FROM DUAL
|
That will only help when you first get the connection from the pool.
i.e. at the start of a new tranaction.
anonymous wrote :
| Even if that worked wouldn't that add unnecessary overhead? I mean shouldn't jboss find such unrecoverable exceptions by itself and let go the physical connection handle
|
It obviously has done, that is why you have the connection closed message
most likely spotted by the OracleExceptionSorter you've configured.
anonymous wrote :
| and recreate a new one ?
|
It does, but you have to let the transaction rollback and start it over again
which will retrieve a "new" connection from the pool.
It can't recover mid-transaction.
The connection remains "sticky" to the transaction even when it has errored and closed.
The transaction is dead, the loss of the physical connection means you can
no longer access the local transaction state within the database.
Opening a new connection to take over from the failed one
won't give you access to that state so you could never commit it
or if you tried you would miss committing part of the data.
So what you need is to have some code at whatever starts and ends the transaction
that spots the SQLException (or any other retryable exception) and retry it.
If you were using EJB/CMT then JBoss has a way to configure your own
retry handlers that are transparent to the application:
http://www.jboss.org/community/docs/DOC-11841
Other frameworks may or may not have their own approach?
Either way, the retry policy for a failed transaction is not something that
can or should be configured at the DataSource level it's an application policy.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223686#4223686
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223686
17 years
[JBossWS] - error with wssecurity!!!!
by joncmuniz
My webservice is working without the configuration wssecurity,
when I put the settings an error occurs
- put a annotation in webservices
-----@EndpointConfig(configName="Standard WSSecurity Endpoint")
- put the files in the web-inf
------jboss-wsse-server.xml and the jboss-wsse-client.xml in the client side together with the other files
------wsse.cer
------wsse.csr
------wsse.jks
my client is in the servlet
QName qName = new QName("http://coreo.com.br/teste", "Teste");
String serviceURL = "http://jon.ctbc.com.br:8080/jbossWebServiceSecurity-1.0.0/Teste?wsdl";
Service service = null;
URL url;
try {
url = new URL(serviceURL);
service = Service.create(url,qName);
ITeste s = service.getPort(ITeste.class);
System.out.println(s.localizacao("jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj"));
} catch (MalformedURLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
09:09:30,343 ERROR [[MyServlet]] Servlet.service() for servlet MyServlet threw exception
javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy82.localizacao(Unknown Source)
at br.teste.client.MyServlet.executa(MyServlet.java:54)
at br.teste.client.MyServlet.doGet(MyServlet.java:33)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223648#4223648
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223648
17 years