[JBoss Web Services] - Policy not supported problem
by marcin.motyka
marcin.motyka [https://community.jboss.org/people/marcin.motyka] created the discussion
"Policy not supported problem"
To view the discussion, visit: https://community.jboss.org/message/775940#775940
--------------------------------------------------------------
Hello everyone.
I'm facing a strange problem while developing a web service client secured with *WS Security Username Token Profile 1.0.*
I've created a maven project and developed client out of wsdl file. The secured webservice was created by another company, not by me.
We need to put this client to our regular JAX-WS webservice.
The client is working fine while I test it from my local machine. The problem is when I run it on another webservice. Then I got an exception in JBoss console:
*Policy not supported! #wss_username_token_service_policy*
I'm running JBoss 5.1.0.GA
Exception:
ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.RuntimeException: javax.xml.ws.WebServiceException
: org.jboss.ws.WSException: Policy not supported! #wss_username_token_service_policy
at com.comarch.comarchgis.ws.wss.WSSClient.getService(WSSClient.java:46)
at com.comarch.comarchgis.ws.wss.WSSClient.uwierzytelnij(WSSClient.java:
54)
at com.comarch.comarchgis.ws.auth.service.WsService.authUser(WsService.j
ava:89)
at com.comarch.comarchgis.ws.auth.AuthWebServiceImpl.uwierzytelnijG2(Aut
hWebServiceImpl.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(A
bstractInvocationHandlerJSE.java:129)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpoin
tInvoker.java:240)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:505)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:300)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:207)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.java:132)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(Abstract
EndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce
ss(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok
e(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
7)
at java.lang.Thread.run(Thread.java:662)
Is there a way to get it running on that JBoss ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/775940#775940]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[jBPM] - jbpm 5.3 sessions, dispose and SessionInfo table, across machines
by Sam Matsoukis
Sam Matsoukis [https://community.jboss.org/people/matsoukis] created the discussion
"jbpm 5.3 sessions, dispose and SessionInfo table, across machines"
To view the discussion, visit: https://community.jboss.org/message/775850#775850
--------------------------------------------------------------
hello,
I am using jbpm 5.3 in persisted to db. Am able to work through most of the setup, but have come across a "leak" of session ids in the SessionInfo table. This was reported in https://issues.jboss.org/browse/JBPM-3582 https://issues.jboss.org/browse/JBPM-3582 and is scheduled to be addressed in jbpm 6. The SingleSessionCommandService line 360 (jbpm 5.3 final) reads "if ( !(command instanceof DisposeCommand) ) {" where the dispose is explicitly pruned.
To minimize the "leak" above lead me to reuse sessionIds, where meaningful, by loading sessions by Id.
This brings me to my question, spurred by discussion in https://community.jboss.org/thread/168837 https://community.jboss.org/thread/168837 where session usage, thread safeness and scope is covered. My question relates to session usage across machines. Scenario: Machine A and Machine B are failover+loadbalanced duplicates of each other and persist to a common database cluster. May these two machines load sessions with the same sessionId? Allowed or Not?
Thanks in advance for any feedback - sam.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/775850#775850]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months