[jboss-jira] [JBoss JIRA] Commented: (JBAS-8453) InvokerLocator for default EJB Connector being formed incorrectly with IPv6 bind address

Richard Achmatowicz (JIRA) jira-events at lists.jboss.org
Wed Dec 1 18:04:04 EST 2010


    [ https://jira.jboss.org/browse/JBAS-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566701#comment-12566701 ] 

Richard Achmatowicz commented on JBAS-8453:
-------------------------------------------

A fix for this issue has been implemented and used in IPv6 testing of AS 6 on a separate branch. It remians only for AS 6 trunk to be patched.

The fix simply uses the SBM to provide the correct URL as follows:
Need to replace:
<value-factory bean="ServiceBindingManager" method="getStringBinding">
   <parameter> jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3</parameter>
   <parameter><null /></parameter>
   <parameter>socket://${jboss.bind.address}:${port}?timeout=300000</parameter>
   <parameter><null /></parameter>
   <parameter>3873</parameter>
 </value-factory>
with:
<value-factory bean="ServiceBindingManager" method="getStringBinding">
   <parameter> jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3</parameter>
   <parameter><null /></parameter>
   <parameter>socket://${hostforurl}:${port}?timeout=300000</parameter>
   <parameter><null /></parameter>
   <parameter>3873</parameter>
 </value-factory> 
 Problem is that the file deploy/ejb3-connectors-jboss-beans.xml which contains this text is copied in from an EJB3 project jar, jboss-ejb3-core.jar..

Made the change by adding the following line:
<replace file="target/resources/ejb3-connectors-jboss-beans.xml" token="jboss.bind.address" value="hostforurl"/>
to the maven-antrun-plugin goal in the file ejb3/src/pom.xml. This goal installs EJB3 in the AS 6 distribution.


> InvokerLocator for default EJB Connector being formed incorrectly with IPv6 bind address
> ----------------------------------------------------------------------------------------
>
>                 Key: JBAS-8453
>                 URL: https://jira.jboss.org/browse/JBAS-8453
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Integration
>    Affects Versions: 6.0.0.M4
>            Reporter: Richard Achmatowicz
>            Assignee: Scott Marlow
>             Fix For: TBD-6.x
>
>
> When starting the AS with an IPv6 bind address, the following WARN log entry is seen on the console:
> 17:04:10,765 INFO  [SnmpAgentService] SNMP agent going active
> 17:04:10,783 ERROR [TrapEmitter] SNMP send error for localhost/127.0.0.1:1162: <java.security.InvalidParameterException: Buffer overflow error converting IP address>
> 17:04:11,030 WARN  [InvokerLocator] Host resolves to null in socket://3ffe:ffff:100:f101::1:3873?timeout=300000. Perhaps the host contains an invalid character.  See http://www.ietf.org/rfc/rfc2396.txt.
> 17:04:11,465 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> THis is due to the InvokerLocator for the MBean 
> jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
> being incorrectlly formed by substitution of the bind address into the URL template in the file deploy/ejb3-connection-jboss-beans.xml
> socket://${jboss.bind.address}:${port}?timeout=300000
> In order to create a well-formed URL, this needs to check for the case when the bind address is an IPv6 literal, and add brackets accordingly.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list