[Remoting] - Re: https with path and ejb3 can not be configured
by rino_salvade
Hi Ron
Thank you for your response
anonymous wrote : 1. The problem in JBWS-1141 comes from the fact that Remoting versions 2.x require a call to org.jboss.remoting.Client.connect() before any calls to Client.invoke(), whereas earlier versions of Remoting didn't impose that requirement. The current version of EJB3 is compatible with Remoting 2.x. Perhaps you can upgrade to JBossAS 4.2, where this problem is solved.
This problem is solved. As I mentioned, I adapted the Remoting 2.x version so that it is backwards compatible with the 1.4.3 version. Unfortunately we're not currently upgrade our productive system to 4.2
anonymous wrote :
| 2. Are you familiar with the "path" configuration attribute, which adds a path the the InvokerLocator:
I did find this parameter for the servlet approach, but I didn't know (and found nothing in the documentation) that it works as well for http
anonymous wrote : 3. How are you passing in the org.jboss.remoting.serverAuthMode parameter? You want it to be available to the client when it is creating its socket factory. You could do that by passing it in the configuration map to the client, e.g., new Client(locator, configuration). If you put it in an XML server configuration file, be sure to use the "isParam" attribute.
What I tried was like this
<mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="Configuration">
| <config>
| <invoker transport="sslservlet">
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">8443</attribute>
| <attribute name="path">/invoker/EJBInvokerServlet</attribute>
| <attribute name="org.jboss.remoting.serverAuthMode" isParam="true">false</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
But as I wrote, I got the impression that the parameter is not used correctly
anonymous wrote :
| What does your URL look like?
The url looked like this
<attribute name="InvokerLocator">servlet://${jboss.bind.address}:8443/invoker/EJBInvokerServlet?serverAuthMode=false</attribute>
|
So, all the above mentioned problems are solved so far. It works fine with the sslservlet.
The problem which I have currently is to make it accessible through a remote proxy (Web Entry Server) that requires client authentication. Geting the JNDIFactory and the JMXInvokerServlet works fine, but calling the EJB causes a problem. This is based on the fact that the calling opens up a new http session which is of course not yet authenticated. So when the http POST for the invocation is sent, the remote proxy answers with a redirect to get the client certificate. Unfortunately the redirect results that the http POST is transformed into a http GET (this is according to the http standards). The server side of the EJBInvokerServlet then can not handle the GET properly and goes into a npe.
So any help on this would be appreciated. I was looking if it is possible to configure the request right from the beginning as a GET but wasn't lucky so far.
Regards Rino
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043739#4043739
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043739
19 years
[JBoss Seam] - Seam apps leaking memory?!
by stephen.friedrich
My (not so large) app can be redeployed on JBoss 4.0.5 exactly two times before the deployment is failing.
I know that the issue of OOME in PermGenSpace has been discussed before and the default answers were either "Sun JVM bug", "use jrockit" (which only increases the available redeploys a little without really solving the problem) or "increase perm space" (dito, I manage up to four redeploys).
I don't really buy any of thse answers because other apps do not have such severe problems.
Here's a nice summary:
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?p...
Using Yourkit I tried to investigate the problem:
| * Started JBoss.
| * Deployed the booking app.
| * Undeployed the booking app.
| * Looked at instances of org.jboss.seam.* classes.
|
I have found these two problems:
| * java.beans.Introspector leaks if flushCaches() isn't called. For testing I added such a call in org.jboss.seam.servlet.SeamListener.contextDestroyed()
| * The cache used in javassist's ProxyFactory is never cleared. I updated javassist to version 3.4 and added "ProxyFactory.useCache = false;" to org.jboss.seam.servlet.SeamListener.contextInitialized()
| I doubt that this is the correct way, but it brought down the instance count and did not seem to break anything. (javassist's ProxyFactory is used from org.jboss.seam.Component.createProxyFactory().)
|
These changes reduced the instance count but there are still some objects that refuse to get collected. I am stuck: All references to remaining objects come from the UnifiedClassLoader3.
Looks like "org.jboss.util.timeout.TimeoutFactory$1" is still holding a strong reference to the class loader.
This is well out of my expertise. I'd really appreciate if somebody could look into that.[/url]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043738#4043738
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043738
19 years
[JBoss Seam] - Outjection and component instantiation question
by zzzz8
I think I may have a misconception of some of the intricacies of outjection and Seam component instantiation. I have a Seam component that is created by Seam via the @In(create=true) annotation. Unfortunately, I cannot seem to inject another Seam component into this component. Here's what I'm doing:
Seam component 1
| @Name("comp1")
| @Stateful
| public class MySample1Bean implements MySample1 {
| ...
|
| @Out
| Connection connection = null;
| ...
| public void myMethod() {
| ...
| connection = ...;
| ...
| }
| }
Seam component 2
| @Name("comp2")
| @Stateful
| public class MySample2Bean implements MySample2 {
| ...
|
| @In(create=true) // I've also tried @In(create=true, required=false)
| MySample3 comp3 = null;
|
| @In
| Connection connection = null;
| ...
|
| }
Seam component 3
| @Name("comp3")
| @Stateful
| public class MySample3Bean implements MySample3 {
| ...
|
| @In // I've put @In(required=false) here, too just so component gets created
| Connection connection = null;
|
| ...
|
| }
I have a page where comp1 is called. The user then invokes an action method which then navigates the user to another page, where comp2 is accessed. BTW, I have it on my pages.xml file that a long running conversation gets started (i.e. using <begin-conversation> when the page is invoked) for the page that calls comp2. The Seam component comp3 gets created in comp2 because of the @In(create=true) annotation. However, when comp3 is created, I'm expecting the connection context variable to be outjected to comp3. Unfortunately, connection is always null in comp3. Interestingly, connection is non-null in comp2. What's going on here and what am I doing wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043731#4043731
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043731
19 years
[JBoss Portal] - JBoss WSRP consumer and file uploads
by superfilin
Hello, JBoss Community!
We are developing a portlet on BEA WebLogic Portal that is supposed to be consumed later by JBoss Portal. This portlet is used for file data upload. The thing is that portlet contains a form that has enctype attribute set to multipart/form-data to enable file sending. When the form is submitted on the consumer (JBoss) no form parameters are passed to producer. Looking in the WSRP request sent to BEA Portal by JBoss only action name is seen. If enctype attribute is removed from the form then when form is submitted all parameters are sent to producer except file content.
Is it JBoss WSRP implementation bug? Or is it possble to add some configuration settings on consumer part?
Thanks in advance!
Best regards,
Andrey
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043730#4043730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043730
19 years