[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
19 years, 5 months
[JCA/JBoss] - Not getting XADataSource
by pkdj
I'm using JBoss 4.0.5.GA with Oracle 10g. I created a datasource definition in server/default/deploy/oracle-xa-ds.xml as follows:
| <datasources>
| <xa-datasource>
| <jndi-name>BasicService01DS</jndi-name>
| <track-connection-by-tx>true</track-connection-by-tx>
| <no-tx-separate-pools>true</no-tx-separate-pools>
| <isSameRM-override-value>false</isSameRM-override-value>
| <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
| <xa-datasource-property name="URL">
| jdbc:oracle:thin:@weezer:1521:demo1
| </xa-datasource-property>
| <xa-datasource-property name="User">bs01</xa-datasource-property>
| <xa-datasource-property name="Password">bs01</xa-datasource-property>
| <exception-sorter-class-name>
| org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
| </exception-sorter-class-name>
| </xa-datasource>
|
| <mbean code="org.jboss.resource.adapter.jdbc.vendor.OracleXAExceptionFormatter"
| name="jboss.jca:service=OracleXAExceptionFormatter">
| <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
| </mbean>
| </datasources>
When I look at it in the JXM console, it shows
+- BasicService01DS (class: javax.sql.DataSource)
|
When I try to get a transactional connection using JBoss Transactions' TransactionalDriver
Connection conn = arjunaJDBC2Driver.connect("jdbc:arjuna:java:BasicService01DS", new Properties());
it throws a ClassCastException
14:20:27,308 ERROR [STDERR] java.lang.ClassCastException: org.jboss.resource.adapter.jdbc.WrapperDataSource
For some reason the datasource definition above is not realizing an XA datasource. Does this indicate that the Oracle database is not configured to support XA (I'm checking into this now) or is it some other configuration I've neglected to perform in JBoss?
Thanks,
Paul
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990543#3990543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990543
19 years, 5 months
[Security & JAAS/JBoss] - JAAS newbie - missing something that should be obvious
by grego＠spiekerpoint.com
I'm using jboss-4.0.5.GA installed with the ejb3 "flavor". I'm using the default install.
Playing around with securing some web content. I created a login.html page for now that has the proper fields: j_username & j_password. Its post action references j_security_check.
jboss-web.xml:
| <?xml version="1.0" encoding="UTF-8"?>
| <jboss-web>
| <security-domain>java:/jaas/SPDB</security-domain>
| </jboss-web>
|
web.xml:
| <web-app>
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>All resources</web-resource-name>
| <description>Protects all resources</description>
| <url-pattern>/*</url-pattern>
|
|
| </web-resource-collection>
| <auth-constraint>
| <role-name>MyUser</role-name>
| </auth-constraint>
| </security-constraint>
|
| <security-role>
| <description>My User Role</description>
| <role-name>MyUser</role-name>
| </security-role>
|
| <login-config>
| <auth-method>FORM</auth-method>
| <realm-name>SPDB</realm-name>
| <form-login-config>
| <form-login-page>/login.html</form-login-page>
| <form-error-page>/error.html</form-error-page>
| </form-login-config>
| </login-config>
| </web-app>
|
I've copied one of the other application-policy sections from login-config.xml trying to get some sort of response out of JBoss in the log files. This is what I've added in to login-config.xml right now (in $JBOSS_HOME/server/default/conf):
| <application-policy name = "SPDB">
| <authentication>
| <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
| flag = "required">
| <module-option name = "unauthenticatedIdentity">guest</module-option>
| <module-option name = "dsJndiName">java:/polarDS</module-option>
| <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
| <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
Here is what happens: when I hit the URL of a secured jsp page, the login page comes up as it should. When I type in the user name, pw and hit "login", I immediately get the error page.
The JBoss console and log files don't even show a single message when I press "login" - let alone showing an entry that anything went wrong..
In fact, the startup logs don't even mention the new application-policy (called "SPDB"); they should - shouldn't they?
I'm left thinking that perhaps JAAS isn't even turned on. Being a newbie, I've poured through the documentation and can't find anything on "turning on" JAAS security - it appears to be turned on by default (am I wrong there?).
I expect I'm missing something simple, and I would appreciate any pointers that you can provide...
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990542#3990542
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990542
19 years, 5 months
[JCA/JBoss] - config hibernate->jboss connection pooling
by mikedanese
on Jboss4.04 hibernate3
followed howto's and (thought) I have setup jboss-conn pooling. However, server.log emits "not for production use"?? what pooling am I using? How can I tell hibernate to use jboss pooling?
11:18:37,500 INFO [DriverManagerConnectionProvider] Using Hibernate built-in connection pool (not for production use!)
11:18:37,765 INFO [DriverManagerConnectionProvider] Hibernate connection pool size: 20
11:18:37,765 INFO [DriverManagerConnectionProvider] autocommit mode: false
11:18:37,765 INFO [DriverManagerConnectionProvider] using driver: com.mysql.jdbc.Driver at URL: jdbc:mysql://localhost/alertnet2
<hibernate-configuration>
<session-factory>
com.mysql.jdbc.Driver
jdbc:mysql://localhost/alertnet2
<property name="hibernate.connection.username
<jboss-web>
<context-root>/</context-root>
<resource-ref>
<res-ref-name>jdbc/mySQL</res-ref-name>
<jndi-name>java:/jdbc/mySQL</jndi-name>
<res-type>javax.sql.DataSource</res-type>
</resource-ref>
</jboss-web>
mysql-ds.xml
<local-tx-datasource>
<jndi-name>jdbc/mySQL</jndi-name>
<connection-url>jdbc:mysql://localhost/alertnet2</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>capuser</user-name>
capuser
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<!-- intent: close pooled connections sitting idle for 30 minutes -->
<idle-timeout-minutes>30</idle-timeout-minutes>
<!-- should only be used on drivers after 3.22.1 with "ping" support -->
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
<!-- sql to call when connection is created -->
<new-connection-sql>Select 1 from USER</new-connection-sql>
<!-- sql to call on an existing pooled connection when it is obtained from pool
- MySQLValidConnectionChecker is preferred for newer drivers -->
<check-valid-connection-sql>Select 1 from USER</check-valid-connection-sql>
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<type-mapping>mySQL</type-mapping>
</local-tx-datasource>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990541#3990541
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990541
19 years, 5 months
[Messaging, JMS & JBossMQ] - Re: MDBs and Connection Factories
by somejunk
Incorrectly posted earlier ? sorry
I have a two node JBoss 4.0.2 cluster with one node per machine. I set the connection factories in \jboss-4.0.2\server\bbw\deploy-hasingleton\jms\ uil2-service.xml as
QueueConnectionFactory
ConnectionFactory
java:/JmsXA
jboss:service=Naming
TopicConnectionFactory
ConnectionFactory
java:/JmsXA
jboss:service=Naming
I am trying to see the connection factories listed on the jmx-console of both machines. But I only see them on the node that is started first and I get the following error message
javax.naming.NameNotFoundException: queue 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:267)
at org.jboss.ha.jndi.TreeHead.lookupLocally(TreeHead.java:296)
at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:215)
at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155)
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.ha.framework.server.HARMIServerImpl.invoke(HARMIServerImpl.java:209)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
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:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990537#3990537
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990537
19 years, 5 months
[Messaging, JMS & JBossMQ] - MDBs and Connection Factories
by somejunk
I have a two node JBoss 4.0.2 cluster with one node per machine. I set the connection factories in \jboss-4.0.2\server\bbw\deploy-hasingleton\jms\ uil2-service.xml as
QueueConnectionFactory
ConnectionFactory
java:/JmsXA
jboss:service=Naming
TopicConnectionFactory
ConnectionFactory
java:/JmsXA
jboss:service=Naming
I am trying to see the connection factories listed on the jmx-console of both machines. But I only see them on the node that is started first and I get the following error message
javax.naming.NameNotFoundException: queue 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:267)
at org.jboss.ha.jndi.TreeHead.lookupLocally(TreeHead.java:296)
at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:215)
at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155)
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.ha.framework.server.HARMIServerImpl.invoke(HARMIServerImpl.java:209)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
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:595)
Any help appreciated Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990536#3990536
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990536
19 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
19 years, 5 months