August 2010 - jboss-dev-forums - Jboss List Archives

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by Kabir Khan

Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557357#557357 -------------------------------------------------------------- > Brian Stansberry wrote: > > > David Lloyd wrote: > > > > Might be easier to use specific exit values: 0 means shut down on purpose, anything else means crash? > > That certainly seems simpler. :) > > > Either way the SM should be notified if a Server exits, regardless of the cause: if the server is not configured to be shut down but it returns 0, the SM needs to kick it back alive again. Also the same respawn logic has to apply; otherwise a poorly-placed System.exit(0) can bog down the system with fork/execs. > > +1 on notifying the SM and the restart rules. Whether the SM should automatically restart the server following getting a signal that one shut down cleanly, I'm not so sure. The signal should imply some human action was taken to cause the shutdown, and if that's the case I think requiring human action to restart makes sense. The SM should squawk in the logs though if the shutdown happens via something other than the intended managment API. I have handled exit code = 0 to not respawn in http://github.com/kabir/jboss-as/commit/8862da78064ca95b5ff8d2e866e38093e... http://github.com/kabir/jboss-as/commit/8862da78064ca95b5ff8d2e866e38093e... I'll look at notifying the SM next week when I get to implementing the SM<->Server protocol. I have made a start on socket-base PM-process communication but should probably hold off until some consensus on if we want that is reached? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557357#557357] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557351#557351 -------------------------------------------------------------- CLI is a no go. Someone can do ps -ef and get the token. STDIN sounds best -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557351#557351] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by David Lloyd

David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557350#557350 -------------------------------------------------------------- > Jason Greene wrote: > > The big issue is of course security. We likely will have to add some kind of auth protocol to this. Perhaps some kind of token is written to a tmp file that can be read by the other child processes. Yes, a security token should be used, but it should just be passed into the child process on stdin or as a CLI argument. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557350#557350] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by David Lloyd

David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557347#557347 -------------------------------------------------------------- > Brian Stansberry wrote: > > If we're going to open sockets, we need to make the binding configurable so admins can lock down what is used. 127.0.0.1:0 is fine as a default though. > > Haha, I started off as opposed to using stdio, but now feel oddly supportive of it. Not sure why. > > In any case, even if we use sockets for the inter-process messaging traffic, these thread dumps are going to go to the PM via stdout/ManagedProcess$OutputStreamHandler. So we need to decide what to do with them. Convert them to log messages in the PM log, a la the above? Dump the directly to PM's stdout? (I'm checking if that will actually just result in log messages in the PM log file.) Maintain a file per managed process? I think just continuing with the idea of using a log category per server is fine. Then the PM's logging.properties can configure it however the user wants. I think people will be looking for this info on the console though. Also, it's worth verifying that hitting ctrl-/ on the PM will or won't cascade to all child processes, causing a huge mass of thread dumps to occur. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557347#557347] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557346#557346 -------------------------------------------------------------- The big issue is of course security. We likely will have to add some kind of auth protocol to this. Perhaps some kind of token is written to a tmp file that can be read by the other child processes. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557346#557346] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Process Manager

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "Process Manager" To view the discussion, visit: http://community.jboss.org/message/557340#557340 -------------------------------------------------------------- If we're going to open sockets, we need to make the binding configurable so admins can lock down what is used. 127.0.0.1:0 is fine as a default though. Haha, I started off as opposed to using stdio, but now feel oddly supportive of it. Not sure why. In any case, even if we use sockets for the inter-process messaging traffic, these thread dumps are going to go to the PM via stdout/ManagedProcess$OutputStreamHandler. So we need to decide what to do with them. Convert them to log messages in the PM log, a la the above? Dump the directly to PM's stdout? (I'm checking if that will actually just result in log messages in the PM log file.) Maintain a file per managed process? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557340#557340] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Deploying services and error handling

by Alexey Loubyansky

Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] replied to the discussion "Deploying services and error handling" To view the discussion, visit: http://community.jboss.org/message/557321#557321 -------------------------------------------------------------- I've created the main task for deployment error handling https://jira.jboss.org/browse/JBAS-8334 https://jira.jboss.org/browse/JBAS-8334 (which is assigned to me for now) and subtasks to make sure it's properly done > A deployment can fail validation on the domain controller. In this event, the deployment is not added to the domain and an error is thrown from the deployer API, so this does not impact the server. > https://jira.jboss.org/browse/JBAS-8336 https://jira.jboss.org/browse/JBAS-8336 (unassigned for now) > A deployment can fail to be added to the MSC batch. For example, a service may be attempted to be defined which already exists in the batch (in fact, at present this is the only possible error outside of outright code bugs). In this event, the correct thing to do is to log the error and continue. https://jira.jboss.org/browse/JBAS-8335 https://jira.jboss.org/browse/JBAS-8335 (unassigned at the moment) > A failure can happen at batch resolve time. *This is currently a problem case.* In this case the entire batch is undone. Types of failures here include: duplicate service definition (i.e. a service was defined that already exists in the container), missing required dependency (i.e. a service was defined that depends on something that isn't there), circular dependency (i.e. two or more service definitions represent circularity in terms of their dependency links). Right now this erases the entire batch, which means that the server cannot start if any of these errors occur. I think that circularity is quite unlikely but the other two errors are not uncommon, and should not prevent the server from starting up. The correct behavior is, in my opinion, to log each error and continue, possibly yielding a report of problem services after the batch is resolved (it is likely, however, that one failure will lead to others). https://jira.jboss.org/browse/JBAS-8337 https://jira.jboss.org/browse/JBAS-8337 (assigned to me) > A failure can happen during service start. In this case, the exception is logged, and all the service's dependents will be trapped in a waiting state. This type of error will typically be due to transient conditions, like an incorrectly configured IP address, disk space issues, and so on. The correct behavior here is to log the error and let the user decide (based on the GUI or perhaps by deployment plan policy) whether to fix the issue and retry the failed service, let the error stand, or pull out the deployment unit. https://jira.jboss.org/browse/JBAS-8338 https://jira.jboss.org/browse/JBAS-8338 (unassigned at the moment) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557321#557321] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2830 change the strategy of BPMN name and key convertion

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "JBPM-2830 change the strategy of BPMN name and key convertion" To view the discussion, visit: http://community.jboss.org/message/557293#557293 -------------------------------------------------------------- sounds reasonable to me. Please include some documentation for that to let users find it easily. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557293#557293] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2873 - support for like in query

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "JBPM-2873 - support for like in query" To view the discussion, visit: http://community.jboss.org/message/557291#557291 -------------------------------------------------------------- Finally I am done with implementation work for this issue, it covers all queries plus requested change to use hibernate way of applying parameters to the query. Supported SQL operands are: - Equals - Like - In - Not in Please have a look at latest patch ( https://jira.jboss.org/secure/attachment/12336300/JBPM-2873-final.patch JBPM-2873-final.patch) and let me know what do you think about it. In the end I decided to change it a bit and provide overloaded method for each available parameter that allows to provide operand for the query instead of having one method that sets the operand prior to setting the parameter. This way is more intuitive and in line with current implementation. Cheers -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557291#557291] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

[JBoss ESB Development] - Exposing webservice on ESB using SoapProcessor - wrong soap:address

by Mikael JÃ¸rgensen

Mikael JÃ¸rgensen [http://community.jboss.org/people/mikaelfj] created the discussion "Exposing webservice on ESB using SoapProcessor - wrong soap:address" To view the discussion, visit: http://community.jboss.org/message/557289#557289 -------------------------------------------------------------- Hi, I'm building up some action pipelines in JBoss ESB. The first action is a webservice, exposed by the SoapProcessor - and the idea is to let the action pipeline be triggered by an invokation of the webservice, and then to have the next actions perform various tasks based on the content of the provided Message. It seems as if there are two ways of getting the WSDL for the webservice * Through http://host:8080/contract/ http://host:8080/contract/... * Through http://host:8080/Webservice.../....WS?wsdl http://host:8080/Webservice.../....WS?wsdl The first is the one generated by the ESB and and the latter is (if understood correctly) the one generated by JBossWS. If I use the latter one, then when I invoke the webservice, the Message gotten from SOAPProcessor.getMessage() is null, and if I understood it correctly, I need to use the first WSDL that refers to the specific port that was defined for the JBR provider that my service listens to. So all this works fine when running it all locally - i.e. I have a webservice client that uses the WSDL obrtained from http://host:8080/contract/ http://host:8080/contract/... to invoke the webservice. But, if I deploy the ESB/action pipeline on a remote server it breaks. I expect that the cause of the problem is, that the WSDL returned from http://host:8080/contract/...contains http://host:8080/contract/...contains a soap:address looking like: <soap:address location=" http://localhost:8770/ http://localhost:8770/"/> and this address does not make sense when the webservice is deployed on a remote host. It looks like the soap:address of the WSDL just contains the string from the host attribute in the JBR provider definition from the jboss-esb.xml. Is this how it is supposed to be? If it is, how am I supposed to deploy the ESB stuff remotely - I't can't be that I need to alter the host attribute of the JBR provided to match the hostname of the machine it is deployed to. If this is not how it is supposed to be - how do I get hold on the proper WSDL which points to the proper host and port. (Or am I doing this entirely wrong ....?) Regards Mikael -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557289#557289] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2010