The server has been restarted in the last few months also, so unsure as to how we haven't run into this before now, odd!įor reference, our setenv. however I just assumed the communication issues were isolated to communication with DEP, and not that Tomcat itself wouldn't start without the edit. It is located at: C:Program FilesJSSbinserver-tools-gui.jar Jamf Pro Server Tools also has a. Jamf Pro Server Tools is installed automatically when you run the Jamf Pro Installer. It also allows you to restart Apache Tomcat and MySQL and modify their settings. Very interesting, as that's the change I was about to make when I initially discovered this problem. Jamf Pro Server Tools allows you to back up and restore the Jamf Pro database. tab and configure basic settings for the package, including the display name and category. Double-click the package in the main repository. The package is displayed in blue text in the Unknown category until you add it to a category. Thank you both for your responses btw, hugely Thank you for this. Drag the package to the main repository in Jamf Admin. The JSS received an error (Error creating bean with name 'artifactVersionManager': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)) for a request made by device.ĮDIT: Also seeing a few instances of the following when the server starts: Error processing communication content - .BeanCreationNotAllowedException: Error creating bean with name 'runningServiceHelper': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!) Error deleting by computer_id for table installed_printers Poking through the JAMFSoftwareLog I can see the following from when I initiated the connection: I logged on to the JSS server (out of hours thankfully) and decided to snapshot and then restart it before making any changes, which is when I noticed the issue. The JSS & DB servers are currently up and running without any issue so the database config should be all fine (this hasn't changed in years), it just falls over on restart of Tomcat for some No changes were made to revert unfortunately. Checking the MySQL config, the database user has "ALL PRIVILEGES" set, so should be ok.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |