Bug 1133537 - Issues with file replacement and path too long errors on extracting jdr zip file
Summary: Issues with file replacement and path too long errors on extracting jdr zip file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: JON3-41
TreeView+ depends on / blocked
 
Reported: 2014-08-25 12:10 UTC by Sunil Kondkar
Modified: 2015-03-27 11:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-25 13:30:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot_issue1.png (34.75 KB, image/png)
2014-08-25 12:11 UTC, Sunil Kondkar
no flags Details
screenshot1_Windows-PathTooLongError (34.50 KB, image/png)
2014-08-25 12:12 UTC, Sunil Kondkar
no flags Details
screenshot2_Windows-PathTooLongError (34.77 KB, image/png)
2014-08-25 12:13 UTC, Sunil Kondkar
no flags Details
screenshot3_Windows-PathTooLongError (35.81 KB, image/png)
2014-08-25 12:13 UTC, Sunil Kondkar
no flags Details
screenshot4_Windows-PathTooLongError (35.66 KB, image/png)
2014-08-25 12:14 UTC, Sunil Kondkar
no flags Details

Description Sunil Kondkar 2014-08-25 12:10:26 UTC
Description of problem:

The operation 'Generate JDR Report' on JDR resource, creates a JDR zip file at the <Jboss ON Server>\jbossas\standalone\tmp\ folder. When extracting the JDR zip file, observed below issues:


Issue 1 : While extracting the jdr zip file on linux, it asks for replacing some files in 'standalone-full_xml_history' folder as below:

[root@dhcp201-174 tmp]# unzip jdr_14-08-25_02-49-40_dhcp201-174.zip

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history/20140820-144016630? [y]es, [n]o, [A]ll, [N]one, [r]ename: 

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history/20140821-171635651? [y]es, [n]o, [A]ll, [N]one, [r]ename:

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history? [y]es, [n]o, [A]ll, [N]one, [r]ename: 

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/tmp/jdr_14-08-22_06-56-56_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history/20140820-144016630? [y]es, [n]o, [A]ll, [N]one, [r]ename:

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/tmp/jdr_14-08-22_06-56-56_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history/20140821-171635651? [y]es, [n]o, [A]ll, [N]one, [r]ename:

replace jdr_14-08-25_02-49-40_dhcp201-174/JBOSS_HOME/standalone/tmp/jdr_14-08-22_06-56-56_dhcp201-174/JBOSS_HOME/standalone/configuration/standalone-full_xml_history? [y]es, [n]o, [A]ll, [N]one, [r]ename:

The same issue on Windows:

Please refer screenshot_issue1.png for the same.

---------------------------------------------------

Issue 2 :

On Windows, whiles extracting the JDR zip file on default location, it displays path too long errors.
Ex Path : C:\jon33ER01\jon-server-3.3.0.ER01\jbossas\standalone\tmp\jdr_14-08-25_04-07-34_win-8embulm9lu7

Please refer the attached screenshots for path too long errors.

Note: If the file is extracted on another location, ex: on C:\ , it does not display path too long errors.



Version-Release number of selected component (if applicable):

Version : 3.3.0.ER01 Build Number : 23b3476:f3aa7e7
Windows: Windows server 2008
Linux: RHEL6

How reproducible:

Always

Steps to Reproduce:

1. Schedule 'Generate JDR report' operation on RHQ server->Subsystem->JDR resource.

2. Navigate to the location of JDR report zip file.

3. Unzip the JDR report zip file on the default location.
( Ex: C:\jon33ER01\jon-server-3.3.0.ER01\jbossas\standalone\tmp)

Actual results:

1. Asks for file replacement for some files in 'standalone-full_xml_history' folder on Linux and Windows.
2. path too long errors on extracting jdr zip file on Windows.


Expected results:

No errors on extracting JDR report zip file

Additional info:

Comment 1 Sunil Kondkar 2014-08-25 12:11:09 UTC
Created attachment 930444 [details]
screenshot_issue1.png

Comment 2 Sunil Kondkar 2014-08-25 12:12:37 UTC
Created attachment 930445 [details]
screenshot1_Windows-PathTooLongError

Comment 3 Sunil Kondkar 2014-08-25 12:13:15 UTC
Created attachment 930446 [details]
screenshot2_Windows-PathTooLongError

Comment 4 Sunil Kondkar 2014-08-25 12:13:44 UTC
Created attachment 930447 [details]
screenshot3_Windows-PathTooLongError

Comment 5 Sunil Kondkar 2014-08-25 12:14:13 UTC
Created attachment 930448 [details]
screenshot4_Windows-PathTooLongError

Comment 6 Heiko W. Rupp 2014-08-25 13:26:31 UTC
Those are both issues from the underlying JBoss EAP jdr report and nothing that JON/RHQ can fix.
In fact those JDR reports are not meant to be extracted from a user inside the JON-server directory, but are supposed to be sent to support to extract and analyze them.

I think this issue can be closed as either WONT_FIX or WORKS_AS_DESIGNED.

Comment 7 andrewpo 2015-03-27 11:57:31 UTC
I got the same message recently and installed "Long Path Tool" program which solved the problem.


Note You need to log in before you can comment on or make changes to this bug.