[JBoss AS 7 Development] - JBoss AS 7.1.1.Final custom login module for remoting and custom principal
by Sebastian Raue
Sebastian Raue [https://community.jboss.org/people/sraue] created the discussion
"JBoss AS 7.1.1.Final custom login module for remoting and custom principal"
To view the discussion, visit: https://community.jboss.org/message/726343#726343
--------------------------------------------------------------
For remoting we have made a custom login module which extends org.jboss.security.auth.spi.AbstractServerLoginModule.
The overwritten method getIdenttity() returns a custom principal - ApplicationPrincipal.
We can access the principal inside our ejbs via
@Resource
public SessionContext sessionContext;
....
Principal principal = sessionContext.getCallerPrincipal();
....
but we get a ClassCastException when we try to cast the returned Principal into ApplicationPrincipal.
On the other hand principal.getClass().getName() returns the expected class name.
The problem is that our login module is deployed as a jboss module (<jboss-home>/modules) - inside a jar which also
contains ApplicationPrincipal. The ear containing our ejb.jar which contains our ejbs also contains a copy of ApplicationPrincipal.
The problem is that our custom login module and the ApplicationPrincipal are loaded by one class loader and our
ejbs and the ApplicationPrincipal copy are loaded by another class loader. The ApplicationPrincipal from the login module which we get
by calling sessionContext.getCallerPrincipal() in the ejb is no ApplicationPrincipal known by the ejbs.
What can we do to solve this problem?
I have tried to put the custom login module code into our ear and adjusted the "module" attribute value of <login-module>
in our standalone.xml to deployment.<app-name>.ear.<ejb-jar-name>.jar but it did not work. Exception on the remote client was:
javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
As a separate module and the respective <login-module> configuration in standalone.xml the authentication works fine with our login module
- we only have the described ClassCastException problem.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/726343#726343]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 7 months
[JBoss AS 7 Development] - EJBCLIENT000024: No EJB receiver available for handling
by Michael Gronau
Michael Gronau [https://community.jboss.org/people/Michael_Gronau] created the discussion
"EJBCLIENT000024: No EJB receiver available for handling"
To view the discussion, visit: https://community.jboss.org/message/753527#753527
--------------------------------------------------------------
Hi,
During some stress-testing our application, i get this exception, when we create multiple EJBClientContext Objects in different threads simultaniously (only in some of those threads):
java.lang.IllegalStateException : EJBCLIENT000024: No EJB receiver available for handling [appName:jas-application, moduleName:core-ejb, distinctName:] combination
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:522)
at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:161)
at org.jboss.ejb.client.naming.ejb.EjbNamingContext.doCreateProxy(EjbNamingContext.java:135)
at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:113)
... 9 more
In our case this exception occurs in at least 1 Thread when connecting and looking up a stateful bean with more than 10 Threads at the same time.
Some debugging around this has shown that this exception is thrown because of a hard-coded timeout value in the class org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(). The code line has a TODO:
| | boolean successfulHandshake = false; |
| | try { |
| | // wait for the handshake to complete |
| | *// TODO: Think about externalizing this timeout* |
| | *successfulHandshake = versionHandshakeLatch.await(5, TimeUnit.SECONDS);* |
| | if (successfulHandshake) { |
| | final Channel compatibleChannel = versionReceiver.getCompatibleChannel(); |
| | final ChannelAssociation channelAssociation = new ChannelAssociation(this, context, compatibleChannel, this.clientProtocolVersion, this.marshallerFactory, this.reconnectHandler); |
| | synchronized (this.channelAssociations) { |
| | this.channelAssociations.put(context, channelAssociation); |
| | } |
| | Logs.REMOTING.successfulVersionHandshake(context, compatibleChannel); |
| | } else { |
| | // no version handshake done. close the context |
| | Logs.REMOTING.versionHandshakeNotCompleted(context); |
| | context.close(); |
| | } |
| | } catch (InterruptedException e) { |
| | context.close(); |
| | } |
When stressing the remote ejb client enough the client EJBClientContext is closed silently (because version handshake was not done within 5 seconds) and so no ejb receivers are available.
I think, to make the timeout configurable would be a perfect solution for us.
Should I create an Issue in JIRA?
With best regards,
Michael
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/753527#753527]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss AS 7 Development] - EJB invocations from a remote client using JNDI: Invalid User
by Alano de Campos
Alano de Campos [https://community.jboss.org/people/alanoc] created the discussion
"EJB invocations from a remote client using JNDI: Invalid User"
To view the discussion, visit: https://community.jboss.org/message/754534#754534
--------------------------------------------------------------
I'm trying to invocations from a remote client using JNDI in JBOSS 7.1.1, but I get the exception:
[main] DEBUG org.jboss.logging - Logging Provider: org.jboss.logging.Log4jLoggerProvider
[main] INFO org.jboss.ejb.client - JBoss EJB Client version 1.0.5.Final
[main] DEBUG org.jboss.ejb.client.EJBClientPropertiesLoader - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@601bb1
[main] DEBUG org.jboss.ejb.client.EJBClientPropertiesLoader - Found jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@601bb1
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - endpoint.create.options. has the following options {}
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - remote.connectionprovider.create.options. has the following options {org.xnio.Options.SSL_ENABLED=>false}
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - remote.connection.default.connect.options. has the following options {org.xnio.Options.SASL_DISALLOWED_MECHANISMS=>[JBOSS-LOCAL-USER]}
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - remote.connection.default.channel.options. has the following options {}
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - Connection org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration$RemotingConnectionConfigurationImpl@13bd574 successfully created for connection named default
[main] DEBUG org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration - No clusters configured in properties
[main] INFO org.xnio - XNIO Version 3.0.3.GA
[main] INFO org.xnio.nio - XNIO NIO Implementation Version 3.0.3.GA
[main] INFO org.jboss.remoting - JBoss Remoting version 3.2.3.GA
[Remoting "config-based-ejb-client-endpoint" write-1] DEBUG org.xnio.nio - Started channel thread 'Remoting "config-based-ejb-client-endpoint" write-1', selector sun.nio.ch.WindowsSelectorImpl@181ed9e
[Remoting "config-based-ejb-client-endpoint" read-1] DEBUG org.xnio.nio - Started channel thread 'Remoting "config-based-ejb-client-endpoint" read-1', selector sun.nio.ch.WindowsSelectorImpl@18f5824
[Remoting "config-based-ejb-client-endpoint" task-4] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Channel Channel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to localhost/127.0.0.1:4447 opened for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]} Waiting for version handshake message from server
[Remoting "config-based-ejb-client-endpoint" task-4] INFO org.jboss.ejb.client.remoting.VersionReceiver - Received server version 1 and marshalling strategies [river]
[main] INFO org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]} on channel Channel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to localhost/127.0.0.1:4447
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Received module availability report for 5 modules
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='cissupdateserver-ear', moduleName='cissupdateserver', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]}
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='jsr-77', moduleName='jsr-77', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]}
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='cissupdateserver-ear', moduleName='cissupdateserver-ear', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]}
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='cissupdateserver-ear', moduleName='cisscore', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]}
[Remoting "config-based-ejb-client-endpoint" task-2] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='cissupdateserver-ear', moduleName='cissupdateserver-ejb', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@da18ac, receiver=Remoting connection EJB receiver [connection=Remoting connection <1bde4>,channel=jboss.ejb,nodename=alano]}
[Remoting "config-based-ejb-client-endpoint" task-2] WARN org.jboss.ejb.client.remoting.ChannelAssociation - Unsupported message received with header 0xffffffff
[main] DEBUG org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector - Registered 1 remoting EJB receivers for EJB client context org.jboss.ejb.client.EJBClientContext@da18ac
[main] DEBUG org.jboss.ejb.client.EJBClientContext - org.jboss.ejb.client.RandomDeploymentNodeSelector@15f7107 deployment node selector selected alano node for appname=cissupdateserver-ear,modulename=cissupdateserver-ejb,distinctname=
[Remoting "config-based-ejb-client-endpoint" task-1] INFO org.jboss.ejb.client.remoting.ChannelAssociation - Discarding result for invocation id 0 since no waiting context found
Exception in thread "main" javax.ejb.EJBAccessException: JBAS013323: Invalid User
at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:54)
at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:45)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:74)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:302)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:196)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:270)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:47)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:272)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:132)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:260)
at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:399)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.informarDados(Unknown Source)
at br.com.ciss.client.service.informacao.InformacaoServiceImpl.informarDados(InformacaoServiceImpl.java:224)
at br.com.ciss.client.agente.EnviaInformacaoMaquina.enviarInformacao(EnviaInformacaoMaquina.java:29)
at br.com.ciss.client.agente.EnviaInformacaoMaquina.main(EnviaInformacaoMaquina.java:49)
[Thread-1] DEBUG org.jboss.ejb.client.remoting.AutoConnectionCloser - Closing Remoting connection <1bde4>
[Remoting "config-based-ejb-client-endpoint" read-1] DEBUG org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Closing channelChannel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to null
[Remoting "config-based-ejb-client-endpoint" read-1] DEBUG org.jboss.ejb.client.remoting.ChannelAssociation - Closing channel Channel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to null
[Remoting "config-based-ejb-client-endpoint" read-1] DEBUG org.jboss.ejb.client.remoting.ChannelAssociation - Registering a re-connect handler org.jboss.ejb.client.remoting.EJBClientContextConnectionReconnectHandler@9a9b65 for broken channel Channel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to null in EJB client context org.jboss.ejb.client.EJBClientContext@da18ac
[Remoting "config-based-ejb-client-endpoint" task-4] INFO org.jboss.ejb.client.remoting.ChannelAssociation - Channel Channel ID f7fd41c3 (outbound) of Remoting connection 01cef4f7 to null can no longer process messages
[Thread-1] DEBUG org.jboss.ejb.client.remoting.AutoConnectionCloser - Closing endpoint "config-based-ejb-client-endpoint" <18aab40>
I'm using the security mechanisms of jboss, and I have added the user through the add-user.bat also have the file jboss-ejb-client.properties with username and password and still get the exception. I followed the example set of the link: https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+... EJB invocations from a remote client using JNDI, the same works when I'm not using the security mechanisms, but when I use the security mechanisms the error occurs
What you're missing?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754534#754534]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss AS 7 Development] - JBoss AS 7.1.1.Final Vault HornetQ Windows/Linux
by Doug Martin
Doug Martin [https://community.jboss.org/people/doug.j.martin] created the discussion
"JBoss AS 7.1.1.Final Vault HornetQ Windows/Linux"
To view the discussion, visit: https://community.jboss.org/message/757109#757109
--------------------------------------------------------------
I know there has been a lot of discussion on this topic and a number of issues opened/closed. I'm trying to make sense of were this problem currently stands and if there are any fixes / workarounds.
The following bug reports seemed to be the most relevant. It appears 5251 was Closed/Rejected but I'm still having a number of issues on 7.1.1.Final and wasn't clear on why this was closed.
https://issues.jboss.org/browse/AS7-5251 https://issues.jboss.org/browse/AS7-5251
https://issues.jboss.org/browse/AS7-5274 https://issues.jboss.org/browse/AS7-5274
I followed the following instruction on Windows and Linux:
https://community.jboss.org/docs/DOC-17763 https://community.jboss.org/wiki/AS7PasswordVaultOnWindows
On both platforms I get the following error when I try to use the vault with netty connectors/acceptors:
2012-08-30 15:03:55,880 SEVERE [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Failure in initialisation: java.lang.IllegalStateException: Unable to create NettyAcceptor for 0.0.0.0:5445
at org.hornetq.core.remoting.impl.netty.NettyAcceptor.start(NettyAcceptor.java:344) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.remoting.server.impl.RemotingServiceImpl.start(RemotingServiceImpl.java:240) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1495) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.access$1200(HornetQServerImpl.java:138) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation.run(HornetQServerImpl.java:1919) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:366) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:269) [hornetq-jms-2.2.13.Final.jar:]
at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:73) [jboss-as-messaging-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771) [rt.jar:1.6.0_31]
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38) [rt.jar:1.6.0_31]
at java.security.KeyStore.load(KeyStore.java:1185) [rt.jar:1.6.0_31]
at org.hornetq.core.remoting.impl.ssl.SSLSupport.loadKeystore(SSLSupport.java:147) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.remoting.impl.ssl.SSLSupport.loadKeyManagers(SSLSupport.java:168) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.remoting.impl.ssl.SSLSupport.createServerContext(SSLSupport.java:63) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.remoting.impl.netty.NettyAcceptor.start(NettyAcceptor.java:340) [hornetq-core-2.2.13.Final.jar:]
... 12 more
Caused by: java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769) [rt.jar:1.6.0_31]
It does work for datasources and web connectors on Linux but I get the following exceptions on Windows:
2012-08-30 14:40:18,208 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 57) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "web"),
("connector" => "https")
]): java.lang.SecurityException: JBAS013311: Security Exception
at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:104)
at org.jboss.as.server.RuntimeExpressionResolver.resolvePluggableExpression(RuntimeExpressionResolver.java:45)
at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressionsRecursively(ExpressionResolverImpl.java:58) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressions(ExpressionResolverImpl.java:40) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.ModelControllerImpl.resolveExpressions(ModelControllerImpl.java:448) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.OperationContextImpl.resolveExpressions(OperationContextImpl.java:689) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.ParallelBootOperationContext.resolveExpressions(ParallelBootOperationContext.java:283) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AttributeDefinition.resolveModelAttribute(AttributeDefinition.java:242) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.web.WebConnectorAdd.resolveExpressions(WebConnectorAdd.java:138)
at org.jboss.as.web.WebConnectorAdd.performRuntime(WebConnectorAdd.java:116)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:311) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
Caused by: org.jboss.security.vault.SecurityVaultException: PB00027: Vault Mismatch:Shared Key does not match for vault block:XXX and attributeName:password
at org.picketbox.plugins.vault.PicketBoxSecurityVault.retrieve(PicketBoxSecurityVault.java:364)
at org.jboss.as.security.vault.RuntimeVaultReader.getValue(RuntimeVaultReader.java:124)
at org.jboss.as.security.vault.RuntimeVaultReader.getValueAsString(RuntimeVaultReader.java:112)
at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:102)
... 18 more
Thanks in Advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/757109#757109]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss Web Services Development] - JBossWS - Building From Source
by Alessio Soldano
Alessio Soldano [https://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Building From Source"
To view the document, visit: https://community.jboss.org/docs/DOC-13547
--------------------------------------------------------------
This page documents the *Maven* based build that we use *since jbossws-3.0.2*. See the https://community.jboss.org/docs/DOC-13514 Mavenization page for details regarding configuring you Maven environment. The Ant based build of previous versions, is documented https://community.jboss.org/docs/DOC-13548 here.
**
#Checkout_and_build_JBossAS Checkout and build JBossAS
***
#Run_jboss Run jboss
**
#Checkout_and_build_JBossWSCXF Checkout and build JBossWS-CXF
***
#_Edit_profilesxml_JBossWS_3x_only Edit profiles.xml (JBossWS 3.x only)
***
#BuildDeploy Build/Deploy
***
#Run_the_smoke_tests Run the smoke tests
**
#Checkout_and_build_JBossWSNative Checkout and build JBossWS-Native
***
#Edit_profilesxml_JBossWS_3x_only Edit profiles.xml (JBossWS 3.x only)
***
#BuildDeploy_903558 Build/Deploy
***
#Run_the_smoke_tests_315322 Run the smoke tests
h2. Checkout and build JBossAS
For building *JBoss AS 7* series, have a look at https://community.jboss.org/docs/DOC-15596 https://community.jboss.org/wiki/HackingOnAS7
For *previous JBoss AS versions* instead:
svn co http://anonsvn.jboss.org/repos/jbossas/trunk
cd trunk
build/build.sh
For more information, see http://wiki.jboss.org/wiki/Wiki.jsp?page=SVNRepository SVNRepository
h3. Run jboss
Before you start jboss, you should follow the deploy steps for a supported stack (see below).
Then start the application server using the scripts available for that.
h2. Checkout and build JBossWS-CXF
svn co http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk jbossws-cxf
For more information, see https://community.jboss.org/docs/DOC-13526 Subversion
h3. ** Edit profiles.xml (JBossWS 3.x only)
<profile>
<id>jboss-home-profile</id>
<activation>
<property>
<name>user.name</name>
</property>
</activation>
<properties>
<jboss421.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA</jboss421.home>
<jboss422.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_2_GA/build/output/jboss-4.2.2.GA</jboss422.home>
<jboss423.home>/home/tdiesler/svn/jbossas/branches/Branch_4_2/build/output/jboss-4.2.3.GA</jboss423.home>
<jboss500.home>/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_Beta4/build/output/jboss-5.0.0.Beta4</jboss500.home>
<jboss501.home>/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.CR1</jboss501.home>
</properties>
</profile>
Starting from JBossWS 4, the build is supporting Maven 3, which made the use of profiles.xml deprecated.As a consequence of that, you should actually be providing the jbossXYZ.home property on the command line when invoking mvn.h3. Build/Deploy
To deploy jbossws-cxf 4.x or greater (Maven 3) you run (replace XYZ with the selected JBoss AS version):
cd jbossws-cxf
ant -DjbossXYZ.home=<absolute-path-to-JBoss-AS-XYZ> deploy-jbossXYZ
To deploy jbossws-cxf 3.x (Maven 2) you run (replace XYZ with the selected JBoss AS version):
cd jbossws-cxf
ant deploy-jbossXYZ
Starting from JBossWS-CXF 3.4.0 SpringFramework libraries are not installed by default. If you still want that you need to add the -Dspring=true option:
ant -Dspring=true deploy-jboss500
When jboss starts you should see something like
13:16:25,104 INFO [ServerImpl] Starting JBoss (Microcontainer)...
13:16:25,106 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)
...
13:18:01,278 INFO [CXFServerConfig] JBoss Web Services - Stack CXF Runtime Client
13:18:01,279 INFO [CXFServerConfig] 3.0.2-SNAPSHOT
...
13:18:09,355 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:18:09,389 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)] Started in 1m:44s:270ms
h3. Run the smoke tests
cd jbossws-cxf
mvn -Psmoketest,jboss501 test
Starting from JBossWS 4, the integration testsuites have been moved to 'integration-test' maven phase. So you need to use:
mvn -Psmoketest,jbossXYZ -DjbossXYZ.home=path-to-jbossXYZ integration-test
You should expect to see no test failures. There might be a number of FIXME messages on the console. These are linked to open JIRA issues.
Tests that are known to fail should be excluded in the container specific exclude file. Note, if a test is excluded it is not even compiled and hence will not run in any of the ant test targets.
h2. Checkout and build JBossWS-Native
svn co http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk jbossws-native
For more information, see https://community.jboss.org/docs/DOC-13526 Subversion
h3. Edit profiles.xml (JBossWS 3.x only)
<profile>
<id>jboss-home-profile</id>
<activation>
<property>
<name>user.name</name>
</property>
</activation>
<properties>
<jboss421.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA</jboss421.home>
<jboss422.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_2_GA/build/output/jboss-4.2.2.GA</jboss422.home>
<jboss423.home>/home/tdiesler/svn/jbossas/branches/Branch_4_2/build/output/jboss-4.2.3.GA</jboss423.home>
<jboss500.home>/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_Beta4/build/output/jboss-5.0.0.Beta4</jboss500.home>
<jboss501.home>/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.CR1</jboss501.home>
</properties>
</profile>
Starting from JBossWS 4, the build is supporting Maven 3, which made the use of profiles.xml deprecated.As a consequence of that, you should actually be providing the jbossXYZ.home property on the command line when invoking mvn.
h3. Build/Deploy
To deploy jbossws-native you run:
cd jbossws-native
ant deploy-jboss501
When jboss starts you should see something like
09:32:09,581 INFO [ServerImpl] Starting JBoss (Microcontainer)...
09:32:09,583 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)
...
09:33:24,587 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
09:33:24,588 INFO [NativeServerConfig] 3.0.2-SNAPSHOT
...
09:33:32,318 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:33:32,341 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)] Started in 1m:22s:744ms
h3. Run the smoke tests
cd jbossws-native
mvn -Psmoketest,jboss501 test
You should expect to see no test failures. There might be a number of FIXME messages on the console. These are linked to open JIRA issues.
Starting from JBossWS 4, the integration testsuites have been moved to 'integration-test' maven phase. So you need to use:
mvn -Psmoketest,jboss710 -Djboss710.home=path-to-jboss710 integration-test
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-13547]
Create a new document in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 8 months