#91 joc-420 java.lang.IllegalArgumentException jobschedulerId

[Pierrick PAUL]

Hello,

jobscheduler 1.11 RC5 Linux

I'm trying JOC and i have this message :

joc-420
java.lang.IllegalArgumentException

I get the following error,

hope you can help,

kind regards,

2017-02-23 10:55:25,403 INFO qtp1490180672-19 c.s.j.c.JocCockpitProperties - Resolved path of log4j.properties = /home/jobs/sos-berlin.com/joc/resources/joc/log4j.properties
2017-02-23 10:55:25,409 INFO qtp1490180672-19 c.s.j.Globals - HTTP(S) connection timeout = 2
2017-02-23 10:55:25,409 INFO qtp1490180672-19 c.s.j.Globals - HTTP(S) socket timeout = 2
2017-02-23 10:55:25,409 INFO qtp1490180672-19 c.s.j.Globals - HTTPS with hostname verification in certicate = false
2017-02-23 10:55:25,409 INFO qtp1490180672-19 c.s.j.Globals - force comments for audit log = false
2017-02-23 10:55:25,431 INFO qtp1490180672-19 JOCAuditLog - REQUEST: ./login - USER: root - PARAMS: {} - COMMENT: all - TIMESPENT: - - TICKET: -
2017-02-23 10:55:25,469 INFO qtp1490180672-13 c.s.j.c.JOCDefaultResponse -
REQUEST: ./configuration
PARAMS: {"jobschedulerId":"","account":"root","configurationType":"PROFILE","shared":false}
USER: root
2017-02-23 10:55:25,470 ERROR qtp1490180672-13 c.s.j.c.JOCDefaultResponse - JocMissingRequiredParameterException: undefined 'jobschedulerId'
com.sos.joc.exceptions.JocMissingRequiredParameterException: undefined 'jobschedulerId'
at com.sos.joc.classes.JOCResourceImpl.checkRequiredParameter(JOCResourceImpl.java:153)
at com.sos.joc.configuration.impl.JocConfigurationResourceImpl.init(JocConfigurationResourceImpl.java:51)
at com.sos.joc.configuration.impl.JocConfigurationResourceImpl.postReadConfiguration(JocConfigurationResourceImpl.java:144)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2017-02-23 10:55:25,739 INFO qtp1490180672-18 c.s.j.c.JOCDefaultResponse -
REQUEST: ./configuration
PARAMS: {"jobschedulerId":"","account":"root","configurationType":"SETTING","shared":false}
USER: root
2017-02-23 10:55:25,739 ERROR qtp1490180672-18 c.s.j.c.JOCDefaultResponse - JocMissingRequiredParameterException: undefined 'jobschedulerId'
com.sos.joc.exceptions.JocMissingRequiredParameterException: undefined 'jobschedulerId'
at com.sos.joc.classes.JOCResourceImpl.checkRequiredParameter(JOCResourceImpl.java:153)
at com.sos.joc.configuration.impl.JocConfigurationResourceImpl.init(JocConfigurationResourceImpl.java:51)
at com.sos.joc.configuration.impl.JocConfigurationResourceImpl.postReadConfiguration(JocConfigurationResourceImpl.java:144)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2017-02-23 10:55:25,786 INFO qtp1490180672-14 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:25,786 ERROR qtp1490180672-14 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:25,802 INFO qtp1490180672-19 c.s.j.c.JOCDefaultResponse -
REQUEST: ./jobscheduler/agent_clusters
PARAMS: {"jobschedulerId":"","agentClusters":[],"compact":false,"folders":[]}
USER: root
2017-02-23 10:55:25,802 ERROR qtp1490180672-19 c.s.j.c.JOCDefaultResponse - java.lang.NullPointerException
java.lang.NullPointerException
at com.sos.joc.classes.JOCResourceImpl.getUrl(JOCResourceImpl.java:199)
at com.sos.joc.classes.JOCJsonCommand.setUriBuilderForProcessClasses(JOCJsonCommand.java:85)
at com.sos.joc.jobscheduler.impl.JobSchedulerResourceAgentClustersImpl.postJobschedulerAgentClusters(JobSchedulerResourceAgentClustersImpl.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2017-02-23 10:55:25,807 INFO qtp1490180672-19 c.s.j.c.JOCDefaultResponse -
REQUEST: ./orders/overview/snapshot
PARAMS: {"jobschedulerId":"","jobChains":[],"compact":false,"folders":[],"states":[],"close":false}
USER: root
2017-02-23 10:55:25,807 ERROR qtp1490180672-19 c.s.j.c.JOCDefaultResponse - java.lang.NullPointerException
java.lang.NullPointerException
at com.sos.joc.classes.JOCResourceImpl.getUrl(JOCResourceImpl.java:199)
at com.sos.joc.classes.JOCJsonCommand.setUriBuilderForOrders(JOCJsonCommand.java:69)
at com.sos.joc.classes.orders.Orders.getSnapshot(Orders.java:34)
at com.sos.joc.classes.orders.Orders.getSnapshot(Orders.java:30)
at com.sos.joc.orders.impl.OrdersResourceOverviewSnapshotImpl.postOrdersOverviewSnapshot(OrdersResourceOverviewSnapshotImpl.java:28)
2017-02-23 10:55:25,809 INFO qtp1490180672-15 c.s.j.c.JOCDefaultResponse -
REQUEST: ./process_classes
PARAMS: {"jobschedulerId":"","processClasses":[],"folders":[],"isAgentCluster":true}
USER: root
2017-02-23 10:55:25,809 ERROR qtp1490180672-15 c.s.j.c.JOCDefaultResponse - java.lang.NullPointerException
java.lang.NullPointerException
at com.sos.joc.classes.JOCResourceImpl.getUrl(JOCResourceImpl.java:199)
at com.sos.joc.classes.JOCJsonCommand.setUriBuilderForProcessClasses(JOCJsonCommand.java:85)
at com.sos.joc.processClasses.impl.ProcessClassesResourceImpl.postProcessClasses(ProcessClassesResourceImpl.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2017-02-23 10:55:25,831 INFO qtp1490180672-19 c.s.j.c.JOCDefaultResponse -
REQUEST: ./jobscheduler/db
PARAMS: {"jobschedulerId":""}
USER: root
2017-02-23 10:55:25,831 ERROR qtp1490180672-19 c.s.j.c.JOCDefaultResponse - java.lang.NullPointerException
java.lang.NullPointerException
at com.sos.joc.jobscheduler.impl.JobSchedulerResourceDbImpl.postJobschedulerDb(JobSchedulerResourceDbImpl.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
2017-02-23 10:55:27,832 INFO qtp1490180672-15 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:27,832 ERROR qtp1490180672-15 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:29,846 INFO qtp1490180672-18 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:29,846 ERROR qtp1490180672-18 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:31,859 INFO qtp1490180672-16 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:31,859 ERROR qtp1490180672-16 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:33,872 INFO qtp1490180672-14 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:33,872 ERROR qtp1490180672-14 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:35,885 INFO qtp1490180672-10 c.s.j.c.JOCDefaultResponse -
REQUEST: ./events
PARAMS: {"jobscheduler":[],"close":false}
USER: root
2017-02-23 10:55:35,885 ERROR qtp1490180672-10 c.s.j.c.JOCDefaultResponse - java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307)
at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:89)
at com.sos.joc.event.impl.EventResourceImpl.postEvent(EventResourceImpl.java:130)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
2017-02-23 10:55:37,813 INFO qtp1490180672-19 JOCAuditLog - REQUEST: ./logout - USER: root - PARAMS: {} - COMMENT: - TIMESPENT: - - TICKET: -</init></init></init></init></init></init></init></init></init></init></init></init>

[SOSMP]

Hi Paul,

Thank you for reporting the bug.

Please check

1. if your JobScheduler did started at least once after installation. Since JobScheduler write its own information in the database table INVENTROY_INSTANCES and JOC Cockpit read it. Also Make sure the INVENTORY_INSTANCES table has the entry for your JobScheduler.
2. The JobScheduler reporting and JOC Cockpit should use the same database schema, since database is the primary interface between JobScheduler and JOC Cockpit to exchange permanent information.

Please let me know if above analysis help.

Regards
SOSMP

[Pierrick PAUL]

HI,

if your JobScheduler did started at least once after installation : --> yes

Since JobScheduler write its own information in the database table INVENTROY_INSTANCES and JOC Cockpit read it : --> The mysql user's used by jobscheduler can write on INVENTORY_INSTANCES, the user for jobscheduler and joc is the same. but the table is empty.

The JobScheduler reporting and JOC Cockpit should use the same database schema : -- > yes, is the same database schema.

Regards
Paul

[SOSMP]

Hello Paul,

Can you please check if, in your JobScheduler's SCHDULER_DATA/config/scheduler.xml file, following plugin is listed
<plugin java_class="com.sos.jitl.inventory.plugins.InitializeInventoryInstancePlugin"/>

Also do send us your SCHEDULER_DATA/logs/scheduler.log file for furthur analysis.

Best regards
SOSMP

[Pierrick PAUL]

HI,

Can you please check if, in your JobScheduler's SCHDULER_DATA/config/scheduler.xml file, following plugin is listed <plugin java_class="com.sos.jitl.inventory.plugins.InitializeInventoryInstancePlugin"> </plugin>

--> yes this plugin is listed.

SCHEDULER_DATA/logs/scheduler.log

.23 12:41:39.621 1 22208.9D9ED740
.23 12:41:39.621 0 22208.9D9ED740 ----------------------Thu Feb 23 12:41:39 2017
.23 12:41:39.621 0 22208.9D9ED740 Aufruf: /data/jobscheduler/scheduler/bin/scheduler -service -id=scheduler -sos.ini=/data/jobscheduler/scheduler/config/sos.ini -ini=/data/jobscheduler/scheduler/config/factory.ini -config=/data/jobscheduler/scheduler/config/scheduler.xml -param=/data/jobscheduler/scheduler -cd=/data/jobscheduler/scheduler -include-path=/data/jobscheduler/scheduler -pid-file=/data/jobscheduler/scheduler/logs/scheduler.pid -env=LD_LIBRARY_PATH= // log=/data/jobscheduler/scheduler/logs/scheduler.log
.23 12:41:39.621 0 22208.9D9ED740 host=LI-ORD-VXXX, user=jobs, pid=22208
.23 12:41:39.621 0 22208.9D9ED740 sys=Linux node=LI-ORD-VXXX release=3.10.0-327.el7.x86_64 version=#1 SMP Thu Nov 19 22:10:57 UTC 2015 machine=x86_64
.23 12:41:39.621 0 22208.9D9ED740 Compiler GNU gcc 4.8.5, Feb 17 2017, 64bit
.23 12:41:39.621 0 22208.9D9ED740 get_temp_path() => /tmp/jobs
.23 12:41:39.621 0 22208.9D9ED740 working directory = /data/jobscheduler/scheduler
.23 12:41:39.621 0 22208.9D9ED740 Modul
.23 12:41:39.621 0 22208.9D9ED740 Programm
.23 12:41:39.621 0 22208.9D9ED740
.23 12:41:39.621 0 22208.9D9ED740 Hostware 1.6.131.
.23 12:41:39.621 0 22208.9D9ED740 {scheduler} File /data/jobscheduler/scheduler/logs/scheduler.log moved to /data/jobscheduler/scheduler/logs/scheduler-old.log
.23 12:41:39.621 0 22208.9D9ED740 {scheduler} JobScheduler engine 1.11.0-RC5
.23 12:41:39.621 0 22208.9D9ED740 {scheduler} JobScheduler becomes daemon, and process ID changes
.23 12:41:39.621 0 22208.9D9ED740 {scheduler} fork()
.23 12:41:39.621 0 22209.9D9ED740 {scheduler} pid=22209
.23 12:41:39.621 0 22209.9D9ED740 {scheduler} setsid()
.23 12:41:39.621 0 22209.9D9ED740 sos.ini=/data/jobscheduler/scheduler/config/sos.ini
.23 12:41:39.622 1 22209.9D9ED740 [xc.insert "Datei file:/data/jobscheduler/scheduler/config/sos.ini"]
.23 12:41:39.622 0 22209.9D9ED740 [xc.insert "Datei file:/data/jobscheduler/scheduler/config/sos.ini"]
.23 12:41:39.622 0 22209.9D9ED740 [xc.insert "Datei file:/data/jobscheduler/scheduler/config/sos.ini"]
.23 12:41:39.622 0 22209.9D9ED740 (Letzte Zeile wiederholt sich 2 mal)
.23 12:41:39.622 0 22209.9D9ED740 {scheduler} LD_LIBRARY_PATH=

regards
Paul

[SOSMP]

Hi,

Can you please share complete SCHEDULER_DATA/logs/scheduler.log file, if its too big please zip it and attache here.

Regards
SOSMP

[Pierrick PAUL]

Hi,

Regards
Paul

[SOSMP]

Hi Paul,

You have ran into an old error. By default the hibernet.cfg.xml files are validated againest an online schema www.hibernate.org. it seems you are behind a firewall or comupter do not have internet access. This is perfectly fine, since most of the production servers don't have internet access.

You have to just find all the hibernet-*.cfg.xml file under your SCHEDULER_DATA and JOC_DATA and remove the following line from the file.

<!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
                                         "http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">

once you delete the line, the hibernet.cfg.xml files will be validated againest an local DTD schema.

Also restart JobScheduler and JOC Cockpit services to make the settings effective.

Best regards
SOSMP

[Pierrick PAUL]

Hi
thank you, it run.

Best regards
Paul

[Andreas]

Hi Paul,

the issue about hibernate configuration files being validated against online resources is fixed with RC6. Such files are provided without reference to external DTDs and are validated against an internal schema, therefore no internet connection is required for validatiion.

Release Candidate 6 is available for download.

Best regards
Andreas

[mahathir]

Hi Andreas,

I installed RC6(joc.1.11.0-RC6) in linxu using joc_install.xml (sh setup.sh -u joc_install.xml) after installation I could see the UI and I am able to log in as root/root but I am getting "DBInvalidDataException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet" and also I am not able to get the scheduler.log .

Could you please help me to fix the issue. Also Importantly my db has no tables for scheudler (mysql)

Thanks In Advance

[Andreas]

Hi Mhathir,

please do not post new topics into existing threads that have been closed, use a new thread instead.

• First of all check that you installed both JobScheduler Master and the JOC Cockpit.
• Find the JOC Cockpit log from the file YYYY_MM_DD.stderrout.log in the ./logs subdirectory. In addition you will find the Install*.log from the same location.
• Find the JobScheduler Master log from the file scheduler.log in the ./scheduler_data/logs subdirectory where the Master is installed. The file Install*.log is available from the same location.

If the problem persists then please check the four log files for errors and attach the logs to your post.

Best regards
Andreas