[JBossWS] - Re: http://org.jboss.ws/http#chunksize
by centecbertl
"Ratoo" wrote :
| "heiko.braun(a)jboss.com" wrote :
| | HTTP 1.0 Client Did you try that one?
| |
|
| Where is it? How can I configure it?
|
You can use the tomcat Connector configuration to achieve this. Example given for jboss 4.0.5 restricts .net 2.0 clients to use HTTP 1.0:
| $ diff -U 5 server.xml~ server.xml
| --- server.xml~ 2006-12-06 16:03:28.403259700 +0100
| +++ server.xml 2006-12-16 10:18:38.265625000 +0100
| @@ -11,16 +11,18 @@
| <!-- A HTTP/1.1 Connector on port 8080 -->
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
| emptySessionPath="true"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| - connectionTimeout="20000" disableUploadTimeout="true"/>
| + connectionTimeout="20000" disableUploadTimeout="true"
| + restrictedUserAgents="^.*MS Web Services Client Protocol.*$"/>
|
| <!-- Add this option to the connector to avoid problems with
| .NET clients that don't implement HTTP/1.1 correctly
| restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
| -->
| +
|
| <!-- A AJP 1.3 Connector on port 8009 -->
| <Connector port="8009" address="${jboss.bind.address}"
| emptySessionPath="true" enableLookups="false" redirectPort="8443"
| protocol="AJP/1.3"/>
| @@ -29,11 +31,12 @@
| <Connector port="8443" address="${jboss.bind.address}"
| maxThreads="100" strategy="ms" maxHttpHeaderSize="8192"
| emptySessionPath="true"
| scheme="https" secure="true" clientAuth="false"
| keystoreFile="${jboss.server.home.dir}/conf/centec.keystore"
| - keystorePass="centec" sslProtocol = "TLS" />
| + keystorePass="centec" sslProtocol = "TLS"
| + restrictedUserAgents="^.*MS Web Services Client Protocol.*$"/>
| <!-- -->
|
| <Engine name="jboss.web" defaultHost="localhost">
|
| <!-- The JAAS based authentication and authorization realm implementation
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126500#4126500
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126500
18 years, 2 months
[JBoss Seam] - Seam 2.0.1GA : EJB Blockers with Weblogic 9.x/10.x
by joerg.schneider
Hi,
first of all congratulations for the Seam 2.0.1GA release and thanks for the updated documentation, especially how to run Seam in appservers other than JBoss.
As I read from the docs the varargs issue with Bea Weblogic still persists. As far as I understood, BEA claims this issue to be an ambiguity within the Java specs, since the same flag is used to mark fields transient as it is used to mark methods have variable arguments. I furthermore understood, that this issue is not necessarily related to EJB's only, but actually apply to any java code. The fact that the issue shows up with EJB's only is due to jrockits re-compiles the EJB's during deployment.
As per my understanding, a compiler/interpreter should be in a position to handle the transient/vararg flag different for fields and methods (as Sun's implementation apparently does) so I actually see it BEA's responsibility to fix that issue.
Anyhow, according to my experience I'd not expect such a fix is being delivered by BEA within the next 12 months, if at all. Since the next 1 or 2 years certainly will be very important for the roll-out and further distribution of Seam, would it make sense to fix that (rather "work around") within Seam in the meantime ? As far as I understood, the proposed work around is to use arrays instead of varargs in methods/constructors to avoid the issue. This seem to be an acceptable work around for me to overcome the issue for any of my projects/developments. The only problem remaining is : how many Seam internal EJB's are using varargs currently and if it makes sense to use arrays instead of varargs to have some kind of Weblogic/JRockit compatibility ?
I mean I fully understand that using varargs is the proper implementation, but I'd consider using arrays as a valid work around and if it's only the "TimerService" ejb that currently causes the problem in JRockit/Weblogic, why not take a step back (=use arrays) and therefore have another major player (Weblogic) on board. I made much bigger comprises during my IT career so far :-)
If a fix for jrockit is provided that can naturally been reversed.
Any thoughts ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126499#4126499
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126499
18 years, 2 months
[JBoss jBPM] - Seam managed bean property not set by seam.properties
by boocjelle
I hardly believe that the mechanism of the seam.properties does not work. So I made a project using Seam-Gen that can easily be reproduced. I would be grateful to know where I am going wrong.
The project was created using Seam-Gen with the project.type=ear (please note the build.properties below).
The application can be run using the url ..
http://localhost:8080/SeamPropertiesIssue/issue.seam
It shows that the seam.properties name-value-pair <issuebean.value=Value has been set> has no effect. The output is: "Value has not been set".
The sources are ..
1. src/action/de/issue/action/IssueBean.java
2. view/issue.xhtml
3. resources/seam.properties
Seam-gen build.properties:
#Generated by seam setup
#Mon Jan 07 09:25:19 CET 2008
hibernate.connection.password=
workspace.home=C\:/java/jboss-seam-2.0.0.GA/development/
model.package=de.issue.model
driver.jar=C\:/java/jboss-seam-2.0.0.GA/seam-gen/lib/hsqldb.jar
action.package=de.issue.action
test.package=de.issue.test
database.type=hsql
richfaces.skin=DEFAULT
hibernate.default_catalog.null=
hibernate.default_schema=PROTO
database.drop=y
project.name=SeamPropertiesIssue
hibernate.connection.username=sa
hibernate.connection.driver_class=org.hsqldb.jdbcDriver
hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider
project.type=ear
icefaces.home=
database.exists=n
jboss.home=C\:/java/jboss-4.2.2.GA
hibernate.dialect=org.hibernate.dialect.HSQLDialect
hibernate.connection.url=jdbc\:hsqldb\:.
Seam Managed Bean:
package de.issue.action;
import org.jboss.seam.annotations.Logger;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.log.Log;
@Name("issuebean")
public class IssueBean {
@Logger
Log log;
String value="Value has not been set";
public String getValue() {
return value;
}
public void setValue(String value) {
this.value = value;
}
public String checkValue() {
log.info("the issue has the value #0", getValue());
return "";
}
}
View:
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
Issue Concerning seam.properties
<h:form>
<h1>Push the button and check if the properties will set the set the seam managed valuebean</h1>
<h:outputText value="#{issuebean.value}"></h:outputText>
<h:commandButton type="submit" value="Push" action="#{issuebean.checkValue()}">
</h:commandButton>
</h:form>
seam.properties:
issuebean.value=Value has been set
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126496#4126496
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126496
18 years, 2 months
[JBoss Seam] - Re: WARN TwoPhaseCoordinator.afterCompletion
by nhpvti
"nwray" wrote : Hi, I'm seeing the same issue with the recurring WARN message. I get the following warning from TwoPhaseCoordinator.afterCompletion with each iteration of an async task. Nothing obvious is failing, the warning might be in error or could be due to some misconfiguration on my part. It's been annoying during development but it would be nice to resolve it before deployment.
|
| 10:45:24,468 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCo
| mpletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@c03bcd
|
| I've added a comment to the open JIRA below with more details, please let me know if I can add anything else.
| http://jira.jboss.com/jira/browse/EJBTHREE-898
|
I'm getting the same warning after each run of a scheduled job, although the job succeeds.
By the way, I've set EJBTimerService datasource in $JBOSS_HOME/server/default/deploy/ejb-deployer.xml to the same as my application is using in order to have better control over my batch jobs and to avoid multiple non-XA datasources, but the warning is still generated.
My environment:
JBoss 4.2.2.GA
Seam 2.0.0.GA
JDK 1.5.0_14
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126491#4126491
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126491
18 years, 2 months