[JBoss JIRA] Created: (JBCACHE-998) Plain Cache tutorial example broken
by Rajesh Rajasekaran (JIRA)
Plain Cache tutorial example broken
-----------------------------------
Key: JBCACHE-998
URL: http://jira.jboss.com/jira/browse/JBCACHE-998
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Rajesh Rajasekaran
Assigned To: Manik Surtani
Fix For: 2.0.0.BETA2
bsh % sourceRelative("plain.bsh");
<org.jboss.cache.transaction.DummyTransactionManager@1fe4169>
<{}>
<null>
<org.jboss.cache.transaction.DummyUserTransaction@eb7331>
// Error: // Uncaught Exception: Method Invocation this.interpreter.source : at Line: 19 : in file: /bsh/commands/sourceRelative.bsh : this .interpreter .source ( path , this .caller .namespace )
Called from method: sourceRelative : at Line: 1 : in file: <unknown file> : sourceRelative ( "plain.bsh" )
Target exception: Sourced file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0.0.BETA1\JBossCache-all-2.0.0.BETA1\plain.bsh : Typed variable declaration : Attempt to resolve method: createCache() on undefined variable or class name: DefaultCacheFactory : at Line: 25 : in file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0.0.BETA1\JBossCache-all-2.0.0.BETA1\plain.bsh : DefaultCacheFactory .createCache ( "META-INF/replSync-service.xml" )
--
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
19 years, 2 months
[JBoss JIRA] Commented: (JBAS-4183) Failed to update attributes through JMX console
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4183?page=comments#action_12355187 ]
Scott M Stark commented on JBAS-4183:
-------------------------------------
Another way to produce a similar failure is to deploy a SystemPropertiesService mbean:
<mbean code="org.jboss.varia.property.SystemPropertiesService"
name="jboss:type=Service,name=SystemProperties,hi="howdy",this=that" />
and then perform an op like querying whether the user.home property exists. This produces a failure like:
javax.servlet.ServletException: Failed to invoke operation
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:269)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.management.MalformedObjectNameException: Unterminated key property part
javax.management.ObjectName.construct(ObjectName.java:465)
javax.management.ObjectName.<init>(ObjectName.java:1304)
org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:215)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Failed to update attributes through JMX console
> -----------------------------------------------
>
> Key: JBAS-4183
> URL: http://jira.jboss.com/jira/browse/JBAS-4183
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, Management services
> Environment: JBoss 4.0.1sp1, Java 1.5.0_04, Linux
> Reporter: Leon van Zantvoort
> Assigned To: Scott M Stark
> Priority: Minor
>
> It seems that it is not possible to make updates (set attributes) through the JMX webconsole when the MBean name contains quoted property values:
> tradenet.container:type=deployment,component="ev-selector"
> If the quotes - that wrap ev-selector - are removed, it all works fine. Otherwise, see below:
> 13:13:32,580 ERROR [Engine] StandardWrapperValve[HtmlAdaptor]: Servlet.service() for servlet HtmlAdaptor threw exception
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:465)
> at javax.management.ObjectName.<init>(ObjectName.java:1304)
> at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:150)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:215)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:77)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:595)
--
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
19 years, 2 months
[JBoss JIRA] Moved: (JBAS-4183) Failed to update attributes through JMX console
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4183?page=all ]
Scott M Stark moved JBADMCON-126 to JBAS-4183:
----------------------------------------------
Project: JBoss Application Server (was: JBoss Admin Console)
Key: JBAS-4183 (was: JBADMCON-126)
Component/s: JMX
Management services
(was: General Console)
Security: Public
> Failed to update attributes through JMX console
> -----------------------------------------------
>
> Key: JBAS-4183
> URL: http://jira.jboss.com/jira/browse/JBAS-4183
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, Management services
> Environment: JBoss 4.0.1sp1, Java 1.5.0_04, Linux
> Reporter: Leon van Zantvoort
> Assigned To: Scott M Stark
> Priority: Minor
>
> It seems that it is not possible to make updates (set attributes) through the JMX webconsole when the MBean name contains quoted property values:
> tradenet.container:type=deployment,component="ev-selector"
> If the quotes - that wrap ev-selector - are removed, it all works fine. Otherwise, see below:
> 13:13:32,580 ERROR [Engine] StandardWrapperValve[HtmlAdaptor]: Servlet.service() for servlet HtmlAdaptor threw exception
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:465)
> at javax.management.ObjectName.<init>(ObjectName.java:1304)
> at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:150)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:215)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:77)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:595)
--
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
19 years, 2 months
[JBoss JIRA] Assigned: (JBADMCON-126) Failed to update attributes through JMX console
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBADMCON-126?page=all ]
Scott M Stark reassigned JBADMCON-126:
--------------------------------------
Assignee: Scott M Stark
> Failed to update attributes through JMX console
> -----------------------------------------------
>
> Key: JBADMCON-126
> URL: http://jira.jboss.com/jira/browse/JBADMCON-126
> Project: JBoss Admin Console
> Issue Type: Bug
> Components: JMX, Management services
> Environment: JBoss 4.0.1sp1, Java 1.5.0_04, Linux
> Reporter: Leon van Zantvoort
> Assigned To: Scott M Stark
> Priority: Minor
>
> It seems that it is not possible to make updates (set attributes) through the JMX webconsole when the MBean name contains quoted property values:
> tradenet.container:type=deployment,component="ev-selector"
> If the quotes - that wrap ev-selector - are removed, it all works fine. Otherwise, see below:
> 13:13:32,580 ERROR [Engine] StandardWrapperValve[HtmlAdaptor]: Servlet.service() for servlet HtmlAdaptor threw exception
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:465)
> at javax.management.ObjectName.<init>(ObjectName.java:1304)
> at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:150)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:215)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:77)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:595)
--
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
19 years, 2 months
[JBoss JIRA] Commented: (JBPM-395) SwimlaneInstance PooledActor assignment bug (not re-assignment issue)
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-395?page=comments#action_12355157 ]
Ronald van Kuijk commented on JBPM-395:
---------------------------------------
still an issue for 3.1?
3.0.x issues of this type will not be fixed anymore. Please confirm whether it still is an issue with 3.1
> SwimlaneInstance PooledActor assignment bug (not re-assignment issue)
> ---------------------------------------------------------------------
>
> Key: JBPM-395
> URL: http://jira.jboss.com/jira/browse/JBPM-395
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.0.1
> Environment: JDK 1.5, Postgresql, JBoss 4.0.2
> Reporter: Britt Miner
> Assigned To: Tom Baeyens
>
> Initializing swimlaneInstances at process creation (or perhaps any time prior to creation of an associated task) will persist any configured actorId to the database, but configured PooledActors are not persisted. The AssignmentHandler functionality seems to work fine--the newly initialized swimlaneInstance has both actorId and pooledActors set correctly; however, the pooledActors will not be persisted. Allowing the swimlaneInstance to be initialized at creation of a related task does result in both actorId and pooledActors being properly persisted.
> This issue is similar, though not identical, to http://jira.jboss.com/jira/browse/JBPM-375 and http://jira.jboss.com/jira/browse/JBPM-378 which are both related to swimlane assignment issues.
> Why initialize swimlaneInstances at process creation? So that swimlane assignments can be made based on the initiator of the process (responsibilities broken down by regional groups, etc.), and so that those assignments are available for reporting/forcasting purposes.
> This is the code fragment used to initialize the swimlanes:
> ...
> Map swimlanes = processDefinition.getTaskMgmtDefinition().getSwimlanes();
> Iterator itr = swimlanes.keySet().iterator();
> while(itr.hasNext()) {
> Swimlane swimlane = (Swimlane)swimlanes.get(itr.next());
> SwimlaneInstance swi = pi.getTaskMgmtInstance().getInitializedSwimlaneInstance(new Execution
> Context(pi.getRootToken()), swimlane);
> //at this point, swi contains both actors and PooledActors that were specified in configuration and
> populated with an appropriate AssignmentHandler
> }
> graphSession.saveProcessInstance(pi);
> jbpmSession.commitTransaction();
> Thanks,
> Britt
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBAS-4181) If -b 0.0.0.0 is used, do not pass wildcard addresss through to JGroups
by Brian Stansberry (JIRA)
If -b 0.0.0.0 is used, do not pass wildcard addresss through to JGroups
-----------------------------------------------------------------------
Key: JBAS-4181
URL: http://jira.jboss.com/jira/browse/JBAS-4181
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA
If JGroups tries to bind to 0.0.0.0 you get nasty effects like:
11:00:42,765 ERROR [UDP] failed sending message to 0.0.0.0:2902 (0 bytes)
java.net.BindException: Cannot assign requested address: Datagram send failed
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:612)
at org.jgroups.protocols.UDP._send(UDP.java:338)
at org.jgroups.protocols.UDP.sendToSingleMember(UDP.java:299)
at org.jgroups.protocols.TP.doSend(TP.java:940)
at org.jgroups.protocols.TP.send(TP.java:926)
at org.jgroups.protocols.TP.down(TP.java:712)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517)
at org.jgroups.stack.Protocol.passDown(Protocol.java:551)
at org.jgroups.protocols.Discovery.up(Discovery.java:246)
at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
at org.jgroups.stack.Protocol.passUp(Protocol.java:538)
at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
at org.jgroups.protocols.TP.access$400(TP.java:45)
at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
at java.lang.Thread.run(Thread.java:595)
11:00:42,796 WARN [NAKACK] 0.0.0.0:4627] discarded message from non-member 0.0.
0.0:2898, my view is [0.0.0.0:4627|0] [0.0.0.0:4627]
Fix is in org.jboss.Main to pass the -b value through ServerConfigUtil.fixRemoteAddress(), which will return pick a non-wildcard address via InetAddress.getLocalHost().getHostName().
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBAS-3537) Add a startup switch to configure a multicast port
by Brian Stansberry (JIRA)
Add a startup switch to configure a multicast port
--------------------------------------------------
Key: JBAS-3537
URL: http://jira.jboss.com/jira/browse/JBAS-3537
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Proper cluster isolation with UDP requires use of a different cluster name, different multicast address and different multicast port. (See http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic for why the latter is important.)
The -g and -u switches allow easy configuration of the cluster name and multicast address. But, configuring the port that way wasn't practical, as an AS instance may have many different JChannels.
With the JGroups multiplexer, a switch is a possibility, as by default there will only be one JChannel per server instance. (If a user wanted to use more than one JChannel, they would need to manually configure the second one to use a different port.)
--
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
19 years, 2 months