May 2008 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: Recommended testing framework

by tharter

Heh, JUnitEE may be 'dead' but it works... I even ginned up an Injector, so in my test cases I can use the @EJB and @Resource Annotation ;) In fact I even made annotations for DBunit and one that automagically auths my tests. Now, if only @Interceptors() only worked (at all) I'd be golden... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150207#4150207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150207

18 years, 1 month

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - JBoss Connection Socket usage in error scenarios

by dkilley

Original Post, wrong area? - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=133873 Essentially to summarize, we've noticed that when a HA connection data source is configured with a new-connection-sql statement, that if the socket connection succeeds, but the new-connection-sql fails, the connection is not closed prior to throwing the ManagedConnect object away. Thus there exists potential for alot of sockets to be opened and not closed until GC, whereby a bit of extra code can close those sockets proactivly. Before submitting as a bug I wanted to just gather any feedback on this. The above URL has a good code clip at the bottom that describes the exact code and what we are seeing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150206#4150206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150206

18 years, 1 month

1
0
0 / 0

[Remoting] - Re: Create Data Source on Remote JBoss instance

by ron.sigal＠jboss.com

The data layer is completely independent of Remoting. Of course, you can certainly use JDBC in you ServerInvocationHandler code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150203#4150203 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150203

18 years, 1 month

1
0
0 / 0

[Remoting] - Re: No jboss-remoting.jar in 2.2.2SP_4 and 2.2.2SP_7

by ron.sigal＠jboss.com

Sorry. I'll try to get to that soon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150202#4150202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150202

18 years, 1 month

1
0
0 / 0

[Remoting] - Re: Memory leak in remoting objects

by ron.sigal＠jboss.com

Every time you create a JBossMessaging connection, you're creating a Remoting bisocket connection, including a new BisocketClientInvoker.$PingTimerTask. When you close the JBM connection, the PingTimerTask should cancel itself. You're sure that you're closing the JBM connection? Now, the Timer that the PingTimerTasks are registered with is a static object, so I guess it's possible that the Timer is holding references to old PingTimerTasks. I don't know how you're profiling your test, but I know that with JProfiler you can see what's pointing to the PingTimerTasks and preventing them from getting garbage collected. Could you look into that? Thanks, Ron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150201#4150201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150201

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - jBPM 3.2.2 on Weblogic 9.2

by greenHand

Please bear with me. I am new to not only jBPM but also J2EE. I have been struggling and working on a proof of concept to use jBPM on Weblogic. I need to find out if I am on the right course. If I use the downloaded jbpm-enterprise.ear and manage to swap out jboss.xml with weblogic specific deployment descriptor (weblogic-ejb-jar.xml), then deploy. Should that work? Anything else I need do besides configuring hibernate? I like to have a message driven bean be called from a stand alone java program. Then the MDB will start the workflow process. Is it a correct way to have the MDB to load process definition and signal the token to start the process just like many sample unit tests have demonstrated? I guess my question is instead of using the web console interface, what's the right way to programmatically start and transition the process. Thank in advance for your help! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150200#4150200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150200

18 years, 1 month

1
0
0 / 0

[Remoting] - Re: Compression marshalling

by ron.sigal＠jboss.com

Hi Ganesh, Application Server 3.2.5 doesn't use JBossRemoting, and I don't know if there's even a compression marshaller available for that version. When you're ready to upgrade to AS 4.2, let me know and I'll help you with the Remoting compression marshaller. -Ron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150198#4150198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150198

18 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: JMS client in a applet

by clebert.suconic＠jboss.com

"timfox" wrote : Not sure why you would need to patch JBM. | | AFAIK this is a JBoss Remoting issue. | | You should post this in the JBR forum so they are aware of this. Maybe Laurent is using an older TAG, since this seems fixed on Branch_CP. org.jboss.messaging.util.JBMExecutor is already setting the classLoader using a Privileged block. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150195#4150195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150195

18 years, 1 month

1
0
0 / 0

[JBossWS] - WSDL is correctly modified to use the configured https port

by rnagy

Hi, JBoss issue: When an ear file is deployed and used with the https protocol, the WSDL is not correctly modified to use the configured port numbers. Baseline setup: - JBOSS version JBOSS-4.2.2.GA - Linux 2.6.9-55.0 ELsmp - EchoService is packaged as .ear and contains JMX MBean to manage configuration - The .ear contains EchoService wsdl - The endpoint url in the wsdl is expected to be dynamically rebuilt during deployment. HTTP deployment (works as expected) Test Procedure: - Install a clean instance of JBoss - Start JBoss "out of the box" - Deploy the ear file (echows.ear) (drop the file to the directory $JBOSS_HOME/server/default/deploy/) - Verify the echo web service (EchoService) is deployed using the JMX Management Console (http://localhost:8080/jmx-console/) - Use http://localhost:8080/jbossws/services to identify the Registered Service Endpoint Address - Result: http://localhost.localdomain:8080/services/echows/EchoServiceEndpoint?wsdl - Follow link to wsdl. Result: | - <definitions targetNamespace="http://www.accenture.com/afmstt/echows"> | - <types> | - <xs:schema elementFormDefault="qualified" targetNamespace="http://www.accenture.com/afmstt/echows" version="1.0"> | <xs:include schemaLocation="http://localhost.localdomain:8080/services/echows/EchoServiceEndpoint?wsd..."/> | </xs:schema> | </types> | - <message name="echoResponse"> | <part element="ech:echoResponse" name="response"/> | </message> | - <message name="echoRequest"> | <part element="ech:echoRequest" name="request"/> | - </message> | - <portType name="EchoPort"> | - <operation name="echo"> | <input message="ech:echoRequest"/> | <output message="ech:echoResponse"/> | </operation> | </portType> | - <binding name="EchoHttpBinding" type="ech:EchoPort"> | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> | - <operation name="echo"> | <soap:operation soapAction=""/> | - <input> | <soap:body use="literal"/> | </input> | - <output> | <soap:body use="literal"/> | </output> | </operation> | </binding> | - <service name="EchoWebService"> | - <port binding="ech:EchoHttpBinding" name="EchoPort"> | <soap:address location="http://localhost.localdomain:8080/services/echows/EchoServiceEndpoint"/> | </port> | </service> | </definitions> | HTTPS deployment (does not work) - Install a clean instance of JBoss - Reconfigure JBoss to use SSL and port 8443 - Copy keystore to $JBOSS_HOME/server/default/conf - Edit $JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml to enable SSL connector on port 8443 and define keystore file path and password - Comment out the default 8080 connector |  | |  | | <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" | maxThreads="150" scheme="https" secure="true" | clientAuth="false" sslProtocol="TLS" keystoreFile="${jboss.server.home.dir}/conf/test.jks" | keystorePass="echotest" | /> | - Start JBoss - Deploy the ear file (echows.ear) (drop the file to the directory $JBOSS_HOME/server/default/deploy/) - Verify the echo web service (EchoService) is deployed using the JMX Management Console (https://localhost:8443/jmx-console/) - Use https://localhost:8443/jbossws/services to identify the Registered Service Endpoint Address - Result: http://localhost.localdomain:8080/services/echows/EchoServiceEndpoint?wsdl wrong - should be https://localhost.localdomain::8443/services/echows/EchoServiceEndpoint?wsdl - Modify the link to the correct one: https://localhost.localdomain:8443/services/echows/EchoServiceEndpoint?wsdl to expected endpoint wsdl. - Result: - <definitions targetNamespace="http://www.accenture.com/afmstt/echows"> | - <types> | - <xs:schema elementFormDefault="qualified" targetNamespace="http://www.accenture.com/afmstt/echows" version="1.0"> | <xs:include schemaLocation="https://localhost.localdomain:8443/services/echows/EchoServiceEndpoint?ws..."/> | </xs:schema> | </types> | - <message name="echoResponse"> | <part element="ech:echoResponse" name="response"/> | </message> | - <message name="echoRequest"> | <part element="ech:echoRequest" name="request"/> | </message> | - <portType name="EchoPort"> | - <operation name="echo"> | <input message="ech:echoRequest"/> | <output message="ech:echoResponse"/> | </operation> | </portType> | - <binding name="EchoHttpBinding" type="ech:EchoPort"> | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> | - <operation name="echo"> | <soap:operation soapAction=""/> | - <input> | <soap:body use="literal"/> | </input> | - <output> | <soap:body use="literal"/> | </output> | </operation> | </binding> | - <service name="EchoWebService"> | - <port binding="ech:EchoHttpBinding" name="EchoPort"> | <soap:address location="http://localhost.localdomain:8080/services/echows/EchoServiceEndpoint"/> | </port> | </service> | </definitions> | Note that the <xs:include schemaLocation="https://localhost.localdomain:8443/services/echows/EchoServiceEndpoint?ws..."/> contains the updated https and 8443 (as expected). Note that the <soap:address location ... >> contains http and 8080. Again, it had been expected that the soap address location would have been updated to https and port 8443 as was correctly done for SchemaLocation. We are asking for either an explanation of what we did incorrectly or for an indication of when this issue can be expected to be fixed. If desired, we will open a Jira item if we are led to believe this is a suspected bug. Regard, --Rich. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150192#4150192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150192

18 years, 1 month

1
0
0 / 0

[JBossWS] - Trying to deploy ADF Oracle componet in a jsf page getting j

by VijaySri

javax.servlet.ServletException: javax.faces.application.ViewHandler.initView(Ljavax/faces/context/FacesContext;)V javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196) oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause I copied all my jars in server/default/lib. I removed all the JSF jars which comes with the jboss developer studio server\default\deploy\jboss-web.deployer\jsf-libs Server is running fine but when i hit the page with the url : http://localhost:8080/test/faces/Jsp/testLogin.jspx i get exception like javax.servlet.ServletException: javax.faces.application.ViewHandler.initView(Ljavax/faces/context/FacesContext;)V javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336) oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196) oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause Please guide me this regard. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150191#4150191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150191

18 years, 1 month

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 May 2008