[JBoss JIRA] Created: (JGRP-560) Message greater than 16286 bytes is not received on MaxOS
by Bela Ban (JIRA)
Message greater than 16286 bytes is not received on MaxOS
---------------------------------------------------------
Key: JGRP-560
URL: http://jira.jboss.com/jira/browse/JGRP-560
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
I'm new to JGroups, and I have a Mac OS X (10.4)-specific question. I've used
JGroups 2.4.1sp3, 2.5.0CR1, and the new 2.5.0GA - I see the same issue with
all versions.
I've noticed that, for UDP, there seems to be a max message size of 16286
bytes (a little less than 16K). This is using the default udp.xml config,
and just a simple message to another node like:
JChannel ch = new JChannel("udp.xml");
ch.setReceiver(this);
ch.connect("TEST");
//
// 'target' is another group member besides myself
//
byte[] buf = new byte[size];
Arrays.fill(buf, (byte)77);
echo("Sending message: " + size + " bytes");
Message msg = new Message(target, null, buf);
ch.send(msg);
A receiver node will NOT receive the message if 'size' is greater than
16286. In fact, after sending a too-large message, the receiver sees no
message trafffic so it starts doing heartbeats and view changes). I've
attached some debug output below.
TCP transport does not have this problem.
I'm aware of the tos="8" attribute warning in OS X, and changing the value
to 0 to avoid the warning doesn't affect the max size issue. Though perhaps
it's the same Mac quirk causing both problems...
I've searched around, but haven't seen anything about this. Is it a known
issue? Is there a workaround? Am I doing something wrong?
Thanks in advance,
Rick Pike
Debug output:
-------------------------
SENDER:
(Sends increasing size messages, 2 sec apart. As soon as the size goes
beyond 16286, it notices a problem).
Sending message: 16284 bytes
Sending message: 16285 bytes
Sending message: 16286 bytes
2007-07-17 12:06:25,934 [DEBUG] FD sending are-you-alive msg to
192.168.2.71:51607 (own address=192.168.2.71:51610)
2007-07-17 12:06:25,936 [DEBUG] FD received ack from 192.168.2.71:51607
Sending message: 16287 bytes
Sending message: 16288 bytes
RECEIVER:
(Gets messages OK until 16287. I assume FD starts because it sees no message
traffic.)
Received message: 16284 bytes
Received message: 16285 bytes
Received message: 16286 bytes
2007-07-17 12:06:25,876 [DEBUG] FD sending are-you-alive msg to
192.168.2.71:51610 (own address=192.168.2.71:51607)
2007-07-17 12:06:25,884 [DEBUG] FD received ack from 192.168.2.71:51610
2007-07-17 12:06:29,305 [DEBUG] MERGE2
initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
is_server=true], [own_addr=192.168.2.71:51607,
coord_addr=192.168.2.71:51607, is_server=true]]
2007-07-17 12:06:35,877 [DEBUG] FD sending are-you-alive msg to
192.168.2.71:51610 (own address=192.168.2.71:51607)
2007-07-17 12:06:35,880 [DEBUG] FD received ack from 192.168.2.71:51610
2007-07-17 12:06:42,496 [DEBUG] MERGE2
initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
is_server=true], [own_addr=192.168.2.71:51607,
coord_addr=192.168.2.71:51607, is_server=true]]
2007-07-17 12:06:45,879 [DEBUG] FD sending are-you-alive msg to
192.168.2.71:51610 (own address=192.168.2.71:51607)
2007-07-17 12:06:45,880 [DEBUG] FD received ack from 192.168.2.71:51610
2007-07-17 12:06:50,453 [DEBUG] FD_SOCK peer closed socket normally
2007-07-17 12:06:50,453 [DEBUG] FD_SOCK pinger thread terminated
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBPM-1068) Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton
by Vt Ysh (JIRA)
Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton
-------------------------------------------------------------------------------------------------
Key: JBPM-1068
URL: http://jira.jboss.com/jira/browse/JBPM-1068
Project: JBoss jBPM
Issue Type: Feature Request
Components: Web Interface
Affects Versions: jBPM jPDL 3.2.1
Reporter: Vt Ysh
Assigned To: Tom Baeyens
Priority: Optional
If i am trying to put custom action tags between for example <tf:saveButton value="Save"></tf:saveButton > such as it can be done with h:commandButton i am getting NullPointer exception with the next stack trace:
java.lang.NullPointerException
at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.getEnclosingForm(UITask
FormButtonBase.java:30)
at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.addActionListener(UITas
kFormButtonBase.java:44)
at org.jbpm.jsf.core.handler.AbstractHandler.apply(AbstractHandler.java:
64)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:128)
at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(Def
aultFaceletContext.java:306)
at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(Default
FaceletContext.java:279)
at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at test.facelets.IfHandler.apply(IfHandler.java:33)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFac
eletContext.java:143)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:113)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java
:503)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav
a:546)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrap
per.java:178)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha
se.java:106)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
kerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
Seems that problem can be in HtmlCommandButton.getParent() method. Is there any suggestions how to fix this issue?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBPM-1067) token.getAvailableTransitions() -- need equivalent that returns ordered list.
by s b (JIRA)
token.getAvailableTransitions() -- need equivalent that returns ordered list.
-----------------------------------------------------------------------------
Key: JBPM-1067
URL: http://jira.jboss.com/jira/browse/JBPM-1067
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: All OS
Reporter: s b
Assigned To: Tom Baeyens
This feature request is requesting:
1) API which adds a version of token.getAvailableTransitions() which returns an ordered List that preserves the order of the transitions as defined in the processdefinition.xml file for the node, rather than returning an unordered Set object.
2) Also request that TaskInstance.getAvailableTransitions() be modified to return an ordered list rather than a randomly ordered list by calling the new method.
For example:
------------------------
public class TaskInstance extends VariableContainer implements Assignable {
...
public List getAvailableTransitions() {
List transitions = null;
if ( (! isLast())
&& (token!=null)
) {
transitions = token.getAvailableTransitionsList(); // using new method
}
return transitions;
}
...
----------------------------------------
Problem:
node.getLeavingTransitions() appears to preserve the order, but the order is apparently lost when the transistions are added to the Set which is returned by token.getAvailableTransitions().
Preserving the ordering is highly useful when implementing a minimal data-driven interface which presents the user with the transitions to choose from. The designer could exercise some control over the presentation of the choices if only the order were preserved as defined in the processdefinition.xml file.
Solution:
Make a clone of "token.getAvailableTransitions()", name it "token.getAvailableTransitionsList()", and add the filtered transitions to a List instead of to a Collection, and return the list. Make sure the order is preserved the same as the transitions were defined in the "processdefinition.xml" file.
Modify "TaskInstance.getAvailableTransitions()" to call token.getAvailableTransitionsList().
Summary:
Although workarounds exist with existing code, it would be very helpful (and consistent I think) to provide an API that retrieves a list of the "available transitions" that is ordered as defined in the processdefinition.xml file instead of an unordered Set or List as is currently available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBRULES-1220) Integration with jBPM does not work
by Jiri Pechanec (JIRA)
Integration with jBPM does not work
-----------------------------------
Key: JBRULES-1220
URL: http://jira.jboss.com/jira/browse/JBRULES-1220
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.1
Reporter: Jiri Pechanec
Assigned To: Mark Proctor
Priority: Minor
We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
workingMemory.setGlobalResolver(new GlobalResolver() {
private static final long serialVersionUID = 1L;
public Object resolveGlobal(String identifier) {
System.out.println("!!!!!!!!!! resolve " + identifier);
return ci.getVariable(identifier);
}
public void setGlobal(String identifier, Object value) {
System.out.println("!!!!!!!!!! set " + identifier);
ci.setVariable(identifier, value);
}
});
And a rule file that serves as test
package org.jbpm.action
import org.jbpm.resolveraction.Customer;
import org.jbpm.resolveraction.Order;
import org.jbpm.context.exe.ContextInstance;
global java.lang.String shipper
rule "Determine Shipper"
when
Customer( region >= 1 )
Order( totalAmount >= 0 )
then
System.out.println(shipper);
drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
System.out.println("ship via FEDX " );
end
The output of the test is as expected
11:50:51,226 INFO [STDOUT] !!!!!!!!!! resolve shipper
11:50:51,227 INFO [STDOUT] None
11:50:51,227 INFO [STDOUT] !!!!!!!!!! set shipper
11:50:51,227 INFO [STDOUT] ship via FEDX
But if we modify the rule file to
package org.jbpm.action
import org.jbpm.resolveraction.Customer;
import org.jbpm.resolveraction.Order;
import org.jbpm.context.exe.ContextInstance;
global java.lang.String shipper
rule "Determine Shipper"
when
eval ("None".equals(shipper))
Customer( region >= 1 )
Order( totalAmount >= 0 )
then
System.out.println(shipper);
drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
System.out.println("ship via FEDX " );
end
then nothing is printed - no attempt to resolve shipper global variable
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months