search

eclipse-ee4j / glassfish

Eclipse GlassFish
https://eclipse-ee4j.github.io/glassfish/
384 stars 143 forks source link

[BLOCKING] Glassfish 2.1.1Patch8 Enterprise profile (HADB) to Glassfish 3.1 Upgrade #15108

Closed glassfishrobot closed 13 years ago

glassfishrobot commented 13 years ago

Refer http://java.net/jira/browse/GLASSFISH-14970

" B32 Nightly "

followed the manual steps of copying cacerts.jks and keystore.jks to domain1/config directory. copied glassfish3/glassfish/lib/templates/server.policy to the v2 domain1/config dir ./asadmin start-domain --upgrade domain1 ./asadmin start-domain domain1

We get a lot of SEVERE messages in server.log. Please check the attachment. http://:4848 page is blank. Nothing is displayed in the browser.

SEVERE message (1)

[#|2010-12-10T14:01:13.845+0530|SEVERE|sun-appserver2.1.1|javax.enterprise.system.tools.deployment|_ThreadID=24;_ThreadName=Thread-264;_RequestID=5af3d7b4-c9a8-43d1-8478-500c570601fe;|Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException: Deployment Errorjava.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused. – Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused. Error Code: 0 at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:305) at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:150) at oracle.toplink.essentials.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:184) at oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:582) at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:280) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:230) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:93) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:138) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:132) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:91) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.loadPersistenceUnitBundle(PersistenceProcessor.java:573) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.createTablesInDB(PersistenceProcessor.java:421) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processAppBundle(PersistenceProcessor.java:287) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:189) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122) at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79) at com.sun.enterprise.deployment.backend.ModuleDeployer.handlePostDeployEvent(ModuleDeployer.java:639) at com.sun.enterprise.deployment.backend.ModuleDeployer.postDeploy(ModuleDeployer.java:628) at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:191) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:208) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:283) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:835) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:225)

| #] |

SEVERE message 2 [#|2010-12-11T09:58:01.144+0530|SEVERE|glassfish3.1|javax.enterprise.resource.corba.org.glassfish.enterprise.iiop.impl|_ThreadID=16;_ThreadName=Thread-1;|iiop.init_exception java.lang.RuntimeException: java.lang.IllegalStateException: IIOP1004: Key alias s1as not found in keystore at com.sun.enterprise.iiop.security.IIOPSSLUtilImpl.getKeyManagers(IIOPSSLUtilImpl.java:115) at org.glassfish.enterprise.iiop.impl.IIOPSSLSocketFactory.init(IIOPSSLSocketFactory.java:246) at org.glassfish.enterprise.iiop.impl.IIOPSSLSocketFactory.(IIOPSSLSocketFactory.java:148) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.corba.ee.impl.orb.ParserTable$4.operate(ParserTable.java:757) at com.sun.corba.ee.impl.orb.NormalParserAction.apply(NormalParserAction.java:62) at com.sun.corba.ee.spi.orb.PropertyParser.parse(PropertyParser.java:84) at com.sun.corba.ee.spi.orb.ParserImplBase.init(ParserImplBase.java:77) at com.sun.corba.ee.impl.orb.ORBDataParserImpl.(ORBDataParserImpl.java:493) at com.sun.corba.ee.impl.orb.ORBImpl.postInit(ORBImpl.java:569) at com.sun.corba.ee.impl.orb.ORBImpl.set_parameters(ORBImpl.java:704) at com.sun.corba.ee.impl.orb.ORBImpl.setParameters(ORBImpl.java:691) at com.sun.corba.ee.spi.osgi.ORBFactory.initialize(ORBFactory.java:107) at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.initORB(GlassFishORBManager.java:581) at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.getORB(GlassFishORBManager.java:263) at org.glassfish.enterprise.iiop.impl.GlassFishORBFactoryImpl.createORB(GlassFishORBFactoryImpl.java:93) at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getORB(GlassFishORBHelper.java:120) at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getProtocolManager(GlassFishORBHelper.java:187) at com.sun.ejb.containers.BaseContainer.initializeProtocolManager(BaseContainer.java:818) at com.sun.ejb.containers.BaseContainer.(BaseContainer.java:566) at com.sun.ejb.containers.StatelessSessionContainer.(StatelessSessionContainer.java:155) at com.sun.ejb.containers.StatelessSessionContainer.(StatelessSessionContainer.java:149) at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:105) at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:234) at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:290) at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:101) at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:249) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460) at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:351) at com.sun.enterprise.v3.server.ApplicationLoaderService.postConstruct(ApplicationLoaderService.java:202) at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.java:128) at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreator.java:88) at com.sun.hk2.component.AbstractCreatorImpl.get(AbstractCreatorImpl.java:79) at com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:64) at com.sun.hk2.component.EventPublishingInhabitant.get(EventPublishingInhabitant.java:136) at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:73) at com.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:243) at com.sun.enterprise.v3.server.AppServerStartup.start(AppServerStartup.java:135) at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.start(GlassFishImpl.java:79) at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:97) at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55) Caused by: java.lang.IllegalStateException: IIOP1004: Key alias s1as not found in keystore at com.sun.enterprise.iiop.security.IIOPSSLUtilImpl.getKeyManagers(IIOPSSLUtilImpl.java:96) ... 51 more

| #] |

SEVERE message 3

[#|2010-12-11T10:25:28.432+0530|WARNING|glassfish3.1|grizzly|_ThreadID=16;_ThreadName=Thread-1;|GRIZZLY0059: PortUnification exception. java.lang.NullPointerException at com.sun.grizzly.config.SSLConfigHolder.createSSLEngine(SSLConfigHolder.java:193) at com.sun.grizzly.config.HttpProtocolFinder.find(HttpProtocolFinder.java:115) at com.sun.grizzly.config.ConfigProtocolFinderWrapper.find(ConfigProtocolFinderWrapper.java:72) at com.sun.grizzly.portunif.PUReadFilter.findProtocol(PUReadFilter.java:512) at com.sun.grizzly.portunif.PUReadFilter.execute(PUReadFilter.java:188) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:619)

| #] |

Environment

Solaris sparc, Linux 5

Affected Versions

[3.1_dev]

glassfishrobot commented 6 years ago
glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: As http://java.net/jira/browse/GLASSFISH-14970 is closed I am opening a new issue, which is an extension of 14970.

glassfishrobot commented 13 years ago

@glassfishrobot Commented nitkal said: Can you please provide us the details of the domain that is being upgraded, so that we could analyze the errors. Also, please let us know the steps that have been followed so far, in more detail, so that it helps us narrow down the cause.

Thanks Nithya

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: 1)the details steps aare as per the instruction of http://wikis.sun.com/display/GlassFish/V3.1ClusterUpgradeExample In adition to it, 2)v211 P8 bundle EE profile from http://milestone.india.sun.com/java/re/glassfish/v2.1.1-sust/promoted/p08/b01/bundles/sges_ee-2_1_1-p08-solaris-sparc.bin for sparc http://milestone.india.sun.com/java/re/glassfish/v2.1.1-sust/promoted/p08/b01/bundles/sges_ee-2_1_1-p08-linux.bin for linux 3)All the workarouds of " 14970 " this includes copy of domain1 dir from v211 p8 installation. 4) workarounds of http://java.net/jira/browse/GLASSFISH-11665. To isolate the master password issue (what 14970 is about), you can comment out this line in domain.xml:

-Djava.security.manager

copy certs file :

1. Copy and save cacerts.jks from V3.1 installation before copying the V2.1.1 domain over to V3.1 2. Copy the V2.1.1 domain over to V3.1 3. Copy cacerts.jks (saved in step 1) into V2.1.1 domains config directory 4. copy glassfish3/glassfish/lib/templates/server.policy to the v2 domain1/config dir

glassfishrobot commented 13 years ago

@glassfishrobot Commented nitkal said: These errors are being caused because the upgraded v3 domain.xml does not contain the jvm-options for keystore and truststore:

-Djavax.net.ssl.keyStore=$

{com.sun.aas.instanceRoot}/config/keystore.jks -Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}

/config/cacerts.jks

These are to be added to the v3 domain.xml before startup. This step is documented in the wiki : http://wikihome.sfbay.sun.com/security/Wiki.jsp?page=V2.XEEToV3.1NSSUpgrade

It appears that these wiki instructions are not followed during the upgrade. The link that is provided in the bug description (viz) http://wikis.sun.com/display/GlassFish/V3.1ClusterUpgradeExample does not seem to contain the link to the above wiki for NSS upgrade.

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: There are so many manual steps and workaround for upgrade. Are these workaround getting integrated in the product?

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: B35

v211 Patch8 to Glassfish V3 upgrade with NSS

Followed the before and after upgrade instruction http://wikis.sun.com/display/GlassFish/V3.1ClusterUpgradeExample and http://wikis.sun.com/display/GlassFish/NSS+upgrade+instructions

I am stuck at Manual Steps to be Carried out after upgrade ( http://wikis.sun.com/display/GlassFish/NSS+upgrade+instructions)

1. Start the server and run the following command ./asadmin --secure=true create-ssl --type http-listener --certname s1as admin-listener I am getting error as

java.net.SocketException : Unexpected end of file from server. I have attached the server.log.b35

glassfishrobot commented 13 years ago

@glassfishrobot Commented @vbkumarjayanti said: Please attach the domain.xml for this error and the also attach keystore.jks present in the domain/config

glassfishrobot commented 13 years ago

@glassfishrobot Commented @vbkumarjayanti said: asadmin --secure=true create-ssl ...

this command is not owned by the security team. Request someone from admin team to reassign the bug appropriately. The server log attached contains nothing useful (no exceptions...).

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: So what am I fixing? It says it can't find the alias in the keystore... Looks like a config problem...

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: Two thoughts:

1. this isn't a 2.1.1 configuration file. Whatever the issue here is, it should probably have been opened under a new issue. It doesn't seem to be upgrade-related at all. 2. I'm not entirely sure why this ended up on my plate. It's not a grizzly or an admin issue. I'm not sure what the problem is but it seems like the cacerts.jks and keystore.jks files are out of date.

The system starts fine with the provided domain.xml and only chokes with the keystore file is added. I'm going to reassign this to the security team to look at. It's outside of my area of expertise at this point.

glassfishrobot commented 13 years ago

@glassfishrobot Commented @vbkumarjayanti said: Justin :

According to the comments last, here is what the QE sss150302 reopened the bug with

1. Start the server and run the following command ./asadmin --secure=true create-ssl --type http-listener --certname s1as admin-listener I am getting error as

java.net.SocketException : Unexpected end of file from server. I have attached the server.log.b35

this means the server starts fine as such but running the create-ssl command gives the above error.

Since create-ssl is not a command handled by the security team i asked Tom to reassign. The problem at this point could be with create-ssl or with --secure=true both of which are not handled by the security team.

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: I'm actually getting PKIX errors on startup which is why i bumped it back. Are you not seeing that when you try? What I'm doing to test, and this might be where I'm doing it wrong, is I'm creating a v3 distribution, copying over the domain.xml and the keystore.jks from the issues and trying to start up the server. Doing that gets me the PKIX errors so I haven't even gotten to the create-ssl steps. If I'm missing something, I'd be happy to correct and try again, though.

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: Please follow the steps as per the doc http://wikis.sun.com/display/GlassFish/V3.1ClusterUpgradeExample 2)Get v211 P8 bundle EE profile from http://milestone.india.sun.com/java/re/glassfish/v2.1.1-sust/promoted/p08/b01/bundles/sges_ee-2_1_1-p08-solaris-sparc.bin for sparc 3)Follow the before and after upgrade instruction http://wikis.sun.com/display/GlassFish/NSS+upgrade+instructions

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: OK. I think i see the main issue. You're trying to issue a secure asadmin command on a system that isn't configured for a secure admin listener. passing --secure=false to create-ssl succeeds. Can you try that and see what happens.

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: Did you try it yourself? I still got the same error ./asadmin --secure=false create-ssl --type http-listener --certname s1as admin-listener java.net.SocketException : Unexpected end of file from server. Command create-ssl failed.

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: Of course, I tried it. I also scripted it so I could recreate the steps I took. Attached is the script auto.sh.

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: the script auto.sh that scripted uses a cluster profile bundle of v2.1.1 (fcs) for upgrade. This is a cluster profile upgrade. "We do not have issue with cluster profile upgrade".

We have a issue with Enterprise profile Upgrade. You must use EE bits of v211 if you use v211 P8 bundle EE profile from http://milestone.india.sun.com/java/re/glassfish/v2.1.1-sust/promoted/p08/b01/bundles/sges_ee-2_1_1-p08-solaris-sparc.bin for sparc http://milestone.india.sun.com/java/re/glassfish/v2.1.1-sust/promoted/p08/b01/bundles/sges_ee-2_1_1-p08-linux.bin for linux then we will be on the same page.

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: I tried that but it wouldn't install without a 1.5 JVM which isn't supported on this version of OS X. I can fire up a VM with linux and try again. But is there any way to install this version of SGES without using that installer or bypassing the JVM version check?

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: Is India really the only place to download these bundles? It literally takes almost half a day to download these things over the VPN.

glassfishrobot commented 13 years ago

@glassfishrobot Commented @ssevozen said: Justin, first of all, you will really need to use either Linux or Solaris for this since enterprise profile was never supported on MacOS at all, regardless of JDK version. Also, patches should be also be available on SunSolve with presumably better download performance, I'll take a look and drop you an e-mail.

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: OK. I have a linux VM locally and dhiru has set me up with an ubuntu box in his office for testing which is what i'm using now. He could download those bundles much more quickly than I could so he downloaded what i needed and put it on that box.

glassfishrobot commented 13 years ago

@glassfishrobot Commented @ssevozen said: Good, because I completely forgot that SunSolve moved to My Oracle Support back in December so that was non-starter

glassfishrobot commented 13 years ago

@glassfishrobot Commented ai109478 said: Justin is working on this.

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: Whew. I had to wrestle this to the ground but I finally got the upgrade process work. Mostly. create-ssl was indeed failing on linux with 1.6_20. Upgrading to _22 fixed the problem for me. Could you try that and see what happens?

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: Could you follow up, please?

glassfishrobot commented 13 years ago

@glassfishrobot Commented sss150302 said: I upgraded to latest jdk -1.6._23 on sparc

copied freshly domain1 and followed the NSS workaround doc. ./asadmin start-domain --upgrade domain1 ---> passed no exception in server.log ./asadmin start-domain domain1 ---> passed no exception in server.log

bash-3.00# ./asadmin --secure=true create-ssl --type http-listener --certname s1as admin-listener Enter admin user name> admin Enter admin password for user "admin"> ( Here I entered adminadmin ) remote failure: Network Listener named admin-listener to which this ssl element is being added already has an ssl element. Command create-ssl failed. bash-3.00# ./asadmin --secure=false create-ssl --type http-listener --certname s1as admin-listener Enter admin user name> admin Enter admin password for user "admin"> ( Here I entered adminadmin ) remote failure: Network Listener named admin-listener to which this ssl element is being added already has an ssl element. Command create-ssl failed. pwd /space/31/upgrade/glassfish3/glassfish/bin bash-3.00# ./asadmin stop-domain domain1 Waiting for the domain to stop ... Command stop-domain executed successfully. bash-3.00# ./asadmin start-domain domain1 Waiting for domain1 to start ......................................... Successfully started the domain : domain1 domain Location: /space/31/upgrade/glassfish3/glassfish/domains/domain1 Log File: /space/31/upgrade/glassfish3/glassfish/domains/domain1/logs/server.log Admin Port: 4848 Command start-domain executed successfully.

Now in browser https://ejp-156s-46.india.sun.com:4848/ Does not give the login user name and password window for a long time. I need to reload the page, as browser refresh. then the browser loaded and shown admin username password I Entered admin / adminadmin , url turns to https://ejp-156s-46.india.sun.com:4848/j_security_check And I get

" Authentication failed " message. screen attached as upgraded-admin-b35-jdk6u23.png

The server.log does not show any warning SEVERE message.

Here is the log that I got , detail log attached as server.log.jdk6u23 domain.xml attached as domain.xml.upgraded.jdk6u23

[#|2011-01-11T14:24:35.496+0530|INFO|glassfish3.1|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=15;_ThreadName=Thread-1;|Initializing Mojarra 2.1.0 (SNAPSHOT b09) for context ''|#]

[#|2011-01-11T14:24:56.383+0530|INFO|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=15;_ThreadName=Thread-1;|WEB0671: Loading application [__admingui] at [/]|#]

[#|2011-01-11T14:24:56.388+0530|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=15;_ThreadName=Thread-1;|CORE10010: Loading application __admingui done in 32,756 ms|#]

[#|2011-01-11T14:24:56.388+0530|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=15;_ThreadName=Thread-1;|The Admin Console application is loaded.|#]

[#|2011-01-11T14:27:00.463+0530|INFO|glassfish3.1|com.sun.jersey.server.impl.application.WebApplicationImpl|_ThreadID=15;_ThreadName=Thread-1;|Initiating Jersey application, version 'Jersey: 1.5-ea08 12/10/2010 02:57 PM'|#]

[#|2011-01-11T14:27:14.590+0530|INFO|glassfish3.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=15;_ThreadName=Thread-1;|Listening to REST requests at context: /management/domain|#]

[#|2011-01-11T14:28:10.891+0530|WARNING|glassfish3.1|org.apache.catalina.connector.Request|_ThreadID=15;_ThreadName=Thread-1;|PWC4011: Unable to set request character encoding to UTF-8 from context , because request parameters have already been read, or ServletRequest.getReader() has already been called|#]

[#|2011-01-11T14:28:46.721+0530|WARNING|glassfish3.1|org.apache.catalina.connector.Request|_ThreadID=15;_ThreadName=Thread-1;|PWC4011: Unable to set request character encoding to UTF-8 from context , because request parameters have already been read, or ServletRequest.getReader() has already been called|#]

[#|2011-01-11T14:29:01.828+0530|WARNING|glassfish3.1|org.apache.catalina.connector.Request|_ThreadID=15;_ThreadName=Thread-1;|PWC4011: Unable to set request character encoding to UTF-8 from context , because request parameters have already been read, or ServletRequest.getReader() has already been called|#]

glassfishrobot commented 13 years ago

@glassfishrobot Commented ap2257 said: Assigning the bug back to Engineering. Not sure who the engineer should be, thus, I've assigned the Dev manager as the assignee.

glassfishrobot commented 13 years ago

@glassfishrobot Commented bbissett said: Am assigning back to Kumar for an answer to where we're stopped.

I'm getting the same message as sss150302 at the first manual step after the upgrade:

kamakawiwoole% ./asadmin --secure=true create-ssl --type http-listener --certname s1as admin-listener remote failure: Network Listener named admin-listener to which this ssl element is being added already has an ssl element. Command create-ssl failed.

Without this, I don't expect the admin console to load properly. Kumar, can clarify what the step should be to create the proper info in the config?

Here is the admin-listener protocol element in server-config right after the upgrade:

It's unchanged after the failed create-ssl call. Is there a different call that should be made, or does this need to be edited manually (and if so, what's the final result)?

glassfishrobot commented 13 years ago

@glassfishrobot Commented @vbkumarjayanti said: This seems like a bug in create-ssl command and i do not own the create-ssl command..

glassfishrobot commented 13 years ago

@glassfishrobot Commented cheeser said: I don't think it's a create-ssl issue at all. The problem is at the transport layer where it's not return a valid document. An error from the command would look different. It's a configuration/JDK issue from what I've seen.