Re: [codehaus-cargo] 1.4.14 regression when starting weblogic

[Jorg Heymans]

Hi,

I have no idea what changed since the snapshot i tested but with the 1.4.15 release i get this during startup :

####<15-Jul-2015 13:09:02 o'clock CEST> <Critical> <WebLogicServer> <D02DI1419933AGR> <server_RDIS2DEV7L> <main> <<WLS Kernel>> <> <> <1436958542731> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException

java.lang.AssertionError: java.lang.reflect.InvocationTargetException

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:179)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:196)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:118)

at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1188)

at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:908)

at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)

at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)

at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)

at java.security.AccessController.doPrivileged(Native Method)

at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)

at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)

at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)

at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:305)

at weblogic.server.channels.ChannelService.start(ChannelService.java:263)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

Caused By: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:177)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:196)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:118)

at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1188)

at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:908)

at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)

at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)

at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)

at java.security.AccessController.doPrivileged(Native Method)

at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)

at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)

at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)

at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:305)

at weblogic.server.channels.ChannelService.start(ChannelService.java:263)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

Caused By: weblogic.security.internal.encryption.EncryptionServiceException

at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:137)

at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:185)

at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:99)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:177)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:196)

at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:118)

at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1188)

at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:908)

at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)

at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)

at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)

at java.security.AccessController.doPrivileged(Native Method)

at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)

at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)

at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)

at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:305)

at weblogic.server.channels.ChannelService.start(ChannelService.java:263)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

Jorg

On Monday, July 13, 2015 at 9:59:29 PM UTC+2, Savaş Ali Tokmen wrote:

Hey Karel

The CI is also happy - Release is now in progress.

Thank you

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

On 13/07/15 09:39, Karel Suta wrote:

Hi,

Created PR containing WLST log messages and other improvements - https://github.com/codehaus-cargo/cargo/pull/16.

Ali - After merging of this PR I think you may go for 1.4.15 release.

Br, Karel


Dne pátek 10. července 2015 8:29:36 UTC+2 Jorg Heymans napsal(a):

That's ok Karel, the benefits of using wlst are clearly there going forward. It makes sense to stick to it.

Jorg

On Thursday, July 9, 2015 at 3:05:05 PM UTC+2, Karel Suta wrote:

Hi Jorg,

Sorry for late reply.
Performance got worse than it was before. That is because new version implements WLST for domain creation and configuration, old version was directly creating configuration xml files in domain folder. Advantage of new version is that after domain is created you can invoke it without Cargo - domain contains startWeblogic script and other created files. New version offers also advanced functionality like admin username/password change when domain is created, has implemented JMS.
I can try to look for ways how to improve startup speed, but so far I didn't find anything.
Putting some stuff to output - good idea, will try to implement it :) Anyway most time of WLST execution is consumed by creating basic structure of domain from WebLogic domain template and to write domain to domain folder.

Br, Karel


Dne čtvrtek 2. července 2015 13:13:25 UTC+2 Jorg Heymans napsal(a):

I confirm NPE fix, and WLST is invoked only once. Still performance is not the same as it was before but it's a lot better, quite acceptable. Perhaps if you would output some stuff like 'creating datasources...' , 'creating queues' while executing wlst one would get the feeling that it is faster... purely cosmetic suggestion though :-)

Jorg

On Tuesday, June 30, 2015 at 8:46:19 AM UTC+2, Karel Suta wrote:

Hi Jorg,

Both things(NullPointer and slow start) should be fixed or improved now in 1.4.15-SNAPSHOT.
Please try it.

Br, Karel


Dne středa 24. června 2015 19:42:24 UTC+2 Savaş Ali Tokmen napsal(a):

Hi Jorg, Karel

Thanks a lot for this - I'll then refrain from tagging 1.4.15 until these are resolved :)

Keep the good work!

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

---

From: Karel Suta
Sent: ‎24/‎06/‎2015 10:04
To: codehau...@googlegroups.com
Subject: Re: [codehaus-cargo] 1.4.14 regression when starting weblogic

Hi,

About NullPointer - it is caused by bug in Cargo, Cargo expects some servlet users to be defined which will be put to WebLogic security domain. If you don't need any users defined you can do such workaround in pom file:

<plugin>
          <groupId>org.codehaus.cargo</groupId>
          <artifactId>cargo-maven2-plugin</artifactId>
...
          <configuration>
            <configuration>
              <properties>
                 <cargo.servlet.users/>
              </properties>
            </configuration>
          </configuration>
...

Will try to fix it soon.

About collapsing script calls - that is good point, will work on it.

Br, Karel Suta


Dne středa 24. června 2015 9:36:11 UTC+2 Jorg Heymans napsal(a):

Hi,

Apologies for not following up on this. I have tested 1.4.15-SNAPSHOT now and can confirm that weblogic is starting. However after it starts it fails immediately with a NPE:

[INFO] Total time: 42.719s

[INFO] Finished at: Wed Jun 24 09:28:35 CEST 2015

[INFO] Final Memory: 12M/32M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.15-SNAPSHOT:run (default-cli) on project sfc-fo-bridge-model-generator-war: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.15-SNAPSHOT:run failed: Failed to start the WebLogic 12.1.x container. NullPointerException -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.15-SNAPSHOT:run (default-cli) on project model-generator-war: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.15-SNAPSHOT:run failed: Failed to start the WebLogic 12.1.x container.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

at org.codehaus.classworlds.Launcher.main(Launcher.java:46)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)

Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.15-SNAPSHOT:run failed: Failed to start the WebLogic 12.1.x container.

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

... 25 more

Caused by: org.codehaus.cargo.container.ContainerException: Failed to start the WebLogic 12.1.x container.

at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:252)

at org.codehaus.cargo.maven2.ContainerStartMojo.executeLocalContainerAction(ContainerStartMojo.java:66)

at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:57)

at org.codehaus.cargo.maven2.ContainerRunMojo.doExecute(ContainerRunMojo.java:85)

at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:436)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)

... 26 more

Caused by: java.lang.NullPointerException

at java.util.StringTokenizer.<init>(StringTokenizer.java:199)

at java.util.StringTokenizer.<init>(StringTokenizer.java:221)

at org.codehaus.cargo.container.property.User.parseUsers(User.java:152)

at org.codehaus.cargo.container.weblogic.WebLogic121xWlstInstalledLocalContainer.executePostStartTasks(WebLogic121xWlstInstalledLocalContainer.java:128)

at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:233)

... 31 more

Also, I noticed that WLST is invoked several times during container configuration, this makes it much slower to start the server than before which is a bit of an issue during development. Would it not be possible to collapse all script calls into one so that WLST gets invoked only once ? 

Jorg

On Thursday, June 18, 2015 at 9:25:28 AM UTC+2, Karel Suta wrote:

Patch and JIRA entry done and merged.

Br, Karel


Dne středa 10. června 2015 19:55:40 UTC+2 Savaş Ali Tokmen napsal(a):

Hi Karel

That's excellent, I guess the problem there was the (back)slash.

Would you be so kind to create a JIRA entry and propose a patch? With this one as well, since it would be c.a. 2 months since the last release, we could also release a new CARGO version.

Cheers

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

On 10/06/15 00:23, Karel Suta wrote:

Hi Ali,

Spaces aren't ok too - on linux (Fedora)

About windows - spaces are allowed, other characters not allowed are same as for linux and includes also :(colon) and ?(question mark)
I tried just "normal" characters which can be found on standard keyboard, there can be some other special characters which can make this issue.

Big issue for windows users can be \, which is not allowed and is defaultly used as folder path. Temporary fix for 1.4.14 can be to manually define domain home path using / instead of \. Or to use 1.4.13, which doesn't contain WLST implementation.
I should fix this issue for 1.4.15 by replacing \ with / directly in application so it will work on windows out of the box.

Br, Karel


Dne pátek 5. června 2015 18:31:24 UTC+2 Savaş Ali Tokmen napsal(a):

Hi Karel

Thank you, so does this means spaces also are not OK?

Please advise

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

On 03/06/15 09:44, Karel Suta wrote:

Hi Ali,

Didn't find any documentation about restricted characters for WLST. This is what I found by my own testing.
List of characters causing problems when contained in domain path: 
* [ ] '
\ followed by number - for example \789

This was tested on Fedora, not sure about Windows environment, could check there too.
It is affecting just weblogic121x as just this version use WLST for domain and resource handling.

Br, Karel


Dne úterý 26. května 2015 20:00:55 UTC+2 Savaş Ali Tokmen napsal(a):

Hi Karel

Thanks, this is very helpful.

Do you have examples of working and "broken" paths, also the list of affected

...

[Karel Suta]

Hi Jorg,

Seems to be really weird issue in our case. I tried 1.4.15 on my own PC and WebLogic started successfully.
Found this link where they explain such error: http://weblogicscripting.blogspot.nl/2014/04/unable-to-start-admin-server-bea-000386.html
Line numbers seems slightly misaligned, but that would be caused by version differences I guess.

So problem seems to be in corrupted file SerializedSystemIni.dat. I am not sure how that could happen. Maybe it may be caused by installing new WebLogic domain over old domain which wasn't correctly deleted.
Please try to run maven build again. If it will fail with same error, try to manually delete domain folder - if it isn't defined then it is in project target folder - you may delete whole target folder.

Do you make some separate changes in domain while creating that domain - for example copying own config.xml file there or something similar?

Br, Karel



Dne středa 15. července 2015 13:12:53 UTC+2 Jorg Heymans napsal(a):

...

[Jorg Heymans]

Hi Karel,

Yes we have our own config.xml file containing @@ placeholder, as well as jdbc and jms config files that are referenced from the plugin configuration:

...
          <configuration>

            <files>

              <copy>

                <file>${project.build.directory}/cargo/config/config.xml</file>

                <tofile>config/config.xml</tofile>

                <configfile>true</configfile>

                <overwrite>true</overwrite>

              </copy>

              <copy>

                <file>${project.build.directory}/cargo/config/jdbc/activitiDataSource-jdbc.xml</file>

                <tofile>config/jdbc/activitiDataSource-jdbc.xml</tofile>

                <configfile>true</configfile>

                <overwrite>true</overwrite>

              </copy>

We always do a 'clean install cargo:run' , so there is no possibility that previous files get corrupted. Still, at some point with the snapshot things worked fine so i wonder what has changed since then ?

Jorg

[Karel Suta]

Hi Jorg,

Seems that this issue may be caused by change in default admin password. I did that change already some time ago, so it is quite surprising that error showed now.

Problem was that default weblogic admin password was "weblogic", but WebLogic security settings enforces at least one number or special character. It was ok in earlier version as password was hardcoded in config.xml so security check was bypassed, but when using WLST we have to comply validation so I changed password to "weblogic1".

Issue is in incompatibility between SerializedSystemIni.dat which is created during creation domain by WLST and config.xml where are encrypted credentials.

SerializedSystemIni.dat#sthash.KLN933XL.dpuf

How to solve it:
possibility 1: Copy SerializedSystemIni.dat configured for old password from cargo-core-container-weblogic artifact - it is stored in /org/codehaus/cargo/container/internal/resources/weblogic121x - somewhere to your project. Then copy this file to domain (same as you do with config.xml). Domain path for that file is <domain>/security
possibility 2: Overwrite encrypted credentials stored in config.xml. They should be in 3 places in that file. Try to put there "weblogic1" in plaintext - it should be ok if it is used just for test purposes. Then it may work.

Br, Karel


Dne čtvrtek 16. července 2015 8:35:04 UTC+2 Jorg Heymans napsal(a):

...

[Jorg Heymans]

Hi,

There is actually a setting for that : min-numeric-or-special-characters , see http://docs.oracle.com/cd/E15523_01/apirefs.1111/e13952/pagehelp/Securitysecurityproviderssystempasswordvalidatorproviderspecifictitle.html 

  <security-configuration xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">

    <name>test</name>

    <realm>

  ........

      <sec:name>myrealm</sec:name>

      <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">

        <sec:name>SystemPasswordValidator</sec:name>

        <pas:min-password-length>8</pas:min-password-length>

        <pas:min-numeric-or-special-characters>0</pas:min-numeric-or-special-characters>

      </sec:password-validator>

    </realm>

    <default-realm>myrealm</default-realm>

.......

    <cross-domain-security-enabled>true</cross-domain-security-enabled>

  </security-configuration>

I tried solution 2. but it gives me the same error. Solution 1. worked though, however the console password to use is "weblogic1" instead of "weblogic" what we had before. I do not know if this should be made configurable, or if this is even possible.

Thanks,

Jorg

...

[S. Ali Tokmen]

Hi Jorg, Karel

Shall we perhaps update the default password in CARGO and add this as a "warning" in the documentation?

Let me know what you think

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

--
You received this message because you are subscribed to the Google Groups "Codehaus Cargo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codehaus-carg...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codehaus-cargo/098472d3-9959-4ab0-92b6-d3ee0d90f514%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Karel Suta]

Hi Jorg, Ali,

I checked WLST documentation and there should be possible to configure password validator. Will prepare PR with fix.
After that fix I will change default password back to weblogic.

Jorg - password can be configured using property "cargo.weblogic.administrator.password". See:
https://codehaus-cargo.github.io/cargo/WebLogic+12.1.x.html - section "Standalone Local Configuration Properties"
https://codehaus-cargo.github.io/cargo/Configuration+properties.html

Br, Karel


Dne středa 22. července 2015 22:52:49 UTC+2 Savaş Ali Tokmen napsal(a):

...

[Karel Suta]

Hi Jorg, Ali,

I tried to play with password settings in WebLogic, but without success. Administration user has to have at least 8 characters including one with number or special character - this validation cannot be changed.

Jorg, can you please try to replace content of these tags in your config.xml which you copy:
<security-configuration>
...
<credential-encrypted>{AES}EB/JDAkyYyt1O8t53rxqjcnpbWYA01emTIaCL4ruqzvNMphhuyU5o5xON5h0ZphmZkvCzuREirTCgx2VelAMO6nD1gK2BlmD9E+fo+qcu9H0NKcOeYveUFFc/KNQxdgN</credential-encrypted>
...
<node-manager-password-encrypted>{AES}F2Di2uxPDYCPQUr+DyvFZrI3vOPdj+y6y42Xrb4zX7E=</node-manager-password-encrypted>
...
</security-configuration>

  <embedded-ldap>
...
    <credential-encrypted>{AES}Zrl4P15iiQmqOPq9Lyn2Fl/vnbCmwrtgIP9YjjqVKuKIXzNhTwen8ZVWfi47rm/U</credential-encrypted>
  </embedded-ldap>


That should be encrypted "weblogic1" password. I hope it will help.

Ali: Password information should be updated on WebLogic properties page, adding warning can be good idea as this is tricky change, can confuse people.
Can you please prepare such warning? I am not much familiar with Cargo documentation changes.

Thank you both.

Br, Karel


Dne pátek 24. července 2015 9:13:31 UTC+2 Karel Suta napsal(a):

...

[S. Ali Tokmen]

Hi Karel

You know best :) I let you also propose the patch, as soon as the CI passes I'll accept your request.

Cheers

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

--

You received this message because you are subscribed to the Google Groups "Codehaus Cargo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codehaus-carg...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/codehaus-cargo/580afa00-1bdd-457c-b783-b823ab2f44bc%40googlegroups.com.

[Jorg Heymans]

Hi,

It's ok for us with the current situation. But users should be aware, maybe you could print a message to stdout about the pwd while creating the domain ? 

Jorg

...

[S. Ali Tokmen]

Hi Jorg, Karel

I updated the documentation for all WebLogic containers - See here: https://codehaus-cargo.github.io/cargo/WebLogic+12.1.x.html (scroll down a bit and you'll see). I pasted there the full error message as well so perhaps it's easier to find.

What do you think?

Cheers

S. Ali Tokmen
http://ali.tokmen.com/
http://contact.ali.tokmen.com/

--

You received this message because you are subscribed to the Google Groups "Codehaus Cargo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codehaus-carg...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/codehaus-cargo/553d142b-a120-4f06-9dfd-7490c2933297%40googlegroups.com.

[Jorg Heymans]

looks good to me

Jorg

...

[Karel Suta]

Looks good.
Maybe lately I will try to prepare some summary about what can be configured on WebLogic and how.

Br, Karel

Dne čtvrtek 30. července 2015 6:38:24 UTC+2 Savaş Ali Tokmen napsal(a):

...