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

Re: [jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/559353#559353 -------------------------------------------------------------- > Given most of this classes above is package protected, I'll refactor those and write a method that does this internally as part of the API. I'll post back when I'm done. No need for this, as I can simply move this service into that package. And if there is really a need, I can hide its impl details later on. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559353#559353] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - History details

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "History details" To view the discussion, visit: http://community.jboss.org/message/559331#559331 -------------------------------------------------------------- Charles, I am aware of this problem (it is cause by not completed implementation) and it will not be fixed with this particular patch but with another one that I worked on - it focuses mainly on modification to queries ( JBPM-2873 ). Once both patches are applied it will work properly. I am planning to do the commits in few days. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559331#559331] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - History details

by Charles Aznavour

Charles Aznavour [http://community.jboss.org/people/charles_a] replied to the discussion "History details" To view the discussion, visit: http://community.jboss.org/message/559322#559322 -------------------------------------------------------------- Hi Maciej, In 4.4, I receive a Nullpointer exception when using the historyService.createHistoryDetailQuery().processInstanceId(executionId).count(); It´s based on the count() method of AbstractQuery trying to cast null to a Long, null comes from query.uniqueResult() in execute method of the same class. Will that be fixed with this patch? Cheers, Charles -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559322#559322] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM in graphic presentation

by Michael Wohlfart

Michael Wohlfart [http://community.jboss.org/people/mwohlf] replied to the discussion "JBPM in graphic presentation" To view the discussion, visit: http://community.jboss.org/message/559307#559307 -------------------------------------------------------------- please check out this thread: http://community.jboss.org/thread/155492 http://community.jboss.org/thread/155492 -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559307#559307] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Profiler Development] - problem after installation

by Uwe Rasmus

Uwe Rasmus [http://community.jboss.org/people/uwerasmus] replied to the discussion "problem after installation" To view the discussion, visit: http://community.jboss.org/message/559297#559297 -------------------------------------------------------------- ok, I have found that startProfiler and snapshot snapshot snapshot :) will generate reports. But how to use it effectively, along with other commands? I was not successfull with getSnapshot X. :( Thanks for help Uwe -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559297#559297] Start a new discussion in JBoss Profiler Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Profiler Development] - problem after installation

by Uwe Rasmus

Uwe Rasmus [http://community.jboss.org/people/uwerasmus] replied to the discussion "problem after installation" To view the discussion, visit: http://community.jboss.org/message/559292#559292 -------------------------------------------------------------- As I am on Windows, editing of run.bat should be sufficient. However I found that when starting JBoss from Eclipse, it doesn't use run.bat. I added the java-opts parameters into VM arguments and it works. Still, I'm not sure, what is the usual profiling cycle after successfull start of JBoss. Somewhere I read - After installing the profiler use the * startProfiler * stopProfiler * getSnapshot but the stopProfiler command justs hangs and never returns to my cmdline. Any help? Thanks a lot Uwe -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559292#559292] Start a new discussion in JBoss Profiler Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - History details

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "History details" To view the discussion, visit: http://community.jboss.org/message/559286#559286 -------------------------------------------------------------- Yeap. my mistake forgot to include these tests in the patch. Here comes the link to updated patch: https://jira.jboss.org/secure/attachment/12336598/history-detail-20100827... https://jira.jboss.org/secure/attachment/12336598/history-detail-20100827... I modified it a bit to leave only lazy='false' for variables. Huge thanks for reviewing. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559286#559286] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - ServerManager-Server(-ProcessManager) communication

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "ServerManager-Server(-ProcessManager) communication" To view the discussion, visit: http://community.jboss.org/message/559257#559257 -------------------------------------------------------------- Re: respawning Servers, why would a Server die? 1) User kills the Server process via an OS tool. Why would they do that? a) By mistake. Restarting is helpful in this case. b) Because the user doesn't understand our admin interfaces. Here restarting is helpful since they will need to learn to use the management interfaces if they actually want the server to stay dead. :) c) Because the DC is dead and can't be revived or the SM is misbehaving, so the user can't shut down or restart the server via the normal admin interface. Here we don't know whether the user wanted a restart. 2) Some other fatal error occurs. Should we let a human try and figure out what happened? Maybe bringing the server back up will just increase instability in the overall domain. Looking at that, I see no clear answer whether restarting makes sense. So, how about punting? Add a auto-restart flag to the <server> element. Default is true. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559257#559257] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - ServerManager-Server(-ProcessManager) communication

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "ServerManager-Server(-ProcessManager) communication" To view the discussion, visit: http://community.jboss.org/message/559254#559254 -------------------------------------------------------------- Agreed on SM should be responsible for respawning servers. But I'll comment further in another post. Re: *2.4.3.2.1 and .2* -- those seem correct. Otherwise there is a kind of zombie process. I suppose 2.4.3.2.2 (the remove) could be skipped if the SM knew it was going to restart the process. *3.1* I like the idea of the PM being responsible for failure detection. For one thing it has the stdio streams as a fallback to confirm server failure. Contrived example: admin restarts interface lo so all the socket connections break. But the servers are all still working and can reconnect. *3.2.2* I think the PM should restart the SM. The PM has no interface beyond whatever it reads in from the command line. And the servers expect to be managed via the SM. So if the SM is allowed to die and not restart, the entire set of processes can't be managed except via a kill command. The original design was to always have a running SM. We then split out the PM as a separate process just to * Allow the SM to be upgraded/patched w/o requiring Servers to shut down. The PM would be dead simple with no dependencies and thus wouldn't need to be patched. * Make the Servers more reliable by having the process that consumes their stdio streams as simple as possible. So bugs in SM would not causes Servers to crash. *5* Besides the shutdown hook in the PM, the other reasons for closing down everything are * SM receives a command from the DC telling it to do so * If the SM exposes a remote managment interface, it receives a command via that telling it to do so *6.1.1* I don't think this applies. The PM has no remote interface that would let it receive an instruction to restart the SM. And I don't think any internal state change in the PM would trigger such a thing. *6.3.1* IMO it would be restarted by the PM. *6.3.4* Could the differentiator be a simple param passed by the PM to the SM on the command line? Something to think about though is the SM needs get its internal state consistent with the actual state of affairs. What if it thinks there are 3 servers but actually there are 4? (That would be odd.) Or there are only two -- what triggers it to realize it never got a new connection from the 3rd? Right now the SM doesn't keep much state, but as we flesh it out it probably will (e.g. a copy of each Server's Standalone config object). Following a restart it probably shouldn't just assume it's state is consistent with the Server. That can be checked easily enough by getting the result of Standalone.elementHash() from the server and comparing it to its own value. One kinda hacky thought is if the PM knows the ManagedProcess is already started, it could ignore 2.4.1 and when it receives 2.4.2 it sends an SM_RESTARTED message to the Server (instead of starting it). That tells the server to connect to the SM. Another thing to think about with 2.4 is whether we want to support concurrent startup of servers. Also, we need some mechanism to control the order of server start across the domain. That could just be following the order of server-group elements in the domain.xml, and then the order of server elements in the host.xml. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559254#559254] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - History details

by Michael Wohlfart

Michael Wohlfart [http://community.jboss.org/people/mwohlf] replied to the discussion "History details" To view the discussion, visit: http://community.jboss.org/message/559197#559197 -------------------------------------------------------------- I don't have line 186 in my HistoryDetailQueryTest :-/ -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559197#559197] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 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-dev-forums August 2010