Activity
From 07/16/2023 to 08/14/2023
08/11/2023
- 10:50 AM Feature #7675: add missing runtime support for 4GL command line parameters
- Some of the 4GL command line parameters which we can specify (in either the directory or as a bootstrap config value)...
- 10:02 AM Feature #7675 (New): add missing runtime support for 4GL command line parameters
08/01/2023
- 09:28 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- Code Review Task Branch 7649a Revision 14680
No objection. - 09:27 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- > It will take effect if no mode is already selected for the JVM. The point of the mode will be to simply reroute the...
- 03:09 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- ops
- 03:08 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- This is fine.
If you find some interactive tools having inconsistent output in standalone, then we should do as I ... - 03:02 AM Bug #7649 (Review): logging level for ScanDriver's "Failure in file" must be sever to log the sta...
- Created task branch 7649a from trunk rev 14679.
The fix is in 7649a rev 14680. - 03:00 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- Galya B wrote:
> On trunk @Failure in file@ is:
>
> [...]
>
> But maybe you've already reworked it on another ... - 02:59 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- On trunk @Failure in file@ is:...
- 02:57 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- In this case (ScanDriver is used by conversion) FWD uses @CentralLoggerFallback@, which has a default logging level o...
- 02:56 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- An important side note: @Failure in file@ at the moment is not logged in any way way, it's simple System.out.println....
- 02:54 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- With standalone tools I was cautious to convert all @System.out@ prints to logs, because when these run in standalone...
- 02:44 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace
- There are two places in @ScanDriver@ where a @Failure in file@ parsing problem may be encountered - both these need t...
- 02:38 AM Bug #7649 (Closed): logging level for ScanDriver's "Failure in file" must be sever to log the sta...
07/25/2023
- 10:52 AM Bug #7635 (Test): RemoteObject defaults to 'tracing' mode
- I forgot.
Task branch 7635a was merged to trunk as rev 14671 and archived.
- 10:39 AM Bug #7635: RemoteObject defaults to 'tracing' mode
- You can merge to trunk.
- 10:39 AM Bug #7635: RemoteObject defaults to 'tracing' mode
- Code Review 7635a Revision 14669
The change is fine. The cost is 3 extra method calls (isLoggable() and inside th...
07/24/2023
- 08:21 AM Bug #7635 (Review): RemoteObject defaults to 'tracing' mode
- 7635a r14669 simply removing the flag should be good enough. There is already optimization and invalidation in the @C...
- 08:06 AM Bug #7635 (WIP): RemoteObject defaults to 'tracing' mode
- 08:03 AM Bug #7635: RemoteObject defaults to 'tracing' mode
- In @RemoteObject@, the @LOG@ instance gets created and @RemoteObject$RemoteAccess.tracing@ flag gets set before the l...
- 08:01 AM Bug #7635 (Closed): RemoteObject defaults to 'tracing' mode
07/20/2023
- 07:14 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- According to the logs customer's app uses the first implementation it finds, i.e. FWD's, that's why we see Spring try...
- 07:08 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- The customer's log has this:...
07/19/2023
- 10:53 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Roger, thanks for checking.
Galya: I've committed this diff from 7589a to 7156b for the customer. I'll let you kn... - 10:47 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Constantin Asofiei wrote:
> I know you've made edits to build.xml and build.gradle lately, if the change makes sense... - 10:44 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- When used in this "separate Tomcat JVM" scenario, we should to implement a @fwd-appserver-client.jar@ which only incl...
- 10:09 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Roger Borrello wrote:
> Constantin Asofiei wrote:
> > Roger, please take a look at 7589a.
>
> What should I take... - 10:08 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Constantin Asofiei wrote:
> Roger, please take a look at 7589a.
What should I take a look at? You mean with my cu... - 09:45 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Ops, I forgot @bzr add@ again, up in r14665.
- 09:43 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- I've done a @./gradlew all@ and it fails with this:...
- 09:41 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- I checked it, it's fine. This covers it:...
- 09:36 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Roger, please take a look at 7589a.
Galya, I think the jar needs to be added to this, too:... - 09:28 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- I'm not sure if the default slf4j impl that logs to stderr @slf4j-simple-2.0.7.jar@ will work with their setup. Anywa...
- 08:57 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Galya B wrote:
> Do you mean when FWD is used as library, there will be no FWD logs at all?
For FWD, the default is... - 08:55 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Constantin Asofiei wrote:
> Galya B wrote:
> > From FWD's 3rd party libraries.
> FWD can't be in charge of 3rd par... - 08:53 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Galya B wrote:
> From FWD's 3rd party libraries.
FWD can't be in charge of 3rd party libraries when is deployed in ... - 08:52 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Ask the customer to send the full exceptions, when their stress level is lower and they can manage the mouse to copy ...
- 08:51 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Constantin Asofiei wrote:
> Galya B wrote:
> > The real solution of this task is not separating slf4j and losing lo... - 08:50 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Galya B wrote:
> The real solution of this task is not separating slf4j and losing logs.
What do you mean by 'losin... - 08:47 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- When using framework as library inside a container there is a very high chance to get classpath problems. The real so...
- 08:39 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Galya B wrote:
> The problem is not Tomcat, but something with Spring picking up slf4j impl from the classpath.
Th... - 08:33 AM Bug #7589 (WIP): org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- The problem is not Tomcat, but something with Spring picking up slf4j impl from the classpath. Can you please share t...
- 08:28 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- No, the spring web app is running in its own JVM via tomcat - it is not running in the FWD server JVM.
The custome... - 08:16 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Usually when you decide to use a framework, logging is provided by the framework. Here we have Spring framework in FW...
- 07:59 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- Galya B wrote:
> How is their Spring logging configured, does it produce separate files?
I do not know these detail... - 07:37 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- How is their Spring logging configured, does it produce separate files?
- 07:35 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- The problem is not Tomcat, but Spring. I'm not sure how to reproduce it to be able to offer a smarter solution instea...
- 07:17 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
- A customer deploys p2j.jar in a tomcat web app. Having @org.slf4j.impl.StaticLoggerBinder@ defined results in proble...
- 07:14 AM Bug #7589 (Closed): org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat
07/18/2023
- 07:23 AM Bug #7425: Avoid directory usage in static blocks
- The order of the server bootstrap initialization was changed in *trunk/rev.14654* and the resources affected need to ...
Also available in: Atom