[Clustering/JBoss] - How to debug multicast hang?
by peso60
I am running oracle application server 10.1.3.0 which, apparently uses jgoups. All of a sudden on my Red Hat 3 (Red Hat Enterprise Linux AS release 3 (Taroon Update 6)) machine the process starts, but doesn't respond to any requests.
There were no changes to configuration or code, or machine, tried reboot and make sure no other java processes are running.
The last out put before it stops responding is this:
2006-10-30 11:14:22.726 WARNING option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored
Oct 30, 2006 11:14:22 AM org.jgroups.protocols.pbcast.NAKACK handleConfigEvent
INFO: max_xmit_size=64000
Oct 30, 2006 11:14:22 AM org.jgroups.protocols.UDP createSockets
INFO: sockets will use interface 140.87.10.48
Oct 30, 2006 11:14:22 AM org.jgroups.protocols.UDP createSockets
INFO: socket information:
local_addr=140.87.10.48:1045, mcast_addr=234.5.5.5:24667, bind_addr=/140.87.10.48, ttl=32
sock: bound to 140.87.10.48:1045, receive buffer size=524288, send buffer size=524288
mcast_recv_sock: bound to 140.87.10.48:24667, send buffer size=524288, receive buffer size=524288
mcast_send_sock: bound to 140.87.10.48:1046, send buffer size=524288, receive buffer size=524288
'ps' shows that the java process that was supposed to start is in fact running, and the main HTTP listening port (8888) is shown as LISTEN by netstat and lsof; lsof output:
lsof|grep 8888
java 12642 opeschan 35u IPv4 9721891 TCP *:8888 (LISTEN)
But the port is not responding, simple 'kill' does not kill the java process, but 'kill -5/-9' kills it.
Where do I even start looking for a reason?
I tried reboot, it didn't help.
THAAANKS!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981880#3981880
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981880
19 years, 5 months
[JBoss jBPM] - Re: Deploying jbpm.war(3.1.3) to jboss as 4.0.5GA
by zauberlehrling
As I understand a ClasscastException is raised at line 435 in the class SAXReader,
this exception is caught at line 468 and again a DocumentException is thrown at line 484:
| 433 public Document read(InputSource in) throws DocumentException {
| 434 try {
| 435 XMLReader reader = getXMLReader();
| 436
| 437 reader = installXMLFilter(reader);
| 438
| 439 EntityResolver thatEntityResolver = this.entityResolver;
| 440
| 441 if (thatEntityResolver == null) {
| 442 thatEntityResolver = createDefaultEntityResolver(in
| 443 .getSystemId());
| 444 this.entityResolver = thatEntityResolver;
| 445 }
| 446
| 447 reader.setEntityResolver(thatEntityResolver);
| 448
| 449 SAXContentHandler contentHandler = createContentHandler(reader);
| 450 contentHandler.setEntityResolver(thatEntityResolver);
| 451 contentHandler.setInputSource(in);
| 452
| 453 boolean internal = isIncludeInternalDTDDeclarations();
| 454 boolean external = isIncludeExternalDTDDeclarations();
| 455
| 456 contentHandler.setIncludeInternalDTDDeclarations(internal);
| 457 contentHandler.setIncludeExternalDTDDeclarations(external);
| 458 contentHandler.setMergeAdjacentText(isMergeAdjacentText());
| 459 contentHandler.setStripWhitespaceText(isStripWhitespaceText());
| 460 contentHandler.setIgnoreComments(isIgnoreComments());
| 461 reader.setContentHandler(contentHandler);
| 462
| 463 configureReader(reader, contentHandler);
| 464
| 465 reader.parse(in);
| 466
| 467 return contentHandler.getDocument();
| 468 } catch (Exception e) {
| 469 if (e instanceof SAXParseException) {
| 470 // e.printStackTrace();
| 471 SAXParseException parseException = (SAXParseException) e;
| 472 String systemId = parseException.getSystemId();
| 473
| 474 if (systemId == null) {
| 475 systemId = "";
| 476 }
| 477
| 478 String message = "Error on line "
| 479 + parseException.getLineNumber() + " of document "
| 480 + systemId + " : " + parseException.getMessage();
| 481
| 482 throw new DocumentException(message, e);
| 483 } else {
| 484 throw new DocumentException(e.getMessage(), e);
| 485 }
| 486 }
| 487 }
The method getXMLReader() returns an object of type SAXParserImpl$JAXPSAXParser (Why?), which is not a subclass of XMLReader . I can find the class SAXParserImpl$JAXPSAXParser in the file $JBOSS_HOME/lib/endorsed/xercesImpl.jar.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981879#3981879
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981879
19 years, 5 months
[JBoss Seam] - Trying async in 1.1 -- behaves like sync
by rdewell
Thought I'd give this a shot. We have a process that can occur in the background instead of holding up the display of the next page. Perfect candidate for async.
So I created a stateless test bean to call during another form submission / action:
| @Stateless
| @Name("OrderProcessor")
| @Interceptors(SeamInterceptor.class)
| public class OrderProcessorImpl implements OrderProcessor, Serializable{
| private static final long serialVersionUID = -8591335166721681758L;
|
| @Asynchronous
| public void process(@Duration long initialStartMS, String id) {
| LOG.info("Processing: " + id);
|
| try {
| Thread.currentThread().sleep(1000 * 30);
| } catch (InterruptedException e) {
| e.printStackTrace();
| }
| }
|
The 30 second sleep in there just simulates some long running logic in the method.
I expected to:
- Have the submitted action that calls this async method to return almost immediately with a view.
- In 60 seconds (which is what I pass in the duration param), see the "Processing: XYZ" in the logs.
- Of course have the currently submitted action be unaffected by either the 60 seconds passed in as the init duration, and definitely not affected by the 30 second sleep..
But instead:
- Almost immediately after submitting the form action I see in the logs: "Processing: xyz"..
- A full 30 seconds goes by before my view returns from the action that was called (the action which called the async).
?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981877#3981877
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981877
19 years, 5 months