Hello friends,
I have a new installation from OVA, all the setup process went just fine, but now when I go to the option Mailing Lists and click on create a new one, I got an error message after saving it:
" Sorry, something went wrong
Se ha producido un error grave. Por favor, póngase en contacto con nuestro equipo de asistencia."
If I go to the link suggested it shows nothing http://www.openemm.org/systemstoerung
Despite of this error message, when I go again to Mailing Lists I can see my created list and I can use it later to send mailing with success, but of course is not right to have this error at creation of list. Other thing is that when I click on the created mailing list I got this error, similar to the other:
"500 An error has occurred.
Sorry, something went wrong
Se ha producido un error grave. Por favor, póngase en contacto con nuestro equipo de asistencia."
At log level I found this lines suspicious in /home/openemm/tomcat9/logs/catalina.out:
com.agnitas.emm.ORIGIN_URI: /mailinglist/11/view.action;jsessionid=985A17F86920A10A2E246E4E3311FBDB
javax.servlet.error.message: Request processing failed; nested exception is java.lang.IllegalArgumentException: [mailing.test.com.pe/birt/run] is not a valid HTTP URL
javax.servlet.error.servlet_name: spring-mvc
org.springframework.web.servlet.DispatcherServlet.THEME_SOURCE: WebApplicationContext for namespace 'spring-mvc-servlet': startup date [Wed Apr 01 15:14:31 PET 2020]; parent: Root WebApplicationContext
org.springframework.web.servlet.DispatcherServlet.INPUT_FLASH_MAP: FlashMap [attributes={org.apache.struts.action.ERROR={}, org.apache.struts.action.ACTION_MESSAGE={org.apache.struts.action.GLOBAL_MESSAGE=[default.changes_saved[]]}}, targetRequestPath=/mailinglist/11/view.action, targetRequestParams={}]
org.springframework.web.context.request.RequestContextListener.REQUEST_ATTRIBUTES: org.apache.catalina.connector.RequestFacade@7643dd78
org.springframework.web.servlet.HandlerMapping.pathWithinHandlerMapping: /mailinglist/11/view.action
org.springframework.web.servlet.HandlerMapping.uriTemplateVariables: {id=11}
javax.servlet.error.request_uri: /mailinglist/11/view.action;jsessionid=985A17F86920A10A2E246E4E3311FBDB
org.springframework.web.servlet.DispatcherServlet.THEME_RESOLVER: org.springframework.web.servlet.theme.FixedThemeResolver@4782bf5f
javax.servlet.error.exception: java.lang.IllegalArgumentException: [mailing.test.com.pe/birt/run] is not a valid HTTP URL
java.lang.IllegalArgumentException: [mailing.test.com.pe/birt/run] is not a valid HTTP URL
at org.springframework.web.util.UriComponentsBuilder.fromHttpUrl(UriComponentsBuilder.java:270)
Any help would be very appreaciated
Regards!
Error when creating a new mailing list
Moderator: moderator
-
- Posts: 5
- Joined: Wed Apr 01, 2020 11:01 pm
-
- Posts: 5
- Joined: Wed Apr 01, 2020 11:01 pm
Re: Error when creating a new mailing list
Hi,
I finally could solve this issue, as this was my first attempt to the OVA I haven't payed attention to this:
http://<your FQDN>
in every option under Configuration menu where asks for the url the "http://" this must be present. I have only set the FQDN part and that is why it wasn't creating lists correctly, as that line on the log file pointed out:
javax.servlet.error.message: Request processing failed; nested exception is java.lang.IllegalArgumentException: [mailing.test.com.pe/birt/run] is not a valid HTTP URL
After adding explicitly "http://" to the FQDN in Configuration settings this issue was solved.
I finally could solve this issue, as this was my first attempt to the OVA I haven't payed attention to this:
http://<your FQDN>
in every option under Configuration menu where asks for the url the "http://" this must be present. I have only set the FQDN part and that is why it wasn't creating lists correctly, as that line on the log file pointed out:
javax.servlet.error.message: Request processing failed; nested exception is java.lang.IllegalArgumentException: [mailing.test.com.pe/birt/run] is not a valid HTTP URL
After adding explicitly "http://" to the FQDN in Configuration settings this issue was solved.