DOCSLIB.ORG

Visualizing Mirrors Mirrors.Ustc.Edu.Cn 服务器日志分析

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Visualizing Mirrors mirrors.ustc.edu.cn 服务器日志分析 . 李博杰 [email protected] ©USTC LUG August 14, 2012 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Outline 1. Requests & Traffic By Time By IP By Other Measures 2. Files Files Characteristics How Files Are Requested 3. Sessions 4. Distributions Insight CentOS Fedora Ubuntu Eclipse 5. Technical Details 6. Query Optimization . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Notes The data is access log of mirrors.ustc.edu.cn in 51 days. See ‘Technical Details’ section for more info about dataset. Some graphs are in log-scale for clarity. Please note whether x axis, y axis or both are in log-scale. The graph title sometimes lies. Because there may be many points in a graph, sampling is made to reduce file size (they are vector graphics), hence there may be some ‘straight lines’. I have checked the data to make sure the graphs illustrate real trends. Title length is limited, so the title itself may not explain well, please keep an eye on the axis and keys of the graph. Graphs are shown in the hope of conveying information without words. Any questions or suggestions, please email me. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic in a day Requests & Traffic within a day 400000 5e+10 350000 4e+10 300000 250000 3e+10 200000 Requests Traffic (Bytes) 2e+10 150000 100000 1e+10 50000 Request count (Bezier smoothed) Traffic (Bezier smoothed) 0 0 00:00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00 00:00 Time of the day . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic in a week Requests & Traffic in different weekdays 7e+07 8e+12 7e+12 6e+07 6e+12 5e+07 5e+12 4e+07 4e+12 Requests 3e+07 Traffic (Bytes) 3e+12 2e+07 2e+12 1e+07 1e+12 Request count Traffic 0 0 Monday Tuesday Wednesday Thursday Friday Saturday Sunday Time of the day . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic across 50 days Requests & Traffic in 50 days 1.2e+07 1.2e+12 1e+07 1e+12 8e+06 8e+11 6e+06 Requests 6e+11 Traffic (Bytes) 4e+06 4e+11 2e+06 2e+11 Request count Traffic 0 0 05-20 05-27 06-03 06-10 06-17 06-24 07-01 07-08 07-15 Time of the day . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Statistics Requests Traffic Total 328976877 36892 GB Avg. per Day 6450527 723.4 GB Max. per Day 8632963 1049.5 GB Min. per Day 4868022 421.5 GB Avg. per Hour 268771 30.14 GB Max. per Hour 561925 79.75 GB Min. per Hour 99506 2.97 GB Avg. per Minute 4480 514.4 MB Max. per Minute 14714 N/A Min. per Minute 441 N/A Avg. per Second 74.66 8779 KB Max. per Second 2117 N/A Min. per Second 1 N/A Because the time recorded is only completion time of the request, and large requests can span hours, so Max./Min. per minute/second is not applicable. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Cumulative Requests per Hour Sorted Requests per Hour 600000 550000 500000 450000 400000 350000 Requests 300000 250000 200000 150000 100000 Hour Percentage 50000 0 10 20 30 40 50 60 70 80 90 100 Hour Percentage (sorted by Requests count). .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Cumulative Requests per Minute Sorted Requests per Minute 16000 14000 12000 10000 8000 Requests 6000 4000 2000 Minutes Percentage 0 0 10 20 30 40 50 60 70 80 90 100 Minutes Percentage (sorted by Requests count). .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Cumulative Requests per Second Sorted Requests per Second 450 400 350 300 250 Requests 200 150 100 50 Seconds Percentage 0 0 10 20 30 40 50 60 70 80 90 100 Seconds Percentage (sorted by Requests count). .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Cumulative Traffic over IPs: 20%-80% law Cumulative Traffic over unique IPs 4e+13 3.5e+13 3e+13 2.5e+13 2e+13 Cumulative Traffic 1.5e+13 1e+13 5e+12 0 1 10 100 1000 10000 100000 1e+06 1e+07 Percentage of unique IP (log-scale) (sorted by Traffic. DESC). .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Cumulative Requests over IPs: 20%-80% law Cumulative Requests over unique IPs 3.5e+08 3e+08 2.5e+08 2e+08 1.5e+08 Cumulative Requests 1e+08 5e+07 0 1 10 100 1000 10000 100000 1e+06 1e+07 Percentage of unique IP (log-scale) (sorted by Request. Num. DESC). .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . IPv4 vs. IPv6 Requests Traffic IPv4 318575688 (96.84%) 34180 GB (92.65%) IPv6 10401189 (3.15%) 2712 GB (7.35%) It can be seen that IPv6 still have a long way to go… . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic TOP 40: xxx.0.0.0/24 Request & Traffic among IPv4 first fields 0.08 Requests Traffic 0.07 0.06 0.05 0.04 Percentage 0.03 0.02 0.01 0 IPv6 222 202 113 218 58 114 61 183 180 121 124 116 219 210 119 122 59 221 125 123 60 115 117 118 220 211 203 112 111 14 182 110 27 1 120 175 101 159 223 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Traffic TOP 40: IPv4 addrs Request & Traffic among popular IPv4 addrs 0.005 Requests Traffic 0.0045 0.004 0.0035 0.003 0.0025 Percentage 0.002 0.0015 0.001 0.0005 0 219.133.0.1 218.242.250.212 203.114.244.88 114.212.189.93 114.113.226.53 180.169.73.90 180.96.19.25 66.197.225.53 218.3.125.243 61.234.123.57 159.226.126.177 203.198.202.225 124.74.45.130 220.181.145.27 114.213.255.162 202.108.130.138 202.119.45.31 222.66.23.57 124.127.250.34 208.53.156.36 221.216.135.54 116.228.240.198 113.108.76.195 114.80.133.7 210.13.71.73 180.149.134.10 124.126.245.14 218.94.63.55 220.248.0.145 112.65.134.2 222.56.17.109 124.74.78.2 124.207.104.18 58.211.218.74 1.202.225.132 116.226.65.12 220.248.0.154 222.94.140.45 210.73.5.33 116.247.98.50 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Request count TOP 40: IPv4 addrs Request & Traffic among popular IPv4 addrs 0.03 Requests Traffic 0.025 0.02 0.015 Percentage 0.01 0.005 0 63.245.214.78 209.132.181.102 113.111.38.40 129.143.116.10 211.86.56.227 223.5.20.10 49.123.105.219 159.226.20.217 60.208.111.199 119.97.142.81 202.38.95.60 203.244.218.6 221.219.75.222 202.104.151.152 121.49.96.70 59.77.33.100 182.89.199.227 183.45.54.83 218.13.224.81 59.37.44.133 59.44.42.194 222.134.53.246 210.21.243.170 61.130.247.168 116.228.202.66 123.185.172.126 219.134.89.202 114.113.29.21 183.31.242.39 58.19.126.37 27.17.19.75 203.114.244.88 220.178.52.108 124.42.77.160 113.111.40.89 218.94.63.55 180.153.97.82 222.171.60.177 210.34.196.99 222.92.29.130 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . USTC Mirrors Usage (IPv4 only) IP range Requests Traffic Note 202.38.64.0-202.38.95.255 994661 (0.30%) 149.3 GB (0.40%) CERNET 210.45.64.0-210.45.79.255 191141 (0.06%) 68.31 GB (0.19%) CERNET 210.45.112.0-210.45.127.255 243976 (0.07%) 37.59 GB (0.10%) CERNET 211.86.144.0-211.86.159.255 81035 (0.02%) 24.96 GB (0.07%) CERNET 222.195.64.0-222.195.95.255 319435 (0.10%) 86.88 GB (0.24%) CERNET 114.214.160.0-114.214.255.255 0 0 CERNET 210.72.22.0-210.72.22.255 3622 (0.00%) 11.86 MB (0.00%) TechNet (?) 218.22.21.0-218.22.21.31 1 (0.00%) 0.01 MB (0.00%) China Telecom 218.104.71.160-218.104.71.175 0 0 China Unicom 202.141.160.0-202.141.175.255 123455 (0.04%) 12.60 GB (0.03%) China Telecom 202.141.176.0-202.141.191.255 187 (0.00%) 120.4 MB (0.00%) China Mobile Total 1957513 (0.60%) 379.77 GB (1.03%) USTC IPv4 Data source of USTC IP range: http://lib.ustc.edu.cn/ustcip.html . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic of distributions Request & Traffic of Distributions 0.35 0.3 0.25 0.2 Percentage 0.15 0.1 0.05 Requests Traffic 0 eclipsefedoraubuntucentosdebiantdf cygwinCTANarchlinuxmozilla-currentopensusegentookde-applicationdatakde backtrackepel gnu CRANNULLfreebsdubuntu-releasesdebian-securityscientificlinuxlinux-kerneldebian-backportskdemoddebian-cdmeegoslackwaredeepinsourceware.orgCPANlinuxmintlinux-2.6.gitpuppylinux.gitdebian-multimedia4 qomo3.7 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 李博杰 [email protected] Visualizing Mirrors . Requests & Traffic of distributions Request & Traffic of Distributions 0.35 0.3 0.25 0.2 Percentage 0.15 0.1 0.05 Requests Traffic 0 centosNULLeclipsefedoraubuntuubuntu-releasesmozilla-currenttdf debianCTANbacktrackopensusegentoodeepin-cdkde-applicationdatadebian-cdcygwinUbuntulinuxmintarchlinuxkde gnu linuxmint-cdCRANdebian-multimediaqomodebian-securityepel puppyscientificlinuxdebian-backportsfreebsddeepinCPANkdemodturnkeylinuxslackwaredebian-uogentoo-portagelinux-kernel .
Recommended publications
  • Architecture Committee Handbook

    Architecture Committee Handbook

    Architecture Committee Handbook openKONSEQUENZ created by Architecture Committee We acknowledge that this document uses material from the arc 42 architecture template, http://www.arc42.de. Created by Dr. Peter Hruschka & Dr. Gernot Starke. ​ Template Revision: 6.1 EN June 2012 1 Revision History Version Date Reviser Description Status 1.0 2016-07-04 A. Göring Alignment in AC/QC conference call Released 1.0.1 2016-07-19 A. Göring Added UML-Tool decision in chapter 2. Draft for Constraints, Added software-tiers v1.1 image in chapter 8. 1.1 2016-08-18 A.Göring Alignment in AC/QC conference call Released 1.1.1 2016-08-26 F. Korb, M. Description of architecture layer model Draft for Rohr and its APIs. Example internal module v1.2 architecture (Presented in ACQC-Meeting 15.& 29.08.2016) 1.2 2016-09-14 A. Göring Integration of Concept for Plattform Released Module Developmennt, Consolidation v1.1.1 1.2.1 2016-09-16 S.Grüttner Reorganization of Chapter7 Draft for Deployment Environment, clearifying v1.3 the reference environment as “image”. Adding cutting of CIM Cache. Modified Logging (8.17) for use of SLF4J. Added potential non-functional requirement for Offline-Mode. 1.2.2 2017-01-30 A. Göring Adding Link to oK-API Swagger Draft for Definition, deleting old Interfaces v1.3 Annex. Adding CIM Cache Module dependencies image and text (from Felix Korb) 1.3 2017-02-14 A. Göring Alignment in/after AC/QC conference Released call 1.3.1 2017-09-05 A. Göring Minimum requirement change from Released Java EE 7 to Oracle Java SE 8.
  • JPA Persistence Guide (V6.0) Table of Contents

    JPA Persistence Guide (V6.0) Table of Contents

    JPA Persistence Guide (v6.0) Table of Contents EntityManagerFactory. 2 Create an EMF in JavaSE . 2 Create an EMF in JavaEE . 2 Persistence Unit . 3 EntityManagerFactory Properties . 6 Closing EntityManagerFactory . 27 Level 2 Cache. 27 Datastore Schema. 34 Schema Generation for persistence-unit . 34 Schema Auto-Generation at runtime . 35 Schema Generation : Validation . 36 Schema Generation : Naming Issues . 36 Schema Generation : Column Ordering . 37 Schema : Read-Only. 37 SchemaTool . 38 Schema Adaption . 44 RDBMS : Datastore Schema SPI . 44 EntityManager. 48 Opening/Closing an EntityManager. 48 Persisting an Object. 49 Persisting multiple Objects in one call . 49 Finding an object by its identity . 50 Finding an object by its class and unique key field value(s) . 50 Deleting an Object . 51 Deleting multiple Objects. 51 Modifying a persisted Object. 52 Modifying multiple persisted Objects . 52 Refreshing a persisted Object . 52 Getting EntityManager for an object. 53 Cascading Operations . 53 Orphans . 54 Managing Relationships . 54 Level 1 Cache. 56 Object Lifecycle. 58 Transaction PersistenceContext . 58 Extended PersistenceContext . 58 Detachment . 58 Helper Methods . 59 Transactions . 60 Locally-Managed Transactions. 60 JTA Transactions. 61 Container-Managed Transactions . 63 Spring-Managed Transactions . 63 No Transactions . 63 Transaction Isolation . 64 Read-Only Transactions . 64 Flushing . 65 Transactions with lots of data. 66 Transaction Savepoints . 67 Locking . 68 Optimistic Locking. 68 Pessimistic (Datastore) Locking . 69 Datastore.
  • On-Process Verification and Report

    On-Process Verification and Report

    CORE Metadata, citation and similar papers at core.ac.uk Provided by Open Repository of the University of Porto FACULDADE DE ENGENHARIA DA UNIVERSIDADE DO PORTO On-Process Verification and Report Tiago Nunes Project Report Master in Informatics and Computing Engineering Supervisor: João Pascoal Faria (PhD) 3rd March, 2009 On-Process Verification and Report Tiago Nunes Project Report Master in Informatics and Computing Engineering Approved in oral examination by the committee: Chair: Ana Cristina Ramada Paiva Pimenta (PhD) External Examiner: Fernando Brito e Abreu (PhD) Internal Examiner: João Carlos Pascoal de Faria (PhD) 19th March, 2009 Abstract This report describes the motivation, architecture and post-implementation return on in- vestment of an On-Process Validation and Report solution. Its objective was to create an automation tool that would free the Product Assurance team at Critical Software, S.A. from repetitive and time-consuming tasks, while at the same time providing a platform upon which further systems could be implemented, augmenting the tool kit of the Product Assurance Engineers. This was achieved by designing a modular and extensible platform using cutting-edge Java technologies, and following a goal-oriented development process that focused on iteratively providing as many domain-specific features as possible. It is shown that the resulting system has the potential for considerably reducing costs in the validation of projects throughout their entire life cycle. i ii Resumo Este relatório descreve a motivação, arquitectura e o retorno sobre o investimento após a implementação de uma solução para a Validação e Reporting On-Process. O seu objec- tivo era a criação de uma ferramenta de automação que libertaria a equipa de Controlo de Produto da Critical Software, S.A.
  • Eclipselink Understanding Eclipselink 2.4

    Eclipselink Understanding Eclipselink 2.4

    EclipseLink Understanding EclipseLink 2.4 June 2013 EclipseLink Concepts Guide Copyright © 2012, 2013, by The Eclipse Foundation under the Eclipse Public License (EPL) http://www.eclipse.org/org/documents/epl-v10.php The initial contribution of this content was based on work copyrighted by Oracle and was submitted with permission. Print date: July 9, 2013 Contents Preface ............................................................................................................................................................... xiii Audience..................................................................................................................................................... xiii Related Documents ................................................................................................................................... xiii Conventions ............................................................................................................................................... xiii 1 Overview of EclipseLink 1.1 Understanding EclipseLink....................................................................................................... 1-1 1.1.1 What Is the Object-Persistence Impedance Mismatch?.................................................. 1-3 1.1.2 The EclipseLink Solution.................................................................................................... 1-3 1.2 Key Features ...............................................................................................................................
  • Eclipselink and JPA

    Eclipselink and JPA

    <Insert Picture Here> High Performance Persistence with EclipseLink Shaun Smith—Principal Product Manager [email protected] What is EclipseLink? ●Comprehensive Open Source Persistence solution ● EclipseLink JPA Object-Relational (JPA 2.0 RI) ● EclipseLink MOXy Object-XML (JAXB) ● EclipseLink SDO Service Data Objects (SDO 2.1.1 RI) ● EclipseLink DBWS Generated JAX-WS from DB ●Mature and full featured ● Over 13 years of commercial usage ● Initiated by the contribution of Oracle TopLink ●Target Platforms ● Java EE, Web, Spring, Java SE, and OSGi ●Get involved ● Open collaborative community ● Contributions welcomed EclipseLink Project Java SE Java EE OSGi Spring Web JPA MOXy EIS SDO DBWS Eclipse Persistence Services Project (EclipseLink) Databases XML Data Legacy Systems EclipseLink: Distributions ●Eclipse.org ● www.eclipse.org/eclipselink/downloads ● http://download.eclipse.org/rt/eclipselink/updates ●Oracle ● TopLink 11g ● WebLogic Server 10.3 ●GlassFish v3 ● Replaces TopLink Essentials ● JPA 2.0 Reference Implementation ●Spring Source ● Spring Framework and Bundle Repository ●JOnAS ●Jetty ●JEUS TMaxSoft ●SAP NetWeaver coming soon EclipseLink Developer Tool Support . EclipseLink is a Runtime Project but supported by IDEs . Eclipse IDE . EclipseLink support included by Dali in Eclipse 3.4 (Ganymede) . EclipseLink included in Eclipse 3.5 (Galileo) – JavaEE ● Enhanced Dali support for use of EclipseLink . Oracle Enterprise Pack for Eclipse (OEPE) . MyEclipse . JDeveloper 11g . JPA, Native ORM, OXM, and EIS mapping . NetBeans . Standalone
  • Virgo White Paper Introduction the Eclipse Virgo Project Provides a Modular Java Server Runtime and Is Part of the Eclipse Runtime (Eclipsert) Umbrella Project

    Virgo White Paper Introduction the Eclipse Virgo Project Provides a Modular Java Server Runtime and Is Part of the Eclipse Runtime (Eclipsert) Umbrella Project

    Eclipse Virgo A Technical Overview White Paper Version 1.2 June 2012 Table of Contents Introduction.......................................................................................................................................... 3 OSGi Introduction................................................................................................................................ 3 History.................................................................................................................................................. 4 Virgo Feature Summary........................................................................................................................4 Benefits.................................................................................................................................................5 Why Choose Virgo?..............................................................................................................................9 Success Stories................................................................................................................................... 10 A Warning........................................................................................................................................... 11 Technology......................................................................................................................................... 11 Virgo Runtime Deliverables..............................................................................................................
  • E(Fx)Clipse - Javafx Runtime Tom Schindl - Bestsolution Systemhaus Gmbh

    E(Fx)Clipse - Javafx Runtime Tom Schindl - Bestsolution Systemhaus Gmbh

    e(fx)clipse - JavaFX Runtime Tom Schindl - BestSolution Systemhaus GmbH EclipseCon October 2012 (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About Tom ✤ CTO BestSolution Systemhaus GmbH ✤ Eclipse Committer ✤ e4 ✤ Platform UI ✤ EMF ✤ Main developer of e(fx)clipse ✤ Twitter: @tomsontom (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at ✤ All sources provided under EPL (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at ✤ All sources provided under EPL ✤ Started in Summer 2011 (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at ✤ All sources provided under EPL ✤ Started in Summer 2011 ✤ Releases every 6-8 weeks (~2500 Downloads/ release) (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at ✤ All sources provided under EPL ✤ Started in Summer 2011 ✤ Releases every 6-8 weeks (~2500 Downloads/ release) ✤ Community Support: www.efxclipse.org (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26. Oktober 12 About e(fx)clipse ✤ Opensource project lead by BestSolution.at ✤ All sources provided under EPL ✤ Started in Summer 2011 ✤ Releases every 6-8 weeks (~2500 Downloads/ release) ✤ Community Support: www.efxclipse.org ✤ Commercial Support: www.bestsolution.at (c) Tom Schindl - BestSolution Systemhaus GmbH Freitag, 26.
  • Eclipse Roadmap V5

    Eclipse Roadmap V5

    Eclipse RoadMap v5 Introduction As required by the Eclipse Development Process, this document describes the 2010 Eclipse Roadmap. There are three main sections to this document: 1. This Preamble provides some background on Eclipse and the Foundation, and identifies the strategic goals of Eclipse. It also provides a brief overview of the scope of future projects 2. The Themes and Priorities which has been developed by the Eclipse Councils. 3. The Platform Release Plan which has been developed by the Eclipse Planning Council. The Roadmap is intended to be a living document which will see future iterations. This document is the fifth version of the Eclipse Roadmap, and is labeled as version 5.0. In order to preserve this document while the underlying information evolves, the pages have been frozen by copying them from their original project hosted locations. The goal of the Roadmap is to provide the Eclipse ecosystem with guidance and visibility on the future directions of the Eclipse open source community. An important element in this visibility is that the Roadmap help the EMO and the Board of Directors in determining which projects will be accepted by Eclipse during the life of this revision of the Roadmap. In other words, new projects must be consistent with the Roadmap. This does not mean that every new project must be explicitly envisaged by the Roadmap. It does mean that new projects cannot be inconsistent with the stated directions of Eclipse. In particular, Eclipse expects that incubator projects created in the Technology PMC will cover areas not explicitly described in the Roadmap.
  • Das Ende Der Finsternis Markus Karg, Java User Group Pforzheim

    Das Ende Der Finsternis Markus Karg, Java User Group Pforzheim

    Das Ende der Finsternis Markus Karg, Java User Group Pforzheim Nachdem die Anwenderschaft, neudeutsch „Community“, monatelang lautstark an der offensichtlichen Untätigkeit von Oracle herumgemeckert hat, ging es plötzlich ganz schnell: Java EE wurde an die Eclipse Foundation übergeben. Doch was bedeutet das im Detail? Ist Java EE nun tot und die JCP aufgelöst? Ein bewusst provokativer Kommentar aus Anwendersicht. Plötzlich war es da: das lange geforderte Öffnen von Test Compatibility ge Java EE) dort weiterentwickelt werde. Aber werden sie das denn Kits (TCK), Reference Implementations (RI) und Specifications (Specs). wirklich? Fakt ist: Bislang tut sich rein gar nichts, sieht man vom all- Was auch immer der letztendliche Auslöser war, sei es die monatelan- gegenwärtigen Auf-den-Busch-Klopfen einmal ab. ge Nörgelei oder einfach nur der Wunsch, sich einer Altlast zu entledi- gen, der Community soll es recht sein: Java EE ist nun endlich und voll- Zumindest tut sich nicht mehr als vorher. So schnell wird sich das ständig Open Source. Oder doch nicht? Naja, es kommt darauf an, wen auch nicht ändern. Auf die Frage, wo Oracle EE4J in einem Jahr stün- man fragt! Oracle sieht das so, die Community nicht unbedingt. de, will sich Oracle kaum mehr abringen lassen als ein „Aller Code ist von der Rechtsabteilung geprüft, auf die Server der Eclipse Foun- Trau, schau wem … dation kopiert und besteht als das Java EE 8 TCK.“ Moment mal … Die Eclipse Foundation gibt sich zumindest schon mal demonstrativ Java 8? Wurde denn nicht behauptet, durch den Move zur Eclipse euphorisch: Mike Milinkovic, Executive Directory eben jenes Indus- Foundation gehe dank der breiten Community-Beteiligung nun alles trie-Clubs, gab jüngst in der Keynote seiner Hausmesse EclipseCon viel flotter? Schade.
  • SDN Ro2tkits: a Case Study of Subverting a Closed Source SDN Controller

    SDN Ro2tkits: a Case Study of Subverting a Closed Source SDN Controller

    H. Langweg,H. Langweg, M. Meier, M. Meier, B.C. B.C. Witt, Witt, D. Reinhardt D. Reinhardt et al. (Hrsg.): Sicherheit 2018, LectureLecture Notes Notes in in Informatics Informatics (LNI), (LNI), Gesellschaft Gesellschaft für für Informatik, Informatik, Bonn Bonn 2018 2018 7995 SDN Ro2tkits: A Case Study of Subverting A Closed Source SDN Controller Christian Röpke1 Abstract: An SDN controller is a core component of the SDN architecture. It is responsible for managing an underlying network while allowing SDN applications to program it as required. Because of this central role, compromising such an SDN controller is of high interest for an attacker. A recently published SDN rootkit has demonstrated, for example, that a malicious SDN application is able to manipulate an entire network while hiding corresponding malicious actions. However, the facts that this attack targeted an open source SDN controller and applied a specific way to subvert this system leaves important questions unanswered: How easy is it to attack closed source SDN controllers in the same way? Can we concentrate on the already presented technique or do we need to consider other attack vectors as well to protect SDN controllers? In this paper, we elaborate on these research questions and present two new SDN rootkits, both targeting a closed source SDN controller. Similar to previous work, the first one is based on Java reflection. In contrast to known reflection abuses, however, we must develop new techniques asthe existing ones can only be adopted in parts. Additionally, we demonstrate by a second SDN rootkit that an attacker is by no means limited to reflection-based attacks.
  • Oracle Enterprise Pack for Eclipse, Which Is a Set of Plugins for Eclipse, to Support Java EE Development

    Oracle Enterprise Pack for Eclipse, Which Is a Set of Plugins for Eclipse, to Support Java EE Development

    Oracle[1] Enterprise Pack for Eclipse User’s Guide 12c (12.2.1.3) E71327-01 June 2016 Documentation that describes how to use Oracle Enterprise Pack for Eclipse, which is a set of plugins for Eclipse, to support Java EE development. It allows you to create, configure and deploy Oracle Mobile Application Framework applications for iOS and Android. You can create, configure, and run Oracle ADF applications on Glassfish and Oracle WebLogic Server. Oracle Enterprise Pack for Eclipse User's Guide, 12c (12.2.1.3) E71327-01 Copyright © 2008, 2016 Oracle and/or its affiliates. All rights reserved. Primary Author: Catherine Pickersgill This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
  • Oracle Utilities Testing Accelerator Licensing Information User Manual Release 6.0.0.3.0 F35952-01

    Oracle Utilities Testing Accelerator Licensing Information User Manual Release 6.0.0.3.0 F35952-01

    Oracle Utilities Testing Accelerator Licensing Information User Manual Release 6.0.0.3.0 F35952-01 June 2021 Oracle Utilities Testing Accelerator Licensing Information User Manual, Release 6.0.0.3.0 Copyright © 2019, 2021 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation"