2 Replies Latest reply on Jul 13, 2015 1:54 PM by arnab_ghosh

" Failed to read GIOP message" in Server log

arnab_ghosh Jul 13, 2015 12:00 PM

Hi All,

I am seeing the below error's in server log if the server keeps running for considerable time:

on closed

2015-07-13 02:46:39,745 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36332 (4b2f74c0), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,749 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:34409 (1d3e15ae), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,752 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36333 (335d6062), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,756 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36334 (1d0374c3), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,759 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36335 (2d3a8ad7), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,763 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36336 (404469bb), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,766 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:37037 (18424fa1), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,769 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36337 (1ee18506), incorrect magic number --> connecti

on closed

2015-07-13 02:46:39,774 ERROR [jacorb.giop.conn] (ServerMessageReceptor0) Failed to read GIOP message in ServerGIOPConnection to 145.228.145.74:36338 (67f4d83f), incorrect magic number --> connecti

on closed

I don't see any any failures at run time of the deployed app. Any idea ?

Regards

Arnab

1. Re: " Failed to read GIOP message" in Server log

tomekadamski Jul 13, 2015 1:08 PM (in response to arnab_ghosh)

Hi Arnab,
Can you please describe your scenario in more detail? How is the client that connects to the server configured? Also, can you please change org.jacorb logger level in standalone-full.xml configuration file to DEBUG, run server and paste the stacktrace?

Tomek
Actions
2. Re: " Failed to read GIOP message" in Server log

arnab_ghosh Jul 13, 2015 1:54 PM (in response to tomekadamski)

Tomasz,

I have a wildfly instance on which my queues are deployed and then this server is deployed with app which contains MDB's which listen to those remote queues Below are my configurations:

        <outbound-socket-binding name="queue-server-socket">
            <remote-destination host="server1.server.arvato-systems.de" port="15455"/>
        </outbound-socket-binding>

<netty-connector name="netty-remote-queue-server-connector" socket-binding="queue-server-socket"/>

                    <pooled-connection-factory name="pooled-remote-connection-factory">
                        <transaction mode="xa"/>
                        <connectors>
                            <connector-ref connector-name="netty-remote--queue-server-connector"/>
                        </connectors>
                        <entries>
                            <entry name="java:/RemoteJmsXA"/>
                        </entries>
                    </pooled-connection-factory>

I will also increase the log level and paste the logs

Regards
Arnab
Actions

Go to original post