March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite runs failing due to server failed startups/tim

by ryan.campbell＠jboss.com

"rachmatowicz(a)jboss.com" wrote : A similar issue was raised (JBQA-405) and the code was changed by Anil to add the class library commons-logging.jar to the stopServerClasspath(), as when exec'ing org.jboss.Shutdown, it may fail to execute due to classes it needs not being present on ths classpath. I believe this was in response to 'minimal' not shutting down, and this was a repeatble error. However, these changes made in the JIRA issue are not present in the current distribution versions. | If we were seeing the server fail to shutdown cleanly across platforms, I agree investigation of JBQA-405 would be pertinent. But since it is intermittent, I think it is more likely that the "all" server is experiencing an OOME, which prevents it from responding to the shutdown request. Have you verified that the "all" server is not experiencing an OOME by looking at the logs? "rachmatowicz(a)jboss.com" wrote : | 1. reworking the targets above to use server:start and server:stop, so that at least we have consistent behaviours being applied to stopping and starting servers. | 2. re-investigate the probelm with 'all' not shutting down, which may be sue to OOME. One approach would be to introduce TRACE statements which trace the execution of steps between a client exec'ing Shutdown, and the shutdown() request being processed on the server side. | I am in total agreement with #1. As for #2, you should be able to see the presence of an OOME just by greping the logs. If you don't see it, an OOME on the server is unlikely, IIUC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029440#4029440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029440

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Upgrade to JGroups 2.4.1.SP1

by bstansberry＠jboss.com

Bela's released a 2.4.1.SP1 (see http://jira.jboss.com/jira/browse/JGRP?report=com.atlassian.jira.plugin.s...) that's going in AS 4.2.0. I'd like to move AS trunk to it as well, but the build fails with: C:\dev\jboss\jboss-head\build\build-thirdparty.xml:143: A versioning problem exi | sts: | Component: jgroups is at version: 2.4.1.SP1 | but it is also required to be compatible with: [Compatible@12b6c89{id=null, ver | sion=2.4.1}] | by: jboss/messaging Seems we need a process for coordinating these kinds of moves. What do you guys need to be able to do declare compatiblity? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029438#4029438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029438

19 years

1
0
0 / 0

[Design of POJO Server] - Re: Missing EAR/WAR Isolation

by scott.stark＠jboss.org

The EARStructure defines what the deployable content is in the ear along with what its classpath is. It does not define scoping. This should be coming from the metadata of the AppParsingDeployer (jboss-app.xml, deployer isolation property) that is passed to the ServiceClassLoaderDeployer which should be creating the scoped ULR. I'll have to check if this is wired up correctly. I'm working on the jboss5 testsuite so I'll look at the existing ear isolation tests today. On the first port of the war deployer, jbossweb didn't have a mechanism to accept a class loader so it was commented out. It should be creating a scoped class loader by default though, but its probably still an implementation detail of the webcontainer. It does need to be pulled out so its available at the DeploymentUnit level. I assume that is what you are looking for? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029430#4029430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029430

19 years

1
0
0 / 0

[Design of POJO Server] - Missing EAR/WAR Isolation

by jason.greene＠jboss.com

It looks like we are missing EAR isolation in the trunk ear deployer. This results in several WS TCK failures: http://jira.jboss.com/jira/browse/JBWS-1581 After looking at the code, it appears the intention is that EARStructure should be creating an isolated load repository config that is used by the ServiceClassLoaderDeployer. Any reason this has not been implemented yet? Another reason for this failure is that WAR isolation is effectively disabled as well (WarClassLoadingDeployer is commented out). Why? -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029422#4029422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029422

19 years

1
0
0 / 0

[Design of Kosmos] - Re: Error: HessianServiceExporter only supports POST request

by aron.gombas

Can you see any exception or ERROR in your system log? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029401#4029401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029401

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBAS-4204, BasicQueue.removeAllMessages cleanup

by adrian＠jboss.org

Tim, you probably want to port this test to JBoss Messaging if you don't have something similar already. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029397#4029397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029397

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBAS-4204, BasicQueue.removeAllMessages cleanup

by adrian＠jboss.org

I've fixed this. It shouldn't even be doing the removeAllMessages() in this case, it should be throwing an exception to the application. The user will now get an javax.jms.IllegalStateException if they unsubscribe() a Durable TopicSubscription while it is still active. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029392#4029392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029392

19 years

1
0
0 / 0

[Design of JBoss Serialization] - Re: Debug support for Serialization

by nico.ben

"clebert.suconic(a)jboss.com" wrote : anonymous wrote : Every class in my app is serializable and has a default constructor. | | This problem is about non serializable classes without a default constructor. Hi! Is there a way to find which class causes this? The log output doesn't seem to contain the name of my guilty class :) Thx, Nic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029388#4029388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029388

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: CICS gateway

by estebanschifman

Let's see if we can clarify. Currently, gateways are inbound only. They are supposed to obtain any object (file, JMS message, etc.), package it as an ESB message, and send it to an EPR where a 'message aware listener' will pick it up, and pass it to an ActionProcessingPipeline. Once you are in the pipeline, any outgoing arbitrary object (arbitrary in the sense that it does not need to be an esb message), can be produced in any (user) action class, either by the method speficied in the 'process' attribute (default is process(Message) method), or in the method specified in the (optional) 'okMethod ' property for normal completion, or in the method specified in the (also optional) 'exceptionMethod' property A generic example of how to do this is: | <actions> | <action name="outboundObject" class="mypackage.MyClass" process="step1, step2,step3"> | <property name="okMethod" value="mySuccessMethod" /> | <property name="exceptionMethod" value="myFailureMethod" /> | </action> | </actions> | This example has only one action class in the pipeline, but it invokes three methods in sequence: step1, step2 and step3. Signature of these three is Message stepX(Message) throws Exception If the 'process' attribute were not included, the default is to invoke the Message process(Message) method in the action class. If at any point, the sequence of steps throws an Exception, and the property with name 'exceptionMethod' was specified (as in our example), then the corresponding method will be invoked (signature: void xxxxx(Message, Throwable)) If the sequence runs successfully (no Exceptions thrown), and the property with name 'okMethod' was specified (as in our example), then the corresponding method will be invoked (signature void zzzzz(Message)) An 'outbound gateway' can be implemented simply by implementing methods for success and failure with the proper signatures, and specify them in the 'okMethod' and 'exceptionMethod' properties of the action class. I hope this helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029382#4029382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029382

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite broken in 4.2

by mvecera＠redhat.com

Hello, I was applying patch concerning JBAS-3993, but suddenly the ${jboss.dist} is unknown in build.xml. I commented it out, so now it works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029360#4029360 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029360

19 years

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-dev-forums March 2007