OK, I finally fixed it...
After I found an Issue (SCB2336) that dealt with the same problem I gave
it a try and restarted Scarab (I was not very happy with that because its
on a production system with lots of other web apps, and as everybody knows
shit happens, especially on evenings before holidays ;-) ). However the
restart obviously forced the application to grab the correct value from
the SCARAB_GLOBAL_PARAMETER table and also use it in the URLs.
I still wonder what caused the build not to write the port number to the
upgrade SQL script. I'm 100% sure that we configured the
"scarab.http.port" property correctly before running the build.
Torsten
> We had a similar problem after the upgrade, but ended up just modifying
> our Apache configuration to forward the URLs to the proper port:
>
> # Scarab requests on 80 should go to 8080
> RewriteRule ^/scarab/issues/(.*)$ http://ourserver:8080/scarab/issues/$1
> [L]
>
> Not the best solution, but time was of the essence.
>
> Brett
>
> On 3/20/2008 5:40 AM, [email protected] wrote:
>> Hi All,
>>
>> we are facing a problem with URLs in issue change notification emails.
>> After we upgraded an installation from b19 to b20 the URLs do not
>> contain
>> the http port anymore.
>>
>> Before:
>> http://scarab.host.lan:48080/scarab/issues/id/ABC123
>>
>> After:
>> http://scarab.host.lan/scarab/issues/id/ABC123
>>
>> We configured the "scarab.http.port" property at build time to be 48080,
>> and this value is also present in the current runtime config. After
>> poking
>> around a bit I found that a database table named SCARAB_GLOBAL_PARAMETER
>> also holds that value. However, in our current installation the value in
>> the table is "@SCARAB.HTTP.PORT@". When I manually changed this to 48080
>> the port wasn't included in the URL either. But I admit that I didn't
>> restart Scarab nor the Tomcat after I did that change.
>>
>> Btw. there exists a migration SQL that was created during the build that
>> wrote the "@SCARAB.HTTP.PORT@" to the table.
>>
>> Any suggestions on how to get that port back into the URL?
>>
>> Any help appreciated, regards
>> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.