jaewookbyun / epcis Goto Github PK

I am getting following exception while generating Java class
org.xml.sax.SAXParseException EPCglobal-epcis-1_2.xsd
src-resolve: Cannot resolve the name 'sbdh:StandardBusinessDocumentHeader'

war 파일 복사후 tomcat을 실행했는데 localhost:8080/epcis 를 호출하면 404에러가 납니다. epcis 외 다른어플리케이션들은 실행이 되는 상황입니다. 혹시 수정해야할 파일이 있나요?
Tomcat 버전은 8.5.5 버전입니다.

Translated Question:
I faced 404 error after running Tomcat 8.5.5 with epcis.war file even though other applications (maybe, other web application on top of Tomcat) run successfully.

Is there any more setting for running Oliot epcis?

A self developed minimalistic client isn't able to request query names from Oliot EPCIS v1.2.1.
Operation: GetQueryNames failed because server responded with Unexpected element.
javax.xml.ws.soap.SOAPFaultException: Unexpected element {urn:epcglobal:epcis-query:xsd:1}GetQueryNamesResponse found. Expected {urn:epcglobal:epcis-query:xsd:1}GetQueryNamesResult.

Client: self developed based on https://www.gs1.org/standards/epcis/artifacts/1-2

As I'm reading the specifiation I'd expect the GetQueryNamesResult but it sends back a GetQueryNamesRepsonse.
I'v already tried to use the wsdl file which is downloadable from the server (http://localhost:8080/epcis/webservice/QueryService?wsdl) but it's not working with wsimport or cfx.

Do you have any further idea?

Hello.

Firstly, thank you for developing this software.

The issue I want to report is an inconsistency with the names of these files:

epcis-server/src/main/resources/schema/EPCglobal-epcis-2_0.xsd
epcis-server/src/main/resources/schema/EPCglobal-epcis-masterdata-2_0.xsd
epcis-server/src/main/resources/schema/EPCglobal-epcis-query-2_0.xsd
epcis-server/src/main/resources/schema/EPCglobal.xsd

It appears that you developed this software entirely on Microsoft Windows, where filenames are not case sensitive.
While I was attempting to configure the server to run in Docker, I noticed that in some places in the code, these files are referenced as EPCglobal-*, while in others they are referenced as epcglobal-*
(It took me an embarrassing amount of hours to figure out why some resources were found, while others weren't.)

The way I fixed this in my own copy of the project was by renaming these four files to always be in lowercase, and then replacing any mention of EPCglobal with epcglobal.
I am not opening a pull request with these changes, because I thought that you might prefer to do the exact opposite and replace all epcglobal mentions with EPCglobal.
Regardless of which approach you prefer, please make sure that the filenames stay consistent.

Best Regards from Bulgaria,
Aleksandar Dinkov

I'm not sure if there is a reason for it. On the file epcis/src/main/webapp/rest-like_query_service.html, for instance, there are several entries of "http://localhost:8080/epcis/.*" that are used to define the address for the ajax call. If I access it, on my browser, using http://localhost:8080/epcis, everything works fine.

But, if I (or a coworker) access it from my IP "http://192.168.0.10:8080/epcis/." then the browser detects cross scripting, and blocks the request. One way to solve this is making the URL relative "/epcis/." instead. If there is no special reason to point to localhost, I can change it on my repo and make a PR.

Hello again.

I have now started working on using the API of this server. I attempted to call the /capture endpoint with some testing data. (I will provide that testing data bellow.) However the EPCIS document I passed seems to be rejected.

I am not completely sure that my test data is actually correctly formatted, but after examining the code, I believe that it is... or at least that if there is a problem, it is somewhere else and not where the code fails.

The code fails in this method: TagDataTranslationEngine.toInstanceLevelEPC()
In it there are 3 parts of the code:

1. determine a variable IdentifierType type by attempting to parse the parameter as a Digital Link
2. depending on the determined type, go into one out of a series of if statements and properly parse the actual string
   • Inside most of these parsing function, the code will attempt to parse the string as a Digital Link
   • If it fails, it will then attempt to parse it as some sort of EPC URN (urn:epc:id:<some-type>:<some-numbers>)
3. if the type doesn't match any of the if statements, an error is thrown.
   • Unsupported instance level code scheme
   • This is the exact error I see when I pass my event to /capture

To reproduce my problem, simply run this code snippet:
TagDataTranslationEngine.toInstanceLevelEPC("urn:epc:id:sgtin:4023333.000055.1A")

Alternatively, you can call the /capture endpoint with this JSON data:
{"@context":["https://ref.gs1.org/standards/epcis/2.0.0/epcis-context.jsonld"],"type":"EPCISDocument","schemaVersion":"2.0","creationDate":"2021-05-25T08:33:43.015Z","epcisBody":{"eventList":[{"type":"ObjectEvent","@context":[],"eventTime":"2021-05-25T08:33:43.015Z","eventTimeZoneOffset":"+02:00","epcList":["urn:epc:id:sgtin:4023333.000055.1A","urn:epc:id:sgtin:4023333.000055.1B"],"action":"ADD","bizStep":"commissioning","disposition":"active","readPoint":{"id":"urn:epc:id:sgln:4023333.00002.0"},"bizTransactionList":[{"type":"po","bizTransaction":"urn:epc:id:gdti:0614141.00002.123"}]}]}}

So what does actually happen?

1. In step 1 the code tries to get the Digital Link type of "urn:epc:id:sgtin:4023333.000055.1A" and it fails, because it is not a digital link.
2. The correct type should have been IdentifierType.SGTIN.
3. If the type was actually set to IdentifierType.SGTIN, then SerializedGlobalTradeItemNumber.toEPC(instanceLevelDL); would have been called.
4. in the toEPC method the getDigitalLinkMatcher would have failed, as the string is not a digital link.
5. but the next part (getElectronicProductCodeMatcher) would have succeeded, because one of the EPCPatterns.SGTINList regex patterns actually matches that string.
6. That matching regex pattern is my reason to beliefe that my test data is actually in the correct format.
7. however since the type variable was null, the code moves to the last part instead, where it throws an error.

This problem seems to be present in some other methods inside of the TagDataTranslationEngine class.

• toClassLevelEPC
• toInstanceLevelEPC
• toBusinessTransactionEPC
• there might be other places too, but I have not found them.

However the solution seems to already be implemented in another method: TagDataTranslationEngine.toEPC

• In there, you similarly attempted to parse the string as a Digital Link at first
• But you also check if the parsing failed. If it did, you also attempt to parse it as an EPC URN
• Please do the same thing in the other 3 methods

Best regards,
Aleksandar Dinkov

Query by EQ_eventID does not find the desired event by EQ_eventID.

When queried for all events, EPCIS returns an eventID: 1234

But when queried for event with eventID: 1234, EPCIS returns no results

I need regex to search data in EQ_bizTransaction_ parameter.

• Why you didn't provide regex search in this EQ_bizTransaction_ parameter?
• At code level, Could i change search query for this parameter in EQ_bizTransaction_ according to regex or after changing will i face any issue?

according to your Installation procedure

1. Installation as User
   Jaewook Byun edited this page on 6 Oct 2016 · 1 revision

I installed epcis.war
but got the following error in the log:

17-Jul-2018 12:43:40.181 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.32
17-Jul-2018 12:43:40.187 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 20 2018 19:50:35 UTC
17-Jul-2018 12:43:40.188 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.32.0
17-Jul-2018 12:43:40.188 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows 10
17-Jul-2018 12:43:40.188 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
17-Jul-2018 12:43:40.188 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\Java\jre-10.0.1
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 10.0.1+10
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: "Oracle Corporation"
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Apache Software Foundation\Tomcat 8.5
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Apache Software Foundation\Tomcat 8.5
17-Jul-2018 12:43:40.189 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 8.5
17-Jul-2018 12:43:40.190 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 8.5
17-Jul-2018 12:43:40.190 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 8.5\temp
17-Jul-2018 12:43:40.190 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
17-Jul-2018 12:43:40.190 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat 8.5\conf\logging.properties
17-Jul-2018 12:43:40.190 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.lang=ALL-UNNAMED
17-Jul-2018 12:43:40.191 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.io=ALL-UNNAMED
17-Jul-2018 12:43:40.191 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
17-Jul-2018 12:43:40.191 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
17-Jul-2018 12:43:40.191 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
17-Jul-2018 12:43:40.191 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms128m
17-Jul-2018 12:43:40.192 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx256m
17-Jul-2018 12:43:40.192 INFORMATION [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Apache Software Foundation\Tomcat 8.5\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.4.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.4.2\bin;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;c:\Program Files\Intel\WiFi\bin;c:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files\Git\cmd;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Haskell Platform\8.4.2\mingw\bin;C:\Program Files\nodejs;C:\Program Files\Microsoft VS Code\bin;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;.]
17-Jul-2018 12:43:40.251 INFORMATION [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8089"]
17-Jul-2018 12:43:40.314 INFORMATION [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
17-Jul-2018 12:43:40.323 INFORMATION [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
17-Jul-2018 12:43:40.325 SCHWERWIEGEND [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[AJP/1.3-8009]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[AJP/1.3-8009]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.startup.Catalina.load(Catalina.java:632)
at org.apache.catalina.startup.Catalina.load(Catalina.java:655)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:995)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
... 12 more
Caused by: java.net.BindException: Address already in use: bind
at java.base/sun.nio.ch.Net.bind0(Native Method)
at java.base/sun.nio.ch.Net.bind(Unknown Source)
at java.base/sun.nio.ch.Net.bind(Unknown Source)
at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at java.base/sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:210)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1086)
at org.apache.tomcat.util.net.AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:268)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:581)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:993)
... 13 more

17-Jul-2018 12:43:40.327 INFORMATION [main] org.apache.catalina.startup.Catalina.load Initialization processed in 747 ms
17-Jul-2018 12:43:40.411 INFORMATION [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
17-Jul-2018 12:43:40.411 INFORMATION [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.32
17-Jul-2018 12:43:40.427 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\docs]
17-Jul-2018 12:43:40.925 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\docs] has finished in [498] ms
17-Jul-2018 12:43:40.926 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\manager]
17-Jul-2018 12:43:40.990 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\manager] has finished in [64] ms
17-Jul-2018 12:43:40.991 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\ROOT]
17-Jul-2018 12:43:41.026 INFORMATION [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\ROOT] has finished in [35] ms
17-Jul-2018 12:43:41.032 INFORMATION [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8089"]
17-Jul-2018 12:43:41.049 INFORMATION [main] org.apache.catalina.startup.Catalina.start Server startup in 721 ms
17-Jul-2018 12:44:10.890 INFORMATION [http-nio-8089-exec-6] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\epcis.war]
17-Jul-2018 12:44:15.506 INFORMATION [http-nio-8089-exec-6] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
17-Jul-2018 12:44:16.354 INFORMATION [http-nio-8089-exec-6] com.mongodb.diagnostics.logging.JULLogger.log Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500}
17-Jul-2018 12:44:16.468 INFORMATION [cluster-ClusterId{value='5b4dc880b65c2c23546b8d0c', description='null'}-localhost:27017] com.mongodb.diagnostics.logging.JULLogger.log Opened connection [connectionId{localValue:1, serverValue:23}] to localhost:27017
17-Jul-2018 12:44:16.472 INFORMATION [cluster-ClusterId{value='5b4dc880b65c2c23546b8d0c', description='null'}-localhost:27017] com.mongodb.diagnostics.logging.JULLogger.log Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 21]}, minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216, roundTripTimeNanos=835352}
17-Jul-2018 12:44:16.571 INFORMATION [http-nio-8089-exec-6] com.mongodb.diagnostics.logging.JULLogger.log Opened connection [connectionId{localValue:2, serverValue:24}] to localhost:27017
17-Jul-2018 12:44:16.606 SCHWERWIEGEND [http-nio-8089-exec-6] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
17-Jul-2018 12:44:16.607 SCHWERWIEGEND [http-nio-8089-exec-6] org.apache.catalina.core.StandardContext.startInternal Context [/epcis] startup failed due to previous errors
17-Jul-2018 12:44:16.660 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [cluster-ClusterId{value='5b4dc880b65c2c23546b8d0c', description='null'}-localhost:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.waitForSignalOrTimeout(DefaultServerMonitor.java:224)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.waitForNext(DefaultServerMonitor.java:205)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:153)
[email protected]/java.lang.Thread.run(Unknown Source)
17-Jul-2018 12:44:16.661 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[email protected]/java.lang.Thread.run(Unknown Source)
17-Jul-2018 12:44:16.662 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.664 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.665 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.666 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.667 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.668 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.668 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.669 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.670 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.671 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:16.672 WARNUNG [http-nio-8089-exec-6] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:427)
17-Jul-2018 12:44:16.692 INFORMATION [http-nio-8089-exec-6] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [C:\Program Files\Apache Software Foundation\Tomcat 8.5\webapps\epcis.war] has finished in [5,802] ms
17-Jul-2018 12:44:25.207 INFORMATION [http-nio-8089-exec-3] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
17-Jul-2018 12:44:25.738 INFORMATION [http-nio-8089-exec-3] com.mongodb.diagnostics.logging.JULLogger.log Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500}
17-Jul-2018 12:44:25.825 INFORMATION [cluster-ClusterId{value='5b4dc889b65c2c235477a760', description='null'}-localhost:27017] com.mongodb.diagnostics.logging.JULLogger.log Opened connection [connectionId{localValue:1, serverValue:25}] to localhost:27017
17-Jul-2018 12:44:25.828 INFORMATION [cluster-ClusterId{value='5b4dc889b65c2c235477a760', description='null'}-localhost:27017] com.mongodb.diagnostics.logging.JULLogger.log Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 21]}, minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216, roundTripTimeNanos=550534}
17-Jul-2018 12:44:25.903 INFORMATION [http-nio-8089-exec-3] com.mongodb.diagnostics.logging.JULLogger.log Opened connection [connectionId{localValue:2, serverValue:26}] to localhost:27017
17-Jul-2018 12:44:25.930 SCHWERWIEGEND [http-nio-8089-exec-3] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
17-Jul-2018 12:44:25.930 SCHWERWIEGEND [http-nio-8089-exec-3] org.apache.catalina.core.StandardContext.startInternal Context [/epcis] startup failed due to previous errors
17-Jul-2018 12:44:25.959 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [cluster-ClusterId{value='5b4dc889b65c2c235477a760', description='null'}-localhost:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.waitForSignalOrTimeout(DefaultServerMonitor.java:224)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.waitForNext(DefaultServerMonitor.java:205)
com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:153)
[email protected]/java.lang.Thread.run(Unknown Source)
17-Jul-2018 12:44:25.960 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[email protected]/java.lang.Thread.run(Unknown Source)
17-Jul-2018 12:44:25.960 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.960 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.961 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.961 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.961 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.962 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.962 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.963 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.963 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.964 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)
17-Jul-2018 12:44:25.964 WARNUNG [http-nio-8089-exec-3] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [epcis] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Object.wait(Native Method)
org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:427)

When subscribing to EPCIS events with periodic schedule, same events are posted over and over again. This is unpractical because the receiver must filter out the already received events and the posted data grows bigger and bigger over time. Alternative option is to unsubscribe and re-subscribe after every query or once in a while. Both options are bad.

GS1 EPCIS standard 1.2 has a non-normative implementation suggestion in chapter 8.2.5.2 Automatic limitation based on event record time:

Explanation: one possible implementation of this requirement is that the EPCIS service maintains a minRecordTime value for each subscription that exists. The minRecordTime for a given subscription is initially set to initialRecordTime, and updated to the current time each time the query is executed for that subscription. Each time the query is executed, the only events considered are those whose recordTime is greater than or equal to minRecordTime for that subscription.

Suggestion to implement it with one addition - only update the minRecordTime when recipient confirms the reception of the query with HTTP response code 200 (OK). If request isn't confirmed, repeat the query with same events.

Walmart since october 2002 until april 2014 prefer to use EPCIS AS2 binding instead of SOAP binding, why Oliot has decided to use SOAP Binding?

http://cdn.corporate.walmart.com/5d/8d/897b4bb84a95bb05214bf897cee3/edi-getting-started-guide.pdf