July 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss/Tomcat Integration] - Re: Missing Servlet Parameters - JBoss 4.0.3

by rheim

Sorry, Posted this to the wrong forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957204#3957204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957204

19 years, 3 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Missing Servlet Parameters - JBoss 4.0.3

by rheim

Has anyone seen a problem similar to the following: We use OpenSTA to generate varying degrees of load to test our application j2ee app using JBoss/Hibernate vs MSSQL. At low levels (75 users generating approx 5000 requests/minute) the tests complete without issue. However, when we try and ramp up the test to more modest levels (150 users generating approx 10,000 requests/minute) our application fails on random Servlet requests where the parameters are null. Checking our test we noted that OpenSTA sent the request with the correct parameters. Also, using a packet sniffer on the webserver machine, we verified that the webserver received all the packets containing these parameters, however the application log we have shows the parameters weren't submitted. I'm guessing this is a load related item but being a JBoss novice I'm not sure where to really look. We thought the problem might be related to the configuration of the HTTP connector and have played around with the acceptCount (varied from 100 to 500) and bufferSize (from default 2048 to 102400) parameters, but these don't seem to make much of a difference to the issue. Also, we tried setting the maxKeepAliveRequests to -1 in the thought this was the issue, but alas to no avail. The machine we are running is averaging 65% CPU utilization and we have plenty of memory available (avg 500 MB free) during the test run. Also, using the same hardware we are able to test the previous version of our product using BEA Weblogic Server 7.0 (SP5) up to around 250 of these virtual users. I'd be more than happy to deliver greater detail about specific configuration settings, just let me know. Thanks in advance for you help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957202#3957202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957202

19 years, 3 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: EAR Metadata

by scott.stark＠jboss.org

We already have the jboss5 metadata repository which is an extension of the aop metdata notions: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73653 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957189#3957189 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957189

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: webservices and jbpm

by alex.guizar＠jboss.com

The XML Schema allows for deriving types from other types. Java-XML binding frameworks such as JAXB match type derivation with class inheritance. Therefore, the Command service should not be hard to expose. Regarding invocation, be careful, don't treat web services as RMI. For a document-oriented service, the notion of "parameters" has no meaning. We must devise a way to assemble an XML document from the process variables. I remember discussing this topic some time ago (in the sourceforge forums!). Back then I rounded up the conclusions and put together a paper. I just attached it to a Wiki page. We can pick up from there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957176#3957176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957176

19 years, 3 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: EAR Metadata

by jicken

do you think of /** An arbitrary map of state associated with the deployment */ | public transient HashMap context = new HashMap(); in DeploymentInfo filled via a generic key-value xml file describing the deployment? e.g. | <deployment-context> | <jndi-root-context>my-ear</jndi-root-context> | <2ndKey>2ndValue</2ndKey> | </deployment-context> | resulting in the context hashmap {["jndi-root-context", "my-ear"], ["2ndKey", "2ndValue"]} View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957166#3957166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957166

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: webservices and jbpm

by kukeltje

Thanks, I did not look into this for the last few months . For this 'customer' I'll try using axis2 with xmlbeans (their, no rather mine current preference) but it has to wait for at least two weeks since I'm off playing golf in France for 5 days. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957162#3957162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957162

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: decision conditions

by hosierdm

"alex.guizar(a)jboss.com" wrote : Further, jPDL is a process language. Most people will use the GPD for edition, so we don't need to be consistent with programming languages. I just picked up this thread and wanted to comment on the above. I slightly disagree, since there is currently no way to specify conditions on a transition without directly editing the XML. I think it could be viewed like a switch statement in Java (and C/C++ or whatever) with an implied break. It goes down the list and takes the first transition whose expression evaluates to true. If that doesn't happen, it drops to the last one, just like a default: line. I figure I'm way late adding to this debate, but what the hell.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957149#3957149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957149

19 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Use of Throwable in method signatures

by scott.stark＠jboss.org

The use of Throwable in a number of the mc signatures causes integration issues with other apis that only expose an Exception. For example, the BeanDeployer initialization of the BasicXMLDeployer in start is going to have to catch a Throwable and cast it to either an Error subtype or Exception subtype: | /** Overriden to initialize the BasicXMLDeployer | */ | @Override | public void start() throws Exception | { | kernelDeployer = new BasicXMLDeployer(context.getKernel()); | super.start(); | } | In the case of an actual Throwable being seen it will have to be wrapped. Can we just use Exception as the base throws signature in the mc? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957142#3957142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957142

19 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: testing the new list server

by scott.stark＠jboss.org

I'm not seeing emails for these posts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957137#3957137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957137

19 years, 3 months

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: how to test POP3 in Outlook

by gohip＠ichibancomputers.com

currently, JBCS does not clean up after itself, when a message is deleted, it is only removed from messagedata table, it is recommended, for now, to have a cron job, that cleans the other tables, there is code(sql) in forums that does this, or if you like, I can post what I am doing... nice, so it sounds like it is working fine for you now, messagedata, should have message headers in it, if, and only if, the message has not been deleted by the mail client. so nothing wrong with your driver, it is "natural" for this to happen. I suck at hibernnate, and trying to learn(not trying very hard), so cant help with blobs vs. long blobs, one of the other guys, may be able to help! Glad you got it working! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957130#3957130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957130

19 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2006