From: Laura H. <l....@fz...> - 2023-06-06 11:20:04
|
Dear Krzysztof, Dear Roman, we were just about to install unity 3.13.0 and then start testing. To do this, we first switched from unity 3.11.2 to unity 3.12.0, then to 3.13.0. After that, we received an application error message when logging in (see attached screenshot). Unfortunately we could not find any error message in the stack trace, so we switched back to 3.12.0. There we got the same error message at login, but then we could also find an error message in the stack trace. This is also attached as a txt file. Best regards, Laura Hofer -- Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany E-Mail: l....@fz... Phone: +49 2461 61-6576 Fax: +49 2461 61-6656 ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2023-06-06 12:54:35
|
Dear Laura, W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > Dear Krzysztof, Dear Roman, > > we were just about to install unity 3.13.0 and then start testing. To > do this, we first switched from unity 3.11.2 to unity 3.12.0, then to > 3.13.0. After that, we received an application error message when > logging in (see attached screenshot). Unfortunately we could not find > any error message in the stack trace, so we switched back to 3.12.0. > There we got the same error message at login, but then we could also > find an error message in the stack trace. This is also attached as a > txt file. Thank you for the report. Most likely a regression caused by one of recent big refactorings. Some questions: 1. The DB on which you run 3.12 (and got the attached stacktrace) was used (and possible modified) with 3.13 or not? 2. If the answer to above is positive: can you restart your test scenario (i.e. start from 3.11, upgrade to 3.12) and test on 3.12 whether the issue is also present on that version? Answers to those questions should help us a lot. Thank you, Krzysztof |
From: Sander A. <sa....@fz...> - 2023-06-07 09:57:18
Attachments:
smime.p7s
|
Dear Krzysztof, On Tue, 2023-06-06 at 14:54 +0200, Krzysztof Benedyczak wrote: > Dear Laura, > > W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > > Dear Krzysztof, Dear Roman, > > > > we were just about to install unity 3.13.0 and then start testing. > > To > > do this, we first switched from unity 3.11.2 to unity 3.12.0, then > > to > > 3.13.0. After that, we received an application error message when > > logging in (see attached screenshot). Unfortunately we could not > > find > > any error message in the stack trace, so we switched back to > > 3.12.0. > > There we got the same error message at login, but then we could > > also > > find an error message in the stack trace. This is also attached as > > a > > txt file. > > > Thank you for the report. Most likely a regression caused by one of > recent big refactorings. > > Some questions: > > 1. The DB on which you run 3.12 (and got the attached stacktrace) was > used (and possible modified) with 3.13 or not? Yes the database was used also on 3.13. It looks like there was no modification on 3.13 start up, but I'm not sure > > 2. If the answer to above is positive: can you restart your test > scenario (i.e. start from 3.11, upgrade to 3.12) and test on 3.12 > whether the issue is also present on that version? Sadly we did not made a database backup before. By starting 3.11.2 unity throws an error about the supported database version: The database schema version 18 is newer then supported by this version of the server. Please upgrade the server software. Best regards, Sander > > Answers to those questions should help us a lot. > > Thank you, > > Krzysztof > > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2023-06-07 11:17:14
|
Hi Sander, W dniu 7.06.2023 o 11:57, Sander Apweiler pisze: > Dear Krzysztof, > > On Tue, 2023-06-06 at 14:54 +0200, Krzysztof Benedyczak wrote: >> Dear Laura, >> >> W dniu 6.06.2023 o 13:19, Laura Hofer pisze: >>> Dear Krzysztof, Dear Roman, >>> >>> we were just about to install unity 3.13.0 and then start testing. >>> To >>> do this, we first switched from unity 3.11.2 to unity 3.12.0, then >>> to >>> 3.13.0. After that, we received an application error message when >>> logging in (see attached screenshot). Unfortunately we could not >>> find >>> any error message in the stack trace, so we switched back to >>> 3.12.0. >>> There we got the same error message at login, but then we could >>> also >>> find an error message in the stack trace. This is also attached as >>> a >>> txt file. >> >> Thank you for the report. Most likely a regression caused by one of >> recent big refactorings. >> >> Some questions: >> >> 1. The DB on which you run 3.12 (and got the attached stacktrace) was >> used (and possible modified) with 3.13 or not? > Yes the database was used also on 3.13. It looks like there was no > modification on 3.13 start up, but I'm not sure >> 2. If the answer to above is positive: can you restart your test >> scenario (i.e. start from 3.11, upgrade to 3.12) and test on 3.12 >> whether the issue is also present on that version? > Sadly we did not made a database backup before. By starting 3.11.2 > unity throws an error about the supported database version: > OK, we will try to find it on our side then, will take more time in such situation though. Will keep you posted. Best, Krzysztof |
From: Krzysztof B. <kb...@un...> - 2023-06-08 08:16:54
|
Dear Laura, Sander, W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > Dear Krzysztof, Dear Roman, > > we were just about to install unity 3.13.0 and then start testing. To > do this, we first switched from unity 3.11.2 to unity 3.12.0, then to > 3.13.0. After that, we received an application error message when > logging in (see attached screenshot). Unfortunately we could not find > any error message in the stack trace, so we switched back to 3.12.0. > There we got the same error message at login, but then we could also > find an error message in the stack trace. This is also attached as a > txt file. So we have found the problem in 3.12 causing your error. We can fix it, no problem, however I don't think it makes a lot of sense: it is a minor bug, which will only occur on a database which was run on 3.13, and then used in 3.12. This problem on 3.12 is also for sure 100% not related to the (serious) sign-in problem you observed on 3.13. That said, to investigate the real issue we need to get back to 3.13, and diagnose the problem in there. In case of error like in your screenshot, you should rather get a stacktrace or at least ERROR message in log. It is possible we have some omission in logging, but unlikely. Can you please first enable debug logging, then repeat your failing sign-in on 3.13 and inspect log files one more time (or share it with us)? We need to find some clues on what is failing. Without access to your database it will be the only way forward. Best, Krzysztof |
From: Sander A. <sa....@fz...> - 2023-06-12 08:35:27
Attachments:
smime.p7s
|
Dear Krzysztof, we will bring the information as soon as possible. Best regards, Sander On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: > Dear Laura, Sander, > > W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > > Dear Krzysztof, Dear Roman, > > > > we were just about to install unity 3.13.0 and then start testing. > > To > > do this, we first switched from unity 3.11.2 to unity 3.12.0, then > > to > > 3.13.0. After that, we received an application error message when > > logging in (see attached screenshot). Unfortunately we could not > > find > > any error message in the stack trace, so we switched back to > > 3.12.0. > > There we got the same error message at login, but then we could > > also > > find an error message in the stack trace. This is also attached as > > a > > txt file. > > So we have found the problem in 3.12 causing your error. We can fix > it, > no problem, however I don't think it makes a lot of sense: it is a > minor > bug, which will only occur on a database which was run on 3.13, and > then > used in 3.12. This problem on 3.12 is also for sure 100% not related > to > the (serious) sign-in problem you observed on 3.13. > > That said, to investigate the real issue we need to get back to 3.13, > and diagnose the problem in there. In case of error like in your > screenshot, you should rather get a stacktrace or at least ERROR > message > in log. It is possible we have some omission in logging, but > unlikely. > > Can you please first enable debug logging, then repeat your failing > sign-in on 3.13 and inspect log files one more time (or share it with > us)? We need to find some clues on what is failing. Without access to > your database it will be the only way forward. > > Best, > Krzysztof > > -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Roman K. <ro...@un...> - 2023-06-19 09:41:07
|
Dear Sander, Are there any news with regards to additional information? Thank you, Roman pon., 12 cze 2023 o 10:35 Sander Apweiler <sa....@fz...> napisał(a): > Dear Krzysztof, > we will bring the information as soon as possible. > > Best regards, > Sander > > On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: > > Dear Laura, Sander, > > > > W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > > > Dear Krzysztof, Dear Roman, > > > > > > we were just about to install unity 3.13.0 and then start testing. > > > To > > > do this, we first switched from unity 3.11.2 to unity 3.12.0, then > > > to > > > 3.13.0. After that, we received an application error message when > > > logging in (see attached screenshot). Unfortunately we could not > > > find > > > any error message in the stack trace, so we switched back to > > > 3.12.0. > > > There we got the same error message at login, but then we could > > > also > > > find an error message in the stack trace. This is also attached as > > > a > > > txt file. > > > > So we have found the problem in 3.12 causing your error. We can fix > > it, > > no problem, however I don't think it makes a lot of sense: it is a > > minor > > bug, which will only occur on a database which was run on 3.13, and > > then > > used in 3.12. This problem on 3.12 is also for sure 100% not related > > to > > the (serious) sign-in problem you observed on 3.13. > > > > That said, to investigate the real issue we need to get back to 3.13, > > and diagnose the problem in there. In case of error like in your > > screenshot, you should rather get a stacktrace or at least ERROR > > message > > in log. It is possible we have some omission in logging, but > > unlikely. > > > > Can you please first enable debug logging, then repeat your failing > > sign-in on 3.13 and inspect log files one more time (or share it with > > us)? We need to find some clues on what is failing. Without access to > > your database it will be the only way forward. > > > > Best, > > Krzysztof > > > > > > -- > Federated Systems and Data > Juelich Supercomputing Centre > > phone: +49 2461 61 8847 > fax: +49 2461 61 6656 > email: sa....@fz... > > ----------------------------------------------------------------------- > ----------------------------------------------------------------------- > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Stefan Müller > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, > Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior > ----------------------------------------------------------------------- > ----------------------------------------------------------------------- > > > > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss > |
From: Sander A. <sa....@fz...> - 2023-06-19 09:46:56
Attachments:
smime.p7s
|
Dear Roman, not yet since we are quite busy with preparing a summerschool. Maybe later next week. Best regards, Sander On Mon, 2023-06-19 at 11:40 +0200, Roman Krysiński wrote: > Dear Sander, > > Are there any news with regards to additional information? > > Thank you, > Roman > > > pon., 12 cze 2023 o 10:35 Sander Apweiler <sa....@fz...> > napisał(a): > > Dear Krzysztof, > > we will bring the information as soon as possible. > > > > Best regards, > > Sander > > > > On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: > > > Dear Laura, Sander, > > > > > > W dniu 6.06.2023 o 13:19, Laura Hofer pisze: > > > > Dear Krzysztof, Dear Roman, > > > > > > > > we were just about to install unity 3.13.0 and then start > > > > testing. > > > > To > > > > do this, we first switched from unity 3.11.2 to unity 3.12.0, > > > > then > > > > to > > > > 3.13.0. After that, we received an application error message > > > > when > > > > logging in (see attached screenshot). Unfortunately we could > > > > not > > > > find > > > > any error message in the stack trace, so we switched back to > > > > 3.12.0. > > > > There we got the same error message at login, but then we could > > > > also > > > > find an error message in the stack trace. This is also attached > > > > as > > > > a > > > > txt file. > > > > > > So we have found the problem in 3.12 causing your error. We can > > > fix > > > it, > > > no problem, however I don't think it makes a lot of sense: it is > > > a > > > minor > > > bug, which will only occur on a database which was run on 3.13, > > > and > > > then > > > used in 3.12. This problem on 3.12 is also for sure 100% not > > > related > > > to > > > the (serious) sign-in problem you observed on 3.13. > > > > > > That said, to investigate the real issue we need to get back to > > > 3.13, > > > and diagnose the problem in there. In case of error like in your > > > screenshot, you should rather get a stacktrace or at least ERROR > > > message > > > in log. It is possible we have some omission in logging, but > > > unlikely. > > > > > > Can you please first enable debug logging, then repeat your > > > failing > > > sign-in on 3.13 and inspect log files one more time (or share it > > > with > > > us)? We need to find some clues on what is failing. Without > > > access to > > > your database it will be the only way forward. > > > > > > Best, > > > Krzysztof > > > > > > > > -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2023-07-26 11:16:07
|
Hi Sander, Are there any updates on the below topic? We have some nice performance improvements prepared, that should help with your perf-problems, but I'd prefer to release them only after investigating this issue, which sounds critical. Best, Krzysztof W dniu 19.06.2023 o 11:46, Sander Apweiler pisze: > Dear Roman, > not yet since we are quite busy with preparing a summerschool. Maybe > later next week. > > Best regards, > Sander > > On Mon, 2023-06-19 at 11:40 +0200, Roman Krysiński wrote: >> Dear Sander, >> >> Are there any news with regards to additional information? >> >> Thank you, >> Roman >> >> >> pon., 12 cze 2023 o 10:35 Sander Apweiler <sa....@fz...> >> napisał(a): >>> Dear Krzysztof, >>> we will bring the information as soon as possible. >>> >>> Best regards, >>> Sander >>> >>> On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: >>>> Dear Laura, Sander, >>>> >>>> W dniu 6.06.2023 o 13:19, Laura Hofer pisze: >>>>> Dear Krzysztof, Dear Roman, >>>>> >>>>> we were just about to install unity 3.13.0 and then start >>>>> testing. >>>>> To >>>>> do this, we first switched from unity 3.11.2 to unity 3.12.0, >>>>> then >>>>> to >>>>> 3.13.0. After that, we received an application error message >>>>> when >>>>> logging in (see attached screenshot). Unfortunately we could >>>>> not >>>>> find >>>>> any error message in the stack trace, so we switched back to >>>>> 3.12.0. >>>>> There we got the same error message at login, but then we could >>>>> also >>>>> find an error message in the stack trace. This is also attached >>>>> as >>>>> a >>>>> txt file. >>>> So we have found the problem in 3.12 causing your error. We can >>>> fix >>>> it, >>>> no problem, however I don't think it makes a lot of sense: it is >>>> a >>>> minor >>>> bug, which will only occur on a database which was run on 3.13, >>>> and >>>> then >>>> used in 3.12. This problem on 3.12 is also for sure 100% not >>>> related >>>> to >>>> the (serious) sign-in problem you observed on 3.13. >>>> >>>> That said, to investigate the real issue we need to get back to >>>> 3.13, >>>> and diagnose the problem in there. In case of error like in your >>>> screenshot, you should rather get a stacktrace or at least ERROR >>>> message >>>> in log. It is possible we have some omission in logging, but >>>> unlikely. >>>> >>>> Can you please first enable debug logging, then repeat your >>>> failing >>>> sign-in on 3.13 and inspect log files one more time (or share it >>>> with >>>> us)? We need to find some clues on what is failing. Without >>>> access to >>>> your database it will be the only way forward. >>>> >>>> Best, >>>> Krzysztof >>>> >>>> |
From: Laura H. <l....@fz...> - 2023-07-26 11:18:01
Attachments:
smime.p7s
|
Hi Krzysztof, we wanted to recreate the error, but it seems to be working now. The application error does not appear anymore. Best regards, Laura Am 26.07.23 um 13:15 schrieb Krzysztof Benedyczak: > Hi Sander, > > Are there any updates on the below topic? > > We have some nice performance improvements prepared, that should help > with your perf-problems, but I'd prefer > to release them only after investigating this issue, which sounds > critical. > > Best, > Krzysztof > > W dniu 19.06.2023 o 11:46, Sander Apweiler pisze: >> Dear Roman, >> not yet since we are quite busy with preparing a summerschool. Maybe >> later next week. >> >> Best regards, >> Sander >> >> On Mon, 2023-06-19 at 11:40 +0200, Roman Krysiński wrote: >>> Dear Sander, >>> >>> Are there any news with regards to additional information? >>> >>> Thank you, >>> Roman >>> >>> >>> pon., 12 cze 2023 o 10:35 Sander Apweiler <sa....@fz...> >>> napisał(a): >>>> Dear Krzysztof, >>>> we will bring the information as soon as possible. >>>> >>>> Best regards, >>>> Sander >>>> >>>> On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: >>>>> Dear Laura, Sander, >>>>> >>>>> W dniu 6.06.2023 o 13:19, Laura Hofer pisze: >>>>>> Dear Krzysztof, Dear Roman, >>>>>> >>>>>> we were just about to install unity 3.13.0 and then start >>>>>> testing. >>>>>> To >>>>>> do this, we first switched from unity 3.11.2 to unity 3.12.0, >>>>>> then >>>>>> to >>>>>> 3.13.0. After that, we received an application error message >>>>>> when >>>>>> logging in (see attached screenshot). Unfortunately we could >>>>>> not >>>>>> find >>>>>> any error message in the stack trace, so we switched back to >>>>>> 3.12.0. >>>>>> There we got the same error message at login, but then we could >>>>>> also >>>>>> find an error message in the stack trace. This is also attached >>>>>> as >>>>>> a >>>>>> txt file. >>>>> So we have found the problem in 3.12 causing your error. We can >>>>> fix >>>>> it, >>>>> no problem, however I don't think it makes a lot of sense: it is >>>>> a >>>>> minor >>>>> bug, which will only occur on a database which was run on 3.13, >>>>> and >>>>> then >>>>> used in 3.12. This problem on 3.12 is also for sure 100% not >>>>> related >>>>> to >>>>> the (serious) sign-in problem you observed on 3.13. >>>>> >>>>> That said, to investigate the real issue we need to get back to >>>>> 3.13, >>>>> and diagnose the problem in there. In case of error like in your >>>>> screenshot, you should rather get a stacktrace or at least ERROR >>>>> message >>>>> in log. It is possible we have some omission in logging, but >>>>> unlikely. >>>>> >>>>> Can you please first enable debug logging, then repeat your >>>>> failing >>>>> sign-in on 3.13 and inspect log files one more time (or share it >>>>> with >>>>> us)? We need to find some clues on what is failing. Without >>>>> access to >>>>> your database it will be the only way forward. >>>>> >>>>> Best, >>>>> Krzysztof >>>>> >>>>> > -- Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany E-Mail: l....@fz... Phone: +49 2461 61-6576 Fax: +49 2461 61-6656 ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2023-07-26 14:31:37
|
Hi Laura, W dniu 26.07.2023 o 13:17, Laura Hofer pisze: > Hi Krzysztof, > > we wanted to recreate the error, but it seems to be working now. The > application error does not appear anymore. Does it mean that you can now successfully run 3.13 (or at least are progressing with testing it)? Best, Krzysztof |
From: Laura H. <l....@fz...> - 2023-07-26 17:07:55
Attachments:
smime.p7s
|
Hi Krzysztof, yes, we are now in the process of testing 3.13. Best regards, Laura Am 26.07.23 um 16:31 schrieb Krzysztof Benedyczak: > Hi Laura, > > W dniu 26.07.2023 o 13:17, Laura Hofer pisze: >> Hi Krzysztof, >> >> we wanted to recreate the error, but it seems to be working now. The >> application error does not appear anymore. > > Does it mean that you can now successfully run 3.13 (or at least are > progressing with testing it)? > > Best, > Krzysztof > > -- Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany E-Mail: l....@fz... Phone: +49 2461 61-6576 Fax: +49 2461 61-6656 ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |