1 Reply Latest reply on Dec 16, 2004 10:26 AM by Weixin Wang

    Migrating from WebSphere to JBoss...

    Monica Bing Newbie


      I am trying to migrate an ear file from Websphere to Jboss. I have already installed the foe-deployer and the ear into the correct directory. However, at the start of the server there is a warning that an entity is not registered and then a complaint that the webservice cannot be started.

      Can someone please reply with instructions on how to deploy a non-Jboss application onto the server? I think I need to set some bindings but I have not located any documentation that would let me know what to do.

      Please help!

        • 1. java.net.SocketException: The message is larger than the max
          Weixin Wang Newbie

          Hi all,

          I am running two machines in the partition; JBoss 3.2.4 on Windows XP SP2, Java SDK 1.4.2_05. Using the un-modified cluster-service.xml.

          Left it running over the weekend, and saw this error when I came back. (The log is from MACHINE_B, modified for easier viewing)

          2004-09-29 10:06:16,203 DEBUG [org.jgroups.protocols.UNICAST] [MACHINE_B:1057 (additional data: 19 bytes)] --> XMIT(MACHINE_B:4460 (additional data: 19 bytes): #126)
          2004-09-29 10:06:16,203 DEBUG [org.jgroups.Message] header for "UDP" is already present: old header=[UDP:group_addr=DefaultPartition], new header=[UDP:group_addr=DefaultPartition]
          2004-09-29 10:06:16,218 DEBUG [org.jgroups.protocols.UDP] sending message to MACHINE_B:4460 (additional data: 19 bytes) (src=MACHINE_B:1057 (additional data: 19 bytes)), headers are {UNICAST=[UNICAST: DATA, seqno=126], GMS=GmsHeader[JOIN_RSP]: join_rsp=view: [MACHINE_B:1057 (additional data: 19 bytes)|1022] [MACHINE_B:1057 (additional data: 19 bytes), MACHINE_A:2920 (additional data: 19 bytes), MACHINE_B:2429 (additional data: 19 bytes), MACHINE_B:2431 (additional data: 19 bytes),
           ###SIMILAR PATTERN 500 TIMES###
          MACHINE_B:4458 (additional data: 19 bytes), MACHINE_B:4460 (additional data: 19 bytes)], digest: [MACHINE_B:1057 (additional data: 19 bytes): [0 : 1054, MACHINE_A:2920 (additional data: 19 bytes): [0 : 35, MACHINE_B:2429 (additional data: 19 bytes): [0 : 0, MACHINE_B:2431 (additional data: 19 bytes): [0 : 0, MACHINE_B:2433 (additional data: 19 bytes): [0 : 0, MACHINE_B:2435 (additional data: 19 bytes): [0 : 0, MACHINE_B:2437 (additional data: 19 bytes):
           ###SIMILAR PATTERN 500 TIMES###
          MACHINE_B:4456 (additional data: 19 bytes): [0 : 0, MACHINE_B:4458 (additional data: 19 bytes): [0 : 0, MACHINE_B:4460 (additional data: 19 bytes): [0 : 0, MACHINE_B:4460 (additional data: 19 bytes): [0 : 0]
          , UDP=[UDP:group_addr=DefaultPartition]}
          2004-09-29 10:06:16,234 ERROR [org.jgroups.protocols.UDP] exception=java.net.SocketException: The message is larger than the maximum supported by the underlying transport: Datagram send failed, msg=[dst: MACHINE_B:4460 (additional data: 19 bytes), src: MACHINE_B:1057 (additional data: 19 bytes) (3 headers), size = 0 bytes], mcast_addr=

          Is this a known issue? What's going on with the 3rd message?