[JBossWS] - Re: HELP with error
by ajay662
Now that I figured out that I was using the wrong endpoint address, my next question [to the jboss team] is why is this exception logged at ERROR level by the "org.jboss.ws.jaxrpc.CallImpl" class? My endpoints are dynamic and I know them only at run time and its perfectly normal for some of the endpoints (network devices in my case) to be down. I don't want to clutter my log with these exceptions.
Currently only way i can suppress these is by changing the log4j.xml, but I am afraid that by doing this some of the other important ERROR messages will be filtered out.
<category name="org.jboss.ws.jaxrpc.CallImpl">
| <priority value="FATAL"/>
| </category>
Does it make sense to not log this exception at ERROR level??
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990551#3990551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990551
17 years, 5 months
[JBossWS] - WSS problem in JBossWS 1.0.4 sample
by rayymlai
I can run JBossWS 1.0.3 sample JSR181EJB3 and JSR181POJO on JBoss 4.0.5, and can view the WSS header. I can even modify the jboss-wsse-client.xml in the JSR181 EJB3 example to use username token. I can view the WSS username token in the SOAP header from the output/log/samples.log.
However, once I upgrade to JBossWS 1.0.4 sample, I cannot view any WSS header in the SOAP header from any of the examples (including JSR181EJB3 and JSR181POJO). I did not modify the source code yet.
I notice several changes in JBossWS 1.0.4. The JSR181EJB3 does not use any security handler. I add the security handler in the EJBbean03.java, as in JBossWS 1.0.3. I have to rename the class name because JBossWS 1.0.4 renames it with the package name org.jboss.ws.wsse.jaxrpc (an extra jaxrpc). However, I still cannot view the WSS header in the output/log/samples.log.
I did attempt to use tcpmon, tcpspy to view the SOAP message but without luck to find the WSS header. I changed the client config file to use username token. The same result.
It looks like the new JBossWS 1.0.4 samples can't generate any WSS. Pls refer to the log file below. It is possible that the security handler in JBossWS 1.0.4 reads the client config file, and cannot generate the security config, and thus it cannot generate the WSS header.
2006-11-30 18:05:41,781 DEBUG [org.jboss.ws.metadata.config.WSConfigFactory:92] parse: jar:file:/C:/tools/jboss/jbossws-samples-1.0.4.GA/thirdparty/jbossws-client.jar!/META-INF/standard-jaxrpc-client-config.xml
2006-11-30 18:05:42,203 DEBUG [org.jboss.ws.deployment.JSR109ClientMetaDataBuilder:131] END buildMetaData:
UnifiedMetaData:
implementation: jbossws-1.0.4.GA (date=200611150150)
securityDomain: null
ServiceMetaData:
qname={http://org.jboss.ws/samples/jsr181ejb}TestService
wsdName=null
wsdlFile=jar:file:/C:/tools/jboss/server/default/tmp/deploy/tmp1581jaxws-samples-jsr181ejb-client.jar!/META-INF/wsdl/TestService.wsdl
jaxrpcFile=http://www.jboss.org/jbossws/dummy-mapping-url
publishLocation=null
properties=null
TypesMetaData:
ClientEndpointMetaData:
type=JAXRPC
qname={http://org.jboss.ws/samples/jsr181ejb}EndpointInterfacePort
address=http://MTVL04AL3M0346:8080/jaxws-samples-jsr181ejb/EJB3Bean01
binding=http://schemas.xmlsoap.org/wsdl/soap/http
seiName=org.jboss.test.ws.jaxws.samples.jsr181ejb.EndpointInterface
configFile=META-INF/standard-jaxrpc-client-config.xml
configName=Standard WSSecurity Client
authMethod=null
transportGuarantee=null
properties=null
OperationMetaData:
qname={http://org.jboss.ws/samples/jsr181ejb}echo
javaName=echo
style=rpc/literal
oneWay=false
soapAction=
ParameterMetaData:
xmlName=String_1
xmlType={http://www.w3.org/2001/XMLSchema}string
javaType=java.lang.String
mode=IN
inHeader=false
wrappedVariables=[]
wrappedTypes=[]
wrappedElementNames=[]
ReturnMetaData:
xmlName=result
xmlType={http://www.w3.org/2001/XMLSchema}string
javaType=java.lang.String
mode=OUT
inHeader=false
wrappedVariables=[]
wrappedTypes=[]
wrappedElementNames=[]
HandlerMetaDataJAXRPC:
type=POST
name=WSSecurityHandlerOutbound
class=org.jboss.ws.wsse.jaxrpc.WSSecurityHandlerOutbound
params=[]
headers=[]
roles=[]
ports=[]
2006-11-30 18:05:42,203 DEBUG [org.jboss.ws.metadata.UnifiedMetaData:180] Eagerly initialize the meta data model
2006-11-30 18:05:42,218 DEBUG [org.jboss.ws.metadata.OperationMetaData:240] Found best matching java method: public abstract java.lang.String org.jboss.test.ws.jaxws.samples.jsr181ejb.EndpointInterface.echo(java.lang.String) throws java.rmi.RemoteException
2006-11-30 18:05:42,609 WARN [org.jboss.ws.metadata.HandlerMetaData:161] WS-Security requires security configuration
2006-11-30 18:05:42,609 DEBUG [org.jboss.ws.jaxrpc.ServiceObjectFactory:308] Adding client side handler to endpoint '{http://org.jboss.ws/samples/jsr181ejb}EndpointInterfacePort': [class=org.jboss.ws.wsse.jaxrpc.WSSecurityHandlerOutbound,headers=[],config={org.jboss.ws.metadata.HandlerMetaData$HandlerType=POST}]
2006-11-30 18:05:42,625 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:93] Create a handler chain for roles: []
2006-11-30 18:05:42,640 DEBUG [org.jboss.ws.jaxrpc.HandlerRegistryImpl:116] Add handler to: {http://org.jboss.ws/samples/jsr181ejb}EndpointInterfacePort
HandlerMetaDataJAXRPC:
type=ENDPOINT
name=null
class=org.jboss.ws.wsse.jaxrpc.WSSecurityHandlerOutbound
params=[]
headers=[]
roles=[]
ports=[]
2006-11-30 18:05:42,656 DEBUG [org.jboss.ws.jaxrpc.ServiceProxy:112] Invoke on jaxrpc service: getPort
2006-11-30 18:05:42,671 DEBUG [org.jboss.ws.soap.MessageContextAssociation:46] pushMessageContext: org.jboss.ws.jaxrpc.handler.SOAPMessageContextJAXRPC@19646fd
2006-11-30 18:05:42,718 DEBUG [org.jboss.ws.binding.EndpointInvocation:94] setRequestParamValue: [name=String_1,value=java.lang.String]
2006-11-30 18:05:42,718 DEBUG [org.jboss.ws.common.CommonSOAPBinding:131] bindRequestMessage: {http://org.jboss.ws/samples/jsr181ejb}echo
2006-11-30 18:05:42,750 DEBUG [org.jboss.ws.common.CommonSOAPBinding:160] Create RPC body element: {http://org.jboss.ws/samples/jsr181ejb}echo
2006-11-30 18:05:42,750 DEBUG [org.jboss.ws.binding.EndpointInvocation:100] getRequestParamValue: String_1
2006-11-30 18:05:42,750 DEBUG [org.jboss.ws.binding.EndpointInvocation:237] transformPayloadValue: java.lang.String -> java.lang.String
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.soap.SOAPContentElement:334] setObjectValue: Hello world!
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:249] Enter: handleRequest
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:468] Replacing dirty handler: [state=DOES_NOT_EXIST,handler=org.jboss.ws.wsse.jaxrpc.WSSecurityHandlerOutbound@189635d]
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerWrapper:93] init: org.jboss.ws.wsse.jaxrpc.WSSecurityHandlerOutbound@da9ea4
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:298] Exit: handleRequest with status: true
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:249] Enter: handleRequest
2006-11-30 18:05:42,765 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:298] Exit: handleRequest with status: true
2006-11-30 18:05:42,781 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:249] Enter: handleRequest
2006-11-30 18:05:42,781 WARN [org.jboss.ws.wsse.jaxrpc.WSSecurityHandler:92] Cannot obtain security configuration
2006-11-30 18:05:42,781 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:298] Exit: handleRequest with status: true
2006-11-30 18:05:42,796 DEBUG [org.jboss.ws.soap.SOAPConnectionImpl:202] Get locator for: [addr=http://MTVL04AL3M0346:8080/jaxws-samples-jsr181ejb/EJB3Bean01,props={javax.xml.rpc.service.endpoint.address=http://MTVL04AL3M0346:8080/jaxws-samples-jsr181ejb/EJB3Bean01, javax.xml.rpc.security.auth.password=thefrog, javax.xml.rpc.security.auth.username=kermit}]
2006-11-30 18:05:42,796 DEBUG [org.jboss.remoting.Client:514] invoke called, but our invoker is disconnected, discarding and fetching another fresh invoker for: InvokerLocator [http://192.168.234.1:8080/jaxws-samples-jsr181ejb/EJB3Bean01]
2006-11-30 18:05:42,796 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker:275] connect called for: org.jboss.remoting.transport.http.HTTPClientInvoker@9e8c34
2006-11-30 18:05:42,812 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker:146] Setting request header with SOAPAction : ""
2006-11-30 18:05:42,828 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker:146] Setting request header with Content-Type : text/xml; charset=UTF-8
2006-11-30 18:05:42,843 DEBUG [org.jboss.ws.soap.SOAPContentElement:159] getXMLFragment from Object [xmlType={http://www.w3.org/2001/XMLSchema}string,javaType=class java.lang.String]
2006-11-30 18:05:42,843 DEBUG [org.jboss.ws.jaxrpc.encoding.SimpleSerializer:56] serialize: [xmlName=String_1,xmlType={http://www.w3.org/2001/XMLSchema}string]
2006-11-30 18:05:42,859 DEBUG [org.jboss.ws.soap.SOAPContentElement:185] xmlFragment: <String_1>Hello world!</String_1>
2006-11-30 18:05:42,921 DEBUG [org.jboss.ws.binding.soap.SOAPMessageUnMarshaller:106] getMimeHeaders from: {X-Powered-By=[Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5], null=[HTTP/1.1 200 OK], ResponseCodeMessage=OK, http.basic.password=thefrog, Date=[Fri, 01 Dec 2006 02:05:42 GMT], http.basic.username=kermit, Content-Type=[text/xml;charset=UTF-8], Server=[Apache-Coyote/1.1], HEADER={SOAPAction="", Content-Type=text/xml; charset=UTF-8}, Transfer-Encoding=[chunked], ResponseCode=200}
2006-11-30 18:05:42,953 DEBUG [org.jboss.ws.soap.MessageFactoryImpl:165] createMessage: [contentType=text/xml; charset=UTF-8]
2006-11-30 18:05:42,968 DEBUG [org.jboss.ws.soap.SOAPContentElement:211] setXMLFragment: Hello world!
2006-11-30 18:05:42,968 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:331] Enter: handleResponse
2006-11-30 18:05:42,984 WARN [org.jboss.ws.wsse.jaxrpc.WSSecurityHandler:92] Cannot obtain security configuration
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:380] Exit: handleResponse with status: true
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:331] Enter: handleResponse
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:380] Exit: handleResponse with status: true
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:331] Enter: handleResponse
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.handler.HandlerChainBaseImpl:380] Exit: handleResponse with status: true
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.common.CommonSOAPBinding:531] unbindResponseMessage: {http://org.jboss.ws/samples/jsr181ejb}echo
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.binding.EndpointInvocation:171] setReturnValue: org.jboss.ws.soap.SOAPContentElement
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.binding.EndpointInvocation:177] getReturnValue
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.soap.SOAPContentElement:231] getObjectValue [xmlType={http://www.w3.org/2001/XMLSchema}string,javaType=class java.lang.String]
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.jaxrpc.encoding.SimpleDeserializer:47] deserialize: [xmlName=result,xmlType={http://www.w3.org/2001/XMLSchema}string]
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.soap.SOAPContentElement:326] objectValue: java.lang.String
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.binding.EndpointInvocation:237] transformPayloadValue: org.jboss.ws.soap.SOAPContentElement -> java.lang.String
2006-11-30 18:05:42,984 DEBUG [org.jboss.ws.soap.MessageContextAssociation:75] popMessageContext: org.jboss.ws.jaxrpc.handler.SOAPMessageContextJAXRPC@19646fd
Any input, suggestion?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990544#3990544
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990544
17 years, 5 months
[JBossWS] - Re: implementing wsse:UserNameToken
by rayymlai
Thomas:
in my previous threads, we re-use JBossWS examples.
I notice that there is an additional step missing. In your Java bean, you need to use annotation to specify the security handler (this is not documented in JBossWS). Pls refer to JSR181 EJB3 example.
one colleague of mine advised me that he learned from JBoss support that WSS username token only works with the JSR181 EJB3 example, not JSR181 POJO. Apparently, JBossWS 1.0.3 JSR181 POJO can't use the security handler (as in EJB3 example). It complains it cannot get the security configuration. It is possible that the security handler is customized for the EJB3 example (for JAAS authentication).
I've done verification and confirmed that.
any resolution?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990535#3990535
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990535
17 years, 5 months
[JBossWS] - HELP with error "Can not connect http client invoker"
by ajay662
My development environment is
jboss 4.0.5.GA
jbossws-1.0.4.GA
Trying to consume remote web-services from an MDB, using "service-ref" element in the deployment descriptor as mentioned in the JBossWS User guide. While invoking a web-service method, I get the following exception. I have looked through the forums but did not find any relevant help...
I have already tried to increase the timeout value to 2 minutes using StubExt class... same results. My standalone client (outside of Jboss) works fine.
Here is the exception stack
13:18:47,103 ERROR [CallImpl] Call invocation failed with unkown Exception
| javax.xml.soap.SOAPException: Could not transmit message
| at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:204)
| at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:687)
| at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404)
| at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148)
| at $Proxy73.getSipCacheStatus(Unknown Source)
| at com.mycompany.enms.status.PollClusterMDB.pollCluster(PollClusterMDB.java:120)
| at com.mycompany.enms.status.PollClusterMDB.onMessage(PollClusterMDB.java:144)
| 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:585)
| at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
| at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:495)
| at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
| at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
| at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
| at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173)
| at org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT.invoke(MessageDrivenTxInterceptorBMT.java:47)
| at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:116)
| at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:109)
| at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
| at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
| at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:402)
| at org.jboss.ejb.Container.invoke(Container.java:954)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:987)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1287)
| at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:266)
| at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:905)
| at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
| at org.jboss.mq.SpySession.run(SpySession.java:323)
| at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:201)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81)
| at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
| at org.jboss.remoting.Client.invoke(Client.java:525)
| at org.jboss.remoting.Client.invoke(Client.java:488)
| at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189)
| ... 32 more
| Caused by: java.net.ConnectException: Connection timed out: connect
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.Socket.connect(Socket.java:516)
| at sun.net.NetworkClient.doConnect(NetworkClient.java:152)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
| at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
| at sun.net.www.http.HttpClient.New(HttpClient.java:287)
| at sun.net.www.http.HttpClient.New(HttpClient.java:299)
| at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:796)
| at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:748)
| at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:673)
| at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:840)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:163)
| ... 37 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990528#3990528
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990528
17 years, 5 months