[EJB/JBoss] - ssl connection to ejb in cluster using @RemoteBinding
by smolin
Hello there,
could anybody help or point the right direction?
Conf:
JBoss 5.1.0CR1, JDK 1.6, XP (development env)
cluster (configuration: all)
I try to use ssl connection to reach ejb component.
1. added ssl-service.xml to META-INF of ejb jar
| <?xml version="1.0" encoding="UTF-8"?>
|
| <server>
| <!-- The server socket factory mbean to be used as attribute to socket invoker -->
| <!-- which uses the JaasSecurityDomain -->
| <mbean code="org.jboss.remoting.security.domain.DomainServerSocketFactoryService"
| name="jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced"
| display-name="SecurityDomain Server Socket Factory">
| <attribute name="SecurityDomain">java:/jaas/SSLAdvanced</attribute>
| <depends>jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced</depends>
| </mbean>
|
| <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
| name="jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced">
| <!-- This must correlate with the java:/jaas/SSL above -->
| <constructor>
| <arg type="java.lang.String" value="SSLAdvanced"/>
| </constructor>
| <!-- The location of the keystore
| resource: loads from the classloaders conf/ is the first classloader -->
| <attribute name="KeyStoreURL">traffic.keystore</attribute>
| <attribute name="KeyStorePass">trafficssl</attribute>
| </mbean>
|
| <!-- The Connector is the core component of the remoting server service. -->
| <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
| <!-- data marshalling, etc.) with the invocation handlers. -->
| <mbean code="org.jboss.remoting.transport.Connector"
|
| name="jboss.remoting:type=Connector,transport=socket3843,handler=ejb3">
| display-name="Socket transport Connector">
|
| <attribute name="Configuration">
| <config>
| <invoker transport="sslsocket">
| <attribute name="dataType" isParam="true">invocation</attribute>
| <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute>
| <!-- The following is for setting the server socket factory. If want ssl support -->
| <!-- use a server socket factory that supports ssl. The only requirement is that -->
| <!-- the server socket factory value must be an ObjectName, meaning the -->
| <!-- server socket factory implementation must be a MBean and also -->
| <!-- MUST implement the org.jboss.remoting.security.ServerSocketFactoryMBean interface. -->
| <attribute name="serverSocketFactory">jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">3843</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| <depends>jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced</depends>
|
| </mbean>
|
| </server>
|
2. generated all keystore/certificate etc.
3. added annotation to ejb (many different trials):
@RemoteBinding(jndiBinding="someEjb/remote", clientBindUrl = "sslsocket://${jboss.bind.address}:3843")
then
@RemoteBinding(jndiBinding="someEjb/remote", clientBindUrl = "sslsocket://0.0.0.0:3843")
If I put real target ip of ejb container then it works fine, but only with one machines from cluster (obvious, you can't put two ip addresses in clientBindUrl), whenever I try to use 0.0.0.0 mask or ${jboss.bind.address} it doesn't work.
I couldn't find any working solution and of course many examples that use 0.0.0.0 mask works fine (but only for local communication: client and server on the same machine). Could not find any working solution for ssl in cluster setup.
Any help would be really appreciated!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233342#4233342
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233342
16 years, 11 months
[Installation, Configuration & DEPLOYMENT] - Re: pelirr31
by pelirr
Hello, it contain WEB-INF/web.xml, here is it:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
|
| <jsp-config>
| <taglib>
| <taglib-uri>strutsBean</taglib-uri>
| <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>strutsHtml</taglib-uri>
| <taglib-location>/WEB-INF/lib/struts-html.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>strutsLogic</taglib-uri>
| <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>strutsForm</taglib-uri>
| <taglib-location>/WEB-INF/lib/struts-form.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>strutsTemplate</taglib-uri>
| <taglib-location>/WEB-INF/lib/struts-template.tld</taglib-location>
| </taglib>
| </jsp-config>
|
| <display-name>PruebaOsiris.war</display-name>
|
| <servlet>
| <servlet-name>action</servlet-name>
| <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
| <!-- com.empresa.aplicacion.ApplicationResources es la localizacion del archivo ".properties"
| del idioma principal de la aplicacion -->
| <init-param>
| <param-name>application</param-name>
| <param-value>org.apache.struts.example.ApplicationResources</param-value>
| <!-- en el manual después viene que en lugar de este value puede ser
| com.empresa.aplication.ApplicationResources -->
| </init-param>
| <init-param>
| <param-name>config</param-name>
| <param-value>/WEB-INF/struts-config.xml</param-value>
| </init-param>
| <!-- Para el nivel de depuración -->
| <init-param>
| <param-name>debug</param-name>
| <param-value>2</param-value>
| </init-param>
| <!-- Clase java de implementación del mapping -->
| <init-param>
| <param-name>mapping</param-name>
| <param-value>org.apache.struts.example.ApplicationMapping</param-value>
| </init-param>
| <init-param>
| <param-name>detail</param-name>
| <param-value>2</param-value>
| </init-param>
| <init-param>
| <param-name>validate</param-name>
| <param-value>true</param-value>
| </init-param>
| <!-- Orden de ejecución cuando el servlet engine es inicializado -->
| <load-on-startup>2</load-on-startup>
| </servlet>
| <servlet-mapping>
| <servlet-name>action</servlet-name>
| <url-pattern>*.do</url-pattern>
| </servlet-mapping>
|
| <welcome-file-list>
| <welcome-file>registro.jsp</welcome-file>
| </welcome-file-list>
| </web-app>
|
Thanks very much, and regards
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233340#4233340
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233340
16 years, 11 months
[EJB 3.0] - EJB 3 1.1.5 bundle released with JBoss AS 5.1.0.GA
by wolfc
Already old, because a plugin release has already gone passed. :-)
But here is AS 5.1.0.GA with a new and better EJB 3 implementation:
"Rajesh Rajasek" wrote : JBoss AS 5.1.0.GA is released and is available for download.
| http://www.jboss.org/jbossas/downloads/
|
| Along with many bug fixes and enhancements, this is the first general release to include our new, significantly improved open-source console.
| Highlights
| * New Web Console - This release includes our new administration console. Several updates have been made since the CR1 release, including the introduction of WAR metrics.
| * Web Beans Update - In addition, this release includes an updated tech preview of the new JSR-299 Web Beans RI.
| * Farming Returns - Due to popular demand, the farming service is back!
|
| For detailed release notes, visit here:
| http://www.jboss.org/jbossas/docs/Release_Notes/510GA/readme.html
|
| Happy Memorial Day to all folks in the US!
|
| Thanks
| Rajesh
These are the changes since AS 5.0.1.GA:
Release Notes for EJB 3.0
Includes versions: 1.1.0 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5
** Sub-task
* [ EJBTHREE-1718 ] Deprecate usage of org.jboss.ejb3.embedded.deployers.JBossEjbParsingDeployer
* [ EJBTHREE-1722 ] Clear out existing ejb3-async Implementation
* [ EJBTHREE-1729 ] Make jboss-ejb3-async-spi
* [ EJBTHREE-1740 ] Upport JBPAPP-856: Support DeliveryActive MDB activation config property on deployment
* [ EJBTHREE-1753 ] persistenceunits MultipleEarTestCase.testServerFound fails due to changed error message
* [ EJBTHREE-1767 ] Change ejb3-proxy to ejb3-proxy-impl
* [ EJBTHREE-1771 ] Create a proxy transition component
* [ EJBTHREE-1801 ] Performance : Improve the logic in the InterceptorRegistry and InjectInterceptorsFactory
** Feature Request
* [ EJBTHREE-987 ] support DeliveryActive MDB activation config property
* [ EJBTHREE-1624 ] Provide @EJB injection into MC Beans
* [ EJBTHREE-1708 ] Allow the installer to install packages and remain in the temp dir
* [ EJBTHREE-1768 ] Create a Utility to alter Manifest Class-Path in jbossall-client
* [ EJBTHREE-1815 ] Unwarranted deployment errors must specify the offending bean
** Bug
* [ EJBTHREE-1135 ] Interceptor's tutorial page contains outdated XML
* [ EJBTHREE-1346 ] Disabling @Clustered via jboss.xml not being respected
* [ EJBTHREE-1358 ] StrictMaxPool for SFSB does not decrease Pool-Usage on bean-removal
* [ EJBTHREE-1597 ] Missing default persistence properties
* [ EJBTHREE-1629 ] Ejb3DescriptorHandler does not handle complete set of primitives
* [ EJBTHREE-1677 ] Incorrect handling of overloaded methods in ServiceMBeanDelegate
* [ EJBTHREE-1690 ] jboss-ejb3-core has has a transitive dependency on jboss-servlet-api
* [ EJBTHREE-1692 ] Slow memory leak in StatefulTreeCache if removal timeout is not configured.
* [ EJBTHREE-1694 ] FieldBeanProperty.set has potential NPE, not considering Bootstrap CL
* [ EJBTHREE-1700 ] EJB3 installer deletes JBOSS_HOME/client/ejb3-persistence.jar and does not copy it back during patching
* [ EJBTHREE-1745 ] java:comp/env isn't available for SessionSynchronization callbacks
* [ EJBTHREE-1746 ] EJB3 tutorials not working against JBossAS-5.0.1 GA
* [ EJBTHREE-1757 ] Chapter 36 of the tutorial guide is missing the chapter name
* [ EJBTHREE-1778 ] Proxy Factories are not bound in MC under unique names across EARs
* [ EJBTHREE-1793 ] EJb2.x bean in reference21_30 testcase of the testsuite does not strictly follow the spec
* [ EJBTHREE-1795 ] Fix the ChangeXMLUnitTestCase to be more robust
* [ EJBTHREE-1798 ] JNDIKernelRegistryPlugin should not create proxies or sessions during MC context state change
* [ EJBTHREE-1802 ] AbstractEjbReferenceValueMetadata doesn't handle UnresolvableReferenceException while resolving EJB reference
* [ EJBTHREE-1803 ] Installer does not copy core-client to client folder of AS
* [ EJBTHREE-1807 ] StatefulTreeCache removal task can't handle already removed beans
* [ EJBTHREE-1808 ] Fix the pointcut expressions, to introduce annotations on joinpoints, in ejb3-interceptors-aop.xml
* [ EJBTHREE-1825 ] Fix the typo in jboss-ejb3-endpoint-deployer.xml which is used in the plugin for installing the ejb3-endpoint-deployer
** Task
* [ EJBTHREE-1241 ] Address EJB3 TestSuite Regressions
* [ EJBTHREE-1396 ] MockServer must report startup / shutdown
* [ EJBTHREE-1401 ] Create Tests for @Remote pass-by-value within local JVM
* [ EJBTHREE-1693 ] Don't duplicate DeploymentUnit.getTopLevel
* [ EJBTHREE-1695 ] Remove ejb3-core dependency upon ejb3-async
* [ EJBTHREE-1697 ] Move the current ejb3 timer service to a separate optional component
* [ EJBTHREE-1709 ] Check for applicable interceptors is missing (Was: Unnecessary logging at WARN level)
* [ EJBTHREE-1715 ] Define centralized location for versioning of dependency chain
* [ EJBTHREE-1725 ] Create an unit test for ApplicationException inheritance
* [ EJBTHREE-1726 ] ChainedProcessingInvocationHandler duplicates AOP
* [ EJBTHREE-1747 ] Make the individual tutorials runnable through Maven
* [ EJBTHREE-1748 ] Make the EJB3 tutorials Maven releasable
* [ EJBTHREE-1754 ] Fix the "factory" tests in testsuite
* [ EJBTHREE-1758 ] SessionSpecContainer expects a j.l.r.Proxy in invoke method
* [ EJBTHREE-1760 ] Extract a slim remote server into its own test component
* [ EJBTHREE-1761 ] Give ProxyObjectFactory a serialVersionUID
* [ EJBTHREE-1762 ] Remove vestigial code from Invocation Handlers
* [ EJBTHREE-1763 ] Rename and reset hierarchy of StatefulSessionInvokableContext
* [ EJBTHREE-1764 ] Change API of InvokableContext.invoke()
* [ EJBTHREE-1765 ] Unify InvocationHandlers into one implementation
* [ EJBTHREE-1766 ] Break out contracts from ejb3-proxy into ejb3-proxy-spi
* [ EJBTHREE-1769 ] Remove installation of TimerService from Plugin
* [ EJBTHREE-1772 ] Create an endpoint SPI
* [ EJBTHREE-1773 ] Allow SFSB proxies to request non-business-method removal
* [ EJBTHREE-1774 ] Remove StatefulSessionProxy
* [ EJBTHREE-1775 ] Refactor MockServer to be more extensible/generic
* [ EJBTHREE-1777 ] Proxies may not support operations outside of Object.class and business interface methods
* [ EJBTHREE-1780 ] Provide an injectable indirection to the EJB Container for WebBeans
* [ EJBTHREE-1786 ] Create endpoint deployers
* [ EJBTHREE-1788 ] Update the MDB tutorial guide to make a reference to the jboss specific DeliveryActive ActivationConfigProperty
* [ EJBTHREE-1809 ] Remove jboss-ejb3-proxy from as-int
* [ EJBTHREE-1810 ] Plugin needs to add ejb3-endpoint to the AS during the patch process
* [ EJBTHREE-1820 ] Release embedded 1.0.0-Alpha-2
* [ EJBTHREE-1821 ] Release endpoint-deployers 0.1.0
* [ EJBTHREE-1826 ] Configure the tutorials to pass the JBossXB -Dxb.builder.useUnorderedSequence=true property during AS startup
** Thirdparty Change
* [ EJBTHREE-1707 ] Upgrade to apiviz 1.2.5.GA
* [ EJBTHREE-1796 ] Upgrade to 1.0.0-CR1 jboss-jpa-deployers
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233318#4233318
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233318
16 years, 11 months
[JBoss Messaging] - Behavior with selector and fullSize cache
by mclu
Hi!
I am using one of the latest versions of the 1_4 branch
We are using one queue where multiple bridges/clients consume/transport messages using a selector.
Try to visualize it: :-)
Queue A
Bridge X fetch messages with selector destnode=X
Bridge Y fetch messages with selector destnode=Y
Bridge Z fetch messages with selector destnode=Z
The business logic always create one message per destinationnode with the header property destnode set to X,Y or Z
The messages in the queue are added in a sequence like:
a(x),a(y),a(z), b(x),b(y),b(z),....
Our messages are really big. from 20k to 20 megabyte so we want to limit the fullSize from default 200000 to 100 or similar.
What happens now if destination X is not reachable for a longer time. What implications does this fullSize setting have then.
This means that all message with destination (x) can not be delivered for that offline time. The messages in the queue then should look like this
a(X),b(x),c(x),....t(x),t(y),t(z)
Lets say we set it to 100 and there are 120 (x) messages in the queue.
If we now add 3 new messages for x,y and z, does this now mean that the y and z message is not cached in the memoryqueue. Are those messages then delivered? And if so is each message then fetched from the database?
to summarize:
What happens is I use a selector and set the fulSize setting to a very low value.
THX for a short explanation!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233312#4233312
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233312
16 years, 11 months