Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Atlassian JIRA by Jeff Thomas, 1 year ago
The value 'HD-17399 HC2 only - Crash was becuase of stale reference of unit object in the port object after maincard get deleted. This is only applicable to HC2 becuase of not having BCM on line cards.Solution was not to use the unit_obj reference
via Atlassian JIRA by Jeff Thomas, 1 year ago
The value 'HD-17399 HC2 only - Crash was becuase of stale reference of unit object in the port object after maincard get deleted. This is only applicable to HC2 becuase of not having BCM on line cards.Solution was not to use the unit_obj reference
via Atlassian JIRA by Kah Loun Foong [Atlassian], 1 year ago
The value 'testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest' for the property 'defaultSource' is too long. It should have a maximum length of 80
via Atlassian JIRA by Kah Loun Foong [Atlassian], 2 years ago
The value 'testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest' for the property 'defaultSource' is too long. It should have a maximum length of 80
java.lang.IllegalArgumentException: The value 'HD-17399 HC2 only - Crash was becuase of stale reference of unit object in the port object after maincard get deleted. This is only applicable to HC2 becuase of not having BCM on line cards.Solution was not to use the unit_obj reference in port object, rather use the mainboard's unit_obj. read comment section' for the property 'name' is too long. It should have a maximum length of 255	at com.cenqua.crucible.hibernate.PropertyLengthCheckerListener.checkEntity(PropertyLengthCheckerListener.java:25)