-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grabbit AEM components are in 'unsatisfied' state after service restart #215
Comments
Trying out grabbit I'm seeing similar problems to @lakshmin. The grabbit packages/ bundles/ components are all Ok when installed to a 'fresh' aem instance. The problem arises when the grabbit packages are installed after our custom aem components code is already installed 😒. So presumably there is some contention with service dependencies (all bundles show as active)? Any pointers or help much appreciated! AEM 6.3 with service pack 6.3.1 Sun-Misc-Fragment-Bundle-1.0.0.zip system/console/components shows,
When the client tries to kick off a copy from the source to the (local) target, target (client) server logs,
|
Hi,
After installing Grabbit and restarting the AEM6.3 instance, following components goes in to 'unsatisfied' state. Please find below the service names which are in 'unsatisfied' state. We are able to consistently reproduce the issue. Since the components are in 'unsatisfied' state, servlets are not working and not able to submit content migration job.
http://localhost:4502/system/console/components
com.twcable.grabbit.client.batch.workflows.impl.DefaultWorkFlowManager active
com.twcable.grabbit.client.services.impl.DefaultClientService unsatisfied (reference)
com.twcable.grabbit.client.servlets.GrabbitJobServlet unsatisfied (reference)
com.twcable.grabbit.client.servlets.GrabbitRootServlet active
com.twcable.grabbit.client.servlets.GrabbitTransactionServlet unsatisfied (reference) com.twcable.grabbit.resources.GrabbitResourceProvider active
com.twcable.grabbit.server.GrabbitContentPullServlet unsatisfied (reference)
com.twcable.grabbit.server.services.impl.DefaultServerService unsatisfied (reference)
com.twcable.grabbit.spring.batch.repository.services.impl.DefaultCleanJobRepository unsatisfied (reference)
com.twcable.grabbit.spring.batch.repository.servlets.GrabbitCleanJobRepositoryServlet unsatisfied (reference)
Reference configurableApplicationContext Unsatisfied
Service Name: org.springframework.context.ConfigurableApplicationContext
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
Reference clientService Unsatisfied
Service Name: com.twcable.grabbit.client.services.ClientService
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
Reference configurableApplicationContext Unsatisfied
Service Name: org.springframework.context.ConfigurableApplicationContext
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
Reference serverService Unsatisfied
Service Name: com.twcable.grabbit.server.services.ServerService
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
Reference configurableApplicationContext Unsatisfied
Service Name: org.springframework.context.ConfigurableApplicationContext
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
Reference cleanJobRepository Unsatisfied
Service Name: com.twcable.grabbit.spring.batch.repository.services.CleanJobRepository
Cardinality: 1..1
Policy: static
Policy Option: reluctant
No Services bound
What version of AEM are you running?
AEM 6.3
How do you produce the issue?
Install Grabbit, it installs fine and after restarting the AEM 6.3 isntance, above mentioned components goes in to 'unsatisfied' state. If I uninstall the Grabbit 7.5 and reinstall it work, but the issue happens again after restarting AEM6.3 service.
Does the issue occur consistently?
Yes
Any additional details?
Packages installed -
Sun-Misc-Fragment-Bundle-1.0.0.zip
Grabbit-Deserialization-Firewall-Configuration-1.0.zip
Grabbit-Apache-Sling-Login-Whitelist-1.0.zip
Grabbit-7.1.5.zip
Thanks!
The text was updated successfully, but these errors were encountered: