OK, got it.
The problem is that launchctl bsexec requires root privileges. When I changed that to nohup everything works just fine.
Checkout sources from
https://svn.java.net/svn/glassfish~svn/trunk/main/ <
https://svn.java.net/svn/glassfish~svn/trunk/main/>, apply the attached patch, build and everything starts work. The location of the server is in appserver/distributions/glassfish/target/stage/glassfish4.
The only issue I have right now is that NetBeans are unable to recognize the server. Will give it a try.
Good luck.
Cheers,
PETR
> On 17. 4. 2015, at 9:44, William <streetpoet_at_163.com> wrote:
>
> yes, I have the exactly issue. Starting fail in console mode, But can startup in eclipse using plugin.
>
> <PastedGraphic-1.png>
>
>> On Apr 17, 2015, at 2:24 PM, Petr Hadraba <hadrabap_at_gmail.com <mailto:hadrabap_at_gmail.com>> wrote:
>>
>> Hello all,
>>
>> I’ve updated my OS X machine to the all latest updates and patches and that results into Glassfish 4.1 is unable to start:
>>
>> Petrs-MacBook-Pro:bin petr$ ./asadmin start-domain domain1
>> JVM failed to start: com.sun.enterprise.admin.launcher.GFLauncherException: The server exited prematurely with exit code 1.
>> Before it died, it produced the following output:
>>
>>
>> Command start-domain failed.
>>
>> I’ve figure-out that launching the command in verbose mode works just fine.
>>
>> ./asadmin start-domain --verbose domain1
>>
>> But in this case the JMX does not work. It complains about Connection Timeout to bind to my “public” IP address. The workaround is to set the JMX to listen only on localhost instead of 0.0.0.0.
>>
>> It seams that Apple has removed some API (maybe deprecated for some time) which is used by asadmin.
>>
>> Is here somebody else running Glassfish on the latest patched (up-to-date) OS X 10.10.3 and facing the same issues?
>>
>> I’ve reported that at GLASSFISH-21350 <https://java.net/jira/browse/GLASSFISH-21350>.
>>
>> Thanks in advance.
>>
>> Sincerely yours,
>>
>> PETR
>>
>