search

masimbac / myschedule

Automatically exported from code.google.com/p/myschedule
0 stars 0 forks source link

Fail to deploy 3.0.0_q21-SNAPSHOT #116

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Unzip myschedule-3.0.0_q21-SNAPSHOT.zip
2. Copy war to \jboss-as-7.1.1.Final\standalone\deployments

Error stacktrace:
00:23:54 INFO  [SchedulerSettingsStore] Loading scheduler settings from 
file=C:\Users\Magic\.myschedule3\scheduler-configs\3d8f0b0b-d233-47cc-9476-b0b82
c735795.properties
00:23:54 ERROR [StandardContext] Exception sending context initialized event to 
listener instance of class myschedule.web.MyScheduleContextListener: 
java.lang.RuntimeException: Failed to read scheduler settings 
file={}C:\Users\Magic\.myschedule3\scheduler-configs\3d8f0b0b-d233-47cc-9476-b0b
82c735795.properties
        at myschedule.web.SchedulerSettingsStore.get(SchedulerSettingsStore.java:92) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.SchedulerSettingsStore.getAll(SchedulerSettingsStore.java:100) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.MySchedule.initSchedulerSettingsMap(MySchedule.java:126) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.MySchedule.initService(MySchedule.java:55) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.AbstractService.init(AbstractService.java:19) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.MySchedule.getInstance(MySchedule.java:43) [myschedule-web-config-3.0.0_q21-SNAPSHOT.jar:]
        at myschedule.web.MyScheduleContextListener.contextInitialized(MyScheduleContextListener.java:19) [classes:]
        at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
        at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]

BTW, I previous deploy 2.4.4 in same JBoss but I remove it and ensure that 
C:\Users\Magic\myschedule2\configs is empty
BTW2, 
C:\Users\Magic\.myschedule3\scheduler-configs\3d8f0b0b-d233-47cc-9476-b0b82c7357
95.properties is existed!

Original issue reported on code.google.com by magicboo on 13 May 2013 at 4:36

GoogleCodeExporter commented 9 years ago 
Additional information:

My JBoss is in D: and it goto D: to find config files (and ERROR!)

00:56:11 INFO  [SchedulerSettingsStore] Creating scheduler settings store 
dir=C:\Users\Magic\.myschedule3\scheduler-configs.
00:56:11 INFO  [TemplatesStore] Creating template store 
dir=C:\Users\Magic\.myschedule3\templates\scheduler-configs.
00:56:11 INFO  [TemplatesStore] Creating template store 
dir=C:\Users\Magic\.myschedule3\templates\scripts.
00:56:11 WARN  [TemplatesStore] Default template file resource 
name=/myschedule/web/templates/scripts/jobSamples.groovynot found.
00:56:11 INFO  [MySchedule] Adding a new default scheduler settings.
00:56:11 INFO  [SchedulerSettingsStore] Adding new scheduler settings 
file=C:\Users\Magic\.myschedule3\scheduler-configs\0906ec0b-742c-499d-b270-981d5
1c494cd.properties
00:56:11 ERROR [StandardContext] Exception sending context initialized event to 
listener instance of class myschedule.web.MyScheduleContextListener: 
java.lang.IllegalArgumentException: Failed to open 
c:\Users\Magic\.myschedule3\scheduler-configs\0906ec0b-742c-499d-b270-981d51c494
cd.properties

......

Caused by: java.io.FileNotFoundException: 
D:\Users\Magic\.myschedule3\scheduler-configs\0906ec0b-742c-499d-b270-981d51c4
94cd.properties (系統找不到指定的路徑。)
        at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_05]
        at java.io.FileInputStream.<init>(FileInputStream.java:138) [rt.jar:1.7.0_05]
        at java.io.FileInputStream.<init>(FileInputStream.java:97) [rt.jar:1.7.0_05]
        at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) [rt.jar:1.7.0_05]
        at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) [rt.jar:1.7.0_05]
        at java.net.URL.openStream(URL.java:1035) [rt.jar:1.7.0_05]
        at myschedule.quartz.extra.util.Props.load(Props.java:134) [myschedule-quartz-extra-3.0.0_q21-SNAPSHOT.jar:]
        ... 18 more

Original comment by magicboo on 13 May 2013 at 5:01

GoogleCodeExporter commented 9 years ago 
When I move my JBoss to C:, the deploy is OK!

Original comment by magicboo on 13 May 2013 at 5:12

GoogleCodeExporter commented 9 years ago 
Hum... the data store directory is configurable and default to your 
$HOME/.myscheudle3. So even if you have "D:/" drive, your $HOME (%USERPROFILE%) 
probably still using "C:" thefore it will look into there. 

You can override by using 
-Dmyschedule.web.dataStoreDir=/path/to/your/.myschedule3

Original comment by saltnlight5 on 14 May 2013 at 1:51

GoogleCodeExporter commented 9 years ago 
"SchedulerSettingsStore" create the store @ C:
But from my log, "myschedule.quartz.extra.util.Props.load" find log in D:

It's weird!

Original comment by magicboo on 14 May 2013 at 1:09

GoogleCodeExporter commented 9 years ago 
Okay, thanks for reporting. I will check it out and update this ticket.

Original comment by saltnlight5 on 19 May 2013 at 1:16

GoogleCodeExporter commented 9 years ago 
I can not reproduce this. I would assume that you have some odd setup with your 
USER HOME directory in your system. As I mentioned, if that's the case, then 
use explicit Java system property key to specify the location should be fine.

Unless you can help me write down a clear steps on how to reproduce, I would 
have to close the issue as invalid.

Original comment by saltnlight5 on 8 Jun 2013 at 3:41

GoogleCodeExporter commented 9 years ago 
Close as non-reproducible.

Original comment by saltnlight5 on 11 Jun 2013 at 10:39

GoogleCodeExporter commented 9 years ago 
I finally able to reproduce this bug now. It happens when running in Windows OS 
on secondary drive due to we faile to handle local file with URL loading. It's 
now fixed in rev 0a071bdffdef.

Sorry for the delay. :)

Original comment by saltnlight5 on 30 Jul 2014 at 8:06

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 0a071bdffdef.

Original comment by saltnlight5 on 30 Jul 2014 at 8:07