Sunday, March 6, 2016

WebLogic Web Service: A jws BLA should have a package declaration

Caused by: A jws [class PVWSImpl01] should have a package declaration.
        at weblogic.wsee.deploy.DeployInfo.validate(
        at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(
        at javax.servlet.GenericServlet.init(
        at weblogic.servlet.internal.StubSecurityHelper$
        at weblogic.servlet.internal.StubSecurityHelper$
        at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(
        at weblogic.servlet.internal.StubSecurityHelper.initServletInstance(
        at weblogic.servlet.internal.StubSecurityHelper.createServlet(
        at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(
        at weblogic.servlet.internal.StubLifecycleHelper.(
        at weblogic.servlet.internal.StubLifecycleHelper.(
        at weblogic.servlet.internal.ServletStubImpl.initStubLifecycleHelper(
        at weblogic.servlet.internal.ServletStubImpl.prepareServlet(
        at weblogic.servlet.internal.WebAppServletContext.preloadServlet(
        at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(
        at weblogic.servlet.internal.WebAppServletContext.preloadResources(
        at weblogic.servlet.internal.WebAppServletContext.start(
        at weblogic.servlet.internal.WebAppModule.startContexts(
        at weblogic.servlet.internal.WebAppModule.start(
        at weblogic.application.internal.ExtensibleModuleWrapper$
        at weblogic.application.internal.ExtensibleModuleWrapper$
        at weblogic.application.utils.StateMachineDriver.nextState(
        at weblogic.application.internal.ExtensibleModuleWrapper.start(

as the error message says, it's compulsory to assign a package (package;) to your interface and implementation for your WebService and SEI.


import javax.jws.*;

@WebService(portName = "PVWLSWS01Port", serviceName = "PVWLSWS01Service", targetNamespace = "", endpointInterface = "")
public class PVWLSWS01Impl implements PVWLSWS01 {

 public String hello(String name) {
  System.out.println("Hello " + name);
  return "Hello " + name;


import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService(name = "PVWLSWS01", targetNamespace = "")
public interface PVWLSWS01 {

 @WebMethod(operationName = "hello")
 public String hello(String name);

Friday, March 4, 2016


If you get:

java.sql.SQLException: Protocol violation: [ 0, ] at oracle.jdbc.driver.T4CTTIfun.receive(
java.sql.SQLRecoverableException: Closed Connection at oracle.jdbc.driver.PhysicalConnection.needLine( at oracle.jdbc.driver.T4CXAResource.doStart(

then make sure that /jdbc-data-source/jdbc-connection-pool-params/test-connections-on-reserve is set to true

Wednesday, March 2, 2016

The JVM was unable to load the native wlfileio library , on Linux

We are getting this message:

<Warning> <Store> <BEA-280109> <The JVM was unable to load the native wlfileio library for the store "bla". File and paging stores will continue to function correctly. Specifically, file stores that are configured with a transactionally safe synchronous write policy will continue to operate safely and transactionally but may open with a different write-policy. Other store types may not be able to open.> under Synchronous Write Policy it explains a lot
Your default-file-store or file-store should be using in the LD_LIBRARY_PATH env variable one of the following folders / files (LD_LIBRARY_PATH should point to a FOLDER only, not to a specific FILE):
WL_HOME/wlserver/server/native/linux/x86_64/ WL_HOME/wlserver/server/native/linux/i686/ WL_HOME/wlserver/server/native/win/32/wlfileio3.dll WL_HOME/wlserver/server/native/win/x64/wlfileio3.dll WL_HOME/wlserver/server/native/solaris/sparc64/
Check the java.library.path which should also be initialized to the same value.
Otherwise, run weblogic with strace to find out what is going wrong
See also and see
Check also that you are using the 64 bit JVM and not the 32 bit