Category Archives: Error

XML read process error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Content not allowed in preamble

com. sun. xml. internal. ws. streaming. Xmlstreamreaderexception: XML read process error: javax xml. stream. Xmlstreamexception: parseError at [row, col]: [1,1] message: content is not allowed in the preface

The error contents are as follows

com.sun.xml.internal.ws.streaming.XMLStreamReaderException: XML read process error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
Message: No content is allowed in the preamble.
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:311)
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:84)
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:154)
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:89)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.hasWSDLDefinitions(RuntimeWSDLParser.java:310)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:217)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:194)
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:163)
at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:348)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:306)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:215)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:196)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:192)
at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
at javax.xml.ws.Service.<init>(Service.java:77)
at cn.gov.ynhrss.psp.Ynhrsspspservice.<init>(Ynhrsspspservice.java:39)
at com.neusoft.xtpt.web.PspWebService.send(PspWebService.java:38)
at com.neusoft.xtpt.controller.PspCtl.basic(PspCtl.java:25)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792)
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:652)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:374)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:893)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1707)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
Message: No content is allowed in the preamble.
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:604)
at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:81)
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:65)
... 66 more

Background

I call WebService in Java and report an error when I call new xxxxxxxservice().

Cause analysis

When WebService creates new xxxxxxxservice(), it needs to load the URL in xxxxxxxservice first. If the URL is not loaded or the URL is null, the above error may be reported.

There are two solutions

Method 1: Add the url of the webservice’s access address to the static method, as follows:

static {
        URL url = null;
        WebServiceException e = null;
        try {
            url = new URL("http://127.0.0.1:8088/ynhrs/services/info?wsdl");
        } catch (MalformedURLException ex) {
            e = new WebServiceException(ex);
        }
        BIZSERVICE_WSDL_LOCATION = url;
        BIZSERVICE_EXCEPTION = e;
    }

You can also configure the address of WebService file, etc

Method 2: directly add the URL to new xxxxxxxservice(), as follows:

Ynhrsspspservice pspService = new Ynhrsspspservice(new URL("http://127.0.0.1:8088/ynhrs/services/info?wsdl"));

http://127.0.0.1:8088/ynhrs/services/info?wsdl is the URL of webservice

[Solved] Docker Error: WSL 2 installation is incomplete.

Leave a reply

Problem Description:

This article solves two Docker errors:
1.WSL 2 installation is incomplete.
2.System.InvalidOperationException: Failed to set version to docker-desktop: exit code: -1

After successfully installing Docker today, I ran Docker and the following error occurred:

WSL 2 installation is incomplete.
The WSL 2 Linux kernel is now installed using a separate MSI update package.Please click the link and follow the instructions to install the kernel update:https://aka.ms/wsl2kernel.
Press Restart after installing the Linux kernel.
---

Cause Analysis:

Docker is a tool for packaging, distributing, and deploying applications.
Basically a lightweight virtual machine. There are only things we need in the virtual machine, other superfluous things are necessary.
Important Concepts: Image, Container
Image: Similar to software installation package, it can be quickly spread and installed.
Container: After the software is installed, each software running environment is independent and isolated, which is called a container.
Advantages: It ensures that running on different machines is a consistent operating environment, and there will be no situation where my machine runs normally and your machine runs properly.
When we install docker desktop, he asks if we need to use wsl2 (Windows based subsystem for Linux). If not, we’ll run with a Hyper-V virtual machine. However, this subsystem has better performance compared to virtual machines.

The WAL 2 Linux kernel is now installed using a separate MSI update package.

That’s the problem!

solution:

Let’s go to the system to check whether the Linux subsystem of Windows is enabled. The steps are as follows:
Control Panel -> Programs -> Programs and Features

Check if you have checked here: Enable Windows Subsystem for Linux

If not, we check it, restart the computer, and open Docker.
If you still report WSL 2 installation is incomplete. problem. There is only one reason left:
the version of wsl2 we are using is very old, so it needs to be updated manually. We can download the latest version of wsl2 from Microsoft’s official website according to the prompt, and then open it normally.
Visit the link below to download and install the update:

https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi

If the download is slow, use the Google browser to download, it is easy to use!
Install the latest version of wsl2:
insert image description here
reboot. run.

So far, most of them can run successfully. If not, there is the ultimate trick:
if you report an error at this time System.InvalidOperationException: Failed to set version to docker-desktop: exit code: -1

The error is as follows:

System.InvalidOperationException:
Failed to set version to docker-desktop: exit code: -1
 stdout: �S��v�[a�{|�W
N/ec\Ջ�v�d\O0
stderr: 
   在 Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:行号 146
   在 Docker.Engines.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:Line 82
--- The end of the stack trace in the previous location where the exception was raised ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__26.MoveNext() 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:行号 104
--- The end of the stack trace in the previous location where the exception was raised ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:行号 29
--- The end of the stack trace in the previous location where the exception was raised ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:行号 67
--- The end of the stack trace in the previous location where the exception was raised ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() 位置 C:\workspaces\PR-15387\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:行号 92

We open cmd as an administrator:
enter:

netsh winsock reset

Execute, 100% solve this problem!

Note: This command should be used with caution. This is to delete the original docker system, which is equivalent to resetting docker-desktop. The images and containers in me are gone. Restarting docker-desktop will regenerate docker-desktop and docker-desktop-data
insert image description here

[Solved] Bringing up interface eth0: Error: No suitable device found: no device found for connection ‘System eth0’.

Leave a reply

Error Messages:

Bringing up interface eth0: Error: No suitable device found: no device found for connection ‘System eth0’.

 

The reason is because the HWaddr in the /etc/udev/rules.d/70-persistent-net.rules file and the HWaddr of /etc/sysconfig/network-scripts/ifcfg-eth0 do not match the HWaddr of the new machine

The solution is to restart the machine after deleting /etc/udev/rules.d/70-persistent-net.rules, and then change the HWaddr of /etc/sysconfig/network-scripts/ifcfg-eth0 and 70-persistent-net.rules equal

[Solved] Git Error: fatal: refusing to merge unrelated histories

Leave a reply

1. Problem

fatal: refusing to merge unrelated histories

2. Scene

Merge other branches into master branch

3. Reason

The two branches are two different versions with different commit histories, so an error is reported.

4. Solutions

Allow unrelated historical commits and force merges, the code is as follows:

git pull origin master --allow-unrelated-histories

[Solved] Failed to initialize the editor as the document is not in standards mode. TinyMCE requires standards mode.

Leave a reply

error message

  • Failed to initialize the editor as the document is not in standards mode. TinyMCE requires standards mode.

general meaning

  • TinyMCE cannot initialize properly in non-standard document mode.

Solution

  • Make sure the html file starts with a <!DOCTYPE html>single line.

Common scenarios

  • Such a problem will occur when using php\java\js and other languages ​​to write above the head of the html page.

[Solved] ES Query SIZE too large Error: ENTITY CONTENT IS TOO LONG [105539255] FOR THE CONFIGURED BUFFER LIMIT [104857600]

Leave a reply 
RequestOptions.Builder builder = RequestOptions.DEFAULT.toBuilder();
builder.setHttpAsyncResponseConsumerFactory(
          new HttpAsyncResponseConsumerFactory
            // Modified to 500MB 
            .HeapBufferedResponseConsumerFactory(300 * 1024 * 1024 ));
            request.source(SearchSourceBuilder.searchSource().query(boolQueryBuilder).size(10000));

SearchResponse response = null;
  try {
       response = yqClient.search(request, builder.build());
  } catch (IOException e) {
       e.printStackTrace();
  }

Can also be set by reflection

   // Set es query buffer size 
        RequestOptions requestOptions = RequestOptions.DEFAULT;
        Class<? extends RequestOptions> reqClass = requestOptions.getClass();
        Field reqField = reqClass.getDeclaredField("httpAsyncResponseConsumerFactory");
        reqField.setAccessible(true);
        //remove final
        Field modifiersField = Field.class.getDeclaredField("modifiers");
        modifiersField.setAccessible(true);
        modifiersField.setInt(reqField, reqField.getModifiers() & ~Modifier.FINAL);
 
        // Set the default factory 
        reqField.set(requestOptions, new HttpAsyncResponseConsumerFactory() {
            @Override
            public HttpAsyncResponseConsumer<HttpResponse> createHttpAsyncResponseConsumer() {
                //500MB
                return new HeapBufferedAsyncResponseConsumer(5 * 100 * 1024 * 1024);
            }

[Solved] mmdetection yolox Error: find_unused_parameters

Leave a reply

Updated on June 10, 2022 at 09:54:00

—————————————————————————————————

The problem is that the number of categories is not modified

————————————————————————————————————

This issue has been reported on github: https://github.com/open-mmlab/mmdetection/issues/7298

Problem Description:

I used 2 2080ti cards for training, and after a few iterations in epoch1, it stopped moving, but the gpu utilization was still floating; then I used one card for training, and the problem under this issue was reported.

Solution:

I checked all my pictures, each picture has a frame, the frame position is normal, and then I use the error message to try the method find_unused_parameters=True (add it under if distributed in mmdet/apis/train.py), under two cards Currently training 2 epochs without error, continue to observe

[Solved] kubectl error: sou-bash: _get_comp_words_by_ref: command not found

Leave a reply

After deploying the k8s cluster architecture through kubeadm, using the kubectl tool, I want to use the tab key to associate the auto-completion and find that it does not work, and the error is as follows:

[root@k8s-master]# kubectl - bash: _get_comp_words_by_ref: command not found

Google it and found out that the bash-completion package needs to be installed first. The operation is as follows:

#Install bash-completion
 yum install bash -completion -y

#source takes effect
source /usr/share/bash-completion/ bash_completion

source <(kubectl completion bash)
You can use the tab key, the problem is solved!

[Solved] kubeadm init initialize error: “unknown service runtime.v1alpha2.RuntimeService”

Leave a reply

Version: v1.24.1

 

In the test to build a k8s cluster, it is found that kubeadm init initialization error, as shown below: 

 

Looking for Google to search a lot, some bloggers said that it can be solved by deleting the config.toml file. So I made a bold attempt…

rm /etc/containerd/config.toml
systemctl restart containerd

 

After trying the above method, it is found that the problem is not solved, and the error report has new changes. 

 

 I tried the following plan again, and it worked! !

cat > /etc/containerd/config.toml << EOF
[plugins. " io.containerd.grpc.v1.cri " ]
systemd_cgroup = true 
EOF

#Restart
 systemctl restart containerd

,,,

success! ! ! ! !

[Solved] kettle Error: Unexpected problem reading shared objects from XML file: null

Leave a reply

question:

When saving  kettle the conversion, an error is reported Unexpected problem reading shared objects from XML file:null

Solution:

1. Find the C drive directory,C:\Users\Windows_login_name\.kettle

2. Open the  file and delete  the contents of the shared.xml tag <sharedobjects>

As shown below
<? xml version="1.0" encoding="UTF-8" ?> 
< sharedobjects > 
</ sharedobjects >
Finally try to save the conversion/job flow, it’s OK