You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying recent Dataverse versions to Payara, I noticed the following error messages after server start, during the initial application deployment phase:
Unsupported deployment descriptors element message-destination value null
Looking around for similar problems on the internet, I found some old mailing list entries on these log messages regarding JMS.
(First Google results, e. g. 1).
After some investigation, it looks like using the @Resource(name="") syntax is not the best way to go. Sth. about referencing JNDI resources not physically located due to the new mechanism. Whatever - didn't dig deeper to understand every detail.
Looks like changing @Resource(name="") to @Resource(lookup="") might do the trick, but there is manual testing of Ingest needed.
PR forthcoming.
The text was updated successfully, but these errors were encountered:
As we produce the JMS topic and factory for Ingest in
`IngestQueueProducer` since Dataverse 5.3, error messages
about unsupported missing message-destination appeared.
This commit fixes the underlying cause by using lookup()
instead of name() for the @resource dependency injection.
Solves IQSS#7612
A silly question perhaps, but was that error message on startup the only negative effect of this? Or was it actually causing any real problems? (Ingest is still working in 5.3, as far as we know...)
As far as I can tell, yes, that was the only effect. But as there were a lot of 'em (20-30) and IIRC as warning, I did not want to generate confusion and potential issues for the future...
When deploying recent Dataverse versions to Payara, I noticed the following error messages after server start, during the initial application deployment phase:
Looking around for similar problems on the internet, I found some old mailing list entries on these log messages regarding JMS.
(First Google results, e. g. 1).
After some investigation, it looks like using the
@Resource(name="")
syntax is not the best way to go. Sth. about referencing JNDI resources not physically located due to the new mechanism. Whatever - didn't dig deeper to understand every detail.Looks like changing
@Resource(name="")
to@Resource(lookup="")
might do the trick, but there is manual testing of Ingest needed.PR forthcoming.
The text was updated successfully, but these errors were encountered: