IllegalArgumentException in SessionChannel Activate | OPC UA SDK for JavaProsys Forum

Please consider registering
guest

Forum

OPC UA SDK for Java
sp_ArrowRight

IllegalArgumentException in SessionChannel Activate

Topic RSS

IllegalArgumentException in SessionChannel Activate

July 6, 2018
3:43, EEST

Anusha

Member

Members

Forum Posts: 6

Member Since:
April 12, 2018

Offline

Hi,

One of the laptops always gives the following error while trying to connect to any OPC UA device.The same code works fine in other machines. Am not sure where I should start looking.

2018-07-05 21:47:56,725:INFO:Pool-1-SubtaskRunner-3:OpcUaClient:172.27.162.136: Initializing OPC UA Client…
2018-07-05 21:47:56,727:INFO:Pool-1-SubtaskRunner-3:OpcUaClient:172.27.162.136: Opc UA Settings: Discovery URL:[opc.tcp://172.27.162.136:4840], Timeout:[10000], Security Mode:[[http://opcfoundation.org/UA/SecurityPolicy#None,None]], User Identity Token Type:[Anonymous]
2018-07-05 21:47:58,968:DEBUG:Pool-1-SubtaskRunner-3:OpcUaDiscoveryHandler:172.27.162.136: ApplicationDescription: ApplicationDescription
ApplicationUri=urn:localhost:OPCFoundation:ServerTestTool
ProductUri=http://www.3s-software.com
ApplicationName=(en-Us) CODESYS_OPC_UA_Server
ApplicationType=ApplicationType
name=Server
ordinal=0
GatewayServerUri=
DiscoveryProfileUri=null
DiscoveryUrls=class java.lang.String[1]
[0]=opc.tcp://172.27.162.136:4840

2018-07-05 21:47:58,983:INFO:Pool-1-SubtaskRunner-3:OpcUaDiscoveryHandler:172.27.162.136: Complete endpoint url: opc.tcp://172.27.162.136:4840
2018-07-05 21:48:01,887:DEBUG:Pool-1-SubtaskRunner-3:OpcUaClient:172.27.162.136: Supported user identity tokens:[Anonymous]
2018-07-05 21:48:03,567:DEBUG:Pool-1-SubtaskRunner-3:OpcUaClient:172.27.162.136: Supported security modes:[[http://opcfoundation.org/UA/SecurityPolicy#None,None]]
2018-07-05 21:48:03,568:DEBUG:Pool-1-SubtaskRunner-3:OpcUaClient:172.27.162.136: INDOpcUaClient@LAKCHAND-M-K058 Session1
2018-07-05 21:48:06,114:ERROR:Pool-1-SubtaskRunner-3:OpcUaDiscoveryHandler:172.27.162.136:
java.lang.IllegalArgumentException: null arg
at org.opcfoundation.ua.application.SessionChannel.activate(SessionChannel.java:145)
at com.prosysopc.ua.client.UaClient.n(SourceFile:4534)
at com.prosysopc.ua.client.UaClient.connect(SourceFile:787)
at com.cisco.iot.nms.deviceprotocols.opcua.OpcUaClient.connect(OpcUaClient.java:162)

What could be the reason for this exception? Would it be because of any firewall/network issues?

July 6, 2018
13:28, EEST

Bjarne Boström

Moderator

Moderators

Forum Posts: 1026

Member Since:
April 3, 2012

Offline

Hi,

If it is a connectivity issue, then you should get a proper Exception from the UaClient.connect method instead of something like this.

Can you test with the SampleConsoleClient sample from the SDK package as-is to see if it happens with that (if not, then you can check differences to your application). If it happens even with that, please set log to DEBUG for both the SDK and Stack parts and mail the file (will be very big, zip helps) to uajava-support@prosysopc.com.

Also you did not mention SDK version, check again with 3.1.4 unless you had that already.

Technically the exception would mean that either the underlying securechannel is null or the given token for the activate was null. Both should be somewhat impossible under normal conditions at least with the code paths 3.1.4 takes and you would get exception from the connect method (eventually) instead; which makes this case interesting.

All RSS

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 1919

Currently Online:
29 Guest(s)

Currently Browsing this Page:
1 Guest(s)