April 2008 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: EJB with SSL does not work with JBoss AS 4.2.2

by dbmac45

jaikiran, I am pretty much experiencing the same results that TJ is seeing and with an almost identical setup. I followed the steps in "Chapter 9 - Transports" in the JBoss EJB 3.0 Reference Documentation. I am running JBoss AS 4.2.2, Java 1.5.0_11 and Windows XP. I added the following code to the "jboss-service.xml" file in the "server/default/deploy/ejb3.deployer/META-INF" file as specified in the JBoss EJB 3.0 Reference doc. | <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:type=Connector,transport=socket3843,handler=ejb3"> | <depends>jboss.aop:service=AspectDeployer</depends> | <attribute name="InvokerLocator">sslsocket://${jboss.bind.address}:3843</attribute> | <attribute name="Configuration"> | <handlers> | <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> | </handlers> | </attribute> | </mbean> | My EJB code looks like the following: | @RemoteBindings({ | @RemoteBinding(clientBindUrl="sslsocket://0.0.0.0:3843", jndiBinding="TitanServicesSSL"), | @RemoteBinding(jndiBinding="TitanServices") | }) | @Stateless | public class TravelAgentBean implements TravelAgentRemote { | ... | } | My test client looks like the following: | public static void main(String[] args) { | try { | // Get initial context. | Context jndiContext = getInitialContext(); | | // Get a reference to a travel agent session bean. | TravelAgentRemote travelAgentRemote = (TravelAgentRemote) jndiContext.lookup("TitanServicesSSL"); | // TravelAgentRemote travelAgentRemote = (TravelAgentRemote) jndiContext.lookup("TitanServices"); | | // Create a new cabin. | CabinDTO cabin1 = new CabinDTO(1, "Master Suite", 1, 1, 3); | | travelAgentRemote.createCabin(cabin1); | | // Retrieve the newly created cabin. If it was found then | // display it on the console and then delete it. | CabinDTO cabin2 = travelAgentRemote.findCabin(cabin1.getId()); | | if (cabin2 != null) { | System.out.println(cabin2.toString()); | | travelAgentRemote.deleteCabin(cabin1.getId()); | } | | } catch (NamingException ne) { | ne.printStackTrace(); | } | | } | | private static Context getInitialContext() throws NamingException { | return new InitialContext(); | } | | If I do a "lookup" on "TitanServices" then everything works fine. If I do a "lookup" on "TitanServicesSSL" then it fails (the lookup actually succeeds but the createCabin() method fails). I have created the appropriate keystore, self-signed certificate, etc., according to the JBoss EJB 3.0 Reference doc and have added the appropriate JVM args for the client and JBoss that point to the keystore, etc. JBoss starts successfully and without any errors. The following is the server-side exception that is thrown when I attempt to run my program using the "TitanServicesSSL" lookup. | 15:44:44,505 ERROR [ServerThread] Worker thread initialization failure | java.lang.reflect.InvocationTargetException | 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:494) | at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:720) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:368) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) | Caused by: java.net.SocketException: Socket Closed | at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:201) | at java.net.Socket.setSoTimeout(Socket.java:991) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.setSoTimeout(SSLSocketImpl.java:1971) | at org.jboss.remoting.transport.socket.SocketWrapper.setTimeout(SocketWrapper.java:85) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:168) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66) | at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46) | ... 7 more | | The following is the client-side exception that is thrown: | Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://127.0.0.1:3843/] | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) | at $Proxy0.createCabin(Unknown Source) | at com.titan.client.TitanClient.main(TitanClient.java:27) | Caused by: java.lang.reflect.InvocationTargetException | 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:494) | at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:152) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:856) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) | at $Proxy0.createCabin(Unknown Source) | at com.titan.client.TitanClient.main(TitanClient.java:27) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) | ... 10 more | Caused by: java.net.SocketException: Socket Closed | at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:201) | at java.net.Socket.setSoTimeout(Socket.java:991) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.setSoTimeout(SSLSocketImpl.java:1971) | at org.jboss.remoting.transport.socket.SocketWrapper.setTimeout(SocketWrapper.java:85) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:168) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66) | 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:494) | at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:152) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:856) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | ... 10 more | | Like TJ, the following are true: Yes, I can telnet into the SSL port (3843). Yes, the key store and passoword have been generated. Yes, the JVM arguments have been modified to point to the keystore. Yes, the client gets a references to the EJB but fails when trying to call the createCabin() method. Yes, all firewalls have been disabled. Yes, I am using the jbossall-client.jar from version 4.2.2 when running the client. The JRE version is 1.5. Thanks in advance for any help, Dave M. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146930#4146930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146930

17 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Nullpointer at JBossXSEntityResolver.getXMLInputSource

by QPool.Char

Maybe this piece of information helps: I tried wsconsume and wsimport to generate the client artifacts, and both console outputs say: | [wsimport] [WARNING] src-resolve.4.2: Error resolving component 'cms:Store'. It was detected that 'cms:Store' is in namespace 'http://www.alfresco.org/ws/model/content/1.0', but components from this namespace are not referenceable from schema document 'http://localhost:8080/alfresco/wsdl/repository-service.wsdl#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'cms:Store' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'http://localhost:8080/alfresco/wsdl/repository-service.wsdl#types?schema1'. | [wsimport] line 35 of http://localhost:8080/alfresco/wsdl/repository-service.wsdl#types?schema1 | I cannot modify the schema, cause its not mine. So i hope that its an incorrect namespace, which means that i would have to change the prefix of "cms:Store". Is "cms" the prefix? And how can i change it without changing the schema? Again external binding customization? Would be nice if anyone can confirm that i m on the right way.... thx in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146929#4146929 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146929

17 years, 12 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Eclipse doesn't load JBoss Server with endorsed libs

by rob.stryker＠jboss.com

Ah... quotes. Interesting. I'll get on that. As for native, I've just committed exactly what the .bat / .sh scripts do... which is exactly what you've just done ;) -Djava.library.path=home/bin/native I'll commit the quotes that were missing as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146918#4146918 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146918

17 years, 12 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Eclipse doesn't load JBoss Server with endorsed libs

by graben

Yes, endorsed libs are registered but the path to my server instance contains spaces and parameter entry doesn't use "". That's why I didn't worked in the past. After manually correcting everything works fine. I think JBoss Tools should check for spaces by default or even better use "" every time. :-) I'm still looking for a solution for the native libs problem. I tried to set java.library.path to native folder but unfortunately without success. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146914#4146914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146914

17 years, 12 months

1
0
0 / 0

[Clustering/JBoss] - Re: login/client id that is already connected/cluster config

by bstansberry＠jboss.com

I'm not personally familiar with the details of this aspect of JBossMQ, but your analysis sounds correct. A workaround: | <message-driven> | <ejb-name>ContatoConsumerBean</ejb-name> | <configuration-name>Standard Message Driven Bean</configuration-name> | <destination-jndi-name>queue/cadastro</destination-jndi-name> | | <mdb-user>${ContatoConsumerBean.mdb.user:CadastroUser}</mdb-user> | <mdb-passwd>CadastroUser</mdb-passwd> | <mdb-subscription-id>CadastroUser</mdb-subscription-id> | | </message-driven> | then start JBoss like this: ./run.sh -DContatoConsumerBean.mdb.user=$CADASTRO_USER_ID -c all Then on each server you'd use a different value for the $CADASTRO_USER_ID environment var. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146913#4146913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146913

17 years, 12 months

1
0
0 / 0

[JBoss jBPM] - Re: User Interface

by jalamos

Ok perfect, thank you very much kukeltje. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146909#4146909 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146909

17 years, 12 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Eclipse doesn't load JBoss Server with endorsed libs

by rob.stryker＠jboss.com

Graben: YOu're right about the native not being added. However, endorsed-libs *are* definitely added. You can double-check this by double-clicking the server, and in the server editor clicking "Open Launch Configuration". There you'll see the program arguments and java arguments being passed... and endoresed *is* there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146907#4146907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146907

17 years, 12 months

1
0
0 / 0

[Clustering/JBoss] - Re: login/client id that is already connected/cluster config

by maralcbr

I have more information from my tests. If I shutdown the first server, the error stops happening on the second one. The conclusion I can get is that the MDBs from both servers are acessing the queue on the first loaded node - what is correct. As the JMS service is HA singleton. With this info, the error could be fixed by changing the <mdb-user> and/or <mdb-subscription-id> from the MDBs on the xmls of the second server. But - it does not sound nice to have to generate different jars/ears for each node of the cluster. The farm service for example would not be usable. Any ideias/comments? Thanks. Marcelo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146903#4146903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146903

17 years, 12 months

1
0
0 / 0

[Clustering/JBoss] - Re: Unable to run multiple cluster nodes.

by bstansberry＠jboss.com

/casper-2.1**/*=loadbalancer should be /casper-2.1/*=loadbalancer No ** To get rid of the startup failures you posted, don't change the partition name in cluster-service.xml. Restore it to the original value of ${jboss.partition.name:DefaultPartition}. You can then start JBoss like this to have your partition named 'casper' ./run.sh -Djboss.partition.name=casper -c myConfig As a convenience there is a switch that does that exact same thing: ./run.sh -g casper -c myConfig As to why browsing to http://10.20.220.15:9999/casper-2.1/app no longer works, I can't say for certain based on what you've posted. I assume 9999 is the port the Tomcat HttpConnector is listening on; i.e. you've changed it from 8080. Only thing I see is that your posted "replication-trigger" element is missing the closing tag. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146895#4146895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146895

17 years, 12 months

1
0
0 / 0

[JBossWS] - Nullpointer at JBossXSEntityResolver.getXMLInputSource

by QPool.Char

Hi, there already is a similar thread here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124794#4124794 , but i think my situation is slightly different. Using JBoss 4.2.2 with integrated jbossws, i have a locally published WSDL file that i cannot manipulate. I have generated my client artifacts using Metro (wsimport tool), because i had to do some external binding customizations, which i dont know how to do with jbossws. I try to set up the service like this: RepositoryService repositoryService = | new RepositoryService(new URL("http://localhost:8080/alfresco/wsdl/repository-service.wsdl"), | new QName("repositoryService")); but i get this error: | 19:03:51,328 WARN [JBossWSEntityResolver] Trying to resolve id as a non-file URL: http://www.alfresco.org/ws/model/content/1.0 | 19:03:52,703 ERROR [STDERR] java.lang.NullPointerException | 19:03:52,703 ERROR [STDERR] at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.getXMLInputSource(JBossXSEntityResolver.java:167) | 19:03:52,703 ERROR [STDERR] at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.resolveEntity(JBossXSEntityResolver.java:135) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source) | 19:03:52,703 ERROR [STDERR] at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:182) | my wsd (excerptsl: | <wsdl:definitions name="repository-service" targetNamespace="http://www.alfresco.org/ws/service/repository/1.0"> |  |  |  | ÃÂ¢ | <wsdl:types> | ÃÂ¢ÃÂÃÂ | <schema elementFormDefault="qualified" targetNamespace="http://www.alfresco.org/ws/service/repository/1.0"> | <xsd:import namespace="http://www.alfresco.org/ws/headers/1.0" schemaLocation="../wsdl/headers.xsd"/> | <xsd:import namespace="http://www.alfresco.org/ws/cml/1.0" schemaLocation="../wsdl/cml.xsd"/> | ÃÂ¢ÃÂÃÂ | <element name="createStore"> | ÃÂ¢ÃÂÃÂ | <complexType> | ÃÂ¢ÃÂÃÂ | <sequence> | <element name="scheme" type="xsd:string"/> | <element name="address" type="xsd:string"/> | </sequence> | </complexType> | </element> | ÃÂ¢ÃÂÃÂ | <element name="createStoreResponse"> | ÃÂ¢ÃÂÃÂ | <complexType> | ÃÂ¢ÃÂÃÂ | <sequence> | <element name="createStoreReturn" type="cms:Store"/> | </sequence> | </complexType> | </element> | ÃÂ¢ÃÂÃÂ | <element name="getStores"> | ÃÂ¢ÃÂÃÂ | <complexType> | <sequence/> | </complexType> | </element> | ÃÂ¢ÃÂÃÂ | <element name="getStoresResponse"> | ÃÂ¢ÃÂÃÂ | <complexType> | ÃÂ¢ÃÂÃÂ | <sequence> | <element name="getStoresReturn" type="cms:Store" minOccurs="1" maxOccurs="unbounded"/> | </sequence> | </complexType> | </element> | ÃÂ¢ÃÂÃÂ | <element name="query"> | ÃÂ¢ÃÂÃÂ | <complexType> | ÃÂ¢ÃÂÃÂ | <sequence> | <element name="store" type="cms:Store"/> | <element name="query" type="cms:Query"/> | <element name="includeMetaData" type="xsd:boolean"/> | </sequence> | </complexType> | </element> | ÃÂ¢ÃÂÃÂ.................... | </schema> | </wsdl:types> | ÃÂ¢ÃÂÃÂ | <wsdl:message name="Headers"> | <wsdl:documentation>Defines the SOAP headers used by this service.</wsdl:documentation> | <wsdl:part element="rep:QueryConfiguration" name="QueryConfiguration"/> | </wsdl:message> | ÃÂ¢ÃÂÃÂ | <wsdl:message name="createStoreRequest"> | <wsdl:part element="rep:createStore" name="parameters"/> | </wsdl:message> | ÃÂ¢ÃÂÃÂ | <wsdl:message name="createStoreResponse"> | <wsdl:part element="rep:createStoreResponse" name="parameters"/> | </wsdl:message> | ÃÂ¢ÃÂÃÂ | ............ÃÂ¢ÃÂÃÂ | <wsdl:service name="RepositoryService"> | ÃÂ¢ÃÂÃÂ | <wsdl:documentation> | Provides read and write operations against a repository. | </wsdl:documentation> | ÃÂ¢ÃÂÃÂ | <wsdl:port binding="rep:RepositoryServiceSoapBinding" name="RepositoryService"> | <wsdlsoap:address location="http://localhost:8080/alfresco/api/RepositoryService"/> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | Injection also doesnt work, as expected. And using an empty constructor also doesnt work. Any hints on this? Do i have to upgrade jbossws? Or any workaround to show the method where to search for my xsd? thx in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146891#4146891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146891

17 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user April 2008